Open insinfo opened 7 years ago
What's the point of this table? Where's the value in listing all the controls on each platform? Why the columns you have? If v1.0 explicitly aims for support by UWP and Xamarin.Forms, why not all the platforms now (or soon to be) supported by Xamarin.Forms? At the very least I'd have thought you'd put equivalent controls on the same row. There's also lots of things you've put in the XAML Standard column that I haven't seen proposals for. Adding links to each would be much more helpful. You've indicated that the first column is for XAML Standard 1.0 but it doesn't correspond with items marked for that milestone. You've even included items marked for v2.0.
I created this table because it was a request in another post, and I did not have time to align the corresponding controls yet, if you want to help I posted the link just above, but all the items I posted in the column "Standard XAML" A general overview of all posts from this repository I have not added anything that is not in the post titles, for example "Add Control X and Y". I went into each post to do this, and I searched the internet (Site Xamarin ... and etc) and IDEs (Visual Studio, Android Studio etc) to build this table. I put the following columns in the Table: "Proposed for XAML Standard", "IOS", "Android", "WPF", "UWP","Xamarin.Forms","JqueryUI" and "HTML5"
I do not understand the point of this issue. When is it considered done or actioned?
The table would be more useful if the items in the columns were aligned, so you can see a Button control for V1.0, and see what the equivalent control is in the other frameworks that XAML hopes to work with.
It would be even more useful to turn it into a .md file as part of the documentation (after being aligned and ordered per version)
I started trying to align the UWP controls in the doc. HamburgerMenu is now NavigationView, eh?
I think it'd be good to have a version column for planned standard milestone and links to each of the control definitions for the XAML Standard and the platform docs for the others.
Standardizing cross-platform is a VERY hard problem. As a practical matter, it is impossible. Don't go down that road. Don't try to come up with a "universal" set of controls - no good answer will be reached. Instead, use Xamarin.Forms, which includes mechanisms for adapting to specific platform where necessary.
I checked post by post and I made a general overview of all posts so far and I put this table to show what has already been proposed This is without the descriptions of each control, because the table would be very large There must be something missing if you want to contribute. If you want to help align the table, I posted it in google driver and it's public to edit https://docs.google.com/spreadsheets/d/1l_4ACdaYE84SAi5ldfijjeEY-1Jz_SkAdiynB0y0LoY/edit?usp=sharing