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

Jump to: navigation, search
(Second introductory tutorial for beginner KDE programmers)
 
(Add prerequisites/what's next sections)
Line 5: Line 5:
  
 
In order to have a useful KMainWindow, we must sub class it. So we create two files, a <tt>MainWindow.cpp</tt> and a <tt>MainWindow.h</tt> which will contain our code.
 
In order to have a useful KMainWindow, we must sub class it. So we create two files, a <tt>MainWindow.cpp</tt> and a <tt>MainWindow.h</tt> which will contain our code.
 +
 +
==Prerequisites==
 +
* [[Development/Tutorials/Programming_Tutorial_KDE_4/First_program|Hello World Tutorial]]
  
 
==MainWindow Class==
 
==MainWindow Class==
Line 86: Line 89:
 
target_link_libraries( tutorial2 ${KDE4_KDEUI_LIBS})
 
target_link_libraries( tutorial2 ${KDE4_KDEUI_LIBS})
 
</code>
 
</code>
 +
==Moving On==
 +
Now you can move on to [[Development/Tutorials/Programming_Tutorial_KDE_4/Using_KActions|using KActions]].

Revision as of 20:40, 3 January 2007

Contents

Abstract

This tutorial carries on from First Program Tutorial and will introduce the KMainWindow class.

In the previous tutorial, the program caused a dialog box to pop up but were going to take steps towards a functioning application.

In order to have a useful KMainWindow, we must sub class it. So we create two files, a MainWindow.cpp and a MainWindow.h which will contain our code.

Prerequisites

MainWindow Class

MainWindow.h

  1. ifndef MAINWINDOW_H
  2. define MAINWINDOW_H
  1. include <KMainWindow>
  2. include <KTextEdit>

class MainWindow : public KMainWindow {

 public:
   MainWindow(QWidget *parent=0);
 private:
   KTextEdit* textArea;

};

  1. endif

First we Subclass KMainWindow on line 7 with with class MainWindow : public KMainWindow.

The we declare the constructor with MainWindow(QWidget *parent=0);.

And finally we declare a ponter to the object that will make up the bulk of our program. KTextEdit is a generic richtext editor with some KDE niceties like cursor auto-hiding.

MainWindow.cpp

  1. include "mainwindow.h"

MainWindow::MainWindow(QWidget *parent) : KMainWindow(parent) {

 textArea = new KTextEdit;
 setCentralWidget(textArea);
 setupGUI();

} First, of course, on line 1 we have to include the header file containing the class declaration.

On line 5, we initialise our text editor with an object. Then on line 6 we use the built-in setCentralWidget() function which tells the KMainWindow what should appear in the central section of the window.

Finally, KMainWindow::setupGUI() is called which does a lot of behind the scene's stuff and creates the default menu bars (Settings, Help).

Back to main.cpp

In order to actually run this window, we need to add a few lines in main.cpp:

main.cpp

  1. include <KApplication>
  2. include <KAboutData>
  3. include <KCmdLineArgs>
  1. include "mainwindow.h"

int main (int argc, char *argv[]) {

 KAboutData aboutData( "tutorial2", 
     "Tutorial2", "1.0", "A simple text area",
     KAboutData::License_GPL, "(c) 2006" );
 KCmdLineArgs::init( argc, argv, &aboutData );
 
 KApplication app;

 MainWindow* window = new MainWindow();
 window->show();
 return app.exec();

} The only new lines here (compared to Tutorial 1) are 14 and 15. On line 14, we create our MainWindow object and then on line 15, we display it.

CMake

The best way to build the program is to use CMake. All that's changed since tutorial 1 is mainwindow.cpp has been added to the sources list. project (tutorial2) find_package(KDE4 REQUIRED) include_directories( ${KDE4_INCLUDES} ) set(tutorial2_SRCS main.cpp mainwindow.cpp ) kde4_add_executable(tutorial2 ${tutorial2_SRCS}) target_link_libraries( tutorial2 ${KDE4_KDEUI_LIBS})

Moving On

Now you can move on to using KActions.


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