Fork me on GitHub
#chlorine-clover
<
2020-05-02
>
mauricio.szabo23:05:32

I just though of something: on this new version of Chlorine, I'm adding sci as a new dependency. This means that, if we hook it right, it can be possible to extend Chlorine in ClojureScript đŸ˜„

đŸ‘€ 4
mauricio.szabo23:05:01

I do think the current approach of using Atom's init scripts is a good one too, but maybe by changing a little bit we can even live-code configs, so no more Atom reloads to see if init scripts did work... don't know yet on how to do it, but it's quite possible đŸ™‚

sogaiu23:05:31

seems quite interesting!

mauricio.szabo00:05:46

Yes, the thing is that with the current "interactive results" plug-in customizations can be first-class

mauricio.szabo00:05:26

It means that you can evaluate anything, and when you get the result the user can decide how to render that result - even if it involves further interactions with the REPL

mauricio.szabo00:05:59

So, if there's a better way to make it easier for the user to write these interactions... maybe we can see some interesting developments