Express all this as a Pd intrinsic tool.

[rhaleblian]

By this we mean make it possible for users to compile inside the Pd GUI.
Look at Max for examples of this kind of workflow.

[rhaleblian]

Benefit: users would need only know how to operate Pd (which is a given) to get their code on the hardware.
Benefit: use on Windows would be streamlined, as the idiom here assumes *NIX.

[rhaleblian]

Seems like if one is gonna spend effort on a plugin that doing it for Purr Data is most appealing.

[dromer]

Hey spotted your project utilizing pd2dsy :)

I've also been thinking of this idea to be able to "export" from a pd instance (or a version of it).
One of my ideas is that this pd environment should have the same "vanilla restrictions" as heavy has, so only those objects that are compatible. This limits the user in what they can patch, but it ensures compatibility between prototyping and eventual heavy output.

There is also https://github.com/timothyschoen/PlugData/ that wraps libpd in JUCE for an alternate GUI.
Perhaps we can make a version of PlugData that 1) only shows heavy compatible modules 2) has an extra button that calls the hvcc command with correct settings etc.

It would of course be nice if the PATH of this pd then has abstraction libraries set, which are then also used in the -p search paths of hvcc.

[rhaleblian]

hiya @dromer
This is interesting, lemme take a look at PlugData.