Since we changed the method signature of Crafty.load, we should warn when people try to use the old syntax.

This adds a new grunt task `grunt api-server` that will serve the api documentation directly from `api.json`.

Use `grunt view-api` to build the docs and then view them in your default browser.

This copies over some scripts from the craftyjs.com repo, but perhaps there's a better way to share them.

…onal placement of tiles with intelligent Z calculation is now in place. Also methods for choosing tile based on pixel and pixels based on tile work better.

We had inconsistent conventions regarding @param and @returns tags

- In some places, the description of the param/return value was continued across multiple lines
- In many other places, the description of the method as a whole was place directly after such tags

While the latter outnumbered the former, I think its useful to be able to have longer param/return descriptions split across multiple lines.  So to allow this while not breaking the docs, this fixes all incidences of the second style.  (This is probably also more readable when looking directly at the source.)

pathfinding

- better support for internal linking
- @warning and @note tags
- In the intial parse, assume that a block of text doesn't end until *two* linebreaks, rather than one, even if its the value of a tag.

I went through and fixed a large number of small issues in our documentation.  This includes typos, formatting problems, and some places where docs were obviously wrong or missing.

Per bower/spec@a325da3

- Fixes a rounding issue when calculating the sign of negative fractions
- Triggers NewDirection in the frame where the direction changes, instead of the next frame
- Renames NewRotation to NewAngularDirection and fixes the same issues
- Adds/fixes related tests

Add some in-line documentaiton, and tweak the wording of the API docs for the Motion component

Instead of adjusting the speed based on the frame rate, try to saty in sync with the game clock by using frame.dt.  Note that speeds are in pixels per second.

This is a breaking change, because it changes how we interpret speeds.  (Pixels per second instead of pixels per frame.)

"Jumpway" is probably a bit confusing, even though it kind of makes sense in the context of Twoway and Fourway.

…mondIso

…mondIso

…mondIso