QtQuickMinutes20100907: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
h1. Agenda/Minutes September 7th, 2010
{{Delete|reason=Outdated information.}}
{{Cleanup | reason=Auto-imported from ExpressionEngine.}}


= Agenda/Minutes September 7th, 2010 =
* QML / QtDeclarative
* QML / QtDeclarative
** bugfixing[[Image:|Image:]] graphs are pointing down ;)
** bugfixing[[Image:|Image:]] graphs are pointing down ;)
Line 12: Line 14:


* QtComponents
* 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
** 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 24:
*** 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. "http://apidocs.meego.com/mtf/rotation.html":http://apidocs.meego.com/mtf/rotation.html
*** 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
), and can provide it in Qt Quick Components as stopgap and move to real implementation once available

Latest revision as of 08:31, 24 May 2015

This article is nominated for deletion. Reason: Outdated information.
Please raise your support/opposition to this nomination in the article's discussion page.
This article may require cleanup to meet the Qt Wiki's quality standards. Reason: Auto-imported from ExpressionEngine.
Please improve this article if you can. Remove the {{cleanup}} tag and add this page to Updated pages list after it's clean.

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
  • 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

), and can provide it in Qt Quick Components as stopgap and move to real implementation once available