summaryrefslogtreecommitdiffstats
path: root/src/declarative/qml/qdeclarativecompiler_p.h
Commit message (Collapse)AuthorAgeFilesLines
* Don't export declarative private classesMartin Jones2010-07-011-1/+1
| | | | | Those required by creator are still exported. Everything else is no longer exported.
* Test ListElement type via type system, not string comparison.Warwick Allison2010-06-251-0/+1
| | | | | Task-number: QTBUG-11222 Reviewed-by: Aaron Kennedy
* Cleanup: Move import stuff out of the QDeclarativeEngineAaron Kennedy2010-04-291-1/+2
|
* Remove unused variableAaron Kennedy2010-04-281-1/+0
|
* Remove dead codeAaron Kennedy2010-04-221-1/+0
|
* Remove Script {} supportAaron Kennedy2010-04-191-1/+0
|
* Correctly support translation in QDeclarativeCompilerAaron Kennedy2010-04-151-2/+2
| | | | Reviewed-by: Friedemann Kleint
* Add Component.onDestruction attached propertyAaron Kennedy2010-04-151-2/+0
| | | | | | | | | This property complements Component.onCompleted. It is emitted before the destruction actually begins (for the most part) so the objects are still alive and accessible. The QtObject.onDestroyed signal is now blocked as it never really worked properly anyway.
* CleanupAaron Kennedy2010-04-091-0/+2
|
* Update #include of private headers in QtDeclarativeThiago Macieira2010-04-021-8/+8
| | | | | Always use private/. The WinSCW compiler doesn't search the current directory, for whatever reason.
* Improve QML compiler statisticsAaron Kennedy2010-03-291-4/+3
|
* Allow enum constants as list element properties.Warwick Allison2010-03-171-0/+2
| | | | Task-number: QTBUG-5974
* Optimization: Reduce unnecessary QObject allocationsAaron Kennedy2010-03-171-1/+2
|
* Run signal expressions on attached property objects in correct scopeAaron Kennedy2010-03-041-0/+1
| | | | QTBUG-8677
* Move JS global scope to top of the QML scope chainAaron Kennedy2010-03-031-1/+1
| | | | QT-2787
* Make "on" syntax mandatory for value sources and interceptorsAaron Kennedy2010-03-021-0/+5
| | | | | | | | | | | | | | | | | | | | | Where you would have written x: NumberAnimation {} y: Behavior {} you now must write NumberAnimation on x {} Behavior on y {} This change also makes the parser more strict with respect to multiple assignments to a single property - they're no longer allowed. For example this x: 10 x: 11 is now an error.
* Automatically connect to signals "onFooChanged" if property is "foo".Bea Lam2010-02-251-1/+2
| | | | | | | This follows on from a2a8cea2835ef24104fe784b6ce0f508cc5637c0 to make it work for PropertyChanges and QDeclarativeMetaProperty as well. Task-number: QT-2783
* Change class prefix to from QmlXXX to QDeclarativeXXX, QmlGraphicsXXX to ↵Warwick Allison2010-02-241-0/+337
QDeclarativeXXX.