You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The code view was a) distracting, b) took up a lot of screen real estate, and c) provided code which was incomplete and could not be run separately from Waterbear. The current goal is to provide a code export which can be run as needed, although I realize now there is no issue for that (well, now there is: #1309 ). It will be tricky because we don't generate a script and run it anymore, we actually walk the blocks at runtime and call attached functions, which gives the system some interesting properties for debugging and visualization.
For the local server requirement, Waterbear mostly works just by opening playground.html in a browser. Some things might not work (loading things from remote servers) which is why we recommend running it in a local web server. There is issue #371 for making it easier to start a webserver, although for most systems starting a web server is a one-liner, so we haven't made this a high priority.
The current build appears to not have any option to show the underlying JS code. Is that intentional?
Also, to run locally it appears that you must install and run a web server. Is that really needed?
The text was updated successfully, but these errors were encountered: