You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Flutter 1.17 comes with NavigationRail component which is part of material design guideline. It suggest adapting BottomNavigationBar [mobile] -> NavigationRail [tablet] -> NavigationDrawer [desktop]. Check image below:
The text was updated successfully, but these errors were encountered:
I think this should be adapted with this package it self following material design guidelines. If there is a BottomBar defined then It should be replaces with NavigationRail in larger screen (check animation).
It is my package I created too, but I agree. I can have this adapt it as well. This package was made before the rail was added to the spec. Responsive scaffold is a drop in scaffold replacement whereas navigation rail is a new layout widget similar I
in feature set.
Hi @rodydavis
I need this functionality and am starting work on it.
How would you like this feature to be implemented?
Just wrapping the responsive_scaffold in a NavRail does not seem to be the way to go.
How should the tablet view be handled (Currently the AppBar/titlebar continues over the nav rail when in tablet mode, see the picture).
Should the NavigationRail be integrated into the master view? Should we just drop the appbar of the master and detail and show the unified one?.
Also The Master view supports usage of Slivers so how should they be handled?
I'm deprecating my own NavRail and if I already do the work I'd like to contribute it back to the project :)
Flutter 1.17 comes with NavigationRail component which is part of material design guideline. It suggest adapting
BottomNavigationBar
[mobile] ->NavigationRail
[tablet] ->NavigationDrawer
[desktop]. Check image below:The text was updated successfully, but these errors were encountered: