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
Support page transitions #22
Comments
Agreed. We need a router, haven't built one yet. @Hixie has been collecting thoughts on URL handling designs here: https://docs.google.com/document/d/1LTdcq3a0d2qCRzUz5tpU62U3HVkxwHJtMKYgc6cVEPU |
Can you elaborate on what you mean by "page transition" and "routes"? |
Router terminology is from Angular: https://docs.angularjs.org/tutorial/step_07 It is a way to build a single-root app where there is a content node which is replaced based on the URL. Something like: http://myweb.io/main.html -> main page, renders header, footer and content = the initial landing page. Page transition is how you jump from one route to next. Say, landing page should fade out and tasks page should fade in. I had done some experiments on mobile web and this was one of the problematic areas in performance. So I wanted to build a stocks detail page in the sample stocks app and transition to it when a stock row is tapped. |
This concept is akin to intents and activities in Android. You can specify what kind of transition you want. |
Yeah, this stuff is still very much in the air. You can see our current incomplete thoughts here: I filed https://github.com/domokit/mojo/issues/174 to track this. |
We now have this feature in the |
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 |
Right now I do page transitions via something like this:
Then passing the app object around. This is very rudimentary. It would be great if we could inject some sort of router to the components so they can request a page transition. Angular does this via defining routes on dart.
The text was updated successfully, but these errors were encountered: