Difference between revisions of "Development/Tutorials/Using KActions"

Jump to: navigation, search
(12 intermediate revisions by 7 users not shown)
Line 1: Line 1:
{{Template:I18n/Language Navigation Bar|Development/Tutorials/Using_KActions}}
 
  
 
{{TutorialBrowser|
 
{{TutorialBrowser|
Line 27: Line 26:
  
 
===main.cpp===
 
===main.cpp===
<code cppqt>
+
<syntaxhighlight lang="cpp-qt">
 
#include <KApplication>
 
#include <KApplication>
 
#include <KAboutData>
 
#include <KAboutData>
Line 48: Line 47:
 
   return app.exec();
 
   return app.exec();
 
}
 
}
</code>
+
</syntaxhighlight>
 
This time, very little has changed in <tt>main.cpp</tt>, only the KAboutData constructor has been updated to show that we are now on tutorial 3.
 
This time, very little has changed in <tt>main.cpp</tt>, only the KAboutData constructor has been updated to show that we are now on tutorial 3.
  
 
===mainwindow.h===
 
===mainwindow.h===
<code cppqt>
+
<syntaxhighlight lang="cpp-qt">
 
#ifndef MAINWINDOW_H
 
#ifndef MAINWINDOW_H
 
#define MAINWINDOW_H
 
#define MAINWINDOW_H
Line 70: Line 69:
  
 
#endif
 
#endif
</code>
+
</syntaxhighlight>
 
Only a function <tt>void setupActions()</tt> has been added which will do all the work setting up the KActions.
 
Only a function <tt>void setupActions()</tt> has been added which will do all the work setting up the KActions.
  
 
===mainwindow.cpp===
 
===mainwindow.cpp===
<code cppqt>
+
<syntaxhighlight lang="cpp-qt">
 
#include "mainwindow.h"
 
#include "mainwindow.h"
  
Line 95: Line 94:
 
{
 
{
 
   KAction* clearAction = new KAction(this);
 
   KAction* clearAction = new KAction(this);
   clearAction->setText(i18n("Clear"));
+
   clearAction->setText(i18n("&Clear"));
 
   clearAction->setIcon(KIcon("document-new"));
 
   clearAction->setIcon(KIcon("document-new"));
 
   clearAction->setShortcut(Qt::CTRL + Qt::Key_W);
 
   clearAction->setShortcut(Qt::CTRL + Qt::Key_W);
Line 105: Line 104:
 
                         actionCollection());
 
                         actionCollection());
  
   setupGUI();
+
   setupGUI(Default, "tutorial3ui.rc");
 
}
 
}
</code>
+
</syntaxhighlight>
  
 
==Explanation==
 
==Explanation==
Line 114: Line 113:
 
===Creating the KAction object===
 
===Creating the KAction object===
 
The KAction is built up in a number of steps. The first is including the <tt>KAction</tt> library and then creating the KAction:
 
The KAction is built up in a number of steps. The first is including the <tt>KAction</tt> library and then creating the KAction:
<code cppqt>
+
<syntaxhighlight lang="cpp-qt">
 
#include <KAction>
 
#include <KAction>
 
...
 
...
 
KAction* clearAction = new KAction(this);
 
KAction* clearAction = new KAction(this);
</code>
+
</syntaxhighlight>
 
This creates a new KAction called <tt>clearAction</tt>.
 
This creates a new KAction called <tt>clearAction</tt>.
  
 
===Setting KAction Properties===
 
===Setting KAction Properties===
 
====Text====
 
====Text====
Now we have our KAction object, we can start setting its properties. The following code sets the text that will be displayed in the menu and under the <tt>KAction</tt>'s icon in the toolbar.
+
Now that we have our KAction object, we can start setting its properties. The following code sets the text that will be displayed in the menu and under the <tt>KAction</tt>'s icon in the toolbar.
<code cppqt>clearAction->setText(i18n("Clear"));</code>
+
<syntaxhighlight lang="cpp-qt">
Note that the text is passed through the i18n() function; this is necessary for the UI to be translatable (more information on this can be found in the [[Development/Tutorials/Localization/i18n|i18n tutorial]]).
+
clearAction->setText(i18n("&Clear"));
 +
