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

State machines #33

Open
nhaarman opened this issue Sep 5, 2018 · 0 comments
Open

State machines #33

nhaarman opened this issue Sep 5, 2018 · 0 comments
Labels
priority:low This issue has a low priority type:needs-design Uncharted territory

Comments

@nhaarman
Copy link
Owner

nhaarman commented Sep 5, 2018

Using a state machine in a Navigator seemed one of the main advantages of using these Navigators when beginning to design the library. In practice actually, using state machines may prove to be more difficult than initially thought -- there's Scene management, View hierarchy saving, Scene state saving, etc. Combining these with a state machine is not that trivial at all.

Especially with the power that comes with the composing of Navigators, state machines become less necessary. There are definitely cases where state machines may be a better choice, but before that happens some more thought in how to actually implement Navigators with them is necessary.

@nhaarman nhaarman added the type:example An example needs to be created label Sep 12, 2018
@nhaarman nhaarman added the type:needs-design Uncharted territory label Jan 30, 2019
@nhaarman nhaarman changed the title State machine example State machines Jan 30, 2019
@nhaarman nhaarman removed the type:example An example needs to be created label Jan 30, 2019
@nhaarman nhaarman added the priority:low This issue has a low priority label Apr 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority:low This issue has a low priority type:needs-design Uncharted territory
Projects
None yet
Development

No branches or pull requests

1 participant