Uno: Add API support matrix browser

[MartinZikmund]

What would you like to be added:

A website/UWP app tool that would provide quick reference on all of UWP API and its support. I imagine it being similar to HTML5/JS support tables at https://caniuse.com/#feat=flexbox, for example like the following quick mockup:

On the left side are the APIs, and columns represent platforms. Green means API is fully supported, orange means partial support (with explanation or link to Uno Docs), red means no support. The cells could also contain the version number where the API was introduced in Uno.

The website/app would allow for quick filtering - so if I am working with a specific class, I could filter for it and see which methods/properties are available, so that I can design my code correctly at first glance.

Why is this needed:

To help developers quickly see, which APIs are already present in Uno and which are not yet. Would be very helpful to increase productivity. I know analyzer is already there, but this would allow to plan ahead of time, before the code is written.

I think this could be generated during build, as this information is already known. Having it in a browsable, easy to glance visual manner would be great.

For which Platform:

• [x] iOS
• [x] Android
• [x] WebAssembly
• [ ] WebAssembly renderers for Xamarin.Forms
• [x] Windows
• [ ] Build tasks
• [ ] Solution Templates

[carldebilly]

You mean something like this?
https://platform.uno/docs/articles/implemented/windows-ui-xaml-controls-textbox.html

TextBox : Control

[davidjohnoliver]

As Carl points out this is already done for view types, though not with exactly the same formatting. Adding the 'version introduced' is a great idea.

At some point I started working on expanding the doc generation to cover all types, not just views, I'll try to find some time to finish that and get a PR up.

[MartinZikmund]

Such a solution would be great. I didn't notice this exists for views, but if it covered the whole API surface, it would be perfect 👌

[robloo]

Woah, that list of implemented/not-implemented view types is perfect! I've been looking for exactly that as I prepare to start a port from UWP.