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
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 mandag 27. juni 2016 14.30.48 CEST Frederik Gladhorn wrote:
> Hi all,
>
> good news when it comes to packaging on Linux, we added red hat 7.2 as the
> new packaging config for the dev branch - Qt 5.8 that is. We'll also run it
> as developer build with the 5.7 branch. I'll flip the switch to
Hi all,
good news when it comes to packaging on Linux, we added red hat 7.2 as the new
packaging config for the dev branch - Qt 5.8 that is. We'll also run it as
developer build with the 5.7 branch. I'll flip the switch to actually run it in
a few minutes.
I'd not be terribly surprised if
On Mon, Jun 27, 2016 at 10:29:34AM +, Edward Welbourne wrote:
> this would bring them to light early and one at a time, which tends to
> make them easier to resolve !
>
given that mutiple conflicts in the same place are pretty rare, i'll
challenge that claim.
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:
>
>>
Jędrzej Nowacki said (inter alia):
>Technically waiting for merges is not necessary. Coin is able
> to test arbitrary refs from gerrit, I encourage you to not wait for
> the system, but just make bunch of changes and tests the expected
> combination, before it gets merged from stable
> -Original Message-
> From: sean.harmer On Behalf Of Sean Harmer
> Sent: maanantaina 27. kesäkuuta 2016 11.46
> To: development@qt-project.org
> Cc: Tuukka Turunen
> Subject: Re: [Development] [Releasing] brown paper bag issue in Qt 5.6.1
> packages
>
> On Monday
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
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
On Monday 27 June 2016 07:18:02 Tuukka Turunen wrote:
> > -Original Message-
> > From: Development [mailto:development-
> > bounces+tuukka.turunen=qt...@qt-project.org] On Behalf Of Sean Harmer
> > Sent: perjantaina 24. kesäkuuta 2016 11.23
> > To: development@qt-project.org
> > Subject:
> 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
>
> -Original Message-
> From: Development [mailto:development-
> bounces+tuukka.turunen=qt...@qt-project.org] On Behalf Of Thiago
> Macieira
> Sent: maanantaina 27. kesäkuuta 2016 10.58
> To: development@qt-project.org
> Subject: Re: [Development] [Releasing] brown paper bag issue in Qt
On sábado, 25 de junho de 2016 21:24:12 PDT Thiago Macieira wrote:
> On sexta-feira, 24 de junho de 2016 08:51:51 PDT Thiago Macieira wrote:
> > On sexta-feira, 24 de junho de 2016 10:26:37 PDT Tuukka Turunen wrote:
> > > Hi,
> > >
> > > I do not know why 5.6.1 has been deleted, but it is of
On segunda-feira, 27 de junho de 2016 07:18:02 PDT Tuukka Turunen wrote:
> In general, it is valuable to be able to make releases quickly to fix e.g. a
> security vulnerability. The fastest way to do it is to push the needed
> change (or changes) into the release branch, and create new release
>
> -Original Message-
> From: Development [mailto:development-
> bounces+tuukka.turunen=qt...@qt-project.org] On Behalf Of Sean Harmer
> Sent: perjantaina 24. kesäkuuta 2016 11.23
> To: development@qt-project.org
> Subject: Re: [Development] [Releasing] brown paper bag issue in Qt 5.6.1
>
16 matches
Mail list logo