[PD-dev] Re: data structures <> tk mapping

[B. Bogart]

Ok this is wetting my appetite.

I asked a while back about anyone having an example of datastructures being used 
for something other can canvas drawing. No one responded.

So now seems like a good time to ask again.

Are there examples of pd datastructures being used for something other than 
canvas drawing!? Please send me!

Things I'm working on now for pixelTANGO:
* state-saving with memento, except the OSC names are specified dynamically

* dynamic naming of abstractions (instance counting within a class, all in PD land)

* dynamic routing.. I'm working on an abstraction call dir2abstractionArray that 
takes a path glob pattern and uses that to generate an array of each abstraction 
  in the directory. These abstractions have two inlets and two outlets that can 
be used for anything. Anything going into the two inputs on the 
dir2abstractionArray get routed to the abstraction selected by its index value, 
and anything going through the abstractions outlets (when the index value 
matches) gets routed to the dir2abstractionArray outlets. I'm using this to 
switch between various pix_ effects in gem, where each abstraction fx/edge has a 
standard interface to the parent patch. The point is that the user can drag and 
drop a bunch of abstractions (from friends for example) and boom, they show up 
in a popup list automatically.

* OSC name registration so that the dynamically named abstractions dump all 
thier data in a pool and there is a cental repository of all the OSC names in a 
patch that is generated on loading the patch. I'm hoping to be able to 
automatically associate MIDI controlers to each of these OSC names...

Perhaps data-structures could make some of this stuff a little less messy.

B/

zf wrote:
>>There was some discussion of trying to implement iemguis and  
>>unauthorized guis using data structures.  Frank has already implemented  
>>sliders and a [grid]-style object.  It seems to me that this would be  
>>the ultimate way to handle this in a native Pd way.
> 
> 
> i agree this would be a good thing, that is the ability to map the pure data structures to things like blt::vector's or named tcl arrays, for those not content with using mere shapes on a canvas! and then define the gui which 'houses' the mapped data in simple tk, something similar to the miXed/ '.wid' format but eliminating the need to think/code add|remove|update|sync each and every...
> 
> 
> oh and to keep this thread on topic, do you find:
> 
> <list>this list<list>inside<list>a list</list></list></list>
> 
> to be more human readable than:
> 
> this list {inside {a list}}
> 
> ?
> 
> c
> 
> _______________________________________________
> PD-dev mailing list
> PD-dev at iem.at
> http://iem.at/cgi-bin/mailman/listinfo/pd-dev
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
URL: <http://lists.puredata.info/pipermail/pd-dev/attachments/20041218/8ccc992b/attachment.pgp>