Fork me on GitHub
#reagent
<
2015-12-19
>
mpdairy00:12:05

in case anybody is interested, I made a demo Todo List app using Posh, which is a lib I wrote that lets you easily use DataScript to store a single app state for Reagent. Here's a link: https://github.com/mpdairy/posh-todo

mpdairy00:12:32

It was really easy to write. the hardest part is thinking up the database schema, so I'm excited to write a real app with it, though I have to think of a good way to sync the DataScript db with a back-end Datomic db first

eggsyntax00:12:18

@mpdairy: psyched to check that (and Posh) out. I’ve been thinking of adding DataScript to our Reagent front-end anyway, and this seems like a really nice way to go about it.

mpdairy00:12:34

i think you'll like it if you like DataScript since you pretty much just use q, pull, and transact! to get things done. I've never really used regular Reagent or Om so I'm curious to know if Posh is much easier to use

mpdairy00:12:19

do you happen to have any good ideas for syncing your DataScript db with a Datomic back-end?

eggsyntax00:12:37

I haven’t actually used DataScript or Datomic before — I’m interested in exploring that model, though, and using DataScript as a front-end DB with Reagent seems like a good way to experiment.

eggsyntax00:12:37

(hence no idea on DataScript/Datomic syncing — my understanding from David Nolen’s talk at the conj was that Om Next is going to address that, so you might check out how he’s approaching it)

mpdairy00:12:24

Oh right I had heard that Om Next could use datomic for the state

mpdairy00:12:27

I'll check it out

eggsyntax00:12:58

and/or DataScript, with what sounded like at least some degree of transparent syncing.

eggsyntax00:12:44

It’s a great (and almost hilariously fast-paced) talk simple_smile

eggsyntax01:12:38

Just went back & rewatched part of it; if you don’t want to watch the whole thing (though I recommend it) there’s a section on caching starting at 32:35 and then a section on client-side storage at 35:28.

mpdairy15:12:52

@mikethompson: you know how in Reagent the reactions aren't actively looking for changes unless they are in components that are actually loaded and rendered? is there some way to tell when reactions go dormant because their components are no longer loaded in the react tree?

mpdairy15:12:19

or really, I just need a list of actively listening reactions