You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
With the full-blown Visual Studio IDE being the only one that supports XAML, and UNO Platform's team claiming that they're working on one for VS Code, when I've asked directly, Atom (which I'm starting to like) has no such compatibility and would benefit from having such compatibility. In the VS Code repo itself, it was labeled as "out of scope", and for their OmniSharp server repo, it was acknowledged that UNO Platform is working on it but hasn't had a solution for it since the issue was made in 2019. The overall point is to make an open-source and cross-platform solution for this problem; there already several GUI C# frameworks that support XAML and are cross-platform (Avalonia - UNO Platform - .NET 6 MAUI), but with no way to actually code for them on non-Windows OSes efficiently (and for new non-Windows users to pick XAML up), XAML is essentially locked out to anyone without access to Visual Studio (and FYI, MonoDevelop doesn't even compile for Linux OSes anymore; so if anyone is going to suggest that it has XAML support, there's my retort).
Motivation
Providing a package for XAML support will break lack of XAML support in non-Visual Studio IDEs and non-Windows OSes for essentially the first time and will help these developers actually contribute to projects that (can) technically already support their OS as a target platform and/or for developers from non-Windows OSes seeking to work on projects to start using these cross-platform frameworks. Being able to be served the food and also not having the tool(s) to make the food yourself, both in open-source, is frankly dumb.
Describe alternatives you've considered
At the moment, the only solutions are:
Wait for UNO Platform to finally finish their implementation for VS Code (which I have not seen the code for anywhere)
Ask Microsoft nicely to implement it for VS Code which they likely won't do for various reasons
(Both of which, obviously, have nothing to do with Atom)
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Summary
With the full-blown Visual Studio IDE being the only one that supports XAML, and UNO Platform's team claiming that they're working on one for VS Code, when I've asked directly, Atom (which I'm starting to like) has no such compatibility and would benefit from having such compatibility. In the VS Code repo itself, it was labeled as "out of scope", and for their OmniSharp server repo, it was acknowledged that UNO Platform is working on it but hasn't had a solution for it since the issue was made in 2019. The overall point is to make an open-source and cross-platform solution for this problem; there already several GUI C# frameworks that support XAML and are cross-platform (Avalonia - UNO Platform - .NET 6 MAUI), but with no way to actually code for them on non-Windows OSes efficiently (and for new non-Windows users to pick XAML up), XAML is essentially locked out to anyone without access to Visual Studio (and FYI, MonoDevelop doesn't even compile for Linux OSes anymore; so if anyone is going to suggest that it has XAML support, there's my retort).
Motivation
Providing a package for XAML support will break lack of XAML support in non-Visual Studio IDEs and non-Windows OSes for essentially the first time and will help these developers actually contribute to projects that (can) technically already support their OS as a target platform and/or for developers from non-Windows OSes seeking to work on projects to start using these cross-platform frameworks. Being able to be served the food and also not having the tool(s) to make the food yourself, both in open-source, is frankly dumb.
Describe alternatives you've considered
At the moment, the only solutions are:
(Both of which, obviously, have nothing to do with Atom)
Additional context
N/A
The text was updated successfully, but these errors were encountered: