To me, it seems like the most important thing is to add more preset instruments and make it easier to create your own instruments. At the moment, we have a pretty broad set of instruments, but it could certainly be expanded. Also, the interfaces to them are not entirely standardized. The concept of an instrument could be abstracted more within chuck, which would be an asset to the programmer.

Just my 2 cents,
Chris

On 8/15/07, joerg piringer <joerg@piringer.net> wrote:
Kassen schrieb:
> I agree a include statement/dependency finding should be at the top.
> This will not only open the way for easier management of larger projects
> but it will also allow for easy sharing of tools and extentions which
> would be good for community building. Practically speaking it would
> lower the treshold for contributing to ChucK from knowing C++ to knowing
> ChucK which I think is a big deal.

and ah yes! i forgot a very important issue:
EXTERNALS!
i have a couple of ideas that could be easily implemented with external
dlls or dynamic libraries. like for example text to speech (flite) or an
openGL display.

best
joerg

--
http://joerg.piringer.net
http://www.transacoustic-research.com
http://www.iftaf.org
http://www.vegetableorchestra.org/
_______________________________________________
chuck-users mailing list
chuck-users@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users