Re: [SyncEvolution] Announcement: New Mailing list for Genesis development
Hi Patrick!
First, congratulations for your fantastic work with SyncEvolution.
2009/11/6 Patrick Ohly <patrick.ohly_algarroba_intel.com>:
Is there more information available about this application in
English?
The web site seems to be all in Spanish. The reason for asking is that I
want to make sure that SyncEvolution core meets the needs of that app
(assuming that it is used, of course, and not just the Genesis GUI).
I'm sorry, but this webpage is only available in Spanish, because is
more like a showcase with news about free software and Molinux in
general.
There is a forge in https://forja.molinux.info/projects/molinuxsync,
where you can Molinux Sync client (MS). Almost everything is in
Spanish also, but it's a (badly configured) GForge so is easy to find
downloads and SVN repository. MS is basically a Genesis fork, but from
now on I'll try to contribute to Genesis. To begin, I'll implement
back some MS functionalities into Genesis.
When I was working in MS, I missed a way to disable an account without
change the configuration of its origins (addressbook, calendar...
etc.), something like a toggle which control the enabled/disabled
status of the account. Right now it's implemented disabling each of an
account origins.
Another thing I've tried was to support disabled origins in a SyncML
server template. For example, Google only supports addressbook sync;
it would be great if Genesis knew if Google is only able to sync the
addressbook, and disable the unsupported origins. When you load a
SyncML server template, I know if a origin is unsupported if its
'sync' field is equal to 'disabled', so in an "Account Wizard" I
can
disable (sensitive == false) the selection toggle for any unsupported
origin. My first thought was to store 'disabled' in 'sync' field for
unsupported origins, and 'none' if the origin is supported, but
disabled (not synchronized). Then I've realized that SE doesn't
distinguished between 'disabled' and 'none' values, and if you store a
'none' value the next time you load it you'll get a 'disabled' one.
I've read that sync-ui from SE 0.9.1 have added support for disabled
origins; I'll keep an eye out on that.
> Now many improvements, like full account management,
> will find their way back to Genesis.
Does that include using the D-Bus API directly? We are behind plan with
using it in the sync-UI, but the implementation is fairly complete by
now and ready for testing.
No, I used the same syncevolution.py file than Genesis. All I did was
add some functions. It's based in SE CLI client interface.
I registered, just to keep informed. The main list for SyncEvolution
core is still here.
Thank you!! Keep on the good work :-)
Cheers!!!
--
David Castellanos Serrano