On Tuesday 05 July 2011, Artur de Souza wrote:
> Quoting Marco Martin :
> > so, what else remains to do??
>
> Besides not working right now I think that the "module API" that today
> uses QScriptValue will still be present (I just asked for it anyway in
> qt-qml mailing list). Even if it doesn't u
On Tuesday 05 July 2011, Artur de Souza wrote:
> Quoting Marco Martin :
> > so, what else remains to do??
>
> Besides not working right now I think that the "module API" that today
> uses QScriptValue will still be present (I just asked for it anyway in
> qt-qml mailing list). Even if it doesn't u
Quoting Marco Martin :
> so, what else remains to do??
Besides not working right now I think that the "module API" that today
uses QScriptValue will still be present (I just asked for it anyway in
qt-qml mailing list). Even if it doesn't use QScriptValue but some
other stuff in the future.
On Tuesday 05 July 2011, Artur Souza (MoRpHeUz) wrote:
>
>1. Creator integration will probably not work as smoothly in the
> short term - at the very least the JavaScript debugging will not work.
>2. Any QML API that relies on QML's undocumented ability to set and
> get QScriptValue proper
FYI
-- Forwarded message --
From:
Date: Tue, Jul 5, 2011 at 1:20 AM
Subject: [Qt-qml] Merging V8 into qtdeclarative.git#master
To: qt-...@qt.nokia.com
Hi,
Tomorrow we will merge the qtdeclarative.git#v8 branch into
qtdeclarative.git#master. This change switches the JavaScrip
