This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-03
Channels
- # aleph (1)
- # beginners (42)
- # boot (34)
- # cider (157)
- # cljs-dev (12)
- # cljsrn (3)
- # clojure (165)
- # clojure-conj (1)
- # clojure-india (1)
- # clojure-italy (6)
- # clojure-russia (20)
- # clojure-spec (27)
- # clojure-uk (173)
- # clojurescript (116)
- # cursive (30)
- # datomic (87)
- # devcards (1)
- # docs (9)
- # emacs (2)
- # ethereum (2)
- # events (2)
- # fulcro (60)
- # graphql (10)
- # hoplon (2)
- # jobs-rus (6)
- # keechma (1)
- # lein-figwheel (9)
- # leiningen (36)
- # luminus (2)
- # mount (3)
- # off-topic (16)
- # om (14)
- # onyx (12)
- # pedestal (19)
- # portkey (107)
- # re-frame (9)
- # reagent (5)
- # ring (26)
- # shadow-cljs (149)
- # spacemacs (3)
- # sql (6)
So, semantic UI react doesn’t yet work with the new npm libs support, but the cljsjs version is fine, and all of the components in it offer a completely controlled version, meaning they are excellent for use with Fulcro. I’ve been playing with them, and like them quite a bit.
problem with semantic ui is that it dumps styles into style element
which blows for css
so you need to go through their theme system to change things
which is not good enough when you want to, say, vary color of text depending on the data, then you have to spam CSS with important
I still need to figure out how to make my JS files smaller, any trivial site is 1MB js file at least
@tony.kay trying ot use the easy http server, but can't start it... when I try I get:
CompilerException clojure.lang.ExceptionInfo: Error in component :config in system com.stuartsierra.component.SystemMap calling #'com.stuartsierra.component/start {:reason :com.stuartsierra.component/component-function-threw-exception, :function #'com.stuartsierra.component/start, :system-key :config, :component #fulcro.server.Config{:value nil, :config-path "/usr/local/etc/fulcro.edn"}, :system #<SystemMap>}, compiling:
I have wrote at the "/usr/local/etc/fulcro.edn"
with a basic {:port 8890}
am I missing something?
@wilkerlucio I admit the error message leaves something to be desired…
I created with current user, and I can read with that
cat /usr/local/etc/fulcro.edn
{:port 8890}
od -c /usr/local/etc/fulcro.edn
0000000 { : p o r t 8 8 9 0 } \n
0000015
maybe it's broken, this is all the code i'm using:
(def my-server (atom (easy/make-fulcro-server
; components available in query/mutation env:
:parser-injections #{:component-key :config})))
and I wonder if we could send the config inline, my use-case for this is just for a dev server (there is a different pipeline for prod that is used here, but it's bad for dev)
I just left it there from the cheatsheet example
So, config file is configurable via a param, or via a JVM option, just for that reason
For dev I often put the EDN on the classpath, and use a relative path (which reads resources)
why don;t allow an option to the make-fulcro-server
?
(def my-server (atom (easy/make-fulcro-server
:config {:port 8890}
:parser-injections #{:config})))
could be complementary, in my use case I have no need to change it
and -Dconfig
can be used from the command line on JVM to swtich it (takes precedence)
I just think the simplest uses shoud be available, and the current case has no inline (the simplest) case, only indirect ones (via file path or external launch config)
yeah, and it still failing here =/
can you try to run on your side? maybe it got broken at some point accidentally
I'm using fulcro 1.0.0
humm, weird
same thing
but it's fine, let's not take a lot of time on it, I have an alternative here anyway, I was just trying to simplify it
yeah, probably
I just pushed a very light wrapper project for semantic ui: https://github.com/fulcrologic/semantic-ui-wrapper
v 1.0.0-SNAPSHOT is on clojars. Makes using Semantic UI components in Fulcro quite easy
it just contains factories for the UI elements, and symbols for all of the icon names. I hope to integrate the docstrings from the react project, so that we can see the props via cljs docstrings