| Yes it's actually a nice idea. Doing it direct from the examples
directory is fairly straightforward, however, it would be better to
parse the opcode entries to have a categorized list rather than one
long list. I don't think it will be hard, so I'll try to do it when I
get time.
Cheers,
Andres
On 10/9/09, Felipe Sateler wrote:
> I believe in the manual source all the examples are in csd form. So no
> need to parse anything.
>
> On Fri, 2009-10-09 at 09:24 -0400, Dr. Richard Boulanger wrote:
>> It sure would help us all know which opcodes have fantastic and
>> inspiring csd files and which need work! It would be like the great
>> max helpfiles and would be a huge help - even just as a menu of csds
>>
>> Sent from my Radio Baton ;-)
>>
>> On Oct 9, 2009, at 9:09 AM, Rory Walsh wrote:
>>
>> > Don't shoot me Andres but wouldn't it be possible for QuteCsound to
>> > parse the manual and dynamically create a menu with all the examples
>> > in the manual itself. In fact that would be some 1000 examples or so,
>> > might not be the best idea after all, that would be some doozy of a
>> > menu!
>> >
>> > 2009/10/9 Dr. Richard Boulanger :
>> >> Hopefully they will find their way into the QuteCsound examples too.
>> >>
>> >> Sent from my Radio Baton ;-)
>> >>
>> >> On Oct 9, 2009, at 7:04 AM, joachim heintz
>> >> wrote:
>> >>
>> >>> They are included in the manual. pvsadsyn, pvsarp ...
>> >>> Thanks for your interest -
>> >>> joachim
>> >>>
>> >>>
>> >>> Am 09.10.2009 um 12:56 schrieb Rory Walsh:
>> >>>
>> >>>> Where can we find them in the cvs? I'd be interested to see what
>> >>>> you
>> >>>> created!
>> >>>>
>> >>>> 2009/10/9 joachim heintz :
>> >>>>>
>> >>>>> I've written new examples for the pvs opcodes which are included
>> >>>>> in the
>> >>>>> new
>> >>>>> (5.11) release. Please test and let's improve them, if you are
>> >>>>> interested in
>> >>>>> working with these opcodes. Or if you have written them ...-)
>> >>>>> Thanks -
>> >>>>>
>> >>>>> joachim
>> >>>>>
>> >>>>>
>> >>>>> Send bugs reports to this list.
>> >>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>> >>>>> "unsubscribe
>> >>>>> csound"
>> >>>>>
>> >>>>
>> >>>>
>> >>>> Send bugs reports to this list.
>> >>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>> >>>> "unsubscribe
>> >>>> csound"
>> >>>
>> >>>
>> >>>
>> >>> Send bugs reports to this list.
>> >>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>> >>> "unsubscribe
>> >>> csound"
>> >>
>> >>
>> >> Send bugs reports to this list.
>> >> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>> >> "unsubscribe
>> >> csound"
>> >>
>> >
>> >
>> > Send bugs reports to this list.
>> > To unsubscribe, send email sympa@lists.bath.ac.uk with body
>> > "unsubscribe csound"
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>
>
> --
> Saludos,
> Felipe Sateler
>
--
Andrés
Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" |