Hi,
I am working on OSX, using the plain vanilla version of PD-0.42-6.
I can find a listing of objects by ctrl clicking a patcher window,
but it does not list everything.
(For example, "expr" is not mentioned.) Is there any easy way to get
a listing of all the objects currently loaded?
Peeking into the application resources, It looks like the additional
externals hiding in the "extra" folder.
In fact, it looks like the whole source is hiding there. Is it
possible to rebuild pd from the contents of the resources
folder? (That would be a pretty suave archiving feature....)
Cheers,
RJK
On Thu, 10 Mar 2011, ronald kuivila wrote:
I can find a listing of objects by ctrl clicking a patcher window, but it does not list everything. (For example, "expr" is not mentioned.) Is there any easy way to get a listing of all the objects currently loaded?
I coded such a feature in 2004 but it didn't end up being included anywhere, even though part of the code had the same license as Pd.
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
On Thu, 10 Mar 2011, Bernardo Barros wrote:
2011/3/10 Mathieu Bouchard matju@artengine.ca:
where ?
PD? Or PD-ext
I can't force the maintainers to do it.
or even GridFlow?
That would be an idea. In that case, however, I can't get the actual list of classes (pd doesn't keep such a list at all), but I can get the list of creators, which is nearly the same, except I can't detect aliases, and except that I can't get the list of first-inlet methods for each class.
And then, listing any abstractions, or any externals that aren't loaded, is a separate task.
btw GridFlow can list the methods of its own classes for all inlets and stuff... see http://gridflow.ca/help/gf/class_info-help.html ; but this does not include any way to get the list of GF's classes in any way.
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
Hi all -- there's a line in m_class.c in the class_new() function, just before the end, that you can uncomment to get Pd to print out every class as it's loaded (but not abstractions).
Unfortunately that still doesn't tell you about every class in extra, since they're only loaded on demand.
And yes, the source lives inside the "binary" release, contrary to the usual custom, and is intended to make it very easy to recreate old versions on new platforms.
cheers Miller
On Thu, Mar 10, 2011 at 10:57:00AM -0500, Mathieu Bouchard wrote:
On Thu, 10 Mar 2011, Bernardo Barros wrote:
2011/3/10 Mathieu Bouchard matju@artengine.ca:
where ?
PD? Or PD-ext
I can't force the maintainers to do it.
or even GridFlow?
That would be an idea. In that case, however, I can't get the actual list of classes (pd doesn't keep such a list at all), but I can get the list of creators, which is nearly the same, except I can't detect aliases, and except that I can't get the list of first-inlet methods for each class.
And then, listing any abstractions, or any externals that aren't loaded, is a separate task.
btw GridFlow can list the methods of its own classes for all inlets and stuff... see http://gridflow.ca/help/gf/class_info-help.html ; but this does not include any way to get the list of GF's classes in any way.
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list