View source for Tutorials/Hacking KDE

{{DISPLAYTITLE:Hacking KDE}}
This article is about my hobby improving the [http://www.kde.org KDE] desktop environment (KDE). I list some code here that could help either you or me. I have another article about [[KDE administration]]. [[ktimetracker]] is my main kde project.

= Build system =
To build KDE, I use a VMware player virtual machine and follow http://techbase.kde.org/Getting_Started/Build/KDE4/on_virtual_machines (I wrote it as well). I [http://techbase.kde.org/Qt-creator use qt-creator as an IDE].

= debugging output =

== Problem: I cannot see debugging output ==
try kdebugdialog

== How do I remove debugging output == 
Goal ist to remove debugging output caused by kDebug from the programs. Here is how to:
 cmake -DCMAKE_BUILD_TYPE=Release .
[http://techbase.kde.org/Development/CMake/Addons_for_KDE#Buildtypes more info...]

= tools I use =

== eclipse ==
Eclipse is an IDE providing you with 
* call graphs (working)
* code completion
* switching between a function's implementation and declaration (great if you want to read the apidox help)
* one-click-start of the program you are editing

More info: http://techbase.kde.org/Getting_Started/Set_up_KDE_4_for_development#Eclipse

== egypt - creates call graphs ==
[http://www.gson.org/egypt/ egypt] creates static call graphs for a given C/C++ program
you will have to use
 cmake -DCMAKE_CXX_FLAGS=-dr -DCMAKE_C_FLAGS=-dr
then do something like
 /root/egypt-1.6/egypt main.cpp.131r.expand > callgraph.dot
then
 dot -Tps -o callgraph.ps callgraph.dot
then show your ps file
 konqueror callgraph.ps

== doxygen ==
Not as good as egypt for call graphs, but gives you a good api documentation. To get it working as you want, best use doxywizard, e.g. in SUSE:
 yast -i doxywizard
 doxywizard

== sourcenavigator ==
[http://sourcenav.berlios.de/ SourceNaviGatOr] allows you to switch from a call to a function to its implementation

== krazy ==
checks for possibly wrong code

== icemon ==
svn co https://svn.kde.org/home/kde/trunk/playground/devtools

= KDE 4 =
KDE 4 is worse than KDE 3.5. This is because of
* name changes
** kpdf->okular
* instability
* missing functionality like increasing the width of knewsticker without increasing the height
* sluggish over NX protocol
* missing kpersonalizer
** Windows moving/resizing effects
* missing kcontrol
* kdm: you cannot disallow a user to powerdown the computer. Very bad on a terminal server.
* .kde settings are not migrated or the same as before
* cannot create an application link with right mouse button
* cannot move icons in the panel
* cannot remove kicker, updater, and beagle
* strange icon in the upper right that makes the screen smaller suddenly

= Tutorials =

== parser ==
See [[parser]].

== Kontact plugins ==
See [[kontact plugins]].

== Using a kioslave/write a mini-browser ==
This tells you how to use a kioslave in KDE 4. In it, we write some kind of a mini-browser as a demo. We use the http kioslave kio_http.

See [[using a kioslave in KDE 4]].

== Using the fish kioslave/access remote files ==
In KDE, you can access remote files via fish://. Here is an example how to load /tmp/fishtest.txt from localhost. You need to 
 useradd -m fishuser
 passwd fishuser 
 touch /tmp/fishtest.txt
first.

=== main.cpp ===
<pre>
#include <kapplication.h>
#include <kaboutdata.h>
#include <kcmdlineargs.h>
#include <kdebug.h>
#include <kio/netaccess.h>
#include <KMainWindow>
#include <KTemporaryFile>

int main (int argc, char *argv[])
{
  const QByteArray& ba=QByteArray("test");
  const KLocalizedString name=ki18n("myName");
  KAboutData aboutData( ba, ba, name, ba, name);
  KCmdLineArgs::init( argc, argv, &aboutData );
  KApplication khello;
  KMainWindow* mainwindow=new KMainWindow();
  QWidget* mywidget=new QWidget();
  mainwindow->setCentralWidget(mywidget);
  mainwindow->show();
  kDebug() << "loading fish://fishuser@localhost/tmp/fishtest.txt";
  QString err=QString();
  QString content=QString();
  QString filename="fish://fishuser@localhost/tmp/fishtest.txt";
  KUrl url(filename);
  kDebug() << url.url();
  // load remotely
  {
    KTemporaryFile tmpFile;
    if ( !tmpFile.open() ) err = QString::fromLatin1( "Unable to get temporary file" );
    else
    {
      QString test2;
      QString& test=test2;
      if (!KIO::NetAccess::download( url, test, 0 )) err=QString::fromLatin1("Could not download");
      filename=test;
      kDebug() << "Using file " << filename;
      static QFile file(filename);
      static QTextStream stream(&file);
      if (file.open(QIODevice::ReadOnly))
        while (!stream.atEnd()) content.append(stream.readLine()).append("\n");
      file.close();
    }
  }
  kDebug() << "err=" << err;
  kDebug() << "content=" << content;
}
</pre>

=== CMakeLists.txt ===
<pre>
PROJECT( tutorial )
FIND_PACKAGE(KDE4 REQUIRED)
INCLUDE_DIRECTORIES( ${KDE4_INCLUDES} . )


SET(tutorialSources main.cpp )

KDE4_ADD_EXECUTABLE(tutorial ${tutorialSources} )

TARGET_LINK_LIBRARIES(tutorial ${KDE4_KDEUI_LIBS} ${KDE4_KPARTS_LIBS} )
</pre>

=== Compile, link and run ===
 cmake . && make && ./tutorial

== Write a kioslave ==
See [[write a kioslave]].

== dirwatcher ==

=== test.cpp ===
<pre>
#include "hello.h"
#include <qstring.h>
#include <kapplication.h>
#include <kdebug.h>
#include <kwindowsystem.h>
#include <kaboutdata.h>
#include <kmessagebox.h>
#include <kcmdlineargs.h>

int main(int argc, char *argv[])
{
  const QByteArray qba="test";
  const KLocalizedString kls=ki18n("test");
  KAboutData aboutData( qba, qba, kls, qba, kls, KAboutData::License_GPL, kls, kls, qba, qba);
  KCmdLineArgs::init( argc, argv, &aboutData );
  KApplication khello2;
  khello* dw1=new khello("/tmp/test");
  KGuiItem kgi(QString("Hello"),QString(),QString("this is a tooltip"),QString("this is whatsthis"));
  kDebug() << KWindowSystem::activeWindow();
  khello2.exec();
}
</pre>

=== hello.h ===
<pre>
#ifndef _KHELLO_H_
#define _KHELLO_H_

#ifdef HAVE_CONFIG_H
#include <config.h>
#endif

#include <kmainwindow.h>
#include <kdirwatch.h>

/**
 * @short Application Main Window
 * @author Thorsten Staerk
 * @version 0.1
 */
class khello : public KMainWindow
{
    Q_OBJECT
public:
    KDirWatch dw;
    /** Default Constructor */
    khello(char* args);
    /** Default Destructor */
    virtual ~khello();
public slots:
    void slotdirty();
};
#endif // _KHELLO_H_
</pre>

=== hello.cpp ===
<pre>
/*
 This program shows us how to set up a kdirwatch, telling us when a file has changed.
 To compile this, create project with kdevelop and add these files.
 */

#include "hello.h"
#include <qlabel.h>
#include <kdebug.h>
#include <kmainwindow.h>
#include <klocale.h>
#include <kmessagebox.h>

khello::khello(char* args)
    : KMainWindow( 0)
{
    // set the shell's ui resource file
    kDebug() << "args = " << args << endl;
    dw.addFile(args);
    kDebug() << "Watching file " << args << endl;
    connect(&dw, SIGNAL(dirty(const QString & ) ),
           SLOT( slotdirty() ) );
}

khello::~khello()
{
}

void khello::slotdirty()
{
  kDebug() << "File has changed" << endl;
}

#include "hello.moc"
</pre>

=== compile and run it ===
 moc hello.h>hello.moc && g++ -I/usr/include/Qt -I/home/kde-devel/kde/include -L/home/kde-devel/kde/lib -lkdeui -lkio test.cpp hello.cpp


== QTreeWidget ==

This is a very minimalistic QTreeWidget coding demonstration - you can use it to learn, and as a template.

'''main.cpp'''
 #include <QTreeWidget>
 #include <kapplication.h>
 #include <kaboutdata.h>
 #include <kcmdlineargs.h>
 #include <KMainWindow>
 
 int main (int argc, char *argv[])
 {
   const QByteArray& ba=QByteArray("test");
   const KLocalizedString name=ki18n("myName");
   KAboutData aboutData( ba, ba, name, ba, name);
   KCmdLineArgs::init( argc, argv, &aboutData );
   KApplication khello;
   KMainWindow* mainwindow=new KMainWindow();
   QWidget* mywidget=new QWidget();
   QTreeWidget* qw=new QTreeWidget(mywidget);
   qw->setColumnCount(3);
   QStringList columns;
   columns << "first column" << "second column" << "third column";
   QTreeWidgetItem* item=new QTreeWidgetItem(qw,columns);
   qw->addTopLevelItem(item);
   mainwindow->setCentralWidget(mywidget);
   mainwindow->show();
   return khello.exec();
 }
'''CMakeLists.txt'''
<pre>
PROJECT( tutorial )
FIND_PACKAGE(KDE4 REQUIRED)
INCLUDE_DIRECTORIES( ${KDE4_INCLUDES} . )


SET(tutorialSources main.cpp )

KDE4_ADD_EXECUTABLE(tutorial ${tutorialSources} )

TARGET_LINK_LIBRARIES(tutorial ${KDE4_KDEUI_LIBS} ${KDE4_KPARTS_LIBS} )
</pre>
'''To compile, link and run this program, use:'''
 cmake . && make && ./tutorial

== Your own html editor ==

Here we develop an html editor:

'''main.cpp'''
<pre>
#include <QTextEdit>
#include <QTreeWidget>
#include <kapplication.h>
#include <kaboutdata.h>
#include <kcmdlineargs.h>
#include <KMainWindow>

int main (int argc, char *argv[])
{
  const QByteArray& ba=QByteArray("tutorial");
  const KLocalizedString name=ki18n("tutorial");
  KAboutData aboutData( ba, ba, name, ba, name);
  KCmdLineArgs::init( argc, argv, &aboutData );
  KApplication khello;
  KMainWindow* mainwindow=new KMainWindow();
  QWidget* mywidget=new QWidget();
  QTextEdit* qt=new QTextEdit(mywidget);
  qt->setText("these are <b>fat</b> characters");
  mainwindow->setCentralWidget(mywidget);
  mainwindow->show();
  return khello.exec();
}
</pre>
'''CMakeLists.txt'''
<pre>
PROJECT( tutorial )
FIND_PACKAGE(KDE4 REQUIRED)
INCLUDE_DIRECTORIES( ${KDE4_INCLUDES} . )

SET(tutorialSources main.cpp )

KDE4_ADD_EXECUTABLE(tutorial ${tutorialSources} )

TARGET_LINK_LIBRARIES(tutorial ${KDE4_KDEUI_LIBS} ${KDE4_KPARTS_LIBS} )
</pre>
'''To compile, link and run this program, use:'''
 cmake . && make && ./tutorial

= dbus =

dbus has a strange and complicated syntax.
 kde-devel@kolossus:~/qt-copy> dbus-send --type=method_call --print-reply --dest=org.kde.ktimetracker /KTimeTracker org.kde.ktimetracker.ktimetracker.version
 method return sender=:1.64 -> dest=:1.84
    string "4.0.0"


= Error msgs and what they mean =

Error msgs originating from ASSERT are just a shame. Here is a bit of help what they might want to say to you:
 ASSERT: "s->parsed == false" in file /home/kde-devel/kde/src/kdelibs/kdecore/kernel/kcmdlineargs.cpp, line 520
=> You need to call
 KUniqueApplication myApp;
before 
 KCmdLineArgs *args = KCmdLineArgs::parsedArgs();
yes, this makes it impossible to program a switch if you want a konsole application (KUniqueApplication myApp(false,false)) or not.

== qFlagLocation ==

=== Problem ===
When trying to compile a program, you get an error like
 akapplication.cpp:(.text+0xa54): undefined reference to `qFlagLocation(char const*)'

=== Example ===
<pre>
linux-e4ue:~/kdesupport # make
[  0%] Built target automoc4
[  0%] Built target akonadiprotocolinternals
[  0%] Built target akonadiprivate_automoc
[ 10%] Built target akonadiprivate
Linking CXX executable ../../bin/akonadiserver
CMakeFiles/akonadiserver_bin.dir/shared/akapplication.cpp.o: In function `AkApplication::AkApplication(int&, char**)':
akapplication.cpp:(.text+0xa54): undefined reference to `qFlagLocation(char const*)'
akapplication.cpp:(.text+0xa62): undefined reference to `qFlagLocation(char const*)'
</pre>

=== Searching the cause ===
Problem was that I had QT 4.5 installed ''over'' QT 4.4.
 tweedleburg:~/qt-copy # grep -ir "qflaglocation" *
 Binary file lib/libQtCore.so.4.5 matches
 Binary file lib/libQtCore.so.4.5.0.debug matches

 tweedleburg:~/phonon # nm --demangle ../qt-copy/lib/libQtCore.so.4.5 | grep -i qflagl
 0000000000163570 T qFlagLocation(char const*)
 000000000044c2f0 b qFlagLocation(char const*)::idx

 tweedleburg:~/qt-copy # grep -ir "qflaglocation" *
 Binary file lib/libQtCore.so.4.5 matches
 Binary file lib/libQtCore.so.4.5.0.debug matches
 Binary file lib/libQtCore.so matches
 Binary file lib/libQtCore.so.4 matches
 Binary file lib/libQtCore.so.4.5.0 matches
 Binary file src/qt3support/.pch/release-shared/Qt3Support.gch/c++ matches
 Binary file src/corelib/.pch/release-shared/QtCore.gch/c++ matches
 Binary file src/corelib/.obj/release-shared/qobject.o matches
 src/corelib/kernel/qobject.cpp:const char *qFlagLocation(const char *method)
 src/corelib/kernel/qobjectdefs.h:Q_CORE_EXPORT const char *qFlagLocation(const char *method);
 src/corelib/kernel/qobjectdefs.h:# define METHOD(a)   qFlagLocation("0"#a QLOCATION)
 src/corelib/kernel/qobjectdefs.h:# define SLOT(a)     qFlagLocation("1"#a QLOCATION)
 src/corelib/kernel/qobjectdefs.h:# define SIGNAL(a)   qFlagLocation("2"#a QLOCATION)
 src/corelib/kernel/qobject.cpp.orig:const char *qFlagLocation(const char *method)

=== Solution ===
One solution was to re-install QT 4.4, for example with SUSE Linux:
 yast -i libqt4

== Could not run kstartupconfig4 ==
When I got this error, I first wondered why it could not be started, but the problem was rather it returned an error.
To track this error down, call kstartupconfig4 from command line and look for the return code. For me, it was 3. Looking into kdostartupconfig.cpp showed that this means problem when opening the file startupconfig. I added a debugging output how the file name is before returning 3. It is /root/.kde/share/config/startupconfigkeys. This file did not exist. I did a touch on this file. Then KDE came up.

The misleading error msg is contained in startkde.
[http://websvn.kde.org/?view=rev&revision=888689 My bugfix]

== corrupted double-linked list ==

 *** glibc detected *** ktimetracker: corrupted double-linked list: 0x000000000073beb0 ***
I could always resolve this with recompiling the complete module (not only the respective subdir)

= Find out focus window =

'''main.cpp'''
<pre>
#include <qstring.h>
#include <kapplication.h>
#include <kdebug.h>
#include <kwindowsystem.h>
#include <kaboutdata.h>
#include <kmessagebox.h>
#include <kcmdlineargs.h>
#include <iostream>

int main (int argc, char *argv[])
{
  const QByteArray qba="test";
  const KLocalizedString kls=ki18n("test");
  KAboutData aboutData( qba, qba, kls, qba, kls, KAboutData::License_GPL, kls, kls, qba, qba);
  KCmdLineArgs::init( argc, argv, &aboutData );
  KApplication khello;
  std::cout << KWindowSystem::windowInfo(KWindowSystem::activeWindow(),NET::WMName, 0).name().toStdString() << std::endl;
}
</pre>

'''CMakeLists.txt'''
 PROJECT( tutorial )
 FIND_PACKAGE(KDE4 REQUIRED)
 INCLUDE_DIRECTORIES( ${KDE4_INCLUDES} . )
 
 SET(tutorialSources main.cpp )
 
 KDE4_ADD_EXECUTABLE(tutorial ${tutorialSources} )
 
 TARGET_LINK_LIBRARIES(tutorial ${KDE4_KDEUI_LIBS} ${KDE4_KPARTS_LIBS} )

'''Compile and run it'''
 cmake . && make && ./tutorial

== See also ==

* [[How_to_find_out_which_window_has_the_focus]]

= Find out when a focus change occurs =

'''main.cpp'''
<pre>
#include <hello.h>
#include <qstring.h>
#include <kapplication.h>
#include <kdebug.h>
#include <kwindowsystem.h>
#include <kaboutdata.h>
#include <kmessagebox.h>
#include <kcmdlineargs.h>

int main(int argc, char *argv[])
{
  const QByteArray qba="test";
  const KLocalizedString kls=ki18n("test");
  KAboutData aboutData( qba, qba, kls, qba, kls, KAboutData::License_GPL, kls, kls, qba, qba);
  KCmdLineArgs::init( argc, argv, &aboutData );
  KApplication myApp;
  khello* dw1=new khello();
  kDebug() << "Active Window is " << KWindowSystem::activeWindow();
  myApp.exec();
}
</pre>
'''hello.h'''
<pre>
#ifndef _KHELLO_H_
#define _KHELLO_H_

#ifdef HAVE_CONFIG_H
#include <config.h>
#endif

#include <kmainwindow.h>
#include <kdirwatch.h>

/**
 * @short Application Main Window
 * @author Thorsten Staerk
 * @version 0.1
 */
class khello : public KMainWindow
{
    Q_OBJECT
public:
    KDirWatch dw;
    /** Default Constructor */
    khello();
    /** Default Destructor */
    virtual ~khello();
public slots:
    void slotdirty();
};
#endif // _KHELLO_H_
</pre>
'''hello.cpp'''
<pre>
/*
 This program shows us how to set up a watcher which Window gets the focus.
 Copyright (c) 2007-11-04 by Thorsten Staerk
 */

#include "hello.h"
#include <qlabel.h>
#include <kdebug.h>
#include <kmainwindow.h>
#include <klocale.h>
#include <kmessagebox.h>
#include <kwindowsystem.h>

khello::khello()
    : KMainWindow( 0)
{
    kDebug() << "Watching which window gets the focus ";
    KWindowSystem* kw=KWindowSystem::self();
    connect(kw, SIGNAL(activeWindowChanged(WId)), SLOT( slotdirty() ) );
}

khello::~khello()
{
}

void khello::slotdirty()
{
  kdDebug() << "Focus has changed" << endl;
}

#include "hello.moc"
</pre>
'''CMakeLists.txt'''
<pre>
PROJECT( kde4start )
FIND_PACKAGE(KDE4 REQUIRED)
INCLUDE_DIRECTORIES( ${KDE4_INCLUDES} . )


SET(kde4startSources hello.cpp main.cpp)

KDE4_ADD_EXECUTABLE(kde4start ${kde4startSources} )

TARGET_LINK_LIBRARIES(kde4start ${KDE4_KDEUI_LIBS} ${KDE4_KPARTS_LIBS} )
</pre>
'''Compile and run this using'''
 cmake .
 make
 ./kde4start

= ToDo =

* http://bugs.kde.org/buglist.cgi?cmdtype=runnamed&namedcmd=allMyoPenAsSignedBugs

= krep =

krep should look how many processors it has and adjust its thread count accordingly.
Ideas:
* http://doc.trolltech.com/4.3/qthread.html#idealThreadCount
* http://techbase.kde.org/index.php?title=Development/Tutorials/Solid_Tutorials#Listing_Devices

= ktimetracker =

make the kontact plugin selectable. The heart of this is a [http://api.kde.org/4.x-api/kdelibs-apidocs/kdeui/html/classKCModule.html KCModule] that is in every selectable kontact plugin (even in kaddressbook, but not in the plugins path).

= bugzillas =
* bugs.kde.org
* http://www.trolltech.com/developer/task-tracker/

= proposed menu =
* web
* productivity
** locations like home folder, where there is media as well
* games 
** learn games

== Dell menu ==
* web
* productivity
* games
* entertainment
* learn

= kmail =

== Get an ide ==

To get an ide for kmail, I use kdevelop: http://techbase.kde.org/index.php?title=Getting_Started/Set_up_KDE_4_for_development#KDevelop

== allow addresses ending on . ==

e-Mail-addresses may not end with a . before the @. However, some people do have them. We should allow it, but warn. Here is a workaround:
<pre>
--- libemailfunctions/email.cpp (revision 773158)
+++ libemailfunctions/email.cpp (working copy)
@@ -509,6 +509,7 @@
 //-----------------------------------------------------------------------------
 bool KPIM::isValidSimpleEmailAddress( const QString& aStr )
 {
+  return true;
   // If we are passed an empty string bail right away no need to process further
   // and waste resources
   if ( aStr.isEmpty() ) {
</pre>

http://en.wikipedia.org/wiki/E-mail_address

== kmail search ==

This chapter's intention is to improve the kmail searches a bit.

=== Search for attachments ===

Problem: see http://bugs.kde.org/show_bug.cgi?id=84409

<pre>
svn diff
Index: headeritem.cpp
===================================================================
--- headeritem.cpp      (revision 748768)
+++ headeritem.cpp      (working copy)
@@ -297,6 +297,8 @@
         !headers->paintInfo()->showAttachment &&
         msgBase->attachmentState() == KMMsgHasAttachment )
       pixmaps << *KMHeaders::pixAttachment;
+    kdDebug(5006) << "Setting the attachment pix" << endl;
+    kdDebug(5006) << "For msg " << msgBase->subject() << endl;

     // Only merge the crypto icons in if that is configured.
     if ( headers->paintInfo()->showCryptoIcons ) {
</pre>

The problem is the status of a KMMessage which is a KMMsgBase.
KMMessage->status() = mStatus.

=== Stalling when searching / ===

The first problem is that the search stalls when you search the "/" folder in an imap account.


The Stalling happens in searchjob.cpp, function searchCompleteFolder, when it gets the URL imap://user:password@server:143/;SECTION%3DHEADER%20Subject%20%22E%22

Solved by this commit:
http://websvn.kde.org/branches/KDE/3.5/kdepim/kmail/searchjob.cpp?r1=645363&r2=745678&sortby=date

==== the kioslave ====

http://api.kde.org/4.0-api/kdelibs-apidocs/kio/html/classKIO_1_1Scheduler.html#_details

For kmail, kio_imap4's kdemain and IMAP4Protocol::IMAP4Protocol is started after you enter the password.
<pre>
Index: imapaccountbase.cpp
===================================================================
--- imapaccountbase.cpp (revision 743935)
+++ imapaccountbase.cpp (working copy)
@@ -286,6 +286,8 @@

 ImapAccountBase::ConnectionState ImapAccountBase::makeConnection()
 {
+  kDebug() << "***********************************************************************************************";
+  kDebug() << "Entering ImapAccountBase::makeConnection()";
</pre>



= kio_imap4 =
== test.cpp ==
<pre>
#include <kio/scheduler.h>
#include <kurl.h>
#include <kconfiggroup.h>
#include <kconfig.h>
#include <klocale.h>
#include <kcomponentdata.h>
int main()
{
  KComponentData instance( "kcmkmail_config_misc" );
  KConfigGroup passwords( KGlobal::config(), "Passwords" );
  const KUrl url("imap://dummy:password@localhost/inbox");
  KIO::Scheduler::getConnectedSlave(url,KIO::MetaData());
}
kde-devel@kolossus:~/kio> g++ -I/home/kde-devel/kde/include -L/home/kde-devel/kde/lib -lkio test.cpp
</pre>

See also [[kio-imap4 programming]]

==== Patch ====

This has all been resolved, see https://bugs.kde.org/show_bug.cgi?id=153448

=== Multiple folders search ===

<pre>
svn diff kmfoldersearch.cpp
Index: kmfoldersearch.cpp
===================================================================
--- kmfoldersearch.cpp  (revision 744858)
+++ kmfoldersearch.cpp  (working copy)
@@ -173,6 +173,8 @@
         return;
     }

+    // TODO: add multiple folders to be searched here, after gui
+    // extension (BUG 153443)
     mFolders.append( mRoot );
     if ( recursive() )
     {
@@ -259,11 +261,13 @@
             mLastFolder = folder->label();
             folder->open("kmsearch");
             mOpenedFolders.append( folder );
+            kdDebug() << "Opened folder '" << mLastFolder << "' for searching." << endl;
             connect( folder->storage(),
                 SIGNAL( searchResult( KMFolder*, QValueList<Q_UINT32>, const KMSearchPattern*, bool ) ),
                 this,
                 SLOT( slotSearchFolderResult( KMFolder*, QValueList<Q_UINT32>, const KMSearchPattern*, bool ) ) );
             folder->storage()->search( mSearchPattern );
+            kdDebug() << "Searched folder '" << mLastFolder << "'." << endl;
         } else
           --mRemainingFolders;
         mProcessNextBatchTimer->start( 0, true );
@@ -276,7 +280,9 @@
                                        const KMSearchPattern* pattern,
                                        bool complete )
 {
+    kdDebug() << "BEGIN slotSearchFolderResult" << endl;
     if ( pattern != mSearchPattern ) return;
+    kdDebug() << "Doing slotSearchFolderResult" << endl;
     kdDebug(5006) << k_funcinfo << folder->label() << " found " << serNums.count() << endl;
     mLastFolder = folder->label();
     QValueListIterator<Q_UINT32> it;
@@ -579,7 +585,7 @@

     assert(!folder()->name().isEmpty());
     assert(mOpenCount == 0);
-
+    kdDebug() << "tstaerk was here" << endl;
     kdDebug(5006) << "Creating folder " << location() << endl;
     if (access(QFile::encodeName(location()), F_OK) == 0) {
         kdDebug(5006) << "KMFolderSearch::create call to access function failed."


</pre>

= Meetings =

== Osnabr&uuml;ck 2010 ==

=== Friday ===
* have three computers with me: the [[Latitude 2100]], a Latitude D620 and my [[Nokia N810]]
* train-ride where I locked me out of one of my UMTS cards and exchanged SIM card between my two UMTS modems... don't ask
* kompiled KDEPIM trunk ready on both Latitudes
* good talk with Volker who 
** pointed me to http://techbase.kde.org/Projects/PIM/Akonadi#Akonadi_needs_too_much_space_in_my_home_directory.21
** told me that for the libboost problem on the N810 I will have to install libboost-program-options-dev
** I should start mysql server via /etc/init.d when working graphically as root
** liked my tabletdialog and said the best place for it was kdelibs

=== Saturday ===
* got my USB UMTS working on the [[Latitude 2100]] - just start it using 
 sudo ./umtsmon
* 10:00: Discussion on time table
* snowballs and group photo
* 14:15: Patrick on SyncML
* KDE marketing meeting brainstorming

=== Sunday ===
* KDE marketing and cdash meeting as described [http://community.kde.org/KDE_PIM/Meetings/Osnabrueck_8 here].

== Osnabr&uuml;ck 2009 ==

goals: 
* C++ parser
* menus
* N810
* kioslave
* akonadi

=== Friday ===
got to know Bertjan, discussion on Linux Terminal Servers and KDE 4. Got KDE build environment. David wants to kompile on his N810, I want to use this to improve my tutorial. Got to know Stephen.

=== Saturday ===
we should go for Qt Creator as our C++ parser. Together with Will we verify http://bugs.kde.org/show_bug.cgi?id=147948. Backporting now.

you can get qt creator from (note:this has been corrected on 2009-07-05):
 git clone git://gitorious.org/qt-creator/qt-creator.git

CMakeLists.txt by Bertjan:
<pre>
project(c++parser)
 
cmake_minimum_required(VERSION 2.6)
 
include_directories(${CMAKE_SOURCE_DIR})
message(${CMAKE_SOURCE_DIR} STATUS)
 
set(cplusplus_SRCS AST.cpp ASTVisitor.cpp Array.cpp CheckDeclaration.cpp CheckDeclarator.cpp CheckExpression.cpp CheckName.cpp CheckSpecifier.cpp CheckStatement.cpp Control.cpp CoreTypes.cpp DiagnosticClient.cpp FullySpecifiedType.cpp Keywords.cpp ObjectiveCAtKeywords.cpp Lexer.cpp
LiteralTable.cpp Literals.cpp MemoryPool.cpp Name.cpp NameVisitor.cpp Names.cpp Parser.cpp Scope.cpp Semantic.cpp SemanticCheck.cpp Symbol.cpp Symbols.cpp SymbolVisitor.cpp Token.cpp TranslationUnit.cpp Type.cpp TypeVisitor.cpp PrettyPrinter.cpp)
 
add_library(c++parser SHARED ${cplusplus_SRCS})
</pre>

=== Sunday ===
Had a meeting to discuss web page strategy. Found out you need mysql server for operating akonadi.

== Osnabr&uuml;ck 2008 ==

=== My Blog ===

Here's the first blog in my life. [http://pim.kde.org/development/meetings/ KDE PIM meetings] are for hackers like a bottle of water in a desert. Finally time to hack, hack, hack and only sporadic meetings. And those meetings about development topics. This meeting took place from friday 2008-02-01 till 2008-02-03. This time I remembered to take vacation for the friday. At 10:00 am, I departed from [http://en.wikipedia.org/wiki/Alzey Alzey] and arrived shortly after 14:00 in [http://en.wikipedia.org/wiki/Osnabrueck Osnabr&uuml;ck] at [http://www.intevation.org Intevation] who hosted this meeting (thanks!). Some guys were already there. I finally got to know Thomas who showed me [http://techbase.kde.org/index.php?title=Getting_Started/Set_up_KDE_4_for_development#KDevelop how to use kdevelop for KDE 4]. I used this day to get KDE compile on my notebook. We left the office at 1 am.

==== krep ====

On Saturday, I gave a presentation about my pet project, simplified debugging, see 
I showed how you increase your productivity by using a combination of [http://websvn.kde.org/trunk/KDE/kdesdk/scripts/add_trace.pl add_trace] and [http://websvn.kde.org/trunk/playground/utils/krep/ krep].
My pain points are:
* with grep, I filter away either too much or too less
* changing the pattern for grep requires grep's restart
* grep's restart requires the restart of the application whose output you are sending to grep.
This makes debugging hard.

You use add_trace to change your KDE source code so that every function outputs its name first when called: 
 QString KarmStorage::saveCalendar()
 {
   kDebug(0) << "Entering function" << endl;
Here, the kDebug-line has been added by add_trace. You compile again then and watch the output using krep. This way, you can almost create a call tree. And as soon as I manage to make debugging output as soon as you leave a function, you will actually be able.
You would start e.g.
 ktimetracker 2>&1 | krep
krep then allows you to shrink or expand your view of ktimetracker's output.

==== Windows debugging ====

After my presentation, Jaroslaw gave his presentation about debugging KDE on Windows. There you can use MS Visual C's ide and you have a similar functionality as krep. It was also impressive to see the call stack being displayed while debugging and the performance of the system.

==== KDE 4.1 discussion ====

Interesting discussion about our proceeding for KDE 4.1. Good meeting minutes on the mailing list.

==== Akonadi ====

Akonadi for insiders. Discussing about the state (that I do not know). I preferred finally [http://websvn.kde.org/trunk/KDE/kdepim/ktimetracker/taskview.cpp?r1=754220&r2=770045&sortby=date improving the KDE code].

==== debugging output ====

I asked how you compile your KDE programs so that kDebug messages are not output. The correct answer is use 
 cmake -DCMAKE_BUILD_TYPE=Release .

==== Dinner ====

at the italian

==== kmail ====

Discussion with Ingo about kmail bugs. If we manage to get the body structure (documented in some rfc), the body information, we might be able to close [http://bugs.kde.org/80995 bug 80995].

==== key signing party ====

My kmail is now secured thanks to Ingo taking me into the web of trust by signing my gpg key. The key server even had my old key that I had signed by c't at CeBit 2001.

==== HTML editor ====

Mike recommends me to try QTextEdit, QTextBrowser and QTextDocument for an HTML editor.

==== David ====

Hacking session with David on krep. You should replace 
 foo(QString bar)
by 
 foo(const QString& bar)
whenever possible for the reasons:
* const prevents you from accidentially changing bar
* QString& is in contrast to QString a pass-by-reference, not a pass-by-value. You save the time of copying a QString.
 QString blah;
is by default equivalent to 
 QString blah=QString();
for <code>QString blah;</code> uses the default constructor to construct the object (unless adviced otherwise). This is also valid in a header-file. This is valid for all non-trivial data types, for all data types that have a constructor. So, you still need to initialize an int like this:
 int i=0;
And, pay attention, the following will have a NON DEFINED value:
 QString* qs;
You need to initialize it:
 QString* qs=new QString();
or 
 QString* qs=0;
Thinking complicated is the cool and the ugly part of C programming (C++ is a dialect of C).

We created a benchmark for krep:
 for i in $(seq 1 1 300); do echo $i; done | ./krep
it took 17 seconds (in 
[http://websvn.kde.org/trunk/playground/utils/krep/krep.cpp?revision=770163&view=markup revision 770163]), then we worsened it, then it took 10 seconds (in [http://websvn.kde.org/trunk/playground/utils/krep/krep.cpp?revision=770188&view=markup revision 770188]), then 2 seconds (in [http://websvn.kde.org/trunk/playground/utils/krep/krep.cpp?revision=770205&view=markup revision 770205]).

Deleting a pointer ? Best set it to 0 afterwards so you know it is useless.

We left the office shortly after 2am.

==== commitfilter ====

During the breakfast, we discussed about various things, e.g. the strangest bug reports and mails on mailing lists. There was a discussion that the term "spouse" (e.g. in an address book) is discriminating people who live in relations and cannot marry because e.g. they are gay and live in intolerant countries. So it was proposed to change "spouse" to "partner". I think, so far this is good and understandable. But soon, a guy came up demanding to support polygamy for tolerance's sake. Or, there was a guy stating the letter K would make people commit suicide and demanding from us to change our logo...

What I also learned during breakfast: Did you know that you can easily watch changes in KDE's code base by registering at http://commitfilter.kde.org ? This site will send you a mail when the svn branch (can also be trunk ;) that you select changes. Thanks Thomas for the tip.

==== kexi ====

Talked with Jaroslaw about using kexi as database backend for ktimetracker. Also akonadi could be used. I could start with my kexi experiences at http://websvn.kde.org/trunk/koffice/kexi/tests/newapi/. Writing this blog, I discovered, that even german Autobahnen (motorways) are subjects of ENGLISH wikipedia's articles, so, [http://en.wikipedia.org/wiki/Bundesautobahn_63 here] is one of these important topics, including pictures.

==== kcal error messages ====

Discussion with Cornelius and the others about [https://bugs.kde.org/show_bug.cgi?id=152456 error message handling problems with kcal]. As this involves adding of virtual functions, we will not be able to get the fix in before KDE 5. And then, we will have Akonadi.

== KDE wiki meeting ==
June 28 2009, Berlin
wiki.kde.org abloesen? Migrationspfad?

docs.google.com

TODO for Thorsten:
- verify there is no content to be migrated from wiki.kde.org, use IP from wiki.kde.org (64.22.96.42)
- set up namespace-based search

== GCDS 2009 ==

=== Saturday ===
Saturday was 2009-07-04

* sugarware && sugar on a stick 
lightning talks
* ocrfeeder

"Please do not upgrade/update your system (we are 700!!)"

=== Sunday ===
* attended talks on akonadi

* fixed ktimetracker's right-click-crash, problem: kontact plugin no longer seems to react on right-click

* reproduced that ktimetracker crashes if you quit it by the tray icon

* qt-creator talk from danimo

* got latest qt-creator from gitorious, not from trolltech-server

* went to the party from Nokia

=== Monday ===
* got account at and made merge request on http://qt.gitorious.org/qt-creator/

* kdepim 4.3: backported fix that prevents crashing when right-clicking on a task

* went to the beach

* talk with Thomas that started with html import and ended with the qtextdocument class

= Past =

== Bugs worth remembering ==

* [https://bugs.kde.org/show_bug.cgi?id=85328 KDE bug to add focus tracking]
* http://bugs.kde.org/show_bug.cgi?id=153448: cannot search in account, only in sub-folders
* https://bugs.kde.org/show_bug.cgi?id=152456: when saving fails, there is no info if disk is full or locking did not work.
* http://bugs.kde.org/show_bug.cgi?id=159976: KCal::Event's hasEndDate() always delivers true
* http://bugs.kde.org/show_bug.cgi?id=97247: meeting invitation times wrong on reply
* [[170512]] - wrong time zone in invitation display
* [[Qtreewidget-bugs]]
* [https://bugs.kde.org/show_bug.cgi?id=169958 idletime detection does not work]
* [[80995]] - attachment icon not shown immediately
* https://bugs.kde.org/show_bug.cgi?id=145091: problems accepting outlook invitation
* [[147948‎]] - kio_fish stalling
* [https://bugs.kde.org/show_bug.cgi?id=198997 ktimetracker crashes when right-clicking onto a task]
* [http://bugs.kde.org/194867 ktimetracker crashes when quitting via the systray icon]

= See also =
* https://bugs.kde.org/enter_sysadmin_request.cgi