> 1) Use libglade to parse the UI at runtime. Simple. Scalable. Will slow > widget creation enough that gtkg will start up significantly slower on > some machines. Requires us to depend on libglade, which is not that > painful, since we already depend on libxml2, which is also part of gnome. > > 2) Make do with what we have. Huge UI creation functions mean either a > highly cluttered or a highly recursive interface, or both. > gtkg's UI is highly recursive. Basically, it uses a lot of tabs. > We can take the code to create each tab's content off create_main_window() > and create_dlg_filters() and put it each in its own window in another > glade project. Then we use some code at runtime to reparent > the widgets right where they should be.
> What do you think ? We discussed both approaches on #gtk-gnutella already. I personally think that reparenting is probably the better way to go. But it must be made compatible with the lookup_widget() call, because then this approach only requires some small localized changes to the startup code and the largest part of the code can remain unchanged. -- Richard Eckart <[EMAIL PROTECTED]> ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Gtk-gnutella-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
