[PD] PDDP meeting?

[day 5]

Perhaps an idea might be an API function to Pd that scans the user's Pd 
externals directory (on *nix nominally /usr/local/lib/pd/extra) and 
dumps a list of all main_ symbols found to the Pd window or the 
stdout... similar to how users can access GridFlow's "profiler_dump" 
via a menu; Something like "Help" -> "Dump Externals List".

Even better, if it was an API function users could run Pd with a 
certain flag (similar to ./csound -z1) that will dump a list of all 
externals and if Pd senses this flag on the commandline it would return 
a list to the stdout and exit. That way users could keep personal 
repositories in text files and it would be easy to see if new externals 
were being installed correctly or not.


./d5


On Apr 26, 2006, at 6:31 AM, Hans-Christoph Steiner wrote:

>
> On Apr 25, 2006, at 9:39 PM, day 5 wrote:
>
>>
>> On Apr 25, 2006, at 2:49 PM, derek holzer wrote:
>>
>>> My suggestion would be to make a "dictionary" of objects, maybe 
>>> sorted by name, library or general function (dataflow, 3d, audio, 
>>> video, I/O...), such as the directories which were made by the user 
>>> community for CSound. That might be useful as a PDF or hardcopy 
>>> even. The PDcyclopia?
>>
>> This idea garners my unfettered support. I hope this gets implemented 
>> at some point. I'm willing to help out.
>>
>> Would externs in the "unsupported" folder of CVS module "externals" 
>> also be included in this compendium ?
>
> The idea is to have meta data in each help file.  Then that data is 
> parsed by Pd and used to generate a searchable index of all of the 
> objects.  Its been discussed and spec'ed out in the PDDP meetings and 
> template designs.
>
> .hc