Menu
▾
▴
opensync-devel
|
From: Juergen L. <jue...@gm...> - 2009-05-20 17:09:38
|
Hello, I have adjusted the multisync-gui-0.91 code to the new API (0.3x/0.40), mostly copying the code from osynctool/tools/osynctool.c. A few parts may still be oriented towards the old API, but as far as I can see the GUI should now work fully with the new API. I have also introduced the error handling as usual in libopensync and modified this and that. The user can click at - add/remove groups - add/remove members of groups - edit a group configuration - edit a member configuration - which objtypes should be disabled, - which objtypes should be synchronized in a "slow-sync" manner - whether the merger feature should be enabled, - and the converter, and - whether or not he wants to accept the forecast summary (as in osynctool.c) The configuration itself is nothing else but editing the XML file in a textview widget. There's is still quite a lot of output to text console, as soon as it comes to the synchronization. Mabe in the future there could be added a widget dedicated to logging purposes. Currently I have not changed the file names and the function names. The resulting binary is right now called "opensync-gui". If anybody has a better idea for the program name, I am open to all kinds of suggestions. Maybe "osyncgui", or "osynctool-gui", "gosynctool" or whatever. At least eventually I would like to change multisync.(c|h|glade) to a new name. BTW: Who were the original authors? I would like to add a proper copyright notice to each file at the top, but not without mentioning them. Bye, bye Juergen |
|
From: Daniel G. <go...@b1...> - 2009-05-28 14:04:16
|
On Wednesday 20 May 2009 07:09:07 pm Juergen Leising wrote: > Hello, > > I have adjusted the multisync-gui-0.91 code to the new API > (0.3x/0.40), mostly copying the code from > osynctool/tools/osynctool.c. A few parts may still be > oriented towards the old API, but as far as I can see > the GUI should now work fully with the new API. I have also > introduced the error handling as usual in libopensync and > modified this and that. > > The user can click at > - add/remove groups > - add/remove members of groups > - edit a group configuration > - edit a member configuration > - which objtypes should be disabled, > - which objtypes should be synchronized in a "slow-sync" manner > - whether the merger feature should be enabled, > - and the converter, and > - whether or not he wants to accept the forecast summary (as in > osynctool.c) Pretty cool! > The configuration itself is nothing else but editing the XML file > in a textview widget. Actually frontends should never ever touch directly files in ~/.opensync/ directly instead use the OpenSync API - in this case OSyncPluginConfig API. > > There's is still quite a lot of output to text console, as soon > as it comes to the synchronization. Mabe in the future there > could be added a widget dedicated to logging purposes. That would be cool. Please also give us feedback for future OpenSync API design for proper error handling and stuff like that - to avoid the use simple printfs() like in multisync today.... > > Currently I have not changed the file names and the function > names. The resulting binary is right now called "opensync-gui". > > If anybody has a better idea for the program name, I am open > to all kinds of suggestions. Maybe "osyncgui", or > "osynctool-gui", "gosynctool" or whatever. > At least eventually I would like to change > multisync.(c|h|glade) to a new name. I'm very name in giving naming - but why not keep the name "multisync"? "opensync-gui" might give a wroong impression that there is only one GUI :P And i wouldn't base it on "osynctool" .. since osynctool is just a quick and dirty opensync application as reference implementation for opensync based applictions. Not intended for end-users ... just for developers and advanced- testers... > > BTW: Who were the original authors? I would like to add > a proper copyright notice to each file at the top, but > not without mentioning them. Daniel Friedrich ported it to the early 0.3x API. Btw. where do you want to host the projects? Currently we have the problem that opensync.org is maintained by one single person. And to avoid an increasing BUS-factor it might be a better idea to import your project to a different FOSS project hoster - instead of OpenSync.org. If you like i can send you a full copy of the original Subversion repository so you can keep the entire History of MultiSync. Thanks for your contribution! Best Regards, Daniel -- Daniel Gollub Geschaeftsfuehrer: Ralph Dehner FOSS Developer Unternehmenssitz: Vohburg B1 Systems GmbH Amtsgericht: Ingolstadt Mobil: +49-(0)-160 47 73 970 Handelsregister: HRB 3537 EMail: go...@b1... http://www.b1-systems.de Adresse: B1 Systems GmbH, Osterfeldstraße 7, 85088 Vohburg http://pgpkeys.pca.dfn.de/pks/lookup?op=get&search=0xED14B95C2F8CA78D |
|
From: <Juh...@ik...> - 2009-06-01 11:45:38
|
On Thu, 28 May 2009, Daniel Gollub wrote: >> names. The resulting binary is right now called "opensync-gui". >> >> If anybody has a better idea for the program name, I am open >> to all kinds of suggestions. Maybe "osyncgui", or >> "osynctool-gui", "gosynctool" or whatever. >> At least eventually I would like to change >> multisync.(c|h|glade) to a new name. > > I'm very name in giving naming - but why not keep the name "multisync"? > "opensync-gui" might give a wroong impression that there is only one GUI :P > > And i wouldn't base it on "osynctool" .. since osynctool is just a quick and > dirty opensync application as reference implementation for opensync based > applictions. Not intended for end-users ... just for developers and advanced- > testers... How about calling it gsync, gosync, go-sync? Or gnome-sync? I never really liked the kitchensync either. It tries to be funny but probably doesn't open up to majority of target audience. But it might be a good thing give a tiny hint about the environment where the tool is optimized imo. Nowdays those toolkits can be made to look very alike and thus it might be easier. Tuju -- Varo hattup??si??autoilijoita. |
|
From: Michael B. <mb...@gm...> - 2009-06-01 14:07:34
|
On Mon, Jun 01, 2009 at 02:45:20PM +0300, Juh...@ik... wrote: > How about calling it gsync, gosync, go-sync? Or gnome-sync? gnome-sync exists already, gsync sort of treads on the glib namespace (gio, gsocket, gthread) Michael |
Thanks for helping keep SourceForge clean.
X