Community Feedback Requested: WinUI Controls for Avalonia. #5893
Replies: 15 comments 64 replies
-
ColorPicker |
Beta Was this translation helpful? Give feedback.
-
|
@Splitwirez Thats a browser compatibility issue, just use a different one. Graphics are in the description at the very top. |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
I also need a color picker. If there is something to test, let me know 😉 I would be happy to help |
Beta Was this translation helpful? Give feedback.
-
|
You can see the current progress on this issue: #4179 (comment). |
Beta Was this translation helpful? Give feedback.
-
|
Completed with #8215, feel free to test |
Beta Was this translation helpful? Give feedback.
-
RatingControl
|
Beta Was this translation helpful? Give feedback.
-
|
This control is very limited in WinUI and wasn't updated in ages. |
Beta Was this translation helpful? Give feedback.
-
|
Might bringing |
Beta Was this translation helpful? Give feedback.
-
|
This nice Needs just a fraction of changes to work with Avalonia 11 Preview 4 and don't forget to include style into the Here is how you could extend and customize it, for example: |
Beta Was this translation helpful? Give feedback.
-
SplitButton
|
Beta Was this translation helpful? Give feedback.
-
|
I saw an issue post a while back from someone who'd wanted to look into this, along with its toggle-able counterpart, but was waiting on Flyout...now that |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I signed up for this one too. It should be quite easy considering all the code floating around. I will try to reach out to @amwx and work out a good strategy. |
Beta Was this translation helpful? Give feedback.
-
|
Update: This was added to master in PR #7422 |
Beta Was this translation helpful? Give feedback.
-
Flyout |
Beta Was this translation helpful? Give feedback.
-
|
Already done |
Beta Was this translation helpful? Give feedback.
-
PersonPicture
|
Beta Was this translation helpful? Give feedback.
-
|
I'll actually downvote this one as I think it's far too specialized and application specific. A control for displaying a user identify, really? Even if this was an attempt by Microsoft to standardize on how user identities are pictured on Windows it certainly doesn't apply cross-platform. |
Beta Was this translation helpful? Give feedback.
-
|
I think this one is easy to implement via DataTemplate. |
Beta Was this translation helpful? Give feedback.
-
NavigationView
|
Beta Was this translation helpful? Give feedback.
-
|
See #2521 There are multiple avenues for this:
I am curious if all the advanced hierarchical menus are included with port three (@amwx) as that requires 'tree' support in SelectionModel with was not implemented in Avalonia. Plan was a separate TreeSelectionModel or similar or just implement it for the control only. As so many people/companies have asked for this control I think it would be accepted (#2521 states as much). However, it is quite large and highly specialized so someone would likely need to agree to maintain it. |
Beta Was this translation helpful? Give feedback.
-
|
@robloo My port is basically up to date with the current version in WinUI and is a direct C++ to C#/Avalonia port (as best as that can be). I took the original SelectionModel port and used that, so yes hierarchical and all is already there. The only caveat is that my lib defaults to the new WinUI styles (although, I have made it so it can still be used with the base Fluent theme in Avalonia without needing to adopt the new styles). Also as pointed out in gitter last week, multiple data templates (DataTemplateSelector equivalent) aren't supported yet. |
Beta Was this translation helpful? Give feedback.
-
ProgressRing
|
Beta Was this translation helpful? Give feedback.
-
|
brb taking a crack at doing this without Lottie |
Beta Was this translation helpful? Give feedback.
-
|
Lottie in both UWP and Avalonia implementations has better theoretical performance because it's executed on render thread and does not work with xaml logical tree, unlikely simple animations in both frameworks. On other hand Lottie controls are less customizable. |
Beta Was this translation helpful? Give feedback.
-
|
PR for this one incoming, no Lottie lib required. |
Beta Was this translation helpful? Give feedback.
-
|
Progress bagels, fresh out of the oven: #6003 |
Beta Was this translation helpful? Give feedback.
-
|
This control now seems in limbo. Past PR's were closed and there is no response in #7716 |
Beta Was this translation helpful? Give feedback.
-
TeachingTip
|
Beta Was this translation helpful? Give feedback.
-
|
Seems like some flyout with extra steps. Not sure if this is general-purpose enough. |
Beta Was this translation helpful? Give feedback.
-
|
Well, I think its an attempt to standardize this concept more for end users. Having tips displayed in a standard way makes things more user friendly and familiar which is especially important in the case of teaching. Otherwise, I agree this may be too specialized. |
Beta Was this translation helpful? Give feedback.
-
ToggleSplitButton
|
Beta Was this translation helpful? Give feedback.
-
|
This would come over the same time as SplitButton and likely DropDownButton. All buttons are fair game in my opinion and it's on my todo list. |
Beta Was this translation helpful? Give feedback.
-
|
Update: This was added to master in PR #7422 |
Beta Was this translation helpful? Give feedback.
-
CommandBar
|
Beta Was this translation helpful? Give feedback.
-
|
Another question with this: CommandBar contains: |
Beta Was this translation helpful? Give feedback.
-
|
I partially agree that staying in line with WinUI 3's take would be desirable...I say "partially" because I can't help but feel that this argument would likely be a moot point if Avalonia were to rename the Also, with the help of Avalonia's style selectors, using the regular button controls would be fairly easy, no? And another thing...I already have a |
Beta Was this translation helpful? Give feedback.
-
|
The AppBar* controls for command bar have a special Icon and Label property. These properties make a lot of sense in the context of menus. Loosing them means everyone has to do it themselves. So we would trade speed of development for generalization. |
Beta Was this translation helpful? Give feedback.
-
|
@robloo That's a fair point...but perhaps I should've mentioned that my |
Beta Was this translation helpful? Give feedback.
-
|
This exists in FluentAvalonia now. |
Beta Was this translation helpful? Give feedback.
-
ContentDialog
|
Beta Was this translation helpful? Give feedback.
-
|
Can be considered as part of this feature, which also requires managed fallback dialog implementation |
Beta Was this translation helpful? Give feedback.
-
|
I would argue this should ONLY be implemented as a managed overlay: the same as UWP. This makes the most sense for all platforms to be easily supported including mobile. A NativeDialog would be another control IMO. |
Beta Was this translation helpful? Give feedback.
-
|
@robloo I'm in agreement with that as valid and valuable option, though I do think that "modal popup window where possible, managed overlay otherwise" is a valid use case as well, so perhaps it might be worthwhile to offer both behaviours somehow? Maybe even as another Though that may still leave the question of which should be the default behaviour... |
Beta Was this translation helpful? Give feedback.
-
AnimatedIcon
|
Beta Was this translation helpful? Give feedback.
-
|
I raised a lot of similar concerns with Lottie in the original discussion. I would prefer XAML itself is updated to support all these things. If not updating StoryBoard XAML Animations, the integration with Lottie needs to be much further improved and generalized. However, I quickly lost that discussion and everyone is switching over to Lottie for even determinate progress scenarios (as I predicted at the time). microsoft/microsoft-ui-xaml#1858 (comment) and others microsoft/microsoft-ui-xaml#1858 (comment) |
Beta Was this translation helpful? Give feedback.
-
|
I must say.. with my experience of porting Lottie over to Avalonia.. I just think it's insane that they are using it for even the most banal stuff. It's great for large and complex animations but a progressbar? srsly? |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, just because they're taking what they see as the path of least resistance doesn't mean it's a good idea for Avalonia to do the same. Heck, the entire premise of Avalonia itself kind of flies in the face of the notion of "taking the path of least resistance", no? |
Beta Was this translation helpful? Give feedback.
-
|
Microsoft is also getting into the "meta" programming/design concepts. They are using a single design source to generate styles and design elements for many frameworks at once. Because Lottie is well supported on the web and mobile is probably why they went that direction for WinUI too. I certainly agree if we can avoid it we should though. |
Beta Was this translation helpful? Give feedback.
-
@robloo Then I guess it's a good thing I've already set out to do the |
Beta Was this translation helpful? Give feedback.
-
MapControlI'll add this one with a big caveat: I don't expect Avalonia to roll it's own MapControl. However, there should be a partnership with Mapsui in my opinion to get a MapControl ready-to-use with Avalonia. |
Beta Was this translation helpful? Give feedback.
-
No, I was talking about older APIs with .NET 5/6, such as MapControl from Windows Community Toolkit (using XAML Islands) - that works only on .NET Core 3.1 and older. It's technically should be possible to use XAML Islands for WinForms or WPF inside of Avalonia app. But again, only on .NET Core 3.1 and older. |
Beta Was this translation helpful? Give feedback.
-
Ah, sorry, misunderstood. Yea, XAML Islands isn't available at all yet and that is slotted for some unknown date in the future. |
Beta Was this translation helpful? Give feedback.
-
|
Mapsui is now MIT license instead of LGPL3 which should make it a lot more usable with Avalonia apps. |
Beta Was this translation helpful? Give feedback.
-
|
Mapsui 4.0 (currently in beta) will include Avalonia support: This one can be considered complete as well. Perhaps it should be recommended in the docs some place though. |
Beta Was this translation helpful? Give feedback.
-
|
I think awesome avalonia is the right place to mention it |
Beta Was this translation helpful? Give feedback.
-
|
Native WebBrowser using NativeControlHost. |
Beta Was this translation helpful? Give feedback.
-
|
So...you don't think leveraging the renderer from Chromium/Chromium Edge is contributing to the monopoly issue? I'm curious as to why, but...something tells me that's probably a question best saved for Discord DMs... |
Beta Was this translation helpful? Give feedback.
-
|
Unlike IE6, chromium is open sourced. So the fact it has become almost a monopoly is not nearly as much of a concern. Linux is a monopoly on high performance scientific computers but nobody minds. This is how it always goes, when a monopoly starts to stagnate new ideas come in which is how IE6 was defeated. The same is true of very large business who become too big to change and recognize good ideas, smaller agile companies eventually defeat them: look at what Avalonia itself is doing because Microsoft is now so big and mismanaged? This cycle is everywhere, even forests. Don't fear an open source monopoly. Eventually it will be replaced when it looses its way. Until then we can all enjoy some standardization. (That said, I use Firefox because it isnt monetizing data). |
Beta Was this translation helpful? Give feedback.
-
|
@robloo You've raised a valid point...it's certainly good that Chromium is at least open-source. But it's one thing for there to be a monopoly in a specific niche...it's another thing entirely for there to be a monopoly over something that was once referred to as an "information superhighway" (and still lives up to that description today, arguably far more so than when the term was popularly used). And no, smaller, nimbler companies don't always defeat the larger players. Windows has been the desktop OS of choice for most people for a long time now, and that hasn't changed yet. The internet is a really big deal. Sure, a Chromium monopoly wouldn't give Google absolute power over the internet itself...but it would give them a great deal of power over the ability to access the internet. They could make that codebase do what they see fit (such as continuing to validate the very privacy concerns which you yourself cited as your motivation for maining Firefox), and due to its sheer size, a fork, offshoot, or competitor aiming to allow people to evade those terms would have an ever-growing uphill battle on their hands in their quest do so. I'm not saying I think you're wrong, but I am saying I fear that I might also have a point. As for how this affects Avalonia...well, if Avalonia's default offering for displaying web content is based on Chromium's tech, that could end up meaning that the "default behaviour" for web content in Avalonia (which, let's face it, is likely what most use devs wanting to display web content in Avalonia will use) is to push Google's disregard for user privacy on that front as well. ...the web standards aren't strict enough to make retroactively swapping Chromium's tech for some alternative in a later Avalonia release viable, are they? (e.g. if say, Avalonia 0.11 had a Again, I apologize for my paranoia...but you know what they say..."you're not paranoid if you're right". I hope I'm wrong about all of this, but I fear my concerns may someday be warranted, at least in part. |
Beta Was this translation helpful? Give feedback.
-
|
While it's a good discussion, I don't think it's a good place for it.
|
Beta Was this translation helpful? Give feedback.
-
|
Just putting a link here: https://github.com/maxkatz6/AvaloniaWebView/ |
Beta Was this translation helpful? Give feedback.
-
FontIcon / PathIcon / BitmapIcon |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
Hey!
I've recently seen the incredible work of @amwx, who has been porting WinUI controls over to Avalonia. This has started a discussion about which (if any) WinUI controls should be ported and included in Avalonia and how should we prioritise them.
I've included below some WinUI controls that would be helpful to have in Avalonia to get things started. Feel free to add any I've missed (only WinUI controls), and you want to see ported.
To cast your vote, please thumbs up (👍) or thumbs down (👎).
Your feedback is incredibly valuable for us to understand the community's desires, so please vote and share your thoughts!
Beta Was this translation helpful? Give feedback.
All reactions