this is just a proposal of one way the SC engine internals could be structured, in a way that hopefully facilitates an easy division of labor. of course there are many ways to do things. (doesn't need to be classes at all really, but they can be helpful for staying organized, maintaining stable interfaces, and catching errors early.)
i've left out all the critical functionality to be implemented. for now, all i know is that these classes compile.
one next step might be to stub in some placeholder functionality for each component, like playing sinewaves instead of files, and make sure the plumbing is all in order.
adds some supercollider class "skeletons."
this is just a proposal of one way the SC engine internals could be structured, in a way that hopefully facilitates an easy division of labor. of course there are many ways to do things. (doesn't need to be classes at all really, but they can be helpful for staying organized, maintaining stable interfaces, and catching errors early.)
i've left out all the critical functionality to be implemented. for now, all i know is that these classes compile.
one next step might be to stub in some placeholder functionality for each component, like playing sinewaves instead of files, and make sure the plumbing is all in order.