Development/Architecture/KDE4/Akonadi - Revision history

Yurchor: Marked this version for translation

2013-01-04T13:55:47Z

Marked this version for translation

Yurchor: remove extra tags

2013-01-04T13:55:29Z

remove extra tags

Neverendingo: Marked this version for translation

2013-01-04T13:51:38Z

Marked this version for translation

Neverendingo: add translate tags

2013-01-04T13:51:09Z

add translate tags

Neverendingo: add translate tags

2013-01-04T13:50:14Z

add translate tags

Neverendingo: add translate tags

2013-01-04T13:49:02Z

add translate tags

AnneW at 18:36, 15 July 2012

2012-07-15T18:36:47Z

Krake: Adding overview of Akonadi concepts

2009-01-25T19:21:25Z

Adding overview of Akonadi concepts

Krake: Add link to API docs

2009-01-25T15:01:11Z

Add link to API docs

Krake: Adding basic introductional information

2009-01-25T14:50:34Z

Adding basic introductional information

New page

{{Template:I18n/Language Navigation Bar|Development/Architecture/KDE4/Akonadi}}
'''Akonadi'''

Communication, calendaring and keeping information about others are fundamental parts of your daily work and private life.
As a provider of an application development framework and of a Free Software desktop runtime environment, KDE addresses this by tightly integrating with the PIM infrastructure provided by [http://www.akonadi-project.org/ Akonadi].

KDE's implementation of an Akonadi client library stack makes it easy to develop both applications using Akonadi as their data source as well as Akonadi agents for the actual access to the data's persitant storage.

===Further reading===
* [[Development/Tutorials#Personal Information Management (Akonadi)|Akonadi Tutorials]]
* [[Projects/PIM/Akonadi|Akonadi Project Wiki]]

[[Category:KDE4]]
[[Category:Architecture]]
[[Category:Akonadi]]

← Older revision		Revision as of 13:55, 4 January 2013
Line 37:		Line 37:
	All communication with these two roles is implemented in the KDE client libraries for Akonadi and available to developers at different level of abstraction.		All communication with these two roles is implemented in the KDE client libraries for Akonadi and available to developers at different level of abstraction.

		+	<!--T:25-->
	{{tip\|Thinking about the server as a proxy-like service helps to avoid misinterpreting its task, e.g. it is caching data on behalf of its clients, not interpreting or permanently storing it.}}		{{tip\|Thinking about the server as a proxy-like service helps to avoid misinterpreting its task, e.g. it is caching data on behalf of its clients, not interpreting or permanently storing it.}}

@@ Line 36: / Line 36: @@
 <!--T:11-->
 All communication with these two roles is implemented in the KDE client libraries for Akonadi and available to developers at different level of abstraction.
-<translate>
+{{tip|Thinking about the server as a proxy-like service helps to avoid misinterpreting its task, e.g. it is caching data on behalf of its clients, not interpreting or permanently storing it.}}
 === Akonadi Agents === <!--T:13-->

@@ Line 3: / Line 3: @@
 '''Akonadi'''
-<translate>Communication, calendaring and keeping information about others are fundamental parts of your daily work and private life.
+<translate><!--T:1-->
 As a provider of an application development framework and of a Free Software desktop runtime environment, KDE addresses this by tightly integrating with the PIM infrastructure provided by [http://www.akonadi-project.org/ Akonadi].
 KDE's implementation of an Akonadi client library stack makes it easy to develop both applications using Akonadi as their data source as well as Akonadi agents for the actual access to the data's persistant storage.
-== Concepts ==
+== Concepts == <!--T:3-->
 Akonadi's design follows the principle of separation of concerns, meaning that each component has a small, well defined role to fullfil in order to achieve a fully functional setup.
 There are three main categories of components, all of which are implemented as individual processes for increased system stability and implementation independence:
 * Akonadi Server
 * Akonadi Agents
 * Akonadi Applications
-=== Akonadi Server ===
+=== Akonadi Server === <!--T:7-->
 The server category consists of two roles: control and cache.
 Control is implemented by a process called '''akonadi_control'''. It is the first to start and controls the life cycle of all components other than end user applications.
 Cache is implemented by a process called '''akonadiserver'''. It is the hub for the data flow, tracks changes and is responsible for system consistency, e.g. ensures unique identifiers, etc.
 All communication with these two roles is implemented in the KDE client libraries for Akonadi and available to developers at different level of abstraction.
 </translate>
-{{tip|<translate>Thinking about the server as a proxy-like service helps to avoid misinterpreting its task, e.g. it is caching data on behalf of its clients, not interpreting or permanently storing it.</translate>}}
+{{tip|<translate><!--T:12-->
 <translate>
-=== Akonadi Agents ===
+=== Akonadi Agents === <!--T:13-->
 The agent category describes processes which perform their task without human interaction.
 This includes a special role also referred to as Akonadi Resources, agents which transport data between the cache and the data's actual persistant storage locations, e.g. files.
 The KDE client libraries for Akonadi provide convenience classes to ease development of generic agents as well as the resource subtype.
 The KDE PIM project provides a set of commonly required implementations as part of their runtime module.
-=== Akonadi Applications ===
+=== Akonadi Applications === <!--T:16-->
 The application category refers to the usual end user visible application, e.g. address book, calendar or e-mail program. Implementations of this category can sometimes be referred to as Akonadi Clients, since agents can be seen as part of the server-like functionality, both from the point of view of users as well as application developers.
 The KDE client libraries for Akonadi provide both a low level job based API as well as high level data models, views and standard actions.</translate>
-<translate>== Further reading ==</translate>
+<translate>== Further reading == <!--T:19--></translate>
-* <translate>[[Development/Tutorials#Personal Information Management (Akonadi)|Akonadi Tutorials]]</translate>
+* <translate><!--T:20-->
 * [http://api.kde.org/4.x-api/kdepimlibs-apidocs/akonadi/html/index.html Akonadi KDE API Documentation]
-* <translate>[[Projects/PIM/Akonadi|Akonadi Project Wiki]]</translate>
+* <translate><!--T:21-->
-<translate>[[Category:KDE4]]</translate>
+<translate><!--T:22-->
-<translate>[[Category:Architecture]]</translate>
+[[Category:KDE4]]</translate>
-<translate>[[Category:Akonadi]]</translate>
+<translate><!--T:23-->

@@ Line 28: / Line 28: @@
 All communication with these two roles is implemented in the KDE client libraries for Akonadi and available to developers at different level of abstraction.
 </translate>
-{{tip|Thinking about the server as a proxy-like service helps to avoid misinterpreting its task, e.g. it is caching data on behalf of its clients, not interpreting or permanently storing it.}}
+{{tip|<translate>Thinking about the server as a proxy-like service helps to avoid misinterpreting its task, e.g. it is caching data on behalf of its clients, not interpreting or permanently storing it.</translate>}}
 <translate>

@@ Line 51: / Line 51: @@
-[[Category:KDE4]]
+<translate>[[Category:KDE4]]</translate>
-[[Category:Architecture]]
+<translate>[[Category:Architecture]]</translate>
-[[Category:Akonadi]]
+<translate>[[Category:Akonadi]]</translate>

← Older revision		Revision as of 18:36, 15 July 2012
Line 1:		Line 1:
−	~~{{Template:I18n/Language Navigation Bar\|Development/Architecture/KDE4/Akonadi}}~~	+
	'''Akonadi'''		'''Akonadi'''

@@ Line 9: / Line 9: @@
 ===Further reading===
 * [[Development/Tutorials#Personal Information Management (Akonadi)|Akonadi Tutorials]]
 * [[Projects/PIM/Akonadi|Akonadi Project Wiki]]