'Re: [Kde-pim] [RFC] libkmobile - A Universal Mobile Devices'

[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:       Holger Freyther <freyther () gmx ! net>
Date:       2003-04-21 19:26:00
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 21 April 2003 20:09, Helge Deller wrote:
> Hi all,.
>
> 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
>
> As a few examples we currently have:
> 	- kitchensync has it's own type of different plugins e.g. to access qtopia
> (mobile phone support not yet available) - korganizer hasn't any direct
> import/export functionality to/from an organizer or mobile phone yet (IIRC)
> - kaddressbook has a gnokii import/export filter for NOKIA mobile phones
> only, other devices like e.g. organizers are not supported yet.
> 	- most other applications are still lacking any mobile device
> import/export functionalities
>

>
> The idea:
> 	- write a universal/generic plugin system (e.g. "class
> KMobileDeviceManager") - for every mobile device write a access-driver
KonnectorManager
> based on a "KMobileDevice" class (sample code example attached below),
> 	- modify the applications to use this plugin system, so that all types of
> mobile devices will be supported.
What is already in KonnectorManager (libkonnector2)
 - common interface
 - can fetch any data on sync and on demand ( QString like resource )
 - is generic enough to support even KDE<->KDE interaction
 - is generic enough to make use of KIO internally (KonnectorPlugin could wrap 
KIO and then use common Filter to convert from and to Syncee/SyncEntry )
 - You can put about anything into a Syncee/SyncEntry pair ( 
KAddressBookImportSyncee in example... )
What is missing in KonnectorManager:
 - auto configuring and finding of items
 - first implementation of Filters
 - Definintion of a Resource type ( you can ask a KonnectorPlugin to fetch 
data by string this string needs to be defined some how )
 - a way to 'query' what a KonnectorPlugin supports as built in. Can fetch on 
demand ( like Addressbook...PictureCollection, RingTones... )( so 
KAddressbook would ask does XYZ support our Addressbook if yes just fetch it 
for me )
>
> Further ideas could be:
> 	- a kicker module. It would search regulary at the USB/IRDA/Bluetooth
> ports for new devices and allow the user to configure the new device at
> once.
I would put this into KitchenSyncUI ( the SystemTray )
> 	- a kioslave (e.g. "mobile://") , which shows all configured devices.
> 		The root-directory would show an icon for each device (like a
> sub-directory), then in each of those sub-directories you would see
> directories for each capatibility (Addressbook, Calendar, Notes, Storage).
> The Addressbook could show vCard files, the calendar vCalendar files, and
> the storage subdirectory would show the files on the device.
jowenn and me are planning to do this since +1 year. This would integrate into 
the KDED module he wrote ( even added mimetypes for that ). I would do that 
the following way a kioslave which uses DCOP to talk to the GUI. The GUI puts 
the device onto the DESKTOP and KDED calls the GUI. The GUI should then ask 
the Plugin for special stuff( like install, put on cf, put on sd-card ) but 
should also query for standard/built-in types and then call the special 
KIO-Slave.
Showing single vCards sounds nice but is hard to implement. QtopiaKonnector 
for example does not save a copy of the XML files used but only md sums. So 
it would need to fetch and parse the whole XML file to present that way. 
Others may operate on a slow serial connection. It would be better to do it 
like WinCE does ( HPC 2000 at least ) to show them as AddressDataBase and so 
on....
> 	- a new kcontrol module to globally configure the attached mobile devices
can be taken from the GUI
>
> Since my time in general is very limited, I definitively would need help
> from others on such a project.
> Personally I would like to start with an implementation with gnokii and
> gammu to make most mobile phones directly accessible.
> If people don't complain, I would like to create the subdirectory
> kdepim/libkmobile and put my initial work there.
>
> What does people on this list think about such an idea ?
I think your ideas are nice ( want to see them implemented ) but I think all 
this can be done with libkonnector2 already. 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. Please tell me why 
you think the current KitchenSync solution is not suitable for usage in 
inside KDE.

regards Holger
>
> Helge

- -- 
_____________________________________________
Holger 'zecke' Freyther
developer
Project OPIE- the Open Palmtop Integrated Environment
http://opie.handhelds.org | http://www.opie.info (german)
IRC: irc.freenode.net #opie #opie.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+pEXLGckbdURWU2oRAqsHAJ95psRLe9WfDxdNihjI6QHzatBb8QCdGE9i
vFQKTvrpELy/4yXHsqBB8p4=
=9/PQ
-----END PGP SIGNATURE-----

_______________________________________________
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] 