Frank Barknecht wrote:
Hallo, marius schebella hat gesagt: // marius schebella wrote:
sorry, I still don't know exactly what you mean. I think it is the only solution to keep libraries in subfolders if we want to solve nameclashes. but even if in subfolders, they should be accessible as list-abs and not list-abs/list-abs.
Huh? Nameclashes have nothing to do with subfolders per se. A nameclash is, when two objects have the same name registered in Pd but act differently. Folders are a way to organize files in a filesystem (harddisk).
the thing that I was complaining so loudly is that pd-extended ships all these libraries but does not add the paths.
Yes, that's exactly what I mean: Many people would like every objectclass to be global.
but that is not a problem for pd-extended users (and I want to solve the pd-extended problems here), as long as you can overrule the global namespace with a local namespace. pd-extended would provide a default object for every nameclash. If you have old patches that were using objects, that are not the default in pd-extended you would have to add a declare to your patch. or explicitely call them as mynondefaultlib/abs~. am I wrong? marius.