Am Sonntag, den 16.08.2009, 11:06 +0200 schrieb Patrick Ohly:
> On Sat, 2009-08-15 at 18:34 +0100, Frederik Elwert wrote:
> > since SyncEvolution 0.9 ships with the GTK ui, I just tried it out. But
> > after startup, it tells me that no sync service is configured.
>
> The sync-ui remembers the config that the user has selected for use in
> sync-ui in a sync-ui specific gconf key. I suspect that "no sync service
> configured" really means "no sync service selected" here.
Ok, that makes sense.
> > When I go
> > into the configuration dialogue, it lists my account data for
> > ScheduleWorld, except for the password.
>
> The sync-ui assumes that the password is stored in the GNOME keyring. It
> currently doesn't work well with existing configurations where the
> password is in the config.ini itself. I thought we had an open issue for
> it (I found the same problem earlier), but I cannot find the issue.
> Jussi, did we fix this?
This is of course way better in means of security. Maybe I should have a
look if I can implement this for Genesis as well (if gnome-keyring is
present, I’d like not to depend on GNOME too much). But at least for
Genesis some kind of migration would be necessary: If a password is
present in the config file, delete it there and set it in the GNOME
keyring.
I don’t have any experience with gnome-keyring, so I’ll have to see how
much work this would be. Is it even possible to access passwords across
applications (like Genesis and sync-ui)? How does syncevolution know
about the password then? Does it look for it in gnome-keyring for
itself, or do I have to pass it to syncevolution somehow?
> > This surely is not top priority, but I think it would be nice if one
> > could run sync-ui and Genesis next to each other. So services set up in
> > Genesis should work in sync-ui and the other way around. So could anyone
> > help me find out why sync-ui doesn’t recognise the services I set up
> > with Genesis? Then I could adjust Genesis’ configuration mechanisms to
> > be compatible with sync-ui.
>
> You could use the same gconf key to select the active configuration.
> Then sync-ui should work right away. Have a look at
> /apps/sync-ui/server in gconf-editor.
Ah, that sounds good! It makes sense to store common configuration
options in a common place.
I just have two questions:
* I think sync-ui uses the template name instead of the server
name in that option. For me, it stores "ScheduleWorld" instead
of "scheduleworld", which I used as the server name. This makes
it difficult to store more than one configuration for one server
(which is necessary, e.g., for syncing more than one calendar
with one service). Is this intended?
* In the future, it might be desirable to sync more than one
service at a time. Would it make sense to make that option a
list instead of a string?
Cheers,
Frederik
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
