Qt wiki will be updated on October 12th 2023 starting at 11:30 AM (EEST) and the maintenance will last around 2-3 hours. During the maintenance the site will be unavailable.
QtQuickMinutes20100914: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
AutoSpider (talk | contribs) (Add "cleanup" tag) |
||
Line 1: | Line 1: | ||
{{Cleanup | reason=Auto-imported from ExpressionEngine.}} | |||
[[Category:Developing_with_Qt::Qt Quick::Minutes]] | [[Category:Developing_with_Qt::Qt Quick::Minutes]] | ||
Revision as of 16:40, 3 March 2015
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 14th, week 37, 2010
QML / QtDeclarative
- bugs, looking at new models, supporting versions on properties and methods in qobject. text performance experiments. scenegraph text handling
- when do we change QML to scenegraph? When it's finished - some time next year? It will be a very smooth migration for plain QML
- Physical Units support
- mobility system info runs JS expression per property. slow!
- QPainter has it already
- best solution is to expose function call =cm() / mm()= with caching it and not requiring to execute a JS expression
Bauhaus / Creator
- working on designer. Qt Quick components inside Designer being tried out, using Mx style
- dependency for current style is libmeegotouch, on linux - Mx style hasn't been worked on for a while
- could we persist all pixmaps to enable running on other platforms, needed for Qt Quick Designer on multiple platforms
- would also need to do the same for CSS too..
- working on debugger
- implementing features - both side navigation (designer / source code), changing properties applied directly to running app, hover / tooltip
- would be nice to be able to emit signal / execute JavaScript
- server side of inspector needs to be integrated back to Qt
- unify inspector/debugger naming for QML?
Documentation
- class chart, looking at feedback. It's still too unreadable
- looking at Qt Components documentation
QtComponents
- finished slider progress bar, working on dropdown menu. first version of the demo MeeNotes
- Qt Quick Components code camp week before dev days munich
QML Enablers
- split out gesture in separate module
- GestureArea API in review, needs to be more declarative
Scenegraph
- progressing nicely, performance is quite good now - significantly better than QGraphicsView-based QML on average