Re: [Development] QML 3 and JavaScript

2019-11-11 Thread Kevin Kofler
Giuseppe D'Angelo via Development wrote: > Il 11/11/19 11:31, Kevin Kofler ha scritto: >> So, whereas we C++ developers get to deal with all the deprecations and >> porting for Qt 6, QML developers can just stick to QML 2 forever and keep >> their code completely unchanged because you are going to

Re: [Development] QML 3 and JavaScript

2019-11-11 Thread Vlad Stelmahovsky
sounds promising :-> On Mon, Nov 11, 2019 at 7:11 PM Giuseppe D'Angelo via Development < development@qt-project.org> wrote: > Il 11/11/19 11:31, Kevin Kofler ha scritto: > > So, whereas we C++ developers get to deal with all the deprecations and > > porting for Qt 6, QML developers can just stick

Re: [Development] QML 3 and JavaScript

2019-11-11 Thread Giuseppe D'Angelo via Development
Il 11/11/19 11:31, Kevin Kofler ha scritto: So, whereas we C++ developers get to deal with all the deprecations and porting for Qt 6, QML developers can just stick to QML 2 forever and keep their code completely unchanged because you are going to maintain the entire old QML 2 for them??? How is t

Re: [Development] QML 3 and JavaScript

2019-11-11 Thread Jason H
If not _javascript_, then what? Python? This is the first I've heard of this. Just wondering what it is if not _javascript_?     Sent: Monday, November 11, 2019 at 3:10 AM From: "Dmitriy Purgin" To: "Qt development mailing list" Subject: [Development] QML 3 and _javascript_ Hi all,   as

Re: [Development] QML 3 and JavaScript

2019-11-11 Thread Konstantin Tokarev
11.11.2019, 13:35, "Kevin Kofler" : > Simon Hausmann wrote: >>  Am 11.11.19 um 09:10 schrieb Dmitriy Purgin: >>>  I understand that QML 2 is not going anywhere in Qt 6 but maintaining >>>  both QML 2 and QML 3 will be a burden for the developers of the Qt >>>  Framework, and I'm afraid QML 2 won'

Re: [Development] QML 3 and JavaScript

2019-11-11 Thread Kevin Kofler
Simon Hausmann wrote: > Am 11.11.19 um 09:10 schrieb Dmitriy Purgin: >> I understand that QML 2 is not going anywhere in Qt 6 but maintaining >> both QML 2 and QML 3 will be a burden for the developers of the Qt >> Framework, and I'm afraid QML 2 won't get much love after QML 3 is >> released. Just

Re: [Development] Nominating Cristian Adam as approver

2019-11-11 Thread Michal Klocek
+1 Br Michal On 11/8/19 9:35 PM, Alessandro Portale wrote: > Hi, > > I like to propose Cristian Adam as an approver. > > Cristian has been around Qt (and Qt Creator) for what feels like a decade,  > contributing and inspiring, professionally and privately. > > Half a Year ago, he finally joi

Re: [Development] QML 3 and JavaScript

2019-11-11 Thread Simon Hausmann
Am 11.11.19 um 09:10 schrieb Dmitriy Purgin: > Hi all, > > as we learned at the recent Qt World Summit in Berlin, we're getting > QML 3 with Qt 6. There are some cool features and changes to improve > the clarity and the performance of the QML part but there is one thing > that bothers me: the

[Development] QML 3 and JavaScript

2019-11-11 Thread Dmitriy Purgin
Hi all, as we learned at the recent Qt World Summit in Berlin, we're getting QML 3 with Qt 6. There are some cool features and changes to improve the clarity and the performance of the QML part but there is one thing that bothers me: the optionality of JavaScript. What I didn't quite get is wheth