Difference between revisions of "KMyMoney/Features/Plan46"

Jump to: navigation, search
(Features)
(Updated feature plan to match reality)
 
Line 10: Line 10:
 
* Reports internal structure revamp
 
* Reports internal structure revamp
  
==Detail==
+
==Detail (in progress)==
===Budget revamp (Alvaro)===
+
All done :)
* Make budgets rolling (no longer year-specific) and have 1 on the list be the default budget
+
 
* Add assets and liabilities to budget
+
==Detail (done)==
** The user should enter the net variation for each account
+
=== AlkValue (Thomas) ===
** The reports will have to be adjusted for this. Probably separate budgets at first
+
* Make sure we have libalkimia ready and integrated
** Variation on assets and liabilities count toward net variation
+
* Update testcases
* Advice whether budget is feasible: incomes should at least match expenses and net worth variation
 
* Perhaps try to make the budget list dockable, as it won't be used much and it would be best to hide it or shrink it. Leave more room for the actual budget data
 
  
=== Report structure(Alvaro)===
+
=== Balance cache update (Fernando) ===
* Port to a nested structure, to match the account hierarchy
+
* Move balance cache from storage layer to MyMoneyFile layer
* Use a QAbstractModel?
+
* Update/add related test cases
* Allow reports to have an arbitrary level of detail, with subtotals for each level
 
  
 +
==Detail (postponed)==
 
=== Transaction Form Updates ===
 
=== Transaction Form Updates ===
 
* The current design should be freed from some legacy design decisions that are no longer relevant
 
* The current design should be freed from some legacy design decisions that are no longer relevant
Line 34: Line 32:
 
* Before starting on the above, we need requirements capture and a solid design, so that all developers understand the vision for this key piece of the code.
 
* Before starting on the above, we need requirements capture and a solid design, so that all developers understand the vision for this key piece of the code.
  
=== AlkValue (Thomas) ===
+
=== Report structure(Alvaro)===
* Make sure we have libalkimia ready and integrated
+
* Port to a nested structure, to match the account hierarchy
* Update testcases
+
* Use a QAbstractModel?
 +
* Allow reports to have an arbitrary level of detail, with subtotals for each level
  
=== Balance cache update (Fernando) ===
+
===Budget revamp (Alvaro)===
* Move balance cache from storage layer to MyMoneyFile layer
+
* Make budgets rolling (no longer year-specific) and have 1 on the list be the default budget
* Update/add related test cases
+
* Add assets and liabilities to budget
 +
** The user should enter the net variation for each account
 +
** The reports will have to be adjusted for this. Probably separate budgets at first
 +
** Variation on assets and liabilities count toward net variation
 +
* Advice whether budget is feasible: incomes should at least match expenses and net worth variation
 +
* Perhaps try to make the budget list dockable, as it won't be used much and it would be best to hide it or shrink it. Leave more room for the actual budget data

Latest revision as of 08:04, 19 June 2011

Feature Plan for version 4.6 of KMyMoney

Include below the items you think should be included in the next version For each item, add a subheader with a quick explanation

Features

  • AlkValue
  • Budget revamp
  • Performance of the ledger
  • Reports internal structure revamp

Detail (in progress)

All done :)

Detail (done)

AlkValue (Thomas)

  • Make sure we have libalkimia ready and integrated
  • Update testcases

Balance cache update (Fernando)

  • Move balance cache from storage layer to MyMoneyFile layer
  • Update/add related test cases

Detail (postponed)

Transaction Form Updates

  • The current design should be freed from some legacy design decisions that are no longer relevant
  • View/Edit widgets are clumsy
  • Transaction type tabs could be made into a combobox
  • Investment transactions complicate the form
  • Transition auto-fill to an MVC architecture
  • Implement tags and transaction templates
  • Before starting on the above, we need requirements capture and a solid design, so that all developers understand the vision for this key piece of the code.

Report structure(Alvaro)

  • Port to a nested structure, to match the account hierarchy
  • Use a QAbstractModel?
  • Allow reports to have an arbitrary level of detail, with subtotals for each level

Budget revamp (Alvaro)

  • Make budgets rolling (no longer year-specific) and have 1 on the list be the default budget
  • Add assets and liabilities to budget
    • The user should enter the net variation for each account
    • The reports will have to be adjusted for this. Probably separate budgets at first
    • Variation on assets and liabilities count toward net variation
  • Advice whether budget is feasible: incomes should at least match expenses and net worth variation
  • Perhaps try to make the budget list dockable, as it won't be used much and it would be best to hide it or shrink it. Leave more room for the actual budget data

This page was last edited on 19 June 2011, at 08:04. Content is available under Creative Commons License SA 4.0 unless otherwise noted.