Quake2 on HTML5, no plugins
A message appeared in the Google Web Toolkit blog that Google developers were able to tie Quake2 (or rather, Jake 2 project - java port) to GWT.
The following technologies were used: WebGL, Canvas API, html5-tag audio, Local Storage API and WebSockets.
In order to get Jake 2 to work with GWT, I had to make some improvements:
- Rewrite rendering under WebGL.
- Transform work with the network (for multiplayer games) from UDP to WebSockets.
- Make all resource loads asynchronous.
- Make the implementation of Java NIO buffers in GWT using WebGL arrays.
- Implement a simple file system emulation for saving games.
')
Currently only Webkit Nightly Builds (Mac OS X) and the Chrome Development Branch are supported.
Project website: quake2-gwt-port
UPD : As I see, this can be run on AppEngine. If suddenly someone will deploy this application there and test it, then tell me pliz how much it is all loaded, how much prots / traffic / etc. consumes. And that is interesting, but at the very time it is not at all.
The following technologies were used: WebGL, Canvas API, html5-tag audio, Local Storage API and WebSockets.
In order to get Jake 2 to work with GWT, I had to make some improvements:
- Rewrite rendering under WebGL.
- Transform work with the network (for multiplayer games) from UDP to WebSockets.
- Make all resource loads asynchronous.
- Make the implementation of Java NIO buffers in GWT using WebGL arrays.
- Implement a simple file system emulation for saving games.
')
Currently only Webkit Nightly Builds (Mac OS X) and the Chrome Development Branch are supported.
Project website: quake2-gwt-port
UPD : As I see, this can be run on AppEngine. If suddenly someone will deploy this application there and test it, then tell me pliz how much it is all loaded, how much prots / traffic / etc. consumes. And that is interesting, but at the very time it is not at all.
Source: https://habr.com/ru/post/89731/
All Articles