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

Tab Control #618

Open
slovnicki opened this issue Jun 3, 2023 · 0 comments
Open

Tab Control #618

slovnicki opened this issue Jun 3, 2023 · 0 comments
Assignees
Labels
enhancement New feature or request proposal An idea
Milestone

Comments

@slovnicki
Copy link
Owner

slovnicki commented Jun 3, 2023

This is a work in progress proposal and will be updated with implementation details

For more details about where this is coming from, visit v2 Roadmap Discussion or v2 Roadmap Wiki.
This issue might get separated into multiple issues when implementation details become clearer;

  • interact with tabs internally
  • handle delegate priorities
  • rewrite how history is treated
  • rewrite back button dispatchers

Motivation

When we "navigate" through tabs within the application, this is not handled by Navigator, but is a navigation event from user's perspective. Currently, to connect parent Beamer with tabs, most often when we have child Beamers within each tab, we would define a listener in both ways and call setState() / Beamer.update(..., rebuild: false). We will try to connect the tab control with Beamer internally which should provide a better developer experience and remove the need for questioning "Am I doing this the right way?".

Furthermore, if we connect all "navigation events" with Beamer, then dealing with history and back buttons becomes trivial, hopefully.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request proposal An idea
Projects
None yet
Development

No branches or pull requests

1 participant