< PIMRevision as of 11:52, 25 February 2011 by Bernhard (talk | contribs) (→Problem points: meinproc point improved.)(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff) This page covers topics related to the KDE PIM Suite on MS Windows NT. Contents 1 Building 2 Problem points 2.1 Documentation of KDE 2.2 LDAP Support 2.3 Search 2.4 Nepomuk 3 Some notes from the original porting project 3.1 Integration into the Windows Explorer & Desktop 3.1.1 Registry settings for default apps and services 184.108.40.206 Using MAPI 220.127.116.11 KDE-related notes 4 Links Building To build KDE PIM for Windows use [Getting_Started/Build/KDE4/Windows/emerge emerge]] You should be able to get executables just by calling emerge kdepim. Problem points Status Feature Description Contact TO DO Documentation of KDE Due to meinproc4 crashes documentation build is turned off from all kde products. The underlying defect could affect running products as well. TO DO LDAP Support Enabling KLdap Andre Heinecke <[email protected]> TO DO Search Provide a search backend TO DO Nepomuk Provide a working Nepomuk Documentation of KDE Currently as of 22.2.2010 in all KDE builds for Windows Documentation build is turned off because of BUG263828 Meinproc4 crashes. If this is a defect in libxml2 or iconv, this could affect other KDE products during runtime as well. Meinproc4 is just an XSLT processor. LDAP Support 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. Search Strigideamon does not compile for Windows NT at the moment, so apart from Virtuoso/Nepomuk there is no Search for KDE PIM Software available. Nepomuk Nepomuk only supports Virtuoso as Database backend. Virtuoso can not be installed through the KDE-Windows installer, so Nepomuk is currently not availabe for Windows with a working backend. Some notes from the original porting project Integration into the Windows Explorer & Desktop Note 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... Registry settings for default apps and services 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. HKCU\Software\Clients\StartMenuInternet key is used to specify default web browser; could be set to Konqueror HKCU\Software\Clients\StartMenuInternet\app.exe\shell\open\command key is used for "Internet" start menu shortcut, can be set to Konqueror. Note from the KB - "The command might open the browser on the users home page, for example. However, it might launch some other introductory user interface that the ISV feels is appropriate." So this is not the same as 'default browser' setting. HKCU\Software\Clients\Mail\Appname - registered email client, there can be more entries within the 'Mail' node. Adding KMail here makes it available for users to select as a default browser using 'Set Default Programs' system window. HKCU\Software\Clients\Mail - default email client, 'Windows Mail' by default; could be set to KMail. HKCU\Software\Clients\Calendar\Appname - registered calendar application, there can be more entries within the 'Calendar' node. See the note for HKCU\Software\Clients\Mail\Appname. HKCU\Software\Clients\Calendar - default calendar application, 'Windows Calendar' on Vista; could be set to KOrganizer. HKCU\Software\Clients\Contacts\Appname - registered contacts client, there can be more entries within the 'Contacts' node. See the note for HKCU\Software\Clients\Mail\Appname. HKCU\Software\Clients\Contacts - default contacts application, 'Address Book' by default; could be set to KAddressBook. HKCU\Software\Clients\News\Appname - registered newsgroup client, there can be more entries within the 'News' node. See the note for HKCU\Software\Clients\Mail\Appname. HKCU\Software\Clients\News - default newsgroup application, 'Windows Mail' by default; could be set to KNode. 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. Using MAPI 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). KDE-related notes KDElibs execute default web browser or email client for protocols like http(s): and mailto: via QDesktopServices::openUrl(), which in turn uses ShellExecute(). openUrl() is widely used in Qt e.g. for hyperlinks in text boxes and label widgets. A general rule of KDE/win: not to duplicate registry settings in any rc file and use default applications if possible, to avoid changing behaviour expected by users. jstaniek 12:06, 18 June 2008 (CEST): Before LinuxTag I've performed some tests of setting default clients, and looks like it's is not possible to set onlt writing registry entries. Some API calls may be needed, especially because locked at least one registry key is locked for writing during the session. Links The KDE on Windows Project Missing features of kdelibs on Windows - KDE PIM may depend on them Retrieved from "https://community.kde.org/index.php?title=PIM/MS_Windows&oldid=53951" Categories: PIMMS Windows Content is available under Creative Commons License SA 4.0 unless otherwise noted.