From eb97fef4440b8cb6aa906a7c46ee36e0d19af0b9 Mon Sep 17 00:00:00 2001 From: Joshua Sled Date: Fri, 6 Jan 2006 22:55:02 +0000 Subject: [PATCH] buffer-flush notes. git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@12279 57a11ea4-9604-0410-9ed3-97b8803252fd --- GNOME2_STATUS | 39 ++++++++++++++++++++++++++++++++++++--- 1 file changed, 36 insertions(+), 3 deletions(-) diff --git a/GNOME2_STATUS b/GNOME2_STATUS index 7e6eeac65a..3a9a8e4e2e 100644 --- a/GNOME2_STATUS +++ b/GNOME2_STATUS @@ -118,7 +118,7 @@ Resources - New Account Hierarchy - somewhat works - - Simply invoking, even if cancelled, trashes current book state? + - Placeholder status should be set on relevant (non-leaf) accounts? - Sometimes crashes when loading account data. @@ -150,6 +150,37 @@ Resources - conflict-resolution process/display issues. + - weird... + + - Merge Druid -forward-> Account Druid -cancel-| => book commodity (?) changes + + - conflict resolution + + hampton: hmm. trying to figure out the ui here; I think it's: + 1/ make the account-name directly-editable in the account-tree view. + 2/ Change the "add opening balance" page to "edit accounts". + 3/ Add a "existing?" column next to the account name. + 4/ the accounts and editing becomes stateful in a semi-complex way: + That sounds like a plan. #2 will also make account names editable anywhere where an account tree is used which is good (accounts page, budgets page) and bad (transfer dialog, etc.) + there's a 2-bit state space: placeholder-account? and shares-name-woth-existing? + re: editable names: ah, noted; configurably editable, then. + s/woth/with/ + placeholder=true, shares=true: use existing, no problem. + placeholder=true, shares=false: create new, no problem + placeholder=false, shares=true: existing account with same name exists, problem (blocks druid close) + placeholder=false, shares=false: create new, no problem. + I would state it differently. + Maybe ... another Messages column to indicate the problem case... + shares=false, placeholder=don't care: create new, no problem. + shares=true, placeholder=same as existing: use existing, no problem + shares=true, placeholder=diff from existing: problem + Ah. Yup. + Well, kinda. + Ignoring the placeholders for a moment, there are really two types of example-accounts: those that expect the name to be edited, and those that don't. + Those roughly correlate with the placeholder setting. + But if you're re-running the account-hierarchy druid to add another credit card, you should be encouraged to enter a different name for the leaf account. + Its more a question of where the dialog was called from. If from the new user code, you really don't need to edit names. If called from the merge druid, the user should be encouraged to edit leaf names. + - Backend - price_lookup awaits a solution - as a query instead of a backend operation. @@ -161,8 +192,12 @@ Resources - e.g. The To-Create-Transaction read-only review ledger doesn't need any menus or editing functionality. + - [minor] Since Last Run uses deprecated GTKCTrees. + - SX Editor + - bug/crash: http://lists.gnucash.org/pipermail/gnucash-devel/2006-January/015300.html + - Template-register View > {Basic, Auto-Split} options have no effect - Note: they *shouldn't* have any effect, as they don't apply to @@ -202,5 +237,3 @@ Resources - Entering a value (e.g. '20.00') without entering an account or a memo for the first split causes everything else entered so far to be reset when tabbing to the second split. - -