In order to set the stage and gather some ideas and suggestions from the community, here is how navigation is currently performed on the two platforms.

On Android we navigate to a new page like this:

var fragmentTransaction = manager.beginTransaction();
fragmentTransaction.add(this.containerViewId, newFragment, newFragmentTag);
fragmentTransaction.setTransition(transition);
fragmentTransaction.commit();

For going back on Android we do something like this:

manager.popBackStack(backstackEntry[BACKSTACK_TAG], android.app.FragmentManager.POP_BACK_STACK_INCLUSIVE);

On iOS the Frame has a UINavigationController and we navigate to a new page like this:

this._ios.controller.pushViewControllerAnimated(viewController, animated);

this._ios.controller.setViewControllersAnimated(newControllers, animated);

depending on the the navigation type.

Going back on iOS is done like this:

this._ios.controller.popToViewControllerAnimated(controller, animated);

The full-source code is located in frame.android.ts and frame.ios.ts

I am open to suggestions how to incorporate the custom transitions into our existing logic. The basic unit for configuring a navigation is the NavigationEntry so we can add some kind of transition information there which we can later use when we call the native Android and iOS navigation API's.

Let's gather different perspectives and ideas about the best and easiest way to implement such a feature.

Uh oh!

Page Navigation Transitions #811

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions