This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-02
Channels
- # admin-announcements (3)
- # architecture (5)
- # beginners (10)
- # boot (223)
- # cider (13)
- # cljsjs (2)
- # cljsrn (50)
- # clojure (208)
- # clojure-austin (16)
- # clojure-belgium (1)
- # clojure-india (1)
- # clojure-poland (13)
- # clojure-russia (130)
- # clojure-spec (27)
- # clojure-uk (144)
- # clojurescript (135)
- # css (2)
- # cursive (10)
- # datavis (1)
- # datomic (29)
- # dirac (9)
- # funcool (2)
- # hoplon (41)
- # jobs (3)
- # leiningen (6)
- # om (37)
- # onyx (20)
- # pedestal (1)
- # planck (1)
- # proton (4)
- # re-frame (45)
- # reagent (17)
- # rethinkdb (16)
- # ring-swagger (19)
- # schema (5)
- # specter (93)
- # sql (16)
- # test-check (33)
- # untangled (7)
@flyboarder: you're on fire
@micha: yeah sorry for the spam, thought I'd fix up some of the brew hops
š building things for hoplon is fun
Yeah! Would love to, just started a sketch for a live coding series's on making a blog spa with hoplon
But an online meetup would also be sweet
yeah there are many cool things in the works, it would be fun to get together and check it out
the ui kit libraries are especially exciting to me, i want to be free of the giant boat anchor dragging me down
Yeah It's one of the things I think Angular had over hoplon was the UI kits, but now that we have both semantic and material, that might bring the new kids around
It's easier to build with visual components I think
Then hook those components to javelin
Almost at the point where we could make a drag and drop UI builder
once we have ui kits, we just need to figure out awesome ways to connect them to the workflow state machines
State machines is defs on the brain lately, I wrote material UI to use dynamic bindings for all the options it supports
So things like :ripple-effect don't need to be passed in everywhere that supports it
Oh much nicer to look at
And it makes more sense when you see it in use in many components
Like to wrap your head around
@micha: mostly i like abstracting all those class and style strings into keywords
strings are hard to debug, keywords logically make more sense in the code
@thedavidmeister: I am looking at the secretary example, and there are 2 things i noticed that I think we could simplify.
First the anonymous cell=
and r
could be wrapped together. Second the defroute
is essentially just a wrapper for setting cells so we could wrap that and parse any arguments into a cell=
. This way the app.route
ns provides the route cell handling and query-params as 2 exposed cell=
ās and a defroute
wrapper. Then we can put that into a hoplon.secretary
ns in brew.
@micha @flyboarder Let me add š for an online meetup - Iām still a newby but really enjoying Hoplon - Seems like Hoplon and Boot have about the most activity on Clojurians slack
@micha is there work already being done on splitting jquery out of core? like a branch to track or pr?