105
edits
Changes
Jump to navigation
Jump to search
Line 61:
Line 61: − + + +
Features/Automatic activity updates (view source)
Revision as of 14:58, 21 June 2013
, 14:58, 21 June 2013→Scope and implementation
When an update successfully completes, the update time is recorded in the gconf key <tt>/desktop/sugar/update/last_activity_update</tt>. The amount of time that passes before an automatic activity update is executed is defined by the gconf key <tt>/desktop/sugar/update/auto_update_frequency</tt>, units in days, default 0 (which means no periodic update).
When an update successfully completes, the update time is recorded in the gconf key <tt>/desktop/sugar/update/last_activity_update</tt>. The amount of time that passes before an automatic activity update is executed is defined by the gconf key <tt>/desktop/sugar/update/auto_update_frequency</tt>, units in days, default 0 (which means no periodic update).
The gconf key <tt>/desktop/sugar/update/activity_update_mechanism</tt> will specify which update mechanism to use (ASLO or microformat), and the <tt>/desktop/sugar/update/activity_update_uri</tt> gconf key will specify the base server URI to use.
The gconf key <tt>/desktop/sugar/update/backend</tt> will specify which update mechanism to use (ASLO or microformat), and the <tt>/desktop/sugar/update/microformat_update_url</tt> gconf key will specify the base server URI to use for the microformat update backend.
The idea is that the deployer sets the appropriate gconf keys according to his preferences and infrastructure.
The core of the activity update code (src/extensions/cpsection/update/model.py and the backends) will be moved into src/jarabe/model/update, where it will be shared between the activity update control panel, and the automatic background update.
The core of the activity update code (src/extensions/cpsection/update/model.py and the backends) will be moved into src/jarabe/model/update, where it will be shared between the activity update control panel, and the automatic background update.