|
|
| Line 1: |
Line 1: |
| =Notes from QtQuick session=
| |
|
| |
|
| ==Adaptive UI continued from QtCS 2013==
| |
|
| |
| Apparently we have form factor detection now? https://codereview.qt.io/#change,84471<br /> That should help finish enacting the previous adaptable UI plans, but now we need people to use them and provide feedback.
| |
|
| |
| ==Views NG continued from QtCS 2013==
| |
|
| |
| A couple more people partially volunteered. Maybe we can add them together and get 1 full volunteer to start working on this?
| |
|
| |
| ==QtGui equivalent==
| |
|
| |
| ''For types not non-visual QtQml, but not QtQuick specific''
| |
|
| |
| “QtQmlGui” layer is needed, for stuff like Qt.vector3D and colors, which is <span class="caps">GUI</span> related (not viable for QtQml) but should be shared between more than just QtQuick.
| |
|
| |
| Prerequisite feature for the <span class="caps">QML</span> discussion – Module dependencies. Something like<br /> in your qmldir, and then<br />
| |
|
| |
| Then we can have QtQuick using QtQml 2.0 and QtQmlGui 2.0, and “move” items without breaking applications.
| |
|
| |
| ==Some new elements==
| |
|
| |
| Both suggested, and likely will be contributed, by Sean Harmer.
| |
|
| |
| ===Polar Coordinate Positioner===
| |
|
| |
| Positions items around a pole.
| |
|
| |
| ===MouseRegion===
| |
|
| |
| Non-rectangular MouseArea. Probably a new element, as it will be much more complex and it will be overkill for the common case.
| |
|
| |
| ==Expanded Touch Regions for fat fingers==
| |
|
| |
| Touch Special Handling? Threshold around touch events<br /> Long term might want:<br /> Where threshold is implemented inside the touch delivery and includes intelligent heuristics (like if you touch an area between a tiny button and a giant button, you probably wanted the tiny button because if you wanted the giant button you’d be closer to the center).
| |
|
| |
| But for now, MouseArea margins can do the basic, non-intelligent way. Especially when using singletons:<br /> So a per device/form singleton and having MouseArea margins bind to that allows all anchors.fill: parent MouseAreas to extend beyond their parent.
| |
|
| |
| ==QFontMetrics Functionality==
| |
|
| |
| TextContainer element which exposes similar functionality to QFontMetrics. But it exposes it by sizing a non-visual item with set sizes. Like an invisible text item, more efficient and not propagating visibility to its children. Something like:<br /> But TextContainer is a terrible name…
| |