PhoneItemViewModel

   In looking at the Viewmodel structure, I notice that there is a PhoneItemViewModel.  So instead of binding to a collection of Entities, you can bind to a collection of PhoneItemViewModels.

It seems the properties and functions of the ItemViewModel could have been made a part of the partial entity class.

The disadvantage I see of an ItemViewModel is that you can then no longer use convention binding of Caliburn.Micro.  Instead, you have to manually bind to Item.Property.

The advantage I see is that it keeps the ViewModel properties out of the Entity.

Just wondering what your take is on the matter.

Greg