Qt-contributors-summit-2011-QML Tooling: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
m (Categorize) |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{Cleanup | reason=Auto-imported from ExpressionEngine.}} | |||
[[Category:QtCS2011]] | |||
Notes from the discussion (mostly Feedback session): | Notes from the discussion (mostly Feedback session): | ||
| Line 7: | Line 9: | ||
==Photoshop Export Plugin== | ==Photoshop Export Plugin== | ||
There are problems when the source file changes over time, and the already exported .qml files & | There are problems when the source file changes over time, and the already exported .qml files & graphical assets should be updated. Designers should ideally be educated to e.g. retain layer names. | ||
Other ideas: | Other ideas: | ||
| Line 16: | Line 18: | ||
* Can one somehow mark a button as a button in Photoshop already? * Is Photoshop the right tool ten? Better use Adobe Illustrator | * Can one somehow mark a button as a button in Photoshop already? * Is Photoshop the right tool ten? Better use Adobe Illustrator | ||
Ideally Designers should be educated & | Ideally Designers should be educated & be working closely together with the programmer, but that’s just often not the case (e.g. when they are working for another company). | ||
==Interaction Designer / Flowchart Editor== | ==Interaction Designer / Flowchart Editor== | ||
Latest revision as of 16:45, 6 January 2017
| 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. |
Notes from the discussion (mostly Feedback session):
Dependency Graph of Bindings
Can one show which events / property changes trigger the change of a specific binding, which triggered the event / property change again etc?
Photoshop Export Plugin
There are problems when the source file changes over time, and the already exported .qml files & graphical assets should be updated. Designers should ideally be educated to e.g. retain layer names.
Other ideas:
- ‘Explotion Diagram’ or just grid of names that show the assets
- Logging the Actions done in Photoshop to allow mappings of assets independent from names
- View in Photoshop that shows the existing .qml file as e.g. semi-transparent overlay
- Can one somehow mark a button as a button in Photoshop already? * Is Photoshop the right tool ten? Better use Adobe Illustrator
Ideally Designers should be educated & be working closely together with the programmer, but that’s just often not the case (e.g. when they are working for another company).
Interaction Designer / Flowchart Editor
A tool that let you quickly prototype simple flows between screens etc
- Often this is done as wireframes. A component set that shows e.g. everything grayish would help here
- People use Flash, Adobe Illustrator, Powerpoint …
- Needs to be graphical such that Designers, non-technical people can use it * Simple things like ‘if you click here you go to state 2’ should be done without editing .qml (can be a specific element for this purpose)
- Things to check out : Balsamik, Adobe Illustrator
Quick Designer
What is it meant for?
- Right now not useful for Designers (too limited)
- Not enough for programmers either
Problems Quick Designer faces
- Expressiveness of QML
- Imperative code
Ideas:
- Make a new format for static stuff only (Qt Designer alike) * Could be #pragma designer
- Put dynamic stuff in second file * Merging of both files e.g. by inheritance, property aliases
Anchors
- Anchoring does not allow you to select target anchor
- Show anchors as e.g. dotted lines (Adobe Illustrator shows guides)
- Create anchors when e.g. snapping + control key