This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-18
Channels
- # alda (6)
- # architecture (1)
- # bangalore-clj (3)
- # beginners (39)
- # boot (292)
- # braveandtrue (1)
- # cider (7)
- # clara (2)
- # cljs-dev (20)
- # cljsjs (9)
- # cljsrn (42)
- # clojure (127)
- # clojure-chennai (1)
- # clojure-dev (96)
- # clojure-india (1)
- # clojure-russia (175)
- # clojure-spec (56)
- # clojure-uk (11)
- # clojureindia (1)
- # clojurescript (82)
- # core-async (7)
- # cursive (21)
- # data-science (1)
- # datomic (173)
- # funcool (4)
- # hoplon (8)
- # instaparse (1)
- # jobs (7)
- # jobs-discuss (1)
- # jobs-rus (30)
- # lambdaisland (1)
- # lein-figwheel (8)
- # off-topic (5)
- # om (51)
- # onyx (79)
- # other-languages (7)
- # planck (8)
- # re-frame (95)
- # reagent (6)
- # rum (8)
- # specter (4)
- # untangled (54)
- # yada (5)
@pesterhazy: When is 0.3 scheduled to arrive at Clojars?
And here is why I thought my :closure-defines
does not work: https://github.com/mjmeintjes/boot-react-native/blob/master/src/mattsum/boot_react_native.clj#L73
not exactly react, but: https://developer.pebble.com/blog/2016/08/15/introducing-rockyjs-watchfaces/
@vikeri: interesting about the CLOSURE_UNCOMPILED_DEFINES bit
I'm hoping to release to clojars today
@pesterhazy: Great!
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
I.e. when I usually leave to work it could automatically display next public transport times
it’s sad that RN doesn’t support AppleWatch yet
having trouble with clojars: https://github.com/clojars/clojars-web/issues/555
maybe I'm doing it wrong
OK, I did do it wrong 🙂
https://github.com/mjmeintjes/boot-react-native now has 0.3-rc1
with a few new features (less chatty logging, automatic patching of RN)
Also, first non-SNAPSHOT release! 🙂
oh and it did not work 🙂
Fixed by 0.3-rc2
so this issue is the default error you see when the javascript code errors during initialization
it doesn't actually tell you anything about the issue
for that you need to inspect the device log
ahhh, OK, thx
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
yeah it's a bit of a mystery
I've added a note here: https://github.com/mjmeintjes/boot-react-native/wiki/Troubleshooting#problem-unable-to-execute-js-call-__fbbatchedbridge-is-undefined
it's a pretty common issue, if you have some more specific advice, please add it
sure and thanks for the help
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*
@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.
Yeah, it’s like “Whatever doesn't kill you, simply makes you stronger”
🙂
what issues did you run into, @artemyarulin ?
we've seen the >=0.25 React/ReactDOM split
which required us to upgrade all dependencies
@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 🙂
Hey guys, quick question about NavigationExperimental that came up while playing around with @vikeri ’s re-navigate example (https://github.com/vikeri/re-navigate)
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)
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]))