This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # aws (1)
- # beginners (52)
- # boot (1)
- # cider (9)
- # clara (4)
- # cljs-dev (40)
- # cljsrn (2)
- # clojure (168)
- # clojure-dusseldorf (1)
- # clojure-italy (34)
- # clojure-spec (13)
- # clojure-uk (35)
- # clojurescript (337)
- # cursive (11)
- # data-science (47)
- # datomic (11)
- # emacs (3)
- # events (1)
- # fulcro (58)
- # hoplon (16)
- # jobs-discuss (1)
- # juxt (11)
- # keechma (21)
- # mount (2)
- # off-topic (42)
- # onyx (9)
- # re-frame (33)
- # reagent (1)
- # ring-swagger (3)
- # spacemacs (1)
- # specter (2)
- # test-check (37)
@scknkkrer you asked a vague, poor quality question, got no answer and then lashed out with some snark. That comes off as "entitled". Note: people are getting their questions answered (by volunteers) in here ALL THE TIME. But yours wasn't. Think about that. What does it tell you? Perhaps you should be asking yourself what it was about your question that caused it to not be answered? I feel like you might benefit from reading this "classic", regarded by many as the the gold standard in advice on the subject of asking technical questions: http://www.catb.org/esr/faqs/smart-questions.html
@profgra I try to never have data in a component local state. I always try to put all state in app-db, perhaps via
:on-blur (rather than
:on-change) where possible.
The moment we have state in two places, you have to synchronize it. Now, we can certainly find ways to do that. But (as you suggest) my advice is to avoid needing to do it whereever possible.
@sandbags yeah, re-com uses Bootstrap for largely historical reasons. But hard now to evolve that forward. The criticisms about its lack of "ambient classes" is very valid (in effect, every
div should have a class on it which you, the users of the library, can provide a style for, perhaps via Garden?)
We were very influenced by the idea of using in-line syles when we wrote it. That seemed like a very good idea at the time. We're slightly older and wiser now. We still want our CSS to be colocated with the components (and not off in a remote CSS file, if possible), but these days, if we were doing it again, we'd probably do it with Garden.
Just want to take the opportunity to thank those volunteers (yourself in particular, you’re very active here!) for answering all of the questions I’ve answered so far :beers:
I guess so, but I've really only seen these "constants" / "enums" used in redux code bases.
Ok, my fault. How do you guys navigation on react native application with re-natal: re-frame + reagent ?
Hey @scknkkrer it's tricky as there's not that many examples about. http://reactnavigation.org seems to be one of the most promising options, although there's a library from wix too. I've been using http://reactnavigation.org library with reframe thanks to @seantempesta 's library https://github.com/seantempesta/cljs-react-navigation. He's helpfully put together specs for all of the router / screens etc which helps understanding what you have to provide all of the components with.
There's not much documentation about because there's not many people doing it I think!
yeah I don't really 100% understand what's going on either, it's quite hard to follow, with all this
The reframe approach is close to the redux approach. Trouble is that's an "advanced" topic in the reactnavigation docs. https://reactnavigation.org/docs/guides/redux
If I were you I'd clone sean's library above and have a play with it there's a reframe example in the repo
FWIW I'm using a version of http://tachyons.io that I've recreated in Sass on my project, have been for a year. My CSS is 10k and I rarely touch it.
This is different from inline styles in some important but subtle ways that are difficult to understand without actually working in this style of CSS
but that's besides the point; I feel like the main problem people are trying to solve with overrideable/customizeable css is to somehow separate structure from appearance
that is, position/float/flexbox vs color and font-size, and the gray area of things like border-widths and the box model in between