Gtk-- strong points

• Typesafe API - no FCS (Frenetic Casting Syndrome), less Gtk-Warnings at runtime
• Very flexible and powerful signalling system (K. Nelson's libsig++)
  • callbacks can be anything - methods, functions, signals
  • user can create their own signals very easily
• Very complete - all GTK+ widgets and most of the Gnome ones (Gnome--) are wrapped
• Widgets are full-fledged C++ classes which can be derived to create new ones
• No char*, foo[], FooString, FooContainer : std::strings, STL containers
• Low memory overhead (about 75 bytes per widget)
• Widget memory management facility (the manage() function)
• Simplified API thanks to overloading, default args, namespaces

  For instance :

  • int gnome_execute_async (const char *dir, int argc, char *const argv[]);
  • int gnome_execute_async_fds (..., gboolean close_fds);
  • int gnome_execute_async_with_env (...);
  • int gnome_execute_async_with_env_fds (...);

  Wrapped into

  • int Gnome::Execute::async(const string &dir, const SArray &argv, bool close_fds = true);
  • int Gnome::Execute::async(const string &dir, const SArray &argv, const SArray &env, bool close_fds = true);

  Gtk::SArray can accept any STL container<string> (e.g. vector<string>, list<string>...)