This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-05-02
Channels
- # announcements (7)
- # aws (3)
- # babashka (132)
- # beginners (38)
- # calva (3)
- # chlorine-clover (6)
- # clara (1)
- # clj-kondo (20)
- # cljs-dev (24)
- # cljsrn (9)
- # clojure (76)
- # clojure-dev (1)
- # clojure-germany (4)
- # clojure-india (2)
- # clojure-uk (24)
- # clojurescript (15)
- # conf-proposals (1)
- # conjure (114)
- # cursive (3)
- # fulcro (63)
- # graalvm (1)
- # helix (2)
- # joker (10)
- # juxt (1)
- # local-first-clojure (2)
- # meander (9)
- # off-topic (97)
- # rdf (4)
- # re-frame (7)
- # reagent (16)
- # reitit (1)
- # rum (9)
- # shadow-cljs (48)
- # spacemacs (3)
- # tools-deps (3)
- # vim (30)
- # xtdb (10)
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 đŸ˜„
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 đŸ™‚
Yes, the thing is that with the current "interactive results" plug-in customizations can be first-class
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
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