|  | Home · All Classes · Main Classes · Grouped Classes · Modules · Functions |

# Plug & Paint Basic Tools Example

Files:

- tools/plugandpaintplugins/basictools/basictoolsplugin.cpp
- tools/plugandpaintplugins/basictools/basictoolsplugin.h

The Basic Tools example is a plugin for the Plug & Paint example. It provides a set of basic brushes, shapes, and filters. Through the Basic Tools example, we will review the four steps involved in writing a Qt plugin:

1. Declare a plugin class.
2. Implement the interfaces provided by the plugin.
3. Export the plugin using the `Q_EXPORT_PLUGIN()` macro.
4. Build the plugin using an adequate `.pro` file.

## Declaration of the Plugin Class

        #include <plugandpaint/interfaces.h>

        class BasicToolsPlugin : public QObject,
                                 public BrushInterface,
                                 public ShapeInterface,
                                 public FilterInterface
        {
            Q_OBJECT
            Q_INTERFACES(BrushInterface ShapeInterface FilterInterface)

We start by including `interfaces.h`, which defines the plugin interfaces for the Plug & Paint application. For the `#include` to work, we need to add an `INCLUDEPATH` entry to the `.pro` file with the path to Qt's `examples/tools` directory.

The `BasicToolsPlugin` class is a QObject subclass that implements the `BrushInterface`, the `ShapeInterface`, and the `FilterInterface`. This is done through multiple inheritance. The `Q_INTERFACES()` macro is necessary to tell moc, Qt's meta-object compiler, that the base classes are plugin interfaces. Without the `Q_INTERFACES()` macro, we couldn't use qobject_cast() in the Plug & Paint application to detect interfaces.

        public:
            // BrushInterface
            QStringList brushes() const;
            QRect mousePress(const QString &brush, QPainter &painter,
                             const QPoint &pos);
            QRect mouseMove(const QString &brush, QPainter &painter,
                            const QPoint &oldPos, const QPoint &newPos);
            QRect mouseRelease(const QString &brush, QPainter &painter,
                               const QPoint &pos);

            // ShapeInterface
            QStringList shapes() const;
            QPainterPath generateShape(const QString &shape, QWidget *parent);

            // FilterInterface
            QStringList filters() const;
            QImage filterImage(const QString &filter, const QImage &image,
                               QWidget *parent);
        };

In the `public` section of the class, we declare all the functions from the three interfaces.

## Implementation of the Brush Interface

Let's now review the implementation of the `BasicToolsPlugin` member functions inherited from `BrushInterface`.

        QStringList BasicToolsPlugin::brushes() const
        {
            return QStringList() << tr("Pencil") << tr("Air Brush")
                                 << tr("Random Letters");
        }

The `brushes()` function returns a list of brushes provided by this plugin. We provide three brushes: Pencil, Air Brush, and Random Letters.

        QRect BasicToolsPlugin::mousePress(const QString &brush, QPainter &painter,
                                           const QPoint &pos)
        {
            return mouseMove(brush, painter, pos, pos);
        }

On a mouse press event, we just call `mouseMove()` to draw the spot where the event occurred.

        QRect BasicToolsPlugin::mouseMove(const QString &brush, QPainter &painter,
                                          const QPoint &oldPos, const QPoint &newPos)
        {
            painter.save();

            int rad = painter.pen().width() / 2;
            QRect boundingRect = QRect(oldPos, newPos).normalized()
                                                      .adjusted(-rad, -rad, +rad, +rad);
            QColor color = painter.pen().color();
            int thickness = painter.pen().width();
            QColor transparentColor(color.red(), color.green(), color.blue(), 0);

In `mouseMove()`, we start by saving the state of the QPainter and we compute a few variables that we'll need later.

            if (brush == tr("Pencil")) {
                painter.drawLine(oldPos, newPos);
            } else if (brush == tr("Air Brush")) {
                int numSteps = 2 + (newPos - oldPos).manhattanLength() / 2;

                painter.setBrush(QBrush(color, Qt::Dense6Pattern));
                painter.setPen(Qt::NoPen);

                for (int i = 0; i < numSteps; ++i) {
                    int x = oldPos.x() + i * (newPos.x() - oldPos.x()) / (numSteps - 1);
                    int y = oldPos.y() + i * (newPos.y() - oldPos.y()) / (numSteps - 1);

                    painter.drawEllipse(x - (thickness / 2), y - (thickness / 2),
                                        thickness, thickness);
                }
            } else if (brush == tr("Random Letters")) {
                QChar ch('A' + (rand() % 26));

                QFont biggerFont = painter.font();
                biggerFont.setBold(true);
                biggerFont.setPointSize(biggerFont.pointSize() + thickness);
                painter.setFont(biggerFont);

                painter.drawText(newPos, QString(ch));

                QFontMetrics metrics(painter.font());
                boundingRect = metrics.boundingRect(ch);
                boundingRect.translate(newPos);
                boundingRect.adjust(-10, -10, +10, +10);
            }
            painter.restore();
            return boundingRect;
        }

Then comes the brush-dependent part of the code:

- If the brush is Pencil, we just call QPainter::drawLine() with the current QPen.
- If the brush is Air Brush, we start by setting the painter's QBrush to Qt::Dense6Pattern to obtain a dotted pattern. Then we draw a circle filled with that QBrush several times, resulting in a thick line.
- If the brush is Random Letters, we draw a random letter at the new cursor position. Most of the code is for setting the font to be bold and larger than the default font and for computing an appropriate bounding rect.

