Make it all configurable.

[jperon]

This is quite a big change. The idea came from @paulfitz’ message: with this one, it would be possible to create standalone widgets from the code of a "personalized" one.

With that, the name pug_py doesn’t say all it does: it’s now starting from a configuration, that will define an entrypoint (for example a pug or a py code) and possibly other editors.

Another change is that it now uses RapydScript instead of Transcrypt or Brython (or PyScript that I tested too), as it’s far easier to interact with js. The only caveat I saw is that, for functions which really expect a pure Array (like grist.docApi.applyUserActions), it’s necessary to call the Array constructor, or to convert a python list with Array.from(LIST).

[jperon]

I had tested in my self-hosted instance, where the widgets are hosted in the same domain as Grist itself. Now I’m facing cross-origin problems while hosting at docs.getgrist.com. Perhaps I’ll have to go back to Brython…
@berhalak if you had time (but I don’t want to abuse), would you mind looking at this and, if possible, explain me what I’m doing wrong?

[jperon]

@berhalak Never mind, I ended finding the problem. It came from RapydScript, which builds an iframe, but which used, to pass messages between the iframe and its parent, a "pythonesque" equality. This one used an __eq__ property, and its access was forbidden because of CORS.

[jperon]

So here is a very basic showcase, featuring a customizable Markdown widget.

[jperon]

And here is a new version of the Kanban widget, which could very easily be put into its own repository, and whose configuration is more straight forward than the previous one.

[berhalak]

Sorry for the delay @jperon, it was busy week for me.