Issue metadata
Sign in to add a comment
|
Refactor VR implementation to be less Android specific and dependent |
||||||||||||||||||||||||||
Issue descriptionChrome's VR implementation, especially for VR shell, currently only works on Android and is implemented in various android/ directories. We need to generalize as much code as possible so that it can be used on all platforms. This will necessarily involve moving much of it out of the android/ directories. We may also find that some of the implementation is dependent on Android/GVR and need to find generic solutions and/or build abstractions to equivalent functionality on other platforms/HMDs.
,
Dec 28 2016
,
Jan 7 2017
Issue 653182 may be related.
,
Jan 9 2017
,
Jan 18 2017
,
Jan 19 2017
I'd like to help with this is possible. Would an open SDK like OSVR fit in those plans?
,
Jan 20 2017
,
Mar 3 2017
,
Aug 9 2017
Issue 644789 has been merged into this issue.
,
Aug 9 2017
Quite a bit of code has migrated to chrome/browser/vr. This progression will continue naturally, and I believe we can close down this bug.
,
Aug 11 2017
Closing this bug via bulk-edit. This bug tracks future work that is not yet scoped. For maintainability, we are now tracking aspirational future work here: http://go/chrome-vr-backlog In the future, this bug may be re-opened when in scope, or replaced by a new bug if warranted. |
|||||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||||
Comment 1 by sko...@chromium.org
, Dec 17 2016