On Sun, Sep 19, 2010 at 7:58 PM, Robin Burchell <virot...@viroteck.net>wrote:
> > Anyway: this was pretty much in keeping with my idea: move it into the task > switcher (hildon-desktop/other) so that applications which are moved to > background are stopped (unless they signal for whatever reason that they > need to be kept running, but I'm not even sure that is necessary: if > you really need to do background processing constantly, why do it in a > GUI application?) > Hey, continue down that path and you'll be in iOS style cooperative-daemon multitasking in no-time :) Which, while not bad in itself, DOES require a substantial level of effort on part of the developer, especially, as mentioned by others, if it's a port using funky event loops. That's why, unlike in the case of iOS I do believe this call is not to be made by *compulsorily* overcomplicated by the OS/daemons in our case. On Sun, Sep 19, 2010 at 1:42 PM, Ville M. Vainio <vivai...@gmail.com> wrote: > It would be more useful if it wasn't a launch wrapper, but rather a > lone daemon that sits in the background and suspends a set of > processes according to given heuristics (e.g. suspend gpodder when a > call is initiated, matched by /proc/NNN/cmdline). > > This would allow suspend rules to be created for apps outside the > packaging/implementation for the app itself. I kinda would say this fits Shepherd's use-case (DBUS suspend/resume event as trigger, SIGSTOP/resume as action), but considering how late I am on that project I better keep quiet :) Best regards, Attila
_______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
