Copyright (C) 2011 - 2015, Olivier Biot, Jason Oster, Aaron McLeod
melonJS is licensed under the MIT License
melonJS is the result of our enthusiasm & experiments with Javascript, and currently features :
- A fresh & lightweight 2D sprite-based engine
- Standalone library (does not rely on anything else, except a HTML5 capable browser)
- Compatible with most major browser (Chrome, Safari, Firefox, Opera, IE) and mobile devices
- Device motion & accelerometer support
- High DPI & auto scaling
- Multi-channel HTML5 audio support and Web Audio on supported devices
- a lightweight physic implementation to ensure low cpu requirements
- Polygon (SAT) based collision algorithm for accurate detection and response
- Fast Broad-phase collision detection using spatial partitioning
- advanced math API for Vector and Matrix
- Tween Effects
- Transition effects
- A basic set of Object Entities (to be extended)
- Object Pooling
- Basic Particle System
- Basic animation management
- Standard spritesheet and Packed Textures (Texture Packer, ShoeBox) support
- A state manager (to easily manage loading, menu, options, in-game state)
- Tiled map format version +0.9.x integration for easy level design
- Uncompressed Plain, Base64, CSV and JSON encoded XML tilemap loading
- Orthogonal, Isometric and Perspective tilemap support
- Multiple layers (multiple background/Foreground, collision and Image layers)
- Multiple Tileset support
- Tileset Transparency settings
- Layers Alpha settings
- Rectangle, Ellipse, Polygon and Polyline objects support
- Tiled Objects
- Flipped & rotated Tiles
- Dynamic Layer and Object/Group ordering
- Dynamic Entity loading
- Shape based Tile collision support
- System & bitmap fonts
- Mouse and Touch device support (with mouse emulation)
- Built-in support for cocoonJS
- Asynchronous messaging support (minPubSub)
- some basic GUI elements
- a customizable loader
For your first time using melonJS, follow the tutorial here.
When starting your own projects, checkout the boilerplate
Note that due to the cross-origin request policy implemented in most browsers
(that prevents from accessing local files), you will need to either disable this
security check (see the tutorial), or better use a "personal" local web server
like the grunt connect
task that is used for building melonJS (see below for building melonJS).
To build your own version of melonJS you will need to install :
Once the Node.js package manager has been installed (using the installer from their website), we need to install Grunt and the Grunt CLI (Command Line Interface), by doing the following :
Open a Terminal or a Commmand Prompt and type the following :
$ npm install -g grunt-cli
then we can install the melonJS required dependencies, by typing :
$ cd melonJS
$ npm install
Once all the above done, we are ready to build melonJS :
$ cd melonJS (if not already in the melonJS directory)
$ grunt
Both plain and minified library will be available under the "build" directory.
Just do the following to actually build the documentation :
$ cd melonJS (if not already in the melonJS directory)
$ grunt doc
The generated documentation will be then available under the "docs" directory
The recommended way to test is to start the connect
server in keepalive mode:
$ grunt connect:keepalive
Then navigate to http://localhost:8889/ in your browser. Stop the connect
server when you are done by pressed Ctrl+C
in the terminal.
To run melonJS tests in node simply run the following:
$ grunt test
This will run the jasmine spec tests with the output on the shell. This is not recommended because tests are run by PhantomJS in this mode, and there are a lot of known bugs and unsupported features in the version of WebKit shipped with PhantomJS.
melonJS uses Travis-CI for automated testing and build uploads. The latest build artifacts can be downloaded from the melonjs-builds bucket.
If you need technical support, you can contact us through the following channels :
- melonJS developer forum
- gitter web chat
- [melonJS wikipage] (https://github.com/melonjs/melonJS/wiki)
For any other non technical related questions, feel free to also send us an email.