On 4 Jan 2006, at 04:11, James Harkins wrote:
On Jan 3, 2006, at 5:27 AM, tom tlalim wrote:
i'd recommend reading "Streams-Patterns-Events" (you can find reference in Streams help)
it would also be nice if someone could shed some more light here about how to set the arguments to a playing routine/task.
I'm not sure what you mean by "how to set the arguments to a playing routine/task." Routines and tasks don't really have arguments.
sorry. the Routine-new inherits it's args from Thread-new... (func, stackSize)
it's 1st arg, a function, may take args like this:
(
r = Routine { arg inval;
var valuePassedInbyYield;
inval.postln;
valuePassedInbyYield = 123.yield;
valuePassedInbyYield.postln;
}
)
r.value("hello routine");
r.value("goodbye world");
If I may hazard a guess, it sounds very close to the central problem that has animated my coding efforts for the last year and a half. That is, how to create processes you can change from outside while playing them. The environment solution is very much in the right direction. I found that it's risky to keep loose associations of environment variables and tasks or patterns--also, the risk increases the more complex the processes become. So I built a container structure so I can write a prototype that defines all the environment variables that are needed along with defaults, and then you can make as many instances of that prototype as you need.
i guess it was this phrase that scared me off ;)
"A prototype (for now) of a component in an open-ended quasi-artificial-intelligence sequencing technology."
but it looks interesting.
it's interesting this whole design thing. how different interfaces within sc offer different ideas how to do things (ProxySpace for example, OSC messaging style, your chucklib etc.).
Now you have two separate environments, each with its own ~timeisme variable that can be changed independently. I don't have to worry about naming conflicts, and I don't have to worry about forgetting to initialize the variables in performance (assuming I tested the prototype thoroughly!).
can you tell more about what are the advantages over using Events, Environments or JITLib?