[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    Re: [Kde-pim]  [RFC] libkmobile - A Universal Mobile Devices
From:       Helge Deller <deller () gmx ! de>
Date:       2003-04-23 5:47:04
[Download RAW message or body]

Hi Holger,

On Monday 21 April 2003 09:26 pm, Holger Freyther wrote:
> On Monday 21 April 2003 20:09, Helge Deller wrote:
> > I would like to start a universal "Mobile Devices Connection Kit",
> > which should make it easy for a lot of programs to access different
> > mobile devices through a universal and generic interface and enable
> > them to exchange any type of data through this interface.
>
> short I think libkonnector2 + Syncee/SyncEntry does support that all

The main problem with libkonnector2 and it's functionality is, that it
only is available (and from the API usable) for Kitchensync.
I see no way, how kaddressbook or kcalendar could use this
interface at once. On the other side I can see, how easily they can use the 
interface I propose directly.

> > The idea:
> > 	- write a universal/generic plugin system (e.g. "class
> > KMobileDeviceManager") - for every mobile device write a access-driver
>
> KonnectorManager

Yes, something like this is needed.

> > What does people on this list think about such an idea ?
>
> I think your ideas are nice ( want to see them implemented ) 

me too :-)

> but I think all this can be done with libkonnector2 already. 

I disagree. It's the right way to go to do syncronisation, but
not what I intend my proposal for. Please read below.

> I think the libkonnector2
> rewrite did solve the greatest problems api wise and it is known to work. I
> would like you to join KitchenSync so we can spend our limited together on
> one project instead of idling on two different projects. 

Sure.
I would like to start implementing my ideas. And one of the top-goals will be
to write a libkonnector2-plugin, which will use the libkmobile infrastructure.

> Please tell me why you think the current KitchenSync solution is not suitable for usage in
> inside KDE.

It's definitively usable inside KDE. It's goal is to do clean syncronisation, but
I'm thinking of an easy way to connect devices, select some (a single) data structure
(file, contact or calendar entry), drag&drop it from konqueror to kaddressbook or
kcalendar and import/export it that way graphically. This is not about syncronisation, it's 
about moving information.

Think about my mobile phone. I come with my mobile phone to your laptop, it's
automatically detected, we drag 3 different phonebook-entries from it into your addressbook
and ignore all others. With kitchensync you would need to syncronize all entries at once.
At the same time I connect my mp3 player to your laptop and copy 2 of my files to
your machine. Directly. Then I drag one other song from any of your directories onto my player.
This is how I would like it to work later on a common interface for all types of mobile
devices, and this is not what kitchensync is intended for.

I hope you see that libkmobile will not be a clone or another implementation of 
kitchensync. It just does a different job, but if I write a libkmobile plugin for
kitchensync you will get the advatages of both solutions without any syncronisation 
problems.

Regards,
Helge


_______________________________________________
kde-pim mailing list
kde-pim@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/
[prev in list] [next in list] [prev in thread] [next in thread]