To read all comments associated with this story, please click here.
Why create another GTK GUI Designer? Well first I think a loot of people just can't wait for Glade3 but there are other reasons too. Glade3 doesn't create code anymore; it is now the responsibility of the GTK wrapper to provide an XML -> code converter if they want one. Some projects might just create their own GUI Designer if they have to do that.
Example, Stetic:
MonoDevelop needs a GUI Designer, they need a code generator for C# (and maybe others). Option a) wrap Glade3 and create an XML -> c# program, b) write from scratch a program that creates c# code.
Might as well go with b) and get to do some of the fun stuff to and not just the tedious stuff.
>MonoDevelop needs a GUI Designer, they need a code generator for C#
why does they need a code generator? I think code generation is a really bad idea. Also Qt4 has introduce the way to load the xml file into the application.
On c# just type:
Glade.XML gui = new Glade.XML("gladefile.glade", "window");
gui.Autoconnect(this);
and everything is fine.







Member since:
2005-07-15
why everyone writes his own GUI Designer? Glade, Static, Gibeon,... all programs for the same task -> creating Gtk-GUIs. Als long as the create all the same xml file there is at least no compatibility problem but i don't understand why everyone wants to write his own designer?
Especially on Gtkmm: I think the most needed feature is not just another GUI-Designer. I think it would be much more important that libglademm would have an autoconnect function. Gtkmm is the only (big) toolkit were i have to connect all my signals by hand. A GUI Designer could be so much more usefull if i could connect the signals directly with the designer like i can do it with Gtk+ or Gtk#.