> >But QML itself is not bound to graphical user interfaces. It's a generic >declarative language that could just as well be used for many other, non >graphical tasks. Having this powerful engine available everywhere will >open up many possibilities. > >It would longer term also allow things such as using property bindings >from C++. This would allow app developers to save a lot of glue code. >Connecting signals to a piece of JS code also becomes possible (yes, >lambdas solve that problem to some extent as well).
For us in documentation moving the parser to QtCore would give significant benefits. We are implementing a QML Documentation parser currently which allows people to put qdoc comments inside qml files. This parser currently has an older copy of qtdeclarative/src/declarative/qml/parser in qtdoc/tools/qdoc3/declarativeparser since we do not really want to have qdoc to depend on the whole qtdeclarative stack. Moving the parser part to QtCore would allow us to stay on just depending on QtBase (We depend on core + xml) Casper _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
