<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>XAML on Dave Voyles</title><link>https://davevoyles.com/tags/xaml/</link><description>Recent content in XAML on Dave Voyles</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 08 Feb 2013 00:00:00 +0000</lastBuildDate><atom:link href="https://davevoyles.com/tags/xaml/index.xml" rel="self" type="application/rss+xml"/><item><title>[Tutorial] Design Time Data + Passing Data Across Pages (WP8)</title><link>https://davevoyles.com/posts/design-time-data-passing-data-across-pages-tutorial-wp8/</link><pubDate>Fri, 08 Feb 2013 00:00:00 +0000</pubDate><guid>https://davevoyles.com/posts/design-time-data-passing-data-across-pages-tutorial-wp8/</guid><description>&lt;p&gt;The most difficult part of this project thus far has been understanding the idea behind MVVM, or Model-View-View Model. Wikipedia defines it as:&lt;/p&gt;
&lt;p&gt;“MVVM facilitates a clear separation of the development of the &lt;a href="http://en.wikipedia.org/wiki/Graphical_user_interface" title="Graphical user interface"&gt;graphical user interface&lt;/a&gt; (either as &lt;a href="http://en.wikipedia.org/wiki/Markup_language" title="Markup language"&gt;markup language&lt;/a&gt; or GUI code) from the development of the &lt;a href="http://en.wikipedia.org/wiki/Business_logic" title="Business logic"&gt;business logic&lt;/a&gt; or &lt;a href="http://en.wikipedia.org/wiki/Back_end" title="Back end"&gt;back end&lt;/a&gt; logic known as the model (also known as the data model to distinguish it from the view model). The view model of MVVM is a value converter, meaning that the view model is responsible for exposing the data objects from the model in such a way that those objects are easily managed and consumed”&lt;/p&gt;</description></item></channel></rss>