KDE TechBase - User contributions [en]

Thread:Talk:Development/Languages/Python/PyKDE Homepage gone?

2013-01-31T19:08:17Z

Bernhard: New thread: PyKDE Homepage gone?

The link to the PyKDE Homepage at http://www.riverbankcomputing.co.uk/software/pykde/intro is gone.
There is no trace of PyKDE4 at riverbankcomputing, so this cannot be fixed I guess. What happened to it?
How could it be fixed?

Talk:Development/Languages/Python

2013-01-31T19:08:17Z

Bernhard: Talk page autocreated when first thread was posted

Development/Languages/Python

2013-01-31T19:05:56Z

Bernhard: /* Applications using PyKDE */ Adding synaptiks

Python is a powerful object oriented, dynamic language. You can find out more about the language itself on the Python website at http://www.python.org/.

Two important pieces of software are needed to develop KDE applications using Python, [http://www.riverbankcomputing.co.uk/software/pyqt/intro PyQt] and PyKDE. PyQt provides Python support for the Qt library which KDE is built on. PyQt can be obtained at http://www.riverbankcomputing.co.uk/software/pyqt/ . Riverbank Computing has a lot of good documentation about how to use PyQt to create pure Qt applications. If you are new to KDE / Python development, then learning how to use PyQt is the best first step.

PyKDE builds on top of PyQt and adds Python support for KDE's libraries and technologies.

PyKDE is distributed as part of the kdebindings module. Stable releases can be downloaded from the normal [http://kde.org/download/ KDE download page], although it is usually easier to install pre-built packages from your operating system distribution. You can also obtain PyKDE from KDE's subversion repository:

svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdebindings/python/pykde4

The code in subversion can be browsed online via http://websvn.kde.org/trunk/KDE/kdebindings/python/pykde4/.

Or from KDE's git repository:

git clone git://anongit.kde.org/pykde4

==Documentation and Tutorials==
* [http://www.riverbankcomputing.co.uk/software/pyqt/intro PyQt home page and documentation]
* [[/Using PyKDE 4|Using PyKDE 4]]
* [http://api.kde.org/pykde-4.3-api/toc.html PyKDE 4.3 Documentation]
* [http://api.kde.org/pykde-4.3-api/modules.html PyKDE 4.3 API class reference]
* [http://api.kde.org/pykde-4.2-api/ PyKDE 4.2 API class reference]
* [[/PyKDE_WebKit_Tutorial|PyKDE WebKit Tutorial]], a simple web browser application in PyKDE
* [[Development/Tutorials/Python introduction to signals and slots|introduction to signals and slots]]
* [[Development/Tutorials/Python-hello world|Hello world]]. An example that you can also use as a starting point for your development.
* [http://www.rkblog.rk.edu.pl/w/p/introduction-pyqt4/ Introduction article about PyQt4]
* [http://lateral.netmanagers.com.ar/stories/BBS47.html PyQt by Example]
* [[/PyKDE_DBus_Tutorial|Python DBus Tutorial]]. See how to call dbus methods from PyKDE.
* [[/PyKDE_Knotify_Tutorial|Python KNotify Tutorial]]. How to use Notification and Jobs in your Applications
* [[Development/Tutorials/Phonon/Introduction/Python|Phonon Example]]
* [[Development/Tutorials/Plasma#Plasma_Programming_with_Python|Plasma tutorials]]

===KDE 3 and PyKDE 3===
Documentation and tutorials for the older PyQt and PyKDE 3.
* [http://vizzzion.org/?id=pyqt Python-Qt tutorial] '' In this tutorial, the basic steps of creating a Qt-based application with PyQt are explained. ''

==Further reading and information==
*[http://www.riverbankcomputing.com/mailman/listinfo/pyqt PyQt and PyKDE mailing list]
*[http://www.riverbankcomputing.co.uk/software/pykde/intro PyKDE Homepage]
*[http://www.diotavelli.net/PyQtWiki The PyQt and PyKDE community Wiki]
*The book [http://www.qtrac.eu/pyqtbook.html Rapid GUI Programming with Python and Qt] is available and covers Qt 4 programming with Python.
*The IRC channel ''#kubuntu-devel'' on freenode often has PyKDE programmers in it.
*The IRC channel ''#pyqt'' on freenode is used by some PyQt application developers.

==Applications using PyKDE==
*[http://utils.kde.org/projects/printer-applet/ printer-applet]
*[http://websvn.kde.org/trunk/KDE/kdeadmin/system-config-printer-kde/ system-config-printer-kde]
*[http://websvn.kde.org/trunk/extragear/utils/guidance-power-manager/ Guidance Power Manager], a battery applet
*[https://code.launchpad.net/ubiquity/trunk Ubiquity], installer for Kubuntu
*[https://code.launchpad.net/~ubuntu-core-dev/gdebi/ubuntu GDebi], .deb package installer
*[https://code.launchpad.net/~jr/install-package/trunk install-package], graphical apt-get
*[http://draketo.de/light/english/pyrad pyRad], wheel type command interface
*[https://projects.kde.org/projects/kde/kdebindings/pykde4/repository/revisions/master/show/examples/ some examples are in the PyKDE source]
*[https://projects.kde.org/projects/kde/kdeexamples/repository/revisions/master/show/bindings/python/ there are also python examples in the kdeexamples project]
*[http://websvn.kde.org/trunk/KDE/kdegames/kajongg/ Kajongg], a board game
*[http://synaptiks.readthedocs.org Synaptiks], a touchpad configuration and management tool.
[[Category:Python]]

Schedules/KDE4/4.7 Feature Plan

2011-08-31T15:14:55Z

Bernhard: /* kdelibs */ added credits for the klockfile change

This is a list of planned features for the SC 4.7 release.

See also:

*[[Schedules/KDE4/4.7 Release Schedule]]
*[[Schedules/KDE4/4.7 Release Goals]]
*[[Schedules/KDE4/4.6 Feature Plan]] (previous major release)

 Legend:

*todo => not started yet
*in-progress => started, but not completed yet
*done => completed

__TOC__

 

= kdelibs =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

{{FeatureDone
|KLocale
|Number grouping support
|john@layt.net|John Layt}}

{{FeatureDone
|KLocale
|Narrow date name format support
|john@layt.net|John Layt}}

{{FeatureDone
|KLocale
|Week Numbers support
|john@layt.net|John Layt}}

{{FeatureDone
|kdecore/io/klockfile
|For 4.7.1: Implement locking on non-NFS systems using O_EXCL. Good for VFAT, CFIS and other filesystems, as it makes KConfig work and thus many KDE Applications. Details in #203554. Conducted by KDAB and Intevation; funded by IT Services of ETH Zurich.
|faure@kde.org|David Faure}}

{{FeatureInProgress
|KLocale
|Windows Backend
|john@layt.net|John Layt}}

{{FeatureInProgress
|kdeui
|New date/time edit widgets from kdepim
|john@layt.net|John Layt}}

{{FeatureInProgress
|KHelpMenu
|Fast action searching
|afiestas@kde.org|Alex Fiestas}}

{{FeatureInProgress
|KFilePlaces
|Activity-specific Places
|j.maceachern@gmail.com|Jeffery MacEachern}}

{{FeatureInProgress
|KCookieJar
|Storing cookies in KWallet
|fid@gpul.org|José Millán Soto}}

{{FeatureInProgress
|KHTML
|WebIDL usage
|maksim@kde.org|Maksim Orlovich}}

{{FeatureTodo
|KHTML
|Accessibility improvements
|maksim@kde.org|Maksim Orlovich}}

{{FeatureTodo
|Nepomuk
|Query term class to query graph meta data
|trueg@kde.org|Sebastian Trueg}}

{{FeatureTodo
|Plasma
|Preconfigurable plasmoids
|dpalacio@orbitalibre.org|David Palacio}}

|}

 

= kde-baseapps =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|Dolphin|Support Fwd/Back Mouse Buttons|sebastian@sebastian-doerner.de|Sebastian Dörner}}
{{FeatureDone|Dolphin|Polish the default user interface to minimize visual clutter (see http://ppenz.blogspot.com/2011/03/menu-bars.html)|peter.penz19@gmail.com|Peter Penz}}
{{FeatureDone|Dolphin|Improve user interface for searching files and metadata|peter.penz19@gmail.com|Peter Penz}}
{{FeatureTodo|Settings|Improve proxy configuration dialog|adawit@kde.org|Dawit Alemayehu}}

{{FeatureInProgress
|Locale KCM
|Support for Number Grouping, Windows Backend, Country Subdivsions
|john@layt.net|John Layt}}

{{FeatureInProgress
|nspluginviewer
|npruntime support improvements
|maksim@kde.org|Maksim Orlovich}}

{{FeatureTodo
|Dolphin
|Popup menu for advanced queries on the metadata display
|trueg@kde.org|Sebastian Trueg}}

|}

 

= kde-runtime =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureInProgress|kio_sftp|async download support|asn@cryptomilk.org|Andreas Schneider}}
{{FeatureInProgress
|Locale definition files
|Migrate Country and Currency Codes to xml/po formats, re-arrange l10n files including settings and flags, add Subdivision code files.
|john@layt.net|John Layt}}
{{FeatureTodo|kio-upnp-ms|Merge from playground (https://projects.kde.org/projects/playground/base/kio-upnp-ms/) into kde-runtime|nsm.nikhil@gmail.com|Nikhil Marathe}}
{{FeatureDone|network:/ kio-slave|port to Cagibi 0.2|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureDone|Nepomuk Datamanagement Service|Merge it into the master branch|handa.vish@gmail.com|Vishesh Handa & Sebastian Trueg}}
{{FeatureDone|Port Strigi Service to DMS|The Strigi Service needs to use the DMS API|handa.vish@gmail.com|Vishesh Handa & Sebastian Trueg}}

{{FeatureDone
|Nepomuk
|KCM to manage the removable storages to index
|trueg@kde.org|Sebastian Trueg}}

|}

 

= kde-workspace =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

{{FeatureDone|System Settings/keyboard|Allow a shortcut per keyboard layout (bug 224489)|arysin@mail.com|Andriy Rysin}}
{{FeatureDone|System Settings/keyboard|Session management for keyboard layouts (bug 52095, 174948)|arysin@mail.com|Andriy Rysin}}
{{FeatureDone|klipper|Support qrcode as well as datamatrix for mobile barcodes|sune@vuorela.dk|Sune Vuorela}}
{{FeatureDone|weather|Support debian weather|sune@vuorela.dk|Sune Vuorela}}
{{FeatureDone|Oxygen|Various widgets polishing (scrollbars, progressbars, sliders, toolbuttons, menu and menubar selection, etc.)|hugo@oxygen-icons.org|Hugo Pereira Da Costa}}
{{FeatureDone|Oxygen|Implement kwin's new shadow system for menus, drop-downlists, etc.|hugo@oxygen-icons.org|Hugo Pereira Da Costa}}
|-

! style="text-align: center;" colspan="4" | Plasma
{{FeatureInProgress
|Plasma Clock/Calendar
|improve usability, settings, akonadi and holiday data. See Plasma wiki.
|john@layt.net|John Layt}}
{{FeatureDone
|Plasma Desktop
|launch krunner when the user starts typing
|vitorboschi@gmail.com|Vitor Boschi}}
|-

! style="text-align: center;" colspan="4" | KDM
{{FeatureDone
|KDM
|GRUB2 support for KDM (see http://ksmanis.wordpress.com/2011/04/21/hello-planet-and-grub2-support-for-kdm/)
|konstantinos.smanis@gmail.com|Konstantinos Smanis}}
|-

! style="text-align: center;" colspan="4" | KWin
{{FeatureDone|Compositor|OpenGL 2.x/OpenGL ES 2.0 compositing backend (see http://www.kdenews.org/2011/02/18/kwin-embraces-new-platforms-opengl-es-20-support)|mgraesslin@kde.org|Martin Gräßlin}}
{{FeatureDone|Compositor|New Shadow System (see http://blog.martin-graesslin.com/blog/2011/03/new-kwin-shadows/)|mgraesslin@kde.org|Martin Gräßlin}}
{{FeatureDone|Effects|Effect to render outlines|mgraesslin@kde.org|Martin Gräßlin}}
{{FeatureDone|Decorations|Do not require a decoration|mgraesslin@kde.org|Martin Gräßlin}}
{{FeatureInProgress|Core|Export most recently used windows to an X property|mgraesslin@kde.org|Martin Gräßlin}}
{{FeatureInProgress|BoxSwitch Effect|Animated Selection (see http://blog.martin-graesslin.com/blog/2011/02/is-kwin-rocket-science/)|mgraesslin@kde.org|Martin Gräßlin}}
{{FeatureInProgress|libkwineffects|API cleanup|mgraesslin@kde.org|Martin Gräßlin}}
{{FeatureTodo|libkwineffects|JavaScript bindings for writing Effects|mgraesslin@kde.org|Martin Gräßlin}}
{{FeatureInProgress|Mouse Emulation|Better accessibility support in mouse emulation|mgraesslin@kde.org|Martin Gräßlin}}
{{FeatureDone|kwin|Add multi head support|alberto@mattea.info|Alberto Mattea}}
{{FeatureInProgress|kwin|DBusMenu in Windeco|megabigbug@yahoo.fr|Lionel Chauvin}}
{{FeatureDone|ksplashx|Add multi head support|alberto@mattea.info|Alberto Mattea}}
{{FeatureTodo|krunner|Add multi head support|alberto@mattea.info|Alberto Mattea}}
{{FeatureInProgress|kwinrules kcm|UI cleanup (see https://git.reviewboard.kde.org/r/101041/)|thomas.luebking@gmail.com|Thomas Lübking}}
{{FeatureInProgress|kwincompositing kcm|Rearm unsafe OpenGL precheck (see https://git.reviewboard.kde.org/r/101061/)|thomas.luebking@gmail.com|Thomas Lübking}}
{{FeatureInProgress|PresentWindows Effect|Better highlight indication & close button handling)|thomas.luebking@gmail.com|Thomas Lübking}}
{{FeatureInProgress|general|Remove jargon from user interface. Remove all instances of Akonadi/Nepomuk related jargon from the desktop, replace with meaningful text where needed.|wstephenson@kde.org|Will Stephenson}}
|}

 

= kdeedu =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureDone|Marble|Bookmark Manager|earthwings@gentoo.org|Dennis Nienhüser, Thibaut Gridel}}
{{FeatureDone|Marble|QML Bindings: GPS Tracking|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureInProgress|Marble|Routing API|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Offline Address Search|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Support monav version 0.3|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Polish the Map Wizard: simpler UI, comprehensive validation of user input immediately on each page|bbeschow@cs.tu-berlin.de|Bernhard Beschow}}
{{FeatureInProgress|Marble|Reduce memory footprint of cached tiles|bbeschow@cs.tu-berlin.de|Bernhard Beschow}}
{{FeatureTodo|Marble|Separate thread for tile loading and texture blending (not texture mapping at the moment) for more smooth browsing|jmho@c-xx.com|Jens-Michael Hoffmann, Bernhard Beschow}}
{{FeatureTodo|Marble|Tile loading "read ahead" when idle, prerequisite: threaded tile loading|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureDone|Marble|Multi threaded texture mapping|bbeschow@cs.tu-berlin.de|Bernhard Beschow}}
{{FeatureTodo|Marble|Implement mouse cursor wrapping a la Okular or Gwenview|bbeschow@cs.tu-berlin.de|Bernhard Beschow}}
{{FeatureInProgress|Marble|Manipulate Gps track data|tgridel@freedotfr|Thibaut Gridel}}
{{FeatureInProgress|Cantor|Integrate the Qalculate backend|agostinelli@gmail.com|Matteo Agostinelli}}
{{FeatureDone|Kalzium|Use KUnitConversion for all the Unit handling|etienne.rebetez@oberwallisch|Etienne Rebetez}}
{{FeatureDone|KTurtle|Add getdirection command
|nielsslot@gmaildotcom|Niels Slot}}
{{FeatureTodo|KTurtle|Add modulo command
|nielsslot@gmaildotcom|Niels Slot}}
{{FeatureDone|Step|Copy-and-Paste of items|kde@voecking.net|Sebastian Vöcking}}
{{FeatureDone|Step|Zoom on mouse wheel|kde@voecking.net|Sebastian Vöcking}}
{{FeatureDone|Step|Automatic expanding canvas|kde@voecking.net|Sebastian Vöcking}}
{{FeatureInProgress|Rocs|Auto - Handling of the Canvas|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureDone|Rocs|Remove the thread for QtConcurrent on he core|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureInProgress|Rocs|Polish the User Interface|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureDone|Rocs|New Plugin for Automaticaly Graph Generation|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureInProgress|Rocs|Bugfixes in the List Plugin|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureInProgress|Rocs|Speedup in the drawing code|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureInProgress|Rocs|Kalgebra backend|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureDone|Rocs|Transform graph edges plugin|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureDone|Rocs|Assign values to edges/nodes plugin|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureDone|Kalzium|Titration calculator|TRINGALINVENT@libero.it|Luca Tringali}}
{{FeatureInProgress|KStars|SQLite Database of NGC Objects|victor.carbune@kdemail.net|Victor Carbune|}}
|}
 

= kdepim =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

{{FeatureInProgress|KAlarm|Port to Akonadi|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Allow reminders after the main alarm|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Provide wake-from-suspend option for alarms|djarvie@kde.org|David Jarvie}}

{{FeatureInProgress
|KHolidays
|Add support for Holiday Types and Observance Types
|john@layt.net|John Layt}}

{{FeatureDone|Akonadi-contacts/kaddressbook|Show 2d barcodes of contact data|sune@vuorela.dk|Sune Vuorela}}
|}

 

= kdeplasma-addons =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureInProgress|Adjustable Clock|Plasmoid for displaying date and time in very customizable way|emdeck@gmail.com|Michał Dutkiewicz}}
{{FeatureInProgress|Comic Plasmoid|Support random comic strips|mat69@gmx.net|Matthias Fuchs}}
{{FeatureDone|Comic Plasmoid|Support creation of comic Comic Book Archive files|mat69@gmx.net|Matthias Fuchs}}
{{FeatureDone|Comic Plasmoid|Highlight comics that have a new comic strip|mat69@gmx.net|Matthias Fuchs}}
{{FeatureTodo|Events Runner|Support parsing weekdays (e.g. "in next monday"|alexey.noskov@gmail.com|Alexey Noskov}}
|}

 

= kdetoys =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureDone|KTeaTime|Port to KStatusNotifierItem|miha@noughmad.eu|Miha Čančula}}
{{FeatureInProgress|KTeaTime|New svg based status icons|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureInProgress|KTeaTime|Support categories|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|KTeaTime|Improved command line|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|KTeaTime|Tea runner|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|KTeaTime|Port to KConfigXT|kde@hilefoks.org|Stefan Böhmann}}

|}

 

= kdesdk =

{| cellspa/cing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureInProgress|Lokalize|Remote translation memories|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureInProgress|Lokalize|QA: translation checks against user-specified regex-based rules|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Integrate snowball stemmer for glossary|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Continue implementing XLIFF spec|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Segmentation [editing] functionality|shafff@NOSPAMukr.net |Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Integrate with nepomuk (fast stats retrieval, tag cloud - incl sharing!)|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|loading compressed files and then saving them back in the original compression format (bug 65518)|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureInProgress|Okteta|Properly support strings (various Unicode encodings) in structures tool|alex.richardson@gmx.de|Alex Richardson}}
{{FeatureTodo|Okteta|Add custom datatypes to structures tool|alex.richardson@gmx.de|Alex Richardson}}
{{FeatureInProgress|Okteta|Add tool to convert between char encodings|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureInProgress|Umbrello|QDockWidget based interface|elv1313@gmail.com|Emmanuel Lepage Vallee}}
{{FeatureInProgress|Umbrello|KDE4 icon theme and eye candies|elv1313@gmail.com|Emmanuel Lepage Vallee}}
{{FeatureTodo|Umbrello|Replace the current code viewer with katepart|elv1313@gmail.com|Emmanuel Lepage Vallee}}
{{FeatureDone|Umbrello|Add a zoom widget in the statusbar|elv1313@gmail.com|Emmanuel Lepage Vallee}}
{{FeatureDone|Kate|Add a new search in files plugin|kare.sars@iki.fi|Kåre Särs}}
|}
 

= kdegames =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureInProgress|KBreakout|Level editor|julian.helfferich@gmail.com|Julian Helfferich}}
{{FeatureInProgress|KBreakout|Load levelset option + 2 new levelsets|julian.helfferich@gmail.com|Julian Helfferich}}
{{FeatureTodo|KBreakout|Port to QGraphicsView|julian.helfferich@gmail.com|Julian Helfferich}}
{{FeatureInProgress|KPat|Create new saved game format that stores undo/redo history|parker.coates@gmail.com|Parker Coates}}
{{FeatureInProgress|libtagaro|Move first version into the kdegames module|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureTodo|libtagaro|Use the new library: at least in Granatier and Kolf (to replace existing static source copies) and KDiamond|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureInProgress|Palapeli|Cleanup interface|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureDone|Palapeli|Reduce memory consumption for big puzzles|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureInProgress|all games|Add useful fullscreen mode + option to switch between fullscreen/window|kossebau@kde.org|Friedrich W. H. Kossebau}}
|}

 

= kdenetwork =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureDone|KGet|Working Mms plugin|eortiz@uci.cu|Ernesto Rodriguez Ortiz}}
{{FeatureInProgress|KGet|Support for connection limit to servers|mat69@gmx.net|Matthias Fuchs}}
|}

 

= kdegraphics =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureInProgress|Okular|Directory support in Comic Book Generator|dpalacio@orbitalibre.org|David Palacio}}
{{FeatureInProgress|Okular|7zip support in Comic Book Generator|dpalacio@orbitalibre.org|David Palacio}}
{{FeatureDone|libksane|Enable gui less operation|kare.sars@iki.fi|Kåre Särs}}
{{FeatureDone|libksane|Add a way to get scanner device list|kare.sars@iki.fi|Kåre Särs}}
{{FeatureInProgress|Gwenview|Compare mode|agateau@kde.org|Aurélien Gâteau}}
{{FeatureTodo|Gwenview|Merge "Semantic Information" and "Meta Information" sidebar groups|agateau@kde.org|Aurélien Gâteau}}
|}

Projects/PIM/Akonadi/Database

2011-08-25T10:05:25Z

Bernhard: /* Sqlite */ one more link about sqlite concurrency

= Akonadi Server Database Internals =

This page contains information about how the Akonadi server uses its internal SQL database. This is purely for Akonadi server developers, you are NOT supposed to use the database yourself, by-passing Akonadi!

== Database Schema ==

* [http://api.kde.org/kdesupport-api/kdesupport-apidocs/akonadi/html/akonadi_server_database.html Visualization]
* Code is in server/src/storage
** akonadidb.xml contains the schema in an XML format
** dbinitializer* contains the code to create tables out of that
**updatedb.xml contains schema update instructions
** dbupdater.* executes those

== Backends ==

Akonadi can use different SQL backends. The following documents backend-specific details.

In general, backend specific configuration and setup code can be found in server/src/storage/dbconfig*.

There are three possible operation modes for backends, most only support a subset:
* Embedded: No server process, database is completely integrated into the Akonadi process
* Internal server: Akonadi manages the database server process itself, taking care of starting/stopping and configuring it.
* External server: Akonadi connects to an already running database server.

Selecting and configuring the different backends can be done in ~/.config/akonadi/akonadiserverrc, details on the available options can be found here: [http://api.kde.org/kdesupport-api/kdesupport-apidocs/akonadi/html/classAkonadi_1_1DataStore.html akonadiserverrc options]

=== MySQL ===

Status: working, default backend for desktop systems

Supported modes: Internal, External

MySQL server configuration files for the internal mode can be found here: server/src/storage/mysql-global*.conf.

=== Sqlite ===

Status: working with limitations, default backend for mobile systems

Supported modes: Embedded

Known issues:
* Requires newer version than the default Qt one.
* Requires patched QtSql driver to fix concurrency issues (Akonadi ships a fork of the driver with the necessary changes)
* Slower than MySQL (see e.g. http://bertjan.broeksemaatjes.nl/node/53), based on our measurments about 2-5x on the query level, but still in the milliseconds range, so that's probably not a big issue.
* Mutex-based transaction serialization in Akonadi (required because SQlite's support of concurrency might not be enough) can block clients while background operations such as a IMAP sync are going on. This is the real killer here, the more clients (including background processes like indexing) are accessing the data, the more blocking you experience. Background http://www.sqlite.org/faq.html#q5 , http://www.somacon.com/p369.php , http://www.sqlite.org/lockingv3.html , http://www.mail-archive.com/sqlite-users%40sqlite.org/msg43873.html

=== PostgreSQL ===

Status: unknown

Supported modes: Internal, External

TODO

=== Virtuoso ===

Status: not working

Supported modes: External

Proof-of-concept work was done during Akademy 2010, up to the point where the database could be created successfully. Known issues:

* Some column names used by Akonadi are Virtuoso keywords
* Some of the first INSERT query fails with a signed vs. unsigned int mismatch/overflow.

Completion of Virtuoso support is considered non-trivial and probably requires a lot of work on the Akonadi side, the SQL dialect is too different from what we support so far.

=== MySQL/Embedded ===

Status: not working

Supported modes: Embedded

Development stopped, MySQL/Embedded does not support transactions.

== Tools ==

=== Generic ===

''akonadiconsole'' has support for browsing the database and run arbitrary SQL queries. See [[Development/Tutorials/Akonadi/Application]].

=== MySQL ===

There are convenience scripts for running mysqld in the configuration used by Akonadi as well as (and probably more useful) running the MySQL command line client connected to the Akonadi database. See server/src/storage/akonadi-mysql-[client|server].sh.

[[Category:Akonadi]]

Projects/PIM/Akonadi/Database

2011-08-25T09:56:48Z

Bernhard: /* Sqlite */ adding link about SQlite's concurrency support and its limitations

= Akonadi Server Database Internals =

This page contains information about how the Akonadi server uses its internal SQL database. This is purely for Akonadi server developers, you are NOT supposed to use the database yourself, by-passing Akonadi!

== Database Schema ==

* [http://api.kde.org/kdesupport-api/kdesupport-apidocs/akonadi/html/akonadi_server_database.html Visualization]
* Code is in server/src/storage
** akonadidb.xml contains the schema in an XML format
** dbinitializer* contains the code to create tables out of that
**updatedb.xml contains schema update instructions
** dbupdater.* executes those

== Backends ==

Akonadi can use different SQL backends. The following documents backend-specific details.

In general, backend specific configuration and setup code can be found in server/src/storage/dbconfig*.

There are three possible operation modes for backends, most only support a subset:
* Embedded: No server process, database is completely integrated into the Akonadi process
* Internal server: Akonadi manages the database server process itself, taking care of starting/stopping and configuring it.
* External server: Akonadi connects to an already running database server.

Selecting and configuring the different backends can be done in ~/.config/akonadi/akonadiserverrc, details on the available options can be found here: [http://api.kde.org/kdesupport-api/kdesupport-apidocs/akonadi/html/classAkonadi_1_1DataStore.html akonadiserverrc options]

=== MySQL ===

Status: working, default backend for desktop systems

Supported modes: Internal, External

MySQL server configuration files for the internal mode can be found here: server/src/storage/mysql-global*.conf.

=== Sqlite ===

Status: working with limitations, default backend for mobile systems

Supported modes: Embedded

Known issues:
* Requires newer version than the default Qt one.
* Requires patched QtSql driver to fix concurrency issues (Akonadi ships a fork of the driver with the necessary changes)
* Slower than MySQL (see e.g. http://bertjan.broeksemaatjes.nl/node/53), based on our measurments about 2-5x on the query level, but still in the milliseconds range, so that's probably not a big issue.
* Mutex-based transaction serialization in Akonadi (required because SQlite's support of concurrency might not be enough) can block clients while background operations such as a IMAP sync are going on. This is the real killer here, the more clients (including background processes like indexing) are accessing the data, the more blocking you experience. Background http://www.sqlite.org/faq.html#q5 , http://www.somacon.com/p369.php , http://www.sqlite.org/lockingv3.html

=== PostgreSQL ===

Status: unknown

Supported modes: Internal, External

TODO

=== Virtuoso ===

Status: not working

Supported modes: External

Proof-of-concept work was done during Akademy 2010, up to the point where the database could be created successfully. Known issues:

* Some column names used by Akonadi are Virtuoso keywords
* Some of the first INSERT query fails with a signed vs. unsigned int mismatch/overflow.

Completion of Virtuoso support is considered non-trivial and probably requires a lot of work on the Akonadi side, the SQL dialect is too different from what we support so far.

=== MySQL/Embedded ===

Status: not working

Supported modes: Embedded

Development stopped, MySQL/Embedded does not support transactions.

== Tools ==

=== Generic ===

''akonadiconsole'' has support for browsing the database and run arbitrary SQL queries. See [[Development/Tutorials/Akonadi/Application]].

=== MySQL ===

There are convenience scripts for running mysqld in the configuration used by Akonadi as well as (and probably more useful) running the MySQL command line client connected to the Akonadi database. See server/src/storage/akonadi-mysql-[client|server].sh.

[[Category:Akonadi]]

Schedules/KDE4/4.7 Feature Plan

2011-08-24T09:38:18Z

Bernhard: /* kdelibs */ Adding issue number. To the KLockFile improvement.

This is a list of planned features for the SC 4.7 release.

See also:

*[[Schedules/KDE4/4.7 Release Schedule]]
*[[Schedules/KDE4/4.7 Release Goals]]
*[[Schedules/KDE4/4.6 Feature Plan]] (previous major release)

 Legend:

*todo => not started yet
*in-progress => started, but not completed yet
*done => completed

__TOC__

 

= kdelibs =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

{{FeatureDone
|KLocale
|Number grouping support
|john@layt.net|John Layt}}

{{FeatureDone
|KLocale
|Narrow date name format support
|john@layt.net|John Layt}}

{{FeatureDone
|KLocale
|Week Numbers support
|john@layt.net|John Layt}}

{{FeatureDone
|kdecore/io/klockfile
|For 4.7.1: Implement locking on non-NFS systems using O_EXCL. Good for VFAT, CFIS and other filesystems, as it makes KConfig work and thus many KDE Applications. Details in #203554.
|faure@kde.org|David Faure}}

{{FeatureInProgress
|KLocale
|Windows Backend
|john@layt.net|John Layt}}

{{FeatureInProgress
|kdeui
|New date/time edit widgets from kdepim
|john@layt.net|John Layt}}

{{FeatureInProgress
|KHelpMenu
|Fast action searching
|afiestas@kde.org|Alex Fiestas}}

{{FeatureInProgress
|KFilePlaces
|Activity-specific Places
|j.maceachern@gmail.com|Jeffery MacEachern}}

{{FeatureInProgress
|KCookieJar
|Storing cookies in KWallet
|fid@gpul.org|José Millán Soto}}

{{FeatureInProgress
|KHTML
|WebIDL usage
|maksim@kde.org|Maksim Orlovich}}

{{FeatureTodo
|KHTML
|Accessibility improvements
|maksim@kde.org|Maksim Orlovich}}

{{FeatureTodo
|Nepomuk
|Query term class to query graph meta data
|trueg@kde.org|Sebastian Trueg}}

{{FeatureTodo
|Plasma
|Preconfigurable plasmoids
|dpalacio@orbitalibre.org|David Palacio}}

|}

 

= kde-baseapps =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|Dolphin|Support Fwd/Back Mouse Buttons|sebastian@sebastian-doerner.de|Sebastian Dörner}}
{{FeatureDone|Dolphin|Polish the default user interface to minimize visual clutter (see http://ppenz.blogspot.com/2011/03/menu-bars.html)|peter.penz19@gmail.com|Peter Penz}}
{{FeatureDone|Dolphin|Improve user interface for searching files and metadata|peter.penz19@gmail.com|Peter Penz}}
{{FeatureTodo|Settings|Improve proxy configuration dialog|adawit@kde.org|Dawit Alemayehu}}

{{FeatureInProgress
|Locale KCM
|Support for Number Grouping, Windows Backend, Country Subdivsions
|john@layt.net|John Layt}}

{{FeatureInProgress
|nspluginviewer
|npruntime support improvements
|maksim@kde.org|Maksim Orlovich}}

{{FeatureTodo
|Dolphin
|Popup menu for advanced queries on the metadata display
|trueg@kde.org|Sebastian Trueg}}

|}

 

= kde-runtime =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureInProgress|kio_sftp|async download support|asn@cryptomilk.org|Andreas Schneider}}
{{FeatureInProgress
|Locale definition files
|Migrate Country and Currency Codes to xml/po formats, re-arrange l10n files including settings and flags, add Subdivision code files.
|john@layt.net|John Layt}}
{{FeatureTodo|kio-upnp-ms|Merge from playground (https://projects.kde.org/projects/playground/base/kio-upnp-ms/) into kde-runtime|nsm.nikhil@gmail.com|Nikhil Marathe}}
{{FeatureDone|network:/ kio-slave|port to Cagibi 0.2|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureDone|Nepomuk Datamanagement Service|Merge it into the master branch|handa.vish@gmail.com|Vishesh Handa & Sebastian Trueg}}
{{FeatureDone|Port Strigi Service to DMS|The Strigi Service needs to use the DMS API|handa.vish@gmail.com|Vishesh Handa & Sebastian Trueg}}

{{FeatureDone
|Nepomuk
|KCM to manage the removable storages to index
|trueg@kde.org|Sebastian Trueg}}

|}

 

= kde-workspace =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

{{FeatureDone|System Settings/keyboard|Allow a shortcut per keyboard layout (bug 224489)|arysin@mail.com|Andriy Rysin}}
{{FeatureDone|System Settings/keyboard|Session management for keyboard layouts (bug 52095, 174948)|arysin@mail.com|Andriy Rysin}}
{{FeatureDone|klipper|Support qrcode as well as datamatrix for mobile barcodes|sune@vuorela.dk|Sune Vuorela}}
{{FeatureDone|weather|Support debian weather|sune@vuorela.dk|Sune Vuorela}}
{{FeatureDone|Oxygen|Various widgets polishing (scrollbars, progressbars, sliders, toolbuttons, menu and menubar selection, etc.)|hugo@oxygen-icons.org|Hugo Pereira Da Costa}}
{{FeatureDone|Oxygen|Implement kwin's new shadow system for menus, drop-downlists, etc.|hugo@oxygen-icons.org|Hugo Pereira Da Costa}}
|-

! style="text-align: center;" colspan="4" | Plasma
{{FeatureInProgress
|Plasma Clock/Calendar
|improve usability, settings, akonadi and holiday data. See Plasma wiki.
|john@layt.net|John Layt}}
{{FeatureDone
|Plasma Desktop
|launch krunner when the user starts typing
|vitorboschi@gmail.com|Vitor Boschi}}
|-

! style="text-align: center;" colspan="4" | KDM
{{FeatureDone
|KDM
|GRUB2 support for KDM (see http://ksmanis.wordpress.com/2011/04/21/hello-planet-and-grub2-support-for-kdm/)
|konstantinos.smanis@gmail.com|Konstantinos Smanis}}
|-

! style="text-align: center;" colspan="4" | KWin
{{FeatureDone|Compositor|OpenGL 2.x/OpenGL ES 2.0 compositing backend (see http://www.kdenews.org/2011/02/18/kwin-embraces-new-platforms-opengl-es-20-support)|mgraesslin@kde.org|Martin Gräßlin}}
{{FeatureDone|Compositor|New Shadow System (see http://blog.martin-graesslin.com/blog/2011/03/new-kwin-shadows/)|mgraesslin@kde.org|Martin Gräßlin}}
{{FeatureDone|Effects|Effect to render outlines|mgraesslin@kde.org|Martin Gräßlin}}
{{FeatureDone|Decorations|Do not require a decoration|mgraesslin@kde.org|Martin Gräßlin}}
{{FeatureInProgress|Core|Export most recently used windows to an X property|mgraesslin@kde.org|Martin Gräßlin}}
{{FeatureInProgress|BoxSwitch Effect|Animated Selection (see http://blog.martin-graesslin.com/blog/2011/02/is-kwin-rocket-science/)|mgraesslin@kde.org|Martin Gräßlin}}
{{FeatureInProgress|libkwineffects|API cleanup|mgraesslin@kde.org|Martin Gräßlin}}
{{FeatureTodo|libkwineffects|JavaScript bindings for writing Effects|mgraesslin@kde.org|Martin Gräßlin}}
{{FeatureInProgress|Mouse Emulation|Better accessibility support in mouse emulation|mgraesslin@kde.org|Martin Gräßlin}}
{{FeatureDone|kwin|Add multi head support|alberto@mattea.info|Alberto Mattea}}
{{FeatureInProgress|kwin|DBusMenu in Windeco|megabigbug@yahoo.fr|Lionel Chauvin}}
{{FeatureDone|ksplashx|Add multi head support|alberto@mattea.info|Alberto Mattea}}
{{FeatureTodo|krunner|Add multi head support|alberto@mattea.info|Alberto Mattea}}
{{FeatureInProgress|kwinrules kcm|UI cleanup (see https://git.reviewboard.kde.org/r/101041/)|thomas.luebking@gmail.com|Thomas Lübking}}
{{FeatureInProgress|kwincompositing kcm|Rearm unsafe OpenGL precheck (see https://git.reviewboard.kde.org/r/101061/)|thomas.luebking@gmail.com|Thomas Lübking}}
{{FeatureInProgress|PresentWindows Effect|Better highlight indication & close button handling)|thomas.luebking@gmail.com|Thomas Lübking}}
{{FeatureInProgress|general|Remove jargon from user interface. Remove all instances of Akonadi/Nepomuk related jargon from the desktop, replace with meaningful text where needed.|wstephenson@kde.org|Will Stephenson}}
|}

 

= kdeedu =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureDone|Marble|Bookmark Manager|earthwings@gentoo.org|Dennis Nienhüser, Thibaut Gridel}}
{{FeatureDone|Marble|QML Bindings: GPS Tracking|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureInProgress|Marble|Routing API|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Offline Address Search|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Support monav version 0.3|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Polish the Map Wizard: simpler UI, comprehensive validation of user input immediately on each page|bbeschow@cs.tu-berlin.de|Bernhard Beschow}}
{{FeatureInProgress|Marble|Reduce memory footprint of cached tiles|bbeschow@cs.tu-berlin.de|Bernhard Beschow}}
{{FeatureTodo|Marble|Separate thread for tile loading and texture blending (not texture mapping at the moment) for more smooth browsing|jmho@c-xx.com|Jens-Michael Hoffmann, Bernhard Beschow}}
{{FeatureTodo|Marble|Tile loading "read ahead" when idle, prerequisite: threaded tile loading|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureDone|Marble|Multi threaded texture mapping|bbeschow@cs.tu-berlin.de|Bernhard Beschow}}
{{FeatureTodo|Marble|Implement mouse cursor wrapping a la Okular or Gwenview|bbeschow@cs.tu-berlin.de|Bernhard Beschow}}
{{FeatureInProgress|Marble|Manipulate Gps track data|tgridel@freedotfr|Thibaut Gridel}}
{{FeatureInProgress|Cantor|Integrate the Qalculate backend|agostinelli@gmail.com|Matteo Agostinelli}}
{{FeatureDone|Kalzium|Use KUnitConversion for all the Unit handling|etienne.rebetez@oberwallisch|Etienne Rebetez}}
{{FeatureDone|KTurtle|Add getdirection command
|nielsslot@gmaildotcom|Niels Slot}}
{{FeatureTodo|KTurtle|Add modulo command
|nielsslot@gmaildotcom|Niels Slot}}
{{FeatureDone|Step|Copy-and-Paste of items|kde@voecking.net|Sebastian Vöcking}}
{{FeatureDone|Step|Zoom on mouse wheel|kde@voecking.net|Sebastian Vöcking}}
{{FeatureDone|Step|Automatic expanding canvas|kde@voecking.net|Sebastian Vöcking}}
{{FeatureInProgress|Rocs|Auto - Handling of the Canvas|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureDone|Rocs|Remove the thread for QtConcurrent on he core|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureInProgress|Rocs|Polish the User Interface|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureDone|Rocs|New Plugin for Automaticaly Graph Generation|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureInProgress|Rocs|Bugfixes in the List Plugin|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureInProgress|Rocs|Speedup in the drawing code|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureInProgress|Rocs|Kalgebra backend|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureDone|Rocs|Transform graph edges plugin|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureDone|Rocs|Assign values to edges/nodes plugin|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureDone|Kalzium|Titration calculator|TRINGALINVENT@libero.it|Luca Tringali}}
{{FeatureInProgress|KStars|SQLite Database of NGC Objects|victor.carbune@kdemail.net|Victor Carbune|}}
|}
 

= kdepim =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

{{FeatureInProgress|KAlarm|Port to Akonadi|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Allow reminders after the main alarm|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Provide wake-from-suspend option for alarms|djarvie@kde.org|David Jarvie}}

{{FeatureInProgress
|KHolidays
|Add support for Holiday Types and Observance Types
|john@layt.net|John Layt}}

{{FeatureDone|Akonadi-contacts/kaddressbook|Show 2d barcodes of contact data|sune@vuorela.dk|Sune Vuorela}}
|}

 

= kdeplasma-addons =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureInProgress|Adjustable Clock|Plasmoid for displaying date and time in very customizable way|emdeck@gmail.com|Michał Dutkiewicz}}
{{FeatureInProgress|Comic Plasmoid|Support random comic strips|mat69@gmx.net|Matthias Fuchs}}
{{FeatureDone|Comic Plasmoid|Support creation of comic Comic Book Archive files|mat69@gmx.net|Matthias Fuchs}}
{{FeatureDone|Comic Plasmoid|Highlight comics that have a new comic strip|mat69@gmx.net|Matthias Fuchs}}
{{FeatureTodo|Events Runner|Support parsing weekdays (e.g. "in next monday"|alexey.noskov@gmail.com|Alexey Noskov}}
|}

 

= kdetoys =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureDone|KTeaTime|Port to KStatusNotifierItem|miha@noughmad.eu|Miha Čančula}}
{{FeatureInProgress|KTeaTime|New svg based status icons|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureInProgress|KTeaTime|Support categories|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|KTeaTime|Improved command line|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|KTeaTime|Tea runner|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|KTeaTime|Port to KConfigXT|kde@hilefoks.org|Stefan Böhmann}}

|}

 

= kdesdk =

{| cellspa/cing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureInProgress|Lokalize|Remote translation memories|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureInProgress|Lokalize|QA: translation checks against user-specified regex-based rules|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Integrate snowball stemmer for glossary|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Continue implementing XLIFF spec|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Segmentation [editing] functionality|shafff@NOSPAMukr.net |Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Integrate with nepomuk (fast stats retrieval, tag cloud - incl sharing!)|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|loading compressed files and then saving them back in the original compression format (bug 65518)|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureInProgress|Okteta|Properly support strings (various Unicode encodings) in structures tool|alex.richardson@gmx.de|Alex Richardson}}
{{FeatureTodo|Okteta|Add custom datatypes to structures tool|alex.richardson@gmx.de|Alex Richardson}}
{{FeatureInProgress|Okteta|Add tool to convert between char encodings|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureInProgress|Umbrello|QDockWidget based interface|elv1313@gmail.com|Emmanuel Lepage Vallee}}
{{FeatureInProgress|Umbrello|KDE4 icon theme and eye candies|elv1313@gmail.com|Emmanuel Lepage Vallee}}
{{FeatureTodo|Umbrello|Replace the current code viewer with katepart|elv1313@gmail.com|Emmanuel Lepage Vallee}}
{{FeatureDone|Umbrello|Add a zoom widget in the statusbar|elv1313@gmail.com|Emmanuel Lepage Vallee}}
{{FeatureDone|Kate|Add a new search in files plugin|kare.sars@iki.fi|Kåre Särs}}
|}
 

= kdegames =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureInProgress|KBreakout|Level editor|julian.helfferich@gmail.com|Julian Helfferich}}
{{FeatureInProgress|KBreakout|Load levelset option + 2 new levelsets|julian.helfferich@gmail.com|Julian Helfferich}}
{{FeatureTodo|KBreakout|Port to QGraphicsView|julian.helfferich@gmail.com|Julian Helfferich}}
{{FeatureInProgress|KPat|Create new saved game format that stores undo/redo history|parker.coates@gmail.com|Parker Coates}}
{{FeatureInProgress|libtagaro|Move first version into the kdegames module|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureTodo|libtagaro|Use the new library: at least in Granatier and Kolf (to replace existing static source copies) and KDiamond|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureInProgress|Palapeli|Cleanup interface|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureDone|Palapeli|Reduce memory consumption for big puzzles|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureInProgress|all games|Add useful fullscreen mode + option to switch between fullscreen/window|kossebau@kde.org|Friedrich W. H. Kossebau}}
|}

 

= kdenetwork =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureDone|KGet|Working Mms plugin|eortiz@uci.cu|Ernesto Rodriguez Ortiz}}
{{FeatureInProgress|KGet|Support for connection limit to servers|mat69@gmx.net|Matthias Fuchs}}
|}

 

= kdegraphics =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureInProgress|Okular|Directory support in Comic Book Generator|dpalacio@orbitalibre.org|David Palacio}}
{{FeatureInProgress|Okular|7zip support in Comic Book Generator|dpalacio@orbitalibre.org|David Palacio}}
{{FeatureDone|libksane|Enable gui less operation|kare.sars@iki.fi|Kåre Särs}}
{{FeatureDone|libksane|Add a way to get scanner device list|kare.sars@iki.fi|Kåre Särs}}
{{FeatureInProgress|Gwenview|Compare mode|agateau@kde.org|Aurélien Gâteau}}
{{FeatureTodo|Gwenview|Merge "Semantic Information" and "Meta Information" sidebar groups|agateau@kde.org|Aurélien Gâteau}}
|}

Schedules/KDE4/4.7 Feature Plan

2011-08-24T09:33:15Z

Bernhard: /* kdelibs */ Adding improvement for kdecore/io/

This is a list of planned features for the SC 4.7 release.

See also:

*[[Schedules/KDE4/4.7 Release Schedule]]
*[[Schedules/KDE4/4.7 Release Goals]]
*[[Schedules/KDE4/4.6 Feature Plan]] (previous major release)

 Legend:

*todo => not started yet
*in-progress => started, but not completed yet
*done => completed

__TOC__

 

= kdelibs =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

{{FeatureDone
|KLocale
|Number grouping support
|john@layt.net|John Layt}}

{{FeatureDone
|KLocale
|Narrow date name format support
|john@layt.net|John Layt}}

{{FeatureDone
|KLocale
|Week Numbers support
|john@layt.net|John Layt}}

{{FeatureDone
|kdecore/io/klockfile
|For 4.7.1: Implement locking on non-NFS systems using O_EXCL. Good for VFAT, CFIS and other filesystems, as it makes KConfig work and thus many KDE Applications.
|faure@kde.org|David Faure}}

{{FeatureInProgress
|KLocale
|Windows Backend
|john@layt.net|John Layt}}

{{FeatureInProgress
|kdeui
|New date/time edit widgets from kdepim
|john@layt.net|John Layt}}

{{FeatureInProgress
|KHelpMenu
|Fast action searching
|afiestas@kde.org|Alex Fiestas}}

{{FeatureInProgress
|KFilePlaces
|Activity-specific Places
|j.maceachern@gmail.com|Jeffery MacEachern}}

{{FeatureInProgress
|KCookieJar
|Storing cookies in KWallet
|fid@gpul.org|José Millán Soto}}

{{FeatureInProgress
|KHTML
|WebIDL usage
|maksim@kde.org|Maksim Orlovich}}

{{FeatureTodo
|KHTML
|Accessibility improvements
|maksim@kde.org|Maksim Orlovich}}

{{FeatureTodo
|Nepomuk
|Query term class to query graph meta data
|trueg@kde.org|Sebastian Trueg}}

{{FeatureTodo
|Plasma
|Preconfigurable plasmoids
|dpalacio@orbitalibre.org|David Palacio}}

|}

 

= kde-baseapps =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureTodo|Dolphin|Support Fwd/Back Mouse Buttons|sebastian@sebastian-doerner.de|Sebastian Dörner}}
{{FeatureDone|Dolphin|Polish the default user interface to minimize visual clutter (see http://ppenz.blogspot.com/2011/03/menu-bars.html)|peter.penz19@gmail.com|Peter Penz}}
{{FeatureDone|Dolphin|Improve user interface for searching files and metadata|peter.penz19@gmail.com|Peter Penz}}
{{FeatureTodo|Settings|Improve proxy configuration dialog|adawit@kde.org|Dawit Alemayehu}}

{{FeatureInProgress
|Locale KCM
|Support for Number Grouping, Windows Backend, Country Subdivsions
|john@layt.net|John Layt}}

{{FeatureInProgress
|nspluginviewer
|npruntime support improvements
|maksim@kde.org|Maksim Orlovich}}

{{FeatureTodo
|Dolphin
|Popup menu for advanced queries on the metadata display
|trueg@kde.org|Sebastian Trueg}}

|}

 

= kde-runtime =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureInProgress|kio_sftp|async download support|asn@cryptomilk.org|Andreas Schneider}}
{{FeatureInProgress
|Locale definition files
|Migrate Country and Currency Codes to xml/po formats, re-arrange l10n files including settings and flags, add Subdivision code files.
|john@layt.net|John Layt}}
{{FeatureTodo|kio-upnp-ms|Merge from playground (https://projects.kde.org/projects/playground/base/kio-upnp-ms/) into kde-runtime|nsm.nikhil@gmail.com|Nikhil Marathe}}
{{FeatureDone|network:/ kio-slave|port to Cagibi 0.2|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureDone|Nepomuk Datamanagement Service|Merge it into the master branch|handa.vish@gmail.com|Vishesh Handa & Sebastian Trueg}}
{{FeatureDone|Port Strigi Service to DMS|The Strigi Service needs to use the DMS API|handa.vish@gmail.com|Vishesh Handa & Sebastian Trueg}}

{{FeatureDone
|Nepomuk
|KCM to manage the removable storages to index
|trueg@kde.org|Sebastian Trueg}}

|}

 

= kde-workspace =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

{{FeatureDone|System Settings/keyboard|Allow a shortcut per keyboard layout (bug 224489)|arysin@mail.com|Andriy Rysin}}
{{FeatureDone|System Settings/keyboard|Session management for keyboard layouts (bug 52095, 174948)|arysin@mail.com|Andriy Rysin}}
{{FeatureDone|klipper|Support qrcode as well as datamatrix for mobile barcodes|sune@vuorela.dk|Sune Vuorela}}
{{FeatureDone|weather|Support debian weather|sune@vuorela.dk|Sune Vuorela}}
{{FeatureDone|Oxygen|Various widgets polishing (scrollbars, progressbars, sliders, toolbuttons, menu and menubar selection, etc.)|hugo@oxygen-icons.org|Hugo Pereira Da Costa}}
{{FeatureDone|Oxygen|Implement kwin's new shadow system for menus, drop-downlists, etc.|hugo@oxygen-icons.org|Hugo Pereira Da Costa}}
|-

! style="text-align: center;" colspan="4" | Plasma
{{FeatureInProgress
|Plasma Clock/Calendar
|improve usability, settings, akonadi and holiday data. See Plasma wiki.
|john@layt.net|John Layt}}
{{FeatureDone
|Plasma Desktop
|launch krunner when the user starts typing
|vitorboschi@gmail.com|Vitor Boschi}}
|-

! style="text-align: center;" colspan="4" | KDM
{{FeatureDone
|KDM
|GRUB2 support for KDM (see http://ksmanis.wordpress.com/2011/04/21/hello-planet-and-grub2-support-for-kdm/)
|konstantinos.smanis@gmail.com|Konstantinos Smanis}}
|-

! style="text-align: center;" colspan="4" | KWin
{{FeatureDone|Compositor|OpenGL 2.x/OpenGL ES 2.0 compositing backend (see http://www.kdenews.org/2011/02/18/kwin-embraces-new-platforms-opengl-es-20-support)|mgraesslin@kde.org|Martin Gräßlin}}
{{FeatureDone|Compositor|New Shadow System (see http://blog.martin-graesslin.com/blog/2011/03/new-kwin-shadows/)|mgraesslin@kde.org|Martin Gräßlin}}
{{FeatureDone|Effects|Effect to render outlines|mgraesslin@kde.org|Martin Gräßlin}}
{{FeatureDone|Decorations|Do not require a decoration|mgraesslin@kde.org|Martin Gräßlin}}
{{FeatureInProgress|Core|Export most recently used windows to an X property|mgraesslin@kde.org|Martin Gräßlin}}
{{FeatureInProgress|BoxSwitch Effect|Animated Selection (see http://blog.martin-graesslin.com/blog/2011/02/is-kwin-rocket-science/)|mgraesslin@kde.org|Martin Gräßlin}}
{{FeatureInProgress|libkwineffects|API cleanup|mgraesslin@kde.org|Martin Gräßlin}}
{{FeatureTodo|libkwineffects|JavaScript bindings for writing Effects|mgraesslin@kde.org|Martin Gräßlin}}
{{FeatureInProgress|Mouse Emulation|Better accessibility support in mouse emulation|mgraesslin@kde.org|Martin Gräßlin}}
{{FeatureDone|kwin|Add multi head support|alberto@mattea.info|Alberto Mattea}}
{{FeatureInProgress|kwin|DBusMenu in Windeco|megabigbug@yahoo.fr|Lionel Chauvin}}
{{FeatureDone|ksplashx|Add multi head support|alberto@mattea.info|Alberto Mattea}}
{{FeatureTodo|krunner|Add multi head support|alberto@mattea.info|Alberto Mattea}}
{{FeatureInProgress|kwinrules kcm|UI cleanup (see https://git.reviewboard.kde.org/r/101041/)|thomas.luebking@gmail.com|Thomas Lübking}}
{{FeatureInProgress|kwincompositing kcm|Rearm unsafe OpenGL precheck (see https://git.reviewboard.kde.org/r/101061/)|thomas.luebking@gmail.com|Thomas Lübking}}
{{FeatureInProgress|PresentWindows Effect|Better highlight indication & close button handling)|thomas.luebking@gmail.com|Thomas Lübking}}
{{FeatureInProgress|general|Remove jargon from user interface. Remove all instances of Akonadi/Nepomuk related jargon from the desktop, replace with meaningful text where needed.|wstephenson@kde.org|Will Stephenson}}
|}

 

= kdeedu =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureDone|Marble|Bookmark Manager|earthwings@gentoo.org|Dennis Nienhüser, Thibaut Gridel}}
{{FeatureDone|Marble|QML Bindings: GPS Tracking|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureInProgress|Marble|Routing API|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Offline Address Search|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Support monav version 0.3|earthwings@gentoo.org|Dennis Nienhüser}}
{{FeatureDone|Marble|Polish the Map Wizard: simpler UI, comprehensive validation of user input immediately on each page|bbeschow@cs.tu-berlin.de|Bernhard Beschow}}
{{FeatureInProgress|Marble|Reduce memory footprint of cached tiles|bbeschow@cs.tu-berlin.de|Bernhard Beschow}}
{{FeatureTodo|Marble|Separate thread for tile loading and texture blending (not texture mapping at the moment) for more smooth browsing|jmho@c-xx.com|Jens-Michael Hoffmann, Bernhard Beschow}}
{{FeatureTodo|Marble|Tile loading "read ahead" when idle, prerequisite: threaded tile loading|jmho@c-xx.com|Jens-Michael Hoffmann}}
{{FeatureDone|Marble|Multi threaded texture mapping|bbeschow@cs.tu-berlin.de|Bernhard Beschow}}
{{FeatureTodo|Marble|Implement mouse cursor wrapping a la Okular or Gwenview|bbeschow@cs.tu-berlin.de|Bernhard Beschow}}
{{FeatureInProgress|Marble|Manipulate Gps track data|tgridel@freedotfr|Thibaut Gridel}}
{{FeatureInProgress|Cantor|Integrate the Qalculate backend|agostinelli@gmail.com|Matteo Agostinelli}}
{{FeatureDone|Kalzium|Use KUnitConversion for all the Unit handling|etienne.rebetez@oberwallisch|Etienne Rebetez}}
{{FeatureDone|KTurtle|Add getdirection command
|nielsslot@gmaildotcom|Niels Slot}}
{{FeatureTodo|KTurtle|Add modulo command
|nielsslot@gmaildotcom|Niels Slot}}
{{FeatureDone|Step|Copy-and-Paste of items|kde@voecking.net|Sebastian Vöcking}}
{{FeatureDone|Step|Zoom on mouse wheel|kde@voecking.net|Sebastian Vöcking}}
{{FeatureDone|Step|Automatic expanding canvas|kde@voecking.net|Sebastian Vöcking}}
{{FeatureInProgress|Rocs|Auto - Handling of the Canvas|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureDone|Rocs|Remove the thread for QtConcurrent on he core|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureInProgress|Rocs|Polish the User Interface|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureDone|Rocs|New Plugin for Automaticaly Graph Generation|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureInProgress|Rocs|Bugfixes in the List Plugin|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureInProgress|Rocs|Speedup in the drawing code|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureInProgress|Rocs|Kalgebra backend|tcanabrava@kde.org|Tomaz Canabrava}}
{{FeatureDone|Rocs|Transform graph edges plugin|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureDone|Rocs|Assign values to edges/nodes plugin|cola@uni-paderborn.de|Andreas Cord-Landwehr}}
{{FeatureDone|Kalzium|Titration calculator|TRINGALINVENT@libero.it|Luca Tringali}}
{{FeatureInProgress|KStars|SQLite Database of NGC Objects|victor.carbune@kdemail.net|Victor Carbune|}}
|}
 

= kdepim =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"

! Status
! Project
! Description
! Contact

{{FeatureInProgress|KAlarm|Port to Akonadi|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Allow reminders after the main alarm|djarvie@kde.org|David Jarvie}}
{{FeatureDone|KAlarm|Provide wake-from-suspend option for alarms|djarvie@kde.org|David Jarvie}}

{{FeatureInProgress
|KHolidays
|Add support for Holiday Types and Observance Types
|john@layt.net|John Layt}}

{{FeatureDone|Akonadi-contacts/kaddressbook|Show 2d barcodes of contact data|sune@vuorela.dk|Sune Vuorela}}
|}

 

= kdeplasma-addons =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureInProgress|Adjustable Clock|Plasmoid for displaying date and time in very customizable way|emdeck@gmail.com|Michał Dutkiewicz}}
{{FeatureInProgress|Comic Plasmoid|Support random comic strips|mat69@gmx.net|Matthias Fuchs}}
{{FeatureDone|Comic Plasmoid|Support creation of comic Comic Book Archive files|mat69@gmx.net|Matthias Fuchs}}
{{FeatureDone|Comic Plasmoid|Highlight comics that have a new comic strip|mat69@gmx.net|Matthias Fuchs}}
{{FeatureTodo|Events Runner|Support parsing weekdays (e.g. "in next monday"|alexey.noskov@gmail.com|Alexey Noskov}}
|}

 

= kdetoys =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureDone|KTeaTime|Port to KStatusNotifierItem|miha@noughmad.eu|Miha Čančula}}
{{FeatureInProgress|KTeaTime|New svg based status icons|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureInProgress|KTeaTime|Support categories|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|KTeaTime|Improved command line|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|KTeaTime|Tea runner|kde@hilefoks.org|Stefan Böhmann}}
{{FeatureTodo|KTeaTime|Port to KConfigXT|kde@hilefoks.org|Stefan Böhmann}}

|}

 

= kdesdk =

{| cellspa/cing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureInProgress|Lokalize|Remote translation memories|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureInProgress|Lokalize|QA: translation checks against user-specified regex-based rules|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Integrate snowball stemmer for glossary|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Continue implementing XLIFF spec|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Segmentation [editing] functionality|shafff@NOSPAMukr.net |Nick Shaforostoff}}
{{FeatureTodo|Lokalize|Integrate with nepomuk (fast stats retrieval, tag cloud - incl sharing!)|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureTodo|Lokalize|loading compressed files and then saving them back in the original compression format (bug 65518)|shafff@NOSPAMukr.net|Nick Shaforostoff}}
{{FeatureInProgress|Okteta|Properly support strings (various Unicode encodings) in structures tool|alex.richardson@gmx.de|Alex Richardson}}
{{FeatureTodo|Okteta|Add custom datatypes to structures tool|alex.richardson@gmx.de|Alex Richardson}}
{{FeatureInProgress|Okteta|Add tool to convert between char encodings|kossebau@kde.org|Friedrich W. H. Kossebau}}
{{FeatureInProgress|Umbrello|QDockWidget based interface|elv1313@gmail.com|Emmanuel Lepage Vallee}}
{{FeatureInProgress|Umbrello|KDE4 icon theme and eye candies|elv1313@gmail.com|Emmanuel Lepage Vallee}}
{{FeatureTodo|Umbrello|Replace the current code viewer with katepart|elv1313@gmail.com|Emmanuel Lepage Vallee}}
{{FeatureDone|Umbrello|Add a zoom widget in the statusbar|elv1313@gmail.com|Emmanuel Lepage Vallee}}
{{FeatureDone|Kate|Add a new search in files plugin|kare.sars@iki.fi|Kåre Särs}}
|}
 

= kdegames =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureInProgress|KBreakout|Level editor|julian.helfferich@gmail.com|Julian Helfferich}}
{{FeatureInProgress|KBreakout|Load levelset option + 2 new levelsets|julian.helfferich@gmail.com|Julian Helfferich}}
{{FeatureTodo|KBreakout|Port to QGraphicsView|julian.helfferich@gmail.com|Julian Helfferich}}
{{FeatureInProgress|KPat|Create new saved game format that stores undo/redo history|parker.coates@gmail.com|Parker Coates}}
{{FeatureInProgress|libtagaro|Move first version into the kdegames module|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureTodo|libtagaro|Use the new library: at least in Granatier and Kolf (to replace existing static source copies) and KDiamond|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureInProgress|Palapeli|Cleanup interface|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureDone|Palapeli|Reduce memory consumption for big puzzles|majewsky@gmx.net|Stefan Majewsky}}
{{FeatureInProgress|all games|Add useful fullscreen mode + option to switch between fullscreen/window|kossebau@kde.org|Friedrich W. H. Kossebau}}
|}

 

= kdenetwork =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureDone|KGet|Working Mms plugin|eortiz@uci.cu|Ernesto Rodriguez Ortiz}}
{{FeatureInProgress|KGet|Support for connection limit to servers|mat69@gmx.net|Matthias Fuchs}}
|}

 

= kdegraphics =

{| cellspacing="0" cellpadding="5" border="1" style="border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;" class="sortable"
|- style="background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;"
! Status
! Project
! Description
! Contact
{{FeatureInProgress|Okular|Directory support in Comic Book Generator|dpalacio@orbitalibre.org|David Palacio}}
{{FeatureInProgress|Okular|7zip support in Comic Book Generator|dpalacio@orbitalibre.org|David Palacio}}
{{FeatureDone|libksane|Enable gui less operation|kare.sars@iki.fi|Kåre Särs}}
{{FeatureDone|libksane|Add a way to get scanner device list|kare.sars@iki.fi|Kåre Särs}}
{{FeatureInProgress|Gwenview|Compare mode|agateau@kde.org|Aurélien Gâteau}}
{{FeatureTodo|Gwenview|Merge "Semantic Information" and "Meta Information" sidebar groups|agateau@kde.org|Aurélien Gâteau}}
|}

Projects/PIM/MS Windows

2011-06-23T12:02:00Z

Bernhard: /* LDAP Support */ rephrased the two options trying to be more clear

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).

==Building==

To build KDE PIM for Windows use emerge.
For documentation about emerge please see [http://techbase.kde.org/Getting_Started/Build/KDE4/Windows]

You should be able to get executables just by calling emerge kdepim.

== Bugs ==
For a list of open, Windows specific, bugs please see: [http://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=akregator&product=kaddressbook&product=kdepim&product=kdepimlibs&product=kmail2&product=kontact&product=korganizer&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=NEEDSINFO&op_sys=MS+Windows&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= bugs.kde.org]

== Problem points ==
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Feature !! Description !! Contact

{{FeatureDone | [[#Documentation_of_KDE|Documentation of KDE]] | Due to meinproc4 crashes documentation build is turned off from all kde products.| }}

{{FeatureTodo|[[#LDAP_Support|LDAP Support]]| Enabling KLdap |aheinecke@intevation.de| Andre Heinecke }}

{{FeatureDone|[[#Akonadi_Notifications|Akonadi Notifications]]| Akonadi Notifications are not communicated correctly to the GUI |}}

{{FeatureDone|[[#Search|Search]]|Provide a search backend|aheinecke@intevation.de| Andre Heinecke }}

{{FeatureDone|[[#Nepomuk|Nepomuk]]|Provide a working Nepomuk|aheinecke@intevation.de| Andre Heinecke }}

{{FeatureDone|[[#Akonadi_Start_Stop|Akonadi startup/shutdown]]|Decide how akonadi should be started/stopped on Windows (There is now a
Full Shudown button in Kontact that also kills akonadi||}}

{{FeatureTodo|[[#Multiuser_Support|Multiuser Support]]|Make it possible
to deploy KDEPIM in multiuser environments||}}

{{FeatureDone|Image view in Mailviewer|Images in the Mailviewer are not shown correctly||}}

{{FeatureTodo|Configuration dialog asks for save every time|The configuration dialog asks the user to confirm his changes even if no changes were made||}}

{{FeatureDone|[[#Design|Design]]|Make KDEPIM feel native on Windows||}}

{{FeatureTodo|[[#GPG4Win_Integration|Integrate with GPG4Win]]| GnuPG is
currently not supported |aheinecke@intevation.de| Andre Heinecke}}
|}

===Multiuser Support===
Kontact on Windows currently not able to handle multiple users running it in parallel because of several bugs.

===Documentation of KDE ===
For more details about the problem check the bug report: [https://bugs.kde.org/show_bug.cgi?id=263828 BUG263828]

There is a workaround and documentation can be built.

===LDAP Support===
There are two options to get LDAP support for PIM on Windows:

====OpenLDAP====
* Pro:
** Would offer the same API as on GNU/Linux
** Is proven to work on Windows with KDEPIM
** If just a binary is take, the effort is small.

* Contra:
** Current Openldap is not ported to be buildable natively on Windows. So far it would need to be cross compiled, or cygwin compiled or the binaries taken.
** More effort to do a good port to a decent buildsystem which fits the toolchain like cmake/emerge to be build with msvc or mingw-w64 on Windows.
** Can not be debugged with msvc for above reasons
** Is another dependency we have to take care of, which increasing code and complexety, more chance for security issues and the port needs to be maintained.

====WinLDAP====
Windows has native LDAP support with winldap:

* Pro:
** Integrated into the platform, maintained by Microsoft
** API differences should be Minimal so kldap calls could stay the same
** Behaviour consistent with other LDAP client behaviour on Windows.

* Contra:
** Efforts comparable to OpenLDAP with initally ported build system. In particular higher than the simple "take binary" approach.
** kdepimlibs is build with -DUNICODE, but expects LDAP system calls o return ascii, so this needs conversion. There is a bit code in kdepimlibs/kldap/w32ldaphelp.h which works fo WindowsCE, but now Windows>=NT.
** Is propietary we do not know the implementation details and cannot debug it.
** Might show slightly different behavior than OpenLDAP, which raises potential testing and support costs when Kontact behaves differently here.
** Might not implement all functions used by kldap so working around it in kldap would be necessary.

===Search===
Search is available over Nepomuk

===Nepomuk===
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. The NSIS installer does this currently

===Akonadi Notifications===
DBus problem that has been fixed in newer versions of DBus > 1.4.1

===Design===
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
XP and Vista/7 looks.

Best solution would be to check what the System Style is or package the KDE-Systemsettings to customize that style.

===Akonadi Start Stop===
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

===GPG4Win Integration===
Currently crypto operations appearently corrupts the stack, causing Kontact
to crash in unrelated operations. For this reason GnuPG support has been
completly disabled since 2011.04.11. Crypto integration is one of the most
important features of Kontact on Windows and we need a way to integrate it
properly.

== General Hints ==

=== Shutdown everything from KDE ===
Either run killkde.bat in your installation\bin directory or run
kdeinit4 --terminate to shut down everything.

==== Delete all configuration ====

To delete all configuration files remove the folders .local .config .kde in
your userdata directory.
(e.g. c:\documents and settings\testuser\ on xp c:\users\testuser on win7)
Also delete .kde in your application data directory
(e.g. c:\documents and settings\testuser\Applicationdata on xp c:\users\testuser\Applicationdata\roaming on win7)

==== Switch to English ====

To change the application '''language''' of Kontact from German '''to English''' please
use a text editor and change the locale settings in the file 'kdeglobals' to:
Country=en
Language=en_US
and restart all KDE processes (esp. logout, login).
You'll find this file usually under the installed directory
in 'Kontact\share\config' (e.g. c:\Program Files\Kontact\share\config\kdeglobals).

Or goto: help -> change application language

==== Backtrace for Crash reporting ====

If you encounter crashes, a backtrace might help the developers to find
the defect faster. There are some hints doing a backtrace with gdb on windows
in http://techbase.kde.org/Development/Tutorials/Debugging/Debugging_on_MS_Windows#MinGW_debugging_hints

==== Diagnostics ====
General debugging techniques of KDEPIM Software are also available on Windows.
There is akonadiconsole installed as a tool to debug akonadi, as well as qdbusviewer.

DebugView and some other tools from the following URL can be useful to diagnose problems:
http://techbase.kde.org/Projects/KDE_on_Windows/Tools

DebugView will let you see the message of the KDE runtime system, which on GNU/Linux you can see on stdout or stderr.

----

==Some notes from the original porting project==

===Integration into the Windows Explorer & Desktop===
{{Note|[[User:Jstaniek|jstaniek]] 22:01, 14 January 2008 (CET): [http://tortoisesvn.tigris.org/ 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 [http://members.toast.net/4pf/Protocol.html 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 [http://support.microsoft.com/kb/297878 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 - <tt>"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."</tt> 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: <tt>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.</tt>

=====Using MAPI=====
HKLM\Software\Clients\AppName\DllPath points to a dll implementing [http://en.wikipedia.org/wiki/MAPI 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.[http://members.toast.net/4pf/Protocol.html]
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 <nowiki>mailto:</nowiki> via {{Qt|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.
*[[User:Jstaniek|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 ==
* [[Projects/KDE_on_Windows|The KDE on Windows]] Project
* [[Projects/KDE on Windows/Missing features of kdelibs|Missing features of kdelibs on Windows]] - KDE PIM may depend on them

[[Category:PIM]]
[[Category:MS Windows]]

Projects/PIM/MS Windows

2011-03-23T15:40:36Z

Bernhard: /* Documentation of KDE */ better phrasing

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).

==Building==

To build KDE PIM for Windows use emerge.
For documentation about emerge please see [http://techbase.kde.org/Getting_Started/Build/KDE4/Windows]

You should be able to get executables just by calling emerge kdepim.

== Problem points ==
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Feature !! Description !! Contact

{{FeatureDone | [[#Documentation_of_KDE|Documentation of KDE]] | Due to meinproc4 crashes documentation build is turned off from all kde products.| }}

{{FeatureTodo|[[#LDAP_Support|LDAP Support]]| Enabling KLdap |aheinecke@intevation.de| Andre Heinecke }}

{{FeatureDone|[[#Akonadi_Notifications|Akonadi Notifications]]| Akonadi Notifications are not communicated correctly to the GUI |}}

{{FeatureInProgress|[[#Search|Search]]|Provide a search backend|aheinecke@intevation.de| Andre Heinecke }}

{{FeatureInProgress|[[#Nepomuk|Nepomuk]]|Provide a working Nepomuk|aheinecke@intevation.de| Andre Heinecke }}

{{FeatureTodo|[[#Akonadi_Start_Stop|Akonadi startup/shutdown]]|Decide how akonadi should be started/stopped on Windows||}}

{{FeatureTodo|Image view in Mailviewer|Images in the Mailviewer are not shown correctly||}}

{{FeatureTodo|Configuration dialog asks for save every time|The configuration dialog asks the user to confirm his changes even if no changes were made||}}

{{FeatureTodo|[[#Design|Design]]|Make KDEPIM feel native on Windows||}}

{{FeatureTodo|[[#GPG4Win_Integration|Integrate with GPG4Win]]|Use GPG4Win to provide Crypto support on Windows |aheinecke@intevation.de| Andre Heinecke}}
|}

===Documentation of KDE ===
For more details about the problem check the bug report: [https://bugs.kde.org/show_bug.cgi?id=263828 BUG263828]

There is a workaround and documentation can be built.

===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.
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===
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.

===Akonadi Notifications===
DBus problem that has been fixed in newer versions of DBus > 1.4.1

===Design===
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 Start Stop===
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

===GPG4Win Integration===
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.

----

==Some notes from the original porting project==

===Integration into the Windows Explorer & Desktop===
{{Note|[[User:Jstaniek|jstaniek]] 22:01, 14 January 2008 (CET): [http://tortoisesvn.tigris.org/ 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 [http://members.toast.net/4pf/Protocol.html 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 [http://support.microsoft.com/kb/297878 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 - <tt>"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."</tt> 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: <tt>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.</tt>

=====Using MAPI=====
HKLM\Software\Clients\AppName\DllPath points to a dll implementing [http://en.wikipedia.org/wiki/MAPI 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.[http://members.toast.net/4pf/Protocol.html]
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 <nowiki>mailto:</nowiki> via {{Qt|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.
*[[User:Jstaniek|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 ==
* [[Projects/KDE_on_Windows|The KDE on Windows]] Project
* [[Projects/KDE on Windows/Missing features of kdelibs|Missing features of kdelibs on Windows]] - KDE PIM may depend on them

[[Category:PIM]]
[[Category:MS Windows]]

Projects/PIM/MS Windows

2011-03-23T15:37:56Z

Bernhard: explaining Windows NT Kernel

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).

==Building==

To build KDE PIM for Windows use emerge.
For documentation about emerge please see [http://techbase.kde.org/Getting_Started/Build/KDE4/Windows]

You should be able to get executables just by calling emerge kdepim.

== Problem points ==
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Feature !! Description !! Contact

{{FeatureDone | [[#Documentation_of_KDE|Documentation of KDE]] | Due to meinproc4 crashes documentation build is turned off from all kde products.| }}

{{FeatureTodo|[[#LDAP_Support|LDAP Support]]| Enabling KLdap |aheinecke@intevation.de| Andre Heinecke }}

{{FeatureDone|[[#Akonadi_Notifications|Akonadi Notifications]]| Akonadi Notifications are not communicated correctly to the GUI |}}

{{FeatureInProgress|[[#Search|Search]]|Provide a search backend|aheinecke@intevation.de| Andre Heinecke }}

{{FeatureInProgress|[[#Nepomuk|Nepomuk]]|Provide a working Nepomuk|aheinecke@intevation.de| Andre Heinecke }}

{{FeatureTodo|[[#Akonadi_Start_Stop|Akonadi startup/shutdown]]|Decide how akonadi should be started/stopped on Windows||}}

{{FeatureTodo|Image view in Mailviewer|Images in the Mailviewer are not shown correctly||}}

{{FeatureTodo|Configuration dialog asks for save every time|The configuration dialog asks the user to confirm his changes even if no changes were made||}}

{{FeatureTodo|[[#Design|Design]]|Make KDEPIM feel native on Windows||}}

{{FeatureTodo|[[#GPG4Win_Integration|Integrate with GPG4Win]]|Use GPG4Win to provide Crypto support on Windows |aheinecke@intevation.de| Andre Heinecke}}
|}

===Documentation of KDE ===
For more details about the problem check the bug report: [https://bugs.kde.org/show_bug.cgi?id=263828 BUG263828]

It is no longer an acute problem and documentation can be built.

===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.
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===
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.

===Akonadi Notifications===
DBus problem that has been fixed in newer versions of DBus > 1.4.1

===Design===
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 Start Stop===
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

===GPG4Win Integration===
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.

----

==Some notes from the original porting project==

===Integration into the Windows Explorer & Desktop===
{{Note|[[User:Jstaniek|jstaniek]] 22:01, 14 January 2008 (CET): [http://tortoisesvn.tigris.org/ 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 [http://members.toast.net/4pf/Protocol.html 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 [http://support.microsoft.com/kb/297878 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 - <tt>"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."</tt> 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: <tt>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.</tt>

=====Using MAPI=====
HKLM\Software\Clients\AppName\DllPath points to a dll implementing [http://en.wikipedia.org/wiki/MAPI 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.[http://members.toast.net/4pf/Protocol.html]
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 <nowiki>mailto:</nowiki> via {{Qt|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.
*[[User:Jstaniek|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 ==
* [[Projects/KDE_on_Windows|The KDE on Windows]] Project
* [[Projects/KDE on Windows/Missing features of kdelibs|Missing features of kdelibs on Windows]] - KDE PIM may depend on them

[[Category:PIM]]
[[Category:MS Windows]]

Getting Started/Sources

2011-03-23T13:10:27Z

Bernhard: adding bullet point for KDE Playground

== Source Repositories and Revision Control ==

[TODO more background to revision control]

KDE uses a central online repository to store our Source Code and to track changes made to the code. Currently, KDE is in the middle of migrating our main repository from [[/Subversion|Subversion (svn)]] to [[Development/Git|Git]], so some software modules currently live in Git while others are still only available from Subversion. This means you will need to become familiar with both systems.

== Obtaining The Source Code ==

There are three main ways of doing this:

* Directly access the KDE Source Repository using either Git or Subversion to copy the source code as it currently is with a full history of all changes. In Git this is know as Cloning the repository, in Subversion it is Checking-Out the code. This is most commonly done if you want to actively develop the code.
* Download a tarball snapshot of the Source Repository to bootstrap a Git clone or Subversion checkout. This is a good option if you have a slow or unreliable internet connection. See the [[/Snapshots|Source Snapshots]] page for more details.
* Download a tarball snapshot of just the code as at a given time or release. This is most commonly done if you do not want to develop the code itself but just want to use it for a stable system installation, testing a release, or developing applications outside of the KDE SC.

Note that Checkout has a different meaning in Git than it does in Subversion.

== KDE Software Modules ==

Within the KDE Source Repository the code is organized in Projects and Modules. There are also a number of high-level groupings of the Modules.

=== Qt KDE ===

* Qt KDE (qt-kde) git

=== KDE Support ===

The '''KDE Support''' group is a set of tools and libraries that have been developed by KDE and that various KDE modules depend upon but are not themselves dependent on the KDE Development Platform. These libraries can thus be used by non-KDE applications without having to rely on KDE as well.

=== KDE Software Compilation ===

The '''KDE Software Compilation''' (aka KDE SC) is an informal term covering all the KDE Software which is released together on the regular KDE Release Cycle.

==== KDE Development Platform ====

The '''KDE Development Platform''' group is defined as those KDE Modules that are required to run a KDE Application, i.e. the core libraries and runtime dependencies.

* KDE Libraries (kdelibs) Git
* KDE PIM Libraries (kdepimlibs) Git
* KDE Runtime (kde-runtime) Git

==== KDE Workspace ====

The '''KDE Workspace''' group (aka '''Plasma''') is defined as those KDE Modules that are needed to run a workspace, such as the Desktop or Netbook. This group is not needed to run a KDE Application under another workspace such as Gnome or Windows.

* KDE Workspace (kde-workspace) Git
* KDE Base (kde-baseapps) Git

==== KDE Applications ====

The '''KDE Applications''' group is defined as those KDE modules built on the KDE Development Platform that are hosted by the KDE infrastructure and are released as part of the regular KDE Release Cycle, i.e. they are part of the KDE SC.

* KDE Accessibility (kdeaccessibility) svn
* KDE Admin (kdeadmin) svn
* KDE Artwork (kdeartwork) svn
* KDE Bindings (kdebindings) git/svn
* KDE Examples (kdeexamples) git
* KDE Education (kdeedu) svn
* KDE Games (kdegames) svn
* KDE Graphics (kdegraphics) git/svn
* KDE Network (kdenetwork) svn
* KDE Multimedia (kdemultimedia) svn
* Plasma Addons (kdeplasma-addons) git
* KDE PIM Runtime (kdepim-runtime) Git
* '''Kontact''' and Kontact Touch as part of KDE PIM (kdepim) Git
* KDE SDK (kdesdk) svn
* KDE Toys (kdetoys) svn
* KDE Utilities (kdeutils) svn
* KDE Web Development (kdewebdev) svn

=== KDE Extragear ===

The '''KDE Extragear''' group is defined as those applications built on the KDE Development Platform that are hosted by the KDE infrastructure and have a stable release but are not part of a KDE Module and are not released as part of the regular KDE Release Cycle, i.e. they are not part of the KDE SC.

* KDE Extragear (extragear) Git/svn

=== KDE Playground ===

The '''KDE Playground''' group is defined as those applications built on the KDE Development Platform that are hosted by the KDE infrastructure but have not yet had a stable release and may never be released.

* KDE Playground (playground) git/svn

=== KDE Review ===

The '''KDE Review''' group is defined as those applications that are being reviewed for inclusion in a KDE Module or KDE Extragear, usually moving over from KDE Playground.

=== KDE Translations ===

* KDE Translations (i18n) svn

=== KDE Websites ===

* KDE Websites (websites/www) git/svn

=== KOffice ===

* KOffice (koffice) git, stable in svn

=== Calligra ===

* '''Calligra''' (calligra) git

Getting Started/Sources

2011-03-23T11:29:49Z

Bernhard: highlighting all active "new brand" names that people might look for to better visual matching.

== Source Repositories and Revision Control ==

[TODO more background to revision control]

KDE uses a central online repository to store our Source Code and to track changes made to the code. Currently, KDE is in the middle of migrating our main repository from [[/Subversion|Subversion (svn)]] to [[Development/Git|Git]], so some software modules currently live in Git while others are still only available from Subversion. This means you will need to become familiar with both systems.

== Obtaining The Source Code ==

There are three main ways of doing this:

* Directly access the KDE Source Repository using either Git or Subversion to copy the source code as it currently is with a full history of all changes. In Git this is know as Cloning the repository, in Subversion it is Checking-Out the code. This is most commonly done if you want to actively develop the code.
* Download a tarball snapshot of the Source Repository to bootstrap a Git clone or Subversion checkout. This is a good option if you have a slow or unreliable internet connection. See the [[/Snapshots|Source Snapshots]] page for more details.
* Download a tarball snapshot of just the code as at a given time or release. This is most commonly done if you do not want to develop the code itself but just want to use it for a stable system installation, testing a release, or developing applications outside of the KDE SC.

Note that Checkout has a different meaning in Git than it does in Subversion.

== KDE Software Modules ==

Within the KDE Source Repository the code is organized in Projects and Modules. There are also a number of high-level groupings of the Modules.

=== Qt KDE ===

* Qt KDE (qt-kde) git

=== KDE Support ===

The '''KDE Support''' group is a set of tools and libraries that have been developed by KDE and that various KDE modules depend upon but are not themselves dependent on the KDE Development Platform. These libraries can thus be used by non-KDE applications without having to rely on KDE as well.

=== KDE Software Compilation ===

The '''KDE Software Compilation''' (aka KDE SC) is an informal term covering all the KDE Software which is released together on the regular KDE Release Cycle.

==== KDE Development Platform ====

The '''KDE Development Platform''' group is defined as those KDE Modules that are required to run a KDE Application, i.e. the core libraries and runtime dependencies.

* KDE Libraries (kdelibs) Git
* KDE PIM Libraries (kdepimlibs) Git
* KDE Runtime (kde-runtime) Git

==== KDE Workspace ====

The '''KDE Workspace''' group (aka '''Plasma''') is defined as those KDE Modules that are needed to run a workspace, such as the Desktop or Netbook. This group is not needed to run a KDE Application under another workspace such as Gnome or Windows.

* KDE Workspace (kde-workspace) Git
* KDE Base (kde-baseapps) Git

==== KDE Applications ====

The '''KDE Applications''' group is defined as those KDE modules built on the KDE Development Platform that are hosted by the KDE infrastructure and are released as part of the regular KDE Release Cycle, i.e. they are part of the KDE SC.

* KDE Accessibility (kdeaccessibility) svn
* KDE Admin (kdeadmin) svn
* KDE Artwork (kdeartwork) svn
* KDE Bindings (kdebindings) git/svn
* KDE Examples (kdeexamples) git
* KDE Education (kdeedu) svn
* KDE Games (kdegames) svn
* KDE Graphics (kdegraphics) git/svn
* KDE Network (kdenetwork) svn
* KDE Multimedia (kdemultimedia) svn
* Plasma Addons (kdeplasma-addons) git
* KDE PIM Runtime (kdepim-runtime) Git
* '''Kontact''' and Kontact Touch as part of KDE PIM (kdepim) Git
* KDE SDK (kdesdk) svn
* KDE Toys (kdetoys) svn
* KDE Utilities (kdeutils) svn
* KDE Web Development (kdewebdev) svn

=== KDE Extragear ===

The '''KDE Extragear''' group is defined as those applications built on the KDE Development Platform that are hosted by the KDE infrastructure and have a stable release but are not part of a KDE Module and are not released as part of the regular KDE Release Cycle, i.e. they are not part of the KDE SC.

* KDE Extragear (extragear) Git/svn

=== KDE Playground ===

The '''KDE Playground''' group is defined as those applications built on the KDE Development Platform that are hosted by the KDE infrastructure but have not yet had a stable release and may never be released.

=== KDE Review ===

The '''KDE Review''' group is defined as those applications that are being reviewed for inclusion in a KDE Module or KDE Extragear, usually moving over from KDE Playground.

=== KDE Translations ===

* KDE Translations (i18n) svn

=== KDE Websites ===

* KDE Websites (websites/www) git/svn

=== KOffice ===

* KOffice (koffice) git, stable in svn

=== Calligra ===

* '''Calligra''' (calligra) git

Getting Started/Sources

2011-03-23T11:27:05Z

Bernhard: /* KDE Applications */ Explicitely mentioned Kontact, because some people might match on the name.

== Source Repositories and Revision Control ==

[TODO more background to revision control]

KDE uses a central online repository to store our Source Code and to track changes made to the code. Currently, KDE is in the middle of migrating our main repository from [[/Subversion|Subversion (svn)]] to [[Development/Git|Git]], so some software modules currently live in Git while others are still only available from Subversion. This means you will need to become familiar with both systems.

== Obtaining The Source Code ==

There are three main ways of doing this:

* Directly access the KDE Source Repository using either Git or Subversion to copy the source code as it currently is with a full history of all changes. In Git this is know as Cloning the repository, in Subversion it is Checking-Out the code. This is most commonly done if you want to actively develop the code.
* Download a tarball snapshot of the Source Repository to bootstrap a Git clone or Subversion checkout. This is a good option if you have a slow or unreliable internet connection. See the [[/Snapshots|Source Snapshots]] page for more details.
* Download a tarball snapshot of just the code as at a given time or release. This is most commonly done if you do not want to develop the code itself but just want to use it for a stable system installation, testing a release, or developing applications outside of the KDE SC.

Note that Checkout has a different meaning in Git than it does in Subversion.

== KDE Software Modules ==

Within the KDE Source Repository the code is organized in Projects and Modules. There are also a number of high-level groupings of the Modules.

=== Qt KDE ===

* Qt KDE (qt-kde) git

=== KDE Support ===

The '''KDE Support''' group is a set of tools and libraries that have been developed by KDE and that various KDE modules depend upon but are not themselves dependent on the KDE Development Platform. These libraries can thus be used by non-KDE applications without having to rely on KDE as well.

=== KDE Software Compilation ===

The '''KDE Software Compilation''' (aka KDE SC) is an informal term covering all the KDE Software which is released together on the regular KDE Release Cycle.

==== KDE Development Platform ====

The '''KDE Development Platform''' group is defined as those KDE Modules that are required to run a KDE Application, i.e. the core libraries and runtime dependencies.

* KDE Libraries (kdelibs) Git
* KDE PIM Libraries (kdepimlibs) Git
* KDE Runtime (kde-runtime) Git

==== KDE Workspace ====

The '''KDE Workspace''' group (aka Plasma) is defined as those KDE Modules that are needed to run a workspace, such as the Desktop or Netbook. This group is not needed to run a KDE Application under another workspace such as Gnome or Windows.

* KDE Workspace (kde-workspace) Git
* KDE Base (kde-baseapps) Git

==== KDE Applications ====

The '''KDE Applications''' group is defined as those KDE modules built on the KDE Development Platform that are hosted by the KDE infrastructure and are released as part of the regular KDE Release Cycle, i.e. they are part of the KDE SC.

* KDE Accessibility (kdeaccessibility) svn
* KDE Admin (kdeadmin) svn
* KDE Artwork (kdeartwork) svn
* KDE Bindings (kdebindings) git/svn
* KDE Examples (kdeexamples) git
* KDE Education (kdeedu) svn
* KDE Games (kdegames) svn
* KDE Graphics (kdegraphics) git/svn
* KDE Network (kdenetwork) svn
* KDE Multimedia (kdemultimedia) svn
* Plasma Addons (kdeplasma-addons) git
* KDE PIM Runtime (kdepim-runtime) Git
* Kontact and Kontact Touch as part of KDE PIM (kdepim) Git
* KDE SDK (kdesdk) svn
* KDE Toys (kdetoys) svn
* KDE Utilities (kdeutils) svn
* KDE Web Development (kdewebdev) svn

=== KDE Extragear ===

The '''KDE Extragear''' group is defined as those applications built on the KDE Development Platform that are hosted by the KDE infrastructure and have a stable release but are not part of a KDE Module and are not released as part of the regular KDE Release Cycle, i.e. they are not part of the KDE SC.

* KDE Extragear (extragear) Git/svn

=== KDE Playground ===

The '''KDE Playground''' group is defined as those applications built on the KDE Development Platform that are hosted by the KDE infrastructure but have not yet had a stable release and may never be released.

=== KDE Review ===

The '''KDE Review''' group is defined as those applications that are being reviewed for inclusion in a KDE Module or KDE Extragear, usually moving over from KDE Playground.

=== KDE Translations ===

* KDE Translations (i18n) svn

=== KDE Websites ===

* KDE Websites (websites/www) git/svn

=== KOffice ===

* KOffice (koffice) git, stable in svn

=== Calligra ===

* Calligra (calligra) git

Projects/PIM/MS Windows

2011-02-25T11:52:38Z

Bernhard: /* Problem points */ meinproc point improved.

This page covers topics related to the KDE PIM Suite on MS Windows NT.

==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 ==
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"
|- style="background: #ececec; white-space:nowrap;"
! Status !! Feature !! Description !! Contact

{{FeatureTodo | [[#Documentation_of_KDE|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. | }}

{{FeatureTodo|[[#LDAP_Support|LDAP Support]]| Enabling KLdap |aheinecke@intevation.de| Andre Heinecke }}

{{FeatureTodo|[[#Search|Search]]|Provide a search backend| }}

{{FeatureTodo|[[#Nepomuk|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 [https://bugs.kde.org/show_bug.cgi?id=263828 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|[[User:Jstaniek|jstaniek]] 22:01, 14 January 2008 (CET): [http://tortoisesvn.tigris.org/ 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 [http://members.toast.net/4pf/Protocol.html 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 [http://support.microsoft.com/kb/297878 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 - <tt>"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."</tt> 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: <tt>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.</tt>

=====Using MAPI=====
HKLM\Software\Clients\AppName\DllPath points to a dll implementing [http://en.wikipedia.org/wiki/MAPI 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.[http://members.toast.net/4pf/Protocol.html]
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 <nowiki>mailto:</nowiki> via {{Qt|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.
*[[User:Jstaniek|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 ==
* [[Projects/KDE_on_Windows|The KDE on Windows]] Project
* [[Projects/KDE on Windows/Missing features of kdelibs|Missing features of kdelibs on Windows]] - KDE PIM may depend on them

[[Category:PIM]]
[[Category:MS Windows]]

Projects/KDE PIM/Development/Mobile/ResourcesCESearch

2011-02-09T15:36:05Z

Bernhard: smaller updates

On Windows Mobile 6.5 (CE) Kontact Touch has a resource problem,
the searching and indexing is done via strigifeeder and strigidaemon.

Next steps:
* find all places where search is needed
:# real search dialog (_not_ quicksearch)
:# to-field autocompletion
:# MemoryCalendarMemento (could be replaced with IncidenceFetchJob though)
* how much memory does strigidaemon actually use? (Can be found with taskmanager, 1936kb here on an empty device, says Andre)
* how much memory does strigiindexer use (sees more on the desktop)
* check if clucene used by strigidaemon cannot be tuned to use less memory
* implement a display of the last index run, e.g on the search page
* implement a button to trigger a manual index, e.g. on the search page (both can be reused once we come up with an idea when the indexer should run.)
* Can we reliably see if the device is under low load, e.g. if only one or no frontend is running?

Options as tokoe saw them 2011020914:32:
1) A UI option to switch strigi_feeder between online/offline mode

pro: The strigi_feeder in offline mode wouldn't index anything until it
is switched back to online mode. So it would take away pressure on the
device during initial sync, since CPU and I/O usage is reduced.

contra: Since recent data are not indexed with strigi_feeder in offline
mode, some internal searches might not return the correct, or better
said 'expected', data. Switching the strigi_feeder to online mode
automatically when a search is started is not really an option,
because feeding the new data to strigidaemon takes a while, so they
won't be included in the current search results.

costs: We have to extend strigi_feeder to correctly record actions during
offline mode and replay them when switched to online mode.
Furthermore we need options in the UI to switch the mode of the
strigifeeder (Ideas from Björn Balazs?).

2) IDLE detection in strigidaemon with automatic shutdown

pro: Afaik strigidaemon uses lots of memory when running, so
stopping strigidaemon whenever no indexing or search is done,
should provide some free memory on the device.

contra: Searches are done quite often (e.g. the autocompletion in mail
composer) and strigi_feeder will index data as soon as something
changes (e.g. read flags in emails), so I doubt that strigidaemon
will have long idle sessions. Strigidaemon might cause additional
costs during its startup/shutdown phase.

costs: We have to implement an idle detection in strigidaemon
(non qt-based!) and a clean shutdown procedure.
Furthermore we have to extend akonadiserver to handle the
disappearance of strigi dbus interface gracefully and restart the
strigidaemon on demand. This needs a lot of testing!

It would be possible to combine 1) and 2), but this will increase the number
of side effects, so much more testing is needed.

Projects/KDE PIM/Development/Mobile/ResourcesCESearch

2011-02-09T15:11:05Z

Bernhard: first keywords to next steps

On Windows Mobile 6.5 (CE) Kontact Touch has a resource problem,
the searching and indexing is done via strigifeeder and strigidaemon.

Next steps:
* find all places where search is needed
:# real search dialog (_not_ quicksearch)
:# to-field autocompletion
:# ? Calendar?
* how much memory does strigidaemon actually use?
* check if clucene used by strigidaemon cannot be tuned to use less memory
* implement a display of the last index run, e.g on the search page
* implement a button to trigger a manual index, e.g. on the search page (both can be reused once we come up with an idea when the indexer should run.)
* Can we reliably see if the device is under low load, e.g. if only one or no frontend is running?

Options as tokoe saw them 2011020914:32:
1) A UI option to switch strigi_feeder between online/offline mode

pro: The strigi_feeder in offline mode wouldn't index anything until it
is switched back to online mode. So it would take away pressure on the
device during initial sync, since CPU and I/O usage is reduced.

contra: Since recent data are not indexed with strigi_feeder in offline
mode, some internal searches might not return the correct, or better
said 'expected', data. Switching the strigi_feeder to online mode
automatically when a search is started is not really an option,
because feeding the new data to strigidaemon takes a while, so they
won't be included in the current search results.

costs: We have to extend strigi_feeder to correctly record actions during
offline mode and replay them when switched to online mode.
Furthermore we need options in the UI to switch the mode of the
strigifeeder (Ideas from Björn Balazs?).

2) IDLE detection in strigidaemon with automatic shutdown

pro: Afaik strigidaemon uses lots of memory when running, so
stopping strigidaemon whenever no indexing or search is done,
should provide some free memory on the device.

contra: Searches are done quite often (e.g. the autocompletion in mail
composer) and strigi_feeder will index data as soon as something
changes (e.g. read flags in emails), so I doubt that strigidaemon
will have long idle sessions. Strigidaemon might cause additional
costs during its startup/shutdown phase.

costs: We have to implement an idle detection in strigidaemon
(non qt-based!) and a clean shutdown procedure.
Furthermore we have to extend akonadiserver to handle the
disappearance of strigi dbus interface gracefully and restart the
strigidaemon on demand. This needs a lot of testing!

It would be possible to combine 1) and 2), but this will increase the number
of side effects, so much more testing is needed.

Projects/KDE PIM/Development/Mobile/ResourcesCESearch

2011-02-09T15:04:14Z

Bernhard: created

On Windows Mobile 6.5 (CE) Kontact Touch has a resource problem,
the searching and indexing is done via strigifeeder and strigidaemon.

Options as tokoe saw them 2011020914:32:
1) A UI option to switch strigi_feeder between online/offline mode

pro: The strigi_feeder in offline mode wouldn't index anything until it
is switched back to online mode. So it would take away pressure on the
device during initial sync, since CPU and I/O usage is reduced.

contra: Since recent data are not indexed with strigi_feeder in offline
mode, some internal searches might not return the correct, or better
said 'expected', data. Switching the strigi_feeder to online mode
automatically when a search is started is not really an option,
because feeding the new data to strigidaemon takes a while, so they
won't be included in the current search results.

costs: We have to extend strigi_feeder to correctly record actions during
offline mode and replay them when switched to online mode.
Furthermore we need options in the UI to switch the mode of the
strigifeeder (Ideas from Björn Balazs?).

2) IDLE detection in strigidaemon with automatic shutdown

pro: Afaik strigidaemon uses lots of memory when running, so
stopping strigidaemon whenever no indexing or search is done,
should provide some free memory on the device.

contra: Searches are done quite often (e.g. the autocompletion in mail
composer) and strigi_feeder will index data as soon as something
changes (e.g. read flags in emails), so I doubt that strigidaemon
will have long idle sessions. Strigidaemon might cause additional
costs during its startup/shutdown phase.

costs: We have to implement an idle detection in strigidaemon
(non qt-based!) and a clean shutdown procedure.
Furthermore we have to extend akonadiserver to handle the
disappearance of strigi dbus interface gracefully and restart the
strigidaemon on demand. This needs a lot of testing!

It would be possible to combine 1) and 2), but this will increase the number
of side effects, so much more testing is needed.

Projects/KDE PIM/Development/Mobile

2011-02-09T15:00:57Z

Bernhard: added dev item section with first entry

== About Kontact Touch ==

Kontact Touch brings the power of the KDE desktop appliction 'Kontact' to the world of touch screen devices.

[http://userbase.kde.org/Kontact_Touch More information about this product on userbase.kde.org]

== Defining the functional scope ==
The following pages contain the functional scope of the different Kontact Touch frontends:

* [[Projects/KDE_PIM/Development/Mobile/KMail_FunctionalScope|Mail]]
* [[Projects/KDE_PIM/Development/Mobile/Kalendar_FunctionalScope|Calendar]]
* [[Projects/KDE_PIM/Development/Mobile/KTasks_FunctionalScope|Tasks]]
* [[Projects/KDE_PIM/Development/Mobile/KAddressbook_FunctionalScope|Contacts]]
* [[Projects/KDE_PIM/Development/Mobile/KJots_FunctionalScope|Notes]]

== Development topics ==
* [[Projects/KDE_PIM/Development/Mobile/ResourcesCESearch|Resources use of searching for CE]]

Projects/KDE PIM/Development/Mobile

2011-02-09T14:59:14Z

Bernhard: Using the frontend names

Projects/KDE PIM/Development/Mobile

2011-02-09T14:57:31Z

Bernhard: /* About Kontact-Mobile */ It is "Kontact Touch" now.

== About Kontact Touch ==

Kontact Touch brings the power of the KDE desktop appliction 'Kontact' to the world of touch screen devices.

[http://userbase.kde.org/Kontact_Touch More information about this product on userbase.kde.org]

== Defining the functional scope ==
The following pages contain the functional scope of the different Kontact Mobile frontends:

* [[Projects/KDE_PIM/Development/Mobile/KMail_FunctionalScope|KMail]]
* [[Projects/KDE_PIM/Development/Mobile/Kalendar_FunctionalScope|Kalendar]]
* [[Projects/KDE_PIM/Development/Mobile/KTasks_FunctionalScope|KTasks]]
* [[Projects/KDE_PIM/Development/Mobile/KAddressbook_FunctionalScope|KAddressbook]]
* [[Projects/KDE_PIM/Development/Mobile/KJots_FunctionalScope|KJots]]

Projects/KDE PIM/Development/Mobile/Calendar FunctionalScope

2010-09-27T13:12:43Z

Bernhard: moved Projects/KDE PIM/Development/Mobile/Kalendar FunctionalScope to Projects/KDE PIM/Development/Mobile/Calendar FunctionalScope: Type fixed

== Functional Scope of Kontact Mobile - Calendar ==

Following you will find a set contaxtual actions available in the different views
Kontact Mobile - Calendar offers. This way the functional scope is defined.

=== Always available ===
Elements of this section are always visible. This section is always the last section displayed in the contextual menu.

{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="7" valign="top"| Kontact Mobile - Calendar
| Quit Kalender
| OK
|
|-
| Open Task Switcher
| OK
|
|-
| Add new event
| OK
|
|-
| Find event
| Defered
| Opens Search Dialogue - behaves excactly the same as Multiple selection - so results can altered by going back to selection, Search+View can be saved as favorite (Search targets: summary, categories, date range, maybe location)
|-
| Work offline
| OK
|
|-
| Configure Kalender
| Defered
| timezones, holiday regions, tasks, working period, current timezone
|-
| About Kalender
| OK
|
|}

=== Home ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="2" valign="top"|Home
| Sync all events
| OK
|
|-
| Select multiple folders
| OK
| Initiate multiple selection
|-
| rowspan="3" valign="top"| Favorites (OrderFlap)
| Reorder
| OK
|
|-
| Make / Remove default
| Under Discussion
| Default Favorite should be loaded when application starts / Only one default is possible / it must be possible to remove a default and have none - then app is starting with homepage -> Actually right now the application loads the last opend folder on startup, which doesn't seem unreasonable either
|-
| Delete
| OK
|
|-
| rowspan="4" valign="top"| Accounts (OrderFlap)
| Reorder
| Under Discussion
| Reordering is not available on the desktop either
|-
| Edit
| OK
|
|-
| Delete
| OK
|
|-
| Add
| OK
|
|}

=== Account ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="3" valign="top"| Account
| Sync events in account
| OK
|
|-
| Edit account
| OK
| Edit dialogue for account configuration, should contain possibility for Renaming
|-
| Add subfolder
| OK
| Detailed Dialogue for new folder. Parent is prefilled
|}

=== Single folder view ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="1" valign="top"| Folder
| Sync events in folder
| OK
|
|-
| rowspan="5" valign="top"| Edit
| Edit folder
| OK
|
|-
| Add Subfolder
| OK
|
|-
| Move folder to
| OK
|
|-
| Copy folder to
| OK
|
|-
| Delete folder
| OK
|
|-
| rowspan="3" valign="top"| View
| Start maintainence mode
| OK
| Starts Bulk-Action dialogue (Move, Copy, Delete, Toggle Reminders / Alarms)
|-
| Filter view
| Under discussion
| Possibility to filter the mails in the folder (e.g. by name, subject etc.)
|-
| View options
| Under discussion
| View option address sorting of items etc.
|}

=== Multiple folder view ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="1" valign="top"| Folders
| Sync events in selected folders
| OK
|
|-
| rowspan="4" valign="top"| View
| Change folder selection
| OK
|
|-
| Start maintainence mode
| OK
| Starts Bulk-Action dialogue (Move, Copy, Delete, Toggle Reminders / Alarms)
|-
| Filter view
| Under discussion
| Possibility to filter the mails in the folder (e.g. by name, subject etc.)
|-
| View options
| Under discussion
| View option address sorting of items etc.
|}

=== Single calender view ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="6" valign="top"| Calender
| Sync events in calender
| OK
|
|-
| Show today
| OK
|
|-
| Day layout
| OK
|
|-
| Week layout
| OK
|
|-
| Month layout
| OK
|
|-
| Other
| Under Discussion
| We need to define which other views we want to integrate here (e.g. Journal,...)
|-
| rowspan="4" valign="top"| View
| Add as favorite / Rename favorite
| OK
|
|-
| Back to folder selection
| OK
|
|-
| Filter view
| Under discussion
| Anything needed here?
|-
| View options
| Under discussion
| Anything needed here?
|-
|}

=== Multiple calender view ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="6" valign="top"| Calenders
| Sync events in selected calenders
| OK
|
|-
| Show today
| OK
|
|-
| Day layout
| OK
|
|-
| Week layout
| OK
|
|-
| Month layout
| OK
|
|-
| Other
| Under Discussion
| We need to define which other views we want to integrate here (e.g. Journal,...)
|-
| rowspan="4" valign="top"| View
| Add as favorite / Rename favorite
| OK
|
|-
| Back to folder selection
| OK
|
|-
| Filter view
| Under discussion
| Anything needed here?
|-
| View options
| Under discussion
| Anything needed here?
|-
|}

=== Event viewer ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="10" valign="top"| Event
| Detach event
|
| Detaches a nested event - only show if possible
|-
| Publish Item Information
|
|
|-
| Send invitations to attendees
|
|
|-
| Send status update
|
|
|-
| Send cancellation to attendees
|
|
|-
| Request update
|
|
|-
| Request change
|
|
|-
| Send as iCalender
|
|
|-
| Mail free busy information
|
|
|-
| Upload free busy information
|
|
|-
| Attachments
| Save (all)
| Under Discussion
| Show only if attachments exists / View tbd
|-
| rowspan="4" valign="top"| Edit
| Edit event
| OK
|
|-
| Copy event to calender
| OK
|
|-
| Move event to calender
| OK
|
|-
| Delete event
| OK
|
|-
|}

=== Open ===
Here you can find functionallity that still needs to be discussed, wether it makes sense to add it to the mobile version of KDE PIM.

==== We do not need this ====
* Print
* Publish (Webpage, vCalender, hot new stuff)

==== We need to discuss this ====

==== We need to integrate this ====
* Export/Import, we should support one standard format, iCalender.
* "Disassociate from recurrence" should be solved as part of handling recurrent appointments (including acceptence of invitations and exceptions for single dates).

Projects/KDE PIM/Development/Mobile/Kalendar FunctionalScope

2010-09-27T13:12:43Z

Bernhard: moved Projects/KDE PIM/Development/Mobile/Kalendar FunctionalScope to Projects/KDE PIM/Development/Mobile/Calendar FunctionalScope: Type fixed

#REDIRECT [[Projects/KDE PIM/Development/Mobile/Calendar FunctionalScope]]

Projects/KDE PIM/Development/Mobile/Calendar FunctionalScope

2010-09-27T13:12:19Z

Bernhard: /* Functional Scope of Kontact Mobile - Kalender */ Kalender -> Calendar

Projects/KDE PIM/Development/Mobile

2010-08-27T14:07:38Z

Bernhard: /* Defining the functional scope */

== About Kontact-Mobile ==

Kontact-Mobile brings the power of the KDE desktop appliction 'Kontact' to the mobile world. First phones to be supported are:

* Nokia N900
* HTC Touch Pro 2

[http://userbase.kde.org/Kontact_Mobile More information about this project on userbase.kde.org]

== Defining the functional scope ==
The following pages contain the functional scope of the different Kontact Mobile frontends:

* [[Projects/KDE_PIM/Development/Mobile/KMail_FunctionalScope|KMail]]
* [[Projects/KDE_PIM/Development/Mobile/Kalendar_FunctionalScope|Kalendar]]
* [[Projects/KDE_PIM/Development/Mobile/KTasks_FunctionalScope|KTasks]]
* [[Projects/KDE_PIM/Development/Mobile/KAddressbook_FunctionalScope|KAddressbook]]
* [[Projects/KDE_PIM/Development/Mobile/KJots_FunctionalScope|KJots]]

Projects/KDE PIM/Development/Mobile

2010-08-27T14:07:19Z

Bernhard: /* About KDE PIM Mobile */ More consistent with branding.

== About Kontact-Mobile ==

Kontact-Mobile brings the power of the KDE desktop appliction 'Kontact' to the mobile world. First phones to be supported are:

* Nokia N900
* HTC Touch Pro 2

[http://userbase.kde.org/Kontact_Mobile More information about this project on userbase.kde.org]

== Defining the functional scope ==
The following pages contain the functional scope of the different Kontact Mobile applications:

* [[Projects/KDE_PIM/Development/Mobile/KMail_FunctionalScope|KMail]]
* [[Projects/KDE_PIM/Development/Mobile/Kalendar_FunctionalScope|Kalendar]]
* [[Projects/KDE_PIM/Development/Mobile/KTasks_FunctionalScope|KTasks]]
* [[Projects/KDE_PIM/Development/Mobile/KAddressbook_FunctionalScope|KAddressbook]]
* [[Projects/KDE_PIM/Development/Mobile/KJots_FunctionalScope|KJots]]

Projects/KDE PIM/Development/Mobile/KTasks FunctionalScope

2010-08-26T12:56:24Z

Bernhard: /* Open */

== Functional Scope of Kontact Mobile - KTasks ==

Following you will find a set contaxtual actions available in the different views Kontact Mobile - KTasks offers. This way the functional scope is defined.

=== Always available ===
Elements of this section are always visible. This section is always the last section displayed in the contextual menu.

{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="7" valign="top"| Kontact Mobile - KTasks
| Quit KTasks
| OK
|
|-
| Open Task Switcher
| OK
|
|-
| Add new ToDo
|
|
|-
| Find ToDo
|
| Opens Search Dialogue - behaves excactly the same as Multiple selection - so results can altered by going back to selection, Search+View can be saved as favorite (Search targets: summary, categories, date range, maybe location)
|-
| Work offline
|
|
|-
| Configure KTasks
| Under discussion
| Do we need a configuration dialogue for KTasks?
|-
| About KTasks
|
|
|}

=== Home ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="3" valign="top"|Home
| Sync all ToDos
| OK
|
|-
| Select multiple folders
| OK
| Initiate multiple selection
|-
| Purge completed ToDos
|
|
|-
| rowspan="3" valign="top"| Favorites (OrderFlap)
| Reorder
|
|
|-
| Make / Remove default
| Under Discussion
| Default Favorite should be loaded when application starts / Only one default is possible / it must be possible to remove a default and have none - then app is starting with homepage -> Actually right now the application loads the last opend folder on startup, which doesn't seem unreasonable either
|-
| Delete
|
|
|-
| rowspan="4" valign="top"| Accounts (OrderFlap)
| Reorder
| Under Discussion
| Reordering is not available on the desktop either
|-
| Edit
| OK
|
|-
| Delete
| OK
|
|-
| Add
| OK
|
|}

=== Account ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="3" valign="top"| Account
| Sync ToDos in account
| OK
|
|-
| Edit account
| OK
| Edit dialogue for account configuration, should contain possibility for Renaming
|-
| Add subfolder
| OK
| Detailed Dialogue for new folder. Parent is prefilled
|}

=== Single folder view ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="2" valign="top"| Folder
| Sync ToDos in folder
| OK
|
|-
| Purge completed
|
|
|-
| rowspan="5" valign="top"| Edit
| Edit folder
| OK
|
|-
| Add subfolder
| OK
|
|-
| Move folder to
| OK
|
|-
| Copy folder to
| OK
|
|-
| Delete folder
| OK
|
|-
| rowspan="4" valign="top"| View
| Add as favorite / Rename favorite
| OK
|
|-
| Start maintainence mode
|
| Starts Bulk-Action dialogue (Move, Copy, Delete, Toggle Reminders / Alarms)
|-
| Filter view
| Under discussion
| Possibility to filter the mails in the folder (e.g. by name, subject etc.)
|-
| View options
| Under discussion
| View option address sorting of items etc.
|}

=== Multiple folder view ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="2" valign="top"| Folder
| Sync ToDos in selected folder
|
|
|-
| Purge comleted ToDos
|
|
|-
| rowspan="5" valign="top"| View
| Add as favorite / Rename favorite
|
|
|-
| Change folder selection
|
|
|-
| Start maintainence mode
|
| Starts Bulk-Action dialogue (Move, Copy, Delete, Toggle Reminders / Alarms)
|-
| Filter view
| Under discussion
| Possibility to filter the mails in the folder (e.g. by name, subject etc.)
|-
| View options
| Under discussion
| View option address sorting of items etc.
|}

=== ToDo viewer ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="3" valign="top"| ToDo
| New Sub-ToDo
|
|
|-
| Make this Sub ToDo independent
|
| Only show if aplicable
|-
| Make all Sub ToDo independent
|
| Only show if aplicable
|-
| Attachments
| Save (all)
| Under Discussion
| Show only if attachments exists / View tbd
|-
| rowspan="4" valign="top"| Edit
| Edit ToDo
|
|
|-
| Copy ToDo to folder
| OK
|
|-
| Move ToDo to folder
| OK
|
|-
| Delete ToDo
| OK
|
|-
|}

=== Open ===
Here you can find functionallity that still needs to be discussed, wether it makes sense to add it to the mobile version of KDE PIM.

==== We do not need this ====
* Print
* Configure date & Time
* Archive (better replaced by combining "expire and move" in a single folder with "export" a folder)

==== We need to discuss this ====

==== We need to integrate this ====
* Export/Import, we should support one standard format, iCalender. Should be able to exprot a single folder.
* "Disassociate from recurrence" should be solved as part of handling
* Category handling (simple version)
* Expire X days after last occurrance of appointments, either delete or move to a different folder.

Projects/KDE PIM/Development/Mobile/Calendar FunctionalScope

2010-08-26T12:42:03Z

Bernhard: /* Open */ preselected by Björn B and Bernhard E R.

== Functional Scope of Kontact Mobile - Kalender ==

Following you will find a set contaxtual actions available in the different views
Kontact Mobile - Kalender offers. This way the functional scope is defined.

=== Always available ===
Elements of this section are always visible. This section is always the last section displayed in the contextual menu.

{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="7" valign="top"| Kontact Mobile - Kalender
| Quit Kalender
| OK
|
|-
| Open Task Switcher
| OK
|
|-
| Add new event
| OK
|
|-
| Find event
|
| Opens Search Dialogue - behaves excactly the same as Multiple selection - so results can altered by going back to selection, Search+View can be saved as favorite (Search targets: summary, categories, date range, maybe location)
|-
| Work offline
|
|
|-
| Configure Kalender
|
| timezones, holiday regions, tasks, working period, current timezone
|-
| About Kalender
|
|
|}

=== Home ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="2" valign="top"|Home
| Sync all events
| OK
|
|-
| Select multiple folders
| OK
| Initiate multiple selection
|-
| rowspan="3" valign="top"| Favorites (OrderFlap)
| Reorder
|
|
|-
| Make / Remove default
| Under Discussion
| Default Favorite should be loaded when application starts / Only one default is possible / it must be possible to remove a default and have none - then app is starting with homepage -> Actually right now the application loads the last opend folder on startup, which doesn't seem unreasonable either
|-
| Delete
|
|
|-
| rowspan="4" valign="top"| Accounts (OrderFlap)
| Reorder
| Under Discussion
| Reordering is not available on the desktop either
|-
| Edit
| OK
|
|-
| Delete
| OK
|
|-
| Add
| OK
|
|}

=== Account ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="3" valign="top"| Account
| Sync events in account
| OK
|
|-
| Edit account
| OK
| Edit dialogue for account configuration, should contain possibility for Renaming
|-
| Add subfolder
| OK
| Detailed Dialogue for new folder. Parent is prefilled
|}

=== Single folder view ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="1" valign="top"| Folder
| Sync events in folder
| OK
|
|-
| rowspan="5" valign="top"| Edit
| Edit folder
| OK
|
|-
| Add Subfolder
| OK
|
|-
| Move folder to
| OK
|
|-
| Copy folder to
| OK
|
|-
| Delete folder
| OK
|
|-
| rowspan="3" valign="top"| View
| Start maintainence mode
|
| Starts Bulk-Action dialogue (Move, Copy, Delete, Toggle Reminders / Alarms)
|-
| Filter view
| Under discussion
| Possibility to filter the mails in the folder (e.g. by name, subject etc.)
|-
| View options
| Under discussion
| View option address sorting of items etc.
|}

=== Multiple folder view ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="1" valign="top"| Folders
| Sync events in selected folders
| OK
|
|-
| rowspan="4" valign="top"| View
| Change folder selection
|
|
|-
| Start maintainence mode
|
| Starts Bulk-Action dialogue (Move, Copy, Delete, Toggle Reminders / Alarms)
|-
| Filter view
| Under discussion
| Possibility to filter the mails in the folder (e.g. by name, subject etc.)
|-
| View options
| Under discussion
| View option address sorting of items etc.
|}

=== Single calender view ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="6" valign="top"| Calender
| Sync events in calender
|
|
|-
| Show today
|
|
|-
| Day layout
|
|
|-
| Week layout
|
|
|-
| Month layout
|
|
|-
| Other
| Under Discussion
| We need to define which other views we want to integrate here (e.g. Journal,...)
|-
| rowspan="4" valign="top"| View
| Add as favorite / Rename favorite
|
|
|-
| Back to folder selection
|
|
|-
| Filter view
| Under discussion
| Anything needed here?
|-
| View options
| Under discussion
| Anything needed here?
|-
|}

=== Multiple calender view ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="6" valign="top"| Calenders
| Sync events in selected calenders
|
|
|-
| Show today
|
|
|-
| Day layout
|
|
|-
| Week layout
|
|
|-
| Month layout
|
|
|-
| Other
| Under Discussion
| We need to define which other views we want to integrate here (e.g. Journal,...)
|-
| rowspan="4" valign="top"| View
| Add as favorite / Rename favorite
|
|
|-
| Back to folder selection
|
|
|-
| Filter view
| Under discussion
| Anything needed here?
|-
| View options
| Under discussion
| Anything needed here?
|-
|}

=== Event viewer ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="10" valign="top"| Event
| Detach event
|
| Detaches a nested event - only show if possible
|-
| Publish Item Information
|
|
|-
| Send invitations to attendees
|
|
|-
| Send status update
|
|
|-
| Send cancellation to attendees
|
|
|-
| Request update
|
|
|-
| Request change
|
|
|-
| Send as iCalender
|
|
|-
| Mail free busy information
|
|
|-
| Upload free busy information
|
|
|-
| Attachments
| Save (all)
| Under Discussion
| Show only if attachments exists / View tbd
|-
| rowspan="4" valign="top"| Edit
| Edit event
|
|
|-
| Copy event to calender
| OK
|
|-
| Move event to calender
| OK
|
|-
| Delete event
| OK
|
|-
|}

=== Open ===
Here you can find functionallity that still needs to be discussed, wether it makes sense to add it to the mobile version of KDE PIM.

==== We do not need this ====
* Print
* Publish (Webpage, vCalender, hot new stuff)

==== We need to discuss this ====

==== We need to integrate this ====
* Export/Import, we should support one standard format, iCalender.
* "Disassociate from recurrence" should be solved as part of handling recurrent appointments (including acceptence of invitations and exceptions for single dates).

Projects/KDE PIM/Development/Mobile/Calendar FunctionalScope

2010-08-26T12:36:09Z

Bernhard: /* Open */

== Functional Scope of Kontact Mobile - Kalender ==

Following you will find a set contaxtual actions available in the different views
Kontact Mobile - Kalender offers. This way the functional scope is defined.

=== Always available ===
Elements of this section are always visible. This section is always the last section displayed in the contextual menu.

{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="7" valign="top"| Kontact Mobile - Kalender
| Quit Kalender
| OK
|
|-
| Open Task Switcher
| OK
|
|-
| Add new event
| OK
|
|-
| Find event
|
| Opens Search Dialogue - behaves excactly the same as Multiple selection - so results can altered by going back to selection, Search+View can be saved as favorite (Search targets: summary, categories, date range, maybe location)
|-
| Work offline
|
|
|-
| Configure Kalender
|
| timezones, holiday regions, tasks, working period, current timezone
|-
| About Kalender
|
|
|}

=== Home ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="2" valign="top"|Home
| Sync all events
| OK
|
|-
| Select multiple folders
| OK
| Initiate multiple selection
|-
| rowspan="3" valign="top"| Favorites (OrderFlap)
| Reorder
|
|
|-
| Make / Remove default
| Under Discussion
| Default Favorite should be loaded when application starts / Only one default is possible / it must be possible to remove a default and have none - then app is starting with homepage -> Actually right now the application loads the last opend folder on startup, which doesn't seem unreasonable either
|-
| Delete
|
|
|-
| rowspan="4" valign="top"| Accounts (OrderFlap)
| Reorder
| Under Discussion
| Reordering is not available on the desktop either
|-
| Edit
| OK
|
|-
| Delete
| OK
|
|-
| Add
| OK
|
|}

=== Account ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="3" valign="top"| Account
| Sync events in account
| OK
|
|-
| Edit account
| OK
| Edit dialogue for account configuration, should contain possibility for Renaming
|-
| Add subfolder
| OK
| Detailed Dialogue for new folder. Parent is prefilled
|}

=== Single folder view ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="1" valign="top"| Folder
| Sync events in folder
| OK
|
|-
| rowspan="5" valign="top"| Edit
| Edit folder
| OK
|
|-
| Add Subfolder
| OK
|
|-
| Move folder to
| OK
|
|-
| Copy folder to
| OK
|
|-
| Delete folder
| OK
|
|-
| rowspan="3" valign="top"| View
| Start maintainence mode
|
| Starts Bulk-Action dialogue (Move, Copy, Delete, Toggle Reminders / Alarms)
|-
| Filter view
| Under discussion
| Possibility to filter the mails in the folder (e.g. by name, subject etc.)
|-
| View options
| Under discussion
| View option address sorting of items etc.
|}

=== Multiple folder view ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="1" valign="top"| Folders
| Sync events in selected folders
| OK
|
|-
| rowspan="4" valign="top"| View
| Change folder selection
|
|
|-
| Start maintainence mode
|
| Starts Bulk-Action dialogue (Move, Copy, Delete, Toggle Reminders / Alarms)
|-
| Filter view
| Under discussion
| Possibility to filter the mails in the folder (e.g. by name, subject etc.)
|-
| View options
| Under discussion
| View option address sorting of items etc.
|}

=== Single calender view ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="6" valign="top"| Calender
| Sync events in calender
|
|
|-
| Show today
|
|
|-
| Day layout
|
|
|-
| Week layout
|
|
|-
| Month layout
|
|
|-
| Other
| Under Discussion
| We need to define which other views we want to integrate here (e.g. Journal,...)
|-
| rowspan="4" valign="top"| View
| Add as favorite / Rename favorite
|
|
|-
| Back to folder selection
|
|
|-
| Filter view
| Under discussion
| Anything needed here?
|-
| View options
| Under discussion
| Anything needed here?
|-
|}

=== Multiple calender view ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="6" valign="top"| Calenders
| Sync events in selected calenders
|
|
|-
| Show today
|
|
|-
| Day layout
|
|
|-
| Week layout
|
|
|-
| Month layout
|
|
|-
| Other
| Under Discussion
| We need to define which other views we want to integrate here (e.g. Journal,...)
|-
| rowspan="4" valign="top"| View
| Add as favorite / Rename favorite
|
|
|-
| Back to folder selection
|
|
|-
| Filter view
| Under discussion
| Anything needed here?
|-
| View options
| Under discussion
| Anything needed here?
|-
|}

=== Event viewer ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="10" valign="top"| Event
| Detach event
|
| Detaches a nested event - only show if possible
|-
| Publish Item Information
|
|
|-
| Send invitations to attendees
|
|
|-
| Send status update
|
|
|-
| Send cancellation to attendees
|
|
|-
| Request update
|
|
|-
| Request change
|
|
|-
| Send as iCalender
|
|
|-
| Mail free busy information
|
|
|-
| Upload free busy information
|
|
|-
| Attachments
| Save (all)
| Under Discussion
| Show only if attachments exists / View tbd
|-
| rowspan="4" valign="top"| Edit
| Edit event
|
|
|-
| Copy event to calender
| OK
|
|-
| Move event to calender
| OK
|
|-
| Delete event
| OK
|
|-
|}

=== Open ===
Here you can find functionallity that still needs to be discussed, wether it makes sense to add it to the mobile version of KDE PIM.

==== We do not need this ====
* Print
==== We need to discuss this ====
* Publish (Webpage, iCalender, vCalender)

==== We need to integrate this ====
* Export/Import, we should support one standard format, iCalender.
* "Disassociate from recurrence" should be solved as part of handling recurrent appointments (including acceptence of invitations and exceptions for single dates).

Projects/KDE PIM/Development/Mobile/Calendar FunctionalScope

2010-08-26T12:35:16Z

Bernhard: /* Open */ preselected by Björn B and Bernhard E R.

== Functional Scope of Kontact Mobile - Kalender ==

Following you will find a set contaxtual actions available in the different views
Kontact Mobile - Kalender offers. This way the functional scope is defined.

=== Always available ===
Elements of this section are always visible. This section is always the last section displayed in the contextual menu.

{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="7" valign="top"| Kontact Mobile - Kalender
| Quit Kalender
| OK
|
|-
| Open Task Switcher
| OK
|
|-
| Add new event
| OK
|
|-
| Find event
|
| Opens Search Dialogue - behaves excactly the same as Multiple selection - so results can altered by going back to selection, Search+View can be saved as favorite (Search targets: summary, categories, date range, maybe location)
|-
| Work offline
|
|
|-
| Configure Kalender
|
| timezones, holiday regions, tasks, working period, current timezone
|-
| About Kalender
|
|
|}

=== Home ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="2" valign="top"|Home
| Sync all events
| OK
|
|-
| Select multiple folders
| OK
| Initiate multiple selection
|-
| rowspan="3" valign="top"| Favorites (OrderFlap)
| Reorder
|
|
|-
| Make / Remove default
| Under Discussion
| Default Favorite should be loaded when application starts / Only one default is possible / it must be possible to remove a default and have none - then app is starting with homepage -> Actually right now the application loads the last opend folder on startup, which doesn't seem unreasonable either
|-
| Delete
|
|
|-
| rowspan="4" valign="top"| Accounts (OrderFlap)
| Reorder
| Under Discussion
| Reordering is not available on the desktop either
|-
| Edit
| OK
|
|-
| Delete
| OK
|
|-
| Add
| OK
|
|}

=== Account ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="3" valign="top"| Account
| Sync events in account
| OK
|
|-
| Edit account
| OK
| Edit dialogue for account configuration, should contain possibility for Renaming
|-
| Add subfolder
| OK
| Detailed Dialogue for new folder. Parent is prefilled
|}

=== Single folder view ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="1" valign="top"| Folder
| Sync events in folder
| OK
|
|-
| rowspan="5" valign="top"| Edit
| Edit folder
| OK
|
|-
| Add Subfolder
| OK
|
|-
| Move folder to
| OK
|
|-
| Copy folder to
| OK
|
|-
| Delete folder
| OK
|
|-
| rowspan="3" valign="top"| View
| Start maintainence mode
|
| Starts Bulk-Action dialogue (Move, Copy, Delete, Toggle Reminders / Alarms)
|-
| Filter view
| Under discussion
| Possibility to filter the mails in the folder (e.g. by name, subject etc.)
|-
| View options
| Under discussion
| View option address sorting of items etc.
|}

=== Multiple folder view ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="1" valign="top"| Folders
| Sync events in selected folders
| OK
|
|-
| rowspan="4" valign="top"| View
| Change folder selection
|
|
|-
| Start maintainence mode
|
| Starts Bulk-Action dialogue (Move, Copy, Delete, Toggle Reminders / Alarms)
|-
| Filter view
| Under discussion
| Possibility to filter the mails in the folder (e.g. by name, subject etc.)
|-
| View options
| Under discussion
| View option address sorting of items etc.
|}

=== Single calender view ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="6" valign="top"| Calender
| Sync events in calender
|
|
|-
| Show today
|
|
|-
| Day layout
|
|
|-
| Week layout
|
|
|-
| Month layout
|
|
|-
| Other
| Under Discussion
| We need to define which other views we want to integrate here (e.g. Journal,...)
|-
| rowspan="4" valign="top"| View
| Add as favorite / Rename favorite
|
|
|-
| Back to folder selection
|
|
|-
| Filter view
| Under discussion
| Anything needed here?
|-
| View options
| Under discussion
| Anything needed here?
|-
|}

=== Multiple calender view ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="6" valign="top"| Calenders
| Sync events in selected calenders
|
|
|-
| Show today
|
|
|-
| Day layout
|
|
|-
| Week layout
|
|
|-
| Month layout
|
|
|-
| Other
| Under Discussion
| We need to define which other views we want to integrate here (e.g. Journal,...)
|-
| rowspan="4" valign="top"| View
| Add as favorite / Rename favorite
|
|
|-
| Back to folder selection
|
|
|-
| Filter view
| Under discussion
| Anything needed here?
|-
| View options
| Under discussion
| Anything needed here?
|-
|}

=== Event viewer ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="10" valign="top"| Event
| Detach event
|
| Detaches a nested event - only show if possible
|-
| Publish Item Information
|
|
|-
| Send invitations to attendees
|
|
|-
| Send status update
|
|
|-
| Send cancellation to attendees
|
|
|-
| Request update
|
|
|-
| Request change
|
|
|-
| Send as iCalender
|
|
|-
| Mail free busy information
|
|
|-
| Upload free busy information
|
|
|-
| Attachments
| Save (all)
| Under Discussion
| Show only if attachments exists / View tbd
|-
| rowspan="4" valign="top"| Edit
| Edit event
|
|
|-
| Copy event to calender
| OK
|
|-
| Move event to calender
| OK
|
|-
| Delete event
| OK
|
|-
|}

=== Open ===
Here you can find functionallity that still needs to be discussed, wether it makes sense to add it to the mobile version of KDE PIM.

==== We do not need this ====
* Print
==== We need to discuss this ====
* Publish (Webpage, iCalender, vCalender)

==== We need to integrate this ====
* Export/Import, we should support one standard format, iCalender.
* "Disassociate from recurrence" should be solved as part of handling
recurrent appointments (including acceptence of invitations and exceptions
for single dates).

Projects/KDE PIM/Development/Mobile/KMail FunctionalScope

2010-08-26T09:16:46Z

Bernhard: /* We need to integrate this */

== Functional Scope of Kontact Mobile - KMail ==

Following you will find a set contaxtual actions available in the different views Kontact Mobile - KMail offers. This way the functional scope is defined.

=== Always available ===
Elements of this section are always visible. This section is always the last section displayed in the contextual menu.

{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="8" valign="top"| Kontact Mobile - KMail
| Quit KMail
| OK
|
|-
| Open Task Switcher
| OK
|
|-
| Write new email
|
|
|-
| Find message
|
| Opens Search Dialogue - behaves excactly the same as Multiple selection - so results can altered by going back to selection, Search+View can be saved as favorite
|-
| Work offline
|
|
|-
| Configure KMail
|
|
|-
| Configure notifications
|
|
|-
| About KMail
|
|
|}

=== Home ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="5" valign="top"| Home
| Sync all emails
| Under discusssion
| Send and recieve mails (VK: very confusing to have sync and check mail, even I wouldn't know the difference)
|-
| Check emails
|
| Long press offers dialogue to specify account - Thought to be only fetching mails, not sending them - that is how I understood the functionallity in desktop version
|-
| Send queued emails
|
| Long press offers dialogue to specify "via..."
|-
| Select multiple folders
|
| Initiate multiple selection
|-
| Empty all trash folders
|
|
|-
| rowspan="3" valign="top"| Favorites (OrderFlap)
| Reorder
|
|
|-
| Make / Remove default
| Under Discussion
| Default Favorite should be loaded when application starts / Only one default is possible / it must be possible to remove a default and have none - then app is starting with homepage -> Actually right now the application loads the last opend folder on startup, which doesn't seem unreasonable either
|-
| Delete
|
|
|-
| rowspan="4" valign="top"| Accounts (OrderFlap)
| Reorder
| Under Discussion
| Reordering is not available on the desktop either
|-
| Edit
| OK
|
|-
| Delete
| OK
|
|-
| Add
| OK
|
|-
| rowspan="4" valign="top"| Identities (OrderFlap)
| Edit
| OK
|
|-
| Make Default
| OK
|
|-
| Delete
| OK
|
|-
| Add
| OK
|
|}

=== Account ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="5" valign="top"| Account
| Check mail in account
| OK
|
|-
| Serverside subscription...
| Not implemented
| Nowadays both on desktop and mobile, the server side subscription dialog is accessible from the account configuration dialog.
|-
| Local subscription...
| OK
|
|-
| Edit account
| OK
| Edit dialogue for account configuration, should contain possibility for Renaming
|-
| Add subfolder
| OK
| Detailed Dialogue for new folder. Parent is prefilled
|}

=== Single folder view ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="8" valign="top"| Folder
| Check emails in folder
| OK
|
|-
| Mark all emails as read
| OK
|
|-
| Move all emails to trash
| OK
|
|-
| Remove duplicate emails
| OK
|
|-
| Archive folder
| Under Discussion
| Is that really something you do on a phone?
|-
| Expire rules
|
|
|-
| Mailing-list management
| Under discussion
|
|-
| Empty trash
|
| only if folder is a trash folder
|-
| rowspan="5" valign="top"| Edit
| Edit folder
| OK
|
|-
| Add subfolder
| OK
|
|-
| Move folder to
| OK
|
|-
| Copy folder to
| OK
|
|-
| Delete folder
| OK
|
|-
| rowspan="6" valign="top"| View
| Add as favorite / Rename favorite
| OK
|
|-
| Start maintainence mode
|
| Starts Bulk-Action dialogue (Move, Copy, Delete, Toggle Reminders / Alarms)
|-
| Prefer HTML to plain text
|
|
|-
| Load external references
|
|
|-
| Filter view
| Under discussion
| Possibility to filter the mails in the folder (e.g. by name, subject etc.)
|-
| View options
| Under discussion
| View option address sorting of items etc.
|}

=== Multiple folder view ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="5" valign="top"| Folders
| Check emails in selected folders
|
|
|-
| Mark all emails as read
|
|
|-
| Move all emails to trash
|
|
|-
| Remove dublicate emails
|
|
|-
| Archive selected folders
| Under Discussion
| Is that really something you do on a phone?
|-
| rowspan="7" valign="top"| View
| Add as favorite / Rename favorite
| OK
|
|-
| Change folder selection
|
|
|-
| Start maintainence mode
|
| Starts Bulk-Action dialogue (Move, Copy, Delete, Toggle Reminders / Alarms)
|-
| Prefer HTML to plain text
|
|
|-
| Load external references
|
|
|-
| Filter view
| Under discussion
| Possibility to filter the mails in the folder (e.g. by name, subject etc.)
|-
| View options
| Under discussion
| View option address sorting of items etc.
|}

=== Message viewer ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="7" valign="top"| Email
| Reply
|
| long press offers dialogue to choose non-standard reply
|-
| Forward
|
| long press offers dialogue to choose non-standard reply
|-
| Mark email as...
| OK
| unread / read / important,... Works, but not as a submenu of Email.
|-
| Send again
|
|
|-
| Create to-do reminder
|
|
|-
| Find in email
|
|
|-
| Save as
|
|
|-
| Attachments
| Save (all)
| Under Discussion
| Show only if attachments exists / View tbd
|-
| rowspan="4" valign="top"| Edit
| Edit email
|
|
|-
| Copy email to folder
| OK
|
|-
| Move email to folder
| OK
|
|-
| Delete email
| OK
|
|-
|}

=== Open ===
Here you can find functionallity that still needs to be discussed, wether it makes sense to add it to the mobile version of KDE PIM.

==== We do not need this ====
* Print, Rationale: not practical from a handheld decive, most have no printer connection
* Shortcuts (keyboard "accellerators"), Rationale: not needed in a touch screen handheld
* General Sieve Skripts
* Out of office replies - use web-interface if needed
* Multiple views - substituted by favorites concepts
* Copy
* Select all text
* Log viewer

==== We need to discuss this ====
* Templates
* Expire all folders
* Refresh local imap cache
* Undo
* Threads
* Move thread to trash
* Mark thread as...
* select all messages
* Go options
* Anti-Spam
* Anti-Virus
* Certificate Manager
* GnuPG log viewer
* What does subscription actually do? Does it belong to account or to folder level?
* View source - how expensive is this?
* Use fixed font - how expensive is this?

==== We need to integrate this ====
* Show message structure - we need some smart solution to handle multiple attachement and enbedded mails and to include parts of other objects into object (e.g. mail - to substitute drag&drop)
* Import messages / Open... / Save / Export - only provide basic import functionality (e.g. mbox and maildir)

Projects/KDE PIM/Development/Mobile/KMail FunctionalScope

2010-08-26T08:25:04Z

Bernhard: /* We do not need this */

== Functional Scope of Kontact Mobile - KMail ==

Following you will find a set contaxtual actions available in the different views Kontact Mobile - KMail offers. This way the functional scope is defined.

=== Always available ===
Elements of this section are always visible. This section is always the last section displayed in the contextual menu.

{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="8" valign="top"| Kontact Mobile - KMail
| Quit KMail
| OK
|
|-
| Open Task Switcher
| OK
|
|-
| Write new email
|
|
|-
| Find message
|
| Opens Search Dialogue - behaves excactly the same as Multiple selection - so results can altered by going back to selection, Search+View can be saved as favorite
|-
| Work offline
|
|
|-
| Configure KMail
|
|
|-
| Configure notifications
|
|
|-
| About KMail
|
|
|}

=== Home ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="5" valign="top"| Home
| Sync all emails
| Under discusssion
| Send and recieve mails (VK: very confusing to have sync and check mail, even I wouldn't know the difference)
|-
| Check emails
|
| Long press offers dialogue to specify account - Thought to be only fetching mails, not sending them - that is how I understood the functionallity in desktop version
|-
| Send queued emails
|
| Long press offers dialogue to specify "via..."
|-
| Select multiple folders
|
| Initiate multiple selection
|-
| Empty all trash folders
|
|
|-
| rowspan="3" valign="top"| Favorites (OrderFlap)
| Reorder
|
|
|-
| Make / Remove default
| Under Discussion
| Default Favorite should be loaded when application starts / Only one default is possible / it must be possible to remove a default and have none - then app is starting with homepage -> Actually right now the application loads the last opend folder on startup, which doesn't seem unreasonable either
|-
| Delete
|
|
|-
| rowspan="4" valign="top"| Accounts (OrderFlap)
| Reorder
| Under Discussion
| Reordering is not available on the desktop either
|-
| Edit
| OK
|
|-
| Delete
| OK
|
|-
| Add
| OK
|
|-
| rowspan="4" valign="top"| Identities (OrderFlap)
| Edit
| OK
|
|-
| Make Default
| OK
|
|-
| Delete
| OK
|
|-
| Add
| OK
|
|}

=== Account ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="5" valign="top"| Account
| Check mail in account
| OK
|
|-
| Serverside subscription...
| Not implemented
| Nowadays both on desktop and mobile, the server side subscription dialog is accessible from the account configuration dialog.
|-
| Local subscription...
| OK
|
|-
| Edit account
| OK
| Edit dialogue for account configuration, should contain possibility for Renaming
|-
| Add subfolder
| OK
| Detailed Dialogue for new folder. Parent is prefilled
|}

=== Single folder view ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="8" valign="top"| Folder
| Check emails in folder
| OK
|
|-
| Mark all emails as read
| OK
|
|-
| Move all emails to trash
| OK
|
|-
| Remove duplicate emails
| OK
|
|-
| Archive folder
| Under Discussion
| Is that really something you do on a phone?
|-
| Expire rules
|
|
|-
| Mailing-list management
| Under discussion
|
|-
| Empty trash
|
| only if folder is a trash folder
|-
| rowspan="5" valign="top"| Edit
| Edit folder
| OK
|
|-
| Add subfolder
| OK
|
|-
| Move folder to
| OK
|
|-
| Copy folder to
| OK
|
|-
| Delete folder
| OK
|
|-
| rowspan="6" valign="top"| View
| Add as favorite / Rename favorite
| OK
|
|-
| Start maintainence mode
|
| Starts Bulk-Action dialogue (Move, Copy, Delete, Toggle Reminders / Alarms)
|-
| Prefer HTML to plain text
|
|
|-
| Load external references
|
|
|-
| Filter view
| Under discussion
| Possibility to filter the mails in the folder (e.g. by name, subject etc.)
|-
| View options
| Under discussion
| View option address sorting of items etc.
|}

=== Multiple folder view ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="5" valign="top"| Folders
| Check emails in selected folders
|
|
|-
| Mark all emails as read
|
|
|-
| Move all emails to trash
|
|
|-
| Remove dublicate emails
|
|
|-
| Archive selected folders
| Under Discussion
| Is that really something you do on a phone?
|-
| rowspan="7" valign="top"| View
| Add as favorite / Rename favorite
| OK
|
|-
| Change folder selection
|
|
|-
| Start maintainence mode
|
| Starts Bulk-Action dialogue (Move, Copy, Delete, Toggle Reminders / Alarms)
|-
| Prefer HTML to plain text
|
|
|-
| Load external references
|
|
|-
| Filter view
| Under discussion
| Possibility to filter the mails in the folder (e.g. by name, subject etc.)
|-
| View options
| Under discussion
| View option address sorting of items etc.
|}

=== Message viewer ===
{| border="1"
|-
! Category
! Action
! Status
! Comment
|-
| rowspan="7" valign="top"| Email
| Reply
|
| long press offers dialogue to choose non-standard reply
|-
| Forward
|
| long press offers dialogue to choose non-standard reply
|-
| Mark email as...
| OK
| unread / read / important,... Works, but not as a submenu of Email.
|-
| Send again
|
|
|-
| Create to-do reminder
|
|
|-
| Find in email
|
|
|-
| Save as
|
|
|-
| Attachments
| Save (all)
| Under Discussion
| Show only if attachments exists / View tbd
|-
| rowspan="4" valign="top"| Edit
| Edit email
|
|
|-
| Copy email to folder
| OK
|
|-
| Move email to folder
| OK
|
|-
| Delete email
| OK
|
|-
|}

=== Open ===
Here you can find functionallity that still needs to be discussed, wether it makes sense to add it to the mobile version of KDE PIM.

==== We do not need this ====
* Print, Rationale: not practical from a handheld decive, most have no printer connection
* Shortcuts (keyboard "accellerators"), Rationale: not needed in a touch screen handheld
* Sieve
* View source
* Use fixed font
* Show message structure
* Multiple views
* Import messages
* Open...
* Copy
* Select all text
* Log viewer

==== We need to discuss this ====
* Templates
* Expire all folders
* Refresh local imap cache
* Undo
* Out of office replies
* Threads
* Move thread to trash
* Mark thread as...
* select all messages
* Go options
* Anti-Spam
* Anti-Virus
* Certificate Manager
* GnuPG log viewer
* What does subscription actually do? Does it belong to account or to folder level?

==== We need to integrate this ====

Projects/PIM/Akonadi/Development Tools

2010-08-24T15:11:52Z

Bernhard: /* Limitations */ Stressing the UID point.

= Akonadi Developer Tools =

== Akonadi Console ==

Akonadi Console is a tool for developers working with Akonadi or on Akonadi itself.

It provides GUI for

* managing agents and resources
* retrieving, checking and even manipulating data
* monitoring communication between Akonadi server and its clients
* convenience access to the database used by the server

=== Managing Agents ===

[[Image:AkonadiConsoleTabAgents.png]]

This facility is basically a GUI for [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1AgentManager.html Akonadi::AgentManager] and [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/classAkonadi_1_1AgentInstance.html Akonadi::AgentInstance].

It enables the developer to quickly add or remove agents from the currently running Akonadi system, to check an agent's basic properties and status, etc.

While most of these actions can also be performed through end user GUI, e.g. KDE's Systemsettings, this is usually quicker and it provides more detailed information.

{{tip|The '''Synchronize''' action menu can be used to just synchronize the collection tree, basically a convenient way for a resource developer to call just the '''retrieveCollections()''' method.}}

=== Collections and Items ===

[[Image:AkonadiConsoleTabBrowser.png]]

This facility shows all Akonadi collections, how they are organized as a tree and their items and enables the developer to perform actions on these entities.

Developers working on agents can use this perform the most common tasks such as
* retrieving items: see the context menu of collection entries, basically a call to the respective resource's '''retrieveItems()''' method
* retrieve item payloads: either by clicking on an item or, for certain type such as contacts by switching the item view's mode to the respective data type.
* copy and delete items: see the context menu of item entries
* modify items: e.g. by changing the serialized form of the item on the '''Raw Payload''' tab
without having to go through an end user application.

Developers working on end user applications can use this to simulate respective changes by other clients and to check whether changes done by the application itself are correctly applied to the shared data.

{{tip|If a newly added resource's collections do not show up in the collection tree, it might be necessary to explicitly synchronize it. This functionality is available on the '''Agents''' tab.}}}

=== Monitoring Akonadi Communication ===

[[Image:AkonadiConsoleTabDebugger.png]]

This facility allows to monitor the Akonadi data protocol based communication between client sessions and the server. It contains commands, responses and the data transported between the two sides.

{{note|Since this can slow down operations it is disabled by default and has to be enabled manually when needed.}}

=== Access to the Server Database ===

Akonadi uses a SQL database for keeping relations such as which collection an item is in, properties such as MIME types, etc. as well as cached item payload data.

Since this is quite internal to the Akonadi server, it will most likely only be interesting to people working on Akonadi, not for developers working with Akonadi.

[[Image:AkonadiConsoleTabDBBrowser.png]]

The database browser can query and display the database tables used by Akonadi.

[[Image:AkonadiConsoleDBConsole.png]]

The database console enables developers to directly send commands to the database engine.

= Debugging Akonadi Agents =

Agents are automatically started by the Akonadi server and thus are not debugable from the start on by the usual methods. A similar problem is known from KIO slaves, the solution is similar as well.

== Attaching gdb at startup ==

Export the environment variable '''AKONADI_DEBUG_WAIT''' and put the agent type in there you want to debug. You only need to specify a part of the agent type, not the whole one. Example:
<code>
export AKONADI_DEBUG_WAIT=knut
</code>

When starting an agent of this type, you'll see the following debug output by the Akonadi server which is pretty much self-explanatory.

<pre>
============================================================
ProcessControl: Suspending process akonadi_knut_resouce
'gdb -pid 1234' to debug
'kill -SIGCONT 1234' to continue
============================================================
</pre>

== Running an agent in valgrind ==

Running an agent in valgrind is done in a similar way, you need to export '''AKONADI_VALGRIND''' and put the agent type in there.

To specify the valgrind tool to use by exporting '''AKONADI_VALGRIND_SKIN''', the default is memcheck.

Additional config options can be given using '''AKONADI_VALGRIND_OPTIONS'''.

Example:

valgrind akonadi_cpntacs_resource using memcheck:

<pre>
export AKONADI_VALGRIND=akonadi_contacts_resource
</pre>

To get the name of a resource, open akonadiconsole, select your resource and use the identifier being displayed at the bottom, but stip the _0 or similar from the end.

Profile the persons resource using callgrind, disabling instrumentation on start for faster startup, and dumping the callgrind output to a custom file:

<pre>
export AKONADI_VALGRIND=akonadi_contacts_resource
export AKONADI_VALGRIND_SKIN=callgrind
export AKONADI_VALGRIND_OPTIONS="--instr-atstart=no --callgrind-out-file=$HOME/callgrind-vcard.%p"
</pre>

= Akonadi Testing and Benchmark Infrastructure =

The [[Projects/PIM/Akonadi/Testing|Akonadi Test]] project provides tools to run Akonadi tests in self-contained environments, i.e. separated from the developer's personal setup, as well as running automated tests, e.g. as part of a unit test suite.

= Remote Debugging =

When running Akonadi on embedded devices or on a non-UI system, it can be useful to connect to it with clients such as akonadiconsole from a remote system. However, the Akonadi server uses local sockets for communication and therefore does not allow this directly. Same for D-Bus, which is essential for Akonadi client-server communication as well as the various debugging features in akonadiconsole.

The solution for this is the Akonadi Remote Debugging Server (Akonadi RDS), a small tunnel server that runs next to the Akonadi server. Starting it is trivial:

<code bash>
$ akonadi_rds
</code>

Now you need to tell your client how to connect to the remote instance. This is done by setting the following environment variables:

<code bash>
$ export AKONADI_SERVER_ADDRESS=tcp:host=<server ip>,port=31415
$ export DBUS_SESSION_BUS_ADDRESS=tcp:host=<server ip>,port=31416
</code>

Afterwards, just start your client as usual. Obviously, this is not limited to Akonadi but will just as well work for pure D-Bus connections with any D-Bus client, which can be quite useful by itself already.

When using akonadiconsole, this can be done even easier by the following command, without the need of setting up the environment variables:

<code bash>
$ akonadiconsole --remote <server ip>
</code>

== Limitations ==

There are currently a few limitations when using akonadi_rds (which at the same time can be seen as a TODO list ;) ):

* External payload transfer is not supported. If you use Akonadi server with an enabled FS store, payloads greater than the configured threshold will not be transferred correctly. This is fixable in libakonadi with limited effort by not requesting external transfer when using TCP transfer.
* Remote access to Nepomuk is not yet support. Effort unknown, probably requires tunneling the Nepomuk socket in the same way as we do it for Akonadi and D-Bus, as well as adjustments in the Nepomuk library to support TCP sockets.
* Remote access to the underlying database is not yet support in akonadiconsole. Should be relatively easy to do for external DB servers which likely can be forwarded in the same way as Akonadi and D-Bus, no idea about Sqlite.
* '''D-Bus remote connections only work if server and client have the same UID. That for example means to connect to a Maemo5 N900 you need to use UID 29999 on the client.''' Possible fixes involve D-Bus protocol parsing, ie. unreasonable effort.
* The raw socket console in akonadiconsole does not work yet. Easily fixable by honoring the environment variable.
* (Re-)Starting Akonadi remotely does not work.

[[Category:Akonadi]]
[[Category:PIM]]

Projects/KDE on Windows/Meetings/Berlin Meeting September 2007

2010-01-28T11:03:52Z

Bernhard: Fixed link to the dot story.

During the last weekend, the KDE on Windows developers conducted their second real life meeting in the Trolltech offices in Berlin Adlershof, incorporating new developers and improving infrastructure. [http://dot.kde.org/2007/09/18/windows-developers-meet-berlin Read the dot story for details].

Started: [[User:Jstaniek|jstaniek]] 11:40, 15 September 2007 (CEST)

== Topics ==
*mirror related
#having two or more main directories on the server: one for current stable release, one for 'unstable/testing' one
#*we need unstable releases to get people test software early and often and on Windows -> there are snapshots available
#*'unstable' is the term for base system (kdewin32, kdelibs, kdebase); note that in turn, unstable _applications_ could be installed in a stable base system as it's the case on Linux
*installer related
#development installation requires tools having own installers -> rhabacker: The installer is able to handle different installation roots, so one install root can be used for development and one for end-user. There is no need for additional installers.
#*ideally this should not be the case for end-user installation, otherwise updating would be hard (user would be forced to uninstall prev. version of an external app and install a new one in the same place...)
#define directory format of the kde mirrors --> rhabacker: there is a directory structure available on the currently used mirrors, which is usable by the installer.
#USB memory sticks/CDs: it would be possible to run kde apps/infrastructure installed on the stick/CD in two ways:
##If the user's machine already contains KDE 4 runtime installed, it could be reused to run apps from the stick, and settings placed on the host computer could be reused
##If the user's computer contains no KDE-related stuff at all, default settings and .kde directory is used
#*In either case the default user expectation is that after plugging off the stick, no settings or files remain on the machine's filesystem <-really like that???
# extend the installer with the following features:
#** integrity checks (md5 package and file checks) --> rhabacker: not started yet
#** install from cd/dvd --> rhabacker: kde can run directly from a cd or dvd by installing KDE on a harddisc or usb stick and then burning the installation directory complety to a cd/dvd
#** usb stick installation --> rhabacker: fixed

*package related
#<del>Insert compiler name into package and manifest file name (msvc, gcc) --> chehrlic: Should be fixed now</del>
* dbus related
#dbus for win32 is working mostly for recent kde applications, although there are some issues:
#*A service registered in dbus is not removed in case the related application crashes. This was detected with klauncher on msvc.
#*if dbus-daemon is killed, the related tcp port is blocked for reusage for some time and prevents that the dbus-daemon can be started again. The solution is documented in http://support.microsoft.com/?scid=kb%3Ben-us%3B177074&x=7&y=11
#*Efforts to implement win32 named pipe transport protocol were canceled because its need refactoring of the internal dbus api which was to much work yet.
#*There is a bug in dbus which prevents to list anonymous connections. This behavior can be verified with qdbusviewer.
#*There are some efforts required to merge the windows port into the dbus cvs, especialy refactoring the internal api. TODO: more details
*build system related
# KDELibsDependencies.cmake contains absolute file pathes. They have to be variabled to be evaluated on configure time using kdelibs installation. The same belongs to KDEPimLibsDependencies.cmake
saroengels: possibly fixed
* source code related
# missing or not working parts in kdelibs
#* phonon needs a win32 implementation maybe using directx with uses a COM interface
saroengels: hopefully within qt 4.4
#* kioslaves are only working partially --> chehrlic: file, http and ftp are working better now, maybe we still have some unicode problems there.
# kde application state
#* kate - '@' could not be typed in --> chehrlic: fixed for msvc (don't know why it does not work with mingw)
#* konqueror - crashes --> chehrlic: fixed some of them recently
#* dolphin - error messages with could not display root and home dir, problems to contact nepomukdaemon
#* <del>umbrello - writing and printing does not work --> rhabacker: fixed</del>
*compiler tools chain issues
# loading kde applications into gdb needs a long time to load and start when libraries are compiled with debug symbols. This makes it hard to debug.
# There are problems mixing msvc debug and release libraries resulting in runtime errors. One problem seems to be that the FILE structure differs between debug and release libraries. It has to be checked if there are workarounds for all developers.
# The update-mime-database step was taken out for make install DESTDIR builds according to pino toscano; there are two possibilities: try to convince the people to revert the changes or add a post-install script to the packages (I would append the informations into the emerge scripts myself).

=== FAQ ===
#Question: snapshot releases with debugging information - New developers may want to get the core libraries without a need for compilation from scratch, while still being able to step deeply into the its source code while debugging. This helps to enter into the project faster by fixing bugs, discovering structure of a given source code or extending features
#* Answer rhabacker: saroengels has provided mingw snapshot releases with debug informations on http://www.saroengels.net/kde-windows/. Msvc snapshots are probably not possible because the debug msvc runtime isn't distributable.
#Question: Could we have release versions with debug information? On msvc, this could help to achieve the goal mentioned in the above point while it is still possible to link release binaries with and without debug information.
#* Answer chehrlic: the official releases are now build in Release mode with debug informations
#Question: Should not the distribution of the file be reduced by keeping a snapshot of all required files on our server(s) - this would make mirroring possible
#* Answer rhabacker: mirroring is possible already now because the installer is able to fetch package online from external sites. If those external packages would not be available in the future it could be easily added to the mirrors.
#Question: is there a central list of mirrors available ?
#* Answer rhabacker: Yes a list of all available mirrors is located on the main kde on windows mirror http://www.winkde.org/pub/kde/ports/win32/mirrors.lst. This file is used by the installer to let the user choosing a mirror.
#Question: We need someone using Vista on daily basis to test kdeinstaller. Until then Vista is not supported?
#* Answer chehrlic: I got a vista license from Adriaan de Groot and after a system upgrade vista will be supported. Until now we should deny any vista support
#* Answer saroengels: we have several users on vista, probably shakes was one of them, I cannot remember though.

=== KDE on Windows can be called the first official KDE-own distribution ===

[[Category:MS Windows]]
[[Category:Meetings]]

Contribute/Get a Contributor Account

2009-12-23T14:24:52Z

Bernhard: /* Who Can Apply For a KDE SVN Account? */ Typo fixed.

{{Template:I18n/Language Navigation Bar|Contribute/Get a SVN Account}}
This tutorial is about how to apply for a SVN account for KDE.

Note: if you only need a GIT account but no SVN account, simply request that your gitorious account to be added to the kde-developers group, by filing a [https://bugs.kde.org/enter_sysadmin_request.cgi sysadmin request], using the component "gitorious".

== Notations ==

* The word ''SVN'' applies to all SVN servers.
* The phrase ''KDE SVN'' refers only to KDE's SVN server.
* The phrase ''anonymous SVN'' means KDE's anonymous SVN mirrors.

== What is KDE SVN? ==

To have write access to KDE SVN, you have to use the main SVN server of KDE. (Anonymous SVN uses mirrors of this server. SVN does not allow you to read from one server and write to another.)

To be able to use the main KDE SVN server, you need an account there. An account is made up of a ''username'' (normally your family name), a password and an email address. The username is for getting in, the password for authenticating and the email address for knowing who to contact if another developer wants to contact the account holder. (The username is sometimes known also as the ''login''.)

A KDE SVN account allows you to write to nearly anywhere in the KDE SVN. However, there are exceptions:
* the KDE SVN internals
* the admin directory
* the www module (exceptions can be made for this.)

'''Note''': you can see the accounts in [http://websvn.kde.org/trunk/kde-common/accounts kde-common/accounts]. That is the list of all accounts. Yes, '''the account list is public''', for example on [http://websvn.kde.org WebSVN].

To access the main KDE SVN, you have two possibilities, with different ways (protocols) to encrypt transmitted data:
* using HTTPS-protocol
* using SSH-protocol
If you are behind a firewall, you need to use the HTTPS-protocol, you can't use the SSH-protocol.

If you have never used ssh before, you might prefer ''HTTPS'', it's a bit simpler to set up.

However it seems that currently svn-over-ssh is really much faster than svn-over-https, so that is a good reason for using ssh.

The password you will need to create depends on the above:
* a normal password for accessing by HTTPS, or
* a SSH public key for accessing by SSH

== Who Can Apply For a KDE SVN Account? ==

Normally, any developer who has done some work on KDE can apply for a KDE SVN account.

Translators should get approval from their team leader so that they can organize how the work is being done in his/her team. Please mention the approval from the team leader when requesting the account.

Please also [[Policies/SVN Commit Policy|read the KDE SVN commit policy]]. You must accept these rules when using your future KDE SVN account. Please also familiarize yourself with the [http://www.kde.org/code-of-conduct/ KDE Code of Conduct] which describes the social foundations within KDE.

Also please apply for an account only if you think that you will work on KDE for a somewhat longer time. If you know that you will only work for a couple of weeks and then never again, please consider not applying for a KDE SVN account but still, do continue to send patches.

The limitations are not there to exclude anyone - they are there to ensure that the maintenance of accounts remains reasonable.

Of course, to be clear: ''the [mailto:sysadmin@kde.org KDE's sysadmins] have the last word about whether or not to create a KDE SVN account for somebody''.

== Access via HTTPS ==

=== Choosing a Password ===

First of all, you have to choose a password. If possible, one that you do not use for anything else on your computer (as the SVN account has nothing to do with any other account on your computer.)

In any case, please use ''common precautions'' about passwords.

Strong passwords:
* have both upper and lower case letters.
* have digits and/or punctuation characters as well as letters.
* are easy to remember, so they do not have to be written down.
* are at least eight characters long.

A strong password is '''not''':

* Personal information such as your name, phone number, social security number, birth date or address. Even names of acquaintances and the like should not be used.
* Any word in the dictionary, or based closely on such a word (such as a word spelled backwards).
* A word with letters simply replaced by digits. For example, bl0wf1sh is not a strong password.
* Easy to spot while you're typing them in. Passwords like 12345, qwerty (i.e., all keys right next to each other), or nnnnnn should be avoided.

All the rules are not here to annoy you but to guarantee a certain level of security for the KDE SVN server.

=== Getting the Encoded Password ===

Now that you have your password, you need to encode it, not to have to send it in clear. (Note: this encryption is the same type of encryption used by many Linux distributions for their {{path|/etc/shadow}} file.)

If your password is 8 characters long, one way to do this would be using Perl: 
<nowiki>perl -e 'print crypt("<your password>","\$1\$xyz\$")."\n";'</nowiki>
where <your password> has to be replaced with your password and ''xyz'' with 3 to 8 random characters of your choice. Leave the \$1\$ before it and the \$ after it.

(Hint: $ must be "escaped" with a backslash. For instance: If your password is "abc$123" you have to replace <your password> with "abc\$123". )

'''Note''': do not worry to find your choice of <xyz> at the start of the encoded password, it is meant to be so.

Another solution is to create a dummy account on a Unix system where you have administrator access. You can use the built-in user management programs of your distribution and search for the account in your file {{path|/etc/shadow}} or you can use the following code:
useradd dummy; passwd dummy; grep dummy /etc/passwd /etc/shadow; userdel dummy

In any case, the password is then the part between the first ':' and the second ':'. (Note: not a star! (*) That means that it is not the password!)

'''Note''': This might not work anymore with newer systems because they encrypt the password with a hash algorithm that is not (yet) supported by the kde server. To be save, use the perl script

Save the encoded password so that you can use it later in the application.

== Access via SSH ==

You need a SSH public key in order to access your KDE SVN account with SSH. If you already have one, you can skip the next subsection and go to [[#Setting up the SVN+SSH protocol|Setting up the SVN+SSH protocol]].

=== Generating the SSH keys ===

To be able to use your KDE SVN account with SSH, you need a SSH public key. Please notice that it is '''not''' a GPG (OpenPGP) key, which is completely unrelated!

The password in the sense of this documentation is the '''public key''' that you are creating.

For more information on how to create a pair o SSH keys, please refer to a [http://www.openbsd.org/cgi-bin/man.cgi?query=ssh-keygen SSH documentation] or book.

In short, the command to create a pair of keys is '''ssh-keygen''' and it requires the type of key you will create, either DSA or RSA - both are fine.

To create a new pair of keys, use <code bash>ssh-keygen -t dsa</code> or <code bash>ssh-keygen -t rsa</code>

There is also a type called RSA1 which was used in version 1 of the SSH protocol. See the [http://www.openbsd.org/cgi-bin/man.cgi?query=ssh-keygen ssh documentation] for more details.

You can then accept the default filename for your key (either {{path|$HOME/.ssh/id_dsa}} or {{path|$HOME/.ssh/id_rsa}}, depending on the type of key you have chosen). After that, a passphrase is asked. It is recommended that you do not leave it blank.

Now that you are finished generating your key pair, you will have two files: a private key and a public key. If you have accepted the default filename, they will be respectively {{path|$HOME/.ssh/id_dsa}} and {{path|$HOME/.ssh/id_dsa.pub}} or {{path|$HOME/.ssh/id_rsa}} and {{path|$HOME/.ssh/id_rsa.pub}}, depending on the type of key you have specified.

The private key '''must''' remain secret, do not publish it to anyone under any circumstance.

The public key can be published and shall be sent when you are applying for a KDE SVN account.

You should also set up <tt>ssh-agent</tt> so you do not have to type the password every time you connect via SSH. There are several tutorials available explaining how to do this, for example [http://mah.everybody.org/docs/ssh this one]. [http://www.gentoo.org/proj/en/keychain Keychain] is a program that makes this task easier.

'''Note''': if you already have an ssh key, you can just use the existing key instead of creating a new one.

{{tip|
If you want to use SVN with SSH with another user than the one who created the keys, you need to copy <tt>$HOME/.ssh/id_dsa.pub</tt> and <tt>$HOME/.ssh/id_dsa</tt> or <tt>$HOME/.ssh/id_rsa.pub</tt> and <tt>$HOME/.ssh/id_rsa</tt> to the other user's <tt>$HOME/.ssh</tt> directory.

You should probably also backup those files.
}}

=== Setting up the SVN+SSH protocol ===

Once you created your key, you'll have to tell SSH that this one should be used for all connections to KDE sites. Add the following lines to the <tt>~/.ssh/config</tt> file. Replace USERNAME with yours.

<pre>
Host *.kde.org
User USERNAME
IdentityFile ~/.ssh/id_dsa
</pre>

The linked IdentityFile must belong to the public key you send in when applying for the SVN account. But it is ''not'' the public key (<tt>*.pub</tt>).

== Apply for an account ==

Now you are ready to apply for for a KDE SVN account. Go to [https://sysadmin.kde.org/svnaccount/ https://sysadmin.kde.org/svnaccount/] and fill out the form.

You will need to enter your name and an e-mail address, which has to be your own (a normal address or a KDE Mail address). Of course, do not forget that '''this email address becomes public''' (at least by [http://websvn.kde.org WebSVN]) so you will unfortunately get spam.

Also note that this email address should be the same one that you use on [http://bugs.kde.org bugs.kde.org]. If you don't have an account in [http://bugs.kde.org bugs.kde.org], please create one so that it can be given usual developer rights. Closing bug reports with keywords in commit comments only works if the email address of your Subversion and [http://bugs.kde.org bugs.kde.org] accounts match.

After that, you must choose a username for your KDE SVN account between the suggestions presented to you. Please notice it is not possible to propose something else such as a nickname, as the username must be as close as possible to someone's real name.

If you ask for a KDE email address one day, this will be the base for your address. For example: <tt>username@kde.org</tt>. (Note, however, that KDE email addresses are not granted so easily anymore, as too many people have ranted with a KDE address and other people thought that it was the official position of the KDE Team. In the meantime, [http://www.kdemail.net KDE Mail] was created for if you need a permanent address.)

Then you have to specify the password that you will use. If you will prefer SSH access, provide your public key; if you want HTTPS access, enter your encrypted password.

The form also holds a field ''Why do you want an account?'', where you can explain what you want to do with your future KDE SVN account, like for example developing a certain application, making documentations or being the team leader of a translation.

After filling out the form, you will receive an email with a link to click on. This is done to verify your email address. The application is not complete before you click on it.

Also note that the form will ask you who has encouraged you to apply. He or she will also get an email to verify your request.

== Updating Existing Account ==

If you already have a KDE SVN account but want to update the ssh key or https password, [https://bugs.kde.org/enter_sysadmin_request.cgi send a request] to the sysadmins, selecting the "svn account" component and attaching your ssh key or mentioning your new password.

== And Now? ==

After having sent the form and clicking the link in the email, you have to wait for the answer (typically within two or three days).

Once you have confirmation that your account has been created, you need to adapt your local copy to the new server. See the [[Contribute/First Steps with your KDE SVN Account|next tutorial]] for your first steps with your new account.

Please add your geographical location (what country are you in?) and other details at the [http://commit-digest.org/data/ Commit Digest data page] so that the Commit Digest can accurately reflect who is working where.

Projects/Mobile

2009-10-26T20:29:58Z

Bernhard: Removed the wikipedia hint as there are not articles for all mentioned keywords. (e.g. diablo or garage), added the new kde-maemo@ mailinglist.

== Overview ==
* ''garage'' is where the projects for maemo are hosted. Compare it with sourceforge.
* ''diablo'' is the version of maemo. Compare it with lenny.
* [http://maemo.org/intro/platform/ '''maemo'''] is the core software stack that runs on mobile devices like Nokia's N810 or N900
* ''scratchbox'' is a cross-compiling environment to enable you to create software for maemo on an i386.
* ''busybox'' is a single binary that allows you to run commands like ls, cat and bunzip2
* ''hildon'' is a desktop like plasma

There is a [https://mail.kde.org/mailman/listinfo/kde-maemo kde-maemo mailinglist].

== KDE on Maemo ==

This page is for collecting information about getting KDE running on the Maemo platform used by the Nokia mobile devices N800, N810 and N900.

* Instructions on getting a Maemo development environment on openSuSE http://en.opensuse.org/Maemo
* There is also a KDE on maemo project at http://kde.garage.maemo.org/
* [http://www.forwardbias.in/data/articles/qt_on_maemo.txt Tutorial how to get Qt installed on maemo]
* [[Projects/Maemo/kdepim|Tutorial how to compile KDEPIM on maemo]]
* [[Projects/Maemo/KDE4_on_n810|Tutorial how to get KDE installed on Maemo]]
* [[Projects/Maemo/KDE4_on_Mer|Tutorial how to get KDE installed on Mer]]

=== Some blogs entries about KDE on Maemo ===

''Most recent on top''

* [http://www.kdedevelopers.org/node/3672 Marijn Kruisselbrink: Having fun with qemu]
* [http://www.kdedevelopers.org/node/3662 Marijn Kruisselbrink: KOffice on Maemo]
* [http://blog.forwardbias.in/2008/08/n810-is-awesome.html Girish Ramakrishnan: N810 is awesome]
* [http://www.kdedevelopers.org/node/3628 Fredrik Gladhorn: Various Qt apps]
* [http://www.kdedevelopers.org/node/3624 Marijn Kruisselbrink: KDE packages for maemo]
* [http://www.notmart.org/index.php/Software/Misc_plasmoids_on_n810 Marco Martin: Misc plasmoids on n810]
* [http://www.notmart.org/index.php/BlaBla/Akademy,_810_and_stuffs Marco Martin: Akademy, 810 and stuffs]
* [http://www.kdedevelopers.org/node/3623 Richard Dale: Building Ruby on the N810]
* [http://www.fredemmott.co.uk/blog_156 Fred Emmott: Ogg/Vorbis on N810]
* [http://www.omat.nl/drupal/content/N810-and-OpenStreetMap-and-toma Tom Albers: N810 and OpenStreetMap and toma]
* [http://tsdgeos.blogspot.com/2008/08/maemo-scratchbox-on-amd64.html Albert Astals Cid: Maemo scratchbox on amd64]
* [http://blogs.forum.nokia.com/blog/kate-alholas-forum-nokia-blog/maemo/2008/08/13/akademy-2008-embedded-day Kate Alhola: Akademy 2008 Embedded day]
* [http://www.gnuton.org/blog/2008/07/qt-4-maemo-the-new-experience/ Antonio Aloisio: Qt 4 Maemo: the new experience.]
* [http://www.kdedevelopers.org/node/3605 Marijn Kruisselbrink: Getting KDE on an n810.]
* [http://www.kdedevelopers.org/node/3575 Marijn Kruisselbrink: Sound on Maemo]
* [http://www.kdedevelopers.org/node/3546 Marijn Kruisselbrink: Plasma on Maemo]

Projects/Mobile

2009-10-26T20:26:11Z

Bernhard: Added the N900. Clarified the explanation of Maemo a bit and linked maemo.org

== Overview ==
* ''garage'' is where the projects for maemo are hosted. Compare it with sourceforge.
* ''diablo'' is the version of maemo. Compare it with lenny.
* [http://maemo.org/intro/platform/ '''maemo'''] is the core software stack that runs on mobile devices like Nokia's N810 or N900
* ''scratchbox'' is a cross-compiling environment to enable you to create software for maemo on an i386.
* ''busybox'' is a single binary that allows you to run commands like ls, cat and bunzip2
* ''hildon'' is a desktop like plasma

For more information see wikipedia.

== KDE on Maemo ==

This page is for collecting information about getting KDE running on the Maemo platform used by the Nokia mobile devices N800, N810 and N900.

* Instructions on getting a Maemo development environment on openSuSE http://en.opensuse.org/Maemo
* There is also a KDE on maemo project at http://kde.garage.maemo.org/
* [http://www.forwardbias.in/data/articles/qt_on_maemo.txt Tutorial how to get Qt installed on maemo]
* [[Projects/Maemo/kdepim|Tutorial how to compile KDEPIM on maemo]]
* [[Projects/Maemo/KDE4_on_n810|Tutorial how to get KDE installed on Maemo]]
* [[Projects/Maemo/KDE4_on_Mer|Tutorial how to get KDE installed on Mer]]

=== Some blogs entries about KDE on Maemo ===

''Most recent on top''

* [http://www.kdedevelopers.org/node/3672 Marijn Kruisselbrink: Having fun with qemu]
* [http://www.kdedevelopers.org/node/3662 Marijn Kruisselbrink: KOffice on Maemo]
* [http://blog.forwardbias.in/2008/08/n810-is-awesome.html Girish Ramakrishnan: N810 is awesome]
* [http://www.kdedevelopers.org/node/3628 Fredrik Gladhorn: Various Qt apps]
* [http://www.kdedevelopers.org/node/3624 Marijn Kruisselbrink: KDE packages for maemo]
* [http://www.notmart.org/index.php/Software/Misc_plasmoids_on_n810 Marco Martin: Misc plasmoids on n810]
* [http://www.notmart.org/index.php/BlaBla/Akademy,_810_and_stuffs Marco Martin: Akademy, 810 and stuffs]
* [http://www.kdedevelopers.org/node/3623 Richard Dale: Building Ruby on the N810]
* [http://www.fredemmott.co.uk/blog_156 Fred Emmott: Ogg/Vorbis on N810]
* [http://www.omat.nl/drupal/content/N810-and-OpenStreetMap-and-toma Tom Albers: N810 and OpenStreetMap and toma]
* [http://tsdgeos.blogspot.com/2008/08/maemo-scratchbox-on-amd64.html Albert Astals Cid: Maemo scratchbox on amd64]
* [http://blogs.forum.nokia.com/blog/kate-alholas-forum-nokia-blog/maemo/2008/08/13/akademy-2008-embedded-day Kate Alhola: Akademy 2008 Embedded day]
* [http://www.gnuton.org/blog/2008/07/qt-4-maemo-the-new-experience/ Antonio Aloisio: Qt 4 Maemo: the new experience.]
* [http://www.kdedevelopers.org/node/3605 Marijn Kruisselbrink: Getting KDE on an n810.]
* [http://www.kdedevelopers.org/node/3575 Marijn Kruisselbrink: Sound on Maemo]
* [http://www.kdedevelopers.org/node/3546 Marijn Kruisselbrink: Plasma on Maemo]

Development/Tutorials/Debugging/Debugging on MS Windows

2009-07-09T20:51:11Z

Bernhard: /* MinGW debugging hints */ Added the hint that continue is needed after and attach.

=General Hints=
==Debugging with WinDbg==
WinDbg, distributed as a part of ''Debugging Tools for Windows'', is a user-mode and kernel-mode debugger with a graphical interface. It can also be used to debug user-mode crash dumps. It uses the Microsoft Visual Studio debug symbol formats for source-level debugging. [[Projects/KDE_on_Windows/Tools#WinDbg|more...]]

==Debugging with DebugView==
Debug messages (logs) generated by kDebug() and kWarning() are not visible on MS Windows unless application is compiled in so-called CONSOLE subsystem. To show these messages also in WINDOWS subsystem, you can use DebugView tool, coming from SysInternals (currently acquired by Microsoft). [[Projects/KDE_on_Windows/Tools#DebugView|more...]]

==Debugging kioslaves==
kioslaves on windows are started by klauncher (or kio) as separate kioslave processes. The kioslave executable then loads the related kioslave dll dynamically.

=== Using KDE_SLAVE_DEBUG_WAIT variable ===
To debug kioslaves:
#Set the KDE_SLAVE_DEBUG_WAIT environment variable in a current cmd.exe shell to the name of the kioslave's protocol (the first parameter of KIO::SlaveBase() constructor), e.g.<pre>set KDE_SLAVE_DEBUG_WAIT=file</pre>
#Terminate <tt>klauncher</tt> process so it can be restarted.
#Any application you want to debug at kioslave level have to be executed within the scope of the current environment (cmd.exe), what also means that if you want to use development environment, you have to do that in the environment as well, e.g. for MSVC Express, by typing <tt>vcexpress</tt>.

If the kioslave is requested the next time, a debugger will be started and attached to the kioslave process immediatly before the kioslave's kdemain() function.

On mingw platform gdb is launched and connected to the kioslave process. On msvc platforms the currently installed just-in-time debugger is used. This may be msvc's IDE or the [[Projects/KDE_on_Windows/Tools#WinDbg|WinDbg debugger]]. The latter could be set as jit-debugger by running 'windbg -I' command (capital -I like ICE, see [http://msdn2.microsoft.com/en-us/library/cc266343.aspx]).

=== Using KDE_SLAVE_DEBUG_POPUP variable ===
Alternatively, you can set <tt>KDE_SLAVE_DEBUG_POPUP</tt> variable instead of <tt>KDE_SLAVE_DEBUG_WAIT</tt>. This will display a native message box so developer you can attach the debugger to the KIO slave process and click OK. No DebugBreak() is invoked. Just click OK without attaching to continue using the KIO slave without debugging.

=== Notes ===
*You can set, say, the variable to 'file' for the kio_file slave, '''but''' set it to 'smtps' for the kio_smtp is you want to debug smtp protocol secured with SSL.
*(Vista only): ''kioslave.exe has stopped working'' message dialog can appear instead of offer for starting the debugger. Reason: Just-In-Time (JIT) Debugging of an elevated process will fail ([http://msdn2.microsoft.com/en-us/vstudio/aa964140.aspx#question20a msdn link]) apparently for security reasons. Either:
**Use <tt>KDE_SLAVE_DEBUG_POPUP</tt> instead of <tt>KDE_SLAVE_DEBUG_WAIT</tt>. See the [[#Using_KDE_SLAVE_DEBUG_POPUP_variable|Using KDE_SLAVE_DEBUG_POPUP variable]] above for more info.
**(not possible under msvc 2005): start applications and klauncher without administration permissions or attach the debugger manually before the debugger catches unhandled exceptions or an user-defined breakpoint (DebugBreak()).
*You may want to inspect kioslave sources [http://lxr.kde.org/source/KDE/kdelibs/kinit/kioslave.cpp] for more informations.

== Checking dependency of shared libraries ==
Dependency Walker is a free utility that scans any 32-bit or 64-bit Windows module (exe, dll, ocx, sys, etc.) and builds a hierarchical tree diagram of all dependent modules. [[Projects/KDE_on_Windows/Tools#Dependency_Walker|more...]]

= MS Visual Studio hints =

== Using MS Visual Studio environment for just debugging ==

Let's assume you're using command line tools (typically CMake) and want to use MS Visual Studio environment for just debugging. You don't need to create msvc project for your KDE application to be able to start debugging.

* compile and working executable version of your appliation (compiled in debug mode)
* run msvc environment
* execute ''File->Open project''
* pick your exe file in the file window
* you can set command line arguments as usual, by pick ''Project->...Properties'' command and enter all of them it in ''Command Arguments'' field
* if you have libraries placed in other directories than your application's .exe file, and you want to step into these libraries' source code while debugging, pick ''Project->...Properties'' command and enter paths to these directories in ''Symbol Path'' field
* hit F5 to run the application start the application or F10 to start step by step
* all debugging functions like setting breakpoints will be available, so you can open source code in the integrated editor and press F9 where needed
* you can even edit your source code but to compile it, do it with your external, command line tools. You cannot compile the application in the msvc environment because you have not defined a project file
* before compiling your application, stop debugging session to unlock binaries; no need to close msvc window
* after compilation you can start debugging again
* on exit you will be asked to save .sln file (so-called ''solution file'') with your debugging session -- do it and you will be able just to click the .sln file to start your debugging again
* it's recommended to save the .sln file in the .exe file directory
* next time you will run msvc environment, you can see name of your application's .sln file in ''File->Recent Projects'' submenu - you can click it to load your debugging session

== Attaching to running application ==

If you have your application is already running, you can attach to it and then start debugging.

* run msvc environment
* execute ''Debug->processes''
* select your from the processes list and click "Attach..."
* msvc environment will load your .sln file if it exists in the same directory as the .exe file, so your breakpoints set in previous session will be active again
* your program will stop on any breakpoint you have set

== One-step attaching to running application ==
You can create a macro that automates the task. See [http://blogs.msdn.com/jimgries/archive/2005/11/30/498264.aspx].

== Memory Values ==
If you are using the debug heap, memory is initialized and cleared with special values. Most interesting values are:
* 0xCDCDCDCD - Allocated in heap, but not initialized
* 0xDDDDDDDD - Released heap memory.
* 0xFDFDFDFD - "NoMansLand" fences automatically placed at boundary of heap memory. Should never be overwritten. If you do overwrite one, you're probably walking off the end of an array.
* 0xCCCCCCCC - Allocated on stack, but not initialized
See also: [http://www.samblackburn.com/wfc/technotes/WTN006.htm]

==How to Not Step Into Functions in the Debugger==
You'll probably want to avoind stepping into lower-level functions like QString constructors or operators while debugging step-by-step. Here's the detailed (unofficial) [http://blogs.msdn.com/andypennell/archive/2004/02/06/69004.aspx instruction] for various msvc versions.

==Enable automatic expanding of Qt data structures==
From the msvc docs: "While debugging, Data Tips and items in the Watch and Variable windows are automatically expanded to show their most important elements. The expansion follows the format given by the rules in this file. You can add rules for your types or change the predefined rules." ([http://www.thedatafarm.com/blog/content/binary/datatips2.jpg example screen])

MSVC 2005: To add support for expanding Qt data structures like QString of QRect, edit {msvc_installation_directory}\Common7\Packages\Debugger\autoexp.dat file and paste [[/Automatic expanding of Qt data structures|definitions]] after [AutoExpand] line.
==WINDOWS and CONSOLE subsystems==
CONSOLE subsystem is the one that displays console window (used for standard output and error streams) in addition to application's windows. WINDOWS subsystem redirects standard output and error streams to system debugging subsystem that can be displayed if needed in [[Projects/KDE_on_Windows/Tools#DebugView|DebugView]] or debuggers like msvc or [[Projects/KDE_on_Windows/Tools#WinDbg|WinDbg]].
Hint: To remove CONSOLE subsystem from already built .exe file, type <code>editbin /subsystem:windows file.exe</code>
Note: Qt's qmake syntax supports ''console'' and ''windows'' parameters of the ''CONFIG'' variable, so CONSOLE subsystem can be enabled by specifying <tt>CONFIG += console</tt> in the .pro file, windows subsystem can be enabled with <tt>CONFIG += windows</tt>.

==Deployment==
Running a VC++2005 SP1 app on another computer: manifest files are needed. See [http://www.codeproject.com/KB/cpp/vcredists_x86.aspx] and [http://blogs.msdn.com/nikolad/archive/2005/09/02/460368.aspx].

===Note on debug builds===
The hints above are for release builds (or ReleaseWithDebugInfo). Moving Debug versions of binaries to other computers is only allowed (and technicallu possible) if you have Express Edition installed there, as there is no redistributable package for Debug versions provided and even the license disallows distribution of any debug binaries (even your own).

= MinGW debugging hints =

There are gdb binaries you can directly run after unpacking them, e.g. from
[http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=20507 mingw's gdb downloads on sourceforge].

To get a backtrace for a crash you can reproduce: Start the gdb binary with the full path to the executable on the command line, for example like
<code>..\gdb\gdb.exe c:\programme\kontact\bin\kontact.exe</code>. When getting
the command prompt use the run command with the arguments for your application, e.g <code>run --nofork</code>. Now wait until your applications starts and go on reproducing the crash. Once you encounter the crash, gdb will be in control
in the command line again. <code>bt</code> will get you the backtrace.

Instead of running gdb from the beginning, you can also attach to a running process. Use the regular "task-manager" to see which process. Enable the process id columns so you can see the number. Now you can start gdb (still give it the path to the application executable if you can) and use the <code>attach</code> command with the process id you want to attach to from the
gdb prompt. Gdb will stop the process it attached to, so you can say <code>continue</code> and then try to produce the crash.

* Dr. Mingw - Just in Time Debugger [http://jrfonseca.planetaclix.pt/projects/gnu-win32/software/drmingw/]
* Debugging Qt programs on Windows [http://lists.trolltech.com/qt-interest/2005-08/thread01124-0.html]

'''''WARNING''''': If you are having crashes when starting applications via gdb beware of certain applications (mostly anti-virus software) that could cause problems like "Embassy Trust Suite", for example. See this [http://www.cygwin.com/ml/cygwin/2007-06/msg00405.html post].

[[Category:MS Windows]]

Development/Tutorials/Debugging/Debugging on MS Windows

2009-01-19T14:40:55Z

Bernhard: /* MinGW debugging hints */ how to create backtrace with gdb

=General Hints=
==Debugging with WinDbg==
WinDbg, distributed as a part of ''Debugging Tools for Windows'', is a user-mode and kernel-mode debugger with a graphical interface. It can also be used to debug user-mode crash dumps. It uses the Microsoft Visual Studio debug symbol formats for source-level debugging. [[Projects/KDE_on_Windows/Tools#WinDbg|more...]]

==Debugging with DebugView==
Debug messages (logs) generated by kDebug() and kWarning() are not visible on MS Windows unless application is compiled in so-called CONSOLE subsystem. To show these messages also in WINDOWS subsystem, you can use DebugView tool, coming from SysInternals (currently acquired by Microsoft). [[Projects/KDE_on_Windows/Tools#DebugView|more...]]

==Debugging kioslaves==
kioslaves on windows are started by klauncher (or kio) as separate kioslave processes. The kioslave executable then loads the related kioslave dll dynamically.

=== Using KDE_SLAVE_DEBUG_WAIT variable ===
To debug kioslaves:
#Set the KDE_SLAVE_DEBUG_WAIT environment variable in a current cmd.exe shell to the name of the kioslave's protocol (the first parameter of KIO::SlaveBase() constructor), e.g.<pre>set KDE_SLAVE_DEBUG_WAIT=file</pre>
#Terminate <tt>klauncher</tt> process so it can be restarted.
#Any application you want to debug at kioslave level have to be executed within the scope of the current environment (cmd.exe), what also means that if you want to use development environment, you have to do that in the environment as well, e.g. for MSVC Express, by typing <tt>vcepress</tt>.

If the kioslave is requested the next time, a debugger will be started and attached to the kioslave process immediatly before the kioslave's kdemain() function.

On mingw platform gdb is launched and connected to the kioslave process. On msvc platforms the currently installed just-in-time debugger is used. This may be msvc's IDE or the [[Projects/KDE_on_Windows/Tools#WinDbg|WinDbg debugger]]. The latter could be set as jit-debugger by running 'windbg -I' command (capital -I like ICE, see [http://msdn2.microsoft.com/en-us/library/cc266343.aspx]).

=== Using KDE_SLAVE_DEBUG_POPUP variable ===
Alternatively, you can set <tt>KDE_SLAVE_DEBUG_POPUP</tt> variable instead of <tt>KDE_SLAVE_DEBUG_WAIT</tt>. This will display a native message box so developer you can attach the debugger to the KIO slave process and click OK. No DebugBreak() is invoked. Just click OK without attaching to continue using the KIO slave without debugging.

=== Notes ===
*You can set, say, the variable to 'file' for the kio_file slave, '''but''' set it to 'smtps' for the kio_smtp is you want to debug smtp protocol secured with SSL.
*(Vista only): ''kioslave.exe has stopped working'' message dialog can appear instead of offer for starting the debugger. Reason: Just-In-Time (JIT) Debugging of an elevated process will fail ([http://msdn2.microsoft.com/en-us/vstudio/aa964140.aspx#question20a msdn link]) apparently for security reasons. Either:
**Use <tt>KDE_SLAVE_DEBUG_POPUP</tt> instead of <tt>KDE_SLAVE_DEBUG_WAIT</tt>. See the [[#Using_KDE_SLAVE_DEBUG_POPUP_variable|Using KDE_SLAVE_DEBUG_POPUP variable]] above for more info.
**(not possible under msvc 2005): start applications and klauncher without administration permissions or attach the debugger manually before the debugger catches unhandled exceptions or an user-defined breakpoint (DebugBreak()).
*You may want to inspect kioslave sources [http://lxr.kde.org/source/KDE/kdelibs/kinit/kioslave.cpp] for more informations.

== Checking dependency of shared libraries ==
Dependency Walker is a free utility that scans any 32-bit or 64-bit Windows module (exe, dll, ocx, sys, etc.) and builds a hierarchical tree diagram of all dependent modules. [[Projects/KDE_on_Windows/Tools#Dependency_Walker|more...]]

= MS Visual Studio hints =

== Using MS Visual Studio environment for just debugging ==

Let's assume you're using command line tools (typically CMake) and want to use MS Visual Studio environment for just debugging. You don't need to create msvc project for your KDE application to be able to start debugging.

* compile and working executable version of your appliation (compiled in debug mode)
* run msvc environment
* execute ''File->Open project''
* pick your exe file in the file window
* you can set command line arguments as usual, by pick ''Project->...Properties'' command and enter all of them it in ''Command Arguments'' field
* if you have libraries placed in other directories than your application's .exe file, and you want to step into these libraries' source code while debugging, pick ''Project->...Properties'' command and enter paths to these directories in ''Symbol Path'' field
* hit F5 to run the application start the application or F10 to start step by step
* all debugging functions like setting breakpoints will be available, so you can open source code in the integrated editor and press F9 where needed
* you can even edit your source code but to compile it, do it with your external, command line tools. You cannot compile the application in the msvc environment because you have not defined a project file
* before compiling your application, stop debugging session to unlock binaries; no need to close msvc window
* after compilation you can start debugging again
* on exit you will be asked to save .sln file (so-called ''solution file'') with your debugging session -- do it and you will be able just to click the .sln file to start your debugging again
* it's recommended to save the .sln file in the .exe file directory
* next time you will run msvc environment, you can see name of your application's .sln file in ''File->Recent Projects'' submenu - you can click it to load your debugging session

== Attaching to running application ==

If you have your application is already running, you can attach to it and then start debugging.

* run msvc environment
* execute ''Debug->processes''
* select your from the processes list and click "Attach..."
* msvc environment will load your .sln file if it exists in the same directory as the .exe file, so your breakpoints set in previous session will be active again
* your program will stop on any breakpoint you have set

== One-step attaching to running application ==
You can create a macro that automates the task. See [http://blogs.msdn.com/jimgries/archive/2005/11/30/498264.aspx].

== Memory Values ==
If you are using the debug heap, memory is initialized and cleared with special values. Most interesting values are:
* 0xCDCDCDCD - Allocated in heap, but not initialized
* 0xDDDDDDDD - Released heap memory.
* 0xFDFDFDFD - "NoMansLand" fences automatically placed at boundary of heap memory. Should never be overwritten. If you do overwrite one, you're probably walking off the end of an array.
* 0xCCCCCCCC - Allocated on stack, but not initialized
See also: [http://www.samblackburn.com/wfc/technotes/WTN006.htm]

==How to Not Step Into Functions in the Debugger==
You'll probably want to avoind stepping into lower-level functions like QString constructors or operators while debugging step-by-step. Here's the detailed (unofficial) [http://blogs.msdn.com/andypennell/archive/2004/02/06/69004.aspx instruction] for various msvc versions.

==Enable automatic expanding of Qt data structures==
From the msvc docs: "While debugging, Data Tips and items in the Watch and Variable windows are automatically expanded to show their most important elements. The expansion follows the format given by the rules in this file. You can add rules for your types or change the predefined rules." ([http://www.thedatafarm.com/blog/content/binary/datatips2.jpg example screen])

MSVC 2005: To add support for expanding Qt data structures like QString of QRect, edit {msvc_installation_directory}\Common7\Packages\Debugger\autoexp.dat file and paste [[/Automatic expanding of Qt data structures|definitions]] after [AutoExpand] line.
==WINDOWS and CONSOLE subsystems==
CONSOLE subsystem is the one that displays console window (used for standard output and error streams) in addition to application's windows. WINDOWS subsystem redirects standard output and error streams to system debugging subsystem that can be displayed if needed in [[Projects/KDE_on_Windows/Tools#DebugView|DebugView]] or debuggers like msvc or [[Projects/KDE_on_Windows/Tools#WinDbg|WinDbg]].
Hint: To remove CONSOLE subsystem from already built .exe file, type <code>editbin /subsystem:windows file.exe</code>
Note: Qt's qmake syntax supports ''console'' and ''windows'' parameters of the ''CONFIG'' variable, so CONSOLE subsystem can be enabled by specifying <tt>CONFIG += console</tt> in the .pro file, windows subsystem can be enabled with <tt>CONFIG += windows</tt>.

==Deployment==
Running a VC++2005 SP1 app on another computer: manifest files are needed. See [http://www.codeproject.com/KB/cpp/vcredists_x86.aspx] and [http://blogs.msdn.com/nikolad/archive/2005/09/02/460368.aspx].

===Note on debug builds===
The hints above are for release builds (or ReleaseWithDebugInfo). Moving Debug versions of binaries to other computers is only allowed (and technicallu possible) if you have Express Edition installed there, as there is no redistributable package for Debug versions provided and even the license disallows distribution of any debug binaries (even your own).

= MinGW debugging hints =

There are gdb binaries you can directly run after unpacking them, e.g. from
[http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=20507 mingw's gdb downloads on sourceforge].

To get a backtrace for a crash you can reproduce: Start the gdb binary with the full path to the executable on the command line, for example like
<code>..\gdb\gdb.exe c:\programme\kontact\bin\kontact.exe</code>. When getting
the command prompt use the run command with the arguments for your application, e.g <code>run --nofork</code>. Now wait until your applications starts and go on reproducing the crash. Once you encounter the crash, gdb will be in control
in the command line again. <code>bt</code> will get you the backtrace.

Instead of running gdb from the beginning, you can also attach to a running process. Use the regular "task-manager" to see which process. Enable the process id so you have the number. Now you can start gdb and use the <code>attach</code> command with the process id you want to attach to.

* Dr. Mingw - Just in Time Debugger [http://jrfonseca.planetaclix.pt/projects/gnu-win32/software/drmingw/]
* Debugging Qt programs on Windows [http://lists.trolltech.com/qt-interest/2005-08/thread01124-0.html]

'''''WARNING''''': If you are having crashes when starting applications via gdb beware of certain applications (mostly anti-virus software) that could cause problems like "Embassy Trust Suite", for example. See this [http://www.cygwin.com/ml/cygwin/2007-06/msg00405.html post].

[[Category:MS Windows]]

Development/Tutorials/Debugging/Debugging on MS Windows

2009-01-19T14:32:47Z

Bernhard: /* MinGW debugging hints */ adding link to gdb downloads as mingw

=General Hints=
==Debugging with WinDbg==
WinDbg, distributed as a part of ''Debugging Tools for Windows'', is a user-mode and kernel-mode debugger with a graphical interface. It can also be used to debug user-mode crash dumps. It uses the Microsoft Visual Studio debug symbol formats for source-level debugging. [[Projects/KDE_on_Windows/Tools#WinDbg|more...]]

==Debugging with DebugView==
Debug messages (logs) generated by kDebug() and kWarning() are not visible on MS Windows unless application is compiled in so-called CONSOLE subsystem. To show these messages also in WINDOWS subsystem, you can use DebugView tool, coming from SysInternals (currently acquired by Microsoft). [[Projects/KDE_on_Windows/Tools#DebugView|more...]]

==Debugging kioslaves==
kioslaves on windows are started by klauncher (or kio) as separate kioslave processes. The kioslave executable then loads the related kioslave dll dynamically.

=== Using KDE_SLAVE_DEBUG_WAIT variable ===
To debug kioslaves:
#Set the KDE_SLAVE_DEBUG_WAIT environment variable in a current cmd.exe shell to the name of the kioslave's protocol (the first parameter of KIO::SlaveBase() constructor), e.g.<pre>set KDE_SLAVE_DEBUG_WAIT=file</pre>
#Terminate <tt>klauncher</tt> process so it can be restarted.
#Any application you want to debug at kioslave level have to be executed within the scope of the current environment (cmd.exe), what also means that if you want to use development environment, you have to do that in the environment as well, e.g. for MSVC Express, by typing <tt>vcepress</tt>.

If the kioslave is requested the next time, a debugger will be started and attached to the kioslave process immediatly before the kioslave's kdemain() function.

On mingw platform gdb is launched and connected to the kioslave process. On msvc platforms the currently installed just-in-time debugger is used. This may be msvc's IDE or the [[Projects/KDE_on_Windows/Tools#WinDbg|WinDbg debugger]]. The latter could be set as jit-debugger by running 'windbg -I' command (capital -I like ICE, see [http://msdn2.microsoft.com/en-us/library/cc266343.aspx]).

=== Using KDE_SLAVE_DEBUG_POPUP variable ===
Alternatively, you can set <tt>KDE_SLAVE_DEBUG_POPUP</tt> variable instead of <tt>KDE_SLAVE_DEBUG_WAIT</tt>. This will display a native message box so developer you can attach the debugger to the KIO slave process and click OK. No DebugBreak() is invoked. Just click OK without attaching to continue using the KIO slave without debugging.

=== Notes ===
*You can set, say, the variable to 'file' for the kio_file slave, '''but''' set it to 'smtps' for the kio_smtp is you want to debug smtp protocol secured with SSL.
*(Vista only): ''kioslave.exe has stopped working'' message dialog can appear instead of offer for starting the debugger. Reason: Just-In-Time (JIT) Debugging of an elevated process will fail ([http://msdn2.microsoft.com/en-us/vstudio/aa964140.aspx#question20a msdn link]) apparently for security reasons. Either:
**Use <tt>KDE_SLAVE_DEBUG_POPUP</tt> instead of <tt>KDE_SLAVE_DEBUG_WAIT</tt>. See the [[#Using_KDE_SLAVE_DEBUG_POPUP_variable|Using KDE_SLAVE_DEBUG_POPUP variable]] above for more info.
**(not possible under msvc 2005): start applications and klauncher without administration permissions or attach the debugger manually before the debugger catches unhandled exceptions or an user-defined breakpoint (DebugBreak()).
*You may want to inspect kioslave sources [http://lxr.kde.org/source/KDE/kdelibs/kinit/kioslave.cpp] for more informations.

== Checking dependency of shared libraries ==
Dependency Walker is a free utility that scans any 32-bit or 64-bit Windows module (exe, dll, ocx, sys, etc.) and builds a hierarchical tree diagram of all dependent modules. [[Projects/KDE_on_Windows/Tools#Dependency_Walker|more...]]

= MS Visual Studio hints =

== Using MS Visual Studio environment for just debugging ==

Let's assume you're using command line tools (typically CMake) and want to use MS Visual Studio environment for just debugging. You don't need to create msvc project for your KDE application to be able to start debugging.

* compile and working executable version of your appliation (compiled in debug mode)
* run msvc environment
* execute ''File->Open project''
* pick your exe file in the file window
* you can set command line arguments as usual, by pick ''Project->...Properties'' command and enter all of them it in ''Command Arguments'' field
* if you have libraries placed in other directories than your application's .exe file, and you want to step into these libraries' source code while debugging, pick ''Project->...Properties'' command and enter paths to these directories in ''Symbol Path'' field
* hit F5 to run the application start the application or F10 to start step by step
* all debugging functions like setting breakpoints will be available, so you can open source code in the integrated editor and press F9 where needed
* you can even edit your source code but to compile it, do it with your external, command line tools. You cannot compile the application in the msvc environment because you have not defined a project file
* before compiling your application, stop debugging session to unlock binaries; no need to close msvc window
* after compilation you can start debugging again
* on exit you will be asked to save .sln file (so-called ''solution file'') with your debugging session -- do it and you will be able just to click the .sln file to start your debugging again
* it's recommended to save the .sln file in the .exe file directory
* next time you will run msvc environment, you can see name of your application's .sln file in ''File->Recent Projects'' submenu - you can click it to load your debugging session

== Attaching to running application ==

If you have your application is already running, you can attach to it and then start debugging.

* run msvc environment
* execute ''Debug->processes''
* select your from the processes list and click "Attach..."
* msvc environment will load your .sln file if it exists in the same directory as the .exe file, so your breakpoints set in previous session will be active again
* your program will stop on any breakpoint you have set

== One-step attaching to running application ==
You can create a macro that automates the task. See [http://blogs.msdn.com/jimgries/archive/2005/11/30/498264.aspx].

== Memory Values ==
If you are using the debug heap, memory is initialized and cleared with special values. Most interesting values are:
* 0xCDCDCDCD - Allocated in heap, but not initialized
* 0xDDDDDDDD - Released heap memory.
* 0xFDFDFDFD - "NoMansLand" fences automatically placed at boundary of heap memory. Should never be overwritten. If you do overwrite one, you're probably walking off the end of an array.
* 0xCCCCCCCC - Allocated on stack, but not initialized
See also: [http://www.samblackburn.com/wfc/technotes/WTN006.htm]

==How to Not Step Into Functions in the Debugger==
You'll probably want to avoind stepping into lower-level functions like QString constructors or operators while debugging step-by-step. Here's the detailed (unofficial) [http://blogs.msdn.com/andypennell/archive/2004/02/06/69004.aspx instruction] for various msvc versions.

==Enable automatic expanding of Qt data structures==
From the msvc docs: "While debugging, Data Tips and items in the Watch and Variable windows are automatically expanded to show their most important elements. The expansion follows the format given by the rules in this file. You can add rules for your types or change the predefined rules." ([http://www.thedatafarm.com/blog/content/binary/datatips2.jpg example screen])

MSVC 2005: To add support for expanding Qt data structures like QString of QRect, edit {msvc_installation_directory}\Common7\Packages\Debugger\autoexp.dat file and paste [[/Automatic expanding of Qt data structures|definitions]] after [AutoExpand] line.
==WINDOWS and CONSOLE subsystems==
CONSOLE subsystem is the one that displays console window (used for standard output and error streams) in addition to application's windows. WINDOWS subsystem redirects standard output and error streams to system debugging subsystem that can be displayed if needed in [[Projects/KDE_on_Windows/Tools#DebugView|DebugView]] or debuggers like msvc or [[Projects/KDE_on_Windows/Tools#WinDbg|WinDbg]].
Hint: To remove CONSOLE subsystem from already built .exe file, type <code>editbin /subsystem:windows file.exe</code>
Note: Qt's qmake syntax supports ''console'' and ''windows'' parameters of the ''CONFIG'' variable, so CONSOLE subsystem can be enabled by specifying <tt>CONFIG += console</tt> in the .pro file, windows subsystem can be enabled with <tt>CONFIG += windows</tt>.

==Deployment==
Running a VC++2005 SP1 app on another computer: manifest files are needed. See [http://www.codeproject.com/KB/cpp/vcredists_x86.aspx] and [http://blogs.msdn.com/nikolad/archive/2005/09/02/460368.aspx].

===Note on debug builds===
The hints above are for release builds (or ReleaseWithDebugInfo). Moving Debug versions of binaries to other computers is only allowed (and technicallu possible) if you have Express Edition installed there, as there is no redistributable package for Debug versions provided and even the license disallows distribution of any debug binaries (even your own).

= MinGW debugging hints =

To get a backtrace, you can just use a gdb binary. E.g. from
[http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=20507 mingw's gdb downloads on sourceforge]. Start the binary with the full path to the executable on the command line.

* Dr. Mingw - Just in Time Debugger [http://jrfonseca.planetaclix.pt/projects/gnu-win32/software/drmingw/]
* Debugging Qt programs on Windows [http://lists.trolltech.com/qt-interest/2005-08/thread01124-0.html]

'''''WARNING''''': If you are having crashes when starting applications via gdb beware of certain applications (mostly anti-virus software) that could cause problems like "Embassy Trust Suite", for example. See this [http://www.cygwin.com/ml/cygwin/2007-06/msg00405.html post].

[[Category:MS Windows]]

Getting Started/Sources/Anonymous SVN

2008-06-03T07:29:09Z

Bernhard: Slight rewrite to note that anonsvn.kde.org is a round robin dns and only subset of mirrors is listed.

{{Template:I18n/Language Navigation Bar|Getting Started/Sources/Anonymous SVN}}
{{TutorialBrowser|

series=Getting Started|

name=Getting KDE Sources Using Anonymous Subversion (SVN)|

next=[[../../Build/KDE4|Building KDE4]]|

reading=[http://svnbook.red-bean.com/ Version Control with Subversion]|
}}

== Abstract ==

For those of us that like to stay on the "bleeding edge" there's an easy way to keep a local copy of the KDE sources up-to-date — anonymous SVN.

Alternatively, install [[Getting_Started/Distribution_Packages|KDE SVN packages from your distribution]].

== Anonymous SVN ==

=== Setup Subversion ===

First, install the subversion (svn) binary if it isn't already on your computer. Your operating system should have a package for it. Alternatively you can download and compile it yourself via the [http://subversion.tigris.org/project_packages.html svn project download page]. Please read the [[Getting_Started/Sources/Using_Subversion_with_KDE|KDE Subversion tutorial]] if you are interested in how to use Subversion.

=== Checkout KDE ===

'''/trunk/''' is where the Qt4-based KDE 4 is being developed. The following is the minimal set of modules you will need to check out to build KDE and KDE software:

svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdelibs
svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdebase

{{tip|If your firewall doesn't allow access to arbitrary ports, substitute '''svn://anonsvn.kde.org/''' with '''svn://websvn.kde.org:443/''' above.}}

{{tip|The kdebase module has an external dependency, using svn:externals. The problem is, at this time, the externals property is set with an absolute path, pointing to anonsvn. For those using behind a firewall, this is a problem. You can change the property for your workspace, using two commands:
cs KDE
svn propset svn:externals "lib svn://websvn.kde.org:443/home/kde/trunk/KDE/kdebase/runtime/kstyles/oxygen/lib" kdebase/workspace/kwin/clients/oxygen
This way the external property will look for the additional files in the websvn repository.}}

'''qt-copy''' is a copy of the latest stable [http://www.trolltech.com Qt] release which works with KDE, put into SVN for convenience. It also contains patches by KDE developers that haven't found their way to Qt yet. They are recommended for those working with KDE from '''trunk'''. Instructions on how to get and configure it can be found [[Getting_Started/Build/KDE4/Prerequisites#Qt |here]].

If you wish to have a complete copy of the KDE distribution, you can simply check out the entire source tree with one command:

svn co svn://anonsvn.kde.org/home/kde/trunk/KDE

{{note|It is smarter to first use [http://websvn.kde.org/trunk/KDE The KDE Source Repository Web Viewer]. Use it to choose which modules to download. This way KDE will be quicker to install and try out.}}

If you want additional software packages you can check out the following modules within '''trunk/''' as well:

koffice
extragear
playground
kdereview

So, for example, if you want to check out koffice trunk, you can use:

svn co svn://anonsvn.kde.org/home/kde/trunk/koffice

=== Checking out trunk using snapshots ===

If you are checking out modules from '''trunk/''' you may be able to save time by using snapshots. Using Subversion trunk snapshots is described at [[../Snapshots|the Subversion snapshots tutorial page]].

=== Checking out KDE 3 instead ===

If you want to track KDE 3 rather than the bleeding edge, you may retrieve the KDE 3.5 sources using:

svn co svn://anonsvn.kde.org/home/kde/branches/arts/1.5/arts
svn co svn://anonsvn.kde.org/home/kde/branches/KDE/3.5/

And if you want the matching qt-copy:
svn co svn://anonsvn.kde.org/home/kde/branches/qt/3.3/qt-copy

=== Checking out specific releases ===

KDE modules are also tagged at each release so that it is possible to get a specific release of KDE. Most KDE modules have a tag name in the format '''tags/KDE/X.Y.Z''' (where X, Y and Z represent the exact version). The arts module (only needed for KDE 2 and KDE 3) has a different format of tag name, '''tags/arts/X.Y.Z'''. For instance to get kdelibs as it was shipped in KDE 3.5.0, do:

svn co svn://anonsvn.kde.org/home/kde/tags/KDE/3.5.0/kdelibs/

If you then want to update this checkout to KDE 3.5.5, use this command:

svn switch svn://anonsvn.kde.org/home/kde/tags/KDE/3.5.5/kdelibs

{{tip|If you used a '''/branch/''' or '''/trunk/''' path, then there is no need to switch, just run '''svn update'''.}}

=== Checking out translations ===
If you are looking for translations and other localizations, check out the appropriate language from the appropriate module: [http://websvn.kde.org/trunk/l10n-kde4 l10n-kde4] (KDE4) or [http://websvn.kde.org/trunk/l10n-kde3 l10n-kde3] (KDE3).

{{Warning|The l10n module is ''extremely'' large. Be sure you have lots of time and disk space on hand before checking out the entire l10n module. Most people only check out specific language subdirectories rather than the entire l10n module.}}

You are now ready to start building KDE! Visit [[Getting_Started/Build/KDE4|this page]] for instructions on building trunk or [[Getting_Started/Build/Stable_Version|this page]] for instruction on compiling the last stable release.

=== Checkout from behind a proxy ===

If the tip above didn't help you, and you've realized that the only way to go seems to be with http://anonsvn.kde.org/.. , then you will have to jump through a few hoops to get an svn checkout. Since http:// access is open only to developers, you will have to use svn://. Transconnect is a small piece of software that can tunnel all the traffic through your friendly neigbourhood proxy server. Get the transconnect sources from http://transconnect.sourceforge.net/ , compile it, and edit ~/.tconn/tconn.conf to point to your proxy server. Export the LD_PRELOAD variable as per the README from transconnect, and you're set to go.

== Also of interest ==
* anonsvn.kde.org is a round robin DNS entry, which will resolve to one out of several anonsvn mirrors. It is operated in Tuebingen, Germany, maintained by [mailto:dirk@kde.org Dirk Mueller] However, it might be desireable to choose a local mirror explicitely. Some mirrors are listed below, sorted by performance:
** kde.mneisen.org is located near Nuernberg, Germany, maintained by [mailto:martin.eisenhardt@mneisen.org Martin Eisenhardt]
** www.englishbreakfastnetwork.org also hosts an anonymous SVN mirror, at the University of Nijmegen, Netherlands. Maintained by [mailto:groot@kde.org Adriaan de Groot]

: Be careful when switching between mirrors. SVN remembers the server in the working copy, so to switch you have to run
svn switch --relocate svn://anonsvn.kde.org/ svn://kde.mneisen.org/
: in all your checkouts.
If you're interested in setting up a svn mirror, please contact [mailto:mueller@kde.org Dirk Mueller].

[[Category:Build KDE]]