Linked by Nth_Man on Fri 5th Jul 2013 21:42 UTC
Qt Qt 5.1 has been released. It brings several enhancements, Qt Quick Controls, Qt Sensors, a much better C++11, Wayland and OpenGL support, and the development of Android and iOS applications is very usable for a large number of use cases. In related news, the LXDE desktop prepares the change to Qt.
Thread beginning with comment 566478
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Good news
by moondevil on Sat 6th Jul 2013 06:03 UTC in reply to "RE[2]: Good news"
moondevil
Member since:
2005-07-08

Only WPF is comparable somehow but WPF is C# and managed .net and can't be used from regular C++.


You seem to have been away from Windows for some time.

The XAML stack has been rewritten in C++ for Windows 8.

When targeting Metro applications, you can use XAML with C++/CX, which compiles to native code. Or use the Windows Runtime template framework when you prefer to use plain C++ without language extensions.

MFC is just crap.


I always find funny people complaining about MFC.

When Microsoft did MFC they tried to copy Borland's OWL by doing a proper OO framework. This is where Afx prefix comes from.

After some field research, most complained it was too OO and they would prefer just a thin layer over Win32, which triggered a rewrite before publishing it.

So the ones to blame are the C developers moving to Windows that couldn't deal with C++.

Reply Parent Score: 4

RE[4]: Good news
by dpJudas on Sun 7th Jul 2013 02:12 in reply to "RE[3]: Good news"
dpJudas Member since:
2009-12-10

The XAML stack has been rewritten in C++ for Windows 8.

When targeting Metro applications, you can use XAML with C++/CX, which compiles to native code. Or use the Windows Runtime template framework when you prefer to use plain C++ without language extensions.


While true what you write, you are leaving something out:

1. C++/CX only really works for Windows 8+. Thus, unless you are willing to ditch 90% of your potential market, you can't use it yet for quite a while (5+ years with current reception of Win8).

2. C++/CX is not C++. Personally I like C++/CX a lot better than C++/CLI, but it is still a language bridge into a foreign type system. It roughly falls into the same category as Objective C++.

3. The Windows Runtime template framework is indeed C++, but from what I've seen of it so far I'd prefer even MFC over what I saw!

Given those constraints, the C++ XAML stack as an alternative to Qt for a C++ developer is not a very good one at this time. Except when explicitly targeting Metro and nothing else.

Reply Parent Score: 3

RE[5]: Good news
by moondevil on Sun 7th Jul 2013 07:37 in reply to "RE[4]: Good news"
moondevil Member since:
2005-07-08

I agree with your points.

Before using Microsoft tooling, I was using Borland most of the time.

Visual C++ funny enough, being Visual did not offer the same RAD capabilities of Delphi and C++ Builder have since 1995.

Or the capabilities provided by OWL in Turbo Pascal and Turbo/Borland C++.

Instead Microsoft extensions always seemed to cater more to the C developer going C++. Which given the background of the initial MFC prototype seems to have been the case.

Reply Parent Score: 3

RE[5]: Good news
by Nelson on Sun 7th Jul 2013 13:41 in reply to "RE[4]: Good news"
Nelson Member since:
2005-11-29

You can use WRL and ISO C++ as well.
Really you only use CX at the ABI boundary and it maps nicely to C++11 semantics.

Reply Parent Score: 3