How ideo/avocado works
Project type and purpose
• This is an open-source plugin library (Avocado) for Quartz Composer (QC) / Origami.
• It provides a suite of ready-to-use “patch” bundles (.plugin) that extend QC’s interactive prototyping capabilities (interactions, Bluetooth, animations, global values, utilities).
• It ships with example compositions (.qtz) and Arduino sketches to demonstrate usage.
Main components
a. Quartz Composer Application (host)
b. Origami Framework (plugin extension layer inside QC)
c. Avocado Plugin Manager (just the directory of bundles, loaded at QC startup)
d. Avocado Plug-Ins (each bundle in “Avocado Plug-Ins/… .plugin”)
– Interactions (Draggable, Carousel, Bistable, Card, Dial, Master-Detail, Rolodex, Hit Grid, iOS Keyboard)
– Bluetooth Integration (Bluetooth Send, Receive, Connection, Aggregate/Disaggregate)
– Animations (Nod, Pulse, Jiggle, Jump)
– Global Value (Save/Retrieve Boolean, Save/Retrieve String)
– Utilities (Keyboard 2, Delay Value, Gate, Invert, Map to Range, Absolute Value, String to Number)
e. Example Compositions (“Examples/… .qtz”) and sample Arduino code (“Examples/Bluetooth/*/*.ino”)
f. External Services
– Core Bluetooth (macOS BLE stack)
– BLE devices / Arduino boards
Relationships and data flows
• QC launches → loads Origami → scans “Avocado Plug-Ins” directory → dynamically loads each .plugin bundle
• Each plugin registers one or more patches with the Origami runtime
• Inside a .qtz composition:
• Patches are wired together in QC’s dataflow graph → values/signals propagate from patch outputs → patch inputs
• Bluetooth patches invoke Core Bluetooth APIs → connect to nearby BLE devices or Arduino boards (via BLE)
• Global Value patches read/write to a shared store accessible across compositions
• Examples demonstrate end-to-end usage: patch graph + BLE device or UI animation
Architectural patterns / design principles
• Plugin-based architecture: bundles loaded at runtime
• Modular categorization: grouping by functionality (Interactions, Bluetooth, Animations, etc.)
• Dataflow programming model (Quartz Composer graph)
• Separation of concerns: each patch implements a single piece of functionality
• Extensibility: new patches can be dropped into the plugin folder
Essential elements
• Annotations calling out major categories (Interactions, Bluetooth, etc.)
• A boundary around QC to indicate the host process