This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-12-03
Channels
- # admin-announcements (8)
- # beginners (99)
- # boot (60)
- # cider (44)
- # cljs-dev (47)
- # cljsrn (68)
- # clojure (223)
- # clojure-art (1)
- # clojure-russia (190)
- # clojure-sg (9)
- # clojure-uk (2)
- # clojurecup (1)
- # clojurescript (59)
- # clojurex (3)
- # core-async (43)
- # core-typed (2)
- # cursive (18)
- # datavis (7)
- # datomic (16)
- # events (2)
- # funcool (3)
- # hoplon (3)
- # jobs (1)
- # lein-figwheel (10)
- # leiningen (6)
- # off-topic (1)
- # om (123)
- # onyx (57)
- # parinfer (16)
- # portland-or (2)
- # random (1)
- # re-frame (4)
- # reagent (7)
- # remote-jobs (1)
- # spacemacs (12)
@tmtwd: re-frame is an alternative to om
I dont know much about om, but my understanding is it is perfectly compatibile with something like re-frame. You just need to port it..
Well, om is somewhat more than just view layer (as reagent is), so this might be awkward.
om (original) was pure view, like reagent. As I understand it, om.next tries to provide more architecture.
Well, it wasn't exactly pure view if it was opinionated about the shape of state (single atom, using cursors etc.). In reagent you can implement it this way or another.
you needed to do some reify
stuff with om, right?
Yeah, it used protocols to implement React lifecycle events, reagent has this - https://github.com/Day8/re-frame/wiki/Creating-Reagent-Components#form-3-a-class-with-life-cycle-methods - with sugar for common case.