Fork me on GitHub
#om
<
2017-02-03
>
drcode01:02:12

Blueprintjs bindings for Om/OmNext: https://github.com/drcode/blueprint-cljs

drcode01:02:46

In my opinion, Palantir's Blueprintjs is a perfect companion for Om/OmNext: It gives us a boatload of high quality components with a minimal overhead. I hope the community will give it closer a look!

dvingo01:02:00

wow, this is really nice, thanks!

drcode01:02:48

@danvingo be sure to read the caveats at the end of the README.md (lt;dr: still very alpha)

dvingo01:02:58

for sure, i'm digging through the code

baptiste-from-paris10:02:52

hello guys, newbie question for om.next I don’t understand why the the read function received :parser & :query in the env (it’s obvious why :state is passed)

drcode12:02:22

If a query is nested (as most queries are) then Om Next will not parse the child query automatically, by design. Instead, you either have to call db->tree (if your state is normalized and you don't care about possibly sending extraneous information) our you need to call ((:parser env) env (:query env))

baptiste-from-paris12:02:14

yes, i've found the solution in @tony.kay github tuto

baptiste-from-paris12:02:55

i still struggle a little but it's a lot of fun :-)

qqq20:02:11

does om.next ezpect lcojure on server side, or can one use hy on server side and use om.next still ?

baris21:02:45

@drcode: thanks for sharing the blueprintjs "hack"