Looks good. If we split the subentry pane into two panes: one that selects
the type and common information a second one that lets one enter information
specific to the type, I wouldn't need to use a Druid interface.
What's the best way to proceed? I can start on an interface, but I cannot
finish until we have resolved the issues on how to save secondary information.
Bryan
On Thu, 06 Apr 2000, Dave Peticolas wrote:
> I've been looking at the budget stuff and have come up with
> a sketch of what the gui interface might look like:
>
>
> ------------------------------------------
> | Entry | |
> | Sub-entry | Entry information |
> | Sub-entry | |
> | Entry |--------------------------
> | Sub-entry | |
> | Entry | |
> | ... | Sub-entry information |
> | | |
> | | |
> | | |
> ------------------------------------------
>
> The pane on the left contains the buget tree, with entries
> and sub-entries. The pane on the right displays editable
> information about the selected entry in the top portion,
> and editable info about the sub-entry in the bottom portion.
>
> In addition, there would be controls to add/delete entries
> and sub-entries. Maybe move them around too.
>
> thoughts?
>
> dave
>
> --
> Gnucash Developer's List
> To unsubscribe send empty email to: [EMAIL PROTECTED]
--
-------------
Bryan Larsen, Senior Software Engineer & fall guy
Analog Design Automation: Analog Circuit Synthesis? Problem Solved.
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
