Open japboy opened 11 years ago
Not sure :( Pepper has no support for USB APIs. Without running a local app (which I wanted to avoid, as this causes additional latency) I'm not seeing how to make things work :(
Ben Vanik http://www.noxa.org
On Tue, Sep 24, 2013 at 3:35 AM, Yu I. notifications@github.com wrote:
How do you think...
http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html
— Reply to this email directly or view it on GitHubhttps://github.com/benvanik/vr.js/issues/20 .
http://blog.chromium.org/2013/10/connecting-chrome-apps-and-extensions.html An alternative to web sockets for bidirectional communication with native code. Might have better latency properties, though probably still worse than NPAPI.
Perhaps a better architecture would be to get the Rift exposed to the OS as a gamepad (comprised of a handful of analog axes), and then just have a drop-in JS library that knows how to make sense out of the data (using the HTML5 Gamepad API)?
I think we should integrate the work done by Cupola...
https://github.com/DanAndersen/cupola
To use the chrome USB API. I can't get it to work in os x yet, but still working on it.
That API is only usable by Chrome Apps, not extensions. How would you propose making the data accessible to arbitrary tabs? On Mar 26, 2014 11:54 PM, "Ben Nolan" notifications@github.com wrote:
I think we should integrate the work done by Cupola...
https://github.com/DanAndersen/cupola
To use the chrome USB API. I can't get it to work in os x yet, but still working on it.
Reply to this email directly or view it on GitHubhttps://github.com/benvanik/vr.js/issues/20#issuecomment-38769081 .
Oh I didn't realise. That's a bit of a sticking point. :/
How do you think...
http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html