[Docs][SupportedFeatures-Tables][Github-Issue-Templates][Feedback][Enhancement-Request] Please update the Platform specific feature/api support tables and GitHub Issue Templates with v6.0 target and renderer naming conventions #21735
Description
What would you like clarification on? 🤔
I was reading the Image Control Page, that links to the StorageFile.ReadStorageFileFromApplicationUrlAsync Docs and with the not longer Multi Head Uno App Solution/Project Strucutre, it's difficult for me to really understand this table on the top region of this page that should tell me as reader about the supported state for our target platforms in Uno.
The Difficultness in this, to help you understand my point, is the naming of the column headers that should tell me the platform.
Since you added, up from the uno.sdk v6.0, the Differencing between the Renderers SkiaRenderer and Native, the naming convention of Skia as equivalent for Desktop is in my opinion (not longer) a real equivalent we should automatic imply.
I for example do target net9.0-desktop and develop on Windows 11 pro which would then be Desktop (Windows) in my understanding. Assuming you would mean in this table for example Skia == Desktop and the user does maybe make use of SkiaRenderer while targeting Android, which we now can, thanks to Uno's 6.0 release, we have a duplication of targets. And for me searching for the answer for Is this feature supported on Desktop targeting to run on Windows? well, I still don't know the answer!
Maybe you mean:
Skia (Wpf) == Desktop (Windows) -> Yes, we have support for this on your target!
But could also mean:
Skia (Wpf) == Uno Islands embedded in Wpf app, which I tryed and hopelessly failed (following the Uno Islands docs tutorial and sample app) with the error of the Wpf Designer & Compiler in the end was telling me, that WinUI controls are not supported to be embeeded in Wpf apps.
I have at the moment no full list of the Desktop target supported full list, but Skia (Wpf) is defintly nothing that would make me imply Windows, so would be really nice if you could consider to update those in the future!
Concern 📚
Clarification of capabilities 💡
Renderer 🎨
- Skia
- Native
Affected platforms 📱💻🖥️
Desktop (Windows), Desktop (macOS), Desktop (X11), Desktop (Linux Framebuffer), Build tasks
Any feedback? 💬
Tip
Maybe you could change the column header namings to the ones we have here for the docs/Enhancement-Request issue GitHub template, that would fit this need much better 👍
[!NOTE]
While the GitHub unoplatform repo(s) issue template I am currently using is showing this maybe to be targeted Naming, this does not apply, until now, to all other active Uno Repository's
This caused for me already multiple times the same problem and difficultness as mentioned for the tables in the docs when opening a Bug Report or other Report with those in the unoplatform repositories.
So, if you would consider to update those too, it would help me a lot, to provide you better and more useable Feedback/Reports in the future 👍 💯