This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-03-30
Channels
- # admin-announcements (10)
- # beginners (17)
- # boot (14)
- # braveandtrue (4)
- # cider (6)
- # cljsrn (38)
- # clojure (232)
- # clojure-austin (1)
- # clojure-belgium (2)
- # clojure-dev (20)
- # clojure-greece (20)
- # clojure-japan (3)
- # clojure-poland (39)
- # clojure-russia (76)
- # clojure-sanfrancisco (6)
- # clojure-uk (4)
- # clojurescript (90)
- # cursive (2)
- # data-science (10)
- # datomic (18)
- # garden (16)
- # hoplon (244)
- # immutant (3)
- # jobs (6)
- # jobs-discuss (2)
- # juxt (1)
- # off-topic (3)
- # om (50)
- # onyx (23)
- # re-frame (5)
- # reagent (36)
- # remote-jobs (11)
- # slack-help (6)
- # spacemacs (2)
- # untangled (46)
Core Audio is a bit of a painful API last when I looked at it
I’d even consider useing objective C for easier tying in with the C api. I haven’t dived into it since iOS9 came out though so it may be better
I think Obj-C native module + cljsrn may be enough
swift is fun, but cocoatouch is painful in places.
Yeah, I get that too @vikeri. Seems like it's fine to ignore for now: https://github.com/facebook/react-native/issues/4547
I ignore it by calling (set! (.-ignoredYellowBox js/console) #js ["Warning: Failed propType"])
in my init
Stupid question: How do I call the camera roll from cljs? I have tried this: (.getPhotos js/React.CameraRoll #js {:first 2 :groupTypes "Album" :assetType "Photos"})
But I get "Cannot read property 'getPhotos' of undefined"
Aha, I had to link in the native library for CameraRoll...
good day, gentlemen. can someone describe in a few sentences, what it took to port om-next/reagent/etc. to react-native?
the goal is to decide between: a) porting another react wrapper to native, and b) porting application to one of the react-native wrappers
Seriously. After that it's just swapping the library and rendering the root differently. In om.next case it was just replacing the 2 render functions with react native ones
reading reagent's source to see how it is done there to find out how interaction with react differs from react-native one
@dvcrn: ok, i am thinking about porting rum
to RN.
first: I have no idea how it works. yet.
second: it depends on sablono for "dom templating" part. I want to keep it that way, which probably means I might need to extend sablono with RN tags.
third: ???
nth: profit
@dvcrn: fyi https://github.com/tonsky/rum/blob/gh-pages/src/rum/core.cljs#L145-L146 changing this:
(defn mount [component node]
(js/ReactDOM.render component node))
to this:
(defn mount [component node]
(js/React.render component node))
makes re-natal
s hello world app work : )Last time I checked there was still a big difference between react and react native. React is a good chunk more abstract and react native is playing catch up
Stuff like the ReactDOM doing the rendering and react are only components. Not sure how that can translate into native but it will happen for sure. Then both libraries could use the same react
About navigation. Since NavigatorExperimental is such a great fit for re-frame compared to NavigatorIOS or Navigator I’ve been trying to get it to work. I’ve skipped its state management part (since that will be handled by re-frame) but I can’t get a CardStack to render my content. Trying to adapt the following example:
@vikeri: Funny you should ask, I plan on working on that today.
Haha ok great! My approach was to try to adapt the card-stack example since it seems to be the most developed one. How are you thinking?
Well, to be honest, I still don’t understand the underlying concepts so I was going to read the source until I got a better idea. Then I was going to look at adapting the RN-NavigationExperimental-Redux-Example since Redux also has a centralized data store. https://github.com/jlyman/RN-NavigationExperimental-Redux-Example
also, it seems like this discord channel is where a lot of NavigationExperimental discussion happens https://discordapp.com/channels/102860784329052160/154015578669973504
@seantempesta: Ok! Interesting that they have moved from slack to discord btw. Maybe something we also should consider? Or Rocket.Chatt or some equivalent OSS.
It looks like the api is still shifting for NavigationExperimental, so people are staying on top of the changes
Also, apparently there were major performance bugs in Android with it until 0.23.rc1