-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Remove Animations Package reference from Controls package #3578
Comments
I think using the composition api directly would be better than bringing in the animation package |
I did some investigation on some of the interesting dependencies from the controls. ScrollHeaderMicrosoft.Xaml.Behaviors.Uwp.Managed
Microsoft.Toolkit.Uwp.UI
Microsoft.Toolkit.Uwp.UI.Animations
TileControlMicrosoft.Toolkit.Uwp.UI
Microsoft.Toolkit.Uwp.UI.Animations
OtherImageCropper, Eyedropper, InfiniteCanvas all use a bunch of win2d. |
#3611 should take care of |
#3615 Might be hamfisted but its something to remove |
<!-- 🚨 Please Do Not skip any instructions and information mentioned below as they are all required and essential to evaluate and test the PR. By fulfilling all the required information you will be able to reduce the volume of questions and most likely help merge the PR faster 🚨 --> <!-- 📝 It is preferred if you keep the "☑️ Allow edits by maintainers" checked in the Pull Request Template as it increases collaboration with the Toolkit maintainers by permitting commits to your PR branch (only) created from your fork. This can let us quickly make fixes for minor typos or forgotten StyleCop issues during review without needing to wait on you doing extra work. Let us help you help us! 🎉 --> <!-- Add a brief overview here of the feature/bug & fix. --> Sept towards #3578. ## PR Type What kind of change does this PR introduce? <!-- Please uncomment one or more that apply to this PR. --> <!-- - Bugfix --> <!-- - Feature --> <!-- - Code style update (formatting) --> - Refactoring (no functional changes, no api changes) <!-- - Build or CI related changes --> <!-- - Documentation content changes --> <!-- - Sample app changes --> <!-- - Other... Please describe: --> ## What is the current behavior? <!-- Please describe the current behavior that you are modifying, or link to a relevant issue. --> OrbitView uses the Toolkit Animation.Expressions API. ## What is the new behavior? <!-- Describe how was this issue resolved or changed? --> OrbitView uses [ExpressionAnimation](https://docs.microsoft.com/en-us/uwp/api/windows.ui.composition.expressionanimation) ## PR Checklist Please check if your PR fulfills the following requirements: - [ ] Tested code with current [supported SDKs](../readme.md#supported) - [ ] Pull Request has been submitted to the documentation repository [instructions](..\contributing.md#docs). Link: <!-- docs PR link --> - [ ] Sample in sample app has been added / updated (for bug fixes / features) - [ ] Icon has been created (if new sample) following the [Thumbnail Style Guide and templates](https://github.com/windows-toolkit/WindowsCommunityToolkit-design-assets) - [ ] Tests for the changes have been added (for bug fixes / features) (if applicable) - [ ] Header has been added to all new source files (run *build/UpdateHeaders.bat*) - [ ] Contains **NO** breaking changes <!-- If this PR contains a breaking change, please describe the impact and migration path for existing applications below. Please note that breaking changes are likely to be rejected within minor release cycles or held until major versions. --> ## Other information
<!-- 🚨 Please Do Not skip any instructions and information mentioned below as they are all required and essential to evaluate and test the PR. By fulfilling all the required information you will be able to reduce the volume of questions and most likely help merge the PR faster 🚨 --> <!-- 📝 It is preferred if you keep the "☑️ Allow edits by maintainers" checked in the Pull Request Template as it increases collaboration with the Toolkit maintainers by permitting commits to your PR branch (only) created from your fork. This can let us quickly make fixes for minor typos or forgotten StyleCop issues during review without needing to wait on you doing extra work. Let us help you help us! 🎉 --> <!-- Add a brief overview here of the feature/bug & fix. --> Sept towards #3578. Remove the `TileControl`'s usage of the `Animations.Expressions` ns and thus the animations package. ## PR Type What kind of change does this PR introduce? <!-- Please uncomment one or more that apply to this PR. --> <!-- - Bugfix --> <!-- - Feature --> <!-- - Code style update (formatting) --> - Refactoring (no functional changes, no api changes) <!-- - Build or CI related changes --> <!-- - Documentation content changes --> <!-- - Sample app changes --> <!-- - Other... Please describe: --> ## What is the current behavior? <!-- Please describe the current behavior that you are modifying, or link to a relevant issue. --> `TileControl`'s uses `Animations.Expressions` to build expression animation. ## What is the new behavior? <!-- Describe how was this issue resolved or changed? --> `TileControl`'s uses strings to build expression animation. ## PR Checklist Please check if your PR fulfills the following requirements: - [ ] Tested code with current [supported SDKs](../readme.md#supported) - [ ] Pull Request has been submitted to the documentation repository [instructions](..\contributing.md#docs). Link: <!-- docs PR link --> - [ ] Sample in sample app has been added / updated (for bug fixes / features) - [ ] Icon has been created (if new sample) following the [Thumbnail Style Guide and templates](https://github.com/windows-toolkit/WindowsCommunityToolkit-design-assets) - [ ] Tests for the changes have been added (for bug fixes / features) (if applicable) - [ ] Header has been added to all new source files (run *build/UpdateHeaders.bat*) - [ ] Contains **NO** breaking changes <!-- If this PR contains a breaking change, please describe the impact and migration path for existing applications below. Please note that breaking changes are likely to be rejected within minor release cycles or held until major versions. --> ## Other information
This work has been completed. |
Describe the bug
The Animations package is currently being pulled in as a dependency for the Controls package. However, there's only two small uses of it in the package:
RangeSelector
for implicit animations, andScrollHeader
for theQuickReturnHeaderBehavior
.Expected behavior
I think removing the animation for the Tooltip in RangeSelector should be simple enough. I'm not as sure what we do with ScrollHeader as a component.
But migrating these off of the animation package or moving the ScrollHeader to a different package would be a big win for our dependency graph.
This may be dependent on work we do to clean-up the Behaviors/Animations package in general with its reliance on Win2D as well.
Tied to #3062 and #3145
The text was updated successfully, but these errors were encountered: