hi, some things:
a) making use of pdb:
what about giving more life to pdb? as to have (or approach to) *all* of the objects that can be created inside pd, plus their description, parent librabry, + ... at least for stuff inside cvs
by agreeing on a way for documenting each external lib, object or (however we do it)we could have a script parse and insert into a db all relevant data, and then use and improve the search engine, thus achieving solid keword (?) based relational records "connecting" abstractions to objects/externals/abstractions/patches/+ (?) i began something not so advanced but then thought it could be a waste of time if we can get back to pdb @ iem
if u wanna check it is http://pd.xicnet.com just sucked the externals area from pdb at iem and built a php+mysql searchbase. if useful i can continue to work on it
b) I have published some of my pd work at http://rama.xicnet.com
It is an ongoing project and patches names, packaging and documentation is changing constantly.
if anyone wants to try it I'm open to feedback through either list or direct emails
c) list configuration:
for any special reason this list is configured to reply to author instead of reply to list?
some mails I supposed I've posted to the list, just got lost because of not realizing it was going to originator's mailbox.
greetings r
Hallo, rama hat gesagt: // rama wrote:
c) list configuration:
for any special reason this list is configured to reply to author instead of reply to list?
It doesn't set any reply-to at all, which is the correct thing. There is however a header "Old-Reply-To: " which is set, if the original mail had a reply-to, I guess. Your mail had such an old-reply-to.
ciao
On Tue, 2 Dec 2003, rama wrote:
what about giving more life to pdb? as to have (or approach to) *all* of the objects that can be created inside pd, plus their description, parent librabry, + ... at least for stuff inside cvs
by agreeing on a way for documenting each external lib, object or (however we do it)we could have a script parse and insert into a db all relevant data,
I think it would be a realy useful tool, if at least the externals that are on CVS wouild be searchable. We would have to agree on a simple textfile format to document externals, e.g. we name it
extname-help.txt
then we would have to put an easily parseable text into that, like
Name: extname
Keywords: superfast list processing symbolconverter beattracker ..
Description: The extname externals does this and that ...
If we could agree on use such a format and implement it, it would make life a lot easier for users that search for a special external ... (and for developers, who do not have to recode the same functionality) .. and for people who want to keep a database about pd externals up to date.
Guenter
and then use and improve the search engine, thus
achieving solid keword (?) based relational records "connecting" abstractions to objects/externals/abstractions/patches/+ (?) i began something not so advanced but then thought it could be a waste of time if we can get back to pdb @ iem
if u wanna check it is http://pd.xicnet.com just sucked the externals area from pdb at iem and built a php+mysql searchbase. if useful i can continue to work on it
b) I have published some of my pd work at http://rama.xicnet.com
It is an ongoing project and patches names, packaging and documentation is changing constantly.
if anyone wants to try it I'm open to feedback through either list or direct emails
c) list configuration:
for any special reason this list is configured to reply to author instead of reply to list?
some mails I supposed I've posted to the list, just got lost because of not realizing it was going to originator's mailbox.
greetings r -- rama medialist@xicnet.com
PD-dev mailing list PD-dev@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-dev
-
Frank Barknecht -
guenter geiger -
rama