Structured programs


One Sentence: Whats happening in your workshop?
We will design a nice structure for several sample programs, break it into a library of reusable parts and implement one part, share our personal experience about what should have we done better in past and maybe implement a small sample project.

What 3 tags describe your workshop?
Fast patching, structure, library

In which of the three categories does your workshop fall: beginner, intermediate, advanced

How long will your workshop be?
(Standard formats are 3h or 2x 3h, but other formats may be possible)

Who is the target audience of your workshop?
Patchers desperate from constantly losing track in their programs.
Developers who want to bring readability of their patches to perfection.

What knowledge do you presume your participants have?
Basic VVVV knowledge, some practical experience with making programs for clients is useful.

What will attendees of your workshop learn?
To write their patches easy to read and faaaaster by time. Readability, reusability and structure of your programs are cruicial for fast patching speed. If you gradually build your experience of structured programs, with vvvv you can get to totally crazy programming speed.

What technical requirements does your workshop have (apart from internet and a projector)?
e.g. special hardware, software, graphiccards, materials, dancers/performers
Only a projector.

Who would be the two hosts?
Martin Zrcek

How would the hosts qualify for the topic? (Describe and add links to portfolio website, github, vimeo,… accounts)
Years of payching with programming backgrounds.
Works for focus4 gmbh

Patch optimization techniques