Brain storming:

I think whether the app bar is used with an iOS scaffold or not, it needs to be outside of the PageRoute/CupertinoPageTransition since it doesn't slide with the body content (#9446).

Rather, the hierarchy is more like

Root > CupertinoTabBar > PageView > (CupertinoScaffold: CupertinoNavigationBar + Navigator) > pages

vs Material's

Root > Navigator > page > Scaffold > AppBar + BottomNavigationBar

(not too sure how to deal with fullscreen things like dialog barriers etc yet, maybe add something like look for the eldest navigatorstate)

For sharing/interchangeability, CupertinoTabBar is just going to be dumb UI (maybe we need something else to bundle CupertinoTabBar and PageView together for convenience) so that can just go into Scaffold.bottomNavigationBar.

CupertinoNavigationBar will have a simple mode and an 'immersive' mode. The simple mode just mimics the AppBar with less dynamic stuff. One button left, one button right, one title/segmented control/wtv widget in the middle. Can be used for fullscreen dialogs or with material in Scaffold.appBar for just UI.

In full iOS mode, extract a superclass out of MaterialPageRoute that's easy to share with CupertinoPageRoute. Let CupertinoPageRoute take both the normal body builder and an CupertinoNavigationBar builder. If there's CupertinoScaffold (which would hold an animated navigation bar), it would use the page transition animation controller to also coordinate the crossfade between the 2 CupertinoNavigationBars.

Implement CupertinoNavigationBar #7508

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions