<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">I sent Miller an idea the other day about making data structures more expressive. <br>Basically allowing subpatches (including abstractions) to be defined as a field of <br>a struct.<br><br>[struct ex1 float y float i glist foo pd-bar] <-- glist field "foo" using [pd bar] as a template<br><br>So let's say you make a ds array using [struct ex1] above as the template for the elements. Now when you [setsize] to 40, each element has an associated "foo" field <br>which is actually a subpatch. To define a "subpatch template" for foo, you'd just <br>put [pd bar] in the same subpatch as [struct ex1].<br><br>The real power of this would come by being able to access the other ds fields from within <br>the "foo" subpatch. So maybe having some objects for getting a scalar's data from "within" <br>the scalar:<br><br>[getmy y i] <-- used
within the "foo" subpatch, this will output the values of the fields <br>when banged.<br><br>[setmy y i] <-- same for setting. (Since we're already inside the scalar there's <br>no need for sending pointers.)<br><br>[notify] <-- output "change", "select", etc. messages only when they refer to this scalar<br><br>Local variables! Deleting abstraction instances with [setsize]! The possibilities are <br>endless!<br><br>I have no idea how to program any of this!<br><br>-Jonathan<br><br>--- On <b>Tue, 5/11/10, Joćo Pais <i><jmmmpais@googlemail.com></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>From: Joćo Pais <jmmmpais@googlemail.com><br>Subject: Re: [PD] understanding graphics objects on canvas<br>To: pd-list@iem.at, "Ivica Ico Bukvic" <ico@vt.edu><br>Date: Tuesday, May 11, 2010, 1:29 AM<br><br><div class="plainMail">for a very
simple automatic scalar creation, look at my abs jmmmp/pd-colors. I'm sure you'll understand it easily.<br><br>there are many things that should be improved on data-s, so that they're really usable on more complex compositional contexts, and not only to draw some fancy guis. but since this is a very obscure area of pd, don't know if much energy will be put in there.<br><br><br>> Never mind. Figure it out...<br>> <br>> that said, FWIW this part may need better coverage under the "scalar"<br>> help file which pops up when one selects help on it. The other confusing<br>> thing is when you pull up properties for a scalar object on the graph<br>> that the window that pops up is titled misleadingly "Atom".<br>> <br>> Ico<br>> <br>> <br>> _______________________________________________<br>> <a ymailto="mailto:Pd-list@iem.at" href="/mc/compose?to=Pd-list@iem.at">Pd-list@iem.at</a> mailing list<br>> UNSUBSCRIBE and
account-management -> <a href="http://lists.puredata.info/listinfo/pd-list" target="_blank">http://lists.puredata.info/listinfo/pd-list</a><br><br><br>--Friedenstr. 58<br>10249 Berlin (Deutschland)<br>Tel +49 30 42020091 | Mob +49 162 6843570<br>Studio +49 30 69509190<br><a ymailto="mailto:jmmmpais@googlemail.com" href="/mc/compose?to=jmmmpais@googlemail.com">jmmmpais@googlemail.com</a> | skype: jmmmpjmmmp<br><br>_______________________________________________<br><a ymailto="mailto:Pd-list@iem.at" href="/mc/compose?to=Pd-list@iem.at">Pd-list@iem.at</a> mailing list<br>UNSUBSCRIBE and account-management -> <a href="http://lists.puredata.info/listinfo/pd-list" target="_blank">http://lists.puredata.info/listinfo/pd-list</a><br></div></blockquote></td></tr></table><br>