@bnoguchi: nice, looking forward to it

anyone else notice a significant performance difference between om next apps on chrome and firefox?

welp, disabling logging made a huge difference. chrome seems to handle that much better than ff.

@seanirby: Compared to om now you mean?

urbanslug: no I mean om next

Oh I get what you mean, the difference is in between browsers

yeah

I thought it was in between versions of Om

firefox nightly feels much faster

Gotta go, talk later.

Just wondering, when will Om be upgraded to react v15.0?

Anyway, if someone is as excited to use svg shadows in OM, then do this

[org.omcljs/om "1.0.0-alpha32" :exclusions [[cljsjs/react]
                                                             [cljsjs/react-dom]]]
                 [sablono "0.6.3"]
                 [cljsjs/react "15.0.0-0"]
                 [cljsjs/react-dom "15.0.0-0"]

can someone recommend a good example of an app that does things like switching in different components? I think I've got the individual component concepts down, but would like to see it in a less-isolated context.

For example, nav bar on the left lets you select "Books" or "Movies" -> main area switches to a book-list component or movie-list component (assuming those need to be fundamentally different components)

(I tried looking at CircleCI's frontend, but it's got a LOT happening that makes it harder for me to see the components + routing + state + ___ = app)

@curtosis: You might have seen this already, but I’ve found this example app helpful. http://jannis.github.io/om-next-kanban-demo/

It may not speak directly to “switching”, but it might be worth a look.

https://github.com/Jannis/om-next-kanban-demo

@seanirby: chrome/firefox run smooth over here, safari is a nightmare

@kendall.buchanan: thanks, that looks closer to what I'm looking for!

does anyone have a good example of a modal component they built in om next?

When you edit a card (other things too) in the Kanban demo mentioned above, then you (as user) are in a modal component.

@cjmurphy: ill take a look thanks

@cjmurphy: i was looking more for a reusable modal component, that you just pass in some props to

a component that the board-dialog and card-dialog could use, in this example

Quick q: Is the read function within the parser only applied to the query contained in root component?

on the first render, yes

@isak: Cool, thanks.

but when you trigger mutations you can trigger other queries