I, for one, been oscillating between using GTKmm and QT4 for my next pet project.
After playing with both QT4 and GTKmm for more than a month, I've decided to use QT4. Maybe try again using GTK/GTKmm in a year. Right now, I find the documentation lacking in key areas (for example, drag&drop in a tree) and I'm tired of waiting for an answer on a mailing list, answer that might never come, and not in the mood of hacking GTK>Kmm sources. For me, the documentation that comes with GTK/GTKmm is the biggest stopper (to me, it is extremely disturbing that the latest GTK book, www.gtkbook.com, says nothing about Drag&Drop or threading - maybe they are there, but I couldn't found them - or that the container chapter doesn't talk about the Frame widget - not important, but why there is no mention of it?). Cheers, Johnny On Wednesday 07 May 2008 12:59:31 am Hubert Figuiere wrote: > On Tue, 2008-05-06 at 22:54 +0200, Martin (OPENGeoMap) wrote: > > I need GTS library (Gobject) and i would know if it´s difficult create > > C++ bindings or use C API can be anough here?? > > http://gts.sourceforge.net/reference/book1.html > > You can always use C API when there is no C++ version. > > > It´s seems like before GTKMM developer Guillaume Laurent nowadays hates > > GTK or he have good reasons to not defend GTKMM anymore???. > > Long time ago, things have evolved, He is entitled to his own opinion. > > > Guillaume Laurent talks about the problems in use a stack object: > > 1. From the stack : Gtk::Button foo("press me"); > > 2. From the heap : Gtk::Button *foo = new Gtk::Button("press me"); > > , but i see many advantages in use stack widgets because we can build > > new widgets in a easy way like GTK# or ruby/gnome. > > Gtkmm allow both. > Gtk::manage() is here to ensure proper ownership of the object (similar > to Gtk's) when pointer are used. This is all documented. > > > Hub _______________________________________________ gtkmm-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gtkmm-list
