This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-11-24
Channels
- # arachne (1)
- # bangalore-clj (11)
- # beginners (177)
- # boot (63)
- # business (1)
- # cljsjs (21)
- # cljsrn (3)
- # clojars (4)
- # clojure (116)
- # clojure-art (4)
- # clojure-belgium (3)
- # clojure-india (1)
- # clojure-italy (6)
- # clojure-russia (14)
- # clojure-spec (8)
- # clojure-uk (67)
- # clojurescript (51)
- # community-development (5)
- # cursive (13)
- # datascript (14)
- # datomic (29)
- # devcards (3)
- # emacs (3)
- # events (3)
- # funcool (4)
- # hoplon (29)
- # mount (6)
- # om (34)
- # om-next (5)
- # onyx (16)
- # perun (8)
- # planck (22)
- # re-frame (13)
- # reagent (5)
- # ring-swagger (21)
- # rum (3)
- # spacemacs (3)
- # specter (1)
- # untangled (39)
@tiensonqin thanks! With that workaround, I assume the tradeoff is a larger app package because it will include component for both platforms. Do you know if the RN packager excludes platform-specific files in release packages? I assume it does.
@savelichalex thanks! how do you pass the platform-specific components down the component tree - props, app-state? I'm using om.next. I think it would work to have the platform-specific entry points put their platform-specific component classes in the app-state for other components to retrieve.
@paul-c I'm just use closures) for i.e.:
(defn my-scene [platform-specific-component]
(fn [props]
[platform-specific-component props]))
ios.core
(def scene (my-scene ios-component))
that's all)