@ghopper we put a lot of effort into re-frame-10x, so that burned most of the "open source budget" we had available across the last 8 months. But yeah, we'll get around to that stuff in the next 6 months.

I'm kinda interested in doing what's necessary to get re-frame into a better position for doing state machine based UIs.

That, to me, is the next interesting frontier

/docs/EPs is where all thinking goes when there's time

But we'll "promote" stuff from EP stage to real Github issue for general comment when there's enough maturity

@mikethompson Thanks for the update. The 10x stuff is super cool, and I'm very interested in the state machine UI stuff. Thanks for clarifying the EP stuff as well.

State machines rock. This a weird one: https://codepen.io/kennytilton/pen/aGJxMm?editors=0010 JS to make CodePen happy. It simulates an asynchronous chip circuit by having an FSM for each wire. The weird thing is that the only input to the FSMs is the tick of a clock.

why am i gettin re-frame: no :event handler registered for:

cljs.core.Keyword {ns: null, name: "initialize-db", fqn: "initialize-db", _hash: 230998432, cljs$lang$protocol_mask$partition0$: 2153775105, …}
cljs$lang$protocol_mask$partition0$
:
2153775105
cljs$lang$protocol_mask$partition1$
:
4096
fqn
:
"initialize-db"
name
:
"initialize-db"
ns
:
null
_hash
:
230998432
__proto__
:
Object

(ns bus-routes.db)

(def default-db
  {:page :route
   :coord nil})

(ns bus-routes.events
  (:require [re-frame.core :refer [dispatch reg-event-db reg-sub]]
            [bus-routes.db :as db]))

;;dispatchers
(reg-event-db
 :initialize-db
 (fn [_ _]
   db/default-db))

calling

(defn init! []
  (rf/dispatch-sync [:initialize-db])
...

always eval new subs/events

Are you sure your bus-routes.events ns is getting required by the ns that calls init!?

yes

i expected figwheel to load that on save but it didnt once i eval-ed ns - it worked

the tooling for reframe is getting pretty badass. i just got 10x working and big kudos to the team there. i just need to figure out a way to make the epoch replay work with a halted async-flow fx …

Hey all, I have a structured DB like this:

[:devices [:docs [:data ["assignedDate" "1992", "owned" "FALSE", ...]

(re-frame/reg-event-db
 ::owned-updatedb
 (fn [db [_ owned-val]]
   (update db :devices assoc :owned owned-val)))

I know this is simple, but that is my noob level

Why not have a different shaped DB? For example a map?

This DB is pulled in from Firestore, so not sure how I would do that

{:devices {:docs {:data {"assignedDate" "1992"
                         "owned" "FALSE"}}}}

Well you could just convert ur vector into something else i guess?

How do you get ur data?

As a JSON or something?

Yes I believ eJSON

https://github.com/clojure/data.json#converting-keyvalue-types

So you could use data.json to take ur json and turn it into a map for u

(json/read-str "{\"a\":1,\"b\":2}"
               :key-fn keyword)

would produce {:a 1 :b 2}

i believe

i gotta go but ill check this slack in like an hour

brb

Ok thanks. I'm going to keep going through this https://github.com/deg/re-frame-firebase before Itry a new idea

Thank you

@guy figured it out, I needed to use update-in to find the entry

ok nice one @aaron993 !

hi everyone. I have a scroll event listener, that saves the scrollTop in app state. and then I have a few sticky components, that use this subscription. I’m using rf/dispatch to save the scrollTop in state. and whenever I do this, and when I scroll the page up and down, those sticky components are a sort of jiggling a bit

and if I change rf/dispatch to rf/dispatch-sync, then it works fine (it becomes proper smooth). and I was wondering why is this happening? is there an explanation to this?