[maxmsp] nice ideas!

You are right Stefan when you are speaking about not realy big and  
not too complexe Max patches.

But there are situation when the graphical interface is strated to be  
very hard to manage. There are situations it's absolutely impossible  
to create patches graphicaly (there are for example scripting  
thispatcher for do it) and only solution is to use the patch as text.  
Of course there are BBEdit to do it, but we are speaking about  
improvement of next Max version.  Maybe you don't understund "how a  
patch works by looking at its code", but the other people understund  
and used it. I think it's better idea is to alow the decision what is  
important in developement to the cycling stuff.... ;-)


Le 25 sept. 07 à 23:50, Stefan Tiedje a écrit :

> Seejay James schrieb:
>> The "split window" feature would be cool, like when doing Dreamweaver
>> or another html editor and you can see both the design and the code.
>> It would really help understand how the Max code works.
>
> I never would understand how a patch works by looking at its code,  
> I always understand it by looking at the patch. I'd never use it I  
> guess. The text representation is for machines, but is hackable  
> like code in an hex editor. Its not ment to be understood, because  
> you need to count lines and things like that...
> You can always open the patch as text in another window, I'd rather  
> let the cycling folks concentrate on important stuff...
>
> Stefan

Alexander Mihalic
-----------------------------------------------------------
Computer Music Department Manager

IMEB
Pl. André Malraux, 18000 Bourges, France

mihalic.imeb at orange.fr
http://www.imeb.org

tel: (33)-2.48.20.41.87.
fax: (33)-2.48.20.45.51.