> On 19 Jul 2016, at 16:44, Uwe Rathmann wrote:
>
> On Tue, 19 Jul 2016 15:45:44 +0200, Jean-Michaël Celerier wrote:
>
>> Is there some code somewhere ?
>
> Sure on my disk ;)
>
> Being serious: the code is supposed to be available under an Open Source
> License,
On Tue, 19 Jul 2016 15:45:44 +0200, Jean-Michaël Celerier wrote:
> Is there some code somewhere ?
Sure on my disk ;)
Being serious: the code is supposed to be available under an Open Source
License, but it needs to have an initial level of quality first. And
there is still a long way to go.
On Tue, Jul 19, 2016 at 12:33 PM, Uwe Rathmann
wrote:
>
> More details about my experiment will be presented at: https://
> conf.qtcon.org/en/qtcon/public/events/428
Is there some code somewhere ?
I really want to use the Qt scenegraph but I'd much rather use C++ than
On Tue, 19 Jul 2016 11:10:26 +0200, Benjamin TERRIER wrote:
> * you can't even create ...
As I'm currently working on a library offering Quick Controls with an C++
API ( having a QML API as well ) I already have some experience in what
it means.
The very first thing you will notice is that
If your app is for desktop only, I suggest you go with Widget instead
of Qt Quick.
Sure Qt Quick has many advantages but for desktop only software it still lacks
major features, for instance Qt Quick Controls 2 does not handle mouse hovering
(e.g Buttons will not highlight when the cursor is
Op 07/07/2016 om 23:52 schreef Rob Allan:
I'm part of a team that is looking at migrating an existing Windows
C++ app to Qt. The first decision is whether to use Widgets or Qt
Quick. Since Qt Quick is newer, shinier, faster, etc, that seems like
the obvious choice. However, for reasons that
If some of your forms are user defined, maybe you can take a look to the
QML editor code integrated in QtCreator. I don't know if it's rendered with
QML or something else, if it's in QML then the way it is done should be
correspond to what your a looking for.
I don't know why Qt doesn't support
Hi Xavier,
Thanks for your thoughts on this. Yes, I think I understand the way that Qt
Quick and QML can be used to make layouts that are dynamic and updatable
depending on property bindings. However, I think I'm talking about another
level of customization - namely, forms that are constructed
I think that our approche can be wrong, maybe you don't need to be able to
access to the QtQuick components from the C++. The best is to follow the
philosophy of QtQuick with the property bindings. You can expose variables
(properties) from your c++ to the QML and let the QML interact with them.
I'm part of a team that is looking at migrating an existing Windows C++ app
to Qt. The first decision is whether to use Widgets or Qt Quick. Since Qt
Quick is newer, shinier, faster, etc, that seems like the obvious choice.
However, for reasons that I won't go into here, the vast majority of forms
10 matches
Mail list logo