This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-01-09
Channels
- # admin-announcements (40)
- # beginners (6)
- # boot (69)
- # braid-chat (43)
- # business (3)
- # cljsrn (99)
- # clojure (51)
- # clojure-art (2)
- # clojure-brasil (2)
- # clojure-dev (23)
- # clojure-portugal (1)
- # clojure-russia (15)
- # clojurescript (52)
- # community-development (319)
- # core-async (1)
- # cursive (40)
- # datomic (6)
- # editors (11)
- # emacs (1)
- # hoplon (20)
- # jobs (1)
- # ldnclj (5)
- # leiningen (2)
- # mount (5)
- # off-topic (1)
- # om (45)
- # proton (5)
- # re-frame (29)
- # reagent (4)
- # ring-swagger (1)
- # yada (6)
But I think I’ll stick with re-frame and reagent for now. om next made me loose too many hear 😛 Just want to get this app out finally
Hi all, finally figured out how to join. Thanks @mfikes for the link to inviter. It was not obvious to me
Yeah! Everybody is here now I guess But still the question about presenting CLJS + RN is open
I'm too afraid of such responsibility, and I am lazy, and and and
Btw, I have noticed if you log a warn to console in RN application (non cljs) the warning appears on simulator screen. I think this could be emplyed to show messages of heads-up-display of figwheel. Current figwheel integration only works with disabled heads-up-display, so compilation errors are invisible.
Hey, I successfully integrated react-native-vector-icons
into my cljsrn app ! @artemyarulin what’s the address of the cljsrn-cookbook again 😛 ?
@gphilipp: Hey, cool! Have an open source project with it? We have a github organisation created https://github.com/cljsrn and mfikes maintains http://cljsrn.org
@artemyarulin: missed your reply to my question regarding http requests. what’s fetch
?
>[drapanjanas] I'm too afraid of such responsibility, and I am lazy, and and and exactly my thoughts
@wei: Well, react native allows making HTTP requests using XmlHTTPRequest and fetch API
Here if you need some wrapper around fetch api https://github.com/artemyarulin/koh/blob/master/src/koh/http.cljs#L47-L59
or use it as an example
@artemyarulin: thanks! koh looks useful.
hm. Yeah - I assume clj-http using XmlHTTPRequest under the hood and RN have their own implementation for that, maybe something doesn’t follow the browser spec in 100%, dunno
well nrepl + cider output result on the right from the source line
but actually RN catches all the console.log (print from cljs)
then you can see all the output in the xcode debug log (don’t know how to make it without xcode, Console app maybe?) and for android you may want to run adb command like, sec
adb logcat *:S ReactNative:V ReactNativeJS:V
@dvcrn: As a presenter you get hotel room and US ticket or $550 toward international : http://clojurewest.org/cfp
what are you guys thinking at? in general rn on clojure or some om / reagent flavor in particular?
I was thinking a general rundown — state of tech / progress / challenges - areas where help is needed. You can only do so much in 30-40 minutes.
Short demo of live reload running android + ios + browser would also be interesting - but people have seen videos of that - like @artemyarulin posted.
I want to ask more about debugging stuff @wei @artemyarulin et. al, mostly, 1) how to trace unexpected exceptions to CLJS code? assuming I am using figwheel for dev. 2) Is it possible to do any actual debugging with breakpoints & stuff
@docent: do you see red screen in RN? Usually it gives some part of information. Second thing to try - Debug in Chrome and stop on exceptions
and yeah - REPL is a first thing to try. Re-evaluate stuff
Then there is a RN log that worth reading (I posted adb command some time ago)
@artemyarulin: Yeah I am getting red screen but in my case it was of little help
have you tried debug in Chrome?
well, to be honest - this is problem in general about CLJS
but source map yeah should help
let’s see - I see no reason why source-map shouldn’t work with RN, hold a sec
well - running app is a bit different thing as in production you (well me) using advanced compilation - so stack traces doesn’t mean anything
I am coming from java and having stuff like stack traces is a basic tool for examining production issues
I don't have much experience with e.g. Android dev, but I imagine if something like that happens in the mobile app, there's logs too, so we are covered
hold a sec, I’m checking the source-map support
hm, it’s weird - Chrome should automatically get it
ahhh nope
we fetch JS files manually and then eval them. Google Chrome has no idea about source maps
But at least it would be nice to have them if we don't use figwheel but just produce one big js file
once again - this is a problem that boot-react-natvie doesn’t have…
and keeping in mind that RN would have hot reload very soon I’m less and less committed continue working with figwheel here
Can you please elaborate on how boot-react-native doesn't have this issue? And where did you get the info about RN hot reload?
boot-react-native generates JS from CLJS (transforms it a bit) and then put it in a folder that RN packager controls. So no hacks around require package, no hack with source map. Hot-reload - sorry, I’m too lazy right now to search, but one of the maintainers of RN in a twitter mentioned that somebody working already on it
found it
https://github.com/facebook/react-native/commit/4ffb24164712c0f0cafc7c097a0cdbc80e2c04d1
Awesome, thanks for that info! @artemyarulin
All / cc : @dvcrn @mfikes @artemyarulin : Put up https://github.com/cljsrn/community/wiki/ClojureWest-2016 as a repository of ideas on a clojurescript+reactNative talk.
@donmullen: Cool, I’ll think and put my ideas during this weekend
@donmullen: Hm, looks like I cannot edit it,not familiar with wiki on github but it looks I cannot even fork it and make a PR
or should I fork a whole project...
hm, nope, forking doesn’t help
@artemyarulin: sorry - thought I had made it a public wiki. Checking...
@artemyarulin: OK - you should have write access now to wiki. I also sent you a member invite.
yep, works now
I guess it’s worth sending the invites to the other members here
good, thx
To make it easier to submit content to http://cljsrn.org, I put markdown files in https://github.com/cljsrn/cljsrn-org. Feel free to submit PRs there, and I can incorporate them, build the site, deploy it, etc.
@artemyarulin: I wanted to add some of your recent stuff to http://cljsrn.org, but I hadn’t yet figured out if it is “top-level” stuff, interesting repos, etc. Feel free to submit PRs to have your content added, even if that means re-arranging the structure a bit to make things reflect where they are now.
I think the boot-react-native stuff might be a top-level thing under Using. (It wasn’t clear to me yet.)
(By the way, I don’t have strong opinions about the structure of the site… just wanted to collect resources in some logical arrangement that is easy to consume.)
@mfikes: Got it, I’ll make a PR
@donmullen: Nah, that’s perfectly fine. Deployed it.
Published an improvement of showing CLJS compile errors and other warnings on screen when using figwheel in re-natal v0.2.14 check it out. P.S. there was a breaking change, so a manual step is required to upgrade already established projects.