Hi,
derek holzer derek@x-i.net:
oh, I would love to see a list of all the objects too. The main problem is that with a community-developed software like PD, there is no "master list" anywhere with all the objects you have installed. It would be like in Reaktor, if there was a master list of all the instruments you have ever made or downloaded. There is [simply no way/no simple way] to keep track except by hand. You could make an entry manually in that txt file for every object you include in your own setup, I suppose.
Well, you could get a simple list of Pd objects by just looking at, which .pd_linux, .pd_darwin or .dll files are in the directories of your Pd-path. This would not cover libraries, though, but many objects, at least from CVS, aren't in libraries. It could also be possible, but probably slow, to write some function for Pd, which scans all external/library files for the X_setup functions that create the objects. Isn't Max doing something like this?
But then, you would have a list of objects, but still wouldn't know what they do. So maybe it's best to complete the help files, then you would have documentation and a list in one directory.
Frank Barknecht _ ___footils.org_