This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-04
Channels
- # arachne (1)
- # beginners (41)
- # boot (92)
- # capetown (8)
- # cider (10)
- # cljsjs (4)
- # cljsrn (42)
- # clojure (94)
- # clojure-india (1)
- # clojure-russia (48)
- # clojure-sanfrancisco (1)
- # clojure-spec (34)
- # clojure-uk (13)
- # clojurescript (29)
- # cursive (12)
- # datavis (4)
- # datomic (10)
- # dirac (63)
- # editors-rus (16)
- # emacs (57)
- # funcool (5)
- # hoplon (22)
- # jobs (2)
- # lein-figwheel (3)
- # leiningen (5)
- # onyx (51)
- # other-languages (2)
- # proton (1)
- # protorepl (2)
- # re-frame (34)
- # remote-jobs (1)
- # sfcljs (5)
- # spacemacs (1)
- # specter (2)
- # sql (20)
- # test-check (54)
- # yada (1)
@jasongilman: I talked with the ink team about the loading widget but they now use a loading bar on the bottom. I tried it but in my opinion it is not clear enough (see here: https://files.gitter.im/JunoLab/Juno/OHJC/loading.png) as I totally overlooked it until I had saw the previous picture. They also linked me the source code of the old loading widget (see here: https://raw.githubusercontent.com/JunoLab/atom-ink/master/demos/eval.gif). I would like to know your opinion on that matter. I would prefer the old loading widget but that would mean that the code would have to live on proto-repl itself not on atom-ink, meaning, one more (possible) thing to maintain.
@carocad: I'm ok with it going in Proto REPL source code. I've done that with the tree view from atom ink already since I made some Proto REPL specific changes to it.