Home

Systems Thinking

Wait, isn't "Systems Thinking" about nature? The short answer: no. abaaso was created around the paradigm of "Systems Thinking", and that's why its drastically different than most libraries & frameworks. abaaso doesn't try to make animating something on screen easier, it's job is to provide a light weight application framework, which in turn makes API consumption & data display as easy as possible. It's part of the "feedback loop" or "negative loop", relying on the Server for reconcilliation of an action or event.

Representational State Transfer

Hypermedia As The Engine Of Application State (HATEOAS) can be enabled by setting abaaso.state.header to a custom HTTP header, which triggers stateful binding. Listeners for all states must be set before the initial URI is retrieved (on "init" is ideal). URIs are treated as Objects via String representations, so the HTTP verbs are available as methods, including jsonp(), if you choose to enable syntactic sugar with abaaso.sugar().

Application states can be triggered by setting abaaso.state.current.

Tutorials

• Creating an AJAX request
• Creating an event listener
• Creating a data store
• Creating a RESTful data store
• Creating a data list
• Creating a data list filter
• Using events
• Using promises
• Using application states
• Iterating an Array
• Iterating an Object
• Using MongoDB for persistent storage