Fork me on GitHub
#cljsrn
<
2016-01-09
>
dvcrn04:01:05

@mfikes: oh that is good news!

dvcrn04:01:40

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

drapanjanas08:01:18

Hi all, finally figured out how to join. Thanks @mfikes for the link to inviter. It was not obvious to me simple_smile

artemyarulin09:01:13

Yeah! Everybody is here now I guess simple_smile But still the question about presenting CLJS + RN is open

drapanjanas11:01:12

I'm too afraid of such responsibility, and I am lazy, and and and simple_smile

drapanjanas11:01:45

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.

gphilipp11:01:26

Hey, I successfully integrated react-native-vector-icons into my cljsrn app ! @artemyarulin what’s the address of the cljsrn-cookbook again 😛 ?

gphilipp11:01:07

it includes integration with the TabBarIos react component.

artemyarulin11:01:07

@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

wei11:01:12

@artemyarulin: missed your reply to my question regarding http requests. what’s fetch?

artemyarulin11:01:42

>[drapanjanas] I'm too afraid of such responsibility, and I am lazy, and and and simple_smile exactly my thoughts simple_smile

artemyarulin11:01:10

@wei: Well, react native allows making HTTP requests using XmlHTTPRequest and fetch API

artemyarulin11:01:45

or use it as an example

wei11:01:57

@artemyarulin: thanks! koh looks useful.

wei11:01:27

I got clj-http working with POST but not GET. anyways, I’ll try your wrapper

artemyarulin11:01:38

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

wei12:01:44

how are people debugging their apps? where does prn output to?

artemyarulin12:01:30

well nrepl + cider output result on the right from the source line simple_smile

artemyarulin12:01:43

but actually RN catches all the console.log (print from cljs)

artemyarulin12:01:46

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

artemyarulin12:01:05

adb logcat *:S ReactNative:V ReactNativeJS:V

wei13:01:24

ok, I’m using android

wei13:01:41

aha, filtering is key. tried logcat before and got way to many messages

dvcrn13:01:28

If someone buys me a ticket, I present 😛

donmullen14:01:36

@dvcrn: As a presenter you get hotel room and US ticket or $550 toward international : http://clojurewest.org/cfp

dvcrn14:01:04

ok, time to ask the company if I can escape for that time

dvcrn14:01:55

what are you guys thinking at? in general rn on clojure or some om / reagent flavor in particular?

donmullen14:01:21

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.

dvcrn14:01:59

I’ll brainstorm a bit and see if I can come up with something simple_smile

donmullen14:01:01

Short demo of live reload running android + ios + browser would also be interesting - but people have seen videos of that - like @artemyarulin posted.

docent16:01:34

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

docent16:01:08

I am starting a REPL under Cursive FYI

artemyarulin18:01:00

@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

artemyarulin18:01:22

and yeah - REPL is a first thing to try. Re-evaluate stuff

artemyarulin18:01:02

Then there is a RN log that worth reading (I posted adb command some time ago)

docent18:01:09

@artemyarulin: Yeah I am getting red screen but in my case it was of little help

artemyarulin18:01:22

have you tried debug in Chrome?

docent18:01:32

Yeah, but what you see there is basically garbage

docent18:01:07

I see this as a major hurdle

artemyarulin18:01:33

well, to be honest - this is problem in general about CLJS simple_smile

artemyarulin18:01:44

but source map yeah should help

docent18:01:50

Well I guess when you dev for browser not really

docent18:01:55

because you have source maps

docent18:01:31

In case of RN... looks like guesswork so far, which I'm concerned about

artemyarulin18:01:49

let’s see - I see no reason why source-map shouldn’t work with RN, hold a sec

docent18:01:50

besides, what if you have some unexpected exception in some already running app

docent18:01:16

how are you gonna do post-mortem debugging

artemyarulin18:01:32

well - running app is a bit different thing as in production you (well me) using advanced compilation - so stack traces doesn’t mean anything

docent18:01:19

I am coming from java and having stuff like stack traces is a basic tool for examining production issues

docent18:01:14

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

artemyarulin18:01:40

hold a sec, I’m checking the source-map support

docent18:01:43

ok, thanks!

docent18:01:51

I see that figwheel generates them during compilation

artemyarulin18:01:17

hm, it’s weird - Chrome should automatically get it

docent18:01:42

that might be related?

artemyarulin18:01:37

we fetch JS files manually and then eval them. Google Chrome has no idea about source maps

docent18:01:53

Yeah, that's what I thought

docent18:01:15

But at least it would be nice to have them if we don't use figwheel but just produce one big js file

docent18:01:23

i.e. production build or whatever

artemyarulin18:01:52

once again - this is a problem that boot-react-natvie doesn’t have…

artemyarulin18:01:31

and keeping in mind that RN would have hot reload very soon I’m less and less committed continue working with figwheel here

docent18:01:42

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?

artemyarulin18:01:27

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

docent18:01:27

Awesome, thanks for that info! @artemyarulin

donmullen18:01:54

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.

artemyarulin19:01:51

@donmullen: Cool, I’ll think and put my ideas during this weekend

artemyarulin19:01:38

@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

artemyarulin19:01:07

or should I fork a whole project...

artemyarulin19:01:52

hm, nope, forking doesn’t help

donmullen19:01:26

@artemyarulin: sorry - thought I had made it a public wiki. Checking...

donmullen19:01:46

@artemyarulin: OK - you should have write access now to wiki. I also sent you a member invite.

artemyarulin19:01:46

yep, works now

artemyarulin19:01:10

I guess it’s worth sending the invites to the other members here

donmullen19:01:39

Yes - although I think the wiki setting will let everyone edit now.

mfikes20:01:33

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.

mfikes20:01:21

@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.

mfikes20:01:44

I think the boot-react-native stuff might be a top-level thing under Using. (It wasn’t clear to me yet.)

mfikes20:01:25

(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.)

donmullen20:01:38

@mfikes: the boot-reactive-native would go along with natal/re-natal

donmullen20:01:25

Are you regenerating the site - not coming up currently.

mfikes20:01:28

No… it should be live.

mfikes20:01:50

It is just a static site on a Linode served with Nginx.

donmullen20:01:57

Ah - you had put https.

mfikes20:01:12

Ahh… yep. Mistake

artemyarulin20:01:27

@mfikes: Got it, I’ll make a PR

donmullen20:01:40

@mfikes: added boot-react-native

donmullen20:01:13

Probably should have done PR...

mfikes20:01:48

@donmullen: Nah, that’s perfectly fine. Deployed it.

drapanjanas23:01:46

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.