"Gideon is a versatile GUI designer for GTK/C++. The goal of the project is to provide an easy-to-use RAD tool for C++ programmers who want to create multi-platform GTK-based GUI applications. Gideon is not overloaded but strives to provide all necessary features and remain 'simple and lightweight' to end user. Gideon is highly productive for experts and accessible for newcomers."
Post a Comment
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#.
Member since:2005-07-06
Member since:2005-06-29
Member since:---
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.
Member since:2005-07-15
>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:---
Member since:2005-06-29
Member since:---
That's true, but Gtk+ 2.10 will also have it. 
http://www.gtk.org/plan/2.10/
Member since:2005-06-29
Code generation is a great idea... Everyone's doing it . Seriously XAML? It doesn't dynamically load XAML files, they're built into the project and they supposedly end up as code in the end (so they're quick).
The only advantage to not generating code is binary distribution allowing user changing of the layout...
A glade_xml->gtk_c would be really nice. You stick it in your makefile, and boom you're done; and you can edit your project with the gui editor later without being super careful not to break something!
Member since:---
The real advantage of using a xml description of the gui is the strict separation between the layout and the logic of the app.
Loading different layouts at runtime is simply a plus.
Give me libglade over generated code with custom comments to mark the "don't touch" areas any time...
Member since:---
Member since:
---
Member since:
---
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?
But better to have more than one in the beginning. So that we will have different way of genarating GUI with different peoples innovation. At last, we will have one better out of all. I think that may take years. There is no good GUI genarator for GTK/Gnome as QT. But Glade 3.X is look like promising. Any way let us see.
Member since:
2005-07-06
why does they need a code generator?
Well I'd guess it has to do with efficiency, not having to re-parse the same XML and create the same GUI at runtime each time the application is run.
Also Qt4 has introduce the way to load the xml file into the application.
No, that's not correct. This was already possible in Qt3. It's even possible it was included in Qt2, I don't remember. Search for dynamic dialogs in the documentation.
The code look something like this:
QDialog *dialog = (QDialog *) QWidgetFactory::create("dialog.ui");
Member since:
2005-07-07