The aim of the Chessie project is to create tools for creating CSound orchestras. Like a lot of the work here, its very experimental — a learning exercise.
Why does the world need another CSound editor?
It might not. But when I’m editing .orc files, I can’t help think of how powerful programming tools like eclipse or even NetBeans are in contrast to the existing alternatives for CSound. At the moment —and please forgive me if I’m overlooking something —there are a number of choices when it comes to CSound orchestra editors with productivity features including syntax coloring and fully graphical editing.
I guess I’m looking for something in between. Something like code-completion (Microsoft calls it what, Intellitype?) that has awareness of the context beyond the current orchestra statement.
The first task I’ve chosen is to create an XML schema that can be used to describe orchestra opcodes. With this schema, I created a little bit of java software to parse the CSound manual DocBook XML sources and create an XML file containing the essential information about the opcodes in a more useful structure.
At present, the following are available
Because its the word that popped in my head when I tried to find something starting with the letter ‘C’ and not used by any other projects. Very limited research in to this name did uncover:
- a monster that lives in the Chesapeake Bay
- a defunct rail road system
- a porn star