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.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2006-02-04
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.
I personally really like Qt Jambi, the Java language bindings for Qt. And the best thing is, you can even use them with Scala (http://www.scala-lang.org/). Scala is a modern general purpose programming that integrates features of functional and object oriented languages and it runs on the Java VM.
Member since:2006-02-20
>GTK# is extremely dangerous. It's inviting lawsuit,
>or intimidation and/or extortion from Microsoft.
Why? Come on, that's FUD. GTK# is NOT copying a Microsoft product. If GTK+ itself is NOT threatened, then why is a thin wrapper using a de jure standardised language threatened?
If there are any problems, it will be in the WindowsForms or ASP.Net side or other stuff that isn't in the ECMA standard.
Give Microsoft *some* credit for open standardisation where they've done it.
> The recent Fortune magazine article, which contains
> MS's latest patent threats, makes this crystal clear.
Go-one, be specific. MS can threaten wherever they have patents, but GTK# is no more and no less likely to be infringing than any random bit of code, so far as I can see.
James
Member since:2005-07-15
>Thus, with SWT, you can make GTK native looking Java desktop apps.
swt doesn't look native in a Gtk environment. Just look at eclipse and you will find many things which looks different than in a native Gtk+ environment.
Personally i would use SWT only if i know that a write a program mainly for windows and/or MacOS users. But for all programs which i write for myself and/orf for the X11 platform i would always use java-gnome.
>As for GTK# - 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.
Please don't start the 1001th Mono flamewar. Gtk# is just a wrapper around Gtk+ if this violates any (MS) patents it high likely that Gtk+ itself violates the patents, because all the logic is in Gtk+ and not in Gtk#. Also MS is one of the smallest problem if it comes to patents. Today almost every program violates patents and the most danger comes from companies which large patent portfolio and without own "products". MS is one of the most harmless in this regard.
Member since:2005-07-06
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.
Incorrect and misleading.
You *might* be referring to System.Windows.Forms in Mono which is something else.
gtk# is inviting lawsuits as much as gtk+ or qt is.
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.