On Tue, 5 May 2009 12:00:46 +1000, Lex wrote:
Another reason is sometimes it's messy to modify/customize the generated widgets or use own classes (not that important on Geany as we don't have much own widget classes but still).
And I'm finding that it is difficult to exploit the repetitiveness within the dialog and the commonality between projects and build dialogs. Although cut & paste can generate the code reasonably efficiently you then need to hand edit it and when fixing bugs you have to repeat it lots of time ... oops I missed one ;-) This in fact is pushing me towards do it yourself. If I go that way where do you suggest that functions common to build.c and project.c should go,
Either in build.c or in ui_utils.c, I would tend to build.c.
Some time in the future when we can use GTK 2.12 we can/will use GtkBuilder whose XML files can be created with Glade 3 and are read directly by GTK, so we don't need libglade or generated code (and there is a conversion tool for glade XML files to GtkBuilder XML files). But this doesn't matter much for now because we require GTK 2.8 (as said before).
Yeah, as I understand it this is the way to go. Glade 3.6 supports builder xml directly, no converter needed.
Yeah, I meant just to convert our current Glade XML file into the GtkBuilder format, this is only an one-tine action.
Regards, Enrico