On Mon, 2004-03-15 at 12:13, Armin Bauer wrote:
> On Mon, 2004-03-15 at 18:01, Tom Foottit wrote:
> > This means that the sync engine has to have knowledge of each plugin's
> > configuration parameters, which is probably a bad idea.
>
> thats the great thing about xml: i can just take the portion
On Mon, 2004-03-15 at 18:01, Tom Foottit wrote:
> On Mon, 2004-03-15 at 10:45, Armin Bauer wrote:
>
> > the dbus offers a much greater independence to the plugins since they
> > can interecept and alter all the communication between the engine and
> > the plugin.
> >
> > so here is my proposal:
>
On Mon, 2004-03-15 at 10:45, Armin Bauer wrote:
> the dbus offers a much greater independence to the plugins since they
> can interecept and alter all the communication between the engine and
> the plugin.
>
> so here is my proposal:
> - dlopen the plugin
> - call a function on the plugin which i
On Mon, 2004-03-15 at 16:25, Tom Foottit wrote:
> On Mon, 2004-03-15 at 09:39, Armin Bauer wrote:
>
> > I started to work on 0.90, especially on the dbus framework we need.
>
> Remember to keep it in your sandbox until we branch 0.82 :)
i currently keep it on my companies CVS
>
> >
> > But
On Mon, 2004-03-15 at 09:39, Armin Bauer wrote:
> I started to work on 0.90, especially on the dbus framework we need.
Remember to keep it in your sandbox until we branch 0.82 :)
>
> But i have come across some questions:
>
> 1. how to write the syncType plugins (the plugins that handle the
>
