Can I ask why XAML? Nothing against it - I just have only ever worked with CSS and am trying to understand the differences, and pros / cons. As I would not "feel at home" as the WPF devs mentioned, trying to decide if it's something worth learning new, or just for those who started with Webforms.
Is there any drawback to drawing every pixel like what Avalonia does, compared to Uno for example, which strips down native controls of their chrome and applies its own, but otherwise, where possible, delegates rendering to the host platform?
Assuming you do not want native look, which if your stripping the controls down and replacing the chrome, then you dont. Then native controls are just an overhead, and less portable. i.e. when you run on an minimal embedded device with no desktop environment, and no native toolkit (which doesnt exist on Linux for example), then you dont have any native controls to back. The only reason to do this is to inherit accessibility and integration with the OS without having to implement os specific apis for accessibility and IME for example. Avalonia implements those apis. So for an app with non-native design, its an advantage.. less over head, more portability.
That's a pretty Amazing demo!
Loved the capabilities of Avalonia framework!
I'll definitely give it a try for my next project!
Where is this guy ? Amazing bird sounds in the background!!! Great presentation, thanks Dan
Nice ui toolkit. We need a truly cross platform ui for c#
Dan seems Linus Torvalds xD
Can I ask why XAML? Nothing against it - I just have only ever worked with CSS and am trying to understand the differences, and pros / cons. As I would not "feel at home" as the WPF devs mentioned, trying to decide if it's something worth learning new, or just for those who started with Webforms.
The advanced tutorial doesn't exist under the link in the video. Do you know where it is now?
I'm stuck at Opening Dialog part, even when copy pasting the code It still not work :(
Will it be possible to create the Forms like WinForms? I mean, drag and drop a button, a text box, etc..
i have a problem with the constructor when I start the app
Would you please be so kind and submit a support request with more details? rider-support.jetbrains.com/hc/en-us/requests/new
Excelente Tutorial muchísimas gracias.....saludos de los andes peruanos
The links don't work
Is there any drawback to drawing every pixel like what Avalonia does, compared to Uno for example, which strips down native controls of their chrome and applies its own, but otherwise, where possible, delegates rendering to the host platform?
Assuming you do not want native look, which if your stripping the controls down and replacing the chrome, then you dont. Then native controls are just an overhead, and less portable. i.e. when you run on an minimal embedded device with no desktop environment, and no native toolkit (which doesnt exist on Linux for example), then you dont have any native controls to back.
The only reason to do this is to inherit accessibility and integration with the OS without having to implement os specific apis for accessibility and IME for example. Avalonia implements those apis. So for an app with non-native design, its an advantage.. less over head, more portability.