History

[David Ryder]

On 05/02/14 15:15, Geert Janssens wrote:
> On Wednesday 05 February 2014 15:01:28 David Ryder wrote:
>> On 05/02/14 14:53, John Ralls wrote:
>>> On Feb 5, 2014, at 7:41 AM, Geert Janssens <janssens-
> geert at telenet.be> wrote:
>>>> The path to look for now is org>gnucash, but the rest should be
>>>> similar.>
>>> Perhaps it should be org.gnucash.GnuCash just in case we need
>>> preferences for some utility program in the future.
>>>
>>> Regards,
>>> John Ralls
>> Whether Configuration Editor or Dcon Editor, I agree
>> org.gnucash.GnuCash for the same reason.
>> A lot of preferences not usually in 'Preferences" menu could easily be
>> edited that way ... much more configurable. And for individual books.
>> So long as it doesn't become schema.
>>
> I'm not sure I understand your reasoning properly here.
>
> But first off, gsettings won't allow to have preferences without schema.
> So your last sentence makes little sense to me.
>
> And what difference is there to the configurability between storing all
> preferences under org.gnucash or org.gnucash.GnuCash ? It's the same set
> of available preferences only in a different path.
>
> Geert
>
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.

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.

Geert - users always want 'more' - even if we are very happy with what 
we have. Sometimes we just think 'if only' :-)

David