Hi,

Hans-Christoph Steiner <hans@eds.org> wrote:

> I have been thinking that it would be handy to have the abstractions
> collection all in one folder so that it could be added to the path.
> This would be useful for abstractions that are generally useful.  It
> probably makes sense to arrange this the same way the externals are
> arranged: directory for each dev, then when compiled, all of the
> abstractions are put into on directory, which is added to the path.

Abstractions surely will create another problem with dupe names. I'm not
sure if putting them all into one directory will make things easier here,
as probably everyone has abstractions of his/her own and thus you can never
know which name  is already taken. That's why I would rather see it, if
abstractions are not "installed" in another way than by adding some paths to
the pdrc.

One thing that would be very useful though could be wildcard path
expansion. For example I organized my rradical collection so that it
uses several paths:

rradical/instruments
rradical/effects
rradical/control
rradical/...

It would be nice to be able to add them all to pdrc with something like
"-path /usr/lib/pd/rradical/*/" or even "-path /usr/lib/pd/rradical/[^test]/"
to include all subdirs except "test"

This also would allow us to make a pdrc easier to write with the CVS while
still retaining some structure.

ciao
--
 Frank Barknecht                          _ ___footils.org_