This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-12-29
Channels
- # adventofcode (11)
- # beginners (98)
- # boot (2)
- # cider (3)
- # clara (3)
- # cljs-dev (15)
- # cljsrn (2)
- # clojure (122)
- # clojure-austin (4)
- # clojure-russia (1)
- # clojure-spec (2)
- # clojurescript (30)
- # css (6)
- # cursive (5)
- # docs (1)
- # fulcro (4)
- # hoplon (118)
- # keechma (3)
- # leiningen (5)
- # lumo (1)
- # off-topic (28)
- # onyx (6)
- # re-frame (4)
- # reagent (1)
- # reitit (1)
- # shadow-cljs (53)
- # sql (1)
- # unrepl (1)
@akiroz that’s what I’m thinking re: the data structures. They’re one of my favourite things about Clojure/CLJS 🙂 But even with that awesomeness, I haven’t come up with a satisfying way to organize vanilla reagent CSS maps in Clojure.
In order to get what I want - the full functionality of CSS - without actually using stylesheets, I probably need to resort to stylefy
or garden
. Not sure I’ll have won anything, though, I don’t know them well enough. But I guess I’ll explore them next
One of the reasons that the data structures of Clojure are so awesome is because of how transparent the literals are. If I do too much merging or munging of any kind, really, that pro is somewhat lost.
Garden vs pre/post-processors being discussed on slant: https://www.slant.co/topics/217/viewpoints/12/~best-css-preprocessors-postprocessors~garden-clojure
If it's any contribution to the earlier discussion, I find styling my reagent apps with garden and garden-gnome to be a sheer joy (real-time updates of the site appearance in my browser)
And while it's probably standard in css processors, Garden's implementation of color-arithmetic ("inverse", "lighten 15%", "darken 30%") are nice