fulcro

Book: http://book.fulcrologic.com, Community Resources: https://fulcro-community.github.io/, RAD book at http://book.fulcrologic.com/RAD.html
xceno 2020-10-13T11:13:51.280Z

There's the decimal-field in fulcro-rad-sematic-ui , how can I add support for internationalization to it? Should I just replace the :https://github.com/fulcrologic/fulcro-rad-semantic-ui/blob/develop/src/main/com/fulcrologic/rad/rendering/semantic_ui/decimal_field.cljc#L13 or use fulcro-i18n and do something more "clever" ?

exit2 2020-10-13T16:34:22.281500Z

Is the preferred way of writing custom css for a Fulcro application through the fulcro-garden-css lib?

wilkerlucio 2020-10-13T16:42:07.281600Z

yes, via the :css part of the components

tony.kay 2020-10-13T16:45:40.281800Z

Localization isn’t done yet. For now, you can just install a new “style” of control that does what you need and install it as a UI control and select that style for the control in your form

tony.kay 2020-10-13T16:46:06.282Z

Using a more advanced and localized control is the eventual full solution

tony.kay 2020-10-13T16:46:26.282200Z

“preferred” is a tough question, IMO

wilkerlucio 2020-10-13T16:47:16.282400Z

right, I think better to say "I prefer it", hehe, I love the css isolation I get with fulcro and garden, so I like it, but Tony is right, if you don't like it, totally fine to don't use too

tony.kay 2020-10-13T16:47:41.282600Z

Here’s how I look at it: If you’d like your component to have css that is name-munged so it does not conflict with other css libs, then it is a convenient way to do it. Ultimately, that is really all the lib does: namespaces the css classes to the component in question. It’s perfectly reasonable to hand-write small app customizations in a simple css file (or use sass/less/etc) or a theme for semantic ui, etc.

tony.kay 2020-10-13T16:48:21.282800Z

So, a library author that is trying to make exported and reusable controls for Fulcro might choose to do component-localized css just to make it easier to pull into your app.

tony.kay 2020-10-13T16:52:06.283Z

but I personally do not use the feature on my own apps 🙂

tony.kay 2020-10-13T16:52:25.283200Z

(I hate writing css, so I lean very heavily on pre-written libs of css that I can theme)

👍 1
tony.kay 2020-10-13T16:55:47.283400Z

and for minor tweaks I just use :style

exit2 2020-10-13T17:03:58.284Z

thanks all

exit2 2020-10-13T17:04:36.284200Z

I’m hoping to lean heavily on a css framework and have very minimal custom css 🤞

xceno 2020-10-13T18:01:48.284400Z

I see, alright that'll do. Thanks!

2020-10-13T18:54:24.284700Z

I've been happy using emotion css-in-js with fulcro: https://dvingo.github.io/cljs-emotion/#!/dv.cljs_emotion.devcards

👀 1
fjolne 2020-10-13T21:39:44.295600Z

for me the major pain-point in dynamic CSS (fulcro-garden-css & :style) is that it’s hard to apply a build pipeline to it: autoprefixing & minification depending on prod/dev env also hard to do complex styles which span multiple components i’m mostly using TailwindCSS + classic CSS files with PostCSS for reusable components and complex stuff, rarely fulcro-garden-css (mostly for custom grids & custom at-media breakpoints)