This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-12-21
Channels
- # aatree (5)
- # admin-announcements (3)
- # beginners (13)
- # boot (25)
- # cider (4)
- # cljs-dev (2)
- # clojure (107)
- # clojure-austria (2)
- # clojure-japan (12)
- # clojure-russia (128)
- # clojurebridge (2)
- # clojurecup (32)
- # clojurescript (68)
- # css (4)
- # cursive (3)
- # datascript (4)
- # datomic (8)
- # devcards (25)
- # hoplon (19)
- # immutant (2)
- # ldnclj (4)
- # liberator (2)
- # luminus (5)
- # off-topic (184)
- # om (78)
- # onyx (2)
- # portland-or (11)
- # re-frame (27)
- # reagent (11)
- # yada (3)
Eyeballs wanted! I've implemented a very light-weight server notifications channel in hoplon using castra. See https://github.com/laforge49/simple-notifications
The idea is that there is a single poll loop for moving all types of notifications, in batches, to the client. The client maps notification types to functions which process the notifications. When creating a notification, you must provide the client session id, the notification type and the value to be processed by the client-assigned function.
@micha: OOPS! Still need to add a bit of code to the client side to preserve order and avoid duplicates.
@micha Client side now sorts and filters incoming notifications. So again things are finished. Over to you then for review and repackaging.
I'd like to initiate a GET REST to an existing service from a Hoplon client to populate list, fields, etc.. Can't do Castra for now. I haven't seen any mention of this. Anybody done this?
@symbit: hoplon ships with jquery, and you can use the jquery stuff for doing ajax, jsonp, etc
then in the callback, reset some input cell
then build views/behaviors off that cell