This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (11)
- # beginners (16)
- # boot (171)
- # cider (1)
- # clojure (31)
- # clojure-france (2)
- # clojure-italy (3)
- # clojure-korea (12)
- # clojure-russia (1)
- # clojure-sg (4)
- # clojure-uk (3)
- # clojurebridge (3)
- # clojurescript (52)
- # code-reviews (1)
- # datomic (1)
- # editors (3)
- # events (1)
- # jobs (13)
- # ldnclj (3)
- # reagent (6)
- # sneer (1)
@maria Just read through your commit. Awesome! I think I’ll build a local copy of Closure to try it out.
mfikes: thank you :) they just released a new version of the Google Closure compiler (v20150609) including our changes, so you only need to adjust the version when building the ClojureScript compiler ;)
@ivar good chance EuroClojure video will be up sooner And it will be more relevant for Clojure(Script) programmers.
@maria: Ignoring JSX for now, I’m experimenting with a gigantic
:commonjs for React Native https://github.com/mfikes/rn-commonjs/blob/master/project.clj#L15
@mfikes: curious to see how that goes. re: JSX, looks like that’s now dropped for Babel
@dnolen: I didn't quite comprehend what they are doing. Is the JSX dialect going away or just the current transformer impl?
@mfikes: JSX is their custom transform tool, they’re just switching to a standard system and their transforms will be plugins far as I understand to Babel.
@dnolen: Ahh. OK. So if ClojureScript ends up supporting a transform plugin, the plugin for JSX is likely to be built in terms of Babel instead of the older implementation. I also wonder if it is just possible to pre-transform all of the React Native code manually prior to it even being seen by ClojureScript’s
:commonjs (that’s at least what I might try in the interim)
@mfikes: that’s possible but too, but that just means more tools / more steps. I think better if you can just setup ClojureScript to do all the bits.
@dnolen: Yeah. I’m also wondering if the generation of the (gigantic)
:foreign-libs can ever be automated, or if it would end up being packaged up into something perhaps in CLJSJS.
I need to allow the user to download (JSON) data as a file. Since I'm using Sente, I figured the easiest way would be to send the data to the client, and then use https://github.com/eligrey/FileSaver.js — anybody know of an easier way?
@jrychter: ah ok, you want to save a client side string (which happens to be json) to a file
Somebody could explain to me, what exactly happens when I do:
I mean, when I implement methods for Object instead of regular protocols in
(deftype AType  Object (foo [_] "Hi!"))
How to call those methods? I will test this by myself, but maybe somebody knows any tricky parts of it?
@ul the only thing that isn’t compatible with advanced compilation - using strings for properties
I'd like something that looks good on a phone. I've 95% rolled my own because cljs+closure makes it so easy, but I'm concerned that there is something I haven't thought of, like old IE
Math passes as an implicit namespace during analysis, passes through
munge during emit* :var, where the
/ is replaced with a
. here: https://github.com/clojure/clojurescript/blob/f8af10da6429bab8e9838ac90a622b1858ffe983/src/main/clojure/cljs/compiler.cljc#L78
i'm not actually using closure for anything but generating vectors of weeks to layout using om
@ghadi: looks like react supports down to IE8 http://facebook.github.io/react/docs/working-with-the-browser.html#browser-support-and-polyfills