This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-07-11
Channels
- # arachne (5)
- # beginners (28)
- # boot (59)
- # cider (10)
- # cljs-dev (10)
- # cljsrn (10)
- # clojure (58)
- # clojure-brasil (2)
- # clojure-czech (9)
- # clojure-miami (1)
- # clojure-poland (2)
- # clojure-russia (12)
- # clojure-spec (16)
- # clojure-sweden (1)
- # clojure-taiwan (1)
- # clojure-uk (77)
- # clojurebridge (3)
- # clojurescript (108)
- # cursive (5)
- # datomic (25)
- # defnpodcast (2)
- # editors (1)
- # events (1)
- # funcool (24)
- # hoplon (37)
- # instaparse (1)
- # lein-figwheel (7)
- # leiningen (7)
- # luminus (3)
- # off-topic (9)
- # om (90)
- # onyx (88)
- # proton (3)
- # protorepl (9)
- # re-frame (30)
- # reagent (23)
- # rethinkdb (2)
- # untangled (33)
- # vim (1)
- # yada (6)
@niwinz: hey! I started reading the UXbox code, cool stuff 👍, were there any particular things that served as inspiration for the event abstractions?
the WatchEvent is a clever idea and it's also nice that events can be Update+Watch in one because they're just protocols
and watch receives the main stream so it can react to posterior events for cancel/abort stuff
tipical case for autocomplete backed by backend that allows cancel xhr requests if the user writes quickly
> and watch receives the main stream so it can react to posterior events for cancel/abort stuff I'm not sure I understand. Are WatchEvents cancelable? how? (maybe there's an example in the code?)
the basic is, in watch event you trigger some async stuff and in same time subscribe to main stream for watch if more events of same type are emited by the ui
ah ok, I see, saw the stoper
thing before but didn't fully understand it's utility.
any reason you don't use positional record constructors?
about the other topic, maybe is not clear the purpose on simple view but is very very useful