Closed zya closed 8 years ago
The reason we currently use WebVRConfig is that the polyfill is completely invisible to the developer.
All of the WebVRConfig options pertaining to the boilerplate could be converted to an options array, but then there would be two different ways of configuring.
On Wed, Jan 6, 2016 at 3:15 AM Ehsan Ziya notifications@github.com wrote:
At the moment the config is a global variable WebVRConfig. It would be nicer if you could just pass it in as an argument to the manager. I think this also applies to webvr-polyfill.
var manager = new WebVRManager(renderer, effect, options);
— Reply to this email directly or view it on GitHub https://github.com/borismus/webvr-boilerplate/issues/100.
The polyfill is invisible to the developer and so the developer manages the visible and unusual step of defining a global configuration.
At the moment the config is a global variable
WebVRConfig
. It would be nicer if you could just pass it in as an argument to the manager. I think this also applies towebvr-polyfill
.