This page covers topics related to the KDE PIM Suite on MS Windows NT kernel (which means running on Windows Desktop versions NT or newer like XP, Vista or 7).
To build KDE PIM for Windows use emerge. For documentation about emerge please see 
You should be able to get executables just by calling emerge kdepim.
|DONE||Documentation of KDE||Due to meinproc4 crashes documentation build is turned off from all kde products.|| [mailto: < >]
|TO DO||LDAP Support||Enabling KLdap|| Andre Heinecke <firstname.lastname@example.org>
|DONE||Akonadi Notifications||Akonadi Notifications are not communicated correctly to the GUI|| [mailto: <>]
|IN PROGRESS||Search||Provide a search backend|| Andre Heinecke <email@example.com>
|IN PROGRESS||Nepomuk||Provide a working Nepomuk|| Andre Heinecke <firstname.lastname@example.org>
|TO DO||Akonadi startup/shutdown||Decide how akonadi should be started/stopped on Windows|| [mailto: <>]
|TO DO||Image view in Mailviewer||Images in the Mailviewer are not shown correctly|| [mailto: <>]
|TO DO||Configuration dialog asks for save every time||The configuration dialog asks the user to confirm his changes even if no changes were made|| [mailto: <>]
|TO DO||Design||Make KDEPIM feel native on Windows|| [mailto: <>]
|TO DO||Integrate with GPG4Win||Use GPG4Win to provide Crypto support on Windows||Andre Heinecke <email@example.com>|
For more details about the problem check the bug report: BUG263828
There is a workaround and documentation can be built.
OpenLDAP does not build well for Windows on Windows, for this reason there is no working OpenLDAP-src target in emerge, if you want LDAP Support you have to manually install OpenLDAP into your KDE Enviornment before building kdepimlibs.
Since Windows has native LDAP support with winldap it is easily possible to use that, an Obstacle for this is that also kdepimlibs is built with -DUNICODE it expects all system LDAP calls to return ASCII so you would have to do some conversions mappings there. A bit code for that is already in kdepimlibs/kldap/w32ldaphelp.h but it is only finished for WinCE not for WinNT.
Strigideamon does not compile for Windows NT at the moment, so apart from Virtuoso/Nepomuk there is no Search for KDE PIM Software available. Currently Virtuoso gets started in the Enterprise 5 Package on some systems and on others not. There might be a packaging problem or timeouts that are reached. Strigi indexing complains that it is disabled, so even with a running Nepomuk there is no search available at the moment.
Nepomuk only supports Virtuoso as Database backend. For a virtuoso installation to work regsvr32 has to be called on the virtuoso odbc driver at the moment. Soprano has to be fixed so that it checks if that driver is availble and if not registers it.
DBus problem that has been fixed in newer versions of DBus > 1.4.1
Oxygen Theme looks strange and alien on Windows 7 default style but ok on Windows XP style Currently the Packaged Style in the Enterprise 5 package is optimzed for windows 7
Best solution would be to check what the System Style is or package the KDE-Systemsettings to customize that style
Akonadi startup can take a while on slow systems which delays the first Kontact startup.
Once akonadi is running it can not be stopped from the UI
To integrate with gpg4win one has to copy the gpg2.exe in the gpg4win/bin directory to gpg.exe in the same directory. Otherwise no backends will be found. This can be fixed by packaging a better gpg4win-dev package.
|jstaniek 22:01, 14 January 2008 (CET): TortoiseSVN is GPLed SVN client which is nicely integrated with Windows Explorer. Perhaps we can use its source code as a reference...|
Introduction: We can detect whether KMail is the default e-mail client. If set as default, KMail should act as a default mailer, and thus be invoked automatically for actions like RMB "Send To -> E-mail Recipient". This shall be also reused by others for KOrganizer and Konqueror. The solution is relatively simple modifications to the Windows Registry. See Mozilla's solution.
First, we can use HKLM node for system-global settings or HKCU node for current-user-only settings. If the attempt to set the value in HKLM fails, usually because of unsufficient permissions, HKCU should be used. As expected, HKCU overrides HKLM settings. See KB297878. Below we'll use HKCU.
From the KB: After updating the registry keys, the application broadcasts the WM_SETTINGCHANGE message with wParam = 0 and lParam pointing to the null-terminated string "Software\Clients\StartMenuInternet" to notify the operating system that the default client has changed.
HKLM\Software\Clients\AppName\DllPath points to a dll implementing MAPI interface. Internet Explorer uses Windows Messaging by default to invoke a mailer on a mailto: link. Only if the MAPI install is misconfigured will it resort to directly accessing the mailto association key. Example implementation of MAPI services is Thundebird's mozMapi32.dll (the key is usualle equal to C:\Program Files\Mozilla Thunderbird\mozMapi32.dll).