EchoWindow Class Implementation
We start with a look at the constructor:
EchoWindow::EchoWindow()
{
createGUI();
setLayout(layout);
setWindowTitle("Echo Plugin Example");
if (!loadPlugin()) {
QMessageBox::information(this, "Error", "Could not load the plugin");
lineEdit->setEnabled(false);
button->setEnabled(false);
}
}
We create the widgets and set a title for the window. We then load the plugin. loadPlugin() returns false if the plugin could not be loaded, in which case we disable the widgets. If you wish a more detailed error message, you can use errorString(); we will look more closely at QPluginLoader later.
Here is the implementation of sendEcho():
void EchoWindow::sendEcho()
{
QString text = echoInterface->echo(lineEdit->text());
label->setText(text);
}
This slot is called when the user pushes button or presses enter in lineEdit. We call echo() of the echo interface. In our example this is the EchoPlugin, but it could be any plugin that inherit the EchoInterface. We take the QString returned from echo() and display it in the label.
Here is the implementation of createGUI():
void EchoWindow::createGUI()
{
lineEdit = new QLineEdit;
label = new QLabel;
label->setFrameStyle(QFrame::Box | QFrame::Plain);
button = new QPushButton(tr("Send Message"));
connect(lineEdit, SIGNAL(editingFinished()),
this, SLOT(sendEcho()));
connect(button, SIGNAL(clicked()),
this, SLOT(sendEcho()));
layout = new QGridLayout;
layout->addWidget(new QLabel(tr("Message:")), 0, 0);
layout->addWidget(lineEdit, 0, 1);
layout->addWidget(new QLabel(tr("Answer:")), 1, 0);
layout->addWidget(label, 1, 1);
layout->addWidget(button, 2, 1, Qt::AlignRight);
layout->setSizeConstraint(QLayout::SetFixedSize);
}
We create the widgets and lay them out in a grid layout. We connect the label and line edit to our sendEcho() slot.
Here is the loadPlugin() function:
bool EchoWindow::loadPlugin()
{
QDir pluginsDir(qApp->applicationDirPath());
#if defined(Q_OS_WIN)
if (pluginsDir.dirName().toLower() == "debug" || pluginsDir.dirName().toLower() == "release")
pluginsDir.cdUp();
#elif defined(Q_OS_MAC)
if (pluginsDir.dirName() == "MacOS") {
pluginsDir.cdUp();
pluginsDir.cdUp();
pluginsDir.cdUp();
}
#endif
pluginsDir.cd("plugins");
foreach (QString fileName, pluginsDir.entryList(QDir::Files)) {
QPluginLoader pluginLoader(pluginsDir.absoluteFilePath(fileName));
QObject *plugin = pluginLoader.instance();
if (plugin) {
echoInterface = qobject_cast<EchoInterface *>(plugin);
if (echoInterface)
return true;
}
}
return false;
}
Access to plugins at run-time is provided by QPluginLoader. You supply it with the filename of the shared library the plugin is stored in and call instance(), which loads and returns the root component of the plugin (i.e., it resolves the type of the plugin and creates a QObject instance of it). If the plugin was not successfully loaded, it will be null, so we return false. If it was loaded correctly, we can cast the plugin to our EchoInterface and return true. In the case that the plugin loaded does not implement the EchoInterface, instance() will return null, but this cannot happen in our example. Notice that the location of the plugin is not the same for all platforms.
EchoInterface Class Definition
The EchoInterface defines the functions that the plugin will provide. An interface is a class that only consists of pure virtual functions. If non virtual functions were present in the class you would get misleading compile errors in the moc files.
class EchoInterface
{
public:
virtual ~EchoInterface() {}
virtual QString echo(const QString &message) = 0;
};
Q_DECLARE_INTERFACE(EchoInterface,
"com.trolltech.Plugin.EchoInterface/1.0");
We declare echo(). In our EchoPlugin we use this method to return, or echo, message.
We use the Q_DECLARE_INTERFACE macro to let 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.
EchoPlugin Class Definition
We inherit both QObject and 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 EchoInterface. If a class implements more than one interface, they are given as a comma separated list.
class EchoPlugin : public QObject, EchoInterface
{
Q_OBJECT
Q_INTERFACES(EchoInterface)
public:
QString echo(const QString &message);
};
EchoPlugin Class Implementation
Here is the implementation of echo():
QString EchoPlugin::echo(const QString &message)
{
return message;
}
We simply return the functions parameter.
Q_EXPORT_PLUGIN2(echoplugin, EchoPlugin);
We use the Q_EXPORT_PLUGIN2 macro to let Qt know that the EchoPlugin class is a plugin. The first parameter is the name of the plugin; it is usual to give the plugin and the library file it is stored in the same name.
The main() function
int main(int argv, char *args[])
{
QApplication app(argv, args);
EchoWindow window;
window.show();
return app.exec();
}
We create an EchoWindow and display it as a top-level window.
The Profiles
When creating plugins the profiles need to be adjusted. We show here what changes need to be done.
The profile in the echoplugin directory uses the subdirs template and simply includes includes to directories in which the echo window and echo plugin lives:
TEMPLATE = subdirs
SUBDIRS = echowindow \
plugin
The profile for the echo window does not need any plugin specific settings. We move on to the plugin profile:
TEMPLATE = lib
CONFIG += plugin
INCLUDEPATH += ../echowindow
HEADERS = echoplugin.h
SOURCES = echoplugin.cpp
TARGET = $$qtLibraryTarget(echoplugin)
DESTDIR = ../plugins
We need to set the TEMPLATE as we now want to make a library instead of an executable. We also need to tell qmake that we are creating a plugin. The EchoInterface that the plugin implements lives in the echowindow directory, so we need to add that directory to the include path. We set the TARGET of the project, which is the name of the library file in which the plugin will be stored; qmake appends the appropriate file extension depending on the platform. By convention the target should have the same name as the plugin (set with Q_EXPORT_PLUGIN2)
Further reading and examples
You can find an overview of the macros needed to create plugins here.
We give an example of a plugin that extend Qt in the style plugin example. The plug and paint example shows how to create static plugins.
