Partial support for "Workshops" which define hardware configurations.
Bring in a router and support two routes: /workshops and /workshops/:id. Default to /workshops which shows a list of the workshops to go into. They (currently) go into the same view, but will (soon) configure the blocks based on the hardware in the workshop
Add a crude "Workspace" (different from "workshop"... perhaps better names are appropriate) saving/loading option. Right now, you can save your block configuration. When you start back up, it will restore your saved state. Need to extend this functionality to save and load specific files.
Re-organized the Angular code to use a "components" architecture, which will migrate into the Angular 2.0 router eventually.
Added a watch/livereload gulp task
Note: There is a lot of partial features that need more work. Nothing is broken, just some new features not fully functioning yet. I'm creating this PR so that we don't diverge too much, and other people can work on "workshops" or "workspaces" separately.
Partial support for "Workshops" which define hardware configurations.
/workshopsand/workshops/:id. Default to/workshopswhich shows a list of the workshops to go into. They (currently) go into the same view, but will (soon) configure the blocks based on the hardware in the workshopNote: There is a lot of partial features that need more work. Nothing is broken, just some new features not fully functioning yet. I'm creating this PR so that we don't diverge too much, and other people can work on "workshops" or "workspaces" separately.