From tcl/tk to juce - there is a lot to be said about that. Taking in all the FUDI commands from pdsend, and then translating it into a Juce GUI is pretty, and pretty neat. Especially if you can organize the patch cords. You may start a fight, with that in mind.
This is more or less what purr-data does (but then it's tcl to JS), but PlugData works differently. Basically, it assumes that patches only change through user interaction. Since all user interaction goes through PlugData's GUI, it can check and synchronise the patch content with Pd whenever the user does something. I do intercept messages to UI objects, to detect when their state has changed.
The big advantage of that is that we can change the way the UI looks without modifying any Pd source code. PlugData actually works on top of an unmodified pd-vanilla, which saves me a lot of maintenance work.
The only limitation with this is that dynamic patching (using messages to pd to modify the patch, like a meta-patch) doesn't work yet.
