Wednesday 26th March, 2014
4:00pm to 4:30pm
So let's say you're building an online banking application using Ember and your login process has about eighteen different permutations to get through the next few steps. Oh, and every one of those steps are optional, depend on which steps you've been to previously, and the server's state. Easy, right?
We'll review a tree-shaped state machine implementation of moving around inside of an application along a scripted flow that loads any information it needs from the Ember resolver.
Sign in to add slides, notes or videos to this session