Sequential introduction of features #12

A la https://twitter.com/utopiah/status/1153390394215997442

Rely on #13 and its helpers (see 1b3332a178 ) e.g. toggleVisibilityAll() then commands e.g toggleVisibilityAllButClass(classname) in a meaningful sequential order.

environment
background with supporting documents
instructions (themselves as executable commands)
issues and gloassiries (as examples of sources)
screenstack (possibly web-url but seems too unstable for demonstration)
dynamic-view (showcasing non linear layout)

Consider also other features that are currently not available as commands, e.g

networked (audio)
external editing (WebSSH or offline via Termux, partly done via #8 )
jxr itself, with e.g adding shortcuts like qs or sa

Could specify another list of actions, e.g https://fabien.benetou.fr/PIMVRdata/EngineSequentialTutorialCommands?action=source instead of https://fabien.benetou.fr/PIMVRdata/CabinCommands?action=source as a URL parameter. Testable as https://fabien.benetou.fr/pub/home/future_of_text_demo/engine/?commands-url=https://fabien.benetou.fr/PIMVRdata/EngineSequentialTutorialCommands?action=source

See enable-components-via-url, disable-components-via-url and commands-from-external-json used with e.g jxr qs a-scene sa glossary 1 after having removed components directly from the scene.

See also https://twitter.com/utopiah/status/1103761443202232320

Virtual and physical warm up exercises, e.g type this sentence or code snippet then repeat with a countdown based on your previous attempt.

Done via 66a0a7923a

This is currently done per experience but could instead be done more generally through a graph of experiences, namely links between previously setup commands-from-external-json (and all the different options available via getUrlParameter() e.g background).

This means that a starting example here with very basic commands, as suggested by this issue would upon completion (either with an explicit one, e.g warmup() in 66a0a7923a or request by the user or timeout) load the sucessor in the graph.

See also https://www.pmwiki.org/wiki/PmWiki/WikiTrails

By default enable-components-via-url and disable-components-via-url should be interactable in order to show/hide all components that can be played with, an exhaustive menu.

Consider also how a computational notebook could be a starting point, see #69 and with a bit more details https://twitter.com/utopiah/status/1600442418490331136