I would disagree with that reasoning. Sure it's produced by academics, but this is the USERS list. And it is fundamentally a practical tool, not an academic exercise as you suggest. The fact that we are discussing it on this list means that usability is a serious concern.
<br><br>Although I might not disagree with the conclusion, the language itself certainly can and should be improved. I would say that standardizing the Ugen / Instrument interfaces should be high on this list.<br><br>-- Chris
<br><br><div><span class="gmail_quote">On 8/16/07, <b class="gmail_sendername">mike clemow</b> <<a href="mailto:gelfmuse@gmail.com">gelfmuse@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I totally agree that there should be some more effort put toward<br>allowing users to create more Ugens, however, I think that because<br>Chuck is also an academic exercise for the Princeton folks, adding<br>features to the language itself is a higher priority than adding more
<br>instruments, IMHO.<br><br>Mike<br><br>On 8/16/07, chris beck <<a href="mailto:render787@gmail.com">render787@gmail.com</a>> wrote:<br>> To me, it seems like the most important thing is to add more preset<br>> instruments and make it easier to create your own instruments. At the
<br>> moment, we have a pretty broad set of instruments, but it could certainly be<br>> expanded. Also, the interfaces to them are not entirely standardized. The<br>> concept of an instrument could be abstracted more within chuck, which would
<br>> be an asset to the programmer.<br>><br>> Just my 2 cents,<br>> Chris<br>><br>> On 8/15/07, joerg piringer <<a href="mailto:joerg@piringer.net">joerg@piringer.net</a>> wrote:<br>> > Kassen schrieb:
<br>> > > I agree a include statement/dependency finding should be at the top.<br>> > > This will not only open the way for easier management of larger projects<br>> > > but it will also allow for easy sharing of tools and extentions which
<br>> > > would be good for community building. Practically speaking it would<br>> > > lower the treshold for contributing to ChucK from knowing C++ to knowing<br>> > > ChucK which I think is a big deal.
<br>> ><br>> > and ah yes! i forgot a very important issue:<br>> > EXTERNALS!<br>> > i have a couple of ideas that could be easily implemented with external<br>> > dlls or dynamic libraries. like for example text to speech (flite) or an
<br>> > openGL display.<br>> ><br>> > best<br>> > joerg<br>> ><br>> > --<br>> > <a href="http://joerg.piringer.net">http://joerg.piringer.net</a><br>> > <a href="http://www.transacoustic-research.com">
http://www.transacoustic-research.com</a><br>> > <a href="http://www.iftaf.org">http://www.iftaf.org</a><br>> > <a href="http://www.vegetableorchestra.org/">http://www.vegetableorchestra.org/</a><br>> > _______________________________________________
<br>> > chuck-users mailing list<br>> > <a href="mailto:chuck-users@lists.cs.princeton.edu">chuck-users@lists.cs.princeton.edu</a><br>> ><br>> <a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-users">
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users</a><br>> ><br>><br>><br>> _______________________________________________<br>> chuck-users mailing list<br>> <a href="mailto:chuck-users@lists.cs.princeton.edu">
chuck-users@lists.cs.princeton.edu</a><br>> <a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-users">https://lists.cs.princeton.edu/mailman/listinfo/chuck-users</a><br>><br>><br><br><br>--<br><a href="http://shadowofaculture.blogspot.com">
http://shadowofaculture.blogspot.com</a><br>_______________________________________________<br>chuck-users mailing list<br><a href="mailto:chuck-users@lists.cs.princeton.edu">chuck-users@lists.cs.princeton.edu</a><br><a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-users">
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users</a><br></blockquote></div><br>