“When we get qmltc and qmlcachegen into a shape where the code generated
by qmltc can directly call the functions and expressions compiled by
qmlcachegen we won't need much of an engine anymore if you exclusively
run pre-compiled code. “ - Ulf
I very much can’t wait for this as I have run into
To Volker's point: I also mentioned in my post that Qt Quick never had a
Triangle. Or Circle. Or any other primitive shapes. It has come up before that
the use of ShapePath is one solution for such cases, but that also it isn't the
most performant.
To that end I would recommend this thread
+1 for tidying up the API in the manner suggested.
But a welcome addition - thanks to Matthias Rauter.and Mitch Curtis - who I
would be asking about the group properties in the first instance.
- which I already did 7 months ago...
Pedro had already reached out to me on my experience with this for myself and I
gave some helpful feedback at that time. Many folk have since here echoed those
points.
Reading the comments thus made, I would council those responsible for listening
to the feedback to do so without comment until
Yes, this is also in line with a request I had made about the same – and the
documentation has already had some attention in regard to migrating away the
“reference” APIs to differentiate the “core” APIs to affect wider adoption.
+1 from me.
Mike
Confidentiality Notice: This message
+1 for Jarek and for this module.
From: Development on behalf of André
Hartmann
Sent: Friday, December 1, 2023 4:00:07 PM
To: apoenitz ; Fabian Kosmale
Cc: development@qt-project.org
Subject: Re: [Development] Proposing new Qt Creator module: Qt Creator
Definitely!
From: Development on behalf of Shawn
Rutledge
Sent: Wednesday, September 21, 2022 9:01:10 PM
To: Qt Development
Subject: Re: [Development] Requesting a repository for Qt Quick Effect Maker
Yes! I’m looking forward to having that public.
On 2022
