Can't use oboe in HTML5 web worker about oboe.js

[jimhigson]

Ah yes, this certainly worked in the past and looks like a bug. As a quick
workaround you could try loading the node version (although this requires
browserify) but should really be fixed.

Would you be able to make a PR? Should be fairly easy to find where window
is being used and make it optional. Off the top of my head, I imagine this
is the CORS code.
On Tue, 27 Jan 2015 at 15:50, ScreenDriver [email protected] wrote:

Is there a chance to use oboe in a HTML5 web worker? If I try to load use
it I get a

ReferenceError: window is not defined

because in web workers you can't access the window object. My JSON file is
extremely large so I can't process all this stuff in the GUI thread.

—
Reply to this email directly or view it on GitHub
#58.

[screendriver]

Hmm I don't know how exactly I should fix it. Here you attach oboe the global window object. But in web workers there is no window object. How would you handle this? Would you make oboe as a global variable?

[jimhigson]

I suspect that the correct way would be (window|self).oboe = oboe; for that
line but I'm on my iPad now so I can't test that.

IIRC, that would work in a normal page or a worker thread.

Could you try and see if it works? If it does make a PR and I'll merge when
the tests pass on travis.

On Wednesday, January 28, 2015, ScreenDriver [email protected]
wrote:

Hmm I don't know how exactly I should fix it. Here
https://github.com/jimhigson/oboe.js/blob/master/src/wrapper.browser.js#L14
you attach oboe the global window object. But in web workers there is no
window object. How would you handle this? Would you make oboe as a global
variable?

—
Reply to this email directly or view it on GitHub
#58 (comment).

[jimhigson]

Fixed in v2.1.1