I was actually hoping to write a simple “app” that inspects the meta objects,
and generates code based on that, instead of going the shiboken way and trying
to parse the C++ Code myself (though I am looking into shiboken as well). I’m
also looking into misusing clang(d) to parse it :) In the bes
On Wednesday 27 November 2024 23:45:02 Pacific Standard Time Marcus Tillmanns
via Development wrote:
> I would like to script the creation and usage of all of the QWidget classes.
> What’s the likelihood of acceptance (of a merge request) if I were to add
> Q_INVOKABLE to the constructors and meth
> On 28 Nov 2024, at 16:02, Fabian Kosmale via Development
> wrote:
>
> Note however that using QMetaType has the limitation that it will only allow
> calling the default constructor. While all widgets should be default
> constructible, you might want to construct e.g.
> `QDialogButtonBox::QD
Note however that using QMetaType has the limitation that it will only
allow calling the default constructor. While all widgets should be
default constructible, you might want to construct e.g.
`QDialogButtonBox::QDialogButtonBox` with some specific button). Could
be worked around in the bindin
> On 28 Nov 2024, at 15:01, André Somers via Development
> wrote:
>
> Hi Marcus,
>
> On 28-11-2024 14:29, Marcus Tillmanns via Development wrote:
>> Hi Shawn,
>>
>>> On 28. Nov 2024, at 13:15, Shawn Rutledge via Development
>>> wrote:
>>>
>>>
On Nov 28, 2024, at 09:08, Fabian Kosmale
Hi Marcus,
On 28-11-2024 14:29, Marcus Tillmanns via Development wrote:
Hi Shawn,
On 28. Nov 2024, at 13:15, Shawn Rutledge via Development
wrote:
On Nov 28, 2024, at 09:08, Fabian Kosmale via Development
wrote:
- Some are already (indirectly) exposed via Q_PROPERTY; should anyone decid
> On 28. Nov 2024, at 09:08, Fabian Kosmale via Development
> wrote:
>
> Hi,
>
> I can't speak for our Widget maintainers, but in the context of renewed
> interest in Qt Lite, I'd suggest to put this behind a feature flag, so that
> users who don't actually need scriptable widgets don't hav
Hi Shawn,
> On 28. Nov 2024, at 13:15, Shawn Rutledge via Development
> wrote:
>
>
>> On Nov 28, 2024, at 09:08, Fabian Kosmale via Development
>> wrote:
>> - Some are already (indirectly) exposed via Q_PROPERTY; should anyone decide
>> to expose those Widgets to QML (or some other language
> On Nov 28, 2024, at 09:08, Fabian Kosmale via Development
> wrote:
> - Some are already (indirectly) exposed via Q_PROPERTY; should anyone decide
> to expose those Widgets to QML (or some other language binding working on the
> meta-object system), this would cause some friction because ther
Hi,
I can't speak for our Widget maintainers, but in the context of renewed
interest in Qt Lite, I'd suggest to put this behind a feature flag, so
that users who don't actually need scriptable widgets don't have to pay
the price in binary size.
As far as direct drawbacks are concerned, it's
Hi,
I would like to script the creation and usage of all of the QWidget classes.
What’s the likelihood of acceptance (of a merge request) if I were to add
Q_INVOKABLE to the constructors and methods of each QWidget derived class and
QWidget itself?
I guess the downside is enlarged meta objects
11 matches
Mail list logo
