Hi Luis,

Regarding blue, I would just like to mention that it can scale really
to your needs.  If you wish to only use it as a text editor, you can
certainly do so by using only the global orc and sco areas of blue and
still take advantage of syntax highlighting, lookup of documentation
and examples, code repository, different settings for rendering to
realtime and to disk, etc.  Later, if you decide you want take
advantage of other features like the instrument library, the mixer,
the score timeline, etc., you can take advantage of the pieces as you
see fit.

For example, if you were interested in doing a project with csound orc
and doing all score via python script, you could do all of your
orchestra in the global orc section and then use a single pythonObject
on the main timeline to do all of your score work.  If you are using
the embedded python interpreter in blue, this project then becomes
portable across Windows, OSX, and Linux and does not require anything
but blue installed.

Just some thoughts about blue!
steven

On Feb 6, 2008 6:52 AM, k_o_m_p <k_o_m_p@yahoo.de> wrote:
>
>  I used to work with MacCsound as a text editor running csound on the
> terminal as well as a GUI. Now I am starting to set csound-x with Emacs
> (Aquamacs) which works fine in the  MMM mode. But to use it with csound one
> may have to learn Emacs before csound...
>
>  I am curious about Lettuce but I am running Mac. I should also take a look
> at Blue, although, it seams to me at the first look, that the main concept
> is different from the classic csound.
>
>  Csound as changed a lot in the last years and frontends like Lettuce or
> MacCsound are great. The only problem is that they are platform dependent. I
> think this leads to some confusion at the beggin when learning csound (some
> of my students use Mac, some Windows and others use Linux...).
>
>  But I am curious about teaching csound: are you using always Lettuce in
> your lessons?
>
>  Luis
>
>
>  Rory Walsh schrieb:
> Which frontend are you using? In Lettuce users only have to place the cursor
> on an opcode and press f1 which automatically opens the manual at that
> opcode entry. I think MacCsound does this as well, and Blue for that matter.
> Forgive me for asking but what could be easier than a single keystroke?
> Great to see others on the list teaching Csound, is it just me or does there
> seem to be an increase in the numbers of people teaching Csound lately?
>
>  Rory.
>
>
>  k_o_m_p wrote:
>
> Hello,
>
>  I have been teaching csound this semester and my students and I are missing
> some small things which - seams to me - would make the life of beginners
> much easier.
>
>  I am speaking in concrete of the documentation. Not of the content, but the
> way it is linked to csound. Giving supercollider as an example, you have
> easy access to the documentation of the opcodes without
>  much effort. Of course in csound, if you can set properly your text editor
> you will probably be able to set everything according to your needs, but a
> beginner possibly won't. I don't know how difficult it is to implement this
> (MacCsound did something in this direction which I think it is very positiv)
> but I would like to know the opinion of the users community.
>
>  Thanks,
>
>  -Luis
>
>  --
>
>  l u i s   a n t u n e s   p e n a
>
>  http://icem.folkwang-hochschule.de/~pena
> <http://icem.folkwang-hochschule.de/%7Epena>
>
>  http://www.myspace.com/kaurimusik
>
>
>
>
>  Send bugs reports to this list.
>  To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>
>
>
> --
>
>
> l u i s   a n t u n e s   p e n a
>
> http://icem.folkwang-hochschule.de/~pena
>
> http://www.myspace.com/kaurimusik
>