QtQuickMinutes20100907: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 12: | Line 12: | ||
* QtComponents | * QtComponents | ||
** going well, have many components and have a demo application to implement; | ** going well, have many components and have a demo application to implement; "http://bugreports.qt.nokia.com/browse/QTCOMPONENTS-74":http://bugreports.qt.nokia.com/browse/QTCOMPONENTS-74 | ||
* QML Enablers | * QML Enablers | ||
| Line 22: | Line 22: | ||
*** Qt Mobility could provide UI orientation via system info | *** Qt Mobility could provide UI orientation via system info | ||
*** long term should come from Qt to prevent fragmentation | *** long term should come from Qt to prevent fragmentation | ||
*** short term, can be used from C++ (e.g. native frameworks such as e.g. | *** short term, can be used from C++ (e.g. native frameworks such as e.g. "http://apidocs.meego.com/mtf/rotation.html":http://apidocs.meego.com/mtf/rotation.html | ||
), and can provide it in Qt Quick Components as stopgap and move to real implementation once available | |||
Revision as of 13:24, 25 February 2015
h1. Agenda/Minutes September 7th, 2010
- QML / QtDeclarative
- bugfixing[[Image:|Image:]] graphs are pointing down ;)
- Bauhaus / Creator
- working on describing the QML tooling story, in blog form
- currently working on deployment, debugger, text editor
- Documentation
- finished with 4.7.0, only ciritcal stuff. new content 4.7.1
- QtComponents
- going well, have many components and have a demo application to implement; "http://bugreports.qt.nokia.com/browse/QTCOMPONENTS-74":http://bugreports.qt.nokia.com/browse/QTCOMPONENTS-74
- QML Enablers
- investigating refactoring event delivery for non-spatial gestures
- investigating recogniser model that splits between high-level (tap, swipe, pinch) and low level (touch, mouse, sensor)
- Specific Topics
- Orientation: QDeclarativeEngine, qmlviewer, QtMobility?
- Qt Mobility could provide UI orientation via system info
- long term should come from Qt to prevent fragmentation
- short term, can be used from C++ (e.g. native frameworks such as e.g. "http://apidocs.meego.com/mtf/rotation.html":http://apidocs.meego.com/mtf/rotation.html
- Orientation: QDeclarativeEngine, qmlviewer, QtMobility?
), and can provide it in Qt Quick Components as stopgap and move to real implementation once available