Hi Stefan,
I've discovered that QTScript is at the end of the development life and deprecated for future projects.
It will be substituted by the QJSEngine class:
Did you explore the possibility to use QJSEngine, one day, as replacement engine for ScriptCommunicator?
I think that the main limitation of QTScript engine is the lack of the JIT compiler (as V8 for javascript or LuaJIT for Lua). I've read that the inner Javascript engine of the WebView widget is V8-based and has a completely different development branch.
It is incredible that while QTScript is "dead" the WebView Javascript engine is under active development.
This may be an important issue for the future of ScriptCommunicator and, as usual, it could be better to start thinking Today for the development of Tomorrow.
I think that "old technologies" could be powerful if integrated in tools like ScriptCommunicator. Personally I used small, clever tools (but based on old technology) for long time before changing to new ones.
Kindest regards,
Pier Andrea.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Stefan,
I've discovered that QTScript is at the end of the development life and deprecated for future projects.
It will be substituted by the QJSEngine class:
https://forum.qt.io/topic/52306/qt-5-5-qt-script-deprecated-what-is-replacement/3
Did you explore the possibility to use QJSEngine, one day, as replacement engine for ScriptCommunicator?
I think that the main limitation of QTScript engine is the lack of the JIT compiler (as V8 for javascript or LuaJIT for Lua). I've read that the inner Javascript engine of the WebView widget is V8-based and has a completely different development branch.
It is incredible that while QTScript is "dead" the WebView Javascript engine is under active development.
This may be an important issue for the future of ScriptCommunicator and, as usual, it could be better to start thinking Today for the development of Tomorrow.
I think that "old technologies" could be powerful if integrated in tools like ScriptCommunicator. Personally I used small, clever tools (but based on old technology) for long time before changing to new ones.
Kindest regards,
Pier Andrea.
Hi Pier,
I had this on my list.
PS: I think all API functions which are used by SC and SC-scripts are available in QJSEngine.
Thx for pointing this out to me,
Stefan