summaryrefslogtreecommitdiffstats
path: root/examples/designer/doc/src/worldtimeclockplugin.qdoc
diff options
context:
space:
mode:
Diffstat (limited to 'examples/designer/doc/src/worldtimeclockplugin.qdoc')
-rw-r--r--examples/designer/doc/src/worldtimeclockplugin.qdoc32
1 files changed, 12 insertions, 20 deletions
diff --git a/examples/designer/doc/src/worldtimeclockplugin.qdoc b/examples/designer/doc/src/worldtimeclockplugin.qdoc
index bc45a751a..917ab8bda 100644
--- a/examples/designer/doc/src/worldtimeclockplugin.qdoc
+++ b/examples/designer/doc/src/worldtimeclockplugin.qdoc
@@ -145,26 +145,18 @@
\snippet worldtimeclockplugin/worldtimeclockplugin.pro 0
\snippet worldtimeclockplugin/worldtimeclockplugin.pro 1
- The \c TEMPLATE variable's value make \c qmake create the custom
- widget as a library. The \c CONFIG variable contains two values,
- \c designer and \c plugin:
-
- \list
- \li \c designer: Since custom widgets plugins rely on components
- supplied with \QD, this value ensures that our plugin links against
- \QD's library (\c libQtDesigner.so).
-
- \li \c plugin: We also need to ensure that \c qmake considers the
- custom widget a \e plugin library.
- \endlist
-
- When Qt is configured to build in both debug and release modes,
- \QD will be built in release mode. When this occurs, it is
- necessary to ensure that plugins are also built in release
- mode. For that reason you might have to add a \c release value to
- your \c CONFIG variable. Otherwise, if a plugin is built in a mode
- that is incompatible with \QD, it won't be loaded and
- installed.
+ The \c TEMPLATE variable's value in conjunction with the keyword
+ \c plugin in the \c CONFIG variable make \c qmake create the custom
+ widget as a plugin library.
+
+ The \c QT variable contains the keyword \c uiplugin. This plugin type
+ provides a factory function for custom widget creation by implementing
+ the abstract interfaces QDesignerCustomWidgetInterface or
+ QDesignerCustomWidgetCollectionInterface, suitable for use with
+ QUiLoader. It does not have a dependency on the \QD libraries.
+ Plugins accessing other interfaces of \QD to implement container extensions
+ or other \QD specific functionality follow different rules and are covered
+ by other examples.
The header and source files for the widget are declared in the
usual way, and in addition we provide an implementation of the