[Glade-users] why using libglade is better...

[Tristan Van Berkom <tristan van berkom gmail com> (Tristan Van Berkom)]

On Mon, 18 Oct 2004 12:44:54 -0600, Neil Zanella <nzanella gmail com> wrote:
> > You don't actually need to put them into a separate file to be able to
> > recreate them. What I do is put them all in the same file, and only load
> > the widget (the main app window, a dialog window, etc.) that I need,
> > using the root argument to glade_xml_new().
> >
> > The documentation for glade_xml_new() says, "Note also that the XML
> > parse tree is cached to speed up creating another GladeXML object for
> > the same file", so it shouldn't actually have to reload the glade file
> > for every popup. It certainly seems to me that the startup (when it loads
> > the main app window from the glade file) is quite a bit slower than the
> > popup creation, although I haven't profiled it.
>
> Thanks,
>
> But this still doesn't answer my question, which is concerned with the
> implementation
> of libglade. Assuming there is only one .glade file, I want to know
> whether widget
> instantiation occurs on the fly as the .glade file is being parsed, or
> whether it
> occurs only after the whole XML file has been parsed.

Widgets are built during the parse (inside the function glade_xml_new), 
the innermost widgets of each node are built first (and nodes are built
sequentialy).

(Personaly I dont know about your other question... anybody ?)

Cheers,
                                -Tristan