Added a spinner and started working on Sammy routes. It’s actually quite an interesting multi-dimensional design challenge. The in-page routes that I want to handle with Sammy represent “navigation way point” in a session history such that user can conveniently use her browser’s forward and back buttons in a natural way.
Each of these navigatable “way points” is a snapshot of the Schema application’s runtime state that could be meaningfully restored in response to scrubbing the back history timeline.
Taken as a system, Schema comprises many subsystems each of which has state independent of the others. So a way point is kind of like a slice that captures each subsystem state. This is what needs to be encoded into the path after #/ if you’re following 🙂
Anyway, here’s today’s build snapshot of Schema.