Translate
AllDevelopment/Tutorials/Using KXmlGuiWindow
Translate to Bahasa Melayu
Translation of the wiki page Development/Tutorials/Using KXmlGuiWindow from English (en) to Bahasa Melayu (ms)
This tool does not work without JavaScript. JavaScript is disabled, failed to work, or this browser is unsupported.
Translations:Development/Tutorials/Using KXmlGuiWindow/Page display title/ms
Development/Tutorials/Using KXmlGuiWindow
You need translation rights to translate messages.Get permission
{{TutorialBrowser|
series=Beginner Tutorial|
name=How To Use KXmlGuiWindow|
pre=[[Development/Tutorials/First_program|Tutorial 1 - Hello World]]|
next=[[Development/Tutorials/Using_Actions|Tutorial 3 - QActions and XMLGUI]]|
reading={{class|KXmlGuiWindow}}
}}
Translations:Development/Tutorials/Using KXmlGuiWindow/1/ms
{{TutorialBrowser|
series=Beginner Tutorial|
name=How To Use KXmlGuiWindow|
pre=[[Development/Tutorials/First_program|Tutorial 1 - Hello World]]|
next=[[Development/Tutorials/Using_Actions|Tutorial 3 - QActions and XMLGUI]]|
reading={{class|KXmlGuiWindow}}
}}
You need translation rights to translate messages.Get permission
This tutorial carries on from [[Development/Tutorials/First_program/KF5|First Program Tutorial]] and will introduce the {{class|KXmlGuiWindow}} class.
In the previous tutorial, the program caused a dialog box to pop up but we're going to take steps towards a functioning application.
{{class|KXmlGuiWindow}} provides a full main window view with menubars, toolbars, a statusbar and a main area in the centre for a large widget. For example, the help-menu is predefined. Most KDE applications will derive from this class as it provides an easy way to define menu and toolbar layouts through XML files (this technology is called XMLGUI and is part of the KF5::XmlGui framework). While we will not be using XMLGUI in ''this'' tutorial, we will use it in the next.
In order to have a useful KXmlGuiWindow, we must subclass it. So we create two files, a <tt>mainwindow.cpp</tt> and a <tt>mainwindow.h</tt> which will contain our code.
First we subclass KXmlGuiWindow with <tt>class MainWindow : public KXmlGuiWindow</tt> then we declare the constructor with <tt>MainWindow(QWidget *parent = nullptr);</tt>.
And finally, we declare a pointer to the object that will make up the bulk of our program. {{class|KTextEdit}} is a generic rich text editing widget with some niceties like cursor auto-hiding.
We initialise our text editor with an object and use KXmlGuiWindow's built-in setCentralWidget() function on it which tells the KXmlGuiWindow what should appear in the central section of the window.
Finally, KXmlGuiWindow::setupGUI() is called which does a lot of behind-the-scenes stuff and creates the default menu bars (Settings, Help).
<syntaxhighlight lang="cpp-qt">
#include <cstdlib>
#include <QApplication>
#include <QCommandLineParser>
#include <KAboutData>
#include <KLocalizedString>
#include "mainwindow.h"
int main (int argc, char *argv[])
{
QApplication app(argc, argv);
KLocalizedString::setApplicationDomain("tutorial2");
KAboutData aboutData(
// The program name used internally. (componentName)
QStringLiteral("tutorial2"),
// A displayable program name string. (displayName)
i18n("Tutorial 2"),
// The program version string. (version)
QStringLiteral("1.0"),
// Short description of what the app does. (shortDescription)
i18n("A simple text area"),
// 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("submit@bugs.kde.org")
QStringLiteral("submit@bugs.kde.org"));
aboutData.addAuthor(i18n("Name"), i18n("Task"), QStringLiteral("your@email.com"),
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>
Again, we include our new header file in order to create our MainWindow object which we then display.
The best way to build the program is to use CMake. We add <tt>mainwindow.cpp</tt> to the sources list, include the XmlGui and TextWidgets (for KTextEdit) frameworks, and replace all <tt>tutorial1</tt> text to <tt>tutorial2</tt>.
=== Compile and run ===
The best way to compile, link and run it is to [[Getting_Started/Build|set up a correct build environment]]. But for a simple tutorial like this, it's enough to just create a build directory and build from there. This command takes care of all of that in one line:
<syntaxhighlight lang="bash">
mkdir build && cd build && cmake .. && make && ./tutorial2
</syntaxhighlight>
Loading messages...
0% translated, 0% reviewed
Retrieved from "https://techbase.kde.org/Special:Translate"