I now have a Pd console window running on Node-Webkit, plus some menus.
The reason I chose Node-Webkit is because all of the bloat includes within it what I need to change from tcl/tk, yet still retain the same basic GUI interface (and be cross-platform). Things like creating/destroying new windows, adding and disabling menus/menuitems, etc.
To have even a tiny web server one would have to change the basic design to some kind of single-window IDE where you roll your own patch windows. That could be very interesting, but it is too much work at this moment. However, I am using a sys_vgui wrapper that looks more like pd_vmess. That at least helps to get rid of explicit tcl in the c code, which could help going forward with the kind of interface you're talking about.
-Jonathan
On Monday, January 5, 2015 4:22 PM, Brian Fay <ovaltinevortex@gmail.com> wrote:
One thing I really like about a web technology-based interface is the idea that maybe the computer running Pd and the computer accessing the interface wouldn't necessarily have to be the same computer.
I'm imagining running Pd on a small single-board computer, and patching/interacting with it on a tablet or a phone or a laptop, connecting over an ad-hoc wireless network.
Node-webkit from my understanding is really only intended to run locally, as if it were a native application. It includes an implementation of a web browser so that it can run, and that is where the ~100MB bloat comes from.
Maybe instead of relying on node-webkit we could write our own tiny node server, and have users jump into their favorite web browsers to access the interface?
This would lose the convenience of starting Pd like a native program, but it could be really cool to access it from outside devices.
Does anybody with more knowledge of Pd's internals have thoughts on the feasibility of this?
-Brian
_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list