This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-04-08
Channels
- # admin-announcements (7)
- # aws (5)
- # beginners (37)
- # boot (39)
- # cider (4)
- # clara (2)
- # cljs-dev (32)
- # cljsjs (1)
- # cljsrn (12)
- # clojure (235)
- # clojure-austin (3)
- # clojure-belgium (7)
- # clojure-berlin (11)
- # clojure-dev (36)
- # clojure-france (10)
- # clojure-japan (10)
- # clojure-poland (2)
- # clojure-russia (39)
- # clojure-uk (4)
- # clojurescript (81)
- # code-reviews (9)
- # core-async (6)
- # core-logic (1)
- # datomic (32)
- # editors (7)
- # emacs (1)
- # hoplon (191)
- # jobs-discuss (14)
- # juxt (4)
- # lein-figwheel (4)
- # leiningen (3)
- # off-topic (7)
- # om (49)
- # onyx (34)
- # other-lisps (1)
- # overtone (11)
- # parinfer (1)
- # proton (5)
- # re-frame (11)
- # reagent (12)
- # spacemacs (2)
- # untangled (90)
- # yada (15)
anyone got React.addons.TransitionGroup working with Reagent (not the CSSTransitionGroup) ?
Are there any tips on tracking down performance issues with reagent? I am using secretary and cljs-ajax with reagent and in many places I am passing the app-state
. although it's fast in terms of loading data there seems to be slowness in the animations of transitions or when using external javascript libs.
i haven't really explored Om myself because reagent was way too easy to comprehend and build something without knowing anything so I've kinda stuck with it
@naomarik: I was getting weird issues with the atoms and cursors, and trying to on-board new people into the code was harder than expected. Reagent it turned out made the code look simpler. I do use create-class
for a few things, all in all it's been going along well. I'm just not quite sure how to optimize the code or find out the culprit for misbehaving components. The use of ^{:key ...}
has been my goto for now, just not sure what else after that.