Dear all,
in these days several guys complaint with me about the difficulty of finding one particular external in the sea called Deken. The main problem is that people have patches on Extended and the difficult task is to switch on Vanilla + Deken.
So, the most trivial solution that comes to my mind is to create a Latex template where put for each library several infos like the name of the library, the maintainer, the version, and the list of objs maybe with same extra informations. My idea is to provide a general latex template and people can help this project downloading the template and then start to put all informations.
However, the main point is: it si useful? I mean Floss[1] provides something similar, and before to start this project I was just wondering about its concrete helpfulness. Maybe something similar is present and simply I don't know about it. In these case, it could be an idea to upload it on Deken and when people just press "enter" or some typos Deken can suggest to download this pdf.
Finally, an object list can be useful to understand who is maintaining what and what is actually not maintained.
Probably it's only a boring idea. Let me know.
Best regards.
[1]: http://en.flossmanuals.net/pure-data/ch072_introduction/
Hi Marco,
Dear all,
in these days several guys complaint with me about the difficulty of finding one particular external in the sea called Deken. The main problem is that people have patches on Extended and the difficult task is to switch on Vanilla + Deken.
So, the most trivial solution that comes to my mind is to create a Latex template where put for each library several infos like the name of the library, the maintainer, the version, and the list of objs maybe with same extra informations. My idea is to provide a general latex template and people can help this project downloading the template and then start to put all informations.
However, the main point is: it si useful? I mean Floss[1] provides something similar, and before to start this project I was just wondering about its concrete helpfulness. Maybe something similar is present and simply I don't know about it. In these case, it could be an idea to upload it on Deken and when people just press "enter" or some typos Deken can suggest to download this pdf.
Finally, an object list can be useful to understand who is maintaining what and what is actually not maintained.
Probably it's only a boring idea. Let me know.
Yes, I think it would be useful. If it was web-based, it could even help deken suggest libraries with same or similar named objects. Libraries do not change very much these days, so even an one time effort will be useful for some years.
Best regards.
Greetings,
Fred Jan
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
Suggestion: in m_class.c, uncomment this line:
#if 0 post("class: %s", c->c_name->s_name); #endif
Then load the libraries one by one - you'll be rewarded with a printout of all created classes. If you only want to see ones you can tye in a box (supressing invisible helper objects), instead make it:
if (typeflag == CLASS_PATCHABLE) post("class: %s", c->c_name->s_name);
cheers Miller
On Thu, Jun 23, 2016 at 05:41:13PM +0200, Fred Jan Kraan wrote:
Hi Marco,
Dear all,
in these days several guys complaint with me about the difficulty of finding one particular external in the sea called Deken. The main problem is that people have patches on Extended and the difficult task is to switch on Vanilla + Deken.
So, the most trivial solution that comes to my mind is to create a Latex template where put for each library several infos like the name of the library, the maintainer, the version, and the list of objs maybe with same extra informations. My idea is to provide a general latex template and people can help this project downloading the template and then start to put all informations.
However, the main point is: it si useful? I mean Floss[1] provides something similar, and before to start this project I was just wondering about its concrete helpfulness. Maybe something similar is present and simply I don't know about it. In these case, it could be an idea to upload it on Deken and when people just press "enter" or some typos Deken can suggest to download this pdf.
Finally, an object list can be useful to understand who is maintaining what and what is actually not maintained.
Probably it's only a boring idea. Let me know.
Yes, I think it would be useful. If it was web-based, it could even help deken suggest libraries with same or similar named objects. Libraries do not change very much these days, so even an one time effort will be useful for some years.
Best regards.
Greetings,
Fred Jan
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
Dear list,
@Miller: thank you for your suggestion. However I used all my (very limited) bash knowledge and I wrote a simple script that searches the name in the gensym function after the class_new declaration. Using then find I look on all src folder.
@Fred: thank you for your words. If my bash knowledge is limited, my web knowledge is almost zero. However, if it will be possible to open a page on puredata.info and upload the list sorted (by library?) I will do it. But I don't know how to create a page on puredata.info or similar.
In attachment, the script (just chmod +x objlist.sh ) and the zexy object list obtained in this way: find ./zexy/src -name '*.c' -exec ./objlist.sh {} ; > zexy.txt
A final note: I am on OS X, so no GNU sed. I downloaded the GNU sed from MacPorts (gsed). In the script we have to change gsed with sed.
Best regards,
Marco
2016-06-23 17:53 GMT+02:00 Miller Puckette msp@ucsd.edu:
Suggestion: in m_class.c, uncomment this line:
#if 0 post("class: %s", c->c_name->s_name); #endif
Then load the libraries one by one - you'll be rewarded with a printout of all created classes. If you only want to see ones you can tye in a box (supressing invisible helper objects), instead make it:
if (typeflag == CLASS_PATCHABLE) post("class: %s", c->c_name->s_name);
cheers Miller
On Thu, Jun 23, 2016 at 05:41:13PM +0200, Fred Jan Kraan wrote:
Hi Marco,
Dear all,
in these days several guys complaint with me about the difficulty of finding one particular external in the sea called Deken. The main problem is that people have patches on Extended and the difficult task is to switch on Vanilla + Deken.
So, the most trivial solution that comes to my mind is to create a Latex template where put for each library several infos like the name of the library, the maintainer, the version, and the list of objs maybe with same extra informations. My idea is to provide a general latex template and people can help this project downloading the template and then start to put all informations.
However, the main point is: it si useful? I mean Floss[1] provides something similar, and before to start this project I was just wondering about its concrete helpfulness. Maybe something similar is present and simply I don't know about it. In these case, it could be an idea to upload it on Deken and when people just press "enter" or some typos Deken can suggest to download this pdf.
Finally, an object list can be useful to understand who is maintaining what and what is actually not maintained.
Probably it's only a boring idea. Let me know.
Yes, I think it would be useful. If it was web-based, it could even help deken suggest libraries with same or similar named objects. Libraries do
not
change very much these days, so even an one time effort will be useful
for
some years.
Best regards.
Greetings,
Fred Jan
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
Hi Marco,
Dear list,
@Miller: thank you for your suggestion. However I used all my (very limited) bash knowledge and I wrote a simple script that searches the name in the gensym function after the class_new declaration. Using then find I look on all src folder.
@Fred: thank you for your words. If my bash knowledge is limited, my web knowledge is almost zero. However, if it will be possible to open a page on puredata.info http://puredata.info and upload the list sorted (by library?) I will do it. But I don't know how to create a page on puredata.info http://puredata.info or similar.
My approach is to get a list of object names from the *-help.pd patches. Combined with a search function in the puredata.info server this could result in a object search as part of the deken "Find externals"-plugin. See https://github.com/pure-data/deken/issues/133 for more details.
In attachment, the script (just chmod +x objlist.sh ) and the zexy object list obtained in this way: find ./zexy/src -name '*.c' -exec ./objlist.sh {} ; > zexy.txt
The objects list I created(1) also have a description harvested from the META subpatch found in most pd-extended help patches and added by Jonathan Wilkes. The first envisioned version will probably not use it, but it could get useful to find the right object if the search result offers two different ones with the same name.
A final note: I am on OS X, so no GNU sed. I downloaded the GNU sed from MacPorts (gsed). In the script we have to change gsed with sed.
Best regards,
Marco
Greetings,
Fred Jan
1) using a ugly Perl script, but I'll try to make a Python version to match the deken build/package/upload tool.
2016-06-23 17:53 GMT+02:00 Miller Puckette <msp@ucsd.edu mailto:msp@ucsd.edu>:
Suggestion: in m_class.c, uncomment this line: #if 0 post("class: %s", c->c_name->s_name); #endif Then load the libraries one by one - you'll be rewarded with a printout of all created classes. If you only want to see ones you can tye in a box (supressing invisible helper objects), instead make it: if (typeflag == CLASS_PATCHABLE) post("class: %s", c->c_name->s_name); cheers Miller On Thu, Jun 23, 2016 at 05:41:13PM +0200, Fred Jan Kraan wrote: > Hi Marco, > > >Dear all, > > > >in these days several guys complaint with me about the difficulty of > >finding one particular external in the sea called Deken. The main > >problem is that people have patches on Extended and the difficult task > >is to switch on Vanilla + Deken. > > > >So, the most trivial solution that comes to my mind is to create a Latex > >template where put for each library several infos like the name of the > >library, the maintainer, the version, and the list of objs maybe with > >same extra informations. My idea is to provide a general latex template > >and people can help this project downloading the template and then start > >to put all informations. > > > >However, the main point is: it si useful? I mean Floss[1] provides > >something similar, and before to start this project I was just wondering > >about its concrete helpfulness. Maybe something similar is present and > >simply I don't know about it. In these case, it could be an idea to > >upload it on Deken and when people just press "enter" or some typos > >Deken can suggest to download this pdf. > > > >Finally, an object list can be useful to understand who is maintaining > >what and what is actually not maintained. > > > >Probably it's only a boring idea. Let me know. > > Yes, I think it would be useful. If it was web-based, it could even help > deken suggest libraries with same or similar named objects. Libraries do not > change very much these days, so even an one time effort will be useful for > some years. > > > > >Best regards. > > > >[1]: http://en.flossmanuals.net/pure-data/ch072_introduction/ > > Greetings, > > Fred Jan > > > > > >_______________________________________________ > >Pd-dev mailing list > >Pd-dev@lists.iem.at <mailto:Pd-dev@lists.iem.at> > >https://lists.puredata.info/listinfo/pd-dev > > > > _______________________________________________ > Pd-dev mailing list > Pd-dev@lists.iem.at <mailto:Pd-dev@lists.iem.at> > https://lists.puredata.info/listinfo/pd-dev
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
With your good work you made my work so ugly and useless :)
Best,
Marco
2016-07-01 21:24 GMT+02:00 Fred Jan Kraan fjkraan@xs4all.nl:
Hi Marco,
Dear list,
@Miller: thank you for your suggestion. However I used all my (very limited) bash knowledge and I wrote a simple script that searches the name in the gensym function after the class_new declaration. Using then find I look on all src folder.
@Fred: thank you for your words. If my bash knowledge is limited, my web knowledge is almost zero. However, if it will be possible to open a page on puredata.info http://puredata.info and upload the list sorted (by library?) I will do it. But I don't know how to create a page on puredata.info http://puredata.info or similar.
My approach is to get a list of object names from the *-help.pd patches. Combined with a search function in the puredata.info server this could result in a object search as part of the deken "Find externals"-plugin. See https://github.com/pure-data/deken/issues/133 for more details.
In attachment, the script (just chmod +x objlist.sh ) and the zexy object list obtained in this way: find ./zexy/src -name '*.c' -exec ./objlist.sh {} ; > zexy.txt
The objects list I created(1) also have a description harvested from the META subpatch found in most pd-extended help patches and added by Jonathan Wilkes. The first envisioned version will probably not use it, but it could get useful to find the right object if the search result offers two different ones with the same name.
A final note: I am on OS X, so no GNU sed. I downloaded the GNU sed from MacPorts (gsed). In the script we have to change gsed with sed.
Best regards,
Marco
Greetings,
Fred Jan
- using a ugly Perl script, but I'll try to make a Python version to
match the deken build/package/upload tool.
2016-06-23 17:53 GMT+02:00 Miller Puckette <msp@ucsd.edu mailto:msp@ucsd.edu>:
Suggestion: in m_class.c, uncomment this line: #if 0 post("class: %s", c->c_name->s_name); #endif Then load the libraries one by one - you'll be rewarded with a printout of all created classes. If you only want to see ones you can tye in a
box (supressing invisible helper objects), instead make it:
if (typeflag == CLASS_PATCHABLE) post("class: %s", c->c_name->s_name); cheers Miller On Thu, Jun 23, 2016 at 05:41:13PM +0200, Fred Jan Kraan wrote: > Hi Marco, > > >Dear all, > > > >in these days several guys complaint with me about the difficulty
of > >finding one particular external in the sea called Deken. The main > >problem is that people have patches on Extended and the difficult task > >is to switch on Vanilla + Deken. > > > >So, the most trivial solution that comes to my mind is to create a Latex > >template where put for each library several infos like the name of the > >library, the maintainer, the version, and the list of objs maybe with > >same extra informations. My idea is to provide a general latex template > >and people can help this project downloading the template and then start > >to put all informations. > > > >However, the main point is: it si useful? I mean Floss[1] provides > >something similar, and before to start this project I was just wondering > >about its concrete helpfulness. Maybe something similar is present and > >simply I don't know about it. In these case, it could be an idea to > >upload it on Deken and when people just press "enter" or some typos > >Deken can suggest to download this pdf. > > > >Finally, an object list can be useful to understand who is maintaining > >what and what is actually not maintained. > > > >Probably it's only a boring idea. Let me know. > > Yes, I think it would be useful. If it was web-based, it could even help > deken suggest libraries with same or similar named objects. Libraries do not > change very much these days, so even an one time effort will be useful for > some years. > > > > >Best regards. > > > >[1]: http://en.flossmanuals.net/pure-data/ch072_introduction/ > > Greetings, > > Fred Jan > > > > > >_______________________________________________ > >Pd-dev mailing list > >Pd-dev@lists.iem.at mailto:Pd-dev@lists.iem.at > >https://lists.puredata.info/listinfo/pd-dev > > > > _______________________________________________ > Pd-dev mailing list > Pd-dev@lists.iem.at mailto:Pd-dev@lists.iem.at > https://lists.puredata.info/listinfo/pd-dev
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
Hi list,
2016-07-01 21:24 GMT+02:00 Fred Jan Kraan <fjkraan@xs4all.nl mailto:fjkraan@xs4all.nl>:
1) using a ugly Perl script, but I'll try to make a Python version to match the deken build/package/upload tool.
The first public version is here: https://github.com/electrickery/pd-playground/tree/master/dekenRelated
It is intended as a script that can generate an initial list of objects or classes in a library. The result still has to be checked by hand as not every object has its own help-patch, not all help patches have a META sub-patch and not all META sub-patches have a DESCRIPTION field.
There is still much room for improvement as this is my first working python script :-).
Fred Jan