On Friday, 25. May 2012 21:42:50 Stephen Kelly wrote: > Christoph Cullmann wrote: > > Still, a fix for QtScript would be the nicest solution or a port to the > > "new" engine provided in Qt5, as I understood, there QtScript is anyway > > "deprecated" in favour of the V8 based new variant? > > Nope. QtScript might be 'done' - meaning no one is working on it and there's > no replacement. The v8 stuff is not public API like QtScript is, so it is > not a replacement. > > > But does the new engine provide the same nice features to easily wrap your > > objects and expose a custom API? > > Yes. That's how QtDeclarative works. As it's internal, non-public API, that > doesn't really matter much. > > Maybe a public API will be created to replace QtScript eventually though...
According to the docs http://doc-snapshot.qt-project.org/5.0/qjsengine.html QJSEngine and QJSValue are already public API. Maybe I'm mistaken? Dominik
