- From: David Bruant <bruant.d@gmail.com>
- Date: Tue, 13 Nov 2012 16:55:26 +0100
- To: Anssi Kostiainen <anssi.kostiainen@nokia.com>
- CC: "DAP public-device-apis@w3.org" <public-device-apis@w3.org>, Marcos Caceres <w3c@marcosc.com>
Hi, I'd like to get back to the point about step 5 (and step 3 too in a way). I've written a script (or rather a hack) that enables getting the maximum vibration value https://gist.github.com/4066406 What I'm trying to show here is that apps developers can get the info with the current API if they really want. I feel it would be somewhat cleaner to have the implementation exposing the value to avoid hacks (and potentially weird UX at app startup if that's when you run this hack). Also, I have a another piece of feedback. In the 10th step the vibration occur. I feel it should be expressed in some way that these steps are performed asynchronously (that's what triggered my first question in my initial post), because it really looks like they're performed synchronously. David
Received on Tuesday, 13 November 2012 15:56:19 UTC