Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BottomNavBar for only iOS is impossible #72

Closed
calderwoodra opened this issue Aug 26, 2019 · 2 comments
Closed

BottomNavBar for only iOS is impossible #72

calderwoodra opened this issue Aug 26, 2019 · 2 comments

Comments

@calderwoodra
Copy link

Currently it's not possible to generate an iOS app with a bottom nav bar and and Android app without one.

This was the code I tested:

PlatformScaffold(
  appBar: PlatformAppBar(title: PlatformText('TEST', ),),
  ios: (context) => CupertinoPageScaffoldData(
      bottomTabBar: CupertinoTabBar(
      items: <BottomNavigationBarItem>[
          BottomNavigationBarItem(
              title: PlatformText("Feed"),
              icon: Icon(Icons.subject),
           ),
          BottomNavigationBarItem(
              title: PlatformText("Settings"),
              icon: Icon(Icons.settings),
          ),
       ],
  )),
  body: Container(),
);
@aqwert
Copy link
Collaborator

aqwert commented Sep 13, 2019

In this case using PlatformScaffold may not be what you need. It maybe better to use PlatformWidget and use Material and Cupertino widgets directly. This library aims to provide a similar interface between ios and android. Having said that, I notice that perhaps it would be better to separate the PlatformScaffold into a Tabbed and NonTabbed version which I may put up at some stage.

@fredgrott
Copy link
Contributor

@aqwert that was my next question of how to do tabbed and you gave me a solution already great!

@aqwert aqwert closed this as completed May 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants