That sounds like a fun challenge. You can use straight html, and include extra js files. I think it might be as easy as adding the form in html in a md file, and then in a js finding those things (in the dom?) and making the connections to code.
Not that familiar with Google Docs, I don’t think you can just get a new instance (easily) when you use it. Google doesn’t seem to make it easy for me to find this out. I could be wrong though.
My initial thoughts is this can’t be that difficult. We’re taking some simple formula, wrapping a web form around and this and then some client side JavaScript. If @jamiek wants some help, I’m happy to put some time in.
I don’t hate the buttons. Mkdocs needs easier tables. But having it all there in the docs is better than multiple places. so I can deal with no extra columns.
That is blowing my mind. You guys are so good at this stuff. Looking though it I understand it, and could probably edit it, but doing it from scratch…would takes days. You guys popped it off on a coffee break from real work.
I appreciate all of you throwing in all the ideas.
I think if the inputs and the buttons had some kind of box around them, we’d be a lot closer. I think it is a few simple css options, I just always get turned around in css files.
I think we can put the javascript in extra_javascript and I bet we are already loading jquery.
I did remove the table tags from Jamie’s version, just because it is a pain in markdown. We could probably put it back into one table. I think there is some fidgeting to make it more clear.
I think we could probably ditch the buttons entirely though.
If we hooked the onBlur or onChange of the workspace boxes to comoute from workspace, and we hooked onChange of the tube lengths to compute from tube length, it would all just update when the user changed something. When they changed tools or model, we would have to just pick which boxes they wanted to keep.
The markdown tables with html inside really do look nasty. And they end up being enormous lines that I can’t break.
I like having all the features in columns, but can I get away with only making the XYZ user configurable, and leaving the belts and stuff as read only text?