logging overhaul (please read)

[Derek Atkins]

Quoting Josh Sled <jsled at asynchronous.org>:

[snip]
> - enable the Extensions menu
> - allow (gnc:debug ...) logging.
>
> It seems right to have two options: one for enabling the Extensions
> menu, and one for getting log detail.  I like --debug for the latter,
> and some new flag for the former.  As there's a small set of people devs
> who need to be "retrained" for an extension menu option, that seems
> better than the other way around, and "--debug" is a promising candidate
> to the eyes of Joe Linux when scanning --help...
>
> So, maybe:
> --extend?  meh.
> --enable-extensions?  too long.
> --extra?  Hmm...
>
> I'll probably go with --extra in the absence of a better suggestion.

Or --debug-menu ?   I suppose --extra or --extensions or --devel-menu
or..  whatever.. would work.

> (I note, as well, that the scheme logging should probably call wrapped
> g_«log»... calls, rather than just (write ) the lines out.  Oooh,
> that'll be a good way to figure out how to swig-ify some api... :)

Yes, I agree..  gnc:debug should get mapped to the g_log APIs.

-derek

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available