[Kde-pim] Synchronization Framework for KDE

[Pascal Bach]

On Thu, Jul 31, 2008 at 9:28 PM, Stephen Kelly <steveire at gmail.com> wrote:
>
> I'm not sure if opensync and consuit share any code, but they seem to do
> largely the same job, though conduit may be dependant on GNOME after
> reading the first paragraph of the homepage. Opensync is platform
> independent, and might also work on windows (dunno).
>
 Currently it's Gnome dependent specifically PyGTK for the gui,
glib/gobject for the mainloop and the signals and gnomevfs for the
file access.

But the gnomevfs file abstraction is currently replaced with a purely
python based one with the aim to make the software working on windows
too.

The PyGTK UI should be fairly easy to replace with a Qt one as the
software is written with different gui s in mind.

The gobject dependencies are not likely to be dropped. As I have not
enough experience I don't know if this is a problem. One solution we
discussed was to let a KDE frontend communicate with conduit via dbus.
But maybe somebody knows more about gobject <-> Qt integration.

On Thu, Jul 31, 2008 at 9:35 PM, Ingo Klöcker <kloecker at kde.org> wrote:
>
> We use the OpenSync framework (http://www.opensync.org/). kitchensync is
> a KDE frontend using this framework.
>
> Note that OpenSync is mentioned at the bottom of
> http://www.conduit-project.org/wiki/Goals.
>
I haven't seen this yet thanks, as what I can tell until now it seems
to be very easy to write plugins for conuit this makes it easy to
integrate Online services. So maybe a solution would be to support
these plugins in kitchensync alongside the opensync framework. I don't
know if this is possible or even desirable.

Regards,
Pascal
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/