Discussion: just a thought

[ghost]

I noticed that most contributors are suggesting a new controls or features, I think the scope of this project is to agree on which controls to standardize from different platforms not to suggest a new feature, like for example we should discuss that we take stackpanel from UWP or stacklayout from xamarin. am I right here or wrong?

Thank you for contributing to XAML Standard! We are at the very early stages of a long term collaboration towards a unified XAML vocabulary that all XAML developers can comfortably rely on to target all your desired end points.

All submissions

• Have you read the principles?
• Have you checked that your post fits the nature of proposals?
• Have you checked to ensure that there aren't other open issues for the same topic?
• Have you followed the contributor code of conduct?

If you are posting an API for XAML standard consideration:

• Add a brief overview of what you are proposing and why it belongs in XAML Standard (in keeping with the principles of the effort).
• Provide a clear usecase/scenario that describes how this API benefits in sharing cross-platform UI code, preferably a scenario from your experience or application that clearly illustrates why a control/API would benefit from being standardized.
• Add a brief example in XAML syntax for your proposal.
• Provide links to issues/discussions where this proposal has been talked about as well as any other pointer to where this originated or got discussed that could describe the motivation.

For discussions that are not concrete proposals, please prefix title with "Discussion" so we can categorize accordingly.

[insinfo]

Yes I agree that the initial thinking is an alignment between the UWP, WPF and Xamarin platforms, plus the standard can not stop here, the XAML standard has to continuously evolve, this means that the standard will add or set new features over time , this includes specification of new controls and standardized APIs that will have to be implemented by the XAML standard supporters.

I believe that the XAML Standard has to keep advancing

[touseefbsb]

XAML standard should be like .NET STANDARD where eventually xaml and c sharp can take over all possible platforms, and we can write one app with c sharp and xaml which might run on android, ios, uwp, linux, mac os and web as well. xaml standard and .net standard should become the new standard way of building software.

[insinfo]

@touseefbsb I completely agree and subscribe below, this would be great if we could write native high-performance applications, truly cross-platform with XAML and C#

[insinfo]

And for this to be possible it is necessary to assemble the pieces of the great puzzle that is here in github, the ecosystem XAML and C#

http://cshtml5.com/
https://github.com/AvaloniaUI/Avalonia
https://github.com/yuvaltz/Granular
https://github.com/sunnycase/MPF
https://github.com/lrz/mono-wasm
https://github.com/SteveSanderson/Blazor
http://www.mono-project.com/news/2017/08/09/hello-webassembly/

[touseefbsb]

@insinfo yes all these pieces can be assembled but the project of this level should be directly handled by Microsoft itself and backed up by the community of c# and xaml developers to make it a success. Majority of c#/xaml developers dont really like to code in JS and the infinite number of frameworks out there. Alternatively we should make .net and xaml standard so strong and performant that we can create every typeof software and websites with just these 2 languages without needing so many frameworks.

[insinfo]

@touseefbsb I fully agree, especially with this part

"create every typeof software and websites with just these 2 languages without needing so many frameworks."

[ghost]

I also agree that the standard cannot stop here, but I think everything should be done step by step 1st standardization then further development. while going through the discussion I have got another idea I will open a new discussion issue, maybe microsoft engineers will be convinced by it.

…

