Ilya Diallo schreef op 25-6-2015 om 23:30: > Hi Julien, > > A long thread on this list last march on this subject was concluded by > an answer from Frederik Gladhorn (copy below). For now (5.5), the best > is probably to postpone your migration if you want to avoid > "unofficial" workarounds. QtScript is not going anywhere until feature > parity is (more or less) achieved, with a porting guide for > incompatibilities. > Your proposals could be part of a porting documentation, though. > > Ilya. > Current plans are that QtScript will be around up to and including Qt 5.6, but dropped for 5.7. QtQuick 1 and QtWebkit won't make it into 5.6, but will still compile against it. This is the outcome of recent discussions on the Qt Contributor Summit and the development mailinglist afterwards.
Feature freeze for 5.6 is in a bit over a month I think. So, that would be very little time to actually achieve that feature parity. I would not bet on it to be honest. André _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
