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

(serviceByDesktopPath() requires the .desktop extension, use serviceByDesktopName() instead)
(Mark for updating)
Line 1: Line 1:
Line 12: Line 10:
reading=[http://api.kde.org/4.x-api/kdelibs-apidocs/kparts/html/index.html KParts Documentation]
reading=[http://api.kde.org/4.x-api/kdelibs-apidocs/kparts/html/index.html KParts Documentation]
{{Review|Port to KF5}}
== Introduction ==
== Introduction ==

Revision as of 09:42, 31 May 2019

How To Use KParts
Tutorial Series   Plugins and KParts
Previous   Tutorial 5 - Command line arguments
What's Next   n/a
Further Reading   KParts Documentation
This page needs a review and probably holds information that needs to be fixed.

Parts to be reviewed:

Port to KF5


KPart technology is used in kde to reuse GUI components. The advantage that a KPart presents is that it comes with predefined toolbar actions. By using kparts in applications developers can spend less time implementing text editor or command line features, for example and just use a katepart or a konsolepart instead. KParts are also used with Plugin technology to embed applications inside another, such as integrating PIM applications into Kontact.

This tutorial will show you how to use a KPart in your application, and how to create your own KPart.

KParts consist of a .desktop file describing the KPart and a .so file containing the function names and code. The .desktop file resides in KDE's services directory, you can find it out like this:

# kde4-config --path services

The first kPart we describe is KatePart, an editor representing a typical ReadWritePart. A typical ReadOnlyPart would be konsolePart.

Using Katepart

Simple KDE applications use a MainWindow derived from KMainWindow (such as in previous tutorials). To use a KPart in an application, the MainWindow must instead be derived from KParts::MainWindow. This will then take care of integrating the toolbar and menu items of the kpart together.

The following code creates a KParts::MainWindow with a kpart inside it.


#include <KApplication>
#include <KAboutData>
#include <KCmdLineArgs>
#include <KUrl>
#include "mainwindow.h"
int main (int argc, char *argv[])
    KAboutData aboutData( "kparttut1", "kparttut1",
        ki18n("KPart Tutorial 1"), "0.1",
        ki18n("A MainWindow for a KatePart."),
        ki18n("Copyright (c) 2007 Developer") );
    KCmdLineArgs::init( argc, argv, &aboutData );
    KCmdLineOptions options;
    options.add("+[file]", ki18n("Document to open"));
    KApplication app;
    MainWindow* window = new MainWindow();

    KCmdLineArgs *args = KCmdLineArgs::parsedArgs();

    return app.exec();

The main.cpp file is the same as that used in Tutorial 5 - Command line arguments.The only difference is in the details of the KAboutData.


#ifndef KPARTTUTORIAL1_H        
#define KPARTTUTORIAL1_H        
#include <kparts/mainwindow.h>  
 * This is the application "Shell".  It has a menubar, toolbar, and
 * statusbar but relies on the "Part" to do all the real work.     
 * @short Application Shell                                        
 * @author Developer <[email protected]>                           
 * @version 0.1
class MainWindow : public KParts::MainWindow
     * Default Constructor

     * Default Destructor
    virtual ~MainWindow();

public slots:
     * Use this method to load whatever file/URL you have
    void load(const KUrl& url);

     * Use this method to display an openUrl dialog and
     * load the URL that gets entered
    void load();

    void setupActions();

    KParts::ReadWritePart *m_part;

#endif // KPARTTUT1_H

The mainwindow.h file is very simple. The important thing to notice here is that the MainWindow class inherits from KParts::MainWindow.


#include "mainwindow.h"

#include <kaction.h>
#include <kactioncollection.h>
#include <kconfig.h>
#include <kedittoolbar.h>
#include <kfiledialog.h>
#include <kshortcutsdialog.h>
#include <klibloader.h>
#include <kmessagebox.h>
#include <kservice.h>
#include <kstandardaction.h>
#include <kstatusbar.h>
#include <kurl.h>

#include <QApplication>

    : KParts::MainWindow( )

    // Setup our actions

    //query the .desktop file to load the requested Part
    KService::Ptr service = KService::serviceByDesktopName

    if (service)
      m_part = service->createInstance<KParts::ReadWritePart>(0);

      if (m_part)
            // tell the KParts::MainWindow that this is indeed
            // the main widget

            setupGUI(ToolBar | Keys | StatusBar | Save);

            // and integrate the part's GUI with the shell's
          return;//return 1; 
        // if we couldn't find our Part, we exit since the Shell by
        // itself can't do anything useful
        KMessageBox::error(this, "service katepart not found");
        // we return here, cause qApp->quit() only means "exit the
        // next time we enter the event loop...


void MainWindow::load(const KUrl& url)
    m_part->openUrl( url );

void MainWindow::setupActions()
    KStandardAction::open(this, SLOT(load()), 
    KStandardAction::quit(qApp, SLOT(closeAllWindows()),

void MainWindow::load()

The mainwindow.cpp file contains the implementation of MainWindow. The constructor of this class contains all the code used to load the KPart.

First it sets up the actions used by the main window (Open and Quit), and then sets up the gui elements to go with these items (toolbar items, menu items, keyboard shortcuts). Next is the standard code used to load the KPart. The createGUI method is responsible for merging the toolbars and menus of the KPart with the rest of the application.

Note: although the part can also be loaded using KPluginLoader, this method is depricated.

   KPluginFactory* factory = KPluginLoader("katepart").factory();


<!DOCTYPE kpartgui SYSTEM "kpartgui.dtd">
<kpartgui name="kparttut1" version="1">
  <Menu noMerge="1" name="file"><text>&amp;File</text>
    <Action name="file_open"/>
    <Action name="file_quit"/>

  <Merge />
<ToolBar noMerge="1" name="mainToolBar"><text>Main Toolbar</text>
  <Action name="file_open"/>

The kparttut1ui.rc file is used to define how the actions in the part and the actions in the main window will be merged together. The <Merge /> element in the file menu for example indicates that any part containing actions in a file menu should list its parts after the file_open action and before the file_quit action.





kde4_add_executable(kparttut1 ${kparttut1_SRCS})

target_link_libraries(kparttut1 ${KDE4_KDEUI_LIBS} ${KDE4_KPARTS_LIBS})

########### install files ###############
install( FILES kparttut1ui.rc 

The CMakeLists.txt file is very simple in this case.

Running the Application

After compiling, linking and installing the application with

mkdir build && cd build && cmake .. && make -j4 && make install

it can be executed with

kparttut1 filename

where filename is a text file to load. One of the source files would be a good example.

When the file loads you will have a full-featured kate editor running in its own window. All of the editor features of kate are available in the toolbars and menu.

You will notice that the 'Open' action you defined in the MainWindow class has also appeared in the toolbar and in the menu along with the 'Quit' action.

The next tutorial will deal with creating your own kparts for use (and reuse) in other applications.

This page was last edited on 31 May 2019, at 09:42. Content is available under Creative Commons License SA 4.0 unless otherwise noted.