PIM: Difference between revisions

From KDE Community Wiki
(→‎Other Links: Remove dead links)
(→‎Technologies used in KDE PIM: Remove section (massively outdated, incomplete))
Line 79: Line 79:
*[[/RSS_framework_for_Akonadi|RSS framework for Akonadi]]
*[[/RSS_framework_for_Akonadi|RSS framework for Akonadi]]
[[Category:PIM]]
[[Category:PIM]]
===Technologies used in KDE PIM===
This list is quite incomplete.
* http://doc.trolltech.com/4.4/richtext.html - Used for the KMail composer. See also [http://api.kde.org/4.x-api/kdelibs-apidocs/kdeui/html/classKRichTextWidget.html KRichTextWidget].
* http://doc.trolltech.com/4.4/model-view-programming.html - Used throughout KDEPIM including KMail tree views etc.
* Akonadi: [[PIM/Akonadi|Wiki]], [http://www.akonadi-project.org/ Website], [http://download.akonadi-project.org/ Tarballs]

Revision as of 11:52, 9 September 2024

KDE PIM is a package that contains personal information management tools.

The KDEPIM team develops the main application Kontact with all its plugins like KMail, KNode, KOrganizer, KAddressbook, Akregator, KJots and others.

To join the team, simply email the kde-pim mailing list, and join the irc://irc.libera.chat/kontact IRC channel.

Resources

Development

Much of the infrastructure of KDE PIM has been moved to kdepimlibs module as a framework for all KDE applications. Therefore we have two main modules within the KDE SVN: kdepim and kdepimlibs. The latter contains code that provides public APIs.

Current development focus as of January 2009 is on the Akonadi service and porting existing applications to Akonadi and KMime and other frameworks.

If you're looking into starting PIM development, have a look at the Junior Jobs.

Documentation

KDE PIM 4

  • README documents stored in the KDE GIT:
  • kdepim:
  • kdepimlibs

Planning

Other

KDE PIM 3

The KDE PIM 3 branch is frozen and no longer actively maintained. Use the KDE 3 enterprise branch for a version of Kontact that is still being updated.

Enterprise branches

Kontact is the primary Kolab client. There are different release cycles for the Kolab clients and for KDE, and therefore there are so-called enterprise branches in SVN where the Kolab versions are maintained. Changes in the enterprise branches are regularly merged back to SVN trunk. The enterprise branches are maintained by KDAB.

More information about the enterprise branches can be found at:

Other Links

PIM SoC 2008 projects