Cottage

Last Updated: September 29, 2012

Home      To Do List      Download      Changelog      Screenshot      Screencast      API Documentation      Tutorial      Demo      Forum

Tweet
 
Cottage is a simple game engine which is implemented on top of HTML5's canvas and audio elements. Cottage aims to be an easy to use library for web-based game development.
 
  • Cottage source code (HTML, CSS, and JavaScript files) are licensed under the term of the GNU Lesser General Public License (GNU LGPL) either version 3 of the license, or (at your option) any later version as published by the Free Software Foundation.
  • Cottage documentation files are licensed under the the term of the GNU Free Documentation License (GNU FDL) either version 1.3 of the license, or (at your option) any later version as published by the Free Software Foundation.
  • Cottage media files (image, audio, etc.) are licensed under the term of the GNU General Public License (GNU GPL) either version 3 of the license, or (at your option) any later version as published by the Free Software Foundation.
Cottage's Patch-based renderer was originally developed based on the code from:
http://www.benjoffe.com/code/demos/canvascape
http://www.benjoffe.com/code/demos/canvascape/textures

Features

These features are currently available in the library: A high-level utility application (Cottage Designer) is also provided. This application can be used to manage and/or edit sound, image, sprite, character, battle-effect, battle-formation, scene, site, world map, and game-rules (entities, mappers, and transition-rules).

Cottage has been tested with most of the major browsers. It should work correctly in Google Chrome 5.x+, Mozilla Firefox 3.6.x+, Opera 10.6x+, and Internet Explorer 9rc+ (with and without IEWebGL). Currently, Google Chrome produces the best result and performance.

Konqueror 4.3.x (with WebKit v527.x rendering engine) may not be able to play any audio. Internet Explorer 9rc may produce erratic layout and/or behavior when running Cottage Designer. Also, the keyboard and mouse sometimes seems to be frozen when running the test applications (the test applications do not respond to any user input). In this case, you will need refresh the page.

Classic Internet Explorer (IE 8/7/older) is not supported.

If you are using Google Chrome, you can start the browser with the command line option --allow-file-access-from-files so that it allows AJAX requests and cross-scripting to local disk and file.

If you are using Mozilla Firefox 5.x and WebGL no longer can load textures from local files, you may have hit a Firefox bug. Try to go to about:config and set the value of security.fileuri.strict_origin_policy to false. Acording to this MozillaZine's Knowledge Base, same directory or sub-directory counts as same origin (even when strict_origin_policy is set to true). However, early releases of Firefox 5 seem to have bugs that causes file:// URIs to be treated differently for WebGL textures than for other things for which same-origin restrictions apply.

Key assigment in the test applications may conflict with the keyboard shortcuts in some