addition: the name spaces stuff should apply to abstractions (patches), too. maybe i'm influnced to much by python :-)
smoerk wrote:
Thomas Grill wrote:
Btw., on the list there are discussions going on about how to solve this name-clash problem for PD in a generic manner.
proposal:
add the possibility to load externals from inside a patch ( load <external> )
put every external in a name space by default (cyclone.vst~)
possibility to load externals in another name space ( load <external> as <namespace name> )
possibility to load only one object from an external library ( load <object> from <external> ) ( load * from <external>
to remain compatibility the -lib parameter could load the externals as usual.
i think that loading externals at startup without the possibility to load externals later condtradicts the visual on-the-fly programming.
is there are reason not load externals from inside a patch?
i feel that Pd has the biggest flaws with it usability and loading of externals is one of the greatest sources of frustration. (i have to admit that usability of PD vastly improved over the last years, especially with the windows installers and the linux packages for the externals).
PD-list mailing list PD-list@iem.at to manage your subscription (including un-subscription) see http://iem.at/cgi-bin/mailman/listinfo/pd-list