Examples
Each example is a walk, typed line by line, that ends in something you can watch happen. They are sorted by what you need on the desk, the least first. Find the heading that looks like yours: its first lines say how to set up, and what proves you have.
Only a browser
Nothing to install. Each box in the tour of osen holds a machine, in the page: edit one and press Run. The playground is the same machine with its registers and its tree beside it.
A terminal
The command line host: a C compiler, make, git, and a few minutes to
build. Set it up. You have it when a
prompt answers : 23.
- A program leaves one window and finishes in another — two terminals. A line typed at one prompt moves, part way through, to the other, and prints its answer there.
- A line fails at the prompt, and you fix it there — one terminal. A typo stops a program; the prompt keeps the stopped machine; you bind the name, and it finishes.
A terminal and Python
The command line host, and the Python host built beside it.
Set it up. You have it when import ose
works and a machine answers : 23.
- Send data between Python and the command line — three terminals. A message typed at a Python prompt prints at the command line, and one sent from the command line is answered by a Python script.
- A program from Python to the browser — two terminals and a browser tab. A program sent from Python over a WebSocket beeps in the tab, and the tab says when it is done.
Max
Two externals and the objects, built from source as a Max package.
Set it up. You have it when the help
patch’s [o.se] answers a bang with the time.
- The help patches — one per object, in the
package.
o.se.maxhelpfirst: an object that takes instructions as messages, and one named for a program that is loaded when it is made.
A board and a terminal
An ESP32-S3 with PSRAM on a USB cable, a WiFi network the board and the
laptop both join, arduino-cli, and the command line host. Nothing is
soldered. Set it up. You have it when the
board’s terminal prints === ready.
- Talk to a board — the board’s terminal and a prompt. A line typed at the prompt runs on the board, and then a line that starts at the prompt finishes on the board.
- Fix a loop that failed on a board — the board’s terminal and a prompt. A loop on the board reads a name nobody bound, stops, and arrives at the prompt; fixed there and sent back, it carries on with the count it had.
- The browser and a board through the bridge — the board, a prompt and a browser tab. A machine that failed on the board opens in the playground as a tree, is edited there, and goes back as one frame.