<?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>An Interview with the Developer of a Silverlight 2 Ribbon Interface</title><link>http://blogs.msdn.com/synergist/archive/2008/12/02/an-interview-with-the-developer-of-a-silverlight-2-ribbon-interface.aspx</link><description>The first project that I did when I started experimenting with Silverlight 1.0 (at that time it was called WPF/E) was an Office Ribbon UI .&amp;#160; It was a great learning experience and when Silverlight 2 betas started becoming available, I started to</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Silverlight Cream for December 02, 2008 -- #444</title><link>http://blogs.msdn.com/synergist/archive/2008/12/02/an-interview-with-the-developer-of-a-silverlight-2-ribbon-interface.aspx#9167410</link><pubDate>Wed, 03 Dec 2008 03:39:25 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9167410</guid><dc:creator>Community Blogs</dc:creator><description>&lt;p&gt;Chris Anderson, Tim Heuer, Michael S. Scherotter, and Jonathan van de Veen. Shoutout: If you don't read&lt;/p&gt;
</description></item><item><title>re: An Interview with the Developer of a Silverlight 2 Ribbon Interface</title><link>http://blogs.msdn.com/synergist/archive/2008/12/02/an-interview-with-the-developer-of-a-silverlight-2-ribbon-interface.aspx#9176083</link><pubDate>Thu, 04 Dec 2008 21:33:21 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9176083</guid><dc:creator>Pete Brown</dc:creator><description>&lt;p&gt;Hi Michael&lt;/p&gt;
&lt;p&gt;Not to be a wet blanket here, but...&lt;/p&gt;
&lt;p&gt;The ribbon has some serious baggage attached to it. In order to use *any* implementation of the ribbon control, you have to license and comply with the &amp;quot;shalls&amp;quot; and &amp;quot;musts&amp;quot; in the Office UI Guide.&lt;/p&gt;
&lt;p&gt;I've been hesitant to use any ribbon control due to that set of restrictions, and how the available third party controls don't meet the requirements 100%, and therefore don't comply.&lt;/p&gt;
&lt;p&gt;I totally get why MS has done that, but it is not something we're used to.&lt;/p&gt;
&lt;p&gt;Q: What are component vendors’ responsibilities?&lt;/p&gt;
&lt;p&gt;A: As for other licensees, component vendors who intend to implement the new Office UI must license the UI from Microsoft and register their products that include the UI. &amp;nbsp;In addition, component vendors are required to include a statement in their license agreements with their customers directing the customers to &lt;a rel="nofollow" target="_new" href="http://msdn.microsoft.com/officeui"&gt;http://msdn.microsoft.com/officeui&lt;/a&gt; to obtain their own license if they wish to create products with the UI. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;Q: What are the responsibilities of customers of component vendors?&lt;/p&gt;
&lt;p&gt;A: Third parties who obtain Office UI components from component vendors and intend to use them in software need to separately seek a license from Microsoft and comply with its terms in using the components.&lt;/p&gt;
&lt;p&gt;Pete&lt;/p&gt;</description></item><item><title>re: An Interview with the Developer of a Silverlight 2 Ribbon Interface</title><link>http://blogs.msdn.com/synergist/archive/2008/12/02/an-interview-with-the-developer-of-a-silverlight-2-ribbon-interface.aspx#9180966</link><pubDate>Sat, 06 Dec 2008 07:05:09 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9180966</guid><dc:creator>Michael S. Scherotter</dc:creator><description>&lt;p&gt;Pete,&lt;/p&gt;
&lt;p&gt;You're right - this is a new model for Microsoft. &amp;nbsp;The baggage that you mention is a very explicit specification about how the ribbon should look and feel. &amp;nbsp;And for the ribbon it's a lot of work.&lt;/p&gt;
&lt;p&gt;From my read of the specification, about 99% of it could be implemented in Silverlight.&lt;/p&gt;
&lt;p&gt;Even if they are not creating the control themselves, licensees of the ribbon should read the specification to understand what is needed and required.&lt;/p&gt;
&lt;p&gt;Michael&lt;/p&gt;
</description></item></channel></rss>