[Interest] Kicking out QtScript completely

[Koehne Kai]

> -----Original Message-----
> From: Samuel Stirtzel [mailto:s.stirtzel at googlemail.com]
> [...]
> 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?

I'm not really involved in the development here, but my understanding is that QJSEngine should cover most the use cases of QtScript, indeed.

> Currently it lacks the most basic features, not even print() or
> console.log() is available, see [2].

This is trivial to add back yourself though by adding your own print / console object to the engine context. We did so when moving the Qt Installer Framework from QtScript to QtQmlEngine ... Somewhat more interesting was the implementation of the dynamic lookup of objects by their object name, but in the end we managed without breaking any script.

Regards

Kai