# XRSH gesturemanager onboarding

1. read https://xrsh.isvery.ninja/#Getting%20started
2. clone the repository:

```javascript
$ git clone --recurse-submodules ssh://git@forgejo.isvery.ninja:8222/xrsh/xrsh.git 
$ cd xrsh
$ ./make dev    # this will aid in running an https server (otherwise run your own)
```

3. read about prototyping: https://xrsh.isvery.ninja/#Prototyping%20things%20in%20WebXR
4. read about packages: https://xrsh.isvery.ninja/#%F0%9F%90%B5%20What%20is%20a%20package%3F 

> **developer w/laptop rule**: in case of doubt, code AFRAME straight into the repo's `src/index.html` for quick testing. You can later refactor things into an [XRSH package](#%F0%9F%90%B5%20What%20is%20a%20package%3F) or [executable](#Distributing%20XRSH%20executables)

# importing files

1. option A: add new files to package.overlayfs.zip to expose it to the iso-image during pageload
2. option B: run 'upload' in the ISO-image to upload a file

# running commands via AFRAME component

1. read https://xrsh.isvery.ninja/#Unixy%20Javascript%20Interface (the bottom: Javascript to (WASM) terminal API)
2. run `cat /root/bin/enter-ar` to see how easy it is to script from terminal-to-AFRAME
3. as a test, run this in the javascript browserconsole of https://127.0.0.1/src/index.html:

```javascript
// potential aframe component (gesturemanager e.g.) executing 'ls -la' via event
document.querySelector('[isoterminal]').emit("send", ["ls -la\n"])
```

> TIP: for simple experiments / AFRAME component-dev work you can also work directly in `src/index.html` of the repo..which is quicker for testing non-ISO-integrated stuff