IntenseFinance/gnucash
3
0
Fork 0
mirror of https://github.com/Gnucash/gnucash.git synced 2025-02-16 18:25:11 -06:00
Code Issues Packages Projects Releases Wiki Activity

buffer-flush notes.

Browse Source 
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@12279 57a11ea4-9604-0410-9ed3-97b8803252fd
This commit is contained in:
Joshua Sled 2006-01-06 22:55:02 +00:00
parent d20e593428
commit eb97fef444
1 changed files with 36 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

39
GNOME2_STATUS
View File

@ -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
<jsled> hampton: hmm. trying to figure out the ui here; I think it's:
<jsled> 1/ make the account-name directly-editable in the account-tree view.
<jsled> 2/ Change the "add opening balance" page to "edit accounts".
<jsled> 3/ Add a "existing?" column next to the account name.
<jsled> 4/ the accounts and editing becomes stateful in a semi-complex way:
<hampton> 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.)
<jsled> there's a 2-bit state space: placeholder-account? and shares-name-woth-existing?
<jsled> re: editable names: ah, noted; configurably editable, then.
<jsled> s/woth/with/
<jsled> placeholder=true, shares=true: use existing, no problem.
<jsled> placeholder=true, shares=false: create new, no problem
<jsled> placeholder=false, shares=true: existing account with same name exists, problem (blocks druid close)
<jsled> placeholder=false, shares=false: create new, no problem.
<hampton> I would state it differently.
<jsled> Maybe ... another Messages column to indicate the problem case...
<hampton> shares=false, placeholder=don't care: create new, no problem.
<hampton> shares=true, placeholder=same as existing: use existing, no problem
<hampton> shares=true, placeholder=diff from existing: problem
<jsled> Ah. Yup.
<jsled> Well, kinda.
<jsled> 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.
<jsled> Those roughly correlate with the placeholder setting.
<jsled> 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.
<hampton> 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.