This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-27
Channels
- # aws-lambda (3)
- # beginners (3)
- # boot (327)
- # capetown (2)
- # cider (156)
- # cljs-dev (368)
- # cljsjs (13)
- # cljsrn (53)
- # clojure (403)
- # clojure-czech (5)
- # clojure-dev (4)
- # clojure-greece (2)
- # clojure-russia (72)
- # clojure-spec (12)
- # clojure-uk (129)
- # clojurescript (156)
- # core-async (1)
- # cursive (33)
- # datomic (35)
- # emacs (10)
- # events (1)
- # hoplon (4)
- # jobs-discuss (3)
- # klipse (1)
- # lein-figwheel (14)
- # leiningen (5)
- # luminus (5)
- # off-topic (15)
- # om (69)
- # om-next (2)
- # onyx (2)
- # parinfer (15)
- # perun (12)
- # re-frame (30)
- # reagent (7)
- # ring-swagger (8)
- # spacemacs (10)
- # specter (6)
- # untangled (69)
- # yada (13)
@chromalchemy ok cool, CSS is definitely bigger than layouts
also, this is what i do to enable garden inline
(defmethod hoplon.core/do! :garden
[el _ v]
; Replace all the inline styles on an element with css generated by Garden.
; Obviously does not play nice with other methods of setting inline styles.
(let [vs (if (sequential? v) v [v])
css (garden.compiler/compile-style vs)]
(.setAttribute el "style" css)))
@thedavidmeister Cool, thanks for that. Does this work with updating values dynamically with Javelin? (Maybe in the garden code?) One thing I like about using classes is that I can do this pattern to make the garden styling dynamic: (div :class (cell= {:myclass (boolean-function)}