I would very much prefer to include some plugin libraries that compile on all platforms and are aknowledged as useful, such as the fluid opcodes and the Python opcodes.

If CsoundVST can be got to work on OS X, I would prefer to include that and drop flCsound. CsoundVST does everything flCsound does and more besides. In this case CsoundVST would be renamed so that there is no misleading including that it is _only_ a VST plugin, but is a Python scripting environment and a graphical frontend as well.

But if CsoundVST does not work on OS X I have no objection to dropping it from the standard distribution.

-----Original Message-----
From: Victor Lazzarini 
Sent: Nov 15, 2005 7:20 AM
To: csound-devel@lists.sourceforge.net
Subject: [Cs-dev] Csound 5 Reference Manual

I would like to start discussing a structure for the Csound 5 Manual,
which also might spark the debate on what should be included in the
standard distribution.

My idea is to first put together a lean, but updated and correct,
Reference Manual, excluding most of the user's guide text, which can
be compiled as a separate document. An initial structure for
such manual is proposed as:

Csound 5 Reference Manual

1. Csound Language
         1.1  Frontends
                 1.1.1        Csound command-line program
                 1.1.2        CsoundVST
                 1.1.3        Csoundapi~
                 1.1.4        FlCsound
                 1.1.5        TclCsound
         1.2  Orchestra Language
         1.3  Score Language
2. Csound Utilities
         2.1  Analysis utilities
         2.2  File and soundfile utilities
         2.3  Score utilities
3. Csound Host API
         3.1  The C Language API
         3.2  Language Wrappers
                 3.2.1        Python
                 3.2.2        Java
                 3.2.3        Common Lisp
                 3.2.4        Tcl/Tk
4. Csound Module API

I have included everything that seems to be working on all three platforms
(with the exception of CsoundVST I suppose). In moving towards deciding
what goes in to the standard distribution, I would like to make sure we only
include stuff that works in all platforms. Platform-dependent components,
such as frontends or plugin libraries can be distributed separately. This 
excludes
of course the platform-specific IO modules, for which an exception should
always be made.


Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth 



-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel





-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net