Does anyone have an example with CLJS + React Native for Android yet?

@pandeiro: This exists—it appears to directly drive a little React from ClojureScript (no Om or Reagent, etc.). https://github.com/nicholaskariniemi/ReactNativeCljs

@mfikes Cheers I'll take a look

hello all, may i please have your suggestions of methods/frameworks for mobile html5 cross platform development in clojure(script) ? very much appreciated. thank you

@jouerose: I'd take a look at this - https://github.com/enterlab/cordevicljs

@jaen thank you. heading there to have a look

@jouerorse: the example uses OnsenUI, but there's a lot of mobile HTML frameworks you may want to use in cojunction with Phonegap - Ionic, Sencha Touch, Touchstone, Reapp, material-ui; the last three mentioned are React-based so may be the most interesting to you. There's probably a lot more you can find through Google.

thanks again @jaen

It’s happening.

I find myself unwittingly typing “s” at the end of my .clj file extensions

Soon I will only think about the JavaScript runtime

hi all,

anybody made ionic framework and clojurescript work together ?

@jouerose: I haven’t heard of anything, but might have missed it too

hi @dnolen , i researched programming languages over the past few months, and clojure(script) looks like a dream language. today i am wondering what are the ways to do cross platform mobile development with it, therefore my question in reality is beyond ionic. if you know anything, thanks for letting me know.

@jouerose: there’s a good chunk of the ClojureScript community that’s focusing their energies on React as React is immutable friendly

most JavaScript “frameworks” are not

@dnolen is there anything for React Native ? would you know whether React (non Native) is an option with clojurescript when targetting mobile ?

@jouerose: people are already using React Native, and also working actively to enhance it’s usage via ClojureScript

you can of course approach mobile via more “webby” tech and I know people are doing that too.

@dnolen thanks. would you any keyword/reference for the mix of clojurescript and react native ? any project or example ?

would you have*

@jouerose: there are some things but your patience level is going to have to be very high, literally every aspect of this of kind of development is cutting edge

and you’ll have to have some working knowledge of Clojure, ClojureScript, Objective-C, iOS, React

a powerful tool, not exactly a great starting point

@dnolen: i am beginner level in clojure(script) but willing to still have a look at the keywords and references you can drop. if i must wait before using the perfect score, i will take something meanwhile while keeping an eye on the cutting edge

@jouerose: https://github.com/dmotz/natal

@dnolen: thank you, is there any other ?

I’m not aware of anything else or anything easier to get started with. There be dragons.

@dnolen: regarding natal, i have seen in clojure world that sometimes while version number is low, it can be considered production ready. is Natal one of those software ?

well, you have the fundamental instruction stuff here https://github.com/omcljs/ambly/wiki/ClojureScript-React-Native-Quick-Start

@jouerose: cutting edge and “production ready” are generally not said in the same breath

@dnolen: ah ah , true

@dnolen: thanks for your input

This may be attempting rocket surgery on a moving rocket, but is there any way to open a REPL up in the ClojureScript compiler while it’s running from Figwheel?

I’m trying to track down a very sporadic bug, and wanting to get more visibility into what’s going on in the compiler

@danielcompton: the easiest way to do this today is to use Cursive, won’t give you a REPL but that will give you a debugger with in-frame eval which is probably more useful anyhow for this

I do this all the time, def not rocket surgery on a moving rocket

I’ve got Cursive running, but I’m guessing I need to start with a debug config?

yep that’s all you need to do

search for files will show sources in jars

Took a few days for this bug to show up again, so I don’t really want to kill the REPL 😞

you can set breakpoints in any ClojureScript compiler source file.

Can I do this from figwheel, or do I need to launch the compiler directly?

you can attach to any JVM process, easier if Cursive launches it

Got the debugger attached with breakpoints in ClojureScript, off to bed now!

Thanks @dnolen, I appreciate the help

@danielcompton: np the more people know how to do this the better

@maria: @jaen: this is interesting http://blog.persistent.info/2015/05/teaching-closure-compiler-about-react.html

looks like somebody may have already written all the integration bits we would need, open question as to how reusable it is or simple to integrate

@shofetim: because http/get doesn’t throw

it probably just returns a channel

@dnolen: interesting. Though if I understand that correctly it's React-specific, so it does not solve the general module problem, just eases integration with React in an already browserify-processed form.

@jaen yeah sorry wasn’t talking about the module issues, just using this for JSX processing instead

of babel / old jsx transform

@dnolen: hmm, this seems suggest they do JSX beforehand though - https://github.com/mihaip/react-closure-compiler/blob/3317cbef681b943c1854a492d5035ccd32bf7073/demo/index.js#L26-L27

