Hans-Christoph Steiner wrote:
Then there could be also something like a 'maxmsp' distro for a compatibility mode. So I was thinking there could be a "#X declare -distro vanilla" that each distro saves into every file. It would be safely ignored for Pd versions that didn't support the -distro flag.
what would e.g. Pd-vanilla that supported a "-distro" flag do if it encountered a [declare -distro maxmsp]?
furthermore: i don't think that it is good design to have [declare] accept _any_ arguments and ignore them at will (e.g. if it decides to not support "-distro", then it could either explicitely ignore "-distro" or accept any argument and only use those that it knows about.
This distro flag would then setup the canvas-local namespace with the libraries as they are loaded for that distro.
in general, i think the idea tobe able to load named library-bundles is not such a bad idea. i imagine it (right now; but this could be total nonsense) to load snippets of preference-files (that are stored somewhere in the path).
e.g. <snip> % cat ~/.pd/moko.prefs path: ~/pd/mokolib stdlib: rjdj </snip>and using [declare -loadbundle moko] would then add the path and lib to the canvas-local namespace.
gmsft IOhannes
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Pd-dev mailing list [email protected] http://lists.puredata.info/listinfo/pd-dev
