Drop "Example" from the example's title, add SQL instead, and add it to the Input/Output category of examples. It's a documented example, does something meaningful, and looks reasonable. Having one SQL example categorised so that it's easy to see that Qt includes that functionality seems like a good idea. The other examples are mostly small API examples that are still good to have as fully-functional apps rather than just snippets. Pick-to: 6.5 Change-Id: Ib960f38db39c791f7ff5a2b9bf3157ee32b362ec Reviewed-by: Andreas Eliasson <andreas.eliasson@qt.io> |
||
|---|---|---|
| .. | ||
| aggregate | ||
| corelib | ||
| dbus | ||
| embedded | ||
| gui | ||
| network | ||
| opengl | ||
| qmake | ||
| qpa | ||
| qtconcurrent | ||
| qtestlib | ||
| sql | ||
| vulkan | ||
| widgets | ||
| xml | ||
| CMakeLists.txt | ||
| README | ||
| 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.