- From: onyx labo <onyxtechlabo@gmail.com>
- Date: Mon, 28 Oct 2013 23:02:13 +0900
- To: public-sysapps@w3.org
- Message-ID: <CAEHJ6f=6H5rpiejkbakj-_5Tp76bdui0+O2boM3OyLWc+CH-yA@mail.gmail.com>
Hello, I reviewed this specification and have some questions. This specification mainly defined the 3 events at "5.2 The ApplicationLifecycle interface". It's a simple definition I think, but not enough to manage the web application on the mobile terminal. At the view point of the chipset side, it's enough to manage only 3 events. In the case of the mobile terminal, we - application engineers - encounter the screen sleep, network changing (Wi-Fi, LTE, 3G, GSM and no connection), low memory and so. For example, we need to execute the data saving into the storage (temporary backup against the unexpected memory free), set the another behavior (disable the menu user can't select it at the specified terminal status) and garbage collection (improve the application performance) at this time. I propose to add the following events at least: - onSuspend() : when the screen sleep, we need to save data and stop the animation. - onResume() : when the screen is displayed, we need to refresh it and start the animation. onyx
Received on Monday, 28 October 2013 14:02:43 UTC