|
From: Mark E. <ma...@mp...> - 2010-01-10 09:38:08
|
Hi Bjoern ! Ah yes, real life gets in the way sometimes. I'd be delighted to take a look at the python wrappers, I started having a stab already. The other python wrappers I work with are built with pyrex rather than swig, but it looks like the API can be updated without too much of a learning curve. I was also going to try and add some wrappers to libwbxml, does anyone who works on that hang around here ? Thanks Mark On Sun, 2010-01-10 at 09:28 +0100, Bjoern Ricks wrote: > Sorry for the late reply. Currently the development of opensync stucks > again, because Daniel and me haven't had much time to work on it. This > list is correct of course. Your patch seems to be correct and feel > free to commit it to opensync svn. I guess Daniel will be happy to > give you access to our codebase. We currently don't have a maintainer > for the python-module therefore it would be great if you can step in > and take up the maintenance of it. The problem of the python api in > opensync is that there is no developer with python knowledge. I > changed e.g. the opensync list api in the past but don't had any clue > how to convert that to the python api. > > regards > Bjoern > > Am 31.12.09 19:23, schrieb Mark Ellis: > > Hi opensync-devel > > > > I'm hoping this list is used, since I haven't seen much activity .... > > > > I'm involved with the synce project, that uses the python plugin to sync > > against windows mobile devices. > > > > We started looking again at later opensync versions after the 0.39 > > release, and I've attached a patch to the python plugin against trunk. I > > am reasonably confident with what I've done, but haven't actually been > > able to test it since the libopensync python wrappers from trunk aren't > > behaving. I guess they are lagging somewhat behind the api changes. > > > > I may have a look at fixing up the python wrappers, but need to get to > > grips with the opensync internals more first. Is anyone working on this > > at the moment ? Any pointers ? > > > > Thanks > > Mark > > > > > > > > ------------------------------------------------------------------------------ > > This SF.Net email is sponsored by the Verizon Developer Community > > Take advantage of Verizon's best-in-class app development support > > A streamlined, 14 day to market process makes app distribution fast and easy > > Join now and get one step closer to millions of Verizon customers > > http://p.sf.net/sfu/verizon-dev2dev > > > > _______________________________________________ > > Opensync-devel mailing list > > Ope...@li... > > https://lists.sourceforge.net/lists/listinfo/opensync-devel > > > |