Hi Rodrigo; On Wed, 2006-10-25 at 18:33 +0200, Rodrigo Moya wrote: > > That could be a route to explore - I think its really important to > > keep GtkWindow really simple in that respect though - it could be > > a dialog - it could be a popup window, a popup menu - or even a tooltip, > > So I would suggest that if we bind such logic into GtkWindow - making > > it some kind of hybrid composite widget - we should definitly do > > that in a GtkAppWindow subclass (that could be then used by the > > GtkApplication in question). > > > and why not have: > > gtk_window_new -> as it is now > gtk_window_new_dialog (buttons,...) > gtk_window_new_main_app(menus, toolbar, etc) > > ?
Because we have a clear separation: a GtkDialog is a GtkWindow but not the other way around. GtkWindow is a primitive object which should be specialised in subclasses. I'm not sure that having a GtkApplicationWindow is the road to go - it would be a fairly specialised subclass of GtkWindow, and should bind together a bunch of stuff (toolbars, menus, status bar, session state) that might be too generic to effectively be usable by projects. Anyway, a GtkApplicationWindow would be better than shoving stuff directly inside the GtkWindow class. Ciao, Emmanuele. -- Emmanuele Bassi, E: [EMAIL PROTECTED] W: http://www.emmanuelebassi.net B: http://log.emmanuelebassi.net _______________________________________________ gtk-devel-list mailing list gtk-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-devel-list