From: Erik-Jan E. <e.e...@pl...> - 2008-10-29 10:19:20
|
Hi, The whitepaper http://cryptomilch.de/~dgollub/OpenSync/OpenSync-0.40-DRAFT-20080118.pdf http://cryptomilch.de/~dgollub/OpenSync/OpenSync-0.40-DRAFT-20080118.pdf , msynctool.c, and vconvert.c are very useful. It's quite straight forward to make the other examples. Still, one more question. Bjoern Ricks wrote: > > Hi, >> 2. Is there a list of translations of the OpensSync internals? I mean >> a list in which I can find the internals of 0.22 and see what they >> have to be in the new architecture. The page >> http://www.opensync.org/wiki/PluginPortingGuide-0.30 gives some >> information, but not enough. > I don't think so. Because both pages itself are outdated. E.g. we > changed the way to get the configuration of a plugin. We introduced in > 0.37 a new api which is common and usable for all sync plugins. It is > hard to understand how to use the api of opensync but if you want to get > familiar with the code take a look at file-sync or start to write a > plugin (sync or format) or try some code from msynctool. In my opinion > that's the best way to get into opensync. By the way I started with > opensync not even a year ago. > Also found http://www.opensync.org/docs/index.html doxygen output . Why is the opensync_engine not in the list of modules? How can I get the module in the list? Just running doxygen over the source code doesn't do the trick. Bjoern Ricks wrote: > > But in excuse of the delay of the development and unfinished/outdated > documentation all few opensync developers work on opensync in their rare > free time. There is no developer who is working full time on opensync. > It is in no way my intention to offend or criticize the developers. I have to respect mailing list etiquette, so I can't say the do a great job, but they do! Erik-Jan Elfferich -- View this message in context: http://www.nabble.com/Porting-the-examples-to-0.3x-tp20189344p20224130.html Sent from the Opensync - User mailing list archive at Nabble.com. |