QML issues: Difference between revisions
| Line 72: | Line 72: | ||
| MouseEvent should also expose globalX and globalY | | MouseEvent should also expose globalX and globalY | ||
|- | |- | ||
| Proposed solution: | | Proposed solution: adding those properties to the declarative mouse event would be source compatible for existing qml files | ||
|- | |- | ||
| Discussion: | | Discussion: | ||
Revision as of 16:23, 10 June 2011
This page contains a list of issues and required features that we would like to see fixed/implemented in QML(2)
Enter the issues you wish fixed in the following form:
| Idea: | Change QML2 |
|---|---|
| Summary: | We have a chance to change stuff now |
| Proposed solution: | We change things |
| Discussion: | http://labs.qt.nokia.com/2011/05/09/thoughts-about-qt-5/ |
Issues
| Idea: | Improved namespace support |
|---|---|
| Summary: | QML should support namespaces in property types (property MyWidgets.Button myProperty) |
| Proposed solution: | |
| Discussion: |
| Idea: | Improved runtime warnings |
|---|---|
| Summary: | For example: QML should complain when the drag target is invalid |
| Proposed solution: | |
| Discussion: |
| Idea: | No QtSql dependency |
|---|---|
| Summary: | Remove QtSql dependency from QML library: QtSql should be loadable at runtime |
| Proposed solution: | |
| Discussion: |
Required features
| Idea: | MouseEvent.globalX/Y |
|---|---|
| Summary: | MouseEvent should also expose globalX and globalY |
| Proposed solution: adding those properties to the declarative mouse event would be source compatible for existing qml files | |
| Discussion: |
| Idea: | sizeHint |
|---|---|
| Summary: | sizeHint support |
| Proposed solution: | |
| Discussion: |
| Idea: | Layouts |
|---|---|
| Summary: | Layouts |
| Proposed solution: | |
| Discussion: |
| Idea: | Full set of graphical primitives |
|---|---|
| Summary: | at least Line, Path, Ellipse are missing |
| Proposed solution: | |
| Discussion: |