This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-04-06
Channels
- # admin-announcements (17)
- # beginners (78)
- # boot (162)
- # braid-chat (2)
- # cider (20)
- # cljs-dev (9)
- # cljsjs (41)
- # cljsrn (17)
- # clojure (98)
- # clojure-austin (5)
- # clojure-brasil (1)
- # clojure-dusseldorf (1)
- # clojure-greece (1)
- # clojure-ireland (2)
- # clojure-italy (1)
- # clojure-japan (5)
- # clojure-russia (128)
- # clojure-uk (2)
- # clojurescript (29)
- # core-async (1)
- # core-logic (7)
- # css (1)
- # cursive (12)
- # datomic (18)
- # devcards (1)
- # dirac (6)
- # emacs (31)
- # funcool (28)
- # hoplon (208)
- # jaunt (66)
- # jobs (1)
- # juxt (6)
- # lein-figwheel (14)
- # off-topic (9)
- # om (83)
- # om-next (6)
- # onyx (63)
- # overtone (1)
- # parinfer (2)
- # protorepl (23)
- # re-frame (27)
- # reagent (14)
- # ring-swagger (8)
- # slack-help (2)
- # spacemacs (1)
- # untangled (56)
@ckarlsen: and may I ask you, if you can spare a gist of how you are using it, please? That would be awesome
that Victory library looks awesome. I'd like to know how to use that too, @ckarlsen
Wow I was able to load that in http://cljsfiddle.com
thanks so much @ckarlsen: I've never actually seen adapt-react-class used in anything but re-natal before!! Quite easy to use :O
Here's a more involved one: http://cljsfiddle.com/#gist=76289b7500a39349051bef8a2ad3aced
what do people use for communication between components at a distance ? i've got a simple core.async pubsub mechanism https://www.refheap.com/df4ee52e0604006633a5ad182 - are there other solutions in use ?
Hey all, I’m interested to know how people are writing async request handlers in re-frame. I’ve inherited a project that makes requests in a handler inside a go block and then dispatches an event once the response returned. Seems a bit of an anti-pattern because the first event doesn’t mutate the app state, it just fires the request off and waits for the response.
Okay I’ve scrolled up a bit and found the ‘Talking to Servers’ page. Seems like how it’s done. Np
Yeah, I use to do it that way. And it's not that the first handler doesn't return an updated db: it can update some :loading?
flag for example, apart from firing the request
@mccraigmccraig: Could you please explain what you mean? Is it communication between components on one level of hierarchy or between far levels of one hierarchical path?
Quasi off topic: How do you guys work with a designer/CSS-writing workers when using re-frame? Any cautions or problems?
@mccraigmccraig: generally you don’t want components to be communicating, they should mostly be just depending on app-db
@danielcompton: i've got a couple of cases where they need to... in the one i'm looking at atm there's a textfield which was backed by app-db, but perf was bad on crappy mobiles so i'm trying out backing it with a reagent-atom, but this requires coordinating with app-db when things happen far away (such as navigation)
@nidu the two cases i've come across were several levels apart in hierarchy and in one case required multiple responders for an event
@mccraigmccraig: the bad perf is on any optimization level (:none, :simple, :advanced)? do you have any re-frame middleware enabled (debug can be particularly heavy)?
@nberger :simple
and no middleware outside of dev-mode (and the perf problem is in production-mode)
ok @mccraigmccraig, would be nice to know where's that bottleneck, just wanted to discard options
no, that's just my concept configured from a goog-define ... in dev-mode i do schema checking and logging in middleware, in production neither
hmm is it possible to run the chrome devtools profiler on cljs ? that would be useful