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 472447
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Comment by ephracis
by Nelson on Tue 10th May 2011 03:09 UTC 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

RE[6]: Comment by ephracis
by saynte on Tue 10th May 2011 05:23 in reply to "RE[5]: Comment by ephracis"
saynte Member since:
2007-12-10


Better to program in any language but C#.


Yeah, just use Java, then you'll be safe from patent litigation then! ;)

But seriously, patent suits could come from anywhere, to be overly concerned with .Net doesn't seem useful. This is especially true when you consider that two implementations of Java have been taken to court, and AFAIK no .Net implementations have seen the same treatment.

I would say Microsoft's Community Promise actually provides more protection than is usually provided (ie, none).

Reply Parent Score: 3

RE[6]: Comment by ephracis
by ggeldenhuys on Tue 10th May 2011 11:44 in reply to "RE[5]: Comment by ephracis"
ggeldenhuys Member since:
2006-11-13

Better to program in any language but C#.


+1
I would stay far away from Mono. It's a lawsuit waiting to happen. Most of the useful classes and other things in Mono are all patented by Microsoft.

An alternative option I would happily recommend, is the Object Pascal language via the Free Pascal (FPC) compiler. FPC supports a lot of platforms (10+) including mobile ones, and is 32-bit and 64-bit enabled. The language is damn easy to learn and full Object Oriented Programming support is included (it is NOT the Pascal language from the 80's!). FPC also has excellent documentation, loads of bindings to various libraries out of the box, and a huge FCL library (free pascal non-visual component library for a myriad of things).

There are also many GUI toolkits to choose from as well.

Lazarus LCL, which includes a very capable IDE too with a visual forms design, integrated debugging, and excellent editor etc. LCL uses native widgets from each platform and supports Mac, Windows, Linux, Windows CE etc.

Then there is fpGUI Toolkit, which is a 100% custom drawn toolkit, if you want the exact same look and behaviour on all platforms. It supports Windows, Linux, Mac, Windows CE and Embedded Linux.

There is also MSEgui which also includes it's own IDE, which is also 100% custom drawn. Supporting Windows and Linux.

We have used FPC for over 8 years in a commercial environment (moving away from Delphi) and our products run under Windows, Linux and Mac with great success!

http://www.freepascal.org
http://www.lazarus.freepascal.org
http://fpgui.sourceforge.net
http://www.msegui.org

Reply Parent Score: 1