-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[Spec] Transitions #6
Comments
SuggestionPerhaps a property that receives an animation instead of an Example:
Or predefined "Named Transitions"
|
Regarding shared transitions, please note that if you want to make a transition from a list of items (for example a Collectionview) the "TransitionTag" property could not be enough to identify the view you want to animate. Imagine a DataTemplate with a list of items containing an image and a text, every image is different but the TransitionTag is always the same (for example: "ImageToTransition"). When you tap an element, the Navigation Renderer need to know exaclty what element need to be translated, and if you have a single tag for all your images in the CollectionView this could be a problem. In my plugin i resolved using a TransitionGroup property wich i use to identify the element to translate. I would like to contribute to this feature but my code for Android is not stable enough (there are problems with ChildFragments when using TabbedPages/MasterPage, but in shell i think is fine), also in iOS i sue some hacks to make good transitions shape. I reworked a lot of code from the first version and now looks better but i dont think is good enough to go in core, but i'm ready to help and contribute if needed |
Btw a lot of my code could be greatly simplified if some properties can be integrated in the main core |
@felipebaltazar It could be something similar to the proposal to create custom transitions in TabView xamarin/Xamarin.Forms#10773 I will do some tests and after that we will review the Spec. @GiampaoloGabba It will definitely be great to have your feedback on this API. If you want to contribute, as in Xamarin.Forms we will accept PRs and I will be happy to help you. About the parameter that you indicate for collections, I have reviewed it and you are right. Mnn, we can add an extra property to cover these cases ( |
i tried this approach but it was a bit difficult. For example in a collectionview we can start a navigation based on the SelectedItem change. Btw i'm planning to write here a small doc covering the basis architecture i used to develop this (how to track transitions and how to make it happen in iOS, because there is not native support to that and i had to develop everything by hand, while it is much easier in Android, if you exclude child fragments generated by tappedpage and MasterDetail) Just in case there are maybe some good ideas to port here and exclude the bad ones, wich, i'm sure, will be a lot :) |
Sounds good @GiampaoloGabba, thanks! |
Sounds good!!!! https://github.com/HorusSoftwareUY/Xamarin.Forms.Skeleton |
What's the status on this? It's the oldest open issue in this repo. Added to "Under consideration" about 6 months ago. Is it still under consideration? |
* Create build.yml (#4) * Create build.yml * Update build.yml * Update build.yml * Removed Blazor projects from solution. * Added a solution to be used for ci/cd on mac build agents. * Update build.yml * Moved ci/ci solution to build folder. * Update build.yml * Started work on nuspec files. * Update build.yml * Fixed paths in Build solution. * Update build.yml * Update build.yml * Fixed nuspec files. * Fixed another path. * More path updates. * Added additional nuspec files. * Fixed path. * Try secret * Tried secrets 2 * Fixed nuspec file. * Updated the workflows. * Updated workflows again. * Switched from run_number to run_id (#5)
This should have much higher priority in my opinion. |
This can be really cool feature |
Is there any update on this? |
Is this going to be on roadmap? |
If I was a betting man, I'd put my money on "no". |
That was funny, Really this transition so much required. Any workaround? |
I think Flutter has it |
it would be cool to see this going forward |
Really, really we need this!!! |
I checked and at least on Android all the page transition code is internal, and there is no way to override it |
For the moment this package works fine. I tested it in net7.0 and 8.0 |
While that looks like a cool project, it doesn't seem to offer the kind of transitions that are requested here |
@Phantom-KNA While it looks nice, it seems to require Shell, which I don't use. |
setup unit tests for binding intermediate representation
Kind of shocked that there isn't a good way to specify page transition animations in MAUI. :( |
Soo, anybody knows whats the deal with this? I created an entire application in MAUI.. |
I’m switching to Flutter |
|
Any updates on this still? |
Maybe someday after dotnet 9 release... :/ |
Transitions
Maui already has a complete animations API allowing you to create a live and fluid content on a page. However, what happens when navigating between pages?.
This spec defines a Maui transitions API. We have two types of well-differentiated transitions:
API
Traditional transitions
For the traditional transitions, we need a new enumeration with the supported transitions:
And, include new properties in the Page to allow page transitions using NavigationPage and Shell:
Shared element transitions
On the other hand, we need a way to allow the shared element transitions. The key is a way to "link" the same item available in two different pages.
We will have the TransitionTag attached property to the supported elements inherited from View:
The use would be:
Tag the control to transition in the source page.
And tag the control to transition in the destination page.
Scenarios
Let's see some examples.
XAML Example
A sample using transitions between pages:
A sample using shared transitions elements:
Page 1:
Page 2:
Notes
TransitionTag
in source and destination page needs to match in order to display the transition.TransitionTag
in a page needs to be unique.Difficulty : Medium
The text was updated successfully, but these errors were encountered: