-
Notifications
You must be signed in to change notification settings - Fork 4
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
Navigation flow with modals #6
Comments
couldn't we create a new ion-modal for each clicked link? |
@locness3 I've considered that - however, modals are quite literally overlaid on top of the current view. As someone follows more and more links, the DOM will become massive and cause lag in the application. |
Except if you remove the DOM of non-visible modals - or just use something else than modals for what's the main content of the app. |
@locness3 That's possible, but it would be very difficult due to the structured nature of Ionic Vue - maybe you'd like to take a stab at it? |
When I get some time |
At the time, I wasn't aware about all routing stuff. I think, we should create a seperate page/endpoint/route/whatever you name it |
I can work on that. Of course, this isn't top priority right now. The only reason I didn't consider doing this in the first place was that I'm not sure that Ionic will handle transitions if the project page is not a tab (since we're using a tab-based layout). |
Needs some testing, but I'd think it makes a smooth navigation no matter what. |
... it doesn't, even when using an |
Or maybe it would with |
Okay, it looks like we have to use import { RouterLink } from "vue-router";
export default {
...
components: {
RouterLink
}
} |
@locness3 So we essentially need to use a |
Yes, with the project page being its own route. |
@locness3 Ah, so just get rid of the modals. All righty, sounds good. I'll test it out. |
I fixed the problems with modal navigation in 17711bb. Closing now. |
Should be using the router, but whatever |
In the future if it becomes a problem I'll change it. For now it works fine. |
Re-opening because using proper routes instead of modals would improve the structure of the code. |
Since we're using
<ion-modal>
components to implement projects, profiles, and studios, there are a few issues with navigation. When clicking a project link from another project, the back button goes back to the explore tab. We need to fix that by making it move back to the previous project.The text was updated successfully, but these errors were encountered: