Introduce a CurveRendering backend for text

This moves the internals of the curve renderer out from
Qt Quick Shapes and into a more centralized location
in Qt Quick, so that we can use the same code to create
a new text backend for rendering large scale text without
artifacts.

Change-Id: I3f7e6f7961c1bbe230fcb531c0ca028e038c1afd
Reviewed-by: Eirik Aavitsland <eirik.aavitsland@qt.io>

1 files changed, 8 insertions, 0 deletions

diff --git a/src/quick/items/qquicktextinput.cpp b/src/quick/items/qquicktextinput.cpp
index 2cce5378fb..f2042c70bb 100644
--- a/src/quick/items/qquicktextinput.cpp
+++ b/src/quick/items/qquicktextinput.cpp
@@ -136,12 +136,20 @@ void QQuickTextInput::setText(const QString &s)
 
     \value TextInput.QtRendering     Text is rendered using a scalable distance field for each glyph.
     \value TextInput.NativeRendering Text is rendered using a platform-specific technique.
+    \value TextInput.CurveRendering  Text is rendered using a curve rasterizer running directly on
+                                     the graphics hardware. (Introduced in Qt 6.7.0.)
 
     Select \c TextInput.NativeRendering if you prefer text to look native on the target platform and do
     not require advanced features such as transformation of the text. Using such features in
     combination with the NativeRendering render type will lend poor and sometimes pixelated
     results.
 
+    Both \c TextInput.QtRendering and \c TextInput.CurveRendering are hardware-accelerated techniques.
+    \c QtRendering is the faster of the two, but uses more memory and will exhibit rendering
+    artifacts at large sizes. \c CurveRendering should be considered as an alternative in cases
+    where \c QtRendering does not give good visual results or where reducing graphics memory
+    consumption is a priority.
+
     The default rendering type is determined by \l QQuickWindow::textRenderType().
 */
 QQuickTextInput::RenderType QQuickTextInput::renderType() const