At the end, we restore the painter state to what it was upon entering the function and we return the bounding rectangle.

        QRect BasicToolsPlugin::mouseRelease(const QString & /* brush */,
                                             QPainter & /* painter */,
                                             const QPoint & /* pos */)
        {
            return QRect(0, 0, 0, 0);
        }

When the user releases the mouse, we do nothing and return an empty QRect.

## Implementation of the Shape Interface

        QStringList BasicToolsPlugin::shapes() const
        {
            return QStringList() << tr("Circle") << tr("Star") << tr("Text...");
        }

The plugin provides three shapes: Circle, Star, and Text.... The three dots after Text are there because the shape pops up a dialog asking for more information. We know that the shape names will end up in a menu, so we include the three dots in the shape name.

A cleaner but more complicated design would have been to distinguish between the internal shape name and the name used in the user interface.

        QPainterPath BasicToolsPlugin::generateShape(const QString &shape,
                                                     QWidget *parent)
        {
            QPainterPath path;

            if (shape == tr("Circle")) {
                path.addEllipse(0, 0, 50, 50);
            } else if (shape == tr("Star")) {
                path.moveTo(90, 50);
                for (int i = 1; i < 5; ++i) {
                    path.lineTo(50 + 40 * cos(0.8 * i * Pi),
                                50 + 40 * sin(0.8 * i * Pi));
                }
                path.closeSubpath();
            } else if (shape == tr("Text...")) {
                QString text = QInputDialog::getText(parent, tr("Text Shape"),
                                                     tr("Enter text:"),
                                                     QLineEdit::Normal, tr("Qt"));
                if (!text.isEmpty()) {
                    QFont timesFont("Times", 50);
                    timesFont.setStyleStrategy(QFont::ForceOutline);
                    path.addText(0, 0, timesFont, text);
                }
            }

            return path;
        }

The `generateShape()` creates a QPainterPath for the specified shape. If the shape is Text, we pop up a QInputDialog to let the user enter some text.

## Implementation of the Filter Interface

        QStringList BasicToolsPlugin::filters() const
        {
            return QStringList() << tr("Invert Pixels") << tr("Swap RGB")
                                 << tr("Grayscale");
        }

The plugin provides three filters: Invert Pixels, Swap RGB, and Grayscale.

        QImage BasicToolsPlugin::filterImage(const QString &filter, const QImage &image,
                                             QWidget * /* parent */)
        {
            QImage result = image.convertToFormat(QImage::Format_RGB32);

            if (filter == tr("Invert Pixels")) {
                result.invertPixels();
            } else if (filter == tr("Swap RGB")) {
                result = result.rgbSwapped();
            } else if (filter == tr("Grayscale")) {
                for (int y = 0; y < result.height(); ++y) {
                    for (int x = 0; x < result.width(); ++x) {
                        int pixel = result.pixel(x, y);
                        int gray = qGray(pixel);
                        int alpha = qAlpha(pixel);
                        result.setPixel(x, y, qRgba(gray, gray, gray, alpha));
                    }
                }
            }
            return result;
        }

The `filterImage()` function takes a filter name and a QImage as parameters and returns an altered QImage. The first thing we do is to convert the image to a 32-bit RGB format, to ensure that the algorithms will work as expected. For example, QImage::invertPixels(), which is used to implement the Invert Pixels filter, gives counterintuitive results for 8-bit images, because they invert the indices into the color table instead of inverting the color table's entries.

## Exporting the Plugin

Whereas applications have a `main()` function as their entry point, plugins need to contain exactly one occurrence of the `Q_EXPORT_PLUGIN2()` macro to specify which class provides the plugin:

        Q_EXPORT_PLUGIN2(pnp_basictools, BasicToolsPlugin)

This line may appear in any `.cpp` file that is part of the plugin's source code.

## The .pro File

Here's the project file for building the Basic Tools plugin:

        TEMPLATE      = lib
        CONFIG       += plugin
        INCLUDEPATH  += ../..
        HEADERS       = basictoolsplugin.h
        SOURCES       = basictoolsplugin.cpp
        TARGET        = pnp_basictools
        DESTDIR       = ../../plugandpaint/plugins

        contains(TEMPLATE,lib) {
           CONFIG(debug, debug|release) {
              unix:TARGET = $$member(TARGET, 0)_debug
              else:TARGET = $$member(TARGET, 0)d
           }
        }

The `.pro` file differs from typical `.pro` files in many respects. First, it starts with a `TEMPLATE` entry specifying `lib`. (The default template is `app`.) It also adds `plugin` to the `CONFIG` variable. This is necessary on some platforms to avoid generating symbolic links with version numbers in the file name, which is appropriate for most dynamic libraries but not for plugins.

The `INCLUDEPATH` variable sets the search paths for global headers (i.e., header files included using `#include <...>`). We add Qt's `examples/tools` directory (strictly speaking, `examples/tools/plugandpaintplugins/basictools/../..`) to the list, so that we can include `<plugandpaint/interfaces.h>`.

The `TARGET` variable specifies which name we want to give the target library. We use `pnp_` as the prefix to show that the plugin is designed to work with Plug & Paint. On Unix, `lib` is also prepended to that name. On all platforms, a platform-specific suffix is appended (e.g., `.dll` on Windows).

Finally, the `DESTDIR` variable specifies where we want to install the plugin. We put it in Plug & Paint's `plugins` subdirectory, since that's where the application looks for plugins.