[PD] Aciles - the world's worst web server in Pd

Billy Stiltner billy.stiltner at gmail.com
Tue Nov 22 14:49:03 CET 2016


just showed up in my facebook news feed 1 year ago
Billy Stiltner <https://www.facebook.com/billyjoestiltner?fref=nf>
November 22, 2015
<https://www.facebook.com/billyjoestiltner/posts/1170135913014557> ยท

I try to keep from using any toolkits, frameworks, libraries, etc.. that
are not part of a default installation of preferred OS which at the moment
is Linux in the flavor of Ubuntu Studio. Am trying to keep my synth cross
platform. Some parts of the recent developments have been programmed using
javascript and a web browser for the UI. This made rapid development easy.
Some things need redone so that future editing will be easy. Like the mode
display and selection.
It was easy to grab the raw text from the scala mode list then do search
and replace in a text editor to add the html and javascript required for
the user interaction and sending the mode data to the synthesizer. The
problem with this is that there are other parts of the interface that also
send modes and other information to the synthesizer so including a list of
1000s of modes along with their name, etc... kind of makes the source
editing slow and confusing so
The mode data needs to be in a text file and loaded up by javascript then
instead of listing the modes all in a huge list , a smaller subset of the
entire list only need be displayed at one time. A good division of the list
would be grouping by period. It's how the modes are grouped visually in the
big list.
Another problem is the use of JAVA only for creating a TCP or UDP socket in
order to communicate with the synth. JAVA is ok, there have been security
risks with it in the past which is not my concern. The concern is that it's
way too much overhead for adding raw socket capabilities to the browser and
updates often result in an inoperable configuration. I have downloaded
node.js to tinker with but Am having 2nd thoughts about this. I'm not sure
that node will be something that will last. Something that has been working
very good for a really long time without changes that affect old programs
is opengl and xwindows. So what I'm wondering is that if I use node.js to
provide a raw socket between the browser and synthesizer, will it be easy
to include that with the synthesizer and have users easily install the
required parts to make node.js work? So far it seems like a lot of extra
work. Maybe I ought to just make a .ws server patch in puredata and use
html5's websockets. On another note what is this uv_tree thing? looking at
the headers with node I find some similarities in my old dynamic response
loading operating system in that the first things declared are handles, and
a list object (node) of which every other object created inherits
properties from. As the evolution of the objects proceed ...

On Tue, Nov 22, 2016 at 2:07 AM, Billy Stiltner <billy.stiltner at gmail.com>

> the / and ; aRE  being prepended with / so it's a tcl tk thing i guess,
> On Fri, Nov 18, 2016 at 9:32 PM, Billy Stiltner <billy.stiltner at gmail.com>
> wrote:
>> re: "Yeah it would be but the sticking point is going to be the small
>> amount of crypto stuff that websockets require. Not impossible mayb"
>> it's all in here,
>> https://sourceforge.net/projects/websocketserverinapatch/files/
>> looks like  lots of things could be simplified as well as
>> use of the vanilla netrecieve
>> i don't have tof/toasci or would test it out
>> one thing i dont undrstand about  aciles is why the 2nd netreceive within
>> the server?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20161122/5addb2d9/attachment.html>

More information about the Pd-list mailing list