The alpha phase is recently available in its fourth edition of the platform avalonia. Its creators define it as the "transversal UI framework of the .Net platform", it can be defined as avalonia as a platform based on .Net that works in favor of the creation of multiplatform user interfaces, the latter taking advantage of the new adaptations of .Net for its operation in other systems.
avalonia born with the guidance of WPF and makes it possible to run applications XAML on systems like Linux, Mac and Windows. Without leaving behind the support for mobile phones. It is worth saying that it is delivered as a package NuGet and can be compatible with systems like GTK y Cairo.
The most important characteristics of avalonia can be found in the main web from Visual Studio.
Characteristics of Avalonia 4 phase alpha
In design aspects avalonia it comes with a friendly or familiar looking interface, as its developers define it. That it incorporated dialogues in the system when opening a file, when trying to save one or when selecting from a directory.
In addition, you can also make use of colors and brushes in their different modes in terms of style memories. Which means that now you can have more freedom within the selection of resources, outside the framework that XAML establishes on them. Additionally, support for window icons was also incorporated.
For virtualization lists, Avalonia now offers Article list virtualization. This means that Basically the creation of list boxes was modified one by one for each element of the ListBox across ListBoxItem. For now only create a list box in ListBoxItems during the moments where each article is in a current view. This made considerable progress in speed during this process. This option is configured by default, which does not make it necessary to activate it. If you want to do the opposite action you can disable it in this way in the ListBox: VirtualizationMode = »None»
Among other things, it is known that previously validations had been made for data found in the links within Avalonia. This attached support can be activated with the property EnableValidation with the link true.
Although it is important to note that data validation is not available for the INotifyDataErrorInfo. It is known that work continues to expand support in IDataErrorInfo y System.ComponentModel.DataAnnotations in the near future for the platform.
To provide efficiency in terms of application compatibility for different platforms, the framework of a AppBuilder which will be used to make the relevant configuration in the specific areas of the platform for the application. So that the application can run smoothly on other platforms. In the case of desktop applications, you would have a view like the following:
static void Main ( string [] args )
{
AppBuilder . Configure < App >().UsePlatformDetect () . Start < MainWindow>();
}
Avalonia 4 is also working to offer the graphical API Skia backend via the Skia # command. In the need to displace the current Cairo backend API, for those platforms that are not Windows, Skia, in addition to being a more current graphics API, stands out for being more oriented to the demands of Avalonia 4, in addition to being compatible for mobile platforms.
Last but not least, modifications were made so that the contents of applications in Windows are automatically transferred to the DPI of the monitor that is displayed in the window when it is dragged to another monitor with different settings.
With its presentation in alpha phase Avalonia It gives us a taste of the good that comes with it. Although many details remain to be polished, it is interesting to get an idea of what new and renewed the platform will not bring.
We already see that even Linux is moving towards Microsoft, soon we will see Linux by Microsoft.