- From: Kihong Kwon <kihong.kwon@samsung.com>
- Date: Thu, 01 Sep 2011 17:09:45 +0900
- To: public-device-apis@w3.org
- Message-id: <004901cc687e$82f40560$88dc1020$%kwon@samsung.com>
Dear. DAP members.. Hi. This is Kihong Kwon who is a code contributor of battery status event spec to the webkit So far I had done the implementation for webkit EFL port and demo application in according to this spec. but unfortunately I didn't apply latest version of spec(31th August version) to my implementation. It works fine, and the battery status seems to be quite useful for web-apps. I will open it as soon as I get a grant from company. I have some questions about recently changing. 1. I think if web-app developers could configure batterylow and batterycritical level, it would be better. Some web-apps doesn't want to use low and critical level from device. - For example, In case of online RPG game, the exp. point and items in the game are really important to the almost of gamers. Even better we expected. Device must not be turned off during the playing time. If device is turned off suddenly, user would be very upset. Therefore I guess it would be great, if game maker can handle batterylow level and batterycritical level based on the characteristics of their application. E.g. batterylow level = 30% and batterycritical level = 15%. 2. Yesterday, I looked at the batteryok event as a new event in this spec. When this event is occurred? The meaning of this event is not clear to me. In addition, I don't think batteryok event is required for this spec. I think just to have "ok" value in the state property of BatteryStatusEvent is enough. What do you think? BR. Kihong.
Received on Thursday, 1 September 2011 08:10:45 UTC