This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-03-01
Channels
- # announcements (4)
- # aws (1)
- # beginners (172)
- # cider (16)
- # cljdoc (63)
- # cljsrn (7)
- # clojure (150)
- # clojure-dev (8)
- # clojure-europe (26)
- # clojure-gamedev (6)
- # clojure-greece (23)
- # clojure-nl (4)
- # clojure-spec (10)
- # clojure-uk (101)
- # clojurescript (40)
- # community-development (5)
- # cursive (19)
- # datomic (54)
- # emacs (39)
- # figwheel-main (5)
- # fulcro (4)
- # graphql (16)
- # immutant (5)
- # jobs (8)
- # jobs-rus (1)
- # leiningen (1)
- # off-topic (31)
- # planck (1)
- # re-frame (7)
- # reagent (8)
- # reitit (6)
- # remote-jobs (4)
- # shadow-cljs (11)
- # spacemacs (18)
- # specter (2)
- # sql (58)
- # vim (2)
- # yada (5)
@patrickcms yes, there are a few of us. I recommend using https://github.com/thheller/fulcro-expo as a starting point. It’s for Expo, but if you can’t use Expo for some reason, I think @thheller said it should be easy to adapt for pure RN.
I'd like to ask what are you using for routing pages, as fulcro's routing doesn't provide native animations and gestures
So far, I’ve been using Fulcro’s new routing and adding my own gesture handlers (easy to do with Expo). But we don’t get the animations and some other things (like the stack navigator). I’ve actually just started looking into integrating Fulcro with react-navigation. I’ll post (probably in the Fulcro channel) if I get something working.
Alright, thats exactly what I'm trying at the moment Using react-navigation's own state manager is returning a lot of delay in switching pages and lots of workarounds