Fork me on GitHub
#cljsrn
<
2016-01-23
>
dvcrn07:01:02

How's clojurewest from the rn side looking? Do we already have talks?

donmullen12:01:37

@dvcrn: You’re the only one I’ve heard volunteer to consider putting a talk together.

seantempesta16:01:58

So I’m trying to modify a re-natal project to use om-next and am having trouble getting figwheel to detect changes in the source files. Anyone know how this works?

seantempesta16:01:27

Ah never mind. It’s working.

meow17:01:52

we created #C0K2Z0LDB for anyone that wants to discuss conf speaking proposals

gphilipp18:01:23

@seantempesta: I’d be interested to see what the code looks like to have basic support for om-next using re-natal. I’ve used natal since many weeks but debugging with the browser doesn’t work and I’d like to have fighweel to surgically change stuff in the runtime (not whole app reload).

seantempesta19:01:47

@gphilipp: hmm, what I did feels like kind of a hack, but I can share it https://github.com/seantempesta/re-natal-om-next

seantempesta19:01:47

basically, I just updated the project.clj (removed reagent, added the om-next dependencies), removed all references to reagent, and then replaced the ios/core.cljs and android/core.cljs context with the default om-next template from natal.

gphilipp19:01:16

Ok. I cloned the repo, and xcode doesn’t compile the project, RCTRootView.h file not found

gphilipp19:01:34

ok. It can’t find React.xcodeproj

gphilipp19:01:57

I just have to run npm install

gphilipp19:01:27

It still fails with evaluation error in

gphilipp19:01:03

The goog dir is not present under target/ios. Not even using vanilla re-natal init SomeApp

drapanjanas19:01:44

We could think of having support for om-next in re-natal, like in it is done in original natal. But I do not know om-next so I can not support much here

drapanjanas19:01:30

I have started with om.prev and switched to reagent+re-frame. Someday I might get to know om-next, when I have motivation

gphilipp19:01:02

@drapanjanas: I can’t manage to have re-natal run the app after init, it fails with the error above

drapanjanas19:01:46

Was init successful? try lein prod-build

gphilipp19:01:38

yes init was successful

drapanjanas19:01:09

did you run then re-natal use-fighweel and lein figwheel ios?

gphilipp19:01:37

No I didn’t. I expected to run from xcode and it would work.

gphilipp19:01:06

lein prod-build made it work

drapanjanas19:01:55

well, thats funny, that should be the last step of init.

gphilipp19:01:59

How do you add cljs source code in the browser and have source map work ?

drapanjanas19:01:39

using importScripts function to load JS, and I have hacked packager to server *.map files from fs

drapanjanas20:01:04

@seantempesta: I guess you might want also to try out artemyarulin’s template, it is om-next from the start, and uses same figwheel approach https://github.com/artemyarulin/om-next-cross-platform-template

seantempesta20:01:57

@drapanjanas: hmm, I talked to @artemyarulin about this yesterday and he recommended I use re-natal. Not sure what the differences are at this point, but maybe I’ll switch down the road?

jimmy20:01:00

It really depends, I find his new template is really a good match with om next and it's quite easy to get started.

jimmy20:01:18

re-natal is pretty much about the wrapper of react native and reagent.

drapanjanas20:01:17

Yes, re-natal generates reagent+re-frame example app

seantempesta20:01:43

okay, I’ll give it a shot. Thanks for the tip.

gphilipp21:01:22

@seantempesta: there are still references to reagent in your repo in the env.ios.main namespace

gphilipp21:01:17

and in env.android.main

seantempesta22:01:07

@gphilipp: Yeah? Where? I just grepped my repo and didn’t find anything. Maybe you’re seeing it in an old version of my repo?

gphilipp23:01:17

found the culprit: typing re-natal use-figwheel overwrites your versions with ones using reagent

gphilipp23:01:52

log:

Cleaning...
index.ios.js was regenerated
index.android.js was regenerated
Dev server host: localhost