clarative/+/267234 ).
Simon
> *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 we learned at the recent Qt World Summit in Berlin,
Will the live reloading of QML engine be supported as of version 3?
On Tue, Nov 12, 2019 at 11:24 AM Ulf Hermann wrote:
> > If not Javascript, then what? Python? This is the first I've heard of
> > this. Just wondering what it is if not javascript?
>
> It will be a subset of JavaScript, with typ
> If not Javascript, then what? Python? This is the first I've heard of
> this. Just wondering what it is if not javascript?
It will be a subset of JavaScript, with type annotations in TypeScript
style, that does not necessitate a garbage collector and minimizes
dynamic memory allocation. I don
Hello Kevin,
On mandag 11. november 2019 11:31:16 CET Kevin Kofler wrote:
> 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
> >>
The point of maintaining the QML 2 engine is
- to still support live preview/editing of QML components,
- giving users the choice to actually have all of the power of
JavaScript, including closures, generators, the arguments object, etc.,
in their QML components,
- to not break thousands upon
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
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
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
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
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'
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
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
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
13 matches
Mail list logo
