Fork me on GitHub
#clojurescript
<
2015-09-12
>
mfikes00:09:47

@boz: Yes. As you've discovered, the Planck iTerm issue is fixed in master.

venantius00:09:52

There’s been a lot of pro-boot talk in this channel - I’m curious; are people using boot in both front-and-backend Clojure(script) projects, or are you managing these as separate projects and repositories?

masonbrowne03:09:41

Today I demoed an app written in ClojureScript to a 100+ engineers and directors in 4+ cities. They didn’t suspect a thing. I’m sneaking it into the enterprise right through the front door.

masonbrowne03:09:42

(cough also I’m still hiring cough)

martinklepsch08:09:51

@venantius: I nowadays often feel like separating backend and front end is nice but you can really do whatever you want

juhoteperi08:09:13

React 0.14.0-rc1 is now packaged in Cljsjs along with separate React-dom package

maria09:09:01

@dnolen: @jaen I’ve summarised some of my thoughts regarding the ES6ModuleLoader issue: https://gist.github.com/mneise/dc00508e5e9303fed12d 😉

ul11:09:09

when I do lein cljsbuild once with profile which has :optimizations :none, it does not pickup my cljc file, complaining that "java.io.FileNotFoundException: The file resources/public/js/dev/cemerick/url.cljs does not exist" with prod profile seems to be okay

ul11:09:43

does anybody have a clue where to dig?

jaen15:09:22

^ Funny picture of the day - the React library here is taken straight from npm, requires and all, put through some code derived from @maria's work on module conversion, then required as a GClosure module and appears to work in at least basic capacity. This is probably still light years away from being able to use libraries as-is (this is finicky as hell), but a small step et caetera.

dnolen15:09:31

@maria thanks for writing that up!

dnolen15:09:04

@shaunlebron: patch for that welcome simple_smile will be pretty busy with Om Next related things for a while.

dnolen15:09:42

@jaen that’s really cool, thanks for kicking the tires so much. It really helps push this along!

shaunlebron15:09:33

@dnolen: will do, have fun with om :)

masonbrowne17:09:36

@dnolen: re: ecmascript5-strict - no real reason for it. was just poking around and saw that things broke - wasn’t sure if it was something I did or an expected outcome.

adwelly17:09:32

Does anyone know if :pre or :post is working in clojurescript? I'm on version 1.7.48

dnolen17:09:40

@adwelly: it’s generally better to post what you tried that you expected to work than asking broad questions simple_smile

adwelly17:09:16

Fair enough

adwelly17:09:42

I'd expect (defn foo [] {:pre false} (println "hello")) to not print hello, but in the extremely odd javascript environment I'm executing the transpired javascript in, it is.

dnolen17:09:40

that isn’t valid :pre condition syntax

dnolen17:09:50

{:pre [(foo ..) (bar …)]}

adwelly17:09:01

I suspect my JavaScript environment, but just to eliminate the obvious I wondered if :pre and :post were in Clojurescript in the same way they are in clojure

dnolen17:09:17

again that's not valid precondition syntax in Clojure or ClojureScript

adwelly17:09:11

Thanks. Yes, that would make sense. Bad :pre syntax is just ignored then?

dnolen17:09:56

no there isn’t proper pre, post syntax validation in Clojure or ClojureScript far as I’m aware.

dnolen17:09:01

patch welcome for ClojureScript

dnolen17:09:12

to understand what is allowed

adwelly17:09:55

I wish I was confident enough to submit a patch, and in fact I wish I was knowledgeable enough too.

dnolen17:09:36

@adwelly: fixing this isn’t nearly as hard as it sounds simple_smile

dnolen17:09:56

in fact it’s near newcomer level simple_smile so submit something you’re more comfortable w/ Clojure(Script)

adwelly18:09:52

Hmm. Ok. I shall have a poke around. I'm totally unfamiliar with the compiler, any clue as to which namespace I should be looking in?

dnolen18:09:03

@adam: it’s the defn macro, it’s very similar to the Clojure one, in fact you might want to look at that first

dnolen18:09:13

you’ll see the pre/post is specially treated but not validated

adwelly18:09:58

Ok, will take an interested look. Thanks again

mfikes19:09:40

Can't believe ClojureScript's reach is about to extend to TV. Didn't expect that one.

mfikes19:09:34

(Someone got React Native working on tvOS.)

dnolen19:09:15

@mfikes: ha yeah I saw that

wildermuthn20:09:15

@mfikes, ClojureScript on AppleTV? Awesome. You referencing this? https://github.com/facebook/react-native/issues/2618

wildermuthn20:09:58

Anyone have experience using or integrating https://github.com/Matt-Esch/virtual-dom? There is https://github.com/dubiousdavid/dominator, but it bundles a lot of other libraries as well.

bhauman21:09:23

Just want to let CLJS cider users know that the latest figwheel 0.4.0-SNAPSHOT allows you to configure middleware so folks can use the figwheel nrepl connection. In fact it would be great to get some experienced folks trying it out.

bhauman21:09:46

@wildermuthn: haven't tried either ... but the resources and reach of React and the design of its component model are all very impressive

davy22:09:18

@bhauman: Updating to figwheel 0.4.0-SNAPSHOT actually removed the - goog.constructNamespace_ is not a function - error I got with the former release (even when updating to the last cljs, as mentioned in this issue https://github.com/bhauman/lein-figwheel/issues/236)

bhauman22:09:43

Well it pretty much has to be the cljs version.

bhauman22:09:26

Not cleaning could result in having an old goog.base that didn't have the construct namespace function.

bhauman22:09:38

caching could do this as well

davy23:09:43

Thanks for the guidance!