Forked WebQuake supports Async IO about webquake HOT 8 OPEN

Hi efess. I forked your fork, and used/re-enabeled audio context API because audioelement.clone() was causing crashes on chromebooks. https://bitbucket.org/kzahel/webquake

Great work with your fork, love your work with promises. I was able to extend it as necessary. I wasn't a fan of promises until now

Also added gamepad support
And fullscreen setting in options

Basically I am trying to get it working well in a chrome app: https://github.com/kzahel/WebQuake-Chrome

from webquake.

Cool, although I wonder how much the excessive use of promises affects the performance.. I was going to try testing with bluebird promises, but never got around to it. Some of my promise implementations were pretty hacky as well.

from webquake.

99% of those promises are initialization code, and arent used at all in the game loop. so not at all, really.

No idea what bluebird promises are :-) is that an ES6 thing?

from webquake.

I'm just right now trying to Promisify the Server initialization code. Using your work as a reference :-)

from webquake.

Oh yea the game loop definitely uses promises, the program code creates a promise even when one isn't necessary.

I was working in my local copy to optimize and cut down the creation of promises when not needed, but there's some loose ends I haven't been able to figure out (or had time)

Bluebird (http://bluebirdjs.com/) is a faster promise implementation, but it comes at the price of needing to import a library.

from webquake.

Cool. Well please let me know if you make any nice changes!

from webquake.

I had another approach that I tried which was to use "await"
I ended up having still some problems with the loading and would get funny exceptions when a new map loaded. But it mostly worked, and didn't require a lot of rewrite
kzahel@8bb479f

from webquake.

Awesome stuff!

This issue can be closed, #33 is there and a PR is in order I think.

from webquake.