On Saturday 21 August 2010 01:28 PM, ext Andrew Flegg wrote:
On Sat, Aug 21, 2010 at 08:46, Sateesh Kavuri<[email protected]> wrote:
In my view there is no need to hook into the system scheduler when
all that is required is to track the scheduled sessions (which can
straightaway
be implemented using a simple tracking of the latest sessions to be
triggered).
Implementing a simple scheduler isn't hard. However, using the system
scheduler allows a single point of configuration and modification in
the system to enable use cases like:
* Sync every 6 hours, but only if I'm connected to wifi and on battery.
* Sync every 12 hours, after connecting to VPN connection #1, if not
roaming. Disconnect the VPN afterwards.
Yes, this would be feasible, if there exists a System UI that has options
for settings alarms for various entities, like Sync, Alarms, etc. But
this is more related
to the MeeGo UI concept, something that is worth discussing with the UI
designers.
By having a single point which provides the scheduling it doesn't need
to provide these use cases now, but can be modified to support them
later.
Cheers,
Andrew
--
Sateesh
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
