Hi,
I wants to start testing my Qml apps (qt4.8, quick 1.1) with Quick2 Qt5
... But how can I easily test it with Qt5 with a working Qt4 source ..
Is there any way to define #ifdef QT5 import Quick 2.0 #else import
Quick 1.1 ?
___
Interest mailing
On domingo, 19 de fevereiro de 2012 20.41.56, qtnext wrote:
> Hi,
>
> I wants to start testing my Qml apps (qt4.8, quick 1.1) with Quick2 Qt5
> ... But how can I easily test it with Qt5 with a working Qt4 source ..
> Is there any way to define #ifdef QT5 import Quick 2.0 #else import
> Quick 1.1
when 5.0 I will upgrade to Qt Quick 2.0 and never loop back ... But for
now, if it's possible it should allow me to evaluate performance and
continue to use Qt 4.8 for now ... a #ifdef syntax will also allow to
target multiple platform (android, windows... to adjust only certain
part) or differ
20.02.2012, 00:30, "qtnext" :
> when 5.0 I will upgrade to Qt Quick 2.0 and never loop back ... But for now,
> if it's possible it should allow me to evaluate performance and continue to
> use Qt 4.8 for now ... a #ifdef syntax will also allow to target multiple
> platform (android, windows...
On domingo, 19 de fevereiro de 2012 21.30.42, qtnext wrote:
> when 5.0 I will upgrade to Qt Quick 2.0 and never loop back ... But for
> now, if it's possible it should allow me to evaluate performance and
> continue to use Qt 4.8 for now ... a #ifdef syntax will also allow to
> target multiple plat
Op 19-2-2012 21:56, Thiago Macieira schreef:
> On domingo, 19 de fevereiro de 2012 21.30.42, qtnext wrote:
>> when 5.0 I will upgrade to Qt Quick 2.0 and never loop back ... But for
>> now, if it's possible it should allow me to evaluate performance and
>> continue to use Qt 4.8 for now ... a #ifde
Den 19-02-2012 21:00, Thiago Macieira skrev:
> On domingo, 19 de fevereiro de 2012 20.41.56, qtnext wrote:
>> Hi,
>>
>> I wants to start testing my Qml apps (qt4.8, quick 1.1) with Quick2 Qt5
>> ... But how can I easily test it with Qt5 with a working Qt4 source ..
>> Is there any way to define #i
On segunda-feira, 20 de fevereiro de 2012 08.23.26, Bo Thorsen wrote:
> Den 19-02-2012 21:00, Thiago Macieira skrev:
> > On domingo, 19 de fevereiro de 2012 20.41.56, qtnext wrote:
> >> Hi,
> >>
> >> I wants to start testing my Qml apps (qt4.8, quick 1.1) with Quick2 Qt5
> >> ... But how can I ea
On segunda-feira, 20 de fevereiro de 2012 08.07.30, Andre Somers wrote:
> Op 19-2-2012 21:56, Thiago Macieira schreef:
> > On domingo, 19 de fevereiro de 2012 21.30.42, qtnext wrote:
> >> when 5.0 I will upgrade to Qt Quick 2.0 and never loop back ... But for
> >> now, if it's possible it should al
Den 20-02-2012 08:53, Thiago Macieira skrev:
> On segunda-feira, 20 de fevereiro de 2012 08.23.26, Bo Thorsen wrote:
>> Den 19-02-2012 21:00, Thiago Macieira skrev:
>>> On domingo, 19 de fevereiro de 2012 20.41.56, qtnext wrote:
Hi,
I wants to start testing my Qml apps (qt4.8, quick
On segunda-feira, 20 de fevereiro de 2012 09.15.37, Bo Thorsen wrote:
> > Again, not the use-case. You don't support multiple versions of Qt Quick.
> > Multiple versions of Qt Quick support you.
> >
> > If you import Qt Quick 1.1, it will be the same version of 1.1 with the
> > same behaviour issu
On 2/20/12 10:47 AM, "ext Thiago Macieira" wrote:
>> > It's also possible to have different .qml files having slightly
>>different
>> > imports. You just can't mix major versions, because the backend
>>library is
>> > completely different.
>>
>> I would also assume that it's necessary to have s
it's sure that lot of people will wait for a release version of 5.0, or
5.1, if there is no way to use the same source code with #ifdef ...
Providing the way to test Qt5 before, will allow more feedback from
users ... and a stronger release ! just my two cents !
Le 21/02/2012 17:55, henry.have
t.org
Sent: Tuesday, February 21, 2012 12:06 PM
Subject: Re: [Interest] #define in qml
it's sure that lot of people will wait for a release version of 5.0, or
5.1, if there is no way to use the same source code with #ifdef ...
Providing the way to test Qt5 before, will allow more feedback from
On terça-feira, 21 de fevereiro de 2012 16.55.02, henry.haveri...@nokia.com
wrote:
> Another common case for #ifdefs is configuration management in
> cross-platform projects.
> It's not always possible to port a project to a new platform and never
> look back. :-)
That's not how you're supposed to
On terça-feira, 21 de fevereiro de 2012 18.06.37, qtnext wrote:
> it's sure that lot of people will wait for a release version of 5.0, or
> 5.1, if there is no way to use the same source code with #ifdef ...
> Providing the way to test Qt5 before, will allow more feedback from
> users ... and a str
21.02.2012, 22:09, "Thiago Macieira" :
> On terça-feira, 21 de fevereiro de 2012 18.06.37, qtnext wrote:
>
>> it's sure that lot of people will wait for a release version of 5.0, or
>> 5.1, if there is no way to use the same source code with #ifdef ...
>> Providing the way to test Qt5 before,
On terça-feira, 21 de fevereiro de 2012 22.16.09, Konstantin Tokarev wrote:
> 21.02.2012, 22:09, "Thiago Macieira" :
> > On terça-feira, 21 de fevereiro de 2012 18.06.37, qtnext wrote:
> >> it's sure that lot of people will wait for a release version of 5.0, or
> >> 5.1, if there is no way to use
As Thiago mentioned, one way to sidestep the
need for #ifdef is to have branch in version control
for each version.
Not all version control software is created equal in this respect though.
Branching in git is very good, svn less so.
Personally I have branches for meego, symbian, android,
+ adsup
On terça-feira, 21 de fevereiro de 2012 22.53.08, Harri Pasanen wrote:
> As Thiago mentioned, one way to sidestep the
> need for #ifdef is to have branch in version control
> for each version.
>
> Not all version control software is created equal in this respect though.
> Branching in git is very g
Den 21-02-2012 19:17, Thiago Macieira skrev:
> On terça-feira, 21 de fevereiro de 2012 22.16.09, Konstantin Tokarev wrote:
>> 21.02.2012, 22:09, "Thiago Macieira":
>>> On terça-feira, 21 de fevereiro de 2012 18.06.37, qtnext wrote:
it's sure that lot of people will wait for a release version
On 20-Feb-12 08:53, Thiago Macieira wrote:
> If you import Qt Quick 1.1, it will be the same version of 1.1 with
the same
> behaviour issues. If you don't change the import statement, the
behaviour will
> not change, even if Qt is upgraded.
That's not entirely true. The Qt upgrade might imply
22 matches
Mail list logo
