--0016e6dab05256fb4c04725bb634
Content-Type: text/plain; charset=ISO-8859-1
Hello people,
Everything is in the subject but i wanted to raise the discussion before the
Technology Preview of Qt 4.6 will arrive (soon since Qt 4.6 is not open
anymore to features). Actually Plasma people are in Tokamak and after
presenting the QGraphicsView features that will arrive they really would
like to use them for KDE 4.4. The features will be : Animations and state
machine API, QGraphicsEffects and performance improvements (i.e. for
netbooks).
Qt 4.6 will be released end of this year which means that distribution will
probably do the same story that they did with 4.2 and Qt 4.5 (i.e ship 4.5
regardless of the non-testing aspect). So should we based the trunk on top
of 4.6 for KDE 4.4?
In Qt Software side, you will find all the help you need to fix
bugs/problems in #qt-labs or you can catch me on IRC. ogoffart will be happy
to help i am sure.
Thanks for comment...
--0016e6dab05256fb4c04725bb634
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Hello people,
Everything is in the subjec=
t but i wanted to raise the discussion before the Technology Preview of Qt =
4.6 will arrive (soon since Qt 4.6 is not open anymore to features). Actual=
ly Plasma people are in Tokamak and after presenting the QGraphicsView feat=
ures that will arrive they really would like to use them for KDE 4.4. The f=
eatures will be : Animations and state machine API, QGraphicsEffects and pe=
rformance improvements (i.e. for netbooks).
Qt 4.6 will be released end of this year which means th=
at distribution will probably do the same story that they did with 4.2 and =
Qt 4.5 (i.e ship 4.5 regardless of the non-testing aspect). So should we ba=
sed the trunk on top of 4.6 for KDE 4.4?
In Qt Software side, you will find all the help you nee=
d to fix bugs/problems in #qt-labs or you can catch me on IRC. ogoffart wil=
l be happy to help i am sure.
Thanks for comment..=
.
--0016e6dab05256fb4c04725bb634--