> Yes your right, I was just about to say “sorry for the noise”, is rather unpractical & very time consuming to port all *-help.pds. Also is rather irrelevant to make them “nicer”.
They can definitely be nicer, both in terms of readability and the ease of creating
and editing them. It's just difficult to figure out an interface that makes it easy
to do both.
>>> Also it could be an html file with the .pd part inside an <code> </code>.
>>That could be interesting.
>>From the user standpoint, it would make the most sense to be able to position a Pd patch (which is just an svg) inside the flow of a web page. So one could have a blog entry, webapp,
etc., and the Pd patch would be like an interactive image in it.
>>But that would require some significant development time to implement.
> I`m not sure if I get this, as I see it as a potencial “tutorial” which are already covered in the “help browser”.
That's a possibility. But currently you can't open an html file from the menu. You'd
have to open devtools and do it manually.
> I mean the patch inside the </code> is totally working except that you cant save it, right?
Currently there is no functionality that does that.
> We are opening a remote patch inside a nice html?
I'm not sure what you mean here.
-Jonathan
> Mensaje telepatico asistido por maquinas.