I don't think that we are talking about types?
maybe that the type system necessitates "using routes and selects, packs and unpacks to mange...In between goes a layer of type-checking"
im pretty sure the way all the other systems have avoided this confusing-to-n00bs 'list thats not a list due to prepended non-list selector' thing is by having the selector painted right on the object:
http://gstreamer.freedesktop.org/data/images/gst-editor/gst-editor-ambisonic... http://www.nongnu.org/om-synth/gated_sine.png http://img.photobucket.com/albums/v287/joeedh/MusicAppScreenie3.png
even as a non-newbie its useful to see all the methods without traipsing into a gigantic class-selector scrolly-list, or god forbid, the documentation.
this should be doable in DesireData as some kind of inheritable superclass, utilizing data from the class-inspector API, right?
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju | Freelance Digital Arts Engineer, Montréal QC Canada
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list