-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Port to Node.js #2
Comments
Wow, cool idea! I'll look at it today after work. |
I refactored some browser specific code and now we can start jsgbc-core in the node environment. I think a jsgbc-node package including a cli would be an appropriate solution for NodeOS. You can checkout the new branch v0.5.0 on this repo which includes the recent changes. |
I refactored some browser specific code and now we can start jsgbc-core in
the node environment.
But there will be more work for sound support, because of the use of the
webaudio AudioContext. (Audio should be disabled for now with nodejs)
The controls are an other missing feature in nodejs, but should not be a
huge problem.
Npm has modules for everything :-) There are modules that provides
AudioContext API on top of ALSA (but NodeOS don't support it yet, but
should be easy), and the same for the controls, there are modules for
keyboard low level access and for Gamepad API :-) The trick would be to
give an interface-agnostic core (or maybe using W3C standards) and later do
specific wrappers for each environment.
I think a jsgbc-node package including a cli would be an appropriate
solution for nodeos.
Yes, that would be a great design :-D
|
Now that node-canvas has backends support and would allow to print directly to the screen, it would be nice to have a port of this using a node-canvas instance instead of an HTML5 canvas one (the APIs are the same in purposse) to have this working on NodeOS :-)
The text was updated successfully, but these errors were encountered: