qiurui
/
qtdeclarative
mirror of https://github.com/qt/qtdeclarative.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
qtdeclarative/examples/quick/pathitem/pathitem.qrc

24 lines
1.3 KiB
Plaintext
Raw Normal View History

Add QQuickPathItem and its backend infra The generic backend uses the triangulator from QtGui, but is in fact OpenGL-only for now due to materials. The NVPR backend uses GL_NV_path_rendering on NVIDIA hardware with OpenGL 4.3+ or OpenGL ES 3.1+. The software backend simply uses QPainter. With the generic backend each PathItem is backed by a non-visual root node and 0, 1 or 2 child geometry nodes, depending on the presence of visible stroking and filling. The potentially expensive triangulation happens on updatePolish(), on the gui thread. This is proven to provide much smoother results when compared to doing the geometry generation on the render thread in updatePaintNode(), in particular on power-limited embedded devices. The NVPR backend uses a QSGRenderNode in DepthAware mode so that the batch renderer can continue to rely on the depth buffer and use opaque batches. Due to not relying on slow CPU-side triangulation, this backend uses 5-10 times less CPU, even when properties of the path or its elements are animated. The path itself is specified with the PathView's Path, PathLine, PathArc, PathQuad, etc. types. This allows for consistency with PathView and the 2D Canvas and avoids a naming mess in the API. However, there won't be a 100% symmetry: backends like NVPR will not rely on QPainterPath but process the path elements on their own (as QPainterPath is essentially useless with these APIs), which can lead to differences in the supported path elements. The supported common set is currently Move, Line, Quad, Cubic, Arc. The patch introduces PathMove, which is essentially PathLine but maps to moveTo instead of lineTo. More types may get added later (e.g. NVPR can do a wide variety of optimized rounded rects, but this requires directly specifying a GL_ROUNDED_RECTx_NV command, thus neededing a dedicated Path type on our side too) For filling with gradients only linear gradients are supported at the moment. In addition to the declarative API, a more lightweight, QObject-less JS-callable API should be considered as well for the future. Change-Id: I335ad64b425ee279505d60e3e57ac6841e1cbd24 Reviewed-by: Andy Nichols <andy.nichols@qt.io>
2016-12-03 20:30:12 +00:00
<RCC>
<qresource prefix="/pathitem">
<file alias="LauncherList.qml">../shared/LauncherList.qml</file>
<file alias="SimpleLauncherDelegate.qml">../shared/SimpleLauncherDelegate.qml</file>
<file alias="images/next.png">../shared/images/next.png</file>
<file alias="images/back.png">../shared/images/back.png</file>
<file alias="pathitem.qml">content/pathitem.qml</file>
<file alias="pathitemgallery.qml">content/pathitemgallery.qml</file>
<file alias="pathiteminteract.qml">content/pathiteminteract.qml</file>
<file alias="item1.qml">content/item1.qml</file>
<file alias="item2.qml">content/item2.qml</file>
<file alias="item3.qml">content/item3.qml</file>
<file alias="item4.qml">content/item4.qml</file>
<file alias="item5.qml">content/item5.qml</file>
<file alias="item6.qml">content/item6.qml</file>
<file alias="item7.qml">content/item7.qml</file>
<file alias="item8.qml">content/item8.qml</file>
<file alias="item9.qml">content/item9.qml</file>
<file alias="item10.qml">content/item10.qml</file>
<file alias="item11.qml">content/item11.qml</file>
<file alias="item12.qml">content/item12.qml</file>
</qresource>
</RCC>