Add ability to run code examples in the playground

[SeanTAllen]

We had this sort of on the old tutorial but that didn't get migrated over.

[SeanTAllen]

I went looking through the mkdocs material for this functionality and didn't see it. I'm going to reach out to the author and see if I missed the functionality, otherwise, I'll put in a feature request.

[SeanTAllen]

So this is the report:

We can do some custom css and javascript. That's not really my thing, but someone could take this on.

squidfunk/mkdocs-material#3563

[shaedrich]

There doesn't seem to be a native option to add any other button than "copy" and "select" with the latter being sponsors-only:

I went looking through the mkdocs material for this functionality and didn't see it. I'm going to reach out to the author and see if I missed the functionality, otherwise, I'll put in a feature request.

Others have also wished for this functionality to become more generalized: squidfunk/mkdocs-material#4005 The only solution given there is to fork the theme.

However, one could add custom JavaScript to add this behavior: https://squidfunk.github.io/mkdocs-material/customization/#additional-javascript

To achieve a quick and easy solution, we could add buttons to all code blocks manually

Something, that would be more work but would prevent us from duplicating the code (once inside the code block and once URL-encoded in the button), would be to move the code to separate files and embed them. Alternatively, it could be gists.

This could also help in cases where the examples are longer than the URL is allowed to be by the browser (I don't know if we would run into that problem) 🤔

Or should the preview be in the tutorial, not just (in a new tab) in the playground?

[SeanTAllen]

We use the insiders build. So that is available as an option.

[shaedrich]

Yeah, but that is only the "select" button, not the "play"/"run"/"execute" button

[jemc]

The other nice thing about the idea of moving the code examples to separate Pony files, is that we easily could start including testing to prove that all the examples compile.

[shaedrich]

If it helps, this can be done in a separate PR, when other questions are not yet answered

[SeanTAllen]

@shaedrich are you interesting in tackling this? if yes, what additional information or discussion do you need from us?