Fork me on GitHub
#cljsrn
<
2016-08-18
>
vikeri06:08:11

@pesterhazy: When is 0.3 scheduled to arrive at Clojars?

vikeri07:08:07

Pebble is quite nice actually!

pesterhazy08:08:02

@vikeri: interesting about the CLOSURE_UNCOMPILED_DEFINES bit

pesterhazy08:08:53

I'm hoping to release to clojars today

macroz08:08:18

I guess that would be interesting to try on my pebble but more interesting would be to have the watchface display something from an API

macroz08:08:51

I.e. when I usually leave to work it could automatically display next public transport times

macroz08:08:13

that would be quite possible to do but requires some capability to do REST calls

artemyarulin08:08:37

it’s sad that RN doesn’t support AppleWatch yet

pesterhazy08:08:26

maybe I'm doing it wrong

pesterhazy13:08:06

OK, I did do it wrong 🙂

pesterhazy13:08:42

https://github.com/mjmeintjes/boot-react-native now has 0.3-rc1 with a few new features (less chatty logging, automatic patching of RN)

pesterhazy13:08:04

Also, first non-SNAPSHOT release! 🙂

pesterhazy13:08:30

oh and it did not work 🙂

pesterhazy13:08:55

Fixed by 0.3-rc2

pesterhazy14:08:22

so this issue is the default error you see when the javascript code errors during initialization

pesterhazy14:08:31

it doesn't actually tell you anything about the issue

pesterhazy14:08:37

for that you need to inspect the device log

artemyarulin14:08:58

OK found. I’m using folder reference for JS content in XCode and apparently if you edit file in such folder outside of Xcode - it wouldn’t update app bundle resource and continue to use an old one

pesterhazy14:08:01

yeah it's a bit of a mystery

pesterhazy14:08:05

it's a pretty common issue, if you have some more specific advice, please add it

artemyarulin14:08:47

sure and thanks for the help

artemyarulin14:08:10

some time RN development feels.. am.. being too much on a cutting edge. I’ve spend 3 days upgrading RN from 0.10 till 0.31. *was not fun*

vikeri14:08:15

@artemyarulin: I feel ya. I try telling myself it makes me a better programmer. Converting my iOS app to Android in 2 days is pretty impressive though… Only hoping performance will not still suck once I start performance optimizing.

artemyarulin14:08:26

Yeah, it’s like “Whatever doesn't kill you, simply makes you stronger” 🙂

pesterhazy14:08:56

what issues did you run into, @artemyarulin ?

pesterhazy14:08:26

we've seen the >=0.25 React/ReactDOM split

misha14:08:36

simply npm install --save makes-you-stronger

pesterhazy14:08:38

which required us to upgrade all dependencies

tianshu14:08:40

anyone tried react-native-navigation?

artemyarulin14:08:49

@pesterhazy: well, nothing specific - you all know how it happens: Let’s update RN from 0.10 to 0.31. OK, I’ve been using Cocoapods, but now RN doesn’t get released there. Let’s use local podspec file from node_modules, oh - I need to update pod to 1.0, oh, breaking changes, now I need to change Podfile. Oh, react|react-native change, then xcode doesn’t update my bundle, then 100500 other small things like that 🙂

weltan21:08:49

Hey guys, quick question about NavigationExperimental that came up while playing around with @vikeri ’s re-navigate example (https://github.com/vikeri/re-navigate)

weltan21:08:41

the question is, “what is the best way one can switch between scenes using re-natal/RN?” (for more details, there’s a discussion on the question from @coyotespike here: https://github.com/weltan/navigation/issues/1)

weltan21:08:54

I forked re-navigate and put together a more fleshed-out example with scene-switching (https://github.com/weltan/re-navigate), and the question is about this section of code:

; We get current-scene info from props -> "scene" -> "key", rather than :nav/routes,
; because if you use :nav/routes, it switches scenes before the animation happens, and other
; indeterminate behavior...
(defn scene [props]
  (.log js/console props)
  (let [current-scene (aget props "scene" "key")
        _ (.log js/console current-scene)]
        ;current-routes (subscribe [:nav/routes])
        ;current-scene (keyword (:key (last @current-routes)))
    (case (keyword current-scene)
        :scene_login-route [login-scene]
        :scene_chat-table-route [chat-table-view]
        :scene_chat-route [chat-view]
        [login-scene]))

weltan21:08:49

You can see the case-statement that switches between scenes based on (aget props “scene” “key”). This produces a good result, but it’s not very re-frame-y. Anyone else do it differently/ am i totally missing something?