This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-11
Channels
- # aws (6)
- # beginners (105)
- # boot (6)
- # cider (50)
- # cljsrn (10)
- # clojure (41)
- # clojure-brasil (6)
- # clojure-italy (25)
- # clojure-nl (17)
- # clojure-russia (4)
- # clojure-serbia (1)
- # clojure-spec (8)
- # clojure-uk (242)
- # clojurescript (27)
- # core-async (10)
- # cursive (5)
- # data-science (9)
- # datomic (43)
- # emacs (6)
- # fulcro (6)
- # graphql (1)
- # javascript (3)
- # juxt (4)
- # lein-figwheel (1)
- # mount (1)
- # onyx (19)
- # parinfer (2)
- # portkey (15)
- # protorepl (1)
- # re-frame (30)
- # reagent (3)
- # ring-swagger (1)
- # shadow-cljs (22)
- # sql (6)
- # tools-deps (23)
- # vim (13)
@psdp @jeluard I'm enjoying scanning the status-im source lots of good stuff to learn from in there.
Hi @vikeri I noticed a cljs-devtools issue with your name on it. Just wondered. Did you end up with a working setup for using cljs-devtools on android? Seems fine on iOS simulator with Remote JS Debugging enabled but I see Yellow warnings with Android.
My setup: https://confluence.condense.com.au/display/IZ/Remote+JS+debugging+in+Chrome
And now it's fine. Sorry. Must have been something wrong in my setup.
Stand down red alert.
@olivergeorge Donโt recall that issue, works well for me now on both Android and iOS ๐
Setting up react-native-splash-screen is horrid. Not a well polished library but necessary.
As far as I see it for the app to feel right we need a splash screen that seamlessly flows into the app user experience. Problem being that React Native doesn't boot instantly so there's a gap between the launch screen showing and the app being ready to render the first scene.