@jaen ah darn ok I didn’t look too closely!

There's now 3 or 4 people messing with JavaScriptCore / React / Android. Wow!

nice

Is cljs.nodejs suppose to come with ClojureScript? I can’t locate it.

Oh, nevermind… for some reason my non-nodejs build is picking up a directory I’m not specifying, which contains nodejs code.

@mfikes: Nice! Does React Native on Android also run on JSC?

@lvh Yes

Any ideas why I’m getting this error: lojure.lang.Compiler$CompilerException: java.io.FileNotFoundException: Could not locate cljs/nodejs__init.class or cljs/nodejs.clj on classpath., compiling:(projectx/node.clj:1:1)

@pupeno: you probably created a .clj file when you meant to create a .cljs one

Thanks @dnolen.

@pupeno: np!

And now this: SEVERE: cljs.nodejs:1: ERROR - namespace "cljs.nodejs" cannot be provided twice

I’m feeling stupid today.

the errors tell you what’s wrong

the previous error message was exactly right, this is almost always the case

loading .clj file that doesn’t exist

this one isn’t any different, cljs.nodejs is getting provided twice somehow

Yes, I get that bit, but I can’t identify why?

start thinking through the obvious ways this could happen

are you using output directories as input directories to the compiler?

No, I’m not doing that.

do you have your own ns called cljs.nodejs, stuff like that

whenever you think “No, I’m not doing that"

you should be thinking

but “I might be doing something like it though"

the bug doesn’t lie

somehow you are giving Closure the file twice

one helpful thing would be to turn on :verbose true and do a clean build

this will show you everything the compiler looks at and outputs

then do a second build etc.

mhh… would src/cljs also include ser/cljs-node in cljsbuild?

No, that’s not it 😕

@pupeno turn on :verbose true

search for the compilation of that file

Yes, I’m watching it run right now.

check your output dir make sure node.js isn’t in there twice.

cljs/nodejs.js rather

wow, compiling each of my targets individually work, but all together fails.

@pupeno: are you sharing output dirs?

also resources probably should NOT be on your classpath for compilation unless you want very confusing bugs

https://gist.github.com/pupeno/01a9648ab7a70c087322

yup, I am sharing output dirs… but that doesn’t make sense anyway.

it does make sense

compiling to the same output dirs is a surefire way to create problems if you’re not careful

No, I mean, for my project, these two outputs shouldn’t be in the same directory, it makes sense to separate them.

ah I see

I still seem to get the same error… let me try to reproduce it cleanly.

hi @pupeno do you have a folder named esources?

also, can you post your project.clj?

I do have a resources

After properly cleaning the project, it seems to be working.

Thank you @dnolen

np

ok… the error happens when I’m recompiling and I didn’t clean it first. :S

@pupeno: right I mentioned that above

it just sounds like you have resources on the classpath when you are compiling

and I also said not to do that

@dnolen: I didn’t do that explicitly and the nodejs code now outputs outside resources… it outputs to target… which is probably bad too 😕

right you are confused about what I’m saying

it’s fine to output to resources

but DO NOT put resources on the classpath when compiling

if you do this then the compiler will look there for ClojureScript and JavaScript files

this is how you are getting duplicates

and this is why the second build fails

Yes, I understood that, but I don’t see how resources can end up in the classpath.

because lein probably does that for you.

oh! so, the default lein behaviour is bad?

it makes sense for web servers

it doesn’t make sense for the build

lein gets that behavior (probably) from maven, which does the same

How do I undo it then?

just specify explicit :resources-path

might be :resource-path I don’t remember

https://github.com/technomancy/leiningen/blob/master/sample.project.clj#L281

:resource-paths close @dnolen 😜

lol, thx

but is it valid inside cljsbuild? and what does it normally contain so that I remove resources and leave the rest?

you can set it in profiles https://github.com/technomancy/leiningen/blob/master/sample.project.clj#L160

I believe it is :resource-paths ["resources"] by default

but you can always read the source to find out for yourself

bostonaholic: that would require having different profiles for clojure and clojurescript, so instead of dev, now I would need to have dev-clj and dev-cljs.

Anyway, having :resource-paths [] didn’t fix the problem.

@pupeno: I’m very skeptical about that claim. Paste what you tried. And no :resource-paths doesn’t go in :cljsbuild it’s a Lein thing.

dnolen: here it is: https://gist.github.com/pupeno/70eff5d4629f79874233

@pupeno: I doubt supplying an empty :resource-paths will work, you need to supply something

ok...

but the important thing is this ...

resources/cljs/nodejs.js will match a namespace cljs.nodejs

