Howdy, don't think this has ever been discussed... sorry if it had.
So, we need externals with non-alphanumeric names to be loaded into a multi-object library, loaded via start up. If you have them as a set of single-object binaries, the only option seems to be [hexloader] (a third party external). Hence, in order to reduce dependency on third party externals, would there be any opposition in the idea of incorporating the hexloader code into Pd Vanilla?
An alternative could be 'deken' handling dependencies, so if you download one external pack it would also download a dependency such as 'hexloader'.
thoughts?
cheers
Howdy, don't think this has ever been discussed... sorry if it had.
So, we need externals with non-alphanumeric names to be loaded into a multi-object library, loaded via start up. If you have them as a set of single-object binaries, the only option seems to be [hexloader] (a third party external). Hence, in order to reduce dependency on third party externals, would there be any opposition in the idea of incorporating the hexloader code into Pd Vanilla?
An alternative could be 'deken' handling dependencies, so if you download one external pack it would also download a dependency such as 'hexloader'.
thoughts?
Sorry, I just noticed this message. Pd's default loader mechanism has a "hexloader" in it. Curious-- if the user tries to create [foo], what is the use case for the default loader trying to load "foo/foo.$pd_extension" and "foo/foo.pd"?
-Jonathan
cheers
On 08/04/17 06:27, Jonathan Wilkes via Pd-list wrote:
Sorry, I just noticed this message.
Pd's default loader mechanism has a "hexloader" in it.
Nevermind-- it appears to be vestigial, as only the non-hexmunged name is used for the filename.
this is intentional. filenames have way less restrictions than C-symbols, so there is little reason to hexmunge them and make them even more unreadable by the ordinary human.
On 08/04/17 01:30, Jonathan Wilkes via Pd-list wrote:
Curious-- if the user tries to create [foo], what is the use case for the default loader trying to load "foo/foo.$pd_extension" and "foo/foo.pd"?
like: loading libraries that keep all their stuff (e.g. documentation) local in a directory, trying not to pollute your path too much? i very much prefer to look at: bar/ foo1/ foo2/ foo3/ foo4/ foo5/ foo6/ foo7/ foo8/ foo9/ than to look at: bar.pd bar-help.pd foo1.pd foo1-help.pd foo2.pd foo2-help.pd foo2.txt foo3.pd foo3-help.pd foo4.pd foo4-help.pd foo5.pd foo5-help.pd foo5a.txt foo5b.txt foo6.pd foo6-help.pd foo7.pd foo7-help.pd foo8.pd foo8-help.pd foo9.pd foo9-help.pd when i'm really only interested in the [bar] object.
sgdfmars IOhannes
-
Alexandre Torres Porres -
IOhannes m zmoelnig -
Jonathan Wilkes