Comments on CapableObjects: The ViewModel

Thanks for the excellent blog post. Can you explai...

2010-02-04T12:21:29.337+01:00

Thanks for the excellent blog post. Can you explain more about what you meant here?

Quote:

(Notice the datetime picker is gone? Datetime picker is in WPFToolkit so we do not use it by default. Implement ViewModelWPFUserControl.OnColumnUIOverride to add your own components to its layout engine.)

Hello Hans, The approach of having an intermediat...

2010-01-06T05:33:25.945+01:00

Hello Hans,

The approach of having an intermediate layer between the UI and Domain layers is extremely useful. And using ECO in order to model this layer leverages the approach even more. I personally use ECO to model Presenter classes (according to the MVP pattern). And my presenter classes contain such attributes as "canAdd" and "canDelete" (similarly to your "CanStartGame" and "CanEndGame").

However in real-world applications it's too time consuming to have corresponding ViewModel attributes for each and every UI element. That's why I often bind UI elements directly to the Domain. But each time when some intermediate processing is required I place it into the middle layer (specifically into ECO-modeled ViewModel classes).

Overall, great article, thank you :)

--
Oleg Zhukov

We have viewmodel support for win apps and wpf app...

2010-01-05T19:34:27.379+01:00

We have viewmodel support for win apps and wpf apps, but what about silverlight and asp.net?

Enjoying your blogs, Hans. Very helpful resource.

Throg

Hans, I think your explanatory blog posts are exc...

2010-01-05T17:48:06.703+01:00

Hans,

I think your explanatory blog posts are excellent and a sorely needed resource for people trying to understand the real depth of ECO.

Many thanks

Mitch

Thanks Daniel! Samples are updated this morning; ...

2010-01-05T16:29:36.485+01:00

Thanks Daniel!

Samples are updated this morning; they will be in the daily build tomorrow (6 jan,2010) .
And sorry for the API-break - I hate API breaks and I do them very reluctantly. In this case you need to change EcoSpaceTypeName="YourEcoSpaceType" to EcoSpaceType="{x:Type yourns:YourEcoSpaceType}"
The good thing is that this new syntax will force the developer to actually add the EcoSpaceType reference to the xaml wich will ensure that the preview of the ViewModelWPFUserControl actually works, and also the new syntax makes it more stronlgy typed.

Very nice. The one problem that I do see, is th...

2010-01-05T15:01:00.907+01:00

Very nice.

The one problem that I do see, is that you replaced the property EcoSpaceTypeName with EcoSpaceType(in the ViewModelWPFUserControl). I do not have a problem with that. But, for the developers that started developing using the ECO ViewModels and do have a good amount of ViewModel usage in their applications will find it very unpleasant that they will have to change all the XAML that is using the property EcoSpaceTypeName (here I can talk for myself). I would prefer to see that EcoSpaceTypeName would still exist for the next version, but that in the release notes and the help that it is mentioned that it is deprecated and will no longer exist in the version thereafter.

Also, can you update the samples in the daily builds to reflect this change in properties?

And, keep up the excellent work.