________________________________ From: insinfo <[email protected]> Sent: Sunday, November 19, 2017 10:03:22 PM To: Microsoft/xaml-standard Cc: aua; Author Subject: Re: [Microsoft/xaml-standard] Discussion: just a thought (#222) Yes I agree that the initial thinking is an alignment between the UWP, WPF and Xamarin platforms, plus the standard can not stop here, the XAML standard has to continuously evolve, this means that the standard will add or set new features over time , this includes specification of new controls and standardized APIs that will have to be implemented by the XAML standard supporters. I believe that the XAML Standard has to keep advancing — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fxaml-standard%2Fissues%2F222%23issuecomment-345536626&data=02%7C01%7Cauasoft%40hotmail.com%7C3c9bd0f97c46464a717d08d52f77d3a3%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636467114058674170&sdata=JfV0TWPFuxfZiHYnYutJkSwCCYXp0IahM9KRTGieSoA%3D&reserved=0>, or mute the thread<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAPRAgjSobNqUb1GBL2TkjGM4CIpN00hGks5s4G1qgaJpZM4QehFI&data=02%7C01%7Cauasoft%40hotmail.com%7C3c9bd0f97c46464a717d08d52f77d3a3%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636467114058674170&sdata=XpCT9eGzk2c4MMk5lpQ41f5XOCArbwF6UkFBr9C0iFI%3D&reserved=0>.

[touseefbsb]

yeah convincing microsoft regarding all these ideas is most important thing, bcz this level of technology has to be directly engineered by microsoft itself

[touseefbsb]

should we open a user voice as well regarding this? @auahub , @insinfo

[Mike-E-angelo]

FWIW @touseefbsb you can add your votes and feedback to this idea here:
https://visualstudio.uservoice.com/forums/121579-visual-studio-ide/suggestions/10027638-create-a-ubiquitous-net-client-application-develo

Most popular idea on Visual Studio's UserVoice ATM, passing 8k votes as of last week.

[touseefbsb]

@Mike-EEE Thanks a lot. Thatis the perfect uservoice for this requirement it has too many votes, I hope microsoft acts quickly on this and make this a reality ASAP.

[ghost]

@Mike-EEE thats a great suggestion
but the problem as I think it is too complicated for microsoft to start with and I think my idea in issue #228 may be simpler to start with, then try to reach the the ultimate goal mentioned in the user voice.

[insinfo]

@Mike-EEE I voted for your UserVoice

[Mike-E-angelo]

Thanks all. We're actually a lot closer to this reality than you might think. Once Mono officially adds support for WebAssembly (and they are on their way), we'll be able to reach the Big Four: Droid, iOS, Windows, and Web. The roads will be paved and it will be a matter of putting the cars on them to drive. As such, when discussing models (cars) here, don't forget about Noesis which is my top vehicle of choice ATM. 😎

[weitzhandler]

This repo is sleeping.
Looks like MS pays to it very little attention.
Last commit was November '17.

IMHO, MS has the power to change the multi-platform development face of the entire world if they provide a complete C#+XAML solution for all platforms (UWP+Web), but then MS also has to provide easy tooling to make development time less painful, and that includes:

• Speeding up the XAML Standard release
• Look like Xamarin isn't planning to implement the very essential controls it lacks, such as ItemsControl, horizontal ListView, CheckBox, RadioButton etc., and that's because their agenda says only controls native to all platforms are implemented (how stupid)
• Easy tooling for XAML-based clients and server side interaction (such as Breeze# or TrackableEntities, but officially maintained)
• Client side entity generators
• XAML designers or at least previewers for ALL platforms (Xamarin.UWP and XAML web included)
• Easier ways to deploy to all platforms in one click (App Center does a decent job)

[touseefbsb]

@weitzhandler the features you just described, please make a proper uservoice for that and post the link here so that we all can contribute and vote for that. we have to work hard in order for this to become a reality and I agree with all ur points that we need those crucial controls. c# and xaml really need to target all big 4.

[insinfo]

@weitzhandler Undoubtedly, we need better, more competitive, smarter, and more complete development tools, integrating artificial intelligence and node-based visual programming with UI and UML designer integration, so we can build the next generation of intelligent software that interprets the voice in natural conversation, touch, gestures, vision among other means of human machine interaction.

[weitzhandler]

@touseefbsb
I don't really believe in UserVoice. The reason is that in UserVoice, only the first suggestions get upvoted and interesting, while all the new ones never get anyone's attention and will remain abandoned and unread forever. UserVoice is really an overrated service.
But anyway, here you go!
And Here's a discussion about client-side entities.

@insinfo Sky is the limit, but before we try reaching the sky, I'm merely requesting the basic functionality we were used to in WinForms and Silverlight+RIA services to be back, which is included in the aspects I pointed out before.

[touseefbsb]

@weitzhandler I knw it is overrated but we dont have any other choice :P

[weitzhandler]

@touseefbsb make one, you're Microsoft... lol

[touseefbsb]

hhaha I wish I could :P @weitzhandler