Re: [Opensync-users] features for gnome-sync in next two months

> On Tuesday 13 May 2008 03:28:13 Halton Huo wrote:
> > > Do you have any plans for bluetooth already? BlueZ provides for linux
> > > quite nice D-Bus API. (I have no idea about OpenSolaris and Bluetooth
> > > ...)
> >
> > BZ stack is not in Solaris now. Someone inside Sun are working on it,
> > AFAIK no plan. I may develop gnome-sync on Linux if need use bluetooth.
>
>
> Maybe then you should plan to abstract your bluetooth GUI code to replace it
> on build time with D-Bus API of BlueZ or the Solaris Bluetooth stack.

>
>
> >
> > > >    - Object type config enhancement: allow user enable/disable/set_path
> > > > per obj_type for each member
> > > >    - (optional) Configuration GUI for google calendar plugin.
> > >
> > > The google calendar plugin should get rewritten first - iirc Christian
> > > had a look on this task. Christian, any update/progress here?
> >
> > Yep, can I have two requirement?
> > - proxy support
> >   httplib2 support it.
> > - save password safely, I hate plain text.
> >   gnome-keyring maybe a option, not know whether it can be used on KDE
> > environment.
>
> I hope this could be done with OSyncPluginAuthentication .. there is the
> attribute "reference" which is intended to store the ID of the key for Gnome
> key ring or KWallet. There is only some code missing so the plugin can
> request the password via this "ressource" without using specific key-ring
> implementation. I guess a new command for the OpenSync IPC is required, or
> just enhancing the connect command parameter.

>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Opensync-devel mailing list
> Opensync-devel@...
> https://lists.sourceforge.net/lists/listinfo/opensync-devel