This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-09-03
Channels
- # admin-announcements (241)
- # beginners (53)
- # boot (134)
- # cider (20)
- # clara (3)
- # clojure (170)
- # clojure-argentina (13)
- # clojure-brasil (1)
- # clojure-canada (3)
- # clojure-italy (9)
- # clojure-nl (3)
- # clojure-russia (55)
- # clojurescript (115)
- # code-reviews (18)
- # cursive (8)
- # datomic (14)
- # events (8)
- # hoplon (51)
- # immutant (38)
- # jobs (8)
- # ldnclj (11)
- # melbourne (6)
- # off-topic (2)
- # om (5)
- # onyx (9)
- # re-frame (3)
- # reagent (8)
- # sneer-br (1)
- # sydney (1)
- # testing (14)
we often see this pattern, where we have some static and dynamic classes at the same time on a DOM element:
((div :class "some static classes")
:class (cell= {:dynamic (...)})
...)
sometimes the order is important too, so ideally i would like to have something like... for example:
:class (cell= [:some :static {:dynamic (condition)} :classes])
i was also thinking about intermixing inlined kw val pairs with hash-maps, since kids are either dom elements already or vectors or nil
why i was asking is because then the macro u mentioned can actually return a {:class (cell= ...)}
i want to release the homepage with the latest hoplon rig, as a single page app, with backend connection, at least to staging tomorrow
hmm... how am i supposed to use the current route-cell
function?
i got stuck at that implementation which had different implementations for different number of parameters
should i do a (def route (route-cell))
to initialize routing and just compare that route
cell afterwards?
it was actually quite nice in the past how it embedded the cell if u havent provided one from outside
it created a cell if u havent provided it as a parameter and every subsequent call was just returning that cell