This file describes the tasks at hand for making Calligra Sheets a better product.

Legend
======

Status field

----	No work has been done on this (sub)task yet.
DONE    Task is all done
done    This subtask is done
****	This (sub)task cannot be fixed with the current technology.
        It has to wait until something in the internals is fixed.

Prio field

S	Involves string changes.  Must be done before the freeze.
1	Important task.  Should definitely be fixed.
2	Semi-important task.  Should be fixed if possible, but can be
	moved to the next release if necessary.
3	Nice to have.  Should be fixed if there is time. (yeah, right)



BUGS
====
 ---    Painting shapes in RTL layouted sheet is still broken.
 ---    Printing shapes is broken.
 ---    AutoFormatCommand does not redo() properly.




Things to do after the release of Calligra 2.0
=============================================

Item										Prio	Status
----------------------------------------------------------------------------------------------

* Overhaul/Redesign dialogs:
  - "Conditional Styles...": port to .ui file(s); use QTableWidget;             3       ----
    allow more than three conditions; list all cell ranges holding a condition,
    that intersect the cell selection; display the cell range in an extra column
    in the list; allow to choose between those cell ranges and the current cell
    selection; if there are no stored conditions yet or the only stored one's
    range matches the cell selection, hide the list's cell range column; extend
    the conditions to allow cell content text length comparisons and formulas;
    'Reset' button to restore conditions; 'Clear'/'Defaults' button to clear all
    intersecting conditions or just the selected part of them (obsoletes 'Remove
    Conditional Styles' action); rename to just "Conditional Styles..."
  - "Validity...": same as for "Conditional Styles..."; move the error message
    and information panel into the list by using KExtenableItemDelegate
  - "Named Areas...": port to .ui file(s); use QTableWidget; move the cell range
    display into the list editable with a RegionSelector; remove the ability to
    select a named area by moving this functionality into the "Bookmarks" menu
  - "Custom Lists...": port to .ui file(s); use QListWidget; display as is, but
    edit with KTextEdit (one item per row); find a common place for storing
    the (pre-)defined lists (maybe store them all in the config file; if a
    predefined list gets removed, one can restore it by pressing "Defaults");
    the lists are used by the sort dialog and for auto-filling
  - "Insert Comment...": 'Reset' button to restore former comment after editing;
    'Clear'/'Defaults' button to remove comment (obsoletes 'Remove Comment'
    action); rename to just "Comment..."; range-based: put the cell ranges into
    the list as planned for "Conditional Styles..."?
  - "Insert Link...": same as for "Insert Comment...", if applicable

* Source code organization                                                      3       ----
  - Move various features to standalone modules (could be statically linked)

* User Interface                                                                1       ----
  - Add a 'Go' ('Navigation') menu to select the active sheet. Reuse the actions
    from the 'Navigation' toolbar and add a sheet list (use KSelectAction?).
    'View' -> 'Goto Cell' should be moved there, too.
  - 'Rename sheet', 'Duplicate sheet' are also missing in the menu. Move
    them into 'Edit' -> 'Sheet'?
  - 'Auto-Fill' (selection change with size grip) is missing in the menu.
  - Improve conformance to the standard menu layout:
    `kde4-config --install config`/ui/ui_standards.rc
  - Figure out, if it's feasible to add a 'Bookmarks' menu that handles
    named areas.
  - Figure out, if the 'Insert' menu could be merged into the 'Data' menu
    and the 'Data' menu moved in front of the 'Format' menu.
  - Figure out, which 'Data' entries are 'Tools'. They are all affecting
    the data, but also they act like tools. E.g. inserting a comment
    is not tool-like, it's definitely belonging to the 'Data' menu.
  - Would a 'Document' menu containing cell, column, row and sheet related
    actions be a sensible choice?
    'Document': actions, that act on the document (map/sheet) structure
    'Data': actions, that insert new data or remove data
    'Format': actions, that act on the visualization of existing data
    'Tools': actions, that manipulate existing data
    'Edit': difference to 'Data'? only standard editing actions?
  - Alternatives to 'Document':
    'Layout', 'Design', 'Structure', 'Scheme'
    two menus: 'Workbook' and 'Sheet', 'Table'
  - disable sub-menu entries, if all of their actions are disabled (KDElibs!)

* Inform the user about unreachable/unsupported document data on loading.       1       ----

* Load/Save of embedded objects for the old XML format                          1       ----
  see KSPREAD_KOPART_EMBEDDING

* Copy shapes on copying sheet                                                  1       ----
  see KSPREAD_WIP_COPY_SHEET_(SHAPES)

* Loading of old document attributes.                                           1       ----
  see KOXML_USE_QDOM

* Check, if the DTD of the old XML format is up to date.                        2       ----
  Specifically, the border handling (see Sheet::convertObscuringBorders()).
  Implement conditional style saving for 1.1, 1.2 syntax.

* User Interaction:                                                             2       ----
  The canvas does not react on context menu key events.

* Loading/Saving of unreachable (e.g. rows > KS_rowMax) document data.          2       ----

* Commands
  Undo of cell border setting does not restore the border of the adjacent cell. 2       ----
  see KSPREAD_WIP_STYLE_BORDER

* User Interaction:                                                             2       ----
  Check, if the edit widget in the CellTool acts like the EditWidget before.
  see KSPREAD_DISCARD_FORMULA_BAR

* User Interaction                                                              3       ----
  Implement a completion aware KTextEdit. (see Editors.cpp)
  see KSPREAD_COMPLETION_MODE_SETTING

* Commands                                                                      3       ----
  CellStorage: Replace CellStorageUndoData* by a QStack<CellStorageUndoData>,
  so that cascaded undo recordings become possible.

* Style-/RectStorage: Check, if QSharedPointer can be used instead of           3       ----
  Q(Explicitly)SharedDataPointer. This would automagically remove unused
  pointers/data.

* SpellCheck: Save the ignored words to document.                               3       ----
  Doc::addIgnoreWord() et al.

* D-Bus support                                                                 3       ----
  Some old DCOP code parts were not converted yet.

* User Interaction:                                                             3       ----
  Implement a drag indicator. If possible in DragAndDropStrategy, but this
  needs KoInteractionTool/-Strategy to handle dragMove-/dropEvents.
  see KSPREAD_WIP_DRAG_REFERENCE_SELECTION

* Thread support                                                                3       ----
  Move the dependency calculation and cell recalculation into a separate
  thread. In a first step the data manipulating actions should be disabled
  while running the cell recalculation. These actions could also become
  threaded later on. And as a final step, only actions acting on the
  affected cell ranges should be disabled, so the user can continue his/her
  work in other parts of the document.

* Databases									3	----
  Currently Database is used solely for the autofilter functionality.
  Generalize it: Rewrite the filter code, so that Database carries a data
  model. Such a generic data providing class will allow to add data imports of
  any textual kind.
  The OpenDocument spec urges to implement database queries, sorting and
  subtotal implementation this way.

* Page View Mode								3	----
  Add a page view mode. This would be a more intuitive way to see the printing
  layout. The pages should be based on KoShapeContainer, so that the TableShape
  becomes a child of it and can rely on its dimension to layout the table
  pages.
  The column/row header have to be adjusted to be usable with the table shape.
  Or new, specialised classes take care of this.

* Source-/TargetRange concept							3	----
  Currently, cell ranges, which data is exported, are called Binding. The
  opposite, cell ranges, that contain imported data, are called Database.

  Binding's only tasks are to track the movement of the range and to inform
  about value changes. To achieve this it contains a data model, which is used
  by those who want to work with the range's data. Nothing more; very
  minimalistic, very generic. The term SourceRange fits well here.

  Database, on the other hand, is more specialised, even if the filter code
  gets rewritten, so that Database contains a data model. That's because it
  was developed according to the database range in the OpenDocument spec and
  this consists of more than just a target range. For the case of filters or
  sorting, such a database always has got a source and optionally a target
  range, where the filtered or sorted output gets written to. Because of that
  the stored range should be separated from Database and named TargetRange.

  TargetRange will contain a data model, like SourceRange fka. Binding does,
  but retrieves data from it instead of feeding data to it. Additionally,
  both, SourceRange and TargetRange need a method delivering the current cell
  region name, because the range can be moved due to column/row/cell range
  insertions/removals.

  External apps or shapes or internal objects should work with an abstract
  interface, that provides the model and the cell region name, instead of
  directly working with the data model. E.g. KoChart needs the correct cell
  region names in the dialogs even after the source ranges have moved.

  Same should be true for the Database's target range, even though the
  OpenDocument spec does not distinguish between absolute and relative
  addresses. My interpretation is that this means the cell ranges are fixed.
  (e.g. OpenDocument v1.1, 8.7.1 Table Filters, Table Range Address: "A differ-
  entiation between absolute and relative addresses is not possible. Therefore,
  a table name has to exist in the address and dollar signs are ignored.")
  OpenOffice does allow their movement though; an autofilter moves there.
  Calligra Sheets should go the most generic way: allow range movements and allow
  to fix the ranges by dollar signs, even if these are ignored in the ODF in
  this case.

  Summary:
  1. Binding* becomes SourceRange*.
  2. Refactor Database, so that it refers to a TargetRangeModel.
  3. DatabaseStorage becomes TargetRangeStorage.

* Port the editor's function auto-completion to KCompletion.                    3       ----

* Implement a QValidator accepting cell locations, cell ranges and named areas. 3       ----
  Usable for LocationComboBox and RegionSelector.

* Elaborate, if for the user input validation (Validity) a QValidator can be    3       ----
  used for the embedded/external editor.

* Implement a PointStorage::Iterator, which iterates over the non-default data  3       ----
  in a cell range/region in horizontal or vertical direction.

* Harmonize conditions for content validation, filters and conditional styles.  3       ----
     8.5.3 Table Cell Content Validations
            Condition ::= ExtendedTrueCondition | TrueFunction 'and' TrueCondition
            TrueFunction ::= cell-content-is-whole-number() | cell-content-is-decimal-number() | cell-content-is-date() | cell-content-is-time() | cell-content-is-text()
            ExtendedTrueCondition ::= ExtendedGetFunction | cell-content-text-length() Operator Value
            TrueCondition ::= GetFunction | cell-content() Operator Value
            GetFunction ::= cell-content-is-between(Value, Value) | cell- content-is-not-between(Value, Value)
            ExtendedGetFunction ::= cell-content-text-length-is-between(Value, Value) | cell-content-text-length-is-not-between(Value, Value) | cell-content-is-in-list( StringList )
            Operator ::= '<' | '>' | '<=' | '>=' | '=' | '!='
            Value ::= NumberValue | String | Formula
            StringList ::= StringList ';' String | String
            A Formula is a formula without an equals (=) sign at the beginning. See section 8.1.3 for
            more information.
            A String comprises one or more characters surrounded by quotation marks.
            A NumberValue is a whole or decimal number. It must not contain comma separators for
            numbers of 1000 or greater.
     8.7.4 Filter Condition
            match (matches)
            !match (does not match)
            In both case, the table:value attribute contains the regular expression that the table cells have
            to match or must not match.
            The relational operators that do not use regular expressions are:
            = (Equal to)
            != (Not equal to)
            < (Less than)
            > (Greater than)
            <= (Less than or equal to)
            >= (Greater than or equal to)
            In addition, operators “empty”, “!empty”, “bottom values”, “top values”, “bottom percent”, and “top
            percent” can be used. To filter for example the lowest and highest percentage values, the latter
            two operators can be used.
    14.1.1 Style Mappings (Conditional Styles)
            is-true-formula(formula)
            cell-content-is-between(value, value)
            cell-content-is-not-between(value, value)
            cell-content() operator value, where operator is one of; '<', '>', '<=', '>=',
            '=' or '!=', and value is a numberValue, a string or a formula.
            A numberValue is a whole or decimal number. The number cannot contain comma
            separators for numbers of 1000 or greater.
            A string comprises one or more characters surrounded by quotation marks.
            A formula is a formula (see 8.1.3) without the equals (=) sign at the beginning.

* MapViewModel aka. ViewController (or CanvasController?)                       3       ----
    Inherit from QAbstractProxyModel with MapModel as source.
    Manages:
        - active sheet handling incl. sheet navigation ("Go" menu) and shape
          additions/removals
        - named areas ("Bookmarks" menu)

* Modularization                                                                3       ----
    The goal is to make Calligra Sheets more modular. Functionality like cell content
    validation (Validity), source and target cell ranges for external data or
    named areas should become optional. Maybe even more like (conditional)
    styles, comments, cell fusions, etc, so that what's left is the bare
    minimum: user inputs, formulas and values (btw: all stored with
    PointStorage).
    [Point- and RectStorage could also become (low-level) plugins, in order to
    replace them more easily in the future. The storage plugins and the 'core'
    storages should then use these low-level plugins.]
    Plugin categories:
        - FunctionModule
            a set of functions
        - Tool
            cell tool derivative, that works with Selection; should leave actions from other tools
            working with Selection activated; viewers do not need editing tools
        - Storage
            viewers do not need all of them, e.g. cell content validation or cell range locks
        - Manager
        - (Dialog) [could be part of a tool]
            viewers do not need all of them
        - (Command) [could be part of a tool]
            not needed by viewers
        - (Feature) [could also be achieved with plugin dependencies]
            combines other categories, e.g. loads a storage, dialog and command for cell content
            validation
    Steps to go:
    - Extract an interface for RectStorages (or even better for both, Point-
      and RectStorage) based on QAbstractItemModel.
    - Refactor CellStorage to load storage plugins.
    - Combine these plugins with the necessary dialogs/commands acting on the
      cell selection (they could all be placed in one shared object/library, if
      each plugin (storage/dialog/command) gets a corresponding .desktop file).
    - Some extra logic needs to be hard-coded into 'core', e.g. the check
      whether the user input fulfills the restrictions set by Validity. Those
      could hopefully be coded with the help of Qt's model system (item data
      roles). If not, extra interfaces have to be defined, at least for
      non-standard, non-Qt types.


Things to do before the release of Calligra 2.0
==============================================

Item                                                               Prio Status
------------------------------------------------------------------------------

Regressions
-----------

General bugs
------------
* Autofill							      3 ----
  Fix the 'May'-may-be-a-short-or-long-month issue.

Filter bugs
-----------

Things not in bugzilla
----------------------

* Printing
  + Repeated rows and columns don't work if they don't start from     2 ----
    row/column 1.   Also it is not possible to enter just one
    row/column into the dialog, it always has to be a range (2:3).
  + If the used increases(/decreases) and the print settings are      2 ----
    configured to have page limits, trigger an update. The
    calculation of the zoom factor for page limits is an expensive
    operation. Better move it into an own thread first.
  + Expand selection to page                                          3 ----
  + Fit selection to page                                             3 done
    Use page limits of one page in each direction and print just the
    selection.
  + Multiline headers/footers                                         3 ----

* OpenDocument file format
  - see TODO.opendocument					      1 ----

* OpenFormula compliance (Medium group)
  - implement all functions of the Small and Medium group	      1 ----
    see calligra/sheets/functions/TODO
  - implement the calculation settings				      1 ----
    see section 8.5.2 in [1] and section 3.3 in [2]

* Flake integration.
  + Cell anchoring						      1 ----
    - Saving								----
      Query the shape container of the sheet before iterating over
      the cells. Store the shapes anchored in cells in a QHash. Put
      that into a saving context and pass it to the cell saving
      methods. Write out the shape at the appropriate place.
    - Interaction							----
      Shapes anchored cells should be moved, if the cell itself
      got moved; either by column/row/cell range insertions/deletions
      or by column/row dimension changes.

* Internals (See also DESIGN.html)
  + Cell Storage						      1 ----
    - (Re-)Adjust the saving algos to use the new (old) iteration	----
      functionality.
    - Rewrite the MergeManipulator to work directly on the CellStorage.	----
    - PointStorage: Implement setLoadingEnabled(bool) that switches	----
      the insertion method to a mode in which the value, column and
      row are just appended to the vectors.
    - Point-/RectStorage: All yet stored data is implicitly shared.	----
      Make use of this fact: Implement book-keeping with a hash and
      reuse the already stored values. This is already done in
      StyleStorage.

  + Style Storage						      1 ----
    This would dramatically reduce memory consumption and allows
    styles for empty cells.
    - Improve the saving.						----
      Only StyleStorage::Private::usedArea should track the occupied
      cells only - not those of columns or rows. Adjust the saving algo
      appropriately.
    - Add configure option to choose whether the style of the current	----
      or of the previous (default) column/row is used on insertion.
    - Launch the garbage collection in a separate thread.		----

  + Rich text in cells.						      1 ----
    - Use KoText.    							----
      Add a RichTextStorage containing one(!) QTextDocument consisting
      of a sole table. This obsoletes LinkStorage. Plain text can still
      be stored in ValueStorage, but does not have to: unsure what's
      best in this case.
    - Background spell check (necessary to have rich text)		----

  + Evaluation of how best to increase floating point precision.      3 ----
	Suggestion:  GnuMP.    (Tomas)
	This will work by converting all functions to compute using
	ValueCalc, and nothing else, then modifying Value* to
	support GnuMP.  The conversion step shall be done as a part
	of converting to the new parser.

* GUI
  + Indent and multiline doesn't work together			      2 ----
  + RegionSelector						      2 ----
    - add syntax highlighting
    - initialize choice on focus in events, if necessary
    - fix the line edit height
    - implement single cell restriction (maybe in Selection)
    - jump back to parent dialog on closing the mini dialog
  + Scrollbar that supports jumping one row/column forward or back    2 ----
  + New dialog for conditional cell styles                            3 ----
    The dialog should allow to define a variable amount of
    conditional styles - not just three.

* Formula/Value engine
  + DependencyManager / RecalcManager				      3 ----
    - Port to a threaded approach.                               	----

  + Matrix operations						      2 ----
    - Determinant							done
    - Dimension								----
    - Inverse								done
    - Minima/Maxima elements						----
    - Multiply								done
    - Norm								----
    - Rank								----
    - Transpose								done

  + References to cells in other files				      2 ----

  + Tools->Auditing:						      2 ----
    - Trace Precedents						        ----
    - Trace Dependants						        ----
    - Trace Error						        ----
    - Remove all arrows						        ----


* General features
  + Split view							      1 ----
  + "Freeze/Unfreeze Panes"					      2 ----
  + Function optimizer ('Solver')				      2 ----
    - evaluate, if we're able to use linear methods (derivatives!)	----
    - evaluate, how to include side conditions				----
    - check whether the formula cell carries a valid formulas		----
      and further checks of used cell contents


* Major features (big effort)
  + Pivot tables						      3 ----
  + Scenarios							      3 ----
    See [1], section 8.3.3 for details.


Other things: (please add the things you are working on!)


Not yet sorted (will be entered into categories above)

- Multiple Operations (in Excel: "Data"->"Table")
- Insert widgets like buttons, drop down lists,... + having the possibility to
  define action if pressed, or selection changes,...
- Button + Drop-Down-List support (within cells)
- interface for mail merge
- for formulas: fit precision so the result fits in the cell or resize the cell

- need to improve copypaste between sheets and oocalc (or other apps) - drag and drop from sheets to oocalc sort of works (as CSV), the opposite is funky, only copies one value and retains old selection's shape

- changing text angle should resize the cell height automatically
- support for format strings (dd/mm/yyyy)
- more font attributes (outline, shadow,...) + attributes for parts of the text
- double borders
- better AutoFormat dialog + better templates

- more "Related Functions" in function help/desc text
- improve function compatibility with MS Excel
- more information functions (Excel compatible)

- enhance the Gnumeric import filter
- sync the Gnumeric export filter
- StarCalc/OpenCalc import filter
- StarCalc/OpenCalc filter for embedding/embedded objects
- StarCalc/OpenCalc export filter
- dBASE export filter



References:
===========
[1]	Open Document Format for Office Applications (OpenDocument) v1.0,
	http://docs.oasis-open.org/office/v1.0
[2]	Open Document Format for Office Applications (OpenDocument),
	Recalculated Formula (OpenFormula)
	http://www.oasis-open.org/committees/office
