The basic kernel is working at this point, and you can get it here: https://github.com/abingham/jupyter-elm-kernel
But there's still quite a bit to be done, and some of the design decisions I made might be short-sighted. Take it for a spin and let me know what you think. Any feedback, ideas, PRs, etc. would be great. On Mon, Apr 10, 2017 at 5:48 PM Michael Lamb <mlamb...@gmail.com> wrote: > Are you still looking for a hand with this, Austin? > > I'm not an expert, or anything but I'm really interested in making a good > Jupyter kernel for Elm to use with nteract. If you haven't seen it, check > it out: https://nteract.io/ > It mimics Jupyter as a desktop application, so you do not need a server. > > > On Monday, March 27, 2017 at 12:10:33 PM UTC-6, Austin Bingham wrote: > > Hi everyone, > > I started hacking a bit today on a Jupyter notebook kernel for elm. You > can see it here: > > https://github.com/abingham/jupyter-elm-kernel > <https://github.com/abingham/jupyter-elm-kernel> > > It doesn't quite work yet, though, and I think I need help from someone > who knows javascript/requirejs/web stuff a bit better than me. The proximal > problem I'm seeing is that when jupyter tries to run the elm-make-generated > javascript, it thinks that 'Elm' is undefined during (I think) some part of > the AMD machinery. Jupyter show this as the output for the cell: > > Javascript error adding output! > ReferenceError: Elm is not defined > See your browser Javascript console for more details. > > As far as I can see, Elm *should* be defined, and certainly the generated > code looks like any other Elm output I've looked at. So I'm a bit stumped. > > My approach to the kernel is currently very simple. The kernel is > implemented in Python, and it receives a blob of Elm source code. I dump > this to a temp file, use a subprocess to run "elm-make" to make the output, > read the output, and ship it back to jupyter. As far as I can see, all of > that is working properly. I run into problems when jupyter tries to execute > the stuff I return. This design may or may not be optimal in the long run, > but I want to get the plumbing working first. > > So if someone feels up to the challenge, I'd love any help I could get. > This seems like it should be pretty straightforward, but perhaps I'm being > naive and/or missing something obvious. > > Of course, I'm also happy to discuss other aspects of the kernel (e.g. > design, compilation technique, etc.), but my priority is to just get > something into an output cell. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Elm Discuss" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/elm-discuss/4VUQuYukGXM/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > elm-discuss+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
