You can also phrase your modules as C++-only static libraries and
link them all together into the application. - That will depends on
which C++ library your modules depends on. Not all code can be
legally made static, this restriction, seem rather short sighted.
Hope they change this.
Well, yes,
.
-Original Message-
From: Ulf Hermann
Sent: September 15, 2020 2:33 AM
To: Jérôme Godbout ; interestqt-project.org
Subject: Re: [Interest] QML/C++ interaction in Qt6
On 9/14/20 5:29 PM, Jérôme Godbout wrote:
> Oh,... now that's a deal breaker... I guess I will have to stick with
&
On 9/14/20 5:29 PM, Jérôme Godbout wrote:
Oh,... now that's a deal breaker... I guess I will have to stick with
the old method for a while, having 1 plugins per modules to be expose
will need some major refactor over here. I have subrepos who have a
single .pri and might expose a few modules and
D'Angelo
Sent: September 14, 2020 11:22 AM
To: Jérôme Godbout
Subject: Re: [Interest] QML/C++ interaction in Qt6
On 14/09/2020 17:19, Jérôme Godbout wrote:
> Yeah I got that part, the part I do not get is how can you have multiple
> QML_IMPORT_NAME and multiple files in each? how do you tell
Il 14/09/20 15:54, Jérôme Godbout ha scritto:
//
how does the Person class is link to the People name exactly?!?
QML_IMPORT_NAME does the link.
The "equivalent" of registering a QML_ELEMENT class, using the syntax of
old registrations is something like
qmlRegisterType("QML_IMPORT_NAME"
something I don’t get here? Thanks
-Original Message-
From: Ulf Hermann
Sent: September 12, 2020 3:24 AM
To: Jérôme Godbout ; interest@qt-project.org
Subject: Re: [Interest] QML/C++ interaction in Qt6
> Will Qt 6 still use the Meta information to access Qml properties or
> it rely mo
Will Qt 6 still use the Meta information to access Qml properties or
it rely more on compiled C++ now? I guess it still the same as
before. Is the properties declaration of Qt for MCU (Qml lite or
soemthign like that) be available (syntax wise, template)? That would
leverage soo much redundent cod
, 2020 6:20 AM
To: interest@qt-project.org
Subject: Re: [Interest] QML/C++ interaction in Qt6
> - Allow QML to access public properties of classes, even if these
> public properties do not use `Q_PROPERTY`
> - Allow QML access to classes that are neither `QObject`, nor
> `QGadget`
- Allow QML to access public properties of classes, even if these public
properties do not use `Q_PROPERTY`
- Allow QML access to classes that are neither `QObject`, nor `QGadget`
This is not planned right now. Note that we rely on moc to generate the
class descriptions that QML uses. Therefor
Hi,
since Qt6 is going to include the strict QML subset, where everything can be
compiled down to native C++, I was wondering if there are efforts going with
that to improve interactions between the two languages along with it.
Two things I am thinking of specifically:
- Allow QML to access
10 matches
Mail list logo
