From: Armin B. <arm...@de...> - 2005-04-26 10:42:12
|
Matthew Kay wrote: >Glad you're on this list, Pawel! > >Glad people think this is a good idea. I'm fine with converting to XML >in the plugin, that should be very easy (especially in Python) , and >I'll look at the code David suggested for the API. > >Sadly, I've got exams at Imperial College, London over the next few >weeks so I'm unlikely to get started on it right away - if anyone else >is enthused, by all means go ahead and report to the list! > >I had a thought about merging. Obviously it is a complete nightmare >trying to get the specific capabilities of each device, but perhaps >that's something that you could leave to the user, say by getting them >to configure the plugin via an XML file or the GUI as to which fields >their device can handle? For the Gnokii plugin, this problem is >simplified - the restriction is not so much the phones themselves as the >gnokii application, so you could provide the users for presets >(Gnokii-series 60, Gnokii-series 40 etc.). These could be updated on the >plugin side as Gnokii development progressed. This is one more advantage >of the server/client architecture rather than dealing with the phone >directly - you are given predictable output. > > i think opensync should be as easy to use for the user as possible, so if there was a way to have less options for the user i would go this way. Instead of a drop down menu where the user has to pick his phone this should be detected. each phone will tell what it is somewhere and this should be used to report the correct capabilities. I think there could be an even better approach (at least for the user and for the plugin developers): auto detection. We would generate a xml contact for example that has all available fields set. Then we send it to the device and query it again afterwards. Now we just have to compare which fields are missing. We could even implement a caching mechanism for this so we dont have to do this when we see a "known" phone. >But, I can well imagine that it's a big coding job - good luck with the >SyncML plugin, I think that you Opensync developers are making something >really good. The decision to start something completely new and >ambitious (rather than sticking with Multisync 0.8x) is really starting >to pay off, I think. > > > I sure hope so :) >Best wishes, >Matt >-- >M.Sc. Computer Science student >Imperial College, London > >256a Archway Road, >London, >N6 5AX > >tel 07717 204242 > > > >------------------------------------------------------- >SF email is sponsored by - The IT Product Guide >Read honest & candid reviews on hundreds of IT Products from real users. >Discover which products truly live up to the hype. Start reading now. >http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >_______________________________________________ >Opensync-users mailing list >Ope...@li... >https://lists.sourceforge.net/lists/listinfo/opensync-users > > |