Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Native Support of MVVM Pattern #434

Open
AhmedAbuelnour opened this Issue Mar 11, 2019 · 6 comments

Comments

Projects
None yet
4 participants
@AhmedAbuelnour
Copy link

AhmedAbuelnour commented Mar 11, 2019

I really wish to see that one day, we have a native support for MVVM Pattern in all XAML based applications (Xamarin , UWP , and WPF) like you did in ASP.NET MVC

We need a native support of MVVM Pattern to make it more clean and well structured and no need for injecting tons of services and code editting to set up the project to be ready to be used.

@dotMorten

This comment has been minimized.

Copy link
Collaborator

dotMorten commented Mar 11, 2019

There's all the key MVVM ingredients needed: INotifyPropertyChanged, INotifyCollectionChanged, ICommand, and binding support all out of the box.

Could you explain what you mean by "native support" ?

@AhmedAbuelnour

This comment has been minimized.

Copy link
Author

AhmedAbuelnour commented Mar 11, 2019

@dotMorten i meant built-in MVVM Pattern, i know there are some useful classes to make your application MVVM based, but what i mean a ready made MVVM structure of the project, and simplify the process of binding like a command for instance. and the validation process and the navigation between the windows or pages

no need for injecting libraries that change their code every release, that have tons of bugs and messy code structure

ASP.NET MVC for example, is a perfect example for what i mean.

@dotMorten

This comment has been minimized.

Copy link
Collaborator

dotMorten commented Mar 11, 2019

@AhmedAbuelnour Is there any reason you can't just use Prism, MVVMLight, MvvmCross etc? Why would it need to be dictated by the platform?
IMHO 'patterns' can't really be built-in, as they are just that: "a pattern" that you choose to follow - It's not an API. The APIs for doing MVVM is already there - in fact they are all the way down in .NET Standard which is awesome.
So I'm curious what sort of APIs specifically that you feel a lacking?

@AhmedAbuelnour

This comment has been minimized.

Copy link
Author

AhmedAbuelnour commented Mar 11, 2019

There are some lakes API with the following
What about direct binding with events and commands ?
what about simple navigation and carrying data with routing?

@dotMorten

This comment has been minimized.

Copy link
Collaborator

dotMorten commented Mar 11, 2019

Frame and NavigationService is already there in WPF, including forwarding data.

Command binding is also already there with ICommand and many controls having Command properties to bind to.

So am I right in saying you just want to be able to bind an event directly to a method? (similar to UWP's x:Bind method binding?)

@bigworld12

This comment has been minimized.

Copy link

bigworld12 commented Mar 13, 2019

this should be more like replacing wpf's Binding with UWP's x:Bind and unify the binding experience for both platforms

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.