Linked by Thom Holwerda on Mon 9th May 2011 21:14 UTC, submitted by Elv13
Thread beginning with comment 472412
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Comment by ephracis
by Elv13 on Mon 9th May 2011 23:14
in reply to "RE[2]: Comment by ephracis"
RE[4]: Comment by ephracis
by zubzub on Wed 11th May 2011 11:27
in reply to "RE[3]: Comment by ephracis"
I can assure you it's not dead. Trolltech abandoned it but theres a small group of people working very hard on it. Mavenizing the whole project, ironing out bugs, ... It's all being worked on.
http://qt-jambi.org/
RE[3]: Comment by ephracis
by lemur2 on Mon 9th May 2011 23:48
in reply to "RE[2]: Comment by ephracis"
But, the whole application is written in C#. What good is Qt bindings for Java when the language is C#? :S
The package for Qt bindings for C# is called Qyoto:
http://en.wikipedia.org/wiki/Qt_%28framework%29#Bindings
http://techbase.kde.org/Development/Languages/Qyoto
Qyoto makes it possible to develop Qt and KDE applications using C#, or any other .NET language. Qyoto uses SMOKE, and offers access to almost all Qt and KDE classes.
AFAIK you do not need to have Mono installed.
Pre-built binary packages are available in the following distributions:
Debian
Ubuntu
Arch Linux
Debian
Ubuntu
Arch Linux
Edited 2011-05-09 23:51 UTC
RE[4]: Comment by ephracis
by ephracis on Tue 10th May 2011 00:12
in reply to "RE[3]: Comment by ephracis"
RE[4]: Comment by ephracis
by Nelson on Tue 10th May 2011 03:09
in reply to "RE[3]: Comment by ephracis"
Of course you need Mono. Mono is the .NET Runtime required by C#.
As for the binding themselves, they're not too good.
ALSO, worth noting in the anouncement by Nokia is the fact that they admit what I and others have been talking about for months, but people on this website have dismissed.
One platform to rule them all is not practical at all.
The goal of the Qt 5 project is to offer the best possible functionality on each platform, implying that Qt will begin to offer more differentiated functionality on some OS’s, while still offering efficient re-use for the absolute majority of the code across platforms.
This is exactly whats true of the current situation with Silverlight. You can reuse 80% of your code across Xbox 360, Windows, Surface, Zune, and Windows Phone 7, but that other 10% must be specifically catered to the host platform.
The fairy tale that you can just write it once in Qt, and have it look, feel, and behave the same on all the platforms Qt supports is exactly that, a fairy tale.
So I'm glad Nokia has come out and said this, I mean, even if they are repeating what any competent developer has been screaming at the top of their lungs for some time now.
Qt: Good platform. Best C++ platform possibly (despite the fact that it heavily dresses up C++ into something useable using their Meta Object Compiler) for application development.
Lets not make things more than they are.





Member since:
2007-09-23
But, the whole application is written in C#. What good is Qt bindings for Java when the language is C#? :S