To do

Things that need doing

Build System

• figure out a wscript file and instructions that will run on "osx" and "linux"
• properly describe dependencies for building (i.e. mapserver binaries + headers)

API Design

• need to decide on what objects, properties and methods will be exposed
  • property accessors vs functions
    • the semantics of using properties to change values like map.width should be such that changing them does not change other parameters
    • the semantics of using methods implies internal changes
    • properties that rely on a computation based on other properties (such as cellsize, scaledenom) should be read-only

Code Structure

• create a src/ directory to hold the c++ files
• separate out the various objects into separate files and headers instead of a monolithic bindings file
• consider the possibility to move some functionality into mapserver.js and have it use the lower level methods on objects exposed through the bindings (might be easier to do some calculations for things like zoomToScale, setExtent)

Documentation

• keep it up to date!

Examples

• decide what examples would be good to include

Tests

• should we invest in a more serious test infrastructure or just continue to add to tests.js?