Redrawing the line between PCU and MCU
some projects
- teaching: kits for classes
- installations for crowds
- working with obsolete parts
- ambidextrous magazine
research
Sketching 06 - design/test/analyze process for prototyping - getting feedback from tools you use to prototype
Exemplar - demonstrate/edit/review process for generating high-level interaction rules through programming by demonstration
"the best way to have a good idea is to have lots of ideas"
- sketching from elaboration to reduction: we are either widening our scope or narrowing our scope - but it's a fractal pattern occurring throughout the process
- so you can explore a design space really quickly
- good for communicating ideas to clients
- keeping things honest, so that you can make sure that testers aren't just giving you what they want
keeping multiple alternatives open
- exists for graphic representation, but not so much for interaction
- Juxtapose: experimentation with experimentation and alternatives for hardware/software
- so that you can switch back and forth between multiple versions in a runtime environment
- automatically building sliders to control parameters on desktop during runtime
- and tabs to control which program is running
- instead of compiling a program you actually compile the code along with a table that maps variables to a control interface
- tradeoffs: you lose
no more zombie prototypes
- the hardware is in place, but you don't have the software left
- $8 to avoid - add storage to the microcontroller
- plug the desktop to a usb hub, which is connected to a flash drive and to the arduino
- this can be miniaturized to a shield
- you could also keep the entire development environment on your project
Conversation
- where to site runtime controls?
- embed in IDE?
