Fork me on GitHub
#fulcro
<
2018-07-27
>
wilkerlucio15:07:19

hello people, just release an article on how to wrap regular React components to use with Fulcro, hope you enjoy it 🙂 https://medium.com/@wilkerlucio/using-any-react-ui-kit-with-fulcro-82cce271b9cc

😁 20
currentoor17:07:03

hey buddy, this is really neat!

currentoor17:07:12

i know some people were put off by the primitive dom syntax we inherited from om.next (hence the appeal of soblano in reagent, rum, etc)

currentoor17:07:51

but i feel like the one we ultimately settled on is just as expressive but much more performant, and has CSS hooks

currentoor17:07:27

it’s really cool to see how those internals could be repurposed for arbitrary JS components!

wilkerlucio20:07:23

glad you enjoyed man, I figured that when I was trying to port the reakit, the pieces have a good separation so we can reuse, thanks to @U0CKQ19AQ

tony.kay23:07:52

Actually, @U09FEH8GN helped out on that one

wilkerlucio09:07:39

nice job for both of you 🙂

thheller10:07:05

FWIW in my react stuff I have a simple generic (dom/native rk/Image {} ...) helper fn (actually just called $ to be shorter). saves creating all the factory fns and can use the macro trick

thheller10:07:14

($ rk/Heading :.head {:as "h3"} "Card Heading") is good enough imho and can be more performant due to the macro tricks

tony.kay16:07:07

Ah, and i forgot!!! The new dom stuff was heavily based on the work and ideas of @U05224H0W

tony.kay16:07:35

Sorry bout that. Thanks Thomas

currentoor23:07:49

yeah we totally copied all of @U05224H0W’s great ideas!

tony.kay15:07:57

I pushed a new snapshot @bbss that updates update-state! to correctly use setState internally. The bug in that would not have affected you unless you called update-state more than once in a sequence on the same value…so it is unlikely it mattered to many applications