This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-07
Channels
- # aleph (3)
- # aws (7)
- # beginners (117)
- # boot (119)
- # cider (2)
- # cljs-dev (3)
- # clojure (193)
- # clojure-austin (1)
- # clojure-dusseldorf (4)
- # clojure-finland (5)
- # clojure-france (5)
- # clojure-italy (7)
- # clojure-portugal (1)
- # clojure-russia (204)
- # clojure-serbia (5)
- # clojure-spec (31)
- # clojure-uk (64)
- # clojurescript (288)
- # community-development (9)
- # core-async (54)
- # cursive (8)
- # datascript (18)
- # datomic (26)
- # dirac (8)
- # emacs (26)
- # figwheel (1)
- # hoplon (16)
- # jobs (2)
- # jobs-discuss (4)
- # juxt (1)
- # lein-figwheel (4)
- # leiningen (14)
- # london-clojurians (2)
- # lumo (17)
- # off-topic (44)
- # om (63)
- # om-next (2)
- # onyx (26)
- # perun (14)
- # planck (5)
- # portland-or (34)
- # proton (2)
- # protorepl (8)
- # quil (1)
- # re-frame (6)
- # reagent (16)
- # remote-jobs (4)
- # ring (7)
- # ring-swagger (10)
- # rum (1)
- # untangled (2)
emccue: I’m guessing from the context that you were referring to my question on HammerJS and Reagent. Problem solved and thus Reagent and HammerJS do play nice with each other. Discovered however that SVGs [on iOS] do not respond to touch events unless they have some kind of contents (e.g., full-width and height rect). Not sure this is a SVG spec effect, an iOS [browser] bug, or a Reagent one.
The iOS issue it beyond my experience, but you can also probably get the HammerJS interop working in a similar way to d3.js (for which there just happen to be more resources and tutorials for working with)
don't see a reason not to use multiple arities
usually I recommend the pattern (defn my-comp [{:keys [a b c] :as props} & children])
because it matches non-reagent React components
but I think that's a matter of style mainly
although I don't see a need to use r/props
in the render method
and you can just use r/argv
instead of r/props
to access everything
yeah I agree it's annoying there