Greetings,
I just wanted to let everyone know that I've made significant progress toward creating an environment that will allow developers who want the ability to write desktop games using JavaScript as the primary development language.
JSGameClient is a no-frills JavaScript environment that combines Chrome's V8 JavaScript engine with Physics FS, SFML and Texus' TGUI. The project is part of a series of open source projects I am working on to create a fully modable and open source game development system with all major components licensed under a permissive license that makes it usable by closed and open source developers alike.
Developers that wish to contribute are invited to do so provided that they license their work under a compatible license. Message me if you are interested. I am committed to maintaining this project for the next few years eventually expecting to reach version 1.0 and have a reference engine that can be used to speed up development.
-----
Current Needs:
1. Testing and improvement to support building on Mac.
2. Code to prevent privileged execution of the JSGameClient - given the JSGameClient is intended for writing games there is no good reason to allow it to run as elevated administrator or root.
-----
Website:
http://github.com/StevenChristy/JSGameClientDocumentation available through the readme.md and the docs/index.html
-----
Status:
Version 0.3.2 - Added support for setTimeout, clearTimeout, setInterval, clearInterval, and sleep methods. Added additional documentation including some steps for building under Linux.
Version 0.3.1 - The build system was improved and building on Linux has been tested and works well.
Version 0.3.0 - This is a work in progress and is not ready for production use. SFML and Physics FS (readonly) and a few essential commands.
The latest version fixes numerous bugs and supports building for VS 2010 and MinGW 32-bit.
-----
Development: To debug JavaScript applications it is recommended that one use Eclipse. By linking in the JS files in the jsdocs subfolder one can have context sensitive help while writing JavaScript code under Eclipse. Use the Chrome Developer Tools to try and debug the app as a Standalone V8 application. Uncaught exceptions will generate a full call-stack and the risk of crashing should be minimal. In the event that the application does crash I recommend debugging under Visual Studio 2010 to find the source or you could submit a sample that reproduces the issue and I will chase it down.
-Steven