2009 300: Difference between revisions

From XPUB & Lens-Based wiki
No edit summary
No edit summary
 
(17 intermediate revisions by the same user not shown)
Line 1: Line 1:
* Resistor sorting "party"?
Starting idea: comparing the algorithmic to the interactive / heuristic.
 
http://www.cybersyn.cl/ingles/cybersyn/index.html
 
Getting data from the "real world".
 
Demo: Motion/PyGame Mixup, Erkki Kurrenyemi (basica + live instruments), Sketchpad, Tap Type Write
(live microphone / volume visualizer?!)
 
(Pipeline thinking, temporal data streams)
 
"Live" output platforms (PyGame, shoebot?, commandline, pd)
 
Basics as "études"
 
* Necessary Tools: sshfs (on Mac/Windows??)
* Networking
* Reich's Clapping Music (as Distributed Arduino?)
* Command-line Video Editing -- Variation movies
 
* [[Review Bits and Binary]] --> connect to arduino? switches?!, or to "magic" numbers like 4294967295, and the mysteries of two's complements?! bits to images


* [[Review Bits and Binary]] --> connect to arduino? switches?!
* [[Exercise in Post-fix vs. Pre-fix]] Scheme / LISP / Logo?
* [[Exercise in Post-fix vs. Pre-fix]] Scheme / LISP / Logo?
* [[ Relational Databases ]]
* [[ Relational Databases ]]
* Simple Web Servers [http://fragments.turtlemeat.com/pythonwebserver.php]
* Simon Yuill's Motion Graphics tutorial: http://www.yourmachines.org/tutorials/mgpy.html


Part of writing your technical plan is to select a day to present a topic. It could be a particular software package, a piece of code, or a technique. The key is that it should be something you would like to learn more about. You need to think of a small "proof of concept", an idea you would like to realize using the given tool. (Important to keep the scale realistic;) In the process of realizing this project, use the wiki page to document your progress. You should:
Some advanced (practical) lessons:
* Packaging python (understanding the install process)
 
== Technical Plan ==
 
Part of writing your technical plan is to select a topic (and evt. a day) to present. It could be a particular software package, a piece of code, or a technique. The key is that it should be something you would like to learn more about. You need to think of a small "proof of concept", an idea you would like to realize using the given tool. (Important to keep the scale realistic;) In the process of realizing this project, use the wiki page to document your progress. You should:
* Create a page on the TD wiki on your topic.
* Create a page on the TD wiki on your topic.
* Include links to the resources you used / found helpful in preparing your presentation.
* Include links to the resources you used / found helpful in preparing your presentation.
* Create a small "proof of concept" demonstration of what you think you might be able to do / make with the given tool / software. As you go about.
* Create a small "proof of concept" demonstration of what you think you might be able to do / make with the given tool / software. As you go about.


* [[Django]] (Alex?)
The idea is to follow a "cookbook" or tutorial model, as opposed to some sort of exhaustive reference. It is import to focus on a particular aspect of interest to you.
* [[FontForge]] (Emanuele or Loredana?)
 
Example topics:
* [[Django]], [[FontForge]], [[Markov Models]], [[Motion]], [[PyGame]]

Latest revision as of 14:00, 24 April 2009

Starting idea: comparing the algorithmic to the interactive / heuristic.

http://www.cybersyn.cl/ingles/cybersyn/index.html

Getting data from the "real world".

Demo: Motion/PyGame Mixup, Erkki Kurrenyemi (basica + live instruments), Sketchpad, Tap Type Write (live microphone / volume visualizer?!)

(Pipeline thinking, temporal data streams)

"Live" output platforms (PyGame, shoebot?, commandline, pd)

Basics as "études"

  • Necessary Tools: sshfs (on Mac/Windows??)
  • Networking
  • Reich's Clapping Music (as Distributed Arduino?)
  • Command-line Video Editing -- Variation movies
  • Review Bits and Binary --> connect to arduino? switches?!, or to "magic" numbers like 4294967295, and the mysteries of two's complements?! bits to images

Some advanced (practical) lessons:

  • Packaging python (understanding the install process)

Technical Plan

Part of writing your technical plan is to select a topic (and evt. a day) to present. It could be a particular software package, a piece of code, or a technique. The key is that it should be something you would like to learn more about. You need to think of a small "proof of concept", an idea you would like to realize using the given tool. (Important to keep the scale realistic;) In the process of realizing this project, use the wiki page to document your progress. You should:

  • Create a page on the TD wiki on your topic.
  • Include links to the resources you used / found helpful in preparing your presentation.
  • Create a small "proof of concept" demonstration of what you think you might be able to do / make with the given tool / software. As you go about.

The idea is to follow a "cookbook" or tutorial model, as opposed to some sort of exhaustive reference. It is import to focus on a particular aspect of interest to you.

Example topics: