Re: [Opensync-devel] Gnokii patch

[Emanoil K. <del...@ya...>]

Hi, I could do the check in and have a look into the plugin.
I prefer c++ but in C were the first lesson in serious programming that I had back in 1990 ...

If you are familiar with object oriented programming (I think you are) and C++ think of C as if objects (C++) are structures (C) and methods (C++) are loose functions (C) so that everything in C is a function besides structures and variables. I hope this brief info helps you understand it.

Thank you for looking for alternatives I was wondering what this gnkokii thing was all about.

--- On Sat, 1/8/11, Quentin Denis <que...@gm...> wrote:

> There are also a sink and an easy slowsync issue to solve
> in gnokii_contacts.c 
> (and the same for gnokii_calendar.c) but before being able
> to fix this I would 
> need two questions answered:
> 
> 1. what is exactly a sink object and what is the concept
> behind it? Just a two 
> lines explaination please, I have a vague idea...

you can have one sync object type per config (notes, contacts, calendar and todo)

those are paired with the equivalent obj type on the other end(s)/plugin(s)

you assign one or more formats to an obj (like vtodo10/20 etc) on each side and the syncengine is doing the conversion and the sync between for you.

> 
> 2. it's my first time I code in C, but do the functions
> have to respond to a 
> particular constructor? Take the example of this outdated
> one:
> 
> void gnokii_calendar_get_changes(void *plugindata,
> OSyncPluginInfo *info, 
> OSyncContext *ctx)
> 
> which is only called by: 
> osync_objtype_sink_set_get_changes_func(event_sinkenv->sink,
> 
> gnokii_calendar_get_changes);

no, this way you assign a custom function to the object (in this case event_sinkenv->sink is associated with gnokii_calendar_get_changes) The code takes care for passing the right arguments to the function when called

> 
> no argument is passed, to I suppose it tells the engine to
> call the function 
> and to pass itself the required arguments? Hence the need
> to use a certain 
> standard constructor that I would have to take over from
> say the file-sync 
> plugin.

you can follow/borrow from this or any other ... the problem is in the details

> 
> There are also some objformat issues in that file, but I
> will try hard to 
> solve them lateron if nobody is willing to apply his/her
> expertise easily and 
> quickly. ;)
> 
> Best regards,
> Quentin (falling back on gnokii because of syncml issue:
> Ticket #1267)
> 

So your plan is to use gnokii with akonadi?

thanks and kind regards