This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-07-03
Channels
- # admin-announcements (21)
- # beginners (13)
- # boot (215)
- # cider (36)
- # clojure (24)
- # clojure-berlin (7)
- # clojure-japan (59)
- # clojure-korea (2)
- # clojure-russia (5)
- # clojure-seattle (1)
- # clojure-uk (5)
- # clojurescript (119)
- # clojurex (4)
- # code-reviews (4)
- # cursive (8)
- # editors (3)
- # euroclojure (27)
- # ldnclj (15)
- # off-topic (57)
- # re-frame (1)
- # reagent (108)
- # yada (3)
Regarding the tangled relationship between HTML, CSS and js: https://speakerdeck.com/chantastic/inline-styles-react-europe?slide=9 Via Clojurescript/Reagent it appears I'm living in the future. And that it will be insanely popular.
How do I change the port that boot runs on when I run boot dev
? I see serve is defined as (deftask ...)
with a port option, but I can't figure out where in boot.build to put the port.
Figured it out: need to run it as (serve :port <port-number>)
in build.boot.
However, now I am getting an out of memory error when I run boot dev
: java.lang.OutOfMemoryError: PermGen space ... Exception in thread "main"
Fixed: updated my JVM options and learned that export is specific to the current terminal...
hey @mikethompson what can :md-icon-name be? and where did the md- prefix come from
@escherize: See "found here" link on the left of http://re-demo.s3-website-ap-southeast-2.amazonaws.com/#/md-icon-button under "Notes".
Ahh. Looks as if the author of that icon font has updated it to use names that start with zmdi-
.. it used to be md-
md-
prefix is an abbreviation of material design
Right, so after a bit of poking around. That website is now all about v2.x of the icon font. re-com is still using version v1.x. Some docs about the old v1.x names here: http://zavoloklom.github.io/material-design-iconic-font/v1/
I normally use Chestnut - but this time I don't want any server components included..
@stephen: I like the figwheel template https://github.com/bhauman/figwheel-template
Great thanks, with an option to include Om as well.. Looks like it is being maintained as well.
@stephen: heh it’s true, I’ve just deprecated all my templates except for the standard mies one
What I would really like would be some kind of componentised template mechanism, so I could choose multiple templates to merge into my project.
@stephen: well all the templates are handmade now so that would not really be possible
but I've heard that boot plugins compose better
I think boot is looking promising for cljs
Much easier than messing around with lein-cljsbuild
@stephen: it’s not clear to me how you could ever arbitrarily compose different templates bits as they often imply different api calls, different initial side effects.
I kinda think templates are a pretty bad idea for reasons like that, and the fact that when the template changes, what do you do to your 10k line production app that's mutated bits of it
@stephen: as far as templates, what have you seen that’s popular beyond mies, chestnut, and figwheel?
I guess composable templates would need to be set up differently to reduce conflicts..
like every auto generated code templates are in general evil
useful in the beginning to get started
but that's it
I came across one the other day... darn it forgot which one it was.. but I would have liked to have merged it in to my chestnut project..
More specifically Duct https://github.com/weavejester/duct
I could use its template to create the server, but then I missed out on all the cljs setup..
can't talk about web app templates without mentioning http://luminusweb.net
lein new luminus kitchen-sink +postgres +aleph +auth +cljs +cucumber +swagger +sassc
http://martinklepsch.github.io/tenzing/ is one for boot
@escherize: I missed your cljs/d3 stream. Have you looked into saving videos somehow?
templates are really much better at demonstrating how things are setup and wired together, they have a lot of value as such, in this sense the shallower and simpler the better
Figwheel REPL inside of Cursive rocks, I’ve added some new simple instructions get it working https://github.com/bhauman/lein-figwheel/wiki/Running-figwheel-in-a-Cursive-Clojure-REPL
dnolen: one thing to note with this setup is that leinigen :profile merging won't happen. But a simple solution is for folks to explicitly inline their build config.
@bhauman: I don’t know what you mean, but I don’t really use Leiningen for app development
@dnolen: well you may be happy to know that you can om inside a ReactElement the same way that you can canvas or do anything else. Pretty cool actually says alot for React.
@stephen: that's really what I've been trying to do with http://modularity.org - templates are evil, but if what they generate is itself infinitely recomposeable they are less evil (perhaps?)
templates are composed of modules which are composed of components, so the whole thing lends itself to the a la carte approach you're asking for, but I haven't actually written the menu system yet
it's all data driven too
@malcolmsparks: interesting would like to see how that translates to ClojureScript applications, esp. Om/Reagent and tooling integration (browser REPL/figwheel)
it’s definitely either a manual affair or a template thing that doesn’t really compose as you say
@danielsz is doing a similar thing, and is doing interesting things with boot
everything in cljs is moving so fast, will be good when the dust settles a bit and we can think about composeable tooling
malcolmsparks: BTW, I’ve included a compatibility note on system’s README. I think it’s important to let users know they can mix and combine.
@dnolen: Awesome, thanks for that doc, I've been meaning to write it up based on jackjames' gist
@cfleming: yeah I found his gist and just put this together. figwheel + Cursive just seems like an obvious combo.
To get a feel for the dev experience you get when working with boot, there’s a tutorial + video @ https://github.com/danielsz/holygrail
@dnolen: No doubt! I'm planning to add a built-in CLJS REPL based on these configs Real Soon Now. That'll mean I can do the cljs.test integration too.
@danielsz: good stuff, I just learned about leaven and bakery from that
you're doing great stuff there, because really what everyone wants is the whole stack - om-next - graph-query - back-end - with tooling, and recomposeable at will
the cljs part of that is key
who wants a stack that doesn't include cljs these days?
the old refheap link is still pinned here and should prob be swapped out for the new figwheel wiki link. not sure if you pinned that @cfleming or if there is a Person In Charge of Pinning?
@jackjames it must have been the PICoP, it wasn't me
@malcolmsparks: Absolutely. In my opinion, Boot embodies Leiningen’s lessons learnt.
The proliferation of JVM instances when developing is not acceptable anymore. Building on what Leiningen taught us, Boot was designed to tackle the quirks of the JVM toolchain and the practicalities of the Clojure ecosystem.
@danielsz: I don’t actually have a real problem with running multiple JVMs especially on modern hardware. Still it’s nice to have a 1 JVM option I admit.
@dnolen: I’d probably do a disservice to Boot if I emphasize the 1 JVM instance too much. That’s just something that comes with the design, as a benefit. At its heart, it’s a rethinking of what a toolchain is and how to interface with one.
@danielsz: haha, yes that’s what I meant by it’s a hardware thing. But that’s where things have been and continue to head.
@dnolen: I’m in the same boat as you - I just busted my work machine, and any emergency building over the next week or so will be on a 2009-ish MBA 😞
@escherize: honestly the only thing that really annoys me is the lack of sleeping indicator and the lack of indicator light on the power plug
Still, that’s good to know. I’ll probably always need an MBP to run two instances of IntelliJ + Cursive and debug them.