History

[Geert Janssens]

On Wednesday 05 February 2014 15:46:15 David Ryder wrote:
> 
> I expressed myself badly.
> Config Editor vs Dconf Editor - no difference.
> I was alluding to editing schemas keys - fraught with dangers if one
> has the ability to edit schemas setting directly.
> 
Indeed.

> When I read gnucash.Gnucash - I was thinking of situations where each
> book could have independent configurations. I admit I don't know how
> individually configurable each book is now, but (as a poor example) if
> one has books for Trusts the colour scheme of the page could be
> different from Companies, another for previous accounting periods
> .... giving an instant visual indicator ...
> This is, I admit, a poor example but having different settings like
> that would help when working with different entities.
> BUT - please do not take this as a feature request. Reading
> gnucash.Gnucash made me think
> gnucash.Gnucash.<company1>
> gnucash.Gnucash.<company2> etc etc.

Well, since the discussion started with your request to show more files 
in the history section I limited my discourse the the relevant 
preferences part - gsettings.

But gnucash actually has multiple classes of settings:

1. user level settings
Changes to these settings will affect all books for one user. These are 
mostly general preferences like how many files to show in history, the 
default currency for reports, start/end of accounting period,... You 
could argue that some of these settings should configurable per book and 
I'd agree. But it's just how things are currently set up. Most of the 
settings you find in Edit->Preferences are in this category.

2. Per book level settings
These are settings that only affect the book currently open. This 
relates mostly to the settings you find in Files->Properties

3. Metadata
This tracks which tabs/windows were open the last time you closed a 
given book, the positions/sizes of these windows and dialogs, altered 
column widths, sort orders, and so on. Effectively the state your book 
was displayed in the last time you closed it.

4. Low level settings
These are only meant to make gnucash actually work on your system so you 
could call these system level settings as well. With these you could 
override some parts of the system environment, like default locale to 
use, or paths to critical system components. Most users don't need (or 
even shouldn't) touch these.

As you can see gsettings is only a small part of the complete settings 
system provided to the user. And we do have per book settings though you 
may not configure all that you like with them.
> 
> Geert - users always want 'more' - even if we are very happy with what
> we have. Sometimes we just think 'if only' :-)
> 
:-)

Geert