Translate

Translate to башҡортса

Translation of the wiki page Development/Tutorials/First program from English (en) to kernowek (kw)

This tool does not work without JavaScript. JavaScript is disabled, failed to work, or this browser is unsupported.

Translations:Development/Tutorials/First program/Page display title/ba

Development/Tutorials/First program

You need translation rights to translate messages.Get permission

Loading...

series=Beginner Tutorial|‎

Edit

name=Hello World|‎

Edit

pre=[http://mindview.net/Books/TICPP/ThinkingInCPP2e.html C++], [https://www.qt.io/ Qt], [[Special:myLanguage/Getting_Started/Build|Building KDE]]|‎

Edit

next=[[Special:myLanguage/Development/Tutorials/Using_KXmlGuiWindow|Tutorial 2 - KXmlGuiWindow]]|‎

Edit

reading=[[Special:myLanguage/Development/Tutorials/CMake|CMake]] }}‎

Edit

==Abstract==‎

Edit

Your first program shall greet the world with a friendly "Hello World", what else? For that, we will use a {{class|KMessageBox}} and customise one of the buttons.‎

Edit

[[image:Introtokdetutorial1-kf5.png|frame|center]]‎

Edit

{{Tip|To get more information about any class you come across, you can use the ‘kde’ search engine. For example, to look for information about KMessageBox, just type "kde:kmessagebox" into Konqueror, Rekonq or KRunner, and you’ll be taken to the documentation.}}‎

Edit

{{Tip| You might want to use [[Special:myLanguage/KDevelop|KDevelop]] or [[Special:myLanguage/qtcreator|QtCreator]] as IDE for your projects. }}‎

Edit

==The Code==‎

Edit

All the code we need will be in one file, <tt>main.cpp</tt>. Create that file with the code below:‎

Edit

KAboutData aboutData( // The program name used internally. (componentName) QStringLiteral("tutorial1"), // A displayable program name string. (displayName) i18n("Tutorial 1"), // The program version string. (version) QStringLiteral("1.0"), // Short description of what the app does. (shortDescription) i18n("Displays a KMessageBox popup"), // 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);‎

Edit

First we need to create a [http://doc.qt.io/qt-5/qapplication.html QApplication] object. This needs to be done exactly once in each program since it is needed for things such as [[Development/Tutorials/Localization/i18n|i18n]]. It also should be created before any other KDE Framework or Qt object. A call to {{class|KLocalizedString}}::setApplicationDomain() is required to properly set the translation catalog and must be done before the next step happens.‎

Edit

The first KDE Framework specific object we create in this program is {{class|KAboutData}}. This is the class used to store information about the program such as a short description, authors or license information. Pretty much every KDE application should use this class. We then call {{class|KAboutData}}::setApplicationData() to initialize the properties of the [http://doc.qt.io/qt-5/qapplication.html QApplication] object.‎

Edit

Then we come to [http://doc.qt.io/qt-5/qcommandlineparser.html QCommandLineParser]. This is the class one would use to specify command line switches to, for example, open the program with a specific file. However, in this tutorial, we simply initialise it with the {{class|KAboutData}} object we created so we can use the <tt>--version</tt> or <tt>--author</tt> switches.‎

Edit

Now we've done all the necessary setup, we can move on to doing interesting things with our application. We're going to create a popup box but we're going to customise one of the buttons. To do this customisation, we need to use a {{class|KGuiItem}} object. The first argument in the {{class|KGuiItem}} constructor is the text that will appear on the item (in our case, a button). Then we have an option of setting an icon for the button but we don't want one so we just give it <tt>QString()</tt>. We then set the tooltip (what appears when you hover over an item) and finally the "What's This?" (accessed through right-clicking or Shift-F1) text.‎

Edit

Now we have our item, we can create our popup. We call the <tt>{{class|KMessageBox}}::questionYesNo()</tt> function which, by default, creates a message box with a "Yes" and a "No" button. The second argument is the text that will appear in the message box above the buttons. The third is the caption the window will have and finally, we set the KGuiItem for (what would normally be) the "Yes" button to the <tt>KGuiItem yesButton</tt> we created.‎

Edit

Note that all user-visible text is passed through the i18n() function; this is necessary for the UI to be translatable. More information on localization can be found in the [[Special:myLanguage/Development/Tutorials/Localization/i18n|localization tutorial]].‎

Edit

We're all done as far as the code is concerned. Now to build it and try it out.‎

Edit

== Build ==‎

Edit

You want to [[Special:myLanguage/Development/Tutorials/CMake|use CMake]] for your build environment. You provide a file {{Path|CMakeLists.txt}}, CMake uses this file to generate all Makefiles out of it.‎

Edit

=== CMakeLists.txt ===‎

Edit

Create a file named {{Path|CMakeLists.txt}} in the same directory as {{Path|main.cpp}} with this content:‎

Edit

The <tt>find_package()</tt> function locates the package that you ask it for (in this case ECM, Qt5, or KF5) and sets some variables describing the location of the package's headers and libraries. ECM, or Extra CMake Modules, is required to import special CMake files and functions for building KDE applications.‎

Edit

Here we try to find the modules for Qt 5 and KDE Frameworks 5 required to build our tutorial. The necessary files are included by CMake so that the compiler can see them at build time. Minimum version numbers are set at the very top of CMakeLists.txt file for easier reference.‎

Edit

Next we create a variable called <tt>tutorial1_SRCS</tt> using the <tt>set()</tt> function. In this case we simply set it to the name of our only source file.‎

Edit

Then we use <tt>add_executable()</tt> to create an executable called <tt>tutorial1</tt> from the source files listed in our <tt>tutorial1_SRCS</tt> variable. Afterwards, we link our executable to the necessary libraries using <tt>target_link_libraries()</tt> function. The line starting with <tt>install</tt> writes a default "install" target into the Makefile.‎

Edit

=== Make And Run ===‎

Edit

To compile, link and install your program, you must have several software installed, e.g. cmake, make and gcc-c++, and the Qt 5 and KDE Frameworks development files. To be sure you have everything, best follow [https://community.kde.org/Get_Involved/development#One-time_setup:_your_development_environment this install guide].‎

Edit

While you can run '''CMake''' directly inside the source code directory itself, it is a best practice, and actually enforced in some KDE software, to use a separate build directory and run '''CMake''' from there:‎

Edit

And launch it with:‎

Edit

==Moving On==‎

Edit

Now you can move on to [[Special:myLanguage/Development/Tutorials/Using_KXmlGuiWindow|using KXmlGuiWindow]].‎

Edit

[[Category:C++]]‎

Edit