[QBS] Status of QBS w.r.t. deprecation of QtScript
joerg.bornemann at theqtcompany.com
Thu Mar 26 16:29:15 CET 2015
On 25-Mar-15 22:56, Ruslan Nigmatullin wrote:
> 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.
This is unfortunately true. Some features are just missing from
QJSEngine and friends. I've created QTBUG-45246 for the missing
QJSEngine::newFunction and QTBUG-45248 for the missing QScriptClass
IMO, the first one is a must-have for QJSEngine. That feature is
definitely useful for a lot of people. The latter might be an edge case
- I could live with depending on private API for that.
> 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?
There are holes in the API. We could fill those with our own
implementations in qbs. Ideally, they can then be ported to QtQml and be
part of the public API eventually.
More information about the Qbs