Qt 5.7 released

#1

Post by bpierre » Thu, Jun 16, 2016, 10:36 AM UTC

Qt 5.7 released
blog.qt.io

Re: Qt 5.7 released

#2

Post by reddotX » Thu, Jun 16, 2016, 11:43 AM UTC

JIT support for WinRT, and 64bit ARM platforms in Qt QML, leading to much better QML performance on these platforms

+1 for qml perfromance

Re: Qt 5.7 released

#3

Post by smegel » Thu, Jun 16, 2016, 12:03 PM UTC

reddotX wrote: post #2

JIT support for WinRT, and 64bit ARM platforms in Qt QML, leading to much better QML performance on these platforms +1 for qml perfromance

JIT for declarative markup? Has that even been done before?

Re: Qt 5.7 released

#4

Post by rubber_duck » Thu, Jun 16, 2016, 12:22 PM UTC

smegel wrote: post #3

reddotX wrote: post #2

JIT support for WinRT, and 64bit ARM platforms in Qt QML, leading to much better QML performance on these platforms +1 for qml perfromance

JIT for declarative markup? Has that even been done before?

QML is basically a JavaScript superset ?

Re: Qt 5.7 released

#5

Post by CarVac » Thu, Jun 16, 2016, 12:25 PM UTC

smegel wrote: post #3

reddotX wrote: post #2

JIT support for WinRT, and 64bit ARM platforms in Qt QML, leading to much better QML performance on these platforms +1 for qml perfromance

JIT for declarative markup? Has that even been done before?

QML has always had it, as far as I know. It makes for a little pause when loading an application as the logic is compiled. I'm not sure what other markup languages have done this, though.

They do have a Qt Quick compiler though which removes the need to JIT the user interface; maybe next release it'll see the light of day on the open-source side of things.

Re: Qt 5.7 released

#6

Post by _pmf_ » Thu, Jun 16, 2016, 12:33 PM UTC

smegel wrote: post #3

reddotX wrote: post #2

JIT support for WinRT, and 64bit ARM platforms in Qt QML, leading to much better QML performance on these platforms +1 for qml perfromance

JIT for declarative markup? Has that even been done before?

XAML/BAML/WPF?

Re: Qt 5.7 released

#7

Post by once-in-a-while » Thu, Jun 16, 2016, 12:35 PM UTC

rubber_duck wrote: post #4

smegel wrote: post #3

Earlier quoted context omitted.

JIT for declarative markup? Has that even been done before?

QML is basically a JavaScript superset ?

Yeah, it's that bad... If all of your code base is C++, what do you think the mindset is of the main developers? The only compromise they were able to allow themselves to think in was... ECMAScript. Sad.

Re: Qt 5.7 released

#8

Post by Aissen » Thu, Jun 16, 2016, 12:38 PM UTC

With LGPLv3, the Qt company is sending a clear signal it's time to pay if you want to use Qt in a device (the industry being clearly anti-(L)GPLv3). It could be the chance for GTK, if they weren't also busy digging their own grave :-/ http://lwn.net/Articles/691131

Re: Qt 5.7 released

#9

Post by criddell » Thu, Jun 16, 2016, 12:39 PM UTC

Does anybody have experience with other cross platform GUI toolkits that are still actively developed? It's starting to feel like Qt is going to win it all because they are enduring (and excellent).

Re: Qt 5.7 released

#10

Post by rsp1984 » Thu, Jun 16, 2016, 12:50 PM UTC

Aissen wrote: post #8

With LGPLv3, the Qt company is sending a clear signal it's time to pay if you want to use Qt in a device (the industry being clearly anti-(L)GPLv3). It could be the chance for GTK, if they weren't also busy digging their own grave :-/ http://lwn.net/Articles/691131

Why is the industry anti-LGPLv3? In Layman's terms what are the key differences between LGPL v2.1 and v3?