This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-07-08
Channels
- # admin-announcements (1)
- # arachne (3)
- # beginners (17)
- # boot (36)
- # bristol-clojurians (1)
- # cider (4)
- # clara (10)
- # cljsjs (11)
- # cljsrn (20)
- # clojure (134)
- # clojure-austin (2)
- # clojure-boston (1)
- # clojure-czech (1)
- # clojure-greece (128)
- # clojure-norway (1)
- # clojure-romania (1)
- # clojure-russia (17)
- # clojure-spec (106)
- # clojure-sweden (1)
- # clojure-taiwan (1)
- # clojure-uk (41)
- # clojurescript (122)
- # component (4)
- # cursive (1)
- # datomic (34)
- # editors (57)
- # emacs (12)
- # events (5)
- # hoplon (18)
- # instaparse (1)
- # jobs (9)
- # keechma (9)
- # lein-figwheel (3)
- # luminus (1)
- # om (47)
- # onyx (31)
- # proton (2)
- # re-frame (7)
- # reagent (3)
- # rethinkdb (1)
- # specter (25)
- # sql (2)
- # untangled (21)
- # yada (1)
@dobladez: don't get too caught up in what's ephemeral and what's not. Life is a lot easier all around if you put everything (as much as possible) in app-db.
If your taste requires it, put the more persistent state in one place within app-db, and the more transient in another place (path). But as a general rule have all state in app-db, if you can.
@mikethompson: Thanks, point taken. I recently run into a similar case: highlight newly added items in a list. I first implemented it in app-db, but then moved to using a timeout to switch a local ratom. I didn't like having a new subscription, dispatch call and handler function just to switch a boolean flag. More importantly, logic remains locally contained and not spread out into different places.
I'm thinking that may be I could have generic/reusable subscriptions and handlers for this cases. This might address my concerns
Entry and exit animations are a royal pain in the behind currently.
Other annimations are fine.
Even entry ones are not too bad (CSS will get you there). But it is exit annimations!!