Fork me on GitHub
#hoplon
<
2016-08-02
>
micha00:08:03

@flyboarder: you're on fire

flyboarder00:08:59

@micha: yeah sorry for the spam, thought I'd fix up some of the brew hops

micha00:08:36

no not at all! this is the best kind of spam šŸ™‚

micha00:08:02

pretty stoked over here

flyboarder01:08:39

šŸ˜„ building things for hoplon is fun

micha01:08:08

it would be cool to do an online meetup

flyboarder01:08:42

Yeah! Would love to, just started a sketch for a live coding series's on making a blog spa with hoplon

flyboarder01:08:09

But an online meetup would also be sweet

micha01:08:10

sweet! looking forward to that

micha01:08:53

yeah there are many cool things in the works, it would be fun to get together and check it out

micha01:08:49

the ui kit libraries are especially exciting to me, i want to be free of the giant boat anchor dragging me down

micha01:08:57

(bootstrap lol)

flyboarder01:08:32

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

flyboarder01:08:59

It's easier to build with visual components I think

flyboarder01:08:08

Then hook those components to javelin

micha01:08:44

that's really all i need to do my work

micha01:08:55

i don't need to invent new UX paradigms

flyboarder01:08:44

Almost at the point where we could make a drag and drop UI builder

micha01:08:06

the next frontier is the state machines i think

micha01:08:37

once we have ui kits, we just need to figure out awesome ways to connect them to the workflow state machines

micha01:08:49

at that point the UI will be a solved problem i think

flyboarder01:08:56

State machines is defs on the brain lately, I wrote material UI to use dynamic bindings for all the options it supports

micha01:08:57

and it will be great

flyboarder01:08:46

So things like :ripple-effect don't need to be passed in everywhere that supports it

micha01:08:23

yeah totally

micha01:08:47

they dynamic var thing has worked well for me

micha01:08:55

really cleans up the code a lot

flyboarder01:08:52

Oh much nicer to look at

flyboarder01:08:21

And it makes more sense when you see it in use in many components

flyboarder01:08:34

Like to wrap your head around

micha01:08:53

removing the boilerplate lets you see jus tthe things that are needed

micha01:08:20

rather than lots of unimportant boilerplate code

flyboarder01:08:11

@micha: mostly i like abstracting all those class and style strings into keywords

flyboarder01:08:41

strings are hard to debug, keywords logically make more sense in the code

flyboarder18:08:19

@thedavidmeister: I am looking at the secretary example, and there are 2 things i noticed that I think we could simplify.

flyboarder18:08:53

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.

tbrooke18:08:13

@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

flyboarder21:08:54

@micha is there work already being done on splitting jquery out of core? like a branch to track or pr?