Fork me on GitHub
#reagent
<
2015-10-17
>
nowprovision06:10:38

@kidpollo why was google's css framework easier to roll your own components with than say bootstrap etc..

kidpollo06:10:40

materializecss is not from google

kidpollo06:10:59

its a bootstrap-like implementation of the google material design spec

kidpollo06:10:03

there are many out there

kidpollo06:10:14

I like that one

kidpollo06:10:38

thought it looks great and works great with reagent

ul06:10:17

http://www.getmdl.io/index.html — this one is from google

pupeno07:10:26

How can I make things that appear and desapear by means of reagent have an animation?

mikethompson12:10:37

@pupeno: not sure it is exactly matches your needs, but have you seen the work of @rohit : http://blog.ducky.io/reagent-motion-demos/

bherrmann13:10:20

I'm trying to create a single page application in reagent.

bherrmann13:10:27

when editing the page via figwheel, a change will show up immediately (for the first edit)

bherrmann13:10:46

Then after that, no more reloading.

bherrmann13:10:51

The error in the JSConsole is "Warning: Error unmounting: util.js:261 Error: Invariant Violation: ReactMount: Root element ID differed from reactRootID.(…)"

bherrmann13:10:19

I'm wondering why, of course.

bherrmann13:10:03

It also emits this warning... Warning: React attempted to reuse markup in a container but the checksum was invalid. This generally means that you are using server rendering and the markup generated on the server was not what the client was expecting. React injected new markup to compensate which works but you have lost many of the benefits of server rendering. Instead, figure out why the markup being generated is different on the client or server: (client) <html data-reactid=". (server) <div class="navbar na

bherrmann13:10:06

but I'm not sending markup from the server... I do have functions which generate "the page's" contents, and they do vary based on the application state.

bherrmann13:10:37

I guess I should work through the tutorial, and then try and model my application on a smaller scale... so I can isolate what it is that I'm not doing the "reagent/react" way

bherrmann13:10:24

and/or I should investigate reacts's warnings... "Warning: render(): Target node has markup rendered by React, but there are unrelated nodes as well. This is most commonly caused by white-space inserted around server-rendered markup."

bherrmann14:10:13

Turns out I was doing something weird, namely using :html as the root element (reagent/render [myroute] app-elem-id) with myroute (defn myroute [] [:html ... ])

bherrmann14:10:07

which was just strange. I then sprinkled the ":key XX" on one of my vectors. And now reagent/react appears to be calmed. And my updates are working. Whoo Hoo

bherrmann14:10:59

So sweet to have figwheel's instant updates working again!!

bhauman21:10:56

Found out why devcards reagent integration is a bit rough: https://github.com/reagent-project/reagent/issues/195