Am Mittwoch, den 23.09.2009, 11:32 +0300 schrieb Jussi Kukkonen: > Conceptually I liked the idea of a small client that runs as a service > and starts "polling" syncs and takes care of notifications. Practically > it may make more sense to keep the dbus server running... Especially > with EDS-change-based syncing in mind. My only real worry is the > constant memory consumption, but I readily admit my ignorance in this > subject: You guys will be much better at deciding this than I am. > > Whoever starts these automatic syncs should also take care of notifications.
I also like this very idea. This is basically what my idea with Genesis was about: Have a small app that is running in the session, handling automated and manual syncs, and notifying about changes. The configuration thing I added to Genesis later on was meant to take the pain out of configuring SyncEvolution. This is now mainly redundant in Genesis, because sync-ui makes a good job here. If SyncEvolution would also include a small autosync and notification app, this would cover the current use case of Genesis. I think it really makes sense to have all in one place and to develop sync-ui and SyncEvolution together. If Genesis’ days were counted because Upstream develops a superior solution, I wouldn’t be sad. I just would like to know if this is where you’re heading. > > We probably want some kind of very simple notification mechanism (number > > of changed items, sync failed). We can use the normal Linux desktop > > notification mechanism for this and/or ask the Moblin designers how they > > want to have this handled. > > desktop notifications is what they want. This is vaguely covered by the > wireframes. I might even go as far as drop all change numbers and just > say "Synced with Google"... > > The notification rules for moblin are (from memory): > * there will be a "Dismiss" button automatically > * there can be one additional button, for us that would probably > be something like "Details" and it would open sync-ui. If sync-ui and that notification client are not exclusively meant for Moblin, one should think about the different notification implementations. Ubuntu removed the Actions (i.e., those additional buttons) from the notification system. This is, as far as I know, in line with the spec, but one should then poll for the implementation capabilities, and slightly adjust the notification. Cheers, Frederik _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
