Linked by Eugenia Loli-Queru on Wed 23rd May 2007 09:13 UTC
Often I complain that GTK+ documentation (non-reference) is non-existent. The few GTK+ books that were ever written are now old and most of their included source code does not even compile anymore. All hail "Foundations of GTK+ Development" by Andrew Krause.
Permalink for comment 242713
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-07-12
Good point.
That makes GTKmm more compelling.
But if one is going to with a higher level VM language, I would go with SWT / Eclipse RCP.
SWT is an API that in turn calls native APIs of three (currently) different native APIs: Win32, MacOSX, and GTK.
Thus, with SWT, you can make GTK native looking Java desktop apps.
Then with Eclipse RCP, you have all the advantages of JFace, the Eclipse workbench and plugin architure (abstractions on top of SWT), and you can use the Visual Editor.
Of course, then you can package your app for Windows and Mac, very easily.
In short, you get great native looking apps, with good performance (it's using native widgets).
As for GTK# - while it's technologically nice, and Miguel and the Mono crew have done an outstanding job - GTK# is extremely dangerous. It's inviting lawsuit, or intimidation and/or extortion from Microsoft. The recent Fortune magazine article, which contains MS's latest patent threats, makes this crystal clear.