This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-03-06
Channels
- # admin-announcements (1)
- # aws (12)
- # beginners (35)
- # boot (12)
- # cider (32)
- # cljsrn (5)
- # clojars (10)
- # clojure (20)
- # clojure-russia (60)
- # clojurescript (229)
- # community-development (14)
- # cursive (9)
- # data-science (4)
- # datomic (3)
- # funcool (2)
- # hoplon (29)
- # jobs (15)
- # jobs-discuss (53)
- # keechma (2)
- # luminus (8)
- # om (42)
- # onyx (15)
- # parinfer (22)
- # re-frame (12)
- # reagent (162)
- # spacemacs (1)
if anyone’s interested in trying parinfer in nightcode, i built and uploaded a snapshot: https://github.com/oakes/Nightcode/releases/tag/1.1.0-SNAPSHOT
i wrote a new indent system from scratch that uses tools.reader to figure out the proper indent. maybe overkill but it seems ok so far
i updated paren-soup as well, and it’s using the same indentation and undo/redo code as nightcode, so it’s an easy way to try the behaviors out: http://oakes.github.io/paren-soup/
only downside to this change is that nightcode is like 12MB larger 😃 not sure why, maybe it’s the kotlin dependency. it’s worth it though
The size increase is surprising though. I thought Kotlin’s runtime + standard lib came out to be less than 1 MB
Hey guys, wanted to mention that we added a feature to cljsfiddle. http://cljsfiddle.com/#gist=6a609b6af5430a4be97d
@sekao: just tried out the new nightcode and paren-soup versions
works well! surprised that you were able to share code between them
@escherize: nice addition
I was looking at doing this for the parinfer demo site with firebase
I’m guessing you do some Gist API calls on the backend to save snippets?
was hoping to use firebase to skirt the backend requirement
nevermind, just looked at cljsfiddle.gist
. i’ll just do that then!
@shaunlebron: yeah i was surprised too…i wrote it all in paren-soup first, then broke the code out into their own libraries and made them cljc files. one of my first experiences with clj/cljs code reuse, it was pretty cool
that’s cool, tag-soup and mwm, just perused them a bit
@escherize: Interesting that you went gitlab, was pretty confused I couldn't find it on github. I'm really interested to watch how gitlab shapes the github empire.
@dominicm: @escherize: I’ve considered moving the Cursive issues to Gitlab because their issue handling is a lot better and their dev process is more open, but I’m worried about this discoverability issue so I shelved the idea for the moment.