add url routing - open scripts from browser location url

[artfwo]

and update the location url when a script is opened from the editor.

[ngwese]

i believe implementing this requires the introduction of a "router" (possibly https://reacttraining.com/react-router/) and as a result there are some potentially non-trivial changes to the application to make it work - but definitely doable.

[jlmitch5]

what are all the routes we want?

Ideas:

• /maiden/scripts/:script_name?tree_view_open={true|false}
• /maiden/config

[pq]

@ngwese : what were you thinking about norns docs (api, etc)? some way to read docs inline would be great imo. if we did that maybe another route there?

otherwise, maybe routes for the repl(s)?

[ngwese]

currently the only defined routes are:

url	what
/	redirects to /maiden
/maiden	the actual editor app
/doc	static luadoc generated content served as is, not part of maiden
/api/...	backend support for maiden

the above suggestions for script/... or config would be relative to the /maiden root

as far as how the docs/reference get integrated i haven't thought too far ahead. i don't personally have a strong desire to see a ton of documentation hosted directly from the device for space and for maintenance reasons. i do think it is useful to imagine some level of api documentation integrated into the editor (particularly for the lua code which not directly visible in the editor).

[jlmitch5]

thanks for the clarification (also I'll check out the doc endpoint, didn't realize that was a thing). I've updated my comment.

[ryanlaws]

What are the opinions on this now? Specifically I'm wondering what the static paths would look like. I'm thinking below /maiden there'd just be a /dust, so that e.g. awake.lua would work out to http://norns.local/maiden/dust/awake/awake.lua. For now, we could just handle paths starting with /maiden/dust/.

[ngwese]

Support for script URLs is now in master thanks to @ryanlaws