It’s been a little while since the last piece of code made it to github, or a sketch has been drawn up. Nevertheless, a proper first release that’s working and useful would be nice some day. So I began thinking that perhaps I took a too big of a piece to chew. With that, it’s back to square one and rethinking what should be in and what should be out. Here is a step back with a refactoring mentality, along with a working draft of what this tool could be for the first release. Thoughts?
For me the "creation of interaction stories between pages and states" and "sharing of a prototype with someone else" is important, more important than both "working locally or on server" – choose 1 and "moving of work between local setup and server".
Agile would say, choose the most important feature and build that, then the next one, so why not build an ordered list of features and do them one-by-one.
Dojo toolkit would seem to be a better Javascript library to use in this case?
Speaking of citing the op’s post everyone will like this because its correct so its pleasant to see an author thats blogging topics such as this on the internet to review