diff options
author | Axel Waggershauser <awagger@gmail.com> | 2013-03-15 00:42:15 +0100 |
---|---|---|
committer | The Qt Project <gerrit-noreply@qt-project.org> | 2013-03-16 20:22:50 +0100 |
commit | b11317a64339f5a4bcffc8234ecaf15c7fb416f2 (patch) | |
tree | f81e40ee49f5109b4100048d131d5bb922b448aa /examples/widgets/doc/src/echoplugin.qdoc | |
parent | 72367a94a750355eb748793ce8c365373a332c9c (diff) |
Whitespace cleanup: remove trailing whitespace
Remove all trailing whitespace from the following list of files:
*.cpp *.h *.conf *.qdoc *.pro *.pri *.mm *.rc *.pl *.qps *.xpm *.txt *README
excluding 3rdparty, test-data and auto generated code.
Note A): the only non 3rdparty c++-files that still
have trailing whitespace after this change are:
* src/corelib/codecs/cp949codetbl_p.h
* src/corelib/codecs/qjpunicode.cpp
* src/corelib/codecs/qbig5codec.cpp
* src/corelib/xml/qxmlstream_p.h
* src/tools/qdoc/qmlparser/qqmljsgrammar.cpp
* src/tools/uic/ui4.cpp
* tests/auto/other/qtokenautomaton/tokenizers/*
* tests/benchmarks/corelib/tools/qstring/data.cpp
* util/lexgen/tokenizer.cpp
Note B): in about 30 files some overlapping 'leading tab' and
'TAB character in non-leading whitespace' issues have been fixed
to make the sanity bot happy. Plus some general ws-fixes here
and there as asked for during review.
Change-Id: Ia713113c34d82442d6ce4d93d8b1cf545075d11d
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
Diffstat (limited to 'examples/widgets/doc/src/echoplugin.qdoc')
-rw-r--r-- | examples/widgets/doc/src/echoplugin.qdoc | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/examples/widgets/doc/src/echoplugin.qdoc b/examples/widgets/doc/src/echoplugin.qdoc index eae5269d62..7b7aa9b868 100644 --- a/examples/widgets/doc/src/echoplugin.qdoc +++ b/examples/widgets/doc/src/echoplugin.qdoc @@ -46,7 +46,7 @@ System}{meta-object system}. The plugin \l{How to Create Qt Plugins}{overview document} gives a high-level introduction to plugins. - + We have implemented a plugin, the \c EchoPlugin, which implements the \c EchoInterface. The interface consists of \c echo(), which takes a QString as argument. The \c EchoPlugin returns the string @@ -68,8 +68,8 @@ \snippet tools/echoplugin/echowindow/echowindow.h 0 We load the plugin in \c loadPlugin() and cast it to \c - EchoInterface. When the user clicks the \c button we take the - text in \c lineEdit and call the interface's \c echo() with it. + EchoInterface. When the user clicks the \c button we take the + text in \c lineEdit and call the interface's \c echo() with it. \section1 EchoWindow Class Implementation @@ -136,15 +136,15 @@ System}{Qt's meta object system} aware of the interface. We do this so that it will be possible to identify plugins that implements the interface at run-time. The second argument is a - string that must identify the interface in a unique way. + string that must identify the interface in a unique way. \section1 EchoPlugin Class Definition We inherit both QObject and \c EchoInterface to make this class a plugin. The Q_INTERFACES macro tells Qt which interfaces the class - implements. In our case we only implement the \c EchoInterface. - If a class implements more than one interface, they are given as + implements. In our case we only implement the \c EchoInterface. + If a class implements more than one interface, they are given as a comma separated list. The Q_PLUGIN_METADATA macro is included next to the Q_OBJECT macro. It contains the plugins IID and a filename pointing to a json file containing the metadata for the plugin. @@ -158,7 +158,7 @@ \snippet tools/echoplugin/plugin/echoplugin.cpp 0 - We simply return the functions parameter. + We simply return the functions parameter. \section1 The \c main() function @@ -169,7 +169,7 @@ \section1 The Profiles When creating plugins the profiles need to be adjusted. - We show here what changes need to be done. + We show here what changes need to be done. The profile in the echoplugin directory uses the \c subdirs template and simply includes includes to directories in which @@ -196,7 +196,7 @@ You can find an overview of the macros needed to create plugins \l{Macros for Defining Plugins}{here}. - + We give an example of a plugin that extend Qt in the \l{Style Plugin Example}{style plugin} example. The \l{Plug & Paint Example}{plug and paint} example shows how to create static |