britgamer wrote:I like the sound of all the data being in JSON. As well as simplifying the dev environment it may also allow the code base to be refactored into a library + a UI. That way it could be used as part of other projects.
Saving past simulations in cookies/localstorage also sounds like a neat solution. We may need to warn users of the limitations of saving this way so they don't think it's saved like the old site.
I do disagree about not using some kind of framework. I've seen forms far simpler than this become a mess without an MVVM library. Perhaps Angular is too heavy (but it was the quickest I have used to get 2 way binding to a form) but there are plenty of others out there
The only reason I would be against using Angular, is because I personally know nothing about it. If there is an angular wizard out there that wants to design a UI, and let me focus on getting the backend calculations working as intended, I'd be all for it.
For now, I'm personally going to work on that aspect, and hope that other things fall in place from other contributors