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

YaruMasterDetailPage: fix navigator flaw #899

Open
Feichtmeier opened this issue May 18, 2024 · 3 comments
Open

YaruMasterDetailPage: fix navigator flaw #899

Feichtmeier opened this issue May 18, 2024 · 3 comments
Labels
bug Something isn't working widgets

Comments

@Feichtmeier
Copy link
Member

YaruMasterDetailPage navigator design is sadly flawed.

There are two navigators

One in portraitlayout:

And one in LandscapeLayout:

The YaruMasterDetailPage allows passing a key to BOTH of the navs, which does not help at all. Actually it makes things worse.
For simpler apps that eventually does not happen or when only landscape layout is used.
However a simple scenario in musicpod makes this easy to show:

Bildschirmaufzeichnung.vom.2024-05-18.13-23-58.mp4

(recorded from vscode debugging thus screen record flickering... old topic)

@Jupi007 @spydon @d-loose do you have any smart idea how to save this switching between portrait and landscape?
Otherwise, also because from a design perspective this switching is actually not very helpful, I would suggest that we either sunset this widget and convert to landscape layout or to create a differnt layout when the window is really small

In the weather app I made an expriment which shows the list of master tiles only in a Drawer in narrow windows, WDYT?

Bildschirmaufzeichnung.vom.2024-05-18.13-27-00.mp4
@Feichtmeier Feichtmeier added bug Something isn't working widgets labels May 18, 2024
@spydon
Copy link
Collaborator

spydon commented May 18, 2024

The best is probably to just sunset it and start using a better pattern.

@Feichtmeier
Copy link
Member Author

The best is probably to just sunset it and start using a better pattern.

You mean better code pattern, right? Because we will continue to need this UI pattern of Master/Detail

@spydon
Copy link
Collaborator

spydon commented May 18, 2024

The best is probably to just sunset it and start using a better pattern.

You mean better code pattern, right? Because we will continue to need this UI pattern of Master/Detail

Yes, better code pattern :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working widgets
Projects
None yet
Development

No branches or pull requests

2 participants