Katherine MVVM, and other MV* patterns are what can be used for laying out models, some frameworks would go as far as having niceties to match the properties or even picking a control for layout that would match the type of property (e.g. if your in your model you have DateTime then a date time picker is used, or you can specify the type of custom control to be used).
Using or making a framework can be beneficial in having a uniform way of dealing with UI that is directly generated from model as oppose to manually making them. How ever the time to learn/make a frame work is substantial and is only justified if one is expecting some type of uniformity that can be handled automatically by a framework rather than in a manual and error prone way by a human. One of the main ideas behind XAML (WPF), was the ability to break up the visual and code parts to be handled by separate teams. Even sighted programmers are hopeless with layout with XAML and it is preferred to pass it to the designer team. I still recommend the book Illustrated WPF for start, and at some point eventually moving to a framework or using MVVM. Regards Arjang On 22 January 2013 01:30, Katherine Moss <[email protected]> wrote: > I think I may have seen that somewhere, but what is the ppoint of using > MVVM frameworks? What are they, anyway? **** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Greg Keogh > *Sent:* Monday, January 21, 2013 3:40 AM > > *To:* ozDotNet > *Subject:* Re: Xaml basics: where to start?**** > > ** ** > > My favourite book on WPF is an old one called Windows Presentation > Foundation Unleashed by Adam Nathan -- Greg **** >
