These are chat archives for csound/csound.github.io

8th
Nov 2015
Eugene Cherny
@ech2
Nov 08 2015 09:39
I gave the issue a thought and now I agree with Bernt in that we have projects that can be categorized like community-formers, i.e. Cabbage for making VSTs, Blue for composition, etc. They form a kind of infrastructure (sorry, didn't come up a better term) for doing creative things based on Csound. Each of these projects pushes Csound and to some domain, and these projects should be described in the create section. The projects page should list projects made with them.
Rory Walsh
@rorywalsh
Nov 08 2015 09:51
Ok, this is a little clearer now. So we can list any tools for creating things with Csound in the create page, and list projects made with these tools in the projects page. Ok. I'm with you now.
Rory Walsh
@rorywalsh
Nov 08 2015 11:11
I just made a pull requests for the frontends page. Steven will need to add a little something about Blue. I wonder should tools like csoundapi~ and csladspa be listed under frontends? Technically they are, but should we stick with editor type environments?
Rory Walsh
@rorywalsh
Nov 08 2015 11:53
Are direct links to the floss site, reference manual etc a good idea. Or would it be cleaner to link to a page where we provide some info and a link? I find jumping straight to an external site a little abrupt? Thoughts?
Rory Walsh
@rorywalsh
Nov 08 2015 20:05
I've added a few more entries to the Create section. I don't know anything about Python and Csound for the scientific programming section. Can someone else add something there? Also, the projects page is completely empty. Bernt can you add something about Cosmo to get the ball rolling?
Bernt Isak Wærstad
@berntisak
Nov 08 2015 20:05
Yap!