On Sep 27, 2005, at 1:56 PM, IOhannes m zmölnig wrote:

Update of /cvsroot/pd-gem/Gem/examples/02.advanced In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv6107

Added Files: 17.fragment_program.pd Log Message: a fragment-shader demo that adds some b/w-noise...

...nice to see! Now that people are getting into the shaders (cgc is even playing around with them!), I'd like to float some ideas...

...glsl support is very high on my to-do list, but do people think this should be just added to [vertex_program] and [fragment_program], or should another object be created? (and then perhaps another for Cg?) Seems like it'd be trivial to just recognize the program from the header...

...I think it'd be really cool to allow for editing the program from within the patch (so that it's an interactive development tool), but I'm not sure the "best" way to do this...I've thought that I could create a general tk text widget (perhaps via toxy or as another pd object) that would then output the edited text to the [open $1<...or better yet perhaps, put the editor inside each program object, such that an [edit< message to the object opens up a window with the program in it for editing, and the program would be updated if the text is changed...

...finally, there should be some mechanism within each object that allows for automatic "discovery" of input parameters to the programs (and distinguish's between editable ones and "environmental" ones), and then auto-generates inlets (or messages?) for them, with each inlet accepting a list or an atom...

...any other ideas?

jamie