On Friday, May 25, 2012 11:55:08 Christoph Cullmann wrote: > On Friday, May 25, 2012 11:14:17 Dominik Haumann wrote: > > And it's unclear, whether a jsc update would fix the issue, btw :-) > > Still, a fix for QtScript would be the nicest solution or a port to the
Right, maybe an increase of the allowed memory would work, or similar changes... > "new" engine provided in Qt5, as I understood, there QtScript is anyway > "deprecated" in favour of the V8 based new variant? Yes, it's called QJSEngine along with QJSValue then. > But does the new engine provide the same nice features to easily wrap your > objects and expose a custom API? That was the major reason we switched > over from KJS to QtScript. QJSEngine::newQObject exists, I guess it works exactly the same. That does not help us in Qt4/KDE4, though. Greetings, Dominik
