Table of Contents

txo0m workshop

workshop_notes from the Project Txoom workshop, feb.02002 - f0am brussels

still needs to be refactored into topics, rather than sequentially + extended

day 1

tgarden 2001 developers evaluation

we have examined the TG documentation recorded in Linz and Rotterdam - participant's feedback, playspace recordings and developers feedback, discussed glories and downfalls, summarised suggestions for future development.

day 2-4

txOom -> TGarden

“negative feedback: feedback that tends to stabilize a process by reducing its rate or output when its effects are too great”

the tgarden has a very wide (vague?) scope, and part of the rationale for creating another project along similar lines is to focus on certain aspects which were not adequately developed as part of the tgarden. it is also an attempt to learn form the mistakes of the tgarden development cycles, while benefiting from the work which has (and is) being put into its development.

the (re)focii are →

design guidelines

(recycling) “allows the same materials to be transformed from one object to another, such that the materials begin to move into media, that are consumed as a form of nutrition…. the body expands, the environment is brought inside… space gets reconstituted, architecture is what you swallow… ”

these keywords were triggers for a series of discussions on motivations + aesthetic directions

objectives

design suggestions

architecture

media_architecture

component systems

the component systems need to be integrated closely (ex. alexander's horned sphere), and developed with a very tight feedback between the developers involved

all component systems should evolve through state space (yon's dynamics engine) - this will improve the immersion and the involvement of the players

connections/transitions: media+matter synaesthesia

short/middle term solutions

software

media systems

room_logic (aka 'oz')

sensing

body sensing

position tracking

hardware

recording

txo0m venues for 2002

torino

short term timeline

March: all component systems development. dependency chart and deadlines will be put online in the first week of March

April: first two weeks testing, last two weeks Torino

dependencies

tanngets + suggestions

– transcribed + condensed by Nik Gaffney + Maja Kuzmanovic