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

List:       kde-pim
Subject:    Re: [Kde-pim] KMobileTools - Status
From:       Marco Gulino <marco () kmobiletools ! org>
Date:       2006-04-27 10:51:39
Message-ID: 200604271251.42766.marco () kmobiletools ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Alle 18:48, mercoledì 26 aprile 2006, Michal Svec ha scritto:

> So if I understand that properly, it could possibly work like this:
>
>    1. Communication with phone, SMS, etc
>      KMT UI <-> KMT LIB <-> KMT Backend <-> [AT commands] <-> [HW]
>                                         <-> libsyncml     <-> [HW]
>                                         <-> ...
>
>    2. Getting address book (currently uses method 1)
>      KMT UI <-> KDEPIM LIB <-> [addressbook data]
>
>    3. Synchronization of addressbook, etc (currently done directly in KMT)
>      Kitchsync UI <-> KDEPIM LIB <-> [addressbook data]
>                   <-> Kitchsync LIB <-> Opensync LIB <-> libsyncml <-> [HW]
>                                                      <-> ...
>
> Does it make sense or am I missing something?
>
> Michal

It should be almost correct.
But since we're really far away from the final release of a 
KMobileTools-KDEPim integrated solution, let's speculate a bit more...
I had another possible idea: using meta-engines.
Since KMobileTools is plugin-based, we could implement a OpenSync engine.
A mobile phone could use so a meta-engine: like using at commands for fetching 
SMS, status, and similar, and using OpenSync for AddressBook.
A similar option would be having a "OpenSync" option for each engine, but in 
this way this has to be reimplemented in each engine, and sounds a bit 
bloated.

> There's nothing like that to my knowledge. I'm even not sure that you 
> could achieve the functionality opensync requires with just AT commands,
> but I don't know much about this.

It seems it's possible.. i've read OpenSync whitepaper, and there's an option 
for devices that don't implement all required stuff: using hash tables.
Also note that at commands are not only the standard ones: Motorola has an 
extended command set (+MPBR, for instance) that returns much more fields. And 
sonyericsson mobiles can return a VCF file, with another (proprietary) 
command.

-- 
KMobileTools - Open Source meets Mobile Phones.
http://www.kmobiletools.org

[Attachment #5 (application/pgp-signature)]

_______________________________________________
kde-pim mailing list
kde-pim@kde.org
https://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]