<?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>Silverlight Experiment: Create a PullDown Menu using Storyboards.</title><link>http://blogs.msdn.com/msmossyblog/archive/2008/06/29/silverlight-experiment-create-a-pulldown-menu-using-storyboards.aspx</link><description>This is a basic example of how to create a &amp;quot;PullDown Menu&amp;quot; using Silverlight and Expression Blend. The Objectives The GUI will have a PullDown Menu (UserControl) under the main outer chrome. It's intended that when a user clicks on the &amp;quot;MainMenu&amp;quot;</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Silverlight Experiment: Create a PullDown Menu using Storyboards.</title><link>http://blogs.msdn.com/msmossyblog/archive/2008/06/29/silverlight-experiment-create-a-pulldown-menu-using-storyboards.aspx#8669327</link><pubDate>Mon, 30 Jun 2008 03:56:02 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8669327</guid><dc:creator>Ola Karlsson</dc:creator><description>&lt;p&gt;Hi Scott,&lt;/p&gt;
&lt;p&gt;What's your view on building up the XAML declaratively vs programmatically? &lt;/p&gt;
&lt;p&gt;I've heard some people say that when you're working with something which is known at design time you should always set it up declaratively in the XAML. And only use the programmatic approach when dealing with unknowns, like when pulling in things from a datasource.&lt;/p&gt;
&lt;p&gt;I came to think of it after reading this post where obviously you're building the UI programatically.&lt;/p&gt;
&lt;p&gt;Cheers,&lt;/p&gt;
&lt;p&gt;Ola&lt;/p&gt;</description></item><item><title>re: Silverlight Experiment: Create a PullDown Menu using Storyboards.</title><link>http://blogs.msdn.com/msmossyblog/archive/2008/06/29/silverlight-experiment-create-a-pulldown-menu-using-storyboards.aspx#8670005</link><pubDate>Mon, 30 Jun 2008 07:05:10 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8670005</guid><dc:creator>scbarnes</dc:creator><description>&lt;p&gt;There is no specific ruling or best practice on which of the two. Any whom declare this are wrong firstly as they whole charter for have both options is that, options.&lt;/p&gt;
&lt;p&gt;My personal preference is to keep as much logic out of the XAML as possible, as from personal experience in Flex I found it to be cumbersome at times when I didn't need it to be (ie burying logic into a mutated mix of both MXML and ActionScript 3.0 can get you into trouble..)&lt;/p&gt;
&lt;p&gt;I could also be dragging in some Flex legacy into the new Microsoft world as well? I've not yet mastered the full potential of our UX Platform given it's age, but I've found that with Visual Studio 2008 as a tool along side Expression Blend, the smart money on RAD would have to be on keeping as much of the logic in VS2008 - code.&lt;/p&gt;
&lt;p&gt;For now.. whom knows what the future will hold though going forward?&lt;/p&gt;
&lt;p&gt;Just keep your options open and leave rules to those whom don't believe in Rule #1 of programming. Always look for ways to break rules.&lt;/p&gt;
&lt;p&gt;Scott.&lt;/p&gt;
</description></item></channel></rss>