F# plugin

[aolney]

I've been keeping an f# plugin alive for beaker

However this plugin diverged from the still maintained Jupyter plugin some time ago

Is beakerx going to be automatically compatible with existing plugins? My question/uncertainty is the extent to which beakerx will support multiple plugins in a single notebook and therefore require autotranslation extensions for those plugins.

[scottdraves]

thank you for your plugin!

what were the plugins of classic Beaker are now Jupyter kernels in BeakerX, so they really are quite different and not compatible.

We are going to make them fully polyglot the same way they are in classic Beaker. Autotranslation in this context is only a proof-of-concept Python/Groovy -> JavaScript (one way only). This is great for D3 at least but doing it for real is just on the drawing board: #5039

The autotranslation runtime from your f# plugin should be pretty portable to the jupyter kernel, and then it could participate.

[aolney]

So it sounds like the best approach would be

• Fork the existing F# plugin for Jupyter
• Add autotranslation BeakerX style that doesn't break normal plugin function (i.e. works without BeakerX)
• Do pull request with plugin maintainers

Does that sound reasonable? If adding autotranslation necessarily breaks the normal plugin, then I guess I should fork the Jupyter F# plugin as a completely new project, e.g. FSharpPluginX

[scottdraves]

correct. I don't see how it could break the normal function, if that seems to be the case please LMK and I am sure we can figure it out. good luck and please report back with the results! thank you.

[dsblank]

It would be nice if we could come up with a standard that could be adopted by all kernels.

[scottdraves]

Not sure what you mean. A standard for what?

[dsblank]

Would be nice to have a standard for "autotranslation for BeakerX style" that all kernels could adopt.

[scottdraves]

i couldn't agree more :)