3 ms·
With modern browsers, "completely re-output the entire user interface on every state change" is kinda viable. I recently wrote a trebuchet simulator app (hastin
by QuadmasterXLII 3y ago
With modern browsers, "completely re-output the entire user interface on every state change" is kinda viable. I recently wrote a trebuchet simulator app (hastingsgreer.github.io/jstreb) without a framework. instead I wrote a "rebuild UI" function that I call on every new state, and the user experience is super snappy
- stickfigure 3y agoIt doesn't seem to work at all in Chrome, so maybe not the best example.
- QuadmasterXLII 3y agoAh, global variables in modules have to be declared with var etc in chrome, but firefox and safari let it slide if you just assign. Fixed, but I guess I’m gonna have to set up a test suite
- nightpool 3y agoWeirdly I see that changing the "Projectile" selection to "P3" and then back to the original "P4" made the range drop way down, even though the new value was identical to the old value. But changing the "Main Axel" value made it jump way back up: https://imgur.com/a/boo5Xw3 https://imgur.com/a/boo5Xw3 So maybe some kind of "non-functional"/reused state issue exists regardless?
- QuadmasterXLII 3y agoOh, I don’t like the look of that. This may be a valuable lesson in “I should have just used a framework”