</syntaxhighlight>
 +
Note that the text is passed through the <tt>i18n()</tt> function; this is necessary for the UI to be translatable (more information on this can be found in the [[Development/Tutorials/Localization/i18n|i18n tutorial]]).
 +
 
 +
The text of the action should contain a <tt>&</tt> because that makes it easier to translate in non-latin1 languages. In Japanese, the translation might be <tt>ソース(&S)</tt> and without the <tt>&</tt> in the english text the translators cannot know if they have to add a <tt>&</tt> or not.
  
 
====Icon====
 
====Icon====
If the action is going to be displayed in a toolbar, it's nice to have an icon depicting the action. The following code sets the icon to the standard KDE <tt>document-new</tt> icon through the use of the <tt>setIcon()</tt> function:
+
If the action is going to be displayed in a toolbar, it is nice to have an icon depicting the action. The following code sets the icon to the standard KDE <tt>document-new</tt> icon through the use of the <tt>setIcon()</tt> function:
<code cppqt>clearAction->setIcon(KIcon("document-new"));</code>
+
<syntaxhighlight lang="cpp-qt">
 +
clearAction->setIcon(KIcon("document-new"));
 +
</syntaxhighlight>
  
 
====Keyboard Shortcut====
 
====Keyboard Shortcut====
 
Setting a keyboard shortcut to perform our action is equally simple:
 
Setting a keyboard shortcut to perform our action is equally simple:
<code cppqt>clearAction->setShortcut(Qt::CTRL + Qt::Key_W);</code>
+
<syntaxhighlight lang="cpp-qt">
 +
clearAction->setShortcut(Qt::CTRL + Qt::Key_W);
 +
</syntaxhighlight>
 
This associates Ctrl+W with the KAction.
 
This associates Ctrl+W with the KAction.
  
 
===Adding to the Collection===
 
===Adding to the Collection===
 
In order for the action to be accessed by the XMLGUI framework (explained in depth later) it must be added to the application's ''action collection''. The action collection is accessed via the <tt>actionCollection()</tt> function like this:  
 
In order for the action to be accessed by the XMLGUI framework (explained in depth later) it must be added to the application's ''action collection''. The action collection is accessed via the <tt>actionCollection()</tt> function like this:  
<code cppqt>
+
<syntaxhighlight lang="cpp-qt">
 
actionCollection()->addAction("clear", clearAction);
 
actionCollection()->addAction("clear", clearAction);
</code>
+
</syntaxhighlight>
 
Here, the <tt>clearAction</tt> KAction is added to the collection and given a name of ''clear''. This name (''clear'') is used by the XMLGUI framework to refer to the action, ergo, it should not be localized, since it is used internally only.
 
Here, the <tt>clearAction</tt> KAction is added to the collection and given a name of ''clear''. This name (''clear'') is used by the XMLGUI framework to refer to the action, ergo, it should not be localized, since it is used internally only.
  
 
====Connecting the action====
 
====Connecting the action====
 
Now that the action is fully set up, it needs to be connected to something useful. In this case (because we want to clear the text area), we connect our action to the <tt>clear()</tt> action belonging to a KTextEdit (which, unsurprisingly, clears the KTextEdit)
 
Now that the action is fully set up, it needs to be connected to something useful. In this case (because we want to clear the text area), we connect our action to the <tt>clear()</tt> action belonging to a KTextEdit (which, unsurprisingly, clears the KTextEdit)
<code cppqt>
+
<syntaxhighlight lang="cpp-qt">
 
connect( clearAction, SIGNAL( triggered(bool) ),  
 
connect( clearAction, SIGNAL( triggered(bool) ),  
 
         textArea, SLOT( clear() ) );
 
         textArea, SLOT( clear() ) );
</code>
+
</syntaxhighlight>
 
This is the same as it would be done in Qt with a {{qt|QAction}}.
 
This is the same as it would be done in Qt with a {{qt|QAction}}.
  
Line 156: Line 163:
  
 
They are very simple to use. Once the library has been included (<tt>#include <KStandardAction></tt>), simply supply it with what you want the function to do and which KActionCollection to add it to. For example:
 
They are very simple to use. Once the library has been included (<tt>#include <KStandardAction></tt>), simply supply it with what you want the function to do and which KActionCollection to add it to. For example:
<code cppqt>KStandardAction::quit(kapp, SLOT(quit()), actionCollection());</code>
+
<syntaxhighlight lang="cpp-qt">
 +
KStandardAction::quit(kapp, SLOT(quit()), actionCollection());
 +
</syntaxhighlight>
 
This creates a KAction with the correct icon, text and shortcut and even adds it to the File menu.
 
This creates a KAction with the correct icon, text and shortcut and even adds it to the File menu.
  
 
==Adding the action to menus and toolbars==
 
==Adding the action to menus and toolbars==
 
At the moment, the new "Clear" action has been created but it hasn't been associated with any menus or toolbars. This is done with a KDE technology called XMLGUI, which does nice things like movable toolbars for you.
 
At the moment, the new "Clear" action has been created but it hasn't been associated with any menus or toolbars. This is done with a KDE technology called XMLGUI, which does nice things like movable toolbars for you.
 
{{note|In a later version of KDE4, XMLGUI, may be replaced with a new framework called liveui. For now, XMLGUI, is the only and correct way to set up the UI.}}
 
  
 
==Defining your own help menu==
 
==Defining your own help menu==
The help menu is god-given, that is why all KDE help menus look the same. If you want to create your own help menu, go [http://websvn.kde.org/trunk/KDE/kdelibs/kdeui/widgets/khelpmenu.h?revision=1002779&view=markup here] and search for the explanation around showAboutApplication().
+
The help menu is god-given, that is why all KDE help menus look the same. If you want to create your own help menu, search for the explanation around showAboutApplication() in kdelibs.
  
 
==XMLGUI==
 
==XMLGUI==
Line 172: Line 179:
  
 
The rule for naming this XML file is <tt>appnameui.rc</tt>, where <tt>appname</tt> is the name you set in {{class|KAboutData}} (in this case, ''tutorial3''). So in our example, the file is called <tt>tutorial3ui.rc</tt>, and is located in the build directory. Where the file will ultimately be placed is handled by CMake.
 
The rule for naming this XML file is <tt>appnameui.rc</tt>, where <tt>appname</tt> is the name you set in {{class|KAboutData}} (in this case, ''tutorial3''). So in our example, the file is called <tt>tutorial3ui.rc</tt>, and is located in the build directory. Where the file will ultimately be placed is handled by CMake.
 
''See also'' [http://developer.kde.org/documentation/library/kdeqt/kde3arch/xmlgui.html developer.kde.org] which still provides valid information for KDE4.
 
  
 
==''appname''ui.rc File==
 
==''appname''ui.rc File==
Line 180: Line 185:
  
 
===tutorial3ui.rc===
 
===tutorial3ui.rc===
<code xml>
+
<syntaxhighlight lang="xml">
 
<?xml version="1.0" encoding="UTF-8"?>
 
<?xml version="1.0" encoding="UTF-8"?>
 
<gui name="tutorial3"
 
<gui name="tutorial3"
Line 201: Line 206:
  
 
</gui>
 
</gui>
</code>
+
</syntaxhighlight>
  
 
The <tt><Toolbar></tt> tag allows you to describe the toolbar, which is the bar across the top of the window normally with icons. Here it is given the unique name ''mainToolBar'' and its user visible name set to ''Main Toolbar'' using the <tt><text></tt> tag. The clear action is added to the toolbar using the <tt><Action></tt> tag, the name parameter in this tag being the string that was passed to the KActionCollection with <tt>addAction()</tt> in <tt>mainwindow.cpp</tt>.
 
The <tt><Toolbar></tt> tag allows you to describe the toolbar, which is the bar across the top of the window normally with icons. Here it is given the unique name ''mainToolBar'' and its user visible name set to ''Main Toolbar'' using the <tt><text></tt> tag. The clear action is added to the toolbar using the <tt><Action></tt> tag, the name parameter in this tag being the string that was passed to the KActionCollection with <tt>addAction()</tt> in <tt>mainwindow.cpp</tt>.
Line 207: Line 212:
 
Besides having the action in the toolbar, it can also be added to the menubar. Here the action is being added to the ''File'' menu of the <tt>MenuBar</tt> the same way it was added to the toolbar.
 
Besides having the action in the toolbar, it can also be added to the menubar. Here the action is being added to the ''File'' menu of the <tt>MenuBar</tt> the same way it was added to the toolbar.
  
Change the 'version' attribute of the <tt><nowiki><gui></nowiki></tt> tag if you changed .rc file since the last install to force a system cache update. Be sure it is an integer, if you use a decimal value, it will not work, but will not notify that it didn't. '''Note:''' The version attribute must be an integer number, i.e. it may not contain dots or other non-digits like an application version number.
+
Change the 'version' attribute of the <tt><nowiki><gui></nowiki></tt> tag if you changed .rc file since the last install to force a system cache update. Be sure it is an integer, if you use a decimal value, it will not work, but will not notify that it didn't. '
 +
 
 +
{{Warning|The version attribute must be an integer number, if you type in version<nowiki>=</nowiki>"1.2" it will dispose of your kittens  (but not eat them).}}
  
 
Some notes on the interaction between code and the .rc file: Menus appear automatically and should have a <tt><nowiki><text/></nowiki></tt> child tag unless they refer to standard menus. Actions need to be created manually and inserted into the actionCollection() using the name in the .rc file. Actions can be hidden or disabled, whereas menus can't.
 
Some notes on the interaction between code and the .rc file: Menus appear automatically and should have a <tt><nowiki><text/></nowiki></tt> child tag unless they refer to standard menus. Actions need to be created manually and inserted into the actionCollection() using the name in the .rc file. Actions can be hidden or disabled, whereas menus can't.
Line 214: Line 221:
 
Finally, the <tt>tutorial3ui.rc</tt> needs to go somewhere where KDE can find it (can't just leave it in the source directory!). '''This means the project needs to be installed somewhere.'''
 
Finally, the <tt>tutorial3ui.rc</tt> needs to go somewhere where KDE can find it (can't just leave it in the source directory!). '''This means the project needs to be installed somewhere.'''
 
===CMakeLists.txt===
 
===CMakeLists.txt===
<code cmake>
+
<syntaxhighlight lang="cmake">
 
project(tutorial3)
 
project(tutorial3)
  
Line 232: Line 239:
 
install(FILES tutorial3ui.rc  
 
install(FILES tutorial3ui.rc  
 
         DESTINATION  ${DATA_INSTALL_DIR}/tutorial3)
 
         DESTINATION  ${DATA_INSTALL_DIR}/tutorial3)
</code>
+
</syntaxhighlight>
  
 
This file is almost identical to the one for tutorial2, but with two extra lines at the end that describe where the files are to be installed. Firstly, the <tt>tutorial3</tt> target is installed to the <tt>BIN_INSTALL_DIR</tt> then the <tt>tutorial3ui.rc</tt> file that describes the layout of the user interface is installed to the application's data directory.
 
This file is almost identical to the one for tutorial2, but with two extra lines at the end that describe where the files are to be installed. Firstly, the <tt>tutorial3</tt> target is installed to the <tt>BIN_INSTALL_DIR</tt> then the <tt>tutorial3ui.rc</tt> file that describes the layout of the user interface is installed to the application's data directory.
Line 240: Line 247:
  
 
To tell CMake where to install the program, set the <tt>DCMAKE_INSTALL_PREFIX</tt> switch. You probably just want to install it somewhere local for testing (it's probably a bit silly to go to the effort of installing these tutorials to your KDE directory), so the following might be appropriate:
 
To tell CMake where to install the program, set the <tt>DCMAKE_INSTALL_PREFIX</tt> switch. You probably just want to install it somewhere local for testing (it's probably a bit silly to go to the effort of installing these tutorials to your KDE directory), so the following might be appropriate:
mkdir build && cd build
+
<syntaxhighlight lang="bash">
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME
+
mkdir build && cd build
make install
+
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME
$HOME/bin/tutorial3
+
make install
which will create a KDE-like directory structure in your user's home directory directory and will install the executable to {{path|$HOME/bin/tutorial3}}.
+
$HOME/bin/tutorial3
 +
</syntaxhighlight>
 +
which will create a KDE-like directory structure in your user's home directory and will install the executable to {{path|$HOME/bin/tutorial3}}.
  
 
==Moving On==
 
==Moving On==
 
Now you can move on to [[Development/Tutorials/Saving_and_loading|saving and loading]].
 
Now you can move on to [[Development/Tutorials/Saving_and_loading|saving and loading]].
 +
 +
Or you can learn [[Development/Tutorial/Icons|how to add icons to your application]].
 +
 +
Or you can learn [[Development/Tutorials/Desktop_File|how to place your application in the K-Menu using .desktop files]].
  
 
[[Category:C++]]
 
[[Category:C++]]

Revision as of 16:18, 13 July 2012

How To Use KActions and XMLGUI
Tutorial Series   Beginner Tutorial
Previous   Tutorial 2 - KXmlGuiWindow, Basic XML knowledge
What's Next   Tutorial 4 - Saving and loading
Further Reading   None

Contents

Abstract

This tutorial introduces the concept of actions. Actions are a unified way of supplying the user with ways to interact with your program.

For example, if we wanted to let the user of Tutorial 2 clear the text box by clicking a button in the toolbar, from an option in the File menu or through a keyboard shortcut, it could all be done with one KAction.

Introtokdetutorial3.png

KAction

A KAction is an object which contains all the information about the icon and shortcuts that is associated with a certain action. The action is then connected to a slot which carries out the work of your action.

The Code

main.cpp

#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>
 
#include "mainwindow.h"
 
int main (int argc, char *argv[])
{
  KAboutData aboutData( "tutorial3", "tutorial3",
      ki18n("Tutorial 3"), "1.0",
      ki18n("A simple text area using KAction etc."),
      KAboutData::License_GPL,
      ki18n("Copyright (c) 2007 Developer") );
  KCmdLineArgs::init( argc, argv, &aboutData );
  KApplication app;
 
  MainWindow* window = new MainWindow();
  window->show();
  return app.exec();
}

This time, very little has changed in main.cpp, only the KAboutData constructor has been updated to show that we are now on tutorial 3.

mainwindow.h

#ifndef MAINWINDOW_H
#define MAINWINDOW_H
 
#include <KXmlGuiWindow>
#include <KTextEdit>
 
class MainWindow : public KXmlGuiWindow
{
  public:
    MainWindow(QWidget *parent=0);
 
  private:
    KTextEdit* textArea;
    void setupActions();
};
 
#endif

Only a function void setupActions() has been added which will do all the work setting up the KActions.

mainwindow.cpp

#include "mainwindow.h"
 
#include <KApplication>
#include <KAction>
#include <KLocale>
#include <KActionCollection>
#include <KStandardAction>
 
MainWindow::MainWindow(QWidget *parent)
    : KXmlGuiWindow(parent)
{
  textArea = new KTextEdit;
  setCentralWidget(textArea);
 
  setupActions();
}
 
void MainWindow::setupActions()
{
  KAction* clearAction = new KAction(this);
  clearAction->setText(i18n("&Clear"));
  clearAction->setIcon(KIcon("document-new"));
  clearAction->setShortcut(Qt::CTRL + Qt::Key_W);
  actionCollection()->addAction("clear", clearAction);
  connect(clearAction, SIGNAL(triggered(bool)),
          textArea, SLOT(clear()));
 
  KStandardAction::quit(kapp, SLOT(quit()),
                        actionCollection());
 
  setupGUI(Default, "tutorial3ui.rc");
}

Explanation

This builds upon the KXmlGuiWindow code from Tutorial 2. Most of the changes are to mainwindow.cpp, an important structural change being that the constructor for MainWindow now calls setupActions() instead of setupGUI(). setupActions() is where the new KAction code goes before finally calling setupGUI() itself.

Creating the KAction object

The KAction is built up in a number of steps. The first is including the KAction library and then creating the KAction:

#include <KAction>
...
KAction* clearAction = new KAction(this);

This creates a new KAction called clearAction.

Setting KAction Properties

Text

Now that we have our KAction object, we can start setting its properties. The following code sets the text that will be displayed in the menu and under the KAction's icon in the toolbar.

clearAction->setText(i18n("&Clear"));

Note that the text is passed through the i18n() function; this is necessary for the UI to be translatable (more information on this can be found in the i18n tutorial).

The text of the action should contain a & because that makes it easier to translate in non-latin1 languages. In Japanese, the translation might be ソース(&S) and without the & in the english text the translators cannot know if they have to add a & or not.

Icon

If the action is going to be displayed in a toolbar, it is nice to have an icon depicting the action. The following code sets the icon to the standard KDE document-new icon through the use of the setIcon() function:

clearAction->setIcon(KIcon("document-new"));

Keyboard Shortcut

Setting a keyboard shortcut to perform our action is equally simple:

clearAction->setShortcut(Qt::CTRL + Qt::Key_W);

This associates Ctrl+W with the KAction.

Adding to the Collection

In order for the action to be accessed by the XMLGUI framework (explained in depth later) it must be added to the application's action collection. The action collection is accessed via the actionCollection() function like this:

actionCollection()->addAction("clear", clearAction);

Here, the clearAction KAction is added to the collection and given a name of clear. This name (clear) is used by the XMLGUI framework to refer to the action, ergo, it should not be localized, since it is used internally only.

Connecting the action

Now that the action is fully set up, it needs to be connected to something useful. In this case (because we want to clear the text area), we connect our action to the clear() action belonging to a KTextEdit (which, unsurprisingly, clears the KTextEdit)

connect( clearAction, SIGNAL( triggered(bool) ), 
         textArea, SLOT( clear() ) );

This is the same as it would be done in Qt with a QAction.

KStandardAction

For actions which would likely appear in almost every KDE application such as 'quit', 'save', and 'load' there are pre-created convenience KActions, accessed through KStandardAction.

They are very simple to use. Once the library has been included (#include <KStandardAction>), simply supply it with what you want the function to do and which KActionCollection to add it to. For example:

KStandardAction::quit(kapp, SLOT(quit()), actionCollection());

This creates a KAction with the correct icon, text and shortcut and even adds it to the File menu.

Adding the action to menus and toolbars

At the moment, the new "Clear" action has been created but it hasn't been associated with any menus or toolbars. This is done with a KDE technology called XMLGUI, which does nice things like movable toolbars for you.

Defining your own help menu

The help menu is god-given, that is why all KDE help menus look the same. If you want to create your own help menu, search for the explanation around showAboutApplication() in kdelibs.

XMLGUI

The setupGUI() function in KXmlGuiWindow depends on the XMLGUI system to construct the GUI, which XMLGUI does by parsing an XML file description of the interface.

The rule for naming this XML file is appnameui.rc, where appname is the name you set in KAboutData (in this case, tutorial3). So in our example, the file is called tutorial3ui.rc, and is located in the build directory. Where the file will ultimately be placed is handled by CMake.

appnameui.rc File

Since the description of the UI is defined with XML, the layout must follow strict rules. This tutorial will not go into great depth on this topic, but for more information, see the detailed XMLGUI page (here is an older tutorial: [1]).

tutorial3ui.rc

<?xml version="1.0" encoding="UTF-8"?>
<gui name="tutorial3"
     version="1"
     xmlns="http://www.kde.org/standards/kxmlgui/1.0"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://www.kde.org/standards/kxmlgui/1.0
                         http://www.kde.org/standards/kxmlgui/1.0/kxmlgui.xsd" >
 
  <MenuBar>
    <Menu name="file" >
      <Action name="clear" />
    </Menu>
  </MenuBar>
 
  <ToolBar name="mainToolBar" >
    <text>Main Toolbar</text>
    <Action name="clear" />
  </ToolBar>
 
</gui>

The <Toolbar> tag allows you to describe the toolbar, which is the bar across the top of the window normally with icons. Here it is given the unique name mainToolBar and its user visible name set to Main Toolbar using the <text> tag. The clear action is added to the toolbar using the <Action> tag, the name parameter in this tag being the string that was passed to the KActionCollection with addAction() in mainwindow.cpp.

Besides having the action in the toolbar, it can also be added to the menubar. Here the action is being added to the File menu of the MenuBar the same way it was added to the toolbar.

Change the 'version' attribute of the <gui> tag if you changed .rc file since the last install to force a system cache update. Be sure it is an integer, if you use a decimal value, it will not work, but will not notify that it didn't. '

noframe
 
Warning
The version attribute must be an integer number, if you type in version="1.2" it will dispose of your kittens (but not eat them).


Some notes on the interaction between code and the .rc file: Menus appear automatically and should have a <text/> child tag unless they refer to standard menus. Actions need to be created manually and inserted into the actionCollection() using the name in the .rc file. Actions can be hidden or disabled, whereas menus can't.

CMake

Finally, the tutorial3ui.rc needs to go somewhere where KDE can find it (can't just leave it in the source directory!). This means the project needs to be installed somewhere.

CMakeLists.txt

project(tutorial3)
 
find_package(KDE4 REQUIRED)
include_directories(${KDE4_INCLUDES})
 
set(tutorial3_SRCS 
  main.cpp
  mainwindow.cpp
)
 
kde4_add_executable(tutorial3 ${tutorial3_SRCS})
 
target_link_libraries(tutorial3 ${KDE4_KDEUI_LIBS})
 
install(TARGETS tutorial3 DESTINATION ${BIN_INSTALL_DIR})
install(FILES tutorial3ui.rc 
        DESTINATION  ${DATA_INSTALL_DIR}/tutorial3)

This file is almost identical to the one for tutorial2, but with two extra lines at the end that describe where the files are to be installed. Firstly, the tutorial3 target is installed to the BIN_INSTALL_DIR then the tutorial3ui.rc file that describes the layout of the user interface is installed to the application's data directory.

Make, Install And Run

If you don't have write access to where your KDE4 installation directory, you can install it to a folder in your home directory.

To tell CMake where to install the program, set the DCMAKE_INSTALL_PREFIX switch. You probably just want to install it somewhere local for testing (it's probably a bit silly to go to the effort of installing these tutorials to your KDE directory), so the following might be appropriate:

mkdir build && cd build
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME
make install
$HOME/bin/tutorial3

which will create a KDE-like directory structure in your user's home directory and will install the executable to $HOME/bin/tutorial3.

Moving On

Now you can move on to saving and loading.

Or you can learn how to add icons to your application.

Or you can learn how to place your application in the K-Menu using .desktop files.


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal