I want to acknowledge @holyjak’s help, too — I recorded the sessions we’ve done, as well. I’ll get to those after I process the Tony Kay sessions.

Awesome, thanks a lot for sharing, and for putting all the effort into making these available and even more useful for people!

Whoa! This is incredible. Thanks for sharing.

Thanks very much! This is a great resource.

I agree. I've just finished the first video and it is so helpful - great to see the interactions and explanations and undo some of the assumptions about how things work from the ground-up. Thank you both.

amazing. thank you for this!

See https://github.com/fulcrologic/fulcro-rad-semantic-ui for a complete component library using Semantic UI Doesn't need to be as complete just implement the components you need

thank you

what if I don't want to use RAD and use Fulcro base libraries instead ?

this looks like it's heavily baked in with RAD form component

For regular fulcro then just use them as you'd expect to 🙂

i think i'll have to try it out 😄

is there an example anywhere of using react component library and adding it to fulcro ? cause from the docs, i assume you have to use defsc and that manages state etc

sorry if my questions don't make sense

i'm not sure how the component will be called from within fulcro defsc

OK, so here are the general tips: you want the raw namespaces (raw.components and raw.application). The standard components and application are tied to React, as are a few other nses. Fulcro is “react first”, but not “react only”. The trick with doing alternate rendering is that you’ll have to install your own rendering function, which will just be called whenever a transaction changes state somehow (see the fulcro app constructor arguments). Then you’ll need to generate “components” that are compatible with the component options mechanishm (e.g. see http://raw.components.nc). The transaction/networking/data system relies on component options to find query fragments, idents, and initial state for initializing the state database.

thanks @tony.kay - i guess then this is not a trivial change. I was hoping that since Radix is built on React, that using Radix components would be straight forward

You say RAdix like I should know what it is.

A component library of React components

Then they will work fine

FUlcro is not about rendering. React is. Fulcro happens to use it, but unmodified. Fulcro is about data management. It does happen to integrate the two where necessary/convenient, but vanilla js components are usable. See book for examples/.

when you asked what kind of work and said “headless UI” and another thing I’ve never heard of I just assumed you were trying to use something other than react

Both are just plain old React component libraries, think there was just some confusion on React js => cljs from OP

yeah, cljs interop with js is easy

If you use a js React component to “hold” fulcro components then there is a little interop to do, but that is explained in the book

sorry if I confused you guys with my questions. Yes, headless ui and radix are react component libraries which are unstyled components, Radix has good support for accessibility features which is why it's quite popular. Like @U043RSZ25HQ mentioned, i was interested in knowing how easy or difficult it would be to use Radix react components in a fulcro project.