@benkraus i added you as a collaborator. going through a couple of PRs and merging them now
i’ve been super sick last couple of days so haven’t really been working
will try to get to creating some GH issues around specific tasks today if i can
one big(ish) task that i want to talk with you about is this idea i have around portals which i think could make this lib wayyy more useful to people in the “greenfield” case
Yeah, explain portals some more?
basically i want to make it so that people could put arbitrary react views inside of like the nav bar etc.
this isn’t super hard to do on the surface, but building a good API for it has some subtleties
also, animation is tricky
i’d like for people to be able to declare their views and have animations for transitioning between screens
but we need to be able to do the whole screen transition without rerendering
i think this is possible, but it’s definitely going to require some finesse on the native side
It's somewhat working though in that regard, right?
The shared elements and whatnot
Though, still a ways from defining your own transitions and whatnot
i tried to implement this for custom react views inside the nav bar but couldn't get it to work (admittedly i didn't try too hard)
but i did end up questioning the approach of portals v just rendering a new react root view inside e.g. the nav bar
what's the advantage of using a portal?
@nfcampos using a portal would be rendering a new react root view inside the nav bar, but the contents of it would be decided in the render function of a different root view (the screen’s) which is what makes it a portal
then we're speaking of the same thing
you'll find a fairly primitive implementation of this in a PR on the repo. i've since closed the pr because i couldn't get the positioning/transitions working correctly
the positioning/transitioning is indeed the tricky part