Dave Peticolas <[EMAIL PROTECTED]> writes:
> This is something that deserves some discussion, because the
> solution is not entirely clear. Somehow, we should associate
> the account-expanded state with each gnucash file, but we
> shouldn't save the information in the actual file itself,
> since GUI info isn't supposed to be there, and it would
> make it difficult for multiple users to share the file.
>
> We could have a separate file that is saved in the same
> directory for each user, but that seems a bit messy.
As a more radical alternative, we could switch to using a directory
per account group rather than a file, and it could contain whatever
files we need in order to carry all the right state around when the
account group is copied, moved, etc:
my-finances.gnc/data
my-finances.gnc/state.user1
my-finances.gnc/state.user2
my-finances.gnc/lock
my-finances.gnc/pending-transactions
etc. This would allow us a substantial amount of flexibility now and
in the future, but it might be kind of strange to most people. ISTR
that NeXT did something like this instead of Apple's resource/data
fork hack.
> We could save the state in the user's config.auto under a specific
> file name.
True, but then you have the problem that stale info will be carried
around forever (say when account-group files are deleted from the
filesystem), and with this approach copying your files won't preserve
the settings. I.e. if you do a "cp mydata.gnc my-new-data.gnc" and
then work on my-new-data.gnc, you won't see any of your old settings.
We could get this right if we added a per account group, guaranteed
unique ID (like the one used for news/mail articles), for some
definition of "right".
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
