@grant Sure, what kind of project would you be using Antizer for?

@priornix I will need to read up more on Ant Design and try to find a good place to try it out. Most likely it'll end up being some sort of basic CRUD app. I may also look at it as a front end for a automated system, providing a dashboard with few override and adjustment controls. Having it already integrated with Fulcro would make it easier to reach for. I enjoy learning new things, but try not to tackle too many at once.

@grant Cool, sounds great. Just let me know if you need any pointers.

Hello friends, is there an online demo of book/bootstrap

I see many of the bootstraps v3 component that I would like to use

hi, I'm evaluating Fulcro for a new project, mostly reading through the docs right now, and one thing my project will have heavy need for that I don't see discussed at all in the documentation is, how do I map derived state to UI?

Not sure what 'derived' state is. But it is the queries in the components that in the end are grabbing the data/props that end up in the UI.

by "derived state" I mean, let's say I have a list of things, and I want to display their count. Is there a way to query that without either manually storing that in the app db or computing it in the view?

in re-frame I'd define a subscription as (rf/reg-sub :things/count (fn [db] (count (:things db))) and then subscribe to that

my actual use-cases are quite a bit more involved but these sorts of derived calculations are the bread and butter of the data analysis tool I'm building

You could have another component that has that state in it (the count). Your mutations would have to re-compute it every time if it is derived.

that's what I figured

ok, thanks

Derived values are discussed in the book: http://book.fulcrologic.com/#_derived_values.

that's what I figured

slack doesn't let me paste into the webpage version of the app anymore for some reason

but it's advocating for either storing the result in the app db or doing the computation in the view

in my experience neither approach works well

@mattly after a lot of fulcro coding, in my experience derived values are better to be defined at your server level, instead of loading data and calculating in the client, you can give that derived value a name (keyword) and just ask for it on the client, this can reduce complexity at your client code considerably

heh

this is an electron app

that's fine, by server I mean your network layer, even if it's full client side you can still leverage code separation by having a local parser that will do the async operations (like loading data from anywhere)

for writing the parser I recommend pathom (disclaimer: I'm the author of it): https://github.com/wilkerlucio/pathom

For anyone interested in charting I translated a JavaScript chart/app that uses React Vis into a Fulcro app, and wrote a Medium article on it: https://medium.com/@cjmurphy/using-react-vis-from-clojurescript-787d02281f7c

I’m working through the book and when we create (def ui-person (factory Person {:keyfn :person/name})), what is :keyfn doing?

@joshua.d.horwitz its the fn thats used to generate the key attribute on the child elements for react indexing

oh ok, thanks

more here https://reactjs.org/docs/lists-and-keys.html

and there are no :ident, is that no always needed?

@joshua.d.horwitz it's recommended to have :ident most of the time, without it your component data will not get normalise (this is sometimes desired, but most of time should be avoided as it can lead to data duplication / reduced consistency)

I’ve always wondered why om.next didn’t default to using the ident when keyfn wasn’t specified

@matthavener probably because key is very much a react only concern and om.next didn’t want to be too much magic

but that’s just my guess

What is a good strategy to indicate to the user that "loading..." is going on while :started-callback is occupied? I know you can put the loading indicator on the index.html file itself. But is there a way to bring up a loading indicator without doing this?

I guess I want the 'default UI' to come up, hopefully without resorting to SSR or routing. This is for the simple React Vis demo above. At the moment the user sees nothing in the browser window, and then sees a big chart. I would prefer the user to see my simple loading (dom/div "I am loading") div during the initial moments while the local data is being loaded into app state.

I tried this in the :started-callback and it worked, so this is my solution for now