[L2Ork-dev] L2Ork-dev Digest, Vol 90, Issue 42

[Jonathan Wilkes]

On Sun, Apr 18, 2021 at 8:24 AM Prakhar Agarwal
<prakhar at everything.net.in> wrote:
>
> Hi Jonathan,
>
> First of all congratulations, we got selected into the GSoD program this year! The idea of loading interactive patch directly in documentation is great, it will allow readers to experiment with patches directly in the browser and hence improve learning.
>
>>
>> Hi all,
>>
>> We got accepted into the Google Season of Docs program!
>>
>> You can see our proposed idea here:
>>
>> https://git.purrdata.net/jwilkes/summer-of-code-ideas-list/-/blob/master/sod_idea.md
>>
>> This is the first time we've participated, so I'm still learning how
>> things will go. But if anyone has some input or would be interested in
>> participating, you can respond here on the list.
>>
>> Initial impressions of the proposal:
>>
>> Just re-reading what I wrote in the sod_idea.md, one question stands out:
>>
>> Are the Purr Data example patches included *inside* the flow of an
>> HTML page? Or, are the tutorials themselves Purr Data patches?
>>
>> My current opinion is the same as the one when I wrote the proposal--
>> we should make it possible to load an interactive patch in a blog post
>> in the same way that a library like d3 can load an interactive graph.
>> Currently the web app loads from an index.html file. So we'd need to
>> fix this up to load a patch in a div using a javascript method call,
>> plus a hook to specify the file to be loaded.
>
>
> Can you please describe in more detail what needs to be done? What changes are required?

Well, it could be done in a lot of different ways. I suppose the
simplest conceptually would be a single method, something like
"display_canvas" with two methods-- one to specify the target div, and
another to specify an optional file to be loaded there. For an
incremental approach, this could be a decent starting point.

If we get into displaying multiple examples in the same document, we
then must figure out some issues, like how does the frontend know
where to display a subpatch, and other details.

-Jonathan