> > Right, I've been calling these 'instantiated' reports. The infrastructure
> > for saving the parameters is there; we just need to add a way to save
> > information associated with a gnucash data file. We also need a way to
> > refer to accounts in a unique, non-volatile way (fully-qualified account
> > names are guaranteed unique and can change). These things will be done
> > soon, but will take a bit of time since they involve changing file
> > formats and stuff.
>
> I have been reading about requirements for saving information associated with
> data file, and the comments imply that the data will be stored inside the
> gnucash data file. Is this the idea, or will the data be stored in a separat
> file? If a separate file is used for configuration data, existing libraries
> could be used to manipulate the data, and the format for the transaction data
>
> does not have to change. If we want to combine everything into a single file
> we could use some sort of embedded file system as described in the recent
> discussion regarding bonobo reports.
>
> I'm interested in this because the storing everything in one file would make
> important file larger, and therefore more difficult to maintain backups.
It hasn't been firmly decided yet, but I believe the opinion
was tilting toward storing the data in separate files located
in the same directory as the main file.
dave
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
