0efe79f80d
We were already using the 'native' nomenclature when referring to these kinds of APIs, e.g. when talking about native handles, or the existing QPlatformNativeInterface on a QPA level. Using 'native' for the user facing APIs also distinguishes them from the 'platform' backend layer in QPA and elsewhere. Change-Id: I0f3273265904f0f19c0b6d62471f8820d3c3232e Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io> Reviewed-by: Lars Knoll <lars.knoll@qt.io> |
||
---|---|---|
.. | ||
aggregate | ||
corelib | ||
dbus | ||
embedded | ||
gui | ||
network | ||
opengl | ||
qmake | ||
qpa | ||
qtconcurrent | ||
qtestlib | ||
sql | ||
vulkan | ||
widgets | ||
xml | ||
CMakeLists.txt | ||
examples.pro | ||
README |
Qt is supplied with a number of example applications that have been written to provide developers with examples of the Qt API in use, highlight good programming practice, and showcase features found in each of Qt's core technologies. Documentation for examples can be found in the Examples section of the Qt documentation.