opensync-users

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

[Halton H. <Hal...@Su...>]

Hi,

I'm going to implement some new things for gnome-sync[1] in next two
months, this includes:

   - HAL/DBUS support, auto detection and auto connection with existing
groups. 
   - Configuration GUI for palm-sync plugin.
   - Configuration GUI for libsyncml Plugin.
   - Object type config enhancement: allow user enable/disable/set_path
per obj_type for each member 
   - (optional) Configuration GUI for google calendar plugin. 

If you do not know gnome-sync, you could refer th GUI design doc on
http://www.genunix.org/wiki/index.php/Opensync_new_gui_design

[1] http://sourceforge.net/projects/gnome-sync

Comments are welcomed!

Thanks,
Halton.

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

[Daniel G. <dg...@su...>]

On Monday 12 May 2008 13:33:15 Halton Huo wrote:
> Hi,
>
> I'm going to implement some new things for gnome-sync[1] in next two
> months, this includes:
>
>    - HAL/DBUS support, auto detection and auto connection with existing
> groups.

Thats really interesting!

How do you plan to "map" a certain device which get announced via HAL (as 
connected) and the configured group/member? We had some discussion in the 
past about this ...

The new OSyncPluginConfig Interface provides also a connection specific 
subcomponent: OSyncPluginConnection. You would have to load the OSyncGroupEnv 
step through all the member of each group and load the OSyncPluginConfig of 
the member and check for matching device in OSyncPluginConnection. I hope the 
information in OSyncPluginConnection are enough to identify those devices. If 
not please let me know, so we can enhance the interface for this...

Once the OpenSync side got stabilized i hope i can do the same with 
KitchenSync, but using Solid, not speaking to HAL directly.

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 ...)

>    - Configuration GUI for palm-sync plugin.
>    - Configuration GUI for libsyncml Plugin.

I would recommend to take a look on the the new OSyncPluginConfig interface. 
Since I plan to get rid of custom XML configurations - it would be nice if 
you could give me some feedback on the interface as well.. if there is 
anything missing or unhandy to write configuration GUIs..

>    - 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?

>
> If you do not know gnome-sync, you could refer th GUI design doc on
> http://www.genunix.org/wiki/index.php/Opensync_new_gui_design
>
> [1] http://sourceforge.net/projects/gnome-sync

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

[Halton H. <Hal...@Su...>]

On Mon, 2008-05-12 at 23:47 +0200, Daniel Gollub wrote:
> On Monday 12 May 2008 13:33:15 Halton Huo wrote:
> > Hi,
> >
> > I'm going to implement some new things for gnome-sync[1] in next two
> > months, this includes:
> >
> >    - HAL/DBUS support, auto detection and auto connection with existing
> > groups.
> 
> Thats really interesting!
> 
> How do you plan to "map" a certain device which get announced via HAL (as 
> connected) and the configured group/member? We had some discussion in the 
> past about this ...
> 
> The new OSyncPluginConfig Interface provides also a connection specific 
> subcomponent: OSyncPluginConnection. You would have to load the OSyncGroupEnv 
> step through all the member of each group and load the OSyncPluginConfig of 
> the member and check for matching device in OSyncPluginConnection. I hope the 
> information in OSyncPluginConnection are enough to identify those devices. If 
> not please let me know, so we can enhance the interface for this...
I noticed you added them in, definitely will use it.

> 
> Once the OpenSync side got stabilized i hope i can do the same with 
> KitchenSync, but using Solid, not speaking to HAL directly.
> 
> 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.

> 
> >    - Configuration GUI for palm-sync plugin.
> >    - Configuration GUI for libsyncml Plugin.
> 
> I would recommend to take a look on the the new OSyncPluginConfig interface. 
> Since I plan to get rid of custom XML configurations - it would be nice if 
> you could give me some feedback on the interface as well.. if there is 
> anything missing or unhandy to write configuration GUIs..
Yes, you mentioned it on IRC. Will add this change.

> 
> >    - 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.

Cheers,
Halton.
> 
> >
> > If you do not know gnome-sync, you could refer th GUI design doc on
> > http://www.genunix.org/wiki/index.php/Opensync_new_gui_design
> >
> > [1] http://sourceforge.net/projects/gnome-sync
> 
> 
> -------------------------------------------------------------------------
> 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
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-devel

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

[Daniel G. <dg...@su...>]

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.

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

[Halton H. <Hal...@Su...>]

On Tue, 2008-05-13 at 07:45 +0200, Daniel Gollub wrote:
> 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.
Yes, Check BZ stack during configure time.
> 
> 
> >
> > > >    - 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.
Any demo code for it?

-Halton.

> 
> 
> -------------------------------------------------------------------------
> 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
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-devel

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

[Jedy W. <Jed...@Su...>]

On Mon, 2008-05-12 at 23:47 +0200, Daniel Gollub wrote:

> 
> >    - Configuration GUI for palm-sync plugin.
> >    - Configuration GUI for libsyncml Plugin.
> 
> I would recommend to take a look on the the new OSyncPluginConfig
> interface. 
> Since I plan to get rid of custom XML configurations - it would be
> nice if 
> you could give me some feedback on the interface as well.. if there
> is 
> anything missing or unhandy to write configuration GUIs..
> 

Hi daniel,

I took a look at the code of opensync_plugin_config.c. Currently, there
are several APIs for the configuration of palm-sync and libsyncml
plugin, but lack of APIs for the configuration of file/evolution plugin.
For example, APIs to retrieve/store objtype/objformat supported by the
plugin, path of the file/calendar/contacts/.... Now we can get these
information through other APIs. But it's better to provide unified
interfaces.

Regards,

Jedy