Difference between revisions of "Qt-contributors-summit-2013-QtQuickControls CS 2013"

From Qt Wiki
Jump to: navigation, search
m (Categorize)
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
 +
{{Cleanup | reason=Auto-imported from ExpressionEngine.}}
 +
[[Category:QtCS2013]]
 
==Minutes from the Qt Quick Controls session==
 
==Minutes from the Qt Quick Controls session==
  
Qt Contributors’ Summit, Tuesday July 15, 2013 @15.00
+
Qt Contributors' Summit, Tuesday July 15, 2013 @15.00
  
 
===Plans for Qt 5.2===
 
===Plans for Qt 5.2===
Line 17: Line 19:
 
Plans for desktop controls:
 
Plans for desktop controls:
  
* Inter application drag&drop
+
* Inter application drag&drop
 
* Complete styling <span class="caps">API</span> for all controls
 
* Complete styling <span class="caps">API</span> for all controls
 
* Calendar control
 
* Calendar control
Line 30: Line 32:
 
* Plan to design and implement a generic touch style
 
* Plan to design and implement a generic touch style
  
===Q&amp;A===
+
===Q&A===
  
* What about different dpi’s?
+
* What about different dpi's?
 
** Solution is to have two different sets of pixmaps. By using the Styling <span class="caps">API</span> you can take care of what to use where.
 
** Solution is to have two different sets of pixmaps. By using the Styling <span class="caps">API</span> you can take care of what to use where.
  
 
Tizen about Styling:
 
Tizen about Styling:
  
* Tomasz from Tizen: Would like to move the controls’ logic to the Style as well (not only to look)
+
* Tomasz from Tizen: Would like to move the controls' logic to the Style as well (not only to look)
** instead “import qtquickcontrols.tizen”
+
** instead "import qtquickcontrols.tizen"
 
** Will have the the same challenge for Galaxy-style, Sailfish etc.
 
** Will have the the same challenge for Galaxy-style, Sailfish etc.
 
** Will look at the use cases first
 
** Will look at the use cases first
Line 53: Line 55:
 
** Fall back to native controls
 
** Fall back to native controls
 
** import qtquickcontrols.mac should be reserved for things that are purely Mac specific
 
** import qtquickcontrols.mac should be reserved for things that are purely Mac specific
** Could use styleHints. (not official yet): styleHInts: {“rounded”: true}
+
** Could use styleHints. (not official yet): styleHInts: {"rounded": true}
 
* Will try to fix the Unified ToolBar for 5.2
 
* Will try to fix the Unified ToolBar for 5.2
  
More Q&amp;A
+
More Q&A
  
 
* Menu object is a Qt Quick Item.
 
* Menu object is a Qt Quick Item.
Line 64: Line 66:
 
** Answer: This seems too be much magic. Want to be declarative. But to be considered.
 
** Answer: This seems too be much magic. Want to be declarative. But to be considered.
  
* Resize “stutters” on LInux
+
* Resize "stutters" on LInux
 
** Answer: This is a Window manager issue that cannot really be solved within Qt. (any opengl windows display similar behavior)<br /> (There is a Window manager guy at QtCS: Gunnar should discuss with him)
 
** Answer: This is a Window manager issue that cannot really be solved within Qt. (any opengl windows display similar behavior)<br /> (There is a Window manager guy at QtCS: Gunnar should discuss with him)
  

Latest revision as of 17:32, 6 January 2017

Minutes from the Qt Quick Controls session

Qt Contributors' Summit, Tuesday July 15, 2013 @15.00

Plans for Qt 5.2

  • Deployment: Not easy with 5.1. Hope to simplify with 5.1.1 and even more with 5.2
  • Provide a C++ QQuickAction API – possibly support QAction with controls directly
  • Cannot deploy multiple icon sizes currently – possibly introduce a new file format/descriptor for multi-resolution images
  • Make the widget dependency a run time dependency. (currently only possible at compile time).

New API:

Plans for desktop controls:

  • Inter application drag&drop
  • Complete styling API for all controls
  • Calendar control
  • Pickers
  • Editable combo boxes
  • Make it easier to make dialogs

Touch Controls:

  • Extend the controls with more touch specific components
  • However all controls will run on all platforms
  • Plan to design and implement a generic touch style

Q&A

  • What about different dpi's?
    • Solution is to have two different sets of pixmaps. By using the Styling API you can take care of what to use where.

Tizen about Styling:

  • Tomasz from Tizen: Would like to move the controls' logic to the Style as well (not only to look)
    • instead "import qtquickcontrols.tizen"
    • Will have the the same challenge for Galaxy-style, Sailfish etc.
    • Will look at the use cases first
  • E.g. ContextMenu (Java: DropDown menu. Tizen: pop-up)
    • Can use native menu on Android
    • Could make and API to style the style
  • Suggestion: Tizen make a list of where the logic should change compared to the current set of controls. Then the controls team can evaluate whether the logic can be put into the control implementation and optionally turned on with a flag.

Mac Controls

  • Wish for Mac extra like controls
    • Fall back to native controls
    • import qtquickcontrols.mac should be reserved for things that are purely Mac specific
    • Could use styleHints. (not official yet): styleHInts: {"rounded": true}
  • Will try to fix the Unified ToolBar for 5.2

More Q&A

  • Menu object is a Qt Quick Item.
  • For very fancy Controls (like a tree view inside a combo box): End user still has the option to develop this themselves by using QML.
  • Why are there inconstancies between Layouts for Widgets and Controls? (e.g. radio buttons in the widgets world are made into a group box)
    • Answer: This seems too be much magic. Want to be declarative. But to be considered.
  • Resize "stutters" on LInux
    • Answer: This is a Window manager issue that cannot really be solved within Qt. (any opengl windows display similar behavior)
      (There is a Window manager guy at QtCS: Gunnar should discuss with him)
  • Adaptation for different form factors
    • Should controls be adaptable
    • Can internally depend on adaptation selectors
    • Goal is not to have one set of controls that look good on all platforms