Linked by Thom Holwerda on Mon 9th May 2011 21:14 UTC, submitted by Elv13
Qt Since Nokia announced its switch to Windows Phone 7, people have been worried about the future of Qt. Well, it turns out Nokia is still going full steam ahead with Qt, since it has just announced the plans for Qt 5. Some major changes are afoot code and functionality-wise, but the biggest change is that Qt 5 will be developed out in the open from day one (unlike Qt 4). There will be no distinction between a Nokia developer or third party developer.
Thread beginning with comment 472420
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Comment by ephracis
by lemur2 on Mon 9th May 2011 23:48 UTC in reply to "RE[2]: Comment by ephracis"
lemur2
Member since:
2007-02-17

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


Edited 2011-05-09 23:51 UTC

Reply Parent Score: 6

RE[4]: Comment by ephracis
by ephracis on Tue 10th May 2011 00:12 in reply to "RE[3]: Comment by ephracis"
ephracis Member since:
2007-09-23

Yes, I've heard of it. But have anyone used it? Is it good? Any thoughts on it? Experiences? Tips and tricks?

:)

Reply Parent Score: 2

RE[5]: Comment by ephracis
by Elv13 on Tue 10th May 2011 05:03 in reply to "RE[4]: Comment by ephracis"
Elv13 Member since:
2006-06-12

It is autogenerated and as far as I know, nobody use it. Sometime, doing a clean C++ reimplementation is a better idea. C# -> Qt is possible. After all, if you use mono, your code will still use .NET "stdl" instead Qt "stdl", so it wont work that well. Then I am not sure how it handle signal and slots. It work fine in Python and did worked fine in Java, but I am not sure about C#. If the apps is less than 5K LOC, I would consider a rewrite, it will be easier than debugging a binding that your alone to use.

Reply Parent Score: 2

RE[4]: Comment by ephracis
by Nelson on Tue 10th May 2011 03:09 in reply to "RE[3]: Comment by ephracis"
Nelson Member since:
2005-11-29

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.

Reply Parent Score: 2

RE[5]: Comment by ephracis
by lemur2 on Tue 10th May 2011 03:46 in reply to "RE[4]: Comment by ephracis"
lemur2 Member since:
2007-02-17

Of course you need Mono. Mono is the .NET Runtime required by C#.


I looked into this ... it appears that you are correct.

This requirement would make the whole thing a bust. ALthough C# is an ECMA standard and it is covered by Microsot's Community Promise, Mono inseperably includes a lot more than just the C# runtime, including components that are claimed by Microsoft as proprietary to Microsoft, and covered by Microsoft-held patents.

This would appear to make the whole thing a bust.

Better to program in any language but C#.

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.


Perhaps for those who do not like C++, D is the go.

http://en.wikipedia.org/wiki/D_%28programming_language%29

Edited 2011-05-10 03:52 UTC

Reply Parent Score: -1