orphium/proto/synth/02_next_steps

02_next_steps

dz / orphium / proto / synth / 02_next_steps

Summary

Orphium next steps (and beyond). Thinking about what happens after the initial proof of concept. April 23rd, 2024.

Node Tree

Nodes

prev_steps
content Previous steps
children MVP
parents next_steps

next_steps
content Next Steps
children gesture, grid, ilo_hookup, konilo, light, ortho33, prev_steps

MVP
content Proof-of-concept: MVP C program showcasing serial protocol in C
children serial_commands (serial command API using msgpack)
parents prev_steps

ilo_hookup
content Hooking up to Ilo
parents next_steps

sporthy_code_konilo
content sporthy code in konilo
parents konilo

konilo
content konilo
children save_code_version_control, sporthy_code_konilo, SDL_bitmaps_block_editor
parents next_steps

save_code_version_control
content how to save Konilo code using version control?
children text_to_block_utils
parents konilo

text_to_block_utils
content Text-to-block, block-to-text utilities
parents save_code_version_control

SDL_bitmaps_block_editor
content SDL + bitmaps for block editor
children symbol_driven_interface
parents konilo

grid
content Monome Grid Integration
children symbol_driven_interface
parents next_steps

symbol_driven_interface
content Symbol-Driven Interface
children ortho33
parents SDL_bitmaps_block_editor, grid

ortho33
content ortho33
parents symbol_driven_interface, next_steps

gesture
content Gesture Synthesizer Integration
children gestvm (AKA, name of implementation), TAL_eval
parents next_steps

TAL_eval
content TAL evaluator
parents gesture, serial_commands

serial_commands
content serial commands
children gesture_node, TAL_eval
parents MVP

gestvm
content gestvm
parents gesture

light
content Light control (the "light channel")
parents next_steps

gesture_node
content Gesture Node: a way to hook up syn
parents serial_commands, orphium/proto/synth/01_initial_implementation/complex_maps