Hello guys, These are the notes I took from the QtScript session we had in Qt Summit. Not all names are there, it was a best effort to document who was saying what. Please, feel free to fix if there are stuff missing or not clear. :-)
QT-SCRIPT * Fact: V8 is the JS engine for Qt ** Possibly it will be part of QtBase ** Better/lower-level QObject and QML integration * QtScript API with V8 backend ** A lot of work was done, many things working. ** But conclusion is that supporting that old API with new backend is not the way to go. * Richard Dale: what about full Qt / QtScript bindings? Having them by default. ** Existing solution "add on" very heavy on memory ** Lars: should we provide those full bindings? Maybe not, maybe binding just what makes sense for the core. * Lars: how much API we need to provide in C++? ** Dale: want proper API for dealing with garbage collection. ** After understanding Dale's use case, it was conclude it was a misuse of QScriptValue. * Joerg Bornemann: What kind of problems you had with V8 backend? ** Existing debugging API. * Thomas(?): Use JS to control/customize generation of medical images * Thomas(?): What about setProcessInterval? ** Ideal solution is to make QSE et al thread-safe, and use it in other thread. * Lars: What can we improve ** Moving parts to QtBase gives us better conversions ** Just QSE and QSV * And what about current QtScript API? ** We want something simpler/smaller. ** Our API is bigger than V8! * Dale: uses QSC to interface Smoke, to produce bindings ** Original use case: generate bindings for existing * Thomas(?): uses QSC to make code pretty and have dynamic properties ** Exposing a Map of dynamic properties, internal representation * Joerg: uses its own implementation of QMLish property binding * Joerg: include-like mechanism using activationObject ** Can this be done in another way? ** Suggestion: explicit 'require' mechanism (copying object) * V8 only Intel and ARM ** Will this constrain Qt? * Dale: can we keep QScriptClass? ** Probably, it's done for V8, but we can improve QScriptClass API. * Dale: "adding signals/slots" -> useful for Smoke maybe? (???) * tjenssen: Documentation of JS functions (QtSDK) ** Maybe missing Q_INVOKABLE information in the docs? * "Merging" QVariant and QScriptValue ** They could share a lot, but they currently don't. ** Discussion about how to implement this sharing. * QtWebKit: bridging QWebElement and other things? ** Use QMetaType and provide conversion functions. * Stephen Kelly: bug when loading QtScript inside a plugin. * JS on QtBase, is it a good idea? ** Opportunities: regexp, string tables -> fast comparisons * The plan summary ** Build minimal JS support in QtBase: equivalents of QSV, QSE and the QObject binding ** Keep existing QtScript on JSC as done! ** Add more stuff like the equivalent of QSC Cheers, -- Caio Marcelo de Oliveira Filho OpenBossa - INdT _______________________________________________ Qt-script mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-script
