> if we had time to filter out all the good ideas from all the frameworks, we’d
> have a better chance of making ours the best. ;-)
Agreed :)
> Well we advertise that it’s a declarative language. We could make it even
> more that way, even if it’s not strictly necessary. Would it be more eleg
> On 27 Jun 2016, at 23:12, Filippo Cucchetto
> wrote:
>
> Thank you Shawn for your reply
>
> > Control is composed of fewer objects. You should be testing it for some
> > time already.
> Well i already used the QtQuickControls 2 and i do understand that their
> design if superior (like for
Thank you Shawn for your reply
> Control is composed of fewer objects. You should be testing it for some
time already.
Well i already used the QtQuickControls 2 and i do understand that their
design if superior (like for example the font handling) but
i still think that composition of multiple QQu
Please let's try not go off topic. This post is for improving and
collecting ideas for improving the QtQuick event handling.
I would be more interested in knowing the struggle you had dealing with it
and discussing the idea i've proposed
F.
2016-06-27 11:28 GMT+02:00 Uwe Rathmann :
> On Mon, 27
Disclaimer: I'm writing some mix of personal opinion (which is subject to
change anyway) and opinions that I’ve heard from others, in reply to this...
> On 27 Jun 2016, at 11:28, Uwe Rathmann wrote:
>
> On Mon, 27 Jun 2016 08:39:42 +, Shawn Rutledge wrote:
>
>> We have mostly stopped worki
On 27 June 2016 at 17:28, Uwe Rathmann wrote:
>
> On Mon, 27 Jun 2016 08:39:42 +, Shawn Rutledge wrote:
>
> > We have mostly stopped working on QtQuick Controls 1, because the
> > implementation of Controls 2 is much more performant ...
>
> Controls 2 are for "embedded" - what at least means t
On Mon, 27 Jun 2016 08:39:42 +, Shawn Rutledge wrote:
> We have mostly stopped working on QtQuick Controls 1, because the
> implementation of Controls 2 is much more performant ...
Controls 2 are for "embedded" - what at least means to me: not being for
desktop applications.
> It was achiev
> On 25 Jun 2016, at 15:15, Filippo Cucchetto
> wrote:
>
> hi everyone,
> this is going to be a lengthy email so i'd like to thank those
> who will read it and maybe give me their opinions.
> The topic here is throwing some ideas for improving QtQuick event
> handling (both for mouse and keyboa
hi everyone,
this is going to be a lengthy email so i'd like to thank those
who will read it and maybe give me their opinions.
The topic here is throwing some ideas for improving QtQuick event
handling (both for mouse and keyboard).
First let's take a look at some simple/silly keyboard examples tha
