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

Proposal: Integrate XAML Behaviors to WinUI & WPF #3813

Open
michael-hawker opened this issue Dec 15, 2020 · 2 comments
Open

Proposal: Integrate XAML Behaviors to WinUI & WPF #3813

michael-hawker opened this issue Dec 15, 2020 · 2 comments
Labels
area-Tooling feature proposal New feature proposal team-Markup Issue for the Markup team wct

Comments

@michael-hawker
Copy link
Collaborator

Proposal: Integrate XAML Behaviors to WinUI & WPF

Summary

The XAML Behaviors have been a relative staple for XAML development for a long time now having IDE support in Blend and working for both WPF and UWP directly with minimal changes (besides namespaces). Since they provide common patterns/interfaces for others to build upon, it could be handy to have these integrated into the platform directly. Especially now with WinUI going open source.

See the XAML Behavior discussion on this topic here and a corresponding WPF request similar to this one here.

Rationale

  • Would be easier to manage and integrate more directly into the XAML platform if coordinated by the platform team. E.g. Styles, Verbosity, etc...
  • Would be easier for other library creators to create components which interact with behaviors or actions without extra dependencies.

Open Questions

  • Would this make it easier to maintain by having the C++ version able to be projected to C# as well vs. the split approach now? Maybe that's done more for easier maintenance with WPF <-> UWP C#?
@michael-hawker michael-hawker added the feature proposal New feature proposal label Dec 15, 2020
@ghost ghost added the needs-triage Issue needs to be triaged by the area owners label Dec 15, 2020
@YuliKl YuliKl added area-Tooling team-Markup Issue for the Markup team labels Dec 16, 2020
@JeanRoca JeanRoca removed the needs-triage Issue needs to be triaged by the area owners label Feb 3, 2021
@Panda-Sharp
Copy link

Up :)

@GuildOfCalamity
Copy link

Are there still plans to integrate this into Microsoft.UI.Xaml?
This should not have to be added as an additional NuGet to projects, as the functionality is sorely lacking in the base classes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-Tooling feature proposal New feature proposal team-Markup Issue for the Markup team wct
Projects
None yet
Development

No branches or pull requests

5 participants