On Wed, 2010-03-17 at 15:46 +0000, ovek(a)arcticnet.no wrote:
Patrick Ohly skrev:
>> I'm using on a nokia n900 and I'm thinking that it would ideallyt be
>> good to have something linked to dbus signals to syncronise a specific
>> time period after the last calendar update. Sort of delayed realtim e
>> syncing. Only mention it because I'm looking at a wrapper to do this.
> We already implemented regular syncs in the core SyncEvolution, much
> like Ove has done for the Maemo GUI (apparently - haven't seen it
> myself) and Frederik did on the Genesis GUI. Sync frequency is
> configurable there. This depends on running the syncevo-dbus-server,
> something that Ove probably doesn't do yet in the Maemo package.
Right, they're still based on 0.9. I'm not aware of any immediate need
for switching over to the 1.0 codebase.
It makes sense to stick to the stable version; we released 0.9.2 exactly
so that users didn't have to updated to a beta to get some of the fixes
However, there are improvements also for the HTTP client mode. At least
one addresses a problem that a Maemo user had: automatic backups consume
less disk space and inodes compared to 0.9.2.
To do period syncs, the Maemo
frontend just hooks into alarmd, Nokia's crond-on-steroids thing.
In fact, running off syncevo-dbus-server would currently be a
disadvantage on a device such as the N900.
Agreed. The current implementation doesn't take advantage of N900
platform specific features. Thanks for your detailed explanation. Long
term we definitely have to incorporate the same features in the core
SyncEvolution, using whatever services will be provided by MeeGo. It
will be interesting to see whether Nokia contributes the Internet
Connectivity Daemon to MeeGo. I'll ping some people...
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.