Hi all, Looks like right now it's impossible to migrate to QtQml without using private API, i.e. QtQml doesn't provide any alternatives for QScriptContext, QScriptEngine::newFunction and QScriptClass.
So the question - should we force adding this public APIs to QtQml or start using private API to make port? May be I'm missing something and there are other alternatives? Ruslan 25.03.2015, 06:02, "Joerg Bornemann" <joerg.bornem...@theqtcompany.com>: > Hi Bill, >> I wonder, therefore, what the position of QBS within Qt is, when a >> module that QBS depends on is being deprecated in Qt! > > QtScript is going to be deprecated, but it will keep working for quite > some time. > > Sooner or later qbs must be ported to the QJS* API of the QtQml module > anyway. The deprecation of QtScript is yet another motivation point to > do that. > > Note that the 1.3 branch of qbs still had to build with Qt4. Qbs 1.4 is > the first version where such a port would make sense. > > BR, > > Joerg _______________________________________________ QBS mailing list QBS@qt-project.org http://lists.qt-project.org/mailman/listinfo/qbs