Plasma/Clock: Difference between revisions
| Line 34: | Line 34: | ||
== PIM Data Interface == | == PIM Data Interface == | ||
Currently PIM data is read-only and is provided via the Calendar DataEngine. To make PIM data 2-way would require the creation of a Service. However, the Akonadi interface and the creation of PIM data in general is very complex and is not ideally suited to being mapped into a Data Engine or Service. The API would be very big and unwieldy and a maintenance nightmare. This is one occasion where Plasma elements requiring complex functionality will be better off directly using the Akonadi API and UI elements. However this doesn't stop a simplified service being provided that would meet 80% of needs with the more complex requirements being left for the native apps to handle. | Currently PIM data is read-only and is provided via the Calendar [http://techbase.kde.org/Development/Tutorials/Plasma/DataEngines Plasma DataEngine]. To make PIM data 2-way would require the creation of a [http://techbase.kde.org/Development/Tutorials/Plasma/Services Plasma Service]. However, the Akonadi interface and the creation of PIM data in general is very complex and is not ideally suited to being mapped into a Data Engine or Service. The API would be very big and unwieldy and a maintenance nightmare. This is one occasion where Plasma elements requiring complex functionality will be better off directly using the Akonadi API and UI elements. However this doesn't stop a simplified service being provided that would meet 80% of needs with the more complex requirements being left for the native apps to handle. | ||
=== Plasma Service Design === | === Plasma Service Design === | ||
An initial minimal Plasma Service | An initial minimal definition for the Plasma Service [[https://projects.kde.org/projects/kde/kde-workspace/repository/revisions/master/entry/plasma/generic/dataengines/calendar/calendar.operations has been created]. The actual implementation is still required. | ||
https://projects.kde.org/projects/kde/kde-workspace/repository/revisions/master/entry/plasma/generic/dataengines/calendar/calendar.operations | |||
The actual implementation is still required. | |||
Revision as of 13:37, 28 May 2012
Plasma is all about Clocks. It's an old joke, but it contains a kernel of truth. The clock is the one element of the desktop most people depend on, and it can be a valuable conduit for information they need. This page will co-ordinate all the resources around the Plasma Clock and plans for it's future.
Resources
KDE Bugzilla all open Plasma Clock bugs
Current Implementation
The current implementation can be found in the following locations.
Plasma Clock Library holding the common base implementation for all clock/calendar widgets.
PIM Data Interface
Currently PIM data is read-only and is provided via the Calendar Plasma DataEngine. To make PIM data 2-way would require the creation of a Plasma Service. However, the Akonadi interface and the creation of PIM data in general is very complex and is not ideally suited to being mapped into a Data Engine or Service. The API would be very big and unwieldy and a maintenance nightmare. This is one occasion where Plasma elements requiring complex functionality will be better off directly using the Akonadi API and UI elements. However this doesn't stop a simplified service being provided that would meet 80% of needs with the more complex requirements being left for the native apps to handle.
Plasma Service Design
An initial minimal definition for the Plasma Service [has been created. The actual implementation is still required.