<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Maya to XAML Export Plug-In</title><link>http://blogs.msdn.com/b/mswanson/archive/2005/11/20/495118.aspx</link><description>Thomas Goddard has written and released a freely-available plug-in for Maya that exports model and texture data to XAML. There are some clean-up steps that need to be accomplished before performing the export, and Thomas does a fantastic job of explaining</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Maya to XAML Export Plug-In</title><link>http://blogs.msdn.com/b/mswanson/archive/2005/11/20/495118.aspx#8526831</link><pubDate>Wed, 21 May 2008 10:02:22 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8526831</guid><dc:creator>mike wheelaghan</dc:creator><description>&lt;p&gt;just tried this converter out last night first time.. amazed how clean the model came through in xaml. real quality plugin...top work!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=8526831" width="1" height="1"&gt;</description></item><item><title>re: Maya to XAML Export Plug-In</title><link>http://blogs.msdn.com/b/mswanson/archive/2005/11/20/495118.aspx#499274</link><pubDate>Fri, 02 Dec 2005 10:25:40 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:499274</guid><dc:creator>Michael Swanson</dc:creator><description>Mike: you can always be relied upon for insightful commentary, and I agree with you completely. When I wrote the &amp;quot;interface&amp;quot; to &amp;quot;experience&amp;quot; line on Sunday afternoon, I thought it was a bit weak, but I couldn't think of something better (and still catchy) at the time. You've nailed it, though. Immersion is a much more appropriate word.&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=499274" width="1" height="1"&gt;</description></item><item><title>re: Maya to XAML Export Plug-In</title><link>http://blogs.msdn.com/b/mswanson/archive/2005/11/20/495118.aspx#499256</link><pubDate>Fri, 02 Dec 2005 07:52:47 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:499256</guid><dc:creator>Mike Carnevale</dc:creator><description>Interesting post, Mike. You mention the &amp;quot;leap from graphical user interface to graphical user experience,&amp;quot; but I think it's much more than the interface --&amp;gt; experience transition. Our current interfaces are a form of an experience, albeit a somewhat static and detached one. I think what technologies like Maya and WPF offer is a more &amp;lt;i&amp;gt;immersive&amp;lt;/i&amp;gt; interface/experience.&lt;br&gt;&lt;br&gt;Part of the &amp;quot;immersion effect&amp;quot; will be caused by the ability of designers and developers alike to provide more customized UI's than we've ever seen before. Less widgets and generic components adapted to interfaces, and more made-to-order interface elements that suit the functions of the software to a tee. Exciting stuff.&lt;br&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=499256" width="1" height="1"&gt;</description></item></channel></rss>