so you can make resources work correctly if you actually adopt a traditional setup

where you set :output-dir to resources/public/js

then you can leave resources alone

https://gist.github.com/pupeno/70eff5d4629f79874233 (I passed “foo”), still happening.

because cljs.nodejs can no longer be matched to anything on the resources classpath

Figwheel-reloadable local state in Reagent: http://vvvvalvalval.github.io/posts/2015-09-16-bottup-approach-to-reagent-state.html

Feedback appreciated

dnolen: my output dir is resources/public/js for one of my builds, target/js for the other (following your recommendation of not having them in the same directory). There’s no resources/cljs directory.

@pupeno: right so then target/js is also your problem (which I alluded to early)

I set it to something different before and I think it was still happening, let me check.

you can keep checking. But the principle is this - if the ClojureScript compiler sees a namespace called cljs.nodejs it will attempt to find on the classpath in a non-deterministic way

every possible combination of some/classpath/cljs/nodejs.(js|cljs)

so the only way to avoid this is to make sure your classpath is clean for your builds

that is cljs.nodejs should only resolve to what’s in the ClojureScript JAR nothing else

dnolen: I understand that, but I don’t see why a secondary cljs.nodejs is appearing.

Here: https://gist.github.com/pupeno/70eff5d4629f79874233

I set the output directory to foo2

and it’s still happening.

@pupeno if you understand what I said, then it should be obvious how a second one can appear

if you don’t understand how it can appear twice, then you did not understand what I said above

Ok, then I didn’t understand it.

Clearly it’s picking up an extra file: https://gist.github.com/pupeno/70eff5d4629f79874233#file-when-it-doesn-t-work-L8 when it fails (13 sources instead of 12).

1) clean build

2) compile

3) cljs/nodejs.clj gets compiled to “something/on/your/classpath/cljs/nodejs.js"

4) rebuild

5) you now have two matching namespaces on your classpath

Yes, but I don’t understand why 3 is happening.

6) chaos

3) is happening because something is setting :nodejs target or explicitly requiring that ns

dnolen: yes, I am setting :nodejs because I want to run my app in :nodejs and I’m requiring cljs.nodejs so that I can call (cljs.nodejs/enable-util-print!)

@pupeno then you have all the information you need

https://gist.github.com/pupeno/70eff5d4629f79874233#file-project-clj-L54

I explained exactly how you ended up where you ended up

the solution is tweak your classpath so the same resource can’t be resolved twice when you compile

How do I remove foo2//server-side/cljs/ from the classpath then?

(and why is cljsbuild putting node.js there when it breaks things?)

And why isn’t foo2//server-side/cljs/core.js a problem but foo2//server-side/cljs/nodejs.js is? or is nodejs.js just failing first?

@pupeno: now you’re getting to part where I don’t have any answers

your project.clj is pretty complicated

if I were you I would whittle this down to a minimal case to determine if it’s a bug in cljsbuild or something we’ve missed

Ok, it wasn’t that obvious and simple after all.

I’ll try to make a minimum case, although this is already quite a minimum case from what I’m trying to do.

@pupeno the issue is the same one I said it was like an hour ago

Yes, there are two nodejs.js, that’s simple, it’s in the error message, but why they are or how to avoid it is not simple. All cljs gets compiled to js files there, so it doesn’t feel like it’s wrong.

it’s completely simple

but your tooling decisions are polluting the classpath and you’re OK with this.

lein classpath read the output, see which ones are going to intersect

What decision is polluting the classpath?

Lein and cljsbuild “easy” decisions

what do you mean?

I don’t use any of these tools because I want to know that the classpath isn’t going to include some random stuff for whatever operation I intend to do

Using lein and cljsbuild is my mistake?

@pupeno: no, but you should understand the opaqueness of what’s going to be on the classpath is a direct result of what you decided to use

so if you want to use these things you will have to sort out how they work wrt. the classpath

https://gist.github.com/pupeno/70eff5d4629f79874233 there’s the classpath, it doesn’t include foo2//server-side/cljs/nodejs.js

So that’s not the problem.

I never said that was the problem

just that cljs/nodejs.js is in the build twice

I don’t see how that CLASSPATH would include cljs/nodejs.js twice.

have you tried to do recursive directory search to see how many times cljs/nodejs.js occurs in your project?

Yes:

$ find . -name nodejs.js ./foo2/server-side/cljs/nodejs.js ./foo2/server-side/goog/bootstrap/nodejs.js

@pupeno: huh and that isn’t on your :dev profile classpath?

dnolen: not according to lein classpath: https://gist.github.com/pupeno/70eff5d4629f79874233

