[Interest] Kicking out QtScript completely

[Samuel Stirtzel]

2015-03-17 15:54 GMT+01:00 Koehne Kai <Kai.Koehne at theqtcompany.com>:
>> On Behalf Of Christian Dahn
>> Sent: Tuesday, March 17, 2015 3:34 PM
>> To: interest at qt-project.org
>> Subject: [Interest] Kicking out QtScript completely
>>
>> Hi folks,
>>
>> as stated inside the Qt Blog the devs just decided to drop any QtScript
>> support within the next release - without any replacement for users NOT
>> USING QML / console apps!
>>
>> This will even break any backend app running without gui, because starting
>> with Qt 5.6 only scripting by using the QML module is supported and all
>> support for QtScript will be completely dropped without any non-GUI
>> replacement!!!!
>
> The QtQml library has no GUI dependency. So while I see some porting effort to switch from QtScript to QtQml, it's not true that this prevents command line applications.
>
> And you don't have to use the QML language either ... QtQml has a QJSEngine class.
>

Hi,

in what way is the QJSEngine a replacement for QtScript?

IIRC QJSEngine was not designed as a replacement for QtScript because
then it would've been to slow for QML, but this is a rather old topic:
[1].
So is it planned to provide QJSEngine as a full QtScript replacement?

Currently it lacks the most basic features, not even print() or
console.log() is available, see [2].
With QQmlEngine this is another case, but there are other pitfalls..



[1] http://thread.gmane.org/gmane.comp.lib.qt.devel/4185
[2] https://bugreports.qt.io/browse/QTBUG-40772


-- 
Regards
Samuel