Hello!
At the moment, I don’t think I have enough understanding of the D-Bus
thing as to contribute much to the design discussion. But I’ll try
porting Genesis to the D-Bus API, so maybe I will get some ideas during
that process. Until then, I’ll just follow your discussion.
Just some thoughts about automatic syncing:
Am Donnerstag, den 23.07.2009, 23:26 +0300 schrieb Jussi Kukkonen:
> 5 implement automatic syncing
> - sync without user interaction at interval
This is currently implemented in Genesis, using pretty stupid timeouts.
> - sync when local changes happen, if possible
This has been on my agenda for some time, but I never actually
implemented it. It is of course very reasonable only to sync when data
actually changed, but there are some things to think about:
* One can monitor for local changes, but not for remote ones. So I
think it would be good to have a configuration option in the
lines of “sync when local data change, but at least every __
minutes”. That way, one could use a larger interval to look for
remote changes.
* Syncing every time a local change happens might generate quite a
lot of load, for example when editing several entries in a short
time. I think this could be solved using a timeout: After a
local change, syncevolution waits for time x before triggering
the sync. If another change happens during this time, the
timeout is renewed.
* The information about local changes could be used not only for
automated syncs. For example, Genesis could show the information
about changes to the data in the notification area, leaving the
start of the sync to the user.
I think it would be a good starting point, if syncevolution would
implement a D-Bus signal like LocalDataChanged. Then the client could
decide whether to trigger a sync or not. What do you think?
> - libnotify notifications on sync progress/success/failure
> (no notifications when sync ui is visible?)
Genesis currently shows notification about the results of successful
syncs. It used to show a notification in case of an error, containing an
“action” which would show the error log.
The problem with that is that Ubuntu removed actions from the
notifications. Currently, in the case of an error, a dialog is presented
to the user, which is quite obtrusive. I am now thinking about making
more use of the status icon. It could show a modified icon in case of an
error. Clicking the icon would then show the log.
For the progress, I don’t know if this could properly be shown using
notifications. For this, Genesis also uses the status icon.
I don’t know if Moblin provides a notification area and if using a
status icon would be an option for the GTK UI. But for Genesis, I will
try finding a reasonable balance between using the status icon and
notifications.
Cheers,
Frederik
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
