310 votesworking on it · 30 comments · Universal Windows Platform » XAML/Controls APIs (UWP) · Flag idea as inappropriate… · Admin →
Hi @Dustin, thanks for adding votes here. We are currently planning on adding markup extensions support right now with ProvideValue (no service provider though). To answer @Mike's question, spec out means that basically we are defining the implementation for the platform. I can anticipate that someone might say 'duh, it's just the same as what you had before' :-) -- to which I would too! However WPF, Silverlight and Noises operate on the .NET Framework and have different underlying technology that UWP does not have...this is why we are designing the implementation. Our goal here is to support ProvideValue like WPF does with the one exception of IServiceProvider, which is a .NET concept that we can't quite solve yet in the UWP platform (also working on these type of things). If you have further questions, please feel free to email me directly email@example.com
349 votes17 comments · Universal Windows Platform » XAML/Controls APIs (UWP) · Flag idea as inappropriate… · Admin →
This will be possible in Windows 10 Creators Update.
Starts about 3:00 in. Once documentation is on dev center, i’ll close this out.
@T.P. -- on your use of SVG for button icons, have you looked at using PathIcon within the AppBarButton? It supports the changing of colors using foreground/background already.
Thanks for the continued feedback. The SVG support we have in Creator's Update is equivalent to the secure static mode from SVG spec: https://svgwg.org/specs/integration/#secure-static-mode.
17 voteson the backlog · 5 comments · Universal Windows Platform » XAML/Controls APIs (UWP) · Flag idea as inappropriate… · Admin →
Thanks @Mark for your comment. Our ISVs (Telerik, Infragistics, DevExpress, Xceed, ActiPro, Syncfusion, etc) have always delivered way more functional DataGrids in every UI platform we've ever created. Our own information shows that these are used far more than any in-box components because of the capabilities they serve. I realize that there is a desire for everything to be in a core platform, but when we look at things like this, and especially given the vast ecosystem of free, Open Source and royalty-free licensed) can you help us understand why you would still want a 'simple' platform one? Having been on the XAML team for quite some time, nothing is simple :-) -- and DataGrid is quite possibly one of the more complex. Does simple mean display, sort, editable, groupable, virtualized? Yeah, that's not simple :-) I hope you can appreciate. This is where we've always loved how the ISV community has delivered far more flexibility for our customer demands. By the way, this isn't a 'no' but we just want to prioritize the most high-value platform capabilities above commodities.