Le mercredi 25 à 19:25, Geert Janssens a écrit :
> On Wednesday 25 September 2013 11:11:21 David Carlson wrote:
>> As another user I would suggest per data file. One user may want
>> different settings in another file.
>
> I would rather see it per data file as well.
Okay, I guess I can try and see how to store that info in the data file
then. Can't promise a timeframe, as even though that's conceptually
pretty simple, this is my first dabbling in Gnucash code...
> And if you are going to do a GUI to edit this, how about making it a
> currency editor, something like the commodity editor now, but then for
> currencies ?
The way I see it (and what would be sufficient for my own use), the
interface to set the user symbol would look like :
foreach (currency in book->used_currencies)
r = create_row()
r.col1 = label(currency.code)
r.col2 = label(currency.description)
r.col3 = editable_text(currency.user_symbol
if currency.user_symbol else currency.code)
r.col3.on_update = lambda: new_user_symbol ->
currency.set_user_symbol(new_user_symbol)
Well, the equivalent GTK code, but you get the idea.
> The iso-4217-currencies can serve as preset currencies,
> which the user can edit, or even add custom currencies (think Bitcoin
> and friends). Perhaps that's too wide a scope though...
Isn't user-defined currencies something that's been asked a couple of
times ? I mean, googling for "gnucash bitcoin site:lists.gnucash.org"
reveals quite a few past discussions (without, evidently, happy
conclusions or we would have BTC by now).
And the complexity of "I'll store in (GConf|the data file) one
user-defined field per currency" seems much lower than "I'll store
enough data to recreate the entire currency at data-file load time" ; I
don't think I can acheive the second.
--
Fred
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
