标题:Evolution of the QML engine, part 1
作者:fanformylove
日期:2013-04-15 22:15
内容:
原文:http://blog.qt.digia.com/blog/2013/04/15/evolution-of-the-qml-engine-part-1/
Evolution of the QML engine, part 1
Published April 15, 2013 | By Lars Knoll
QML as a technology has become increasinglyimportant for the success of Qt. It allows for the creation of smooth,animated user interfaces, in line with expectations on the market today.There are three main features, that make it so suitable for UIcreation. The first one is the declarative syntax, that makes itextremely easy to create these user interfaces and have both developersand UI designers work on the same code base. Secondly, the technologymakes the integration of native code relatively easy, allowing to domuch of the application logic and heavy lifting in C++. And finally, thechoice of Javascript as an integral part of the QML language allows foreasy prototyping and opens the technology up to a wider audience.
The engine as it is today is a fantastic basis and fills most of ourusers needs. However, it also has a couple of shortcomings and problemsthat will need to get solved in the future. This series of blogs isgoing to outline our findings and present the solutions that we areplanning to implement for them. The goal will be to get to a better,more flexible and easier to maintain QML engine in the future.
So let’s start of with some of the problems we’re facing with the current engine.Several object models
The current QML engine uses the V8 Javascript engine to execute propertybindings. Each QML item has several representations internally. Onetowards V8 (using the public V8 API), one towards the QML engine, andone to expose it as a QObject to native Qt. The problem here is thatthis requires the QML engine to keep these different represen ..
#1 [liuzh_szz 04-17 13:42]
意思是v4vm是一个巨NB的绑定引擎，运行速度能比现在Qt4.8里QtQuick1快三倍？
不知道Qt4.9或者Qt5.2能不能用上哇，反正起码还得等半年