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
{{ message }}
Repository navigation
Create a CupertinoTableRow and CupertinoTable #19228
Instead of specifically a CupertinoTable, that could just be a normal ListView. The additional convenience widgets would be a CupertinoTableGroup for grouping, header, footer and a CupertinoTableTile for UITableViewCell styling
@xster going with a CupertinoTable sounds better to me than using a ListView. I think it fits more symmetrically with other Cupertino widgets. Is there any significant reason to avoid that?
Chatted a bit offline yesterday. I was initially concerned that there wouldn't be enough features at the list level to warrant a new class but it seems like there would be. Ideally, create more composable Cupertino-agnostic layers in between while achieving those features like a DividerSeparatedListView etc.
Forms are also primarily short contents so it doesn't use the sliver mechanism (i.e. the entire content is pre-emptively built). It doesn't lazy build rows or have sticky headers etc which need slivers.
@dehypnosis I think that's great that more than two years after 1.0, we finally got something that Android had from the start - proper form fields. But I think we're still missing the CupertinoTableRow and CupertinoTable, aren't we?
I am in the process of completing implementation of CupertinoListTile and CupertinoListView for my personal project. After I am done, I will dedup code between my widgets and CupertinoFormRowCupertinoFormSection because the code is very much similar yet totally different usecase. You can expect a PR by the end of the week. This will include support for ordinary list tile like the ones in iOS Settings and new notched ones like in Notes or Reminders. I just have to eyeball properly some constants before I call it production ready.
Reacted by NAOE Kenichi, Aleksey Zolotov, mono — Masayuki Ono, Erlend, Rouuuge and Hideaki Sago
Even Google's own app team now thinks that Material UI on iOS is a mistake. If I read this article correctly, then they recently decided to use native iOS components instead of Material Design to "really make products feel great on Apple platforms".
So in that spirit: Any updates on filling this iOS UI gap in Flutter?
Reacted by Sebastian Dwornik, NAOE Kenichi and Antonio Germano
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
xster commentedon Sep 1, 2018
Instead of specifically a CupertinoTable, that could just be a normal ListView. The additional convenience widgets would be a CupertinoTableGroup for grouping, header, footer and a CupertinoTableTile for UITableViewCell styling
matthew-carroll commentedon Sep 21, 2018
@xster going with a CupertinoTable sounds better to me than using a ListView. I think it fits more symmetrically with other Cupertino widgets. Is there any significant reason to avoid that?
xster commentedon Sep 25, 2018
Chatted a bit offline yesterday. I was initially concerned that there wouldn't be enough features at the list level to warrant a new class but it seems like there would be. Ideally, create more composable Cupertino-agnostic layers in between while achieving those features like a DividerSeparatedListView etc.
xster commentedon Oct 8, 2018
A good point from xster/flutter-test#1, the touch down should start highlighting the cell
xster commentedon Oct 22, 2018
One note: the highlight color for the cell should be tied with the page transition animation which could be a bit tricky.
fralways commentedon Mar 7, 2020
Just pointing out some expectations, maybe this is already covered. Not sure how much alignment is planned with native.
3 remaining items
TrGiLong commentedon Dec 20, 2020
Hi everyone,
I want to help flutter team to create
CupertinoTable. Is anyone working on this now? Is #24603 related to here?xster commentedon Dec 22, 2020
@TrGiLong no one is working on it currently. We'd love to take PRs if you're willing.
My general impression is that CupertinoRows will be boxes, CupertinoTableSections will be slivers and CupertinoTable will be the Viewport/Scrollable.
ksilz commentedon Dec 22, 2020
@TrGiLong: Doesn't solve PR #70676 this issue here?
TrGiLong commentedon Dec 23, 2020
@ksilz I think not because the table view in iOS has more features like delete, insert button or drag. This PR contains only Form.
ksilz commentedon Dec 23, 2020
@TrGiLong Ah, I see. Thank you!
xster commentedon Jan 6, 2021
Forms are also primarily short contents so it doesn't use the sliver mechanism (i.e. the entire content is pre-emptively built). It doesn't lazy build rows or have sticky headers etc which need slivers.
dehypnosis commentedon Mar 5, 2021
check it: https://medium.com/flutter/whats-new-in-flutter-2-0-fe8e95ecc65 for iOS style form sections. here is flutter 2
ksilz commentedon Mar 6, 2021
@dehypnosis I think that's great that more than two years after 1.0, we finally got something that Android had from the start - proper form fields. But I think we're still missing the CupertinoTableRow and CupertinoTable, aren't we?
campovski commentedon Mar 18, 2021
I am in the process of completing implementation of
CupertinoListTileandCupertinoListViewfor my personal project. After I am done, I will dedup code between my widgets andCupertinoFormRowCupertinoFormSectionbecause the code is very much similar yet totally different usecase. You can expect a PR by the end of the week. This will include support for ordinary list tile like the ones in iOS Settings and new notched ones like in Notes or Reminders. I just have to eyeball properly some constants before I call it production ready.erf commentedon Aug 2, 2021
@campovski any news on the
CupertinoListTile?I found the package cupertino_list_tile, but it is "not a pixel perfect interpretation".
ksilz commentedon Jan 4, 2022
Even Google's own app team now thinks that Material UI on iOS is a mistake. If I read this article correctly, then they recently decided to use native iOS components instead of Material Design to "really make products feel great on Apple platforms".
So in that spirit: Any updates on filling this iOS UI gap in Flutter?
sedwo commentedon Mar 8, 2022
@xster I second @ksilz comment. What's the plan for Flutter to better support iOS UI?
In this specific case, a Cupertino based table view.
github-actions commentedon Aug 3, 2022
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.