On 6/30/2019 1:05 AM, Miller Puckette wrote:
> Any advice would be very helpful!
Stay in the HTML format.
Following https://www.w3schools.com/html/html_basic.asp anyone can come
up with an object documentation.
HTML is the way to go. No need for latex, md, or whatever. HTML is
really simple
On 6/30/2019 10:41 PM, Miller Puckette wrote:
> The gotcha is that I can't find a way to typeset equations in native HTML...
How about making the rendered image (of the math equation) with
https://www.codecogs.com/latex/eqneditor.php and include the image in
the HTML doc. (isn't this is what
On Sun, Jun 30, 2019 at 08:30:40PM +0200, IOhannes m zm??lnig wrote:
> On 6/30/19 6:05 AM, Miller Puckette wrote:
> > Any advice would be very helpful!
>
> personally, i'd go for markdown as the source format and use pandoc to
> compile it to the final documentation.
>
> reasons:
> - the source
>
> For the moment I'm planning to just put an attempt at documentation for
> > slop~
> > on my own page and point to it from the slop~ help file (which will require
> > fixing Pd to be able to open URLs).
>
>
> This is what I don't get. How would you "fix Pd" to open URLs? With the new
>
Em dom, 30 de jun de 2019 às 02:52, Miller Puckette escreveu:
> To pd dev -
>
> I'm struggling to finish the design of a slew-limiting low-pass filter
> (slop~) to add to Pd vanilla
>
Yay!
> Make Pd able to open files in the native OS (maybe via a new "pdcontrol"
> object that would issue
