more library structure

[Chris Shoemaker]

On Wed, Jan 25, 2006 at 09:08:33PM -0500, Derek Atkins wrote:
> Quoting Chris Shoemaker <c.shoemaker at cox.net>:
> 
> >>I see no instance of "gnc_show_splash_screen" in gnucash-bin.c in any
> >>form..  So when you moved stuff around you removed my comment completely.
> >
> >It's the first thing that happens inside gnc_main_gui_init().  When
> >that was called before loading modules, the module loading messages
> >showed on the splash.  But, the report menu was never populated.
> 
> Well perhaps gnc_main_gui_init() needs to get split up..  Perhaps
> we have a gnc_main_gui_preinit() that could just do the gnome initialization
> and show the splash screen..  Then we load the modules..  And then
> we call gnc_main_gui_init() which does the rest of the initialization
> of the main window?

I alread split it up, that's the difference between
gnc_main_gui_init() and gnc_gui_init() -- not very intuitive names.
Expect that gmgi calls ggi, because I didn't want to pass the windows
around.  OTOH, if the totd could move from gnome to gnome-utils, then
gnc_main_gui_init wouldn't need the window.  That's worth testing...

> >The problem I'm running into isn't so much with the register as with
> >the report-system.  Application startup and tear-down touches
> >everything - including the report-system.  I moved half of it from
> >gnome into gnome-utils, but I think that was a mistake.  It should
> >stay in gnome.  But, that pulls the thread... what about the stuff in
> >gnome-utils that tried to manage lifecycle - specifically, gnc-file
> >and gnc-main-window?
> 
> See, this is where I think that the gnome-report module initialization
> (which should happen AFTER the application initializes but before the
> main-window initalizes) should do the menu insertions.
> 
> You need to split that.
<snip>

I'll try that.

-chris