Development/Tutorials/Using Actions: Difference between revisions

From KDE TechBase
(Marked this version for translation)
(Replaced content with "This page was moved [https://develop.kde.org/docs/getting-started/using_actions/ here].")
Tag: Replaced
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
<languages/>
This page was moved [https://develop.kde.org/docs/getting-started/using_actions/ here].
<translate>
<!--T:1-->
{{TutorialBrowser|
series=Beginner Tutorial|
name=How To Use Actions and XMLGUI|
pre=[[Development/Tutorials/Using_KXmlGuiWindow|Tutorial 2 - KXmlGuiWindow]], Basic XML knowledge|
next=[[Development/Tutorials/Saving_and_loading|Tutorial 4 - Saving and loading]]|
reading=None
}}
 
==Abstract== <!--T:2-->
 
<!--T:3-->
This tutorial introduces the concept of actions. Actions are a unified way of supplying the user with ways to interact with your program.
 
<!--T:4-->
For example, if we wanted to let the user of [[Development/Tutorials/Using_KXmlGuiWindow|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 [http://doc.qt.io/qt-5/qaction.html QAction].
 
<!--T:5-->
[[image:tutorial3-kf5.png|frame|center]]
 
==QAction== <!--T:6-->
 
<!--T:7-->
A [http://doc.qt.io/qt-5/qaction.html QAction] 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 [http://doc.qt.io/qt-5/signalsandslots.html slot] which carries out the work of your action.
 
==The Code== <!--T:8-->
 
===main.cpp=== <!--T:9-->
 
<!--T:10-->
<syntaxhighlight lang="cpp-qt">
#include <cstdlib>
#include <QApplication>
#include <QCommandLineParser>
 
<!--T:11-->
#include <KAboutData>
#include <KLocalizedString>
 
<!--T:12-->
#include "mainwindow.h"
int main (int argc, char *argv[])
{
    QApplication app(argc, argv);
    KLocalizedString::setApplicationDomain("tutorial3");
   
    KAboutData aboutData(
                        // The program name used internally. (componentName)
                        QStringLiteral("tutorial3"),
                        // A displayable program name string. (displayName)
                        i18n("Tutorial 3"),
                        // The program version string. (version)
                        QStringLiteral("1.0"),
                        // Short description of what the app does. (shortDescription)
                        i18n("A simple text area using QAction etc."),
                        // The license this code is released under
                        KAboutLicense::GPL,
                        // Copyright Statement (copyrightStatement = QString())
                        i18n("(c) 2015"),
                        // Optional text shown in the About box.
                        // Can contain any information desired. (otherText)
                        i18n("Some text..."),
                        // The program homepage string. (homePageAddress = QString())
                        QStringLiteral("http://example.com/"),
                        // The bug report email address
                        // (bugsEmailAddress = QLatin1String("[email protected]")
                        QStringLiteral("submit@bugs.kde.org"));
    aboutData.addAuthor(i18n("Name"), i18n("Task"), QStringLiteral("[email protected]"),
                        QStringLiteral("http://your.website.com"), QStringLiteral("OSC Username"));
    KAboutData::setApplicationData(aboutData);
    QCommandLineParser parser;
    aboutData.setupCommandLine(&parser);
    parser.process(app);
    aboutData.processCommandLine(&parser);
   
    MainWindow* window = new MainWindow();
    window->show();
   
    return app.exec();
}
</syntaxhighlight>
 
<!--T:13-->
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=== <!--T:14-->
</translate>
<syntaxhighlight lang="cpp-qt">
#ifndef MAINWINDOW_H
#define MAINWINDOW_H
#include <KXmlGuiWindow>
 
class KTextEdit;
class MainWindow : public KXmlGuiWindow
{
  public:
    explicit MainWindow(QWidget *parent = nullptr);
  private:
    KTextEdit* textArea;
    void setupActions();
};
#endif
</syntaxhighlight>
<translate>
<!--T:15-->
Only a function <tt>void setupActions()</tt> has been added which will do all the work setting up the QActions.
 
===mainwindow.cpp=== <!--T:16-->
</translate>
<syntaxhighlight lang="cpp-qt">
#include <QApplication>
#include <QAction>
 
#include <KTextEdit>
#include <KLocalizedString>
#include <KActionCollection>
#include <KStandardAction>
 
#include "mainwindow.h"
 
MainWindow::MainWindow(QWidget *parent) : KXmlGuiWindow(parent)
{
  textArea = new KTextEdit();
  setCentralWidget(textArea);
 
  setupActions();
}
 
void MainWindow::setupActions()
{
    QAction* clearAction = new QAction(this);
    clearAction->setText(i18n("&Clear"));
    clearAction->setIcon(QIcon::fromTheme("document-new"));
    actionCollection()->setDefaultShortcut(clearAction, Qt::CTRL + Qt::Key_W);
    actionCollection()->addAction("clear", clearAction);
    connect(clearAction, SIGNAL(triggered(bool)), textArea, SLOT(clear()));
   
    KStandardAction::quit(qApp, SLOT(quit()), actionCollection());
   
    setupGUI(Default, "tutorial3ui.rc");
}
</syntaxhighlight>
<translate>
==Explanation== <!--T:17-->
 
<!--T:18-->
This builds upon the KXmlGuiWindow code from [[Development/Tutorials/Using_KXmlGuiWindow/KF5|Tutorial 2]]. Most of the changes are to <tt>mainwindow.cpp</tt>, an important structural change being that the constructor for MainWindow now calls <tt>setupActions()</tt> instead of <tt>setupGUI()</tt>. <tt>setupActions()</tt> is where the new QAction code goes before finally calling <tt>setupGUI()</tt> itself.
 
===Creating the QAction object=== <!--T:19-->
 
<!--T:20-->
The QAction is built up in a number of steps. The first is including the <tt>QAction</tt> header and then creating the QAction:
</translate>
<syntaxhighlight lang="cpp-qt">
#include <QAction>
...
QAction* clearAction = new QAction(this);
</syntaxhighlight>
<translate>
<!--T:21-->
This creates a new QAction called <tt>clearAction</tt>.
 
===Setting QAction Properties=== <!--T:22-->
 
====Text==== <!--T:23-->
 
<!--T:24-->
Now that we have our QAction object, we can start setting its properties. The following code sets the text that will be displayed in the menu and with the <tt>QAction</tt>'s icon in the toolbar, depending on the widget style (whether beside or below the icon) or setting (whether to display the action text or not).
</translate>
<syntaxhighlight lang="cpp-qt">
clearAction->setText(i18n("&Clear"));
</syntaxhighlight>
<translate>
<!--T:25-->
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]]).
 
<!--T:26-->
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==== <!--T:27-->
 
<!--T:28-->
If the action is going to be displayed in a toolbar, it is nice to have an icon depicting the action. The icon may also be displayed beside the action in the menus, depending on the widget style. The following code sets the icon to the standard the <tt>document-new</tt> icon through the use of the <tt>setIcon()</tt> function:
</translate>
<syntaxhighlight lang="cpp-qt">
clearAction->setIcon(QIcon::fromTheme("document-new"));
</syntaxhighlight>
<translate>
====Keyboard Shortcut==== <!--T:29-->
 
<!--T:30-->
Setting a keyboard shortcut to perform our action is equally simple:
</translate>
<syntaxhighlight lang="cpp-qt">
actionCollection()->setDefaultShortcut(clearAction, Qt::CTRL + Qt::Key_W);
</syntaxhighlight>
<translate>
<!--T:31-->
This associates Ctrl+W with the QAction.
 
===Adding to the Collection=== <!--T:32-->
 
<!--T:33-->
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:
</translate>
<syntaxhighlight lang="cpp-qt">
actionCollection()->addAction("clear", clearAction);
</syntaxhighlight>
<translate>
<!--T:34-->
Here, the <tt>clearAction</tt> QAction 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==== <!--T:35-->
 
<!--T:36-->
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)
</translate>
<syntaxhighlight lang="cpp-qt">
connect( clearAction, SIGNAL( triggered(bool) ),
        textArea, SLOT( clear() ) );
</syntaxhighlight>
<translate>
===KStandardAction=== <!--T:37-->
 
<!--T:38-->
For actions which would likely appear in almost every KDE application such as 'quit', 'save', and 'load' there are pre-created convenience QActions, accessed through {{class|KStandardAction}}.
 
<!--T:39-->
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 QActionCollection to add it to. For example:
</translate>
<syntaxhighlight lang="cpp-qt">
KStandardAction::quit(qApp, SLOT(quit()), actionCollection());
</syntaxhighlight>
<translate>
<!--T:40-->
Here we call the QApplicaton's [http://doc.qt.io/qt-5/qapplication.html#quit quit] method whenever the KStandardAction quit is triggered. We are able to access that QApplication method via the [http://doc.qt.io/qt-5/qapplication.html#qApp qApp] macro.
 
<!--T:41-->
In the end, this creates a QAction with the correct icon, text and shortcut and even adds it to the File menu.
 
==Adding the action to menus and toolbars== <!--T:42-->
 
<!--T:43-->
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== <!--T:44-->
 
<!--T:45-->
The Help menu has been standardized to ease the lives of both developers and users, which is why all KDE software Help menus look the same. If you want to create your own help menu, search for the explanation around showAboutApplication() in from the {{class|KHelpMenu}} class in XMLGUI.
 
==XMLGUI== <!--T:46-->
 
<!--T:47-->
The <tt>setupGUI()</tt> function in {{class|KXmlGuiWindow}} depends on the XMLGUI system to construct the GUI, which XMLGUI does by parsing an XML file description of the interface.
 
<!--T:48-->
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.
 
==appnameui.rc file== <!--T:49-->
 
<!--T:50-->
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 [[Development/Architecture/KDE4/XMLGUI_Technology|detailed XMLGUI page]].
 
===tutorial3ui.rc=== <!--T:51-->
</translate>
<syntaxhighlight lang="xml">
<?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>
    <Menu >
      <text>A&amp;nother Menu</text>
      <Action name="clear" />
    </Menu >
  </MenuBar>
  <ToolBar name="mainToolBar" >
    <text>Main Toolbar</text>
    <Action name="clear" />
  </ToolBar>
</gui>
</syntaxhighlight>
<translate>
<!--T:52-->
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>.
 
<!--T:53-->
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.
 
<!--T:54-->
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. '
 
<!--T:55-->
{{Warning|The version attribute must always be an integer number.}}
 
<!--T:56-->
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.
 
==CMake== <!--T:57-->
 
<!--T:58-->
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''', unlike in the previous tutorials.
 
===CMakeLists.txt=== <!--T:59-->
</translate>
<syntaxhighlight lang="cmake">
cmake_minimum_required(VERSION 3.0)
 
project (tutorial3)
 
set(QT_MIN_VERSION "5.3.0")
set(KF5_MIN_VERSION "5.2.0")
 
find_package(ECM 1.0.0 REQUIRED NO_MODULE)
set(CMAKE_MODULE_PATH ${ECM_MODULE_PATH} ${ECM_KDE_MODULE_DIR} ${CMAKE_CURRENT_SOURCE_DIR}/cmake)
 
include(KDEInstallDirs)
include(KDECMakeSettings)
include(KDECompilerSettings NO_POLICY_SCOPE)
include(FeatureSummary)
 
find_package(Qt5 ${QT_MIN_VERSION} CONFIG REQUIRED COMPONENTS
    Core    # QCommandLineParser, QStringLiteral
    Widgets # QApplication, QAction
)
 
find_package(KF5 ${KF5_MIN_VERSION} REQUIRED COMPONENTS
    CoreAddons      # KAboutData
    I18n            # KLocalizedString
    XmlGui          # KXmlGuiWindow, KActionCollection
    TextWidgets    # KTextEdit
    ConfigWidgets  # KStandardActions
)
   
 
feature_summary(WHAT ALL INCLUDE_QUIET_PACKAGES FATAL_ON_MISSING_REQUIRED_PACKAGES)
   
set(tutorial3_SRCS main.cpp mainwindow.cpp)
 
add_executable(tutorial3 ${tutorial3_SRCS})
 
target_link_libraries(tutorial3
    Qt5::Widgets
    KF5::CoreAddons
    KF5::I18n
    KF5::XmlGui
    KF5::TextWidgets
    KF5::ConfigWidgets
)
 
install(TARGETS tutorial3  ${KDE_INSTALL_TARGETS_DEFAULT_ARGS})
install(FILES tutorial3ui.rc DESTINATION ${KDE_INSTALL_KXMLGUI5DIR}/tutorial3)
</syntaxhighlight>
<translate>
<!--T:60-->
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>KDE_INSTALL_TARGETS_DEFAULT_ARGS</tt> then the <tt>tutorial3ui.rc</tt> file that describes the layout of the user interface is installed to the application's data directory under <tt>KDE_INSTALL_KXMLGUI5DIR</tt>.
 
===Make, Install And Run=== <!--T:61-->
 
<!--T:62-->
This is probably the trickiest part. Where you install the files, especially <tt>tutorial3ui.rc</tt> is important. Normally, you'd want to install it where KDE software is installed by your distribution, which is usually under {{path|/usr}}. That, however, would require root/admin access and If you don't have that, you can install it to a folder in your home directory.
 
<!--T:63-->
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:
</translate>
<syntaxhighlight lang="bash">
mkdir build && cd build
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME
make install
</syntaxhighlight>
<translate>
<!--T:64-->
which will create a KDE-like directory structure in your user's home directory. Specifically, it will create the directories {{path|$HOME/bin/}} and {{path|$HOME/share/}} and will install the executable to {{path|$HOME/bin/tutorial3}} and the <tt>tutorial3ui.rc</tt> file to {{path|$HOME/share/kxmlgui/tutorial3/tutorial3ui.rc}}.
 
<!--T:65-->
However, to be able to run the program properly, you will need to let the system know where the XMLGUI file is. Since we installed it in a nonstandard location, we'll have to explicitly to do so every time. The following command would suffice:
</translate>
<syntaxhighlight lang="bash">
XDG_DATA_DIRS=$HOME/share:$XDG_DATA_DIRS $HOME/bin/tutorial3
</syntaxhighlight>
<translate>
<!--T:66-->
This temporarily adds (prepends) the newly created "share" location to <tt>XDG_DATA_DIRS</tt>, the standard path for application data files.
 
==Moving On== <!--T:67-->
 
<!--T:68-->
Now you can move on to [[Development/Tutorials/Saving_and_loading|saving and loading]].
 
<!--T:69-->
Or you can learn [[Development/Tutorial/Icons|how to add icons to your application]].
 
<!--T:70-->
Or you can learn [[Development/Tutorials/Desktop_File|how to place your application in the K-Menu using .desktop files]].
 
<!--T:71-->
[[Category:C++]]
</translate>

Latest revision as of 14:33, 8 September 2020

This page was moved here.

Retrieved from "https://techbase.kde.org/index.php?title=Development/Tutorials/Using_Actions&oldid=106713"