[Development] The missing pieces of QJSEngine
nassian at bitshift-dynamics.de
Sat May 28 11:47:38 CEST 2016
What’s the point with calling C++ code from JS? We are doing this all the day - via signal/slots and registered types.
Beste Grüße / Best regards,
> Am 28.05.2016 um 11:42 schrieb Corentin <corentin.jabot at gmail.com>:
> I'm once again trying to cut dependencies on Qt Script.
> QJSEngine still lacks some features to do so.
> The ability to call a function from JS to C++. I found a work in that direction. https://codereview.qt-project.org/#/c/108871/2 <https://codereview.qt-project.org/#/c/108871/2> . I am told the api was probably abandoned over threading consideration.
> The ability to construct a QObject from JS. QtScript had newQMetaObject for that.
> I have see a lot of people requesting the ability to call a c++ function from JS. One classic usage I have in mind is the implementation of the PAC standard
> As for creating QObject from JS, there are tons of use cases. It is my understanding that QBS
> depends on this feature a lot.
> I don't think that QJSEngine can really pretend to be a replacement for QScriptEngine without those features
> So, I have a few questions
> Is anyone working on these features ?
> If not, is there an interest for these api ?
>  https://developer.mozilla.org/en-US/docs/Mozilla/Projects/Necko/Proxy_Auto-Configuration_(PAC)_file <https://developer.mozilla.org/en-US/docs/Mozilla/Projects/Necko/Proxy_Auto-Configuration_(PAC)_file>
> Development mailing list
> Development at qt-project.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Development