This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # aws (3)
- # bangalore-clj (3)
- # beginners (40)
- # boot (53)
- # cider (1)
- # cljs-dev (124)
- # cljsrn (22)
- # clojure (105)
- # clojure-italy (1)
- # clojure-nl (3)
- # clojure-russia (35)
- # clojure-spec (9)
- # clojure-uk (30)
- # clojurebridge (25)
- # clojurescript (107)
- # datomic (18)
- # dirac (21)
- # events (6)
- # hoplon (29)
- # leiningen (5)
- # off-topic (40)
- # om (17)
- # onyx (25)
- # parinfer (2)
- # pedestal (4)
- # perun (2)
- # planck (1)
- # protorepl (6)
- # re-frame (18)
- # reagent (15)
- # ring-swagger (4)
- # specter (2)
- # test-check (7)
- # testing (3)
- # untangled (45)
- # vim (2)
Still set for a brief meeting about the interactive tutorial, and any other assorted topics in 40 minutes. Feel free to participate or watch. 🙂
So which part of the tutorial except aggregation and windowing would be most relevant to cqrs?
I’m really excited for this. It’s everything I always hoped we’d build as a community 🙂
I'll start playing with blueprint on the weekend and take any section once I get the hang of it
@colinhicks Nice work, I was having a slew of hangouts issues but I caught most of it. Currently busy this week but I hope to be able to knock out some of the tutorials after Friday.
Cool. Even if it’s not a whole section, the more examples we can build up in the better off we do. 🙂 Every contribution will help.
What’s the reasoning behind dispatching off of keyword->component rather than symbol->component?
(Assuming we're talking about keywords in the section layouts ... ) That's a good point—I didn't explore the latter. I got enamored with the symmetry of blueprint component & blueprint layout versus keyword identifiers in catalog task & (e.g.) workflows.
Guys, i'm just starting in onyx and i am still not capable help to much in creating tutorials. I used the blueprint and learn onyx tutorials to starting my study been very good for me. For now im trying to use onyx-datomic plugin and learn about windows and triggers. So i allways update the source from blueprint and ready new tutorials, i can comment about news tutorials from the new onyx user perspective. For now i gonna try build a tutorial from my case.
Using keyword -> component might be nice if we want to remote load a tutorial? Kind of like how Klipse can remote-load from a gist.
Dynamically rendering components from a gist won’t be difficult, but I’m not sure how we’d dynamically compose the component’s query back to the root.
The only reason I bring up the question about keyword/symbol component identifiers is because the tutorial layout looks so much like hiccup syntax already. I can appreciate the desire for symmetry there though. I don’t think its terribly important either way as long as the backing components are not tied to resolving keyword->component. I could see people wanting to use these components in devcards or their own projects, it would be nice if we could decouple our component resolution strategy from the component itself.
I don't think it blocks the tutorial-creation process at this stage, though, do you?
@michaeldrogalis I remember you mentioning
clojure.spec and namespacing all the catalog keywords, but I can't find usages of
clojure.spec in any onyx-platform repository except empathy. Did I imagine?
@yonatanel It’s on a branch using a Spec backport: https://github.com/onyx-platform/onyx/blob/cljc-triggers/src/onyx/spec.cljc