W3C home > Mailing lists > Public > public-device-apis@w3.org > March 2011

Re: Battery Status Event Spec

From: Robin Berjon <robin@berjon.com>
Date: Thu, 31 Mar 2011 16:48:26 +0200
Cc: Anssi Kostiainen <anssi.kostiainen@nokia.com>, "public-device-apis@w3.org Group WG" <public-device-apis@w3.org>
Message-Id: <2F1FC263-AA75-4F62-8904-7CAC97D4EAE1@berjon.com>
To: "Tran, Dzung D" <dzung.d.tran@intel.com>
On Mar 31, 2011, at 16:14 , Tran, Dzung D wrote:
>> Isn't that what level is for?
> Yes, that is right. However, I don't know it make sense to have both timeRemaining and level. Isn't they kind of represent the same thing. It is hard to accurately calculate timeRemaining. At least on my computer, I noticed that timeRemaining fluctuate and sometime it gave me something like 4hr 20mins then later it gives me 4hr 32mins. 

It is certainly true that timeRemaining is hard to calculate, and will necessarily fluctuate as the activities you perform on your computer change. I think that it should be optional (I don't think that all platforms support it) but that it should be exposed if available as it is even harder for an application to evaluate it than it is for the system.

-- 
Robin Berjon - http://berjon.com/
Received on Thursday, 31 March 2011 14:48:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:18 GMT