wiki:plugins

Plugin Introduction

From these pages can be found generic non-version specific information about each available plugin:

Akonadi?

Barry?

This plugin is maintained outside of the OpenSync? trees, but is kept in step with the OpenSync? project, led by one of the OpenSync? developers, Chris Frey. More information can be found at  http://netdirect.ca/barry

Google?

This plugin allows to synchronize your Google Calendar with the OpenSync? framework. More details can be found at Google-Calendar

gnokii?

The gnokii-sync plugin is based on libgnokii from the gnokii project. The gnokii project provides many connectivity functions for Nokia mobile phones. This plugin should be used for older Nokia mobile phones which don't support SyncML. For more details and supported devices see gnokii-sync.

GPE

This plugin allows GPE Palmtop Environment based devices to synchronize with the OpenSync? framework. More details and supported devices can be found at GPE

evolution

The Evolution plugin allows to synchronize with the evolution-data-server Contact, Events and Todos with the OpenSync? framework. evo2-sync.

File?

The file-sync plugin is intended to synchronize all kind of data (all object types), like events, contacts and todos , directly to the file-system. It is also intended to create Backup of your mobile device. For more details see file-sync.

IrMC?

This plugin allows applications using OpenSync? to synchronize mobile phones with IrMC support. IrMC synchronization is mostly used by Siemens and Sony Ericsson mobile phones. For details about the plugin and supported devices see irmc-sync.

kdepim?

The kdepim-sync plugin is intended to synchronize the KDE PIM applications like kaddressbook, korganizer and knotes with other OpenSync? plugins kdepim-sync. Hint: kdepim-sync doesn't have/need any configuration yet (version 0.20)

ldap

Motorola?

This plugin is intended to synchronize Motorola mobile phones via the AT command set. Present Motorola mobile phones, like the Motorola Razr V3, only support synchronize with SyncML via HTTP. The moto-sync plugin solve this fact and allows a local synchronization. For details about the plugin and supported devices see moto-sync.

mozilla

opie?

The opie-sync plugin allows OPIE based devices to synchronize with the OpenSync? framework. For more information about OPIE:

 http://opie.handhelds.org/ More details about the opie-sync plugin and supported devices can be found at opie-sync.

Palm?

The Palm plugin is based on libpisock from pilot-link project. The palm plugin is intended to synchronize Palm OS based devices like PalmOne?, Tungsten, Treo, Sony Clie and others. For more details see palm-sync.

python-module

This is actually not a synchronization plugin. The python module is the OpenSync? interface for python plugins like moto-sync.

qtopia?

Synce?

The Synce plugin is based on the libraries of the synce package, which allows to synchronize Windows CE and Window Mobile devices. For more details and supported devices see Synce.

SyncML

The SyncML plugin actually consists of two parts. SyncML OBEX Client and SyncML HTTP Server. SyncML HTTP requires to setup a network connection between the host and the mobile phone. Also additional configuration on the mobile phone side is required for HTTP synchronization.

SyncML OBEX Client SyncML HTTP Server

Tomboy-format?

Tomboy?

vformat?