Re: [Development] QML import versions

2015-09-20 Thread Nurmi J-P
Hi, > On 20 Sep 2015, at 15:35, Jocelyn Turcotte wrote: > > - It would be nice to be able to increase a module’s major version without > waiting for Qt6 I can see the desire to implement and release new major versions - we developers love rewriting things. :) But in the

Re: [Development] QML import versions

2015-09-20 Thread Filippo Cucchetto
I'm no troll, but i don't see any way to solve this without putting something new to the table 1) What about extending the a little bit the QML language itself. Something like import QtQuick as in 5.5 import QtQuick.Controls as in 5.5 so a way to specify to import a module at version when a

Re: [Development] QML import versions

2015-09-20 Thread Jocelyn Turcotte
Hi, I always had that feeling too, that QML import versions are confusing if you don’t have any IDE to give you direct insight on what is available. If I put my user hat, I can see three reasons on why I’m usually fiddling with the import version: 1) Which major version of the plugin do I

Re: [Development] QML import versions

2015-09-20 Thread Jocelyn Turcotte
> On 20 Sep 2015, at 13:55, Filippo Cucchetto > wrote: > > I'm no troll, but i don't see any way to solve this without putting something > new to the table > > 1) What about extending the a little bit the QML language itself. > Something like > import QtQuick as

Re: [Development] QML import versions

2015-09-20 Thread Nurmi J-P
Hi Alan, > On 18 Sep 2015, at 20:13, Alan Alpert <4163654...@gmail.com> wrote: > > On Fri, Sep 18, 2015 at 8:12 AM, Nurmi J-P wrote: >> Hi all, >> >> I'd like to propose that all QML imports that are part of the Qt Essentials >> start following the respective Qt

Re: [Development] QML import versions

2015-09-20 Thread Olivier Goffart
On Friday 18. September 2015 15:12:22 Nurmi J-P wrote: [...] > What makes the situation even more cumbersome, to ourselves who develop > these modules, is that there's no convention on how new properties are > revisioned. Some classes are using a running revision number that gets > incremented

Re: [Development] QML import versions

2015-09-20 Thread Alan Alpert
On Sun, Sep 20, 2015 at 11:56 AM, Robin Burchell wrote: > On Fri, Sep 18, 2015, at 08:15 PM, Nurmi J-P wrote: >> > I have some opposition to the idea because it entirely prevents us from >> > making changes if they are needed. An example of this came up just the >> > other

Re: [Development] QML import versions

2015-09-20 Thread Alan Alpert
On Sun, Sep 20, 2015 at 4:55 AM, Filippo Cucchetto wrote: > I'm no troll, but i don't see any way to solve this without putting > something new to the table > > 1) What about extending the a little bit the QML language itself. > Something like > import QtQuick as in

Re: [Development] QML import versions

2015-09-20 Thread Jocelyn Turcotte
> On 20 Sep 2015, at 19:34, Nurmi J-P wrote: > > Hi, > >> On 20 Sep 2015, at 15:35, Jocelyn Turcotte wrote: >> >> - It would be nice to be able to increase a module’s major version without >> waiting for Qt6 > > I can see the desire to

Re: [Development] QML import versions

2015-09-20 Thread Robin Burchell
On Fri, Sep 18, 2015, at 08:15 PM, Nurmi J-P wrote: > > I have some opposition to the idea because it entirely prevents us from > > making changes if they are needed. An example of this came up just the > > other day on IRC: Window{} has a number of major (or at least quite > > irritating) flaws.