#Action!

##Road Map So there are a variety of things that need to be completed for Action! to be ready for primetime. Some of them are basic (getting statemachine working), others are more complex (build tooling for troubleshooting event stacks). I am going to keep them here and make this a living document.

###TODOs before RC 0. dependency resolution integration with state machines 0. Figure out the testing side of event driven FED in Action 0. Revise the destroy function to make it really do what it needs to 0. Figure out how views really work... (https://github.com/twitter/hogan.js) 0. Consider web components

###TODOs generally 0. create a prod branch and a debug branch (prod probably doesn't need the extra weight of the call stack and emitterid stuff)? 0. update documentation 0. example app 0. simplify model set function? 0. make the error output even prettier! https://developers.google.com/chrome-developer-tools/docs/console-api#consoleerrorobject_object

###Done 0. Tooling for troubleshooting events 0. Add events into the error handler 0. state machine support 0. Add emitter IDs to every time an event gets emitted for debugging work 0. Clone/ Deep Copy in the set functions 0. Build out the save function for models 0. ajax resolution/integration for models

We'll use these guys as release names: http://en.wikipedia.org/wiki/List_of_action_film_actors

in order from top left - down the column then on to the next column. If we run out we'll add more names to the list :-)

##Documentation ###Browser Support 0. IE 9+ 0. Chrome 0. Firefox 0. Opera?

###Dependencies There are a few dependencies for Action to be a fully useful framework. They are (with the reasons for them): 0. Zepto, jQuery, or jQlite. (Action uses the jQuery syntax to wrap it's ajax and DOM manipulation) 0. localForage (If you want to use the local cache. It will automatically cache all of your ajax requests in local storage and pull from them all subsequent times they are requested) 0. Handlebars (a templating library)