This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-02
Channels
- # aws-lambda (1)
- # beginners (46)
- # boot (190)
- # cider (12)
- # clara (6)
- # cljs-dev (9)
- # cljsjs (8)
- # clojure (152)
- # clojure-austin (3)
- # clojure-berlin (3)
- # clojure-finland (2)
- # clojure-france (5)
- # clojure-italy (3)
- # clojure-russia (92)
- # clojure-serbia (4)
- # clojure-spec (7)
- # clojure-uk (190)
- # clojurescript (115)
- # cursive (20)
- # datomic (20)
- # dirac (4)
- # emacs (9)
- # gsoc (5)
- # hoplon (1)
- # jobs (1)
- # klipse (4)
- # lein-figwheel (1)
- # leiningen (6)
- # lumo (2)
- # mount (18)
- # off-topic (57)
- # om (68)
- # om-next (14)
- # onyx (33)
- # perun (32)
- # portland-or (4)
- # re-frame (21)
- # reagent (85)
- # ring (6)
- # ring-swagger (23)
- # schema (1)
- # uncomplicate (1)
- # untangled (13)
- # vim (7)
@drcode: Have you any example code about how to use and integrate blueprint components in om.next? I mean the workarounds and hacks you mentioned before. I'm curious how to use the blueprint components.
@mruzekw yes, the Om Next parser runs in Clojure too
with regards to Om.next .... what's the proper use of merge!
I know it says novelty but does that come in the form of a 'whole new atom ... or just the bit I want updated?
novelty is just the new stuff
a map
Okay... so even if it's buried deep in the atom someplace...
in that case you want to provide novelty in a shape that matches your app's query structure
and probably define a merge-tree
strategy if the default doesn't fit your needs
Okay. What's the difference between merge and merge-with?
And would it be best to never manage the app-state-atom myself, and always wrap things in the read fn? It seems like a better division of interests
is there a preferred way to get all of a query’s “root” keys? e.g., given [{:foo/a [:bar/y :bar/z]} :foo/b ({:foo/c [:bar/q]} {:params [:x 2]})]
I want :foo/a :foo/b :foo/c
. I could write a function to do it, but wasn’t sure there wasn’t already a way
(map :dispatch-key (:children (om/query->ast query)))
thanks!
solved an old question about joining nested components. http://app.klipse.tech/?cljs_in.gist=hlolli/1ed18c0c5481af99cd13da86db16ca11&container=1 if someone's interested to learn/criticize.
I posted very similar code where component C
was not getting the data it was querying for. So here the recursive parser comes to the rescue.
hello guys, I just did om-next
tuto but I feel I am not ready yet to build production code
any advices on where to go from tutorial to being a beginner ++ ?
resources or anything ?
@baptiste-from-paris read some useful blog posts from https://anmonteiro.com/, watch some of Tony's videos https://www.youtube.com/user/tonythekay read om-next code in the wild from http://github.com
@hlolli you’re talking about the untangled
videos right ?
i’ll give it a try to => https://www.martinklepsch.org/posts/om-next-reading-list.html
yes, not to underestimate untangled but for learning then I say dont overestimate untangled in such a way that you can learn it without understanding of om.next (in the client part of that forementioned framework).
ok, thx
does it greatly simplify your life (untangled)
ok, thx
I was asking about Om vs Re-frame in another channel. One person mentioned a hypothetical weakness of Om is that David is the main contributor. Question: if, one day, David decides he no longer likes Clojure and decides to only program in PHP, what happens to Om ?
Why is that a weakness?
David's also the main ClojureScript contributor, and that has been going on for 5 years and counting
It's a weakness in the same since of "What happens to Linux if Linus gets hit by a bus" weakness. If there isn't a team around David, it may be safer to use a different library.
@qqq Om works fine as it exists now, so it's not really that big of a factor. (Though sure, it's always nice when more people are involved in core development of a project instead of less)
it’s mostly a strength IMO - to have a leader on one project
If mr David decides for any reasons PHP is his new passion, I think someone else will eventually take it’s place
just to be clear, I'm not in anyway attacking David; my main concern, before betting a commercial project on Om, in terms of 'de-risking' -- is, God forbid, something happens to David, what happens to Om.
I don’t agree, it’s open source, you can still read the code and make it you own project
what else do you propose ? having guys like David not contributing because you have a commercial risk ?
it’s like buying an Oracle licence because you are afraid of MySQl core contributors taking holidays
@baptiste-from-paris : I never made the suggestion of "having guys like David not contributing because you have a commercial risk ?" -- please do not accuse me of things I did not say.
oh no, it’s juste a conversation, no hard feelings :-
What I am wondering is if there is a team around David who can continue developing the library if something happened to David. Much like how if Linus was hit by a bus, there's a number of deputies to maintain the various parts of the kernel.
This is probably also not helpful to #om, we can discuss this offline if we're interested (though in all honesty, I don't thin either of us really find it interesting at this point.)
I'm mostly interested in what Om.next appears to solve, and I'm looking for a tutorial assuming I already know the other libs.
haha ok 🙂
in retrospect, that should not have been my first question in #om -- not sure what type of positive answer I was expecting 🙂
so I was looking at https://www.youtube.com/watch?v=xz389Ek2eS8 -- which seems interesting, because reagent/reframe doesn't solve the problem of "streaming data from the server to my client"
Is there a nice tutorial for using Om.Next that does both server side and client side? I think if I saw something that showed how data streamed in Om.next, I'd be able to finally get what it's about.
@qqq you may want to watch David's talk at the 2015 Conj
^ in this one he really goes over lots of topics
may be hard to follow as a beginner, but watch it in steps