Just a "heads-up", but I spent the last couple weeks playing around with
"pyotherside", which binds a Python engine into QML ("pyotherside" is
deployed as a C++ compiled QML plugin).I am really impressed. It is really awesome -- it integrates well, is easy to use, and we can now put QML applications on top of our Python code bases. (We are mostly a C++ shop, and we're mostly doing C++ plugins, but Python is handy for internal tools and prototyping.) Main web site: http://thp.io/2011/pyotherside/ Latest docs (v1.2): http://pyotherside.readthedocs.org/en/latest/ DevDays 2013 Berlin talk here: http://www.youtube.com/watch?v=2HAFOZ5_Xks&index=17&list=PLizsthdRd0YyV6zOEFYog77IAPV85f7w2 I'm not affiliated with the project -- I'm just tickled at how well it integrates into QML. I didn't realize it existed until KDAB put the Berlin talks online. As a silly thought-experiment, IMHO the QML/Javascript is a "better-Javascript" because it's strongly-typed and the new QML/JS engine is "more-integrated" leading to greater possible bytecode/speed/packaging features in the future. However, I'm somewhat curious what the Qt community would think about making "Python" a first-class-citizen in the QML world. If we did, I'd probably vote for an API that looks like that provided through "pyotherside". I have a general "fear/trepidation" with putting more-than-trivial logic into Javascript, but I'm less concerned about scaling logic through Python. --charley
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