@pupeno: don’t you need to run a different command to compute the classpath for a profile?

lein classpath isn’t enough I don’t think

I thought the :dev profile was the default.

I don’t know, I don’t use lein so you’ll have to tell me

ok yeah :dev is in the :default composite

If nodejs.js is a problem there, then core.js should be a problem here ./resources/public/js/app/cljs/core.js and the app should fail with the same error.

@pupeno: I would examine the final output file, I should have suggested that earlier

sorry

look for goog.provide(“cljs.nodejs”)

Oh!

$ grep -R "goog.provide('cljs.nodejs')" target/ target//js/server-side/cljs/nodejs.js:goog.provide('cljs.nodejs'); target//js/server-side/D2E353E.js:goog.provide('cljs.nodejs');

WTF is D2E353E.js?

right so this right back to the problem of sharing output directories and putting them on the classpath

I’m assuming target/js/server is on the classpath

No, it’s not.

https://gist.github.com/pupeno/70eff5d4629f79874233#file-classpath-L1-L7

sorry I mean, it’s on the classpath or ClojureScript sources path

one or the other

It’s not in either of them.

the ClojureScript doesn’t randomly include things

everything must be explicitly specified

:source-paths ["src/cljs" "src/cljc" "src/node"]

@pupeno no I know I’ve seen your file

I’m just saying that whatever you specified doesn’t matter

I’m not saying it does, but I’m not explicitly doing that.

somehow target/js/server-side is part of your build or your classpath

anyways the randomly named file is just a thing we generate under :none

so yeah I have no ideas about that directory is getting considered in your build

@pupeno what happens if you remove the :scope “provided” bit from your ClojureScript dep?

I don’t have :scope “provided"

@pupeno: you do https://gist.github.com/pupeno/70eff5d4629f79874233#file-project-clj-L19

but I just tried that here

doesn’t seem to matter

Ah, that provided, nevermind, let me try.

@pupeno: what I’m confused by is why target exists?

it’s not a part of your project.clj

If I stop requiring it, the problem stops, but then I can’t call enable-util-print!

if it isn’t why don’t you delete it

dnolen: foo2 was my renamed target to try to avoid collisions.

no I mean

target how is that part of the prefix of the output dir?

let me update things so everything is consistent.

heh

There: https://gist.github.com/pupeno/70eff5d4629f79874233

target/js is specified as the output dir in project.clj

@pupeno: why doesn’t :app build specify :output-dir?

It does, here: https://gist.github.com/pupeno/70eff5d4629f79874233#file-project-clj-L48

@pupeno: one second ...

@pupeno: OK I spelunked a bit with Om which uses Lein

I used lein-cljsbuild 1.0.6 same as you

the random files are only generated under :none

never under :simple

in your case it appears that when you run all builds somehow the :none compilation artifacts end up in :simple output-dir

that’s about as far as I’m willing to dig into this, gotta switch gears - this appears to me at the moment that this is firmly in cljsbuild territory

@pupeno and you’re right about your project.clj, it looks fine and doesn’t appear to have any of the issues I mentioned, it’s just that almost every user that reported that bug has always had classpath issues

I suspect that this may be one of those cases people always get tripped up on and just learn to clean and never report the cause 😞

@pupeno: also tried running lein cljsbuild once with two build specs

I still don’t see the wrong files in the wrong place. So maybe this is a profile merging thing? dunno

Huh, interesting how finicky building cljs with lein can be

I switched from :simple to :advance optimizations and now it’s finding even more sources to mess up together (still the same error though).

@pupeno: remove all the profile stuff and try that

@pupeno: also would look at using a more recent version of cljsbuild

lein ancient claims I’m having the latest one.

your project.clj says 1.0.6

github says 1.1.0

mh.

upgrading, same, disabling profiles, same 😞

Removing :target :node or removing :require [cljs.node] fixes it.

hrm

I wonder if it’s because output-dir has target as parent

I tried setting it to foo2 and the behaviour was identical. Before it was set to resources (when the problem started).

yeah I can’t repro here

out of ideas

well other than slowly whittling down the project

(and ruling out weirder stuff like global lein profiles)

@dnolen: ruling out ~/.lein/profiles.clj is usually one of the first steps I take

@danielcompton: I deleted it, no effect.

Oh, nodejs works with :optimizations :none? I thought it required at least simple. Anyway, it works with :optimizations :none, so the problem is with optimizations.

Anyway, thank you everybody and specially @dnolen for the help, I’m off to sleep.

@pupeno yeah Node.js has worked with :none for a while now

@pupeno: let me know if you get to the bottom of it, would like to know!