<?xml version="1.0" encoding="utf-8"?>

























	
	



	
	
	

	
		
		
		

		
		
			
			
			
			
		
	
	
	
	
	
	


<rss version="2.0">	
	<channel>
		<title>Radiant Core: xaml tag</title>
		<link>http://www.radiantcore.com/</link>
		<description>All of the Radiant Core posts tagged with xaml.</description>
		<language>en-ca</language>
		<copyright>Copyright 2006, Radiant Core Inc. All rights reserved.</copyright>
		<managingEditor>webmaster@radiantcore.com</managingEditor>
		<webMaster>webmaster@radiantcore.com</webMaster>
		
			
			
			
			
			
			
			
			

			
				
			
			<item>
				<title><![CDATA[Microsoft User Experience Round Table Trip Report Part 5: Wrapping Up]]></title>
				<author>Jay Goldman &lt;info@radiantcore.com&gt;</author>
				<link>http://www.radiantcore.com/blog/archives/16/03/2007/msuxroundtablereport5</link>
				<guid isPermaLink="true">http://www.radiantcore.com/blog/archives/16/03/2007/msuxroundtablereport5</guid>
				<comments>http://www.radiantcore.com/blog/archives/16/03/2007/msuxroundtablereport5#comments</comments>
				<description><![CDATA[<div id="syndicatePage">This is the fifth and final post in the <a href="http://www.radiantcore.com/blog/archives/12/03/2007/msuxroundtablereport1" title="Radiant Core Blog: Microsoft UX Round Table">Microsoft UX Round Table</a> series.</div><br /><br /><p>What a week it's been! Had I known that it was going to take me about 25 pages and 7,000 words to describe our trip, I never would have volunteered for this gig :) I hope you've enjoyed reading through this as much as I've enjoyed putting it together and that this information is of value to some of you out there. Today is the final post in this series and provides a blissfully short summary, so if you're only going to read one of the five posts, make it this one (although you'll miss the Ali G clip).</p><br /><br /><h2>The New Microsoft (Again)</h2><p>In <a href="http://www.radiantcore.com/blog/archives/13/03/2007/msuxroundtablereport2" title="The New Microsoft (Again)">Tuesday's post</a>, I talked about how Microsoft is turning a new leaf and repositioning themselves as a design-focused organization. I touched on how there's a lot of new blood breathing life into the beast and how they are making massive investments into UX for high-risk products like <a href="http://office.microsoft.com/products" title="Microsoft: Office 2007">Office 2007</a> and the <a href="http://office.microsoft.com/en-us/products/HA101679411033.aspx" title="Microsoft: The new Microsoft Office user interface overview">Ribbon</a>.&nbsp; I covered the development of the <a href="http://firstlook.nytimes.com/?category_name=times%20reader" title="NYT: Times Reader Beta">NYT Reader</a> application and how it carefully balances layout and readability issues with brand and content. These are both examples of the positive impact that design can have when factored into your process and a very elementary and basic level and I applauded Microsoft for their efforts. You can find out a little more about their new focus in the <a href="http://www.microsoft.com/design/" title="Microsoft: Design Center">Microsoft Design Center</a> website.</p><br /><br /><h2>Design Matters (Maybe?)</h2><p> In <a href="http://www.radiantcore.com/blog/archives/14/03/2007/msuxroundtablereport3" title="Design Matters (Maybe?)">Wednesday's post</a>, I provide the corollary in which I talked about how we saw an equal number of examples where design (and UX specifically) had not been taken into account. We looked at the <a href="http://www.microsoft.com/virtualearth/" title="Microsoft: Virual Earth">Virtual Earth</a> Windows Vista <a href="http://gallery.live.com/default.aspx?l=1" title="Microsoft: Gadget Library">Gadget</a> which violates the <a href="http://msdn2.microsoft.com/en-us/aa370759.aspx" title="Microsoft: User Experience Guidelines for Gadgets">User Experience Guidelines for Gadgets</a>, and at <a href="http://www.microsoft.com/products/expression/en/Expression-Blend/default.mspx" title="Microsoft: Expression Blend">Expression Blend</a> which seems to be aimed at the very broad demographic of 'designers' without much consideration as to who that might be specifically. And I managed to sneak in an <a href="http://www.youtube.com/watch?v=nkuOuxRD1Bc" title="YouTube: Ali G invents the ice cream glove">Ali G clip</a> about ice cream gloves that's still making me laugh a full 24 hours later.</p><br /><br /><h2>Expression</h2><p> In <a href="http://www.radiantcore.com/blog/archives/15/03/2007/msuxroundtablereport4" title="Expression">Thursday's post</a>, I gave a review of the new <a href="http://www.microsoft.com/products/expression/en/expression-studio/default.mspx" title="Microsoft: Expression Studio">Expression Studio</a> suite, which includes the <a href="http://www.microsoft.com/products/expression/en/expression-web/default.mspx" title="Microsoft: Expression web">Web</a>, <a href="http://www.microsoft.com/products/expression/en/expression-design/default.mspx" title="Microsoft: Expression Design">Design</a>, <a href="http://www.microsoft.com/products/expression/en/expression-blend/default.mspx" title="Microsoft: Expression Blend">Blend</a>, and <a href="http://www.microsoft.com/products/expression/en/expression-media/default.mspx" title="Microsoft: Expression Media">Media</a> products. I liked Web but wished for a Mac OS X version, thought Design was an Illustrator knock-off with the sole advantage of being able to handle XAML, felt that Blend would be a useful tool for us if we built Windows applications, and wished that Media provided the ability to easily work from shared catalogues.</p><br /><br /><h2>Wrapping Up</h2><p>It's been almost a month since our trip which has given me a fair bit of time to think about what we'd seen and heard. The last five days have really helped me to form some conclusions and I think, in the end, the experience was exactly what I expected it to be. It was an honour to be invited to participate and I hope that I have other opportunities to do the same with Microsoft and with other firms (though I might hold off on the epic blog post series after!). It's not often that you have an opportunity to peek inside the kimono of a big software company and to get a sense of what they're thinking and working on. Like it or not, almost all of us use their software every day of our lives and they have shaped our industry like no other force. I have a lot of respect for the Microsofties and this trip reinforced that they burn their torches with the same passion and strength of belief as our colleagues in the Open Source world.</p><br /><br /><p><a href="http://www.radiantcore.com/blog/authors/mkewart" title="Martin Kuplens-Ewart">Martin</a> joked that I should end the series with a surprise announcement that Radiant Core was going to ditch our Macs and switch over to Windows and I really thought about it (the joke announcement, not the reverse-switch), but in the end I was worried that I'd have a revolt on my hands. The truth is that even after two days of learning about their products and plans, I still don't really get it. One of our fellow attendees, <a href="http://atomiq.org/" title="Gene's blog">Gene Smith</a>, commented that I was <a href="http://atomiq.org/archives/2007/03/links_for_20070314.html" title="Atomiq: links for 2007-03-14">under-reporting the general scepticism in the room</a> and I think he was right. Those of us in the industry, especially my fellow UX folk, have grown used to expecting little from Microsoft and being underwhelmed. The video which Microsoft produced as a study of their own bloated box design, entitled <a href="http://www.youtube.com/watch?v=aeXAcwriid0" title="YouTube: Microsoft re-designs the Microsoft iPod 2005 Package">Microsoft re-designs the Microsoft iPod 2005 Package</a>, was brilliant not only because it was funny but because it was true. Apple is smaller than Microsoft by several orders of magnitude and has a fraction of their cash reserves and market share, and yet they consistently lead their industry because Apple builds products which people <strong>love</strong>. We are victims of marketing as much as anything else, but Apple is cool and hip and now and Microsoft is increasingly becoming boring, square, and then. The <a href="http://www.apple.com/getamac/" title="Apple: Get a Mac">Mac vs. PC</a> ad campaign is winning people over, not because Macs are necessarily better at photos and video, but because people want to buy into the belief that they are. This is an important point: other than the XBOX 360, people don't tend to have an overwhelmingly positive emotional response to Microsoft's products and they don't inspire the unbridled want lust in the way that only the <a href="http://www.apple.com/iphone" title="Apple: iPhone">iPhone</a> can. At the end of the day, we run our business on Mac OS X and Apple hardware because it <strong>is</strong> easier to use, because it just works when we need it to, and because we have far fewer issues and tech support calls than we ever did running Windows. I started this series off by saying that I was no longer the Jobs worshipping, Apple flag waving fan boy that I used to be and that's definitely true. This conclusion isn't an attempt to sell you on making a switch or on how clever we are for our platform decision, though it would have been in days of yore. Bear with me for a moment while I bring us around to the final thoughts.</p><br /><br /><p><strong>We believe in Open in all of its forms.</strong> We use an operating system which is built on top of an Open Source kernel (<a href="http://en.wikipedia.org/wiki/Mac_OS_X" title="Wikipedia: Mac OS X">Mac OS X</a> runs on top of the <a href="http://en.wikipedia.org/wiki/Darwin_%28operating_system%29" title="Wikipedia: Darwin Operating System">Darwin</a> kernel which Apple released in 2000 under the <a hreg="http://en.wikipedia.org/wiki/Apple_Public_Source_License" title="Wikipedia: Apple Public Source License">Apple Public Source License</a>). We run an Open Source web browser which we helped to develop (<a href="http://www.mozilla.com/en-US/firefox/" title="Mozilla: Firefox">Mozilla Firefox</a> is released under the <a href="http://en.wikipedia.org/wiki/Mozilla_Public_License" title="Wikipedia: Mozilla Public License">Mozilla Public License</a>). We currently build our software on a stack which rests on the most popular web server in the world (<a href="http://www.apache.org/" title="Apache">Apache</a> is released under the <a href="http://www.apache.org/licenses/" title="Apache: Licenses">Apache License Version 2.0</a>), includes an Open Source Java Application Server (<a href="http://tomcat.apache.org/" title="Apache: Tomcat">Tomcat</a> is also part of the Apache project) and an Open Source database (<a href="http://www.mysql.com/" title="MySQL">MySQL</a> is released under the <a href="http://en.wikipedia.org/wiki/Gpl" title="Wikipedia: GNU General Public License">GNU General Public License</a>). We write our software in a (mostly) Open Source language (<a href="http://java.sun.com/" title="Sun: Java Technology">Java</a> was <a href="http://www.sun.com/2006-1113/feature/" title="Sun: Sun Opens Java">recently released under the GNU GPL Version 2</a>) and develop in an Open Source development environment (<a href="http://www.eclipse.org/" title="Eclipse">Eclipse</a> started life as an IBM project and is released under the <a href="http://www.eclipse.org/legal/epl/notice.php" title="Eclipse: Eclipse Public License">Eclipse Public License</a>). We are very active members of the <a href="http://www.barcamp.org" title="BarCamp: Wiki">BarCamp</a> community in <a href="http://barcamp.pbwiki.com/TorCamp" title="BarCamp: TorCamp Home">Toronto</a> and around the world and we dedicate a fair portion of our time to promoting the adoption of Open outside of our industry by organizing events like <a href="http://toronto.transitcamp.org/" title="TransitCamp: Wiki">TransitCamp</a>. We believe so strongly in this movement that we are exploring the possibility of releasing <a href="http://www.radiantcore.com/foundation" title="Foundation Website Management Platform">Foundation</a>, our Website Management Platform, under an Open Source License before the end of 2007.</p><br /><br /><p>Microsoft is typically held up as the counter-example to the Open Source world in that their business practises in the past have been very closed, proprietary, and predatory. The decision to make Expression Web speak standard XHTML is a very good one and the right thing to do, but it's tempered by the decision to build the Expression Suite on <a href="http://en.wikipedia.org/wiki/XAML" title="Wikipedia: XAML">XAML</a>, a proprietary file format published for use by the public. They occupy a strange position in the technology universe, balanced on both sides of a dichotomy in which their <a href="http://research.microsoft.com/" title="Microsoft: Research">Research</a> labs are building some of the most innovative software in the world and yet their product divisions build products which engender little interest from consumers (<a href="http://www.zune.net/en-US/" title="Zune: Welcome to the Social">Zune</a>) or fall short of expectations (<a href="http://www.microsoft.com/windows/products/windowsvista/default.mspx" title="Microsft: Windows Vista">Vista</a>). There are rumbles out there that say Microsoft has lost their mojo and are becoming less and less relevant in a world which is focused on the web and which is starting to show a stronger and stronger interest in the value of capital-D Design (led by companies like <a href="http://www.apple.com" title="Apple">Apple</a>, <a href="http://www.oxo.com/" title="Oxo Good Grips">Oxo</a>, and <a href="http://nymag.com/nymetro/health/features/11700/" title="NYMag: Target ClearRx">Target</a> just to name a few). I think there's some truth to those suspicions and you don't need a richter scale to measure them: just compare the worldwide festivities of the Windows 95 or XP launches to the downright mellow and uninspiring "The Wow is Now" campaign for <a href="http://www.microsoft.com/windows/products/windowsvista/default.mspx" ttle="Microsoft: Vista">Vista</a>. Other than the work coming out of the Research labs and XBOX teams, Microsoft is not an innovative company. I had this conversation with a few of my fellow attendees over drinks and the best examples they could come up with to defend innovation at MS were in the data warehousing field. I didn't argue - and I'm sure they're important to Data Warehousers - but that's not much of a defence. Focusing on design is a good move (even if it is playing catch up) but it needs to be a move which starts at the very top of the organization and which inspires everyone to take part. What we were shown during our visit was a great beginning and time will tell where it leads, but given that they are a technology company driven forward by the development of technology, I suspect that it will fall short if the hardcore developers within the company don't buy into it. Bill Gates is worshipped within the organization as the Alpha Geek and his <a href="http://www.usdoj.gov/atr/cases/exhibits/20.pdf" title="DOJ: Internet Tidal Wave memo (PDF)"><em>Internet Tidal Wave</em></a> memo successfully mobilized Microsoft to make an enormous course change in 1995 - where's the <em>Design Tsunami</em> equivalent?</p><br /><br /><p>That's it for Day 5 and the Microsoft Trip Report series! Subscribe to our <a href="http://feeds.feedburner.com/RadiantCore" title="FeedBurner: Radiant Core RSS Feed">RSS feed</a> to make sure that you don't miss out on future insights from the Radiant Core.</p>]]></description>
				<category>Trip Reports, User Experience, Taking Care of Business</category>
				<pubDate>Fri, 16 Mar 2007 09:00:00 GMT</pubDate>
			</item>
		
			
			
			
			
			
			
			
			

			
				
			
			<item>
				<title><![CDATA[Microsoft User Experience Round Table Trip Report Part 4: Expression]]></title>
				<author>Jay Goldman &lt;info@radiantcore.com&gt;</author>
				<link>http://www.radiantcore.com/blog/archives/15/03/2007/msuxroundtablereport4</link>
				<guid isPermaLink="true">http://www.radiantcore.com/blog/archives/15/03/2007/msuxroundtablereport4</guid>
				<comments>http://www.radiantcore.com/blog/archives/15/03/2007/msuxroundtablereport4#comments</comments>
				<description><![CDATA[<div id="syndicatePage">This is the fourth post in the <a href="http://www.radiantcore.com/blog/archives/12/03/2007/msuxroundtablereport1" title="Radiant Core Blog: Microsoft UX Round Table">Microsoft UX Round Table</a> series.</div><br /><br /><p>Today we take a look at <a href="http://www.microsoft.com/products/expression/en/expression-studio/default.mspx" title="Microsoft: Expression Studio">Expression Studio</a>,&nbsp; billed as:</p><blockquote>Better Designer Tools for Better End-User Experiences</blockquote><p>The suite includes tools for visual and web designers (Design and Web respectively), a media cataloguing tool (Media), and a cross-discipline Windows application development environment (Blend - mentioned in <a href="http://www.radiantcore.com/blog/archives/14/03/2007/msuxroundtablereport3" title="Design Matters (Maybe?)">yesterday's post</a>). If you haven't heard of it yet, it's only because most of them are still in Beta. Expect the hype machine to kick into action when the full suite is ready for purchase - until then, you can buy <a href="http://www.microsoft.com/products/expression/en/expression-media/default.mspx" title="Microsoft: Expression Media">Expression Media</a>, buy or try <a href="http://www.microsoft.com/products/expression/en/expression-web/default.mspx" title="Microsoft: Expression Web">Expression Web</a>, play with the RC1 (Release Candidate 1) release of <a href="http://www.microsoft.com/products/expression/en/expression-blend/default.mspx" title="Microsoft: Expression Blend">Expression Blend</a>, or play with the Beta1 release of <a href="http://www.microsoft.com/products/expression/en/expression-design/default.mspx" title="Microsoft: Expression Design">Expression Design</a>.</p><br /><br /><h2>Express Yourself</h2><p>Expression Suite is really interesting in some regards and business as usual in others. The tools share some common DNA with <a href="http://msdn2.microsoft.com/en-us/vstudio/default.aspx" title="Microsoft: Visual Studio">Visual Studio</a> in that they're all part of the .NET 3.0 framework (forgive the occasionally incorrect terminology as we're not a Microsoft development shop - it may be more correct to say that they are built on the .NET 3.0 framework). With the exception of Media, they all communicate using a new XML-based markup language invented by Microsoft, called <a href="http://en.wikipedia.org/wiki/XAML" title="Wikipedia: XAML">eXtensible Application Markup Language (XAML)</a> (prounced zammel). The team behind Expression comes from a varied background of well-known players, including <a href="http://en.wikipedia.org/wiki/Silicon_Beach_Software" title="Wikipedia: Silicon Beach">Silicon Beach</a> (among many other things, makers of the awesome <a href="http://en.wikipedia.org/wiki/Dark_Castle" title="Wikipedia: Dark Castle">Dark Castle</a> series of games), Avid, Adobe, Aldus, and Macromedia.</p><br /><br /><p>Our Expression day started off with a great intro by Angela Baxley, Product Manager (Expression), who stepped in for Erich Zocher, General Manager Tools (Expression), who couldn't make the morning. Despite her warnings about being new to the material, Angela did a great job presenting an overview of the platform based on one of the better PowerPoint decks we saw. As mentioned back on <a href="http://www.radiantcore.com/blog/archives/13/03/2007/msuxroundtablereport2" title="The New Microsoft (Again)">Day 2</a>, her presentation saw a return of the equation Platform + Tools + Craft = UX, although in this case she was talking about the Platform + Tools piece while Darren was addressing the craft bit. Between Web and Blend (think ASP.NET and .NET Framework respectively) where the actual development work happens, the new platform provides the tools to build everything that a modern dev shop needs to produce.</p><br /><br /><h2>The Value of Open Standards: XHTML vs. XAML</h2><p>Most readers of our blog don't need a lecture on why web standards are important (for more information, see <a href="http://en.wikipedia.org/wiki/Web_standards" title="Wikipedia: Web Standards">Web Standards on Wikipedia</a>), nor do you need to be told that Microsoft has not exactly been known to embrace Open Standards in the past. Given that, you would presumably find yourselves equally as curious as I was to find out what was <em>really</em> meant by:</p><blockquote>Expression Web is a professional design tool to create modern, standards-based sites which deliver superior quality on the Web.</blockquote>Turns out, they mean what they say. Web really does produce clean looking XHTML and includes built-in tools to validate the code. Wayne Smith gave a very thorough demo - which I'll get to in a second - but it set the stage for a day of appreciating a new leaf turned and daydreams of a world in which everyone plays on a level playing field.<p></p><br /><br /><p>Which really makes XAML all that much odder. David and I got in a debate with Arturo about whether XAML was actually an 'open standard', during which he confirmed that it was created at Microsoft and is controlled by them. By my books, that makes XAML a published file format rather than a standard and certainly not an open one by any means. This isn't a particularly new effort, as this handy <a href="http://en.wikipedia.org/wiki/Comparison_of_user_interface_markup_languages" title="Wikipedia: Comparision of User Interface Languages">Comparison of user interface markup languages</a> tells us, and some of the projects go back ten years. We're familiar with a different XML-based approach called <a href="http://en.wikipedia.org/wiki/XUL" title="Wikipedia: XUL">XUL</a> (eXtensible User interface Language - pronounced zool as in the ancient Sumerian deity called Zuul, who you know from Ghostbusters). The cynic in me says that having Web do proper XHTML/CSS is an admission of defeat in the sense that Microsoft has been trying for years to&nbsp; <a href="http://en.wikipedia.org/wiki/Embrace_and_extend" title="Wikipedia: Embrace and Extend">embrace and extend</a> the HTML/CSS standards and maybe they've finally given up. Or maybe they got tired of people bashing the horrible HTML that came out of FrontPage and decided to fix it. Either way, standards support is almost always a good thing so yay! But then why not open up XAML or choose to contribute and work on one of the existing efforts? This is an important issue because anyone who choses to use Expression to build their applcations will be held hostage by the XAML file format and may have to make substantial changes to future versions of their software depending on what Micrsoft chooses to do with the format. Truly Open Standards are controlled by independent third parties who have (or at least appear to have) no particular bias towards any one firm and can therefore (theoretically) make decisions which drive the whole industry forward (e.g.: the <a href="http://www.w3.org/" title="W3">W3</a> 'owns' a number of standards including <a href="http://www.w3.org/html/" title="W3: HTML">HTML</a> and <a href="http://www.w3.org/Style/CSS/" title="W3">CSS</a>). Maybe some of the Microsoft folks want to weigh in on this in the comments.</p><br /><br /><h2>Expression Web</h2><img src="http://www.radiantcore.com/images/blogposts/microsoft/expression-web.jpg" alt="Expression Web" style="margin: 0px 0px 10px 10px; float: right;" height="171" width="250"><p>Web replaces FrontPage and is an effort to bring Microsoft's web design technology up to current levels by building a new application and environment rather than trying to fix the old stuff. It's designed to do HTML and XHTML, CSS formatting and code management, and XML/XLSTs, as well as to integrate closely with ASP.NET libraries for things like <a href="http://en.wikipedia.org/wiki/Ajax_%28programming%29" title="Wikipedia: AJAX">AJAX</a> (via the <a href="http://ajax.asp.net/" title="Microsoft: ASP.NET AJAX">AJAX Extensions</a>). The demo was given by Wayne Smith, Senior Product Manager (Expression), who started with a really quick rundown of why standards are important:</p><ol><li>Speed</li><li>Search Engine Indexing</li><li>Efficiency</li><li>Future Proofing the Web</li><li>It's professional!</li></ol><p>We've spent more time cursing at InternetExplorer's lack of support for standards than most people will ever even spend in front of a browser, so this is a very welcome change in tune from the maker of the most popular browser in the world (though, I suppose, it remains to be seen how much the one hand talks to the other). I agree with all of Wayne's points here - we've been building standard compliant sites since we started the company because they just make more sense. In addition to the standards support, Web has a bunch of other great features:</p><ul><li><strong>CSS Box Model:</strong> In 'design mode', the interface goes to great lengths to expose the box model (see <a href="http://www.brainjar.com/css/positioning/" title="BrainJar: CSS Positioning">BrainJar's CSS Positioning</a>, or a neat-o <a href="http://www.hicksdesign.co.uk/boxmodel/" title="Hicks Design: boxmodel">3D rendering by Jon Hicks</a>). Wayne showed us how Web uses shaded borders to make the padding and margins more obvious, which you can kinda see at about 17:50 of this <a href="http://www.learnexpression.com/Videos/EW-01/Video4/Introduction-to-Microsoft-Expression-Web-04.html" title="LearnExpression: Intro to Expression Web Video 4 - Formatting and Styling">training video</a>. Grab the 'crop marks' on the edge of any element to change the margin, or hold down shift and drag to change the padding.</li><li><strong>Style Application Mode:</strong> Web's Page Editor options allow you to toggle between having styles applied in either Auto Mode or Manual Mode, with Manual giving choices between inline, as classes in the head of this page, or as classes in an included document. You can also configure the Manual setting on different types of elements to behave differently (e.g.: apply h1...h6 styles inline but divs get styled in the included CSS).</li><li><strong>Multiple Doctype Support:</strong> Web supports proper <a href="http://en.wikipedia.org/wiki/Doctype" title="Wikipedia: doctype">doctype</a> declarations for XHTML1.0 Transitional and Strict, which will affect the doctype output at the top of the page as well as the options in the IntelliSense code completion menus. Web also supports a Secondary Schema, consisting of various versions of InternetExplorer, which will be used to check code compatibility when rendering Quirks Mode pages.</li><li><strong>Style Manager:</strong> If you've ever used Word's Styles properly, then you're familiar with the way the Style Manager works. <a href="http://en.wikipedia.org/wiki/Wysiwyg" title="Wikipedia: WYSIWYG">WYSIWYG</a> previews of styles make it easy to pick the right text formatting and apply with a simple click.</li></ul><p>Overall, I was really impressed with the product. If they ever released a version for Mac OS there's a good chance we might start using it internally (although it looked good, it didn't look good enough to run Parallels and Vista just to use it). If you're a Windows-based web shop, especially one that does ASP.NET work, you should take a look.</p><h2 style="clear: right;">Expression Design</h2><img src="http://www.radiantcore.com/images/blogposts/microsoft/expression-design.jpg" alt="Expression design" style="margin: 0px 10px 10px 0px; float: left;" height="171" width="250"><p>Arturo Toledo took over to show us Expression Design, a vector-based graphic design tool. I actually have no notes from his demo other than <a href="http://www.adobe.com/products/illustrator/" title="Adobe: Illustrator">"Adobe Illustrator"</a>, which will tell you pretty much all you need to know. Challenging Adobe in this space is like trying to take them on in the Photoshop arena, which is ill-advised unless you're even bigger than they are and have mountains of cash. Which Microsoft happens to be and have. They may, in fact, be the only company out there who could reasonably stand a chance of taking any substantial market share away from the 800-pound gorrila. Right now I think you'll have a tough time ahead of you if you need to get your designers to try and switch over, unless the tools, keyboard shortcuts, and menu items mimick Illustrator pretty closely and your designers don't have to give up years of training and muscle memory. The biggest (only?) reason you would do this is to take advantage of the fact that Design can output XAML files to pull straight into Blend. That said, <a href="http://blogs.msdn.com/mswanson/" title="Mike Swanson's blog">Mike Swanson</a> (a Technical Evangelist with Microsoft) has released an <a href="http://www.mikeswanson.com/xamlexport/" title="Mike Swanson: Adobe Illustrator to XAML Format">Adobe Illustrator to XAML Export</a> plugin with reasonably good support for the Illustrator feature set and better support coming soon (some of the unsupported features aren't available in Design or XAML), so yeah. Draw your own conclusions (get it? draw? ha!).</p><br /><br /><h2 style="clear: left;">Expression Blend</h2><img src="http://www.radiantcore.com/images/blogposts/microsoft/expression-blend.jpg" alt="Expression Blend" style="margin: 0px 0px 10px 10px; float: right;" height="171" width="250"><p>In the same way that you can think of Web replacing FrontPage, Blend basically replaces VisualBasic. The primary intent for the Blend is to build Windows applications on the <a href="http://en.wikipedia.org/wiki/Windows_Presentation_Foundation" title="Wikipedia: Windows Presentation Foundation">Windows Presentation Foundation (WPF)</a>. Arturo showed us a few demos of the kinds of things which Blend is intended for (the now defunct <a href="http://channel9.msdn.com/showpost.aspx?postid=156065" title="Microsoft: Max">Microsoft Max</a> project and the <a href="http://channel9.msdn.com/Showpost.aspx?postid=109413" title="Microsoft: Avalon Patient Monitor">Avalon Patient Monitor</a> specifically), which made for really cool looking interfaces with debatable practical value (like the now famous <a href="http://youtube.com/watch?v=ysEVYwa-vHM" title="YouTube: Jeff Han's Perceptive Pixel promo video">Jeff Han video</a>). I'm always slightly suspicious of totally avant garde interfaces for medical applications which include snazzy animations and effects - when life-threatening decisions need to be made, I sure hope my doctor has to wade through flipping menus and rotating panels! - but it works very well as a proof of concept to show off how flexible Blend's toolset is. I was also slightly put off by Arturo's repeated statements that Blend finally lets you escape the tyranny of the boring gray button (and the <a href="http://msdn2.microsoft.com/en-us/library/aa511258.aspx" title="Microsoft: Windows Vista User Experience Guidelines">Microsoft UX Guidelines</a>) and map full motion video to your spinning control surfaces, which brought to mind thousands of horrendous Flashtastrophes (and one of my favourite <a href="http://www.penny-arcade.com/comic/1999/03/03" title="Penny Arcade: Macromedia FlashDance">Penny Arcade</a> cartoons ever). At any rate, if we built Windows apps (or if <a href="http://en.wikipedia.org/wiki/Windows_Presentation_Foundation#WPF.2FE" title="Wikipedia: Windows Presentation Foundation Everywhere">WPF/E</a> does become a potential competitor to Flash and gets widespread adoption as a browser plugin), it looks like a great environment for building interfaces. I think we, as a group, were a little confused about who it's being aimed at (see <a href="http://www.radiantcore.com/blog/archives/14/03/2007/msuxroundtablereport3" title="Design Matters (Maybe?)">yesterday's post</a> if you haven't already), but once we had sorted out their definition of 'designer', it all made sense. I was particularly impressed when Arturo pulled in an application that only its developer could love, built in Visual Studio, and then reskinned it without affecting the functionality (I grabbed two photos of the finished <a href="http://flickr.com/photos/chesh2000/399512380/in/set-72157594546050781/" title="Flickr: Expression Demo Login Screen">login</a> and <a href="http://flickr.com/photos/chesh2000/399513411/in/set-72157594546050781/" title="Flickr: Expression Demo Welcome Screen">welcome</a> screens). Going on personal experience, I have a suspicion that a lot of shops will end up using Blend by having their Dev team build off a spec and then having their UX/Visual team polish things, so it's great to see that the app works that way too.</p><h2 style="clear: right;">Expression Media</h2><img src="http://www.radiantcore.com/images/blogposts/microsoft/expression-media.jpg" alt="Expression Media" style="margin: 0px 10px 10px 0px; float: left;" height="171" width="250"><p>Media is actually iView Media Pro, formerly made by <a href="http://www.iview-multimedia.com/" title="iView Multimedia">iView Multimedia</a> out of London, and acquired by Microsoft on June 27th, 2006, and is the only product in the Expression Suite which is available for Mac OS X. Media is a Digital Asset Management (DAM) Tool (which is fun to say - Dam Tool!), which basically sucks in all of your media in a whole littany of formats and then provides tagging and sorting capabilities. There's an important distinction in the DAM world between <em>browsers</em> (which just read the info available in the media files themselves - like <a href="http://en.wikipedia.org/wiki/Exif" title="Wikipedia: EXIF">EXIF</a> data in <a href="http://en.wikipedia.org/wiki/Jpg" title="Wikipedia: JPEG">JPEGs</a>) and <em>catalogues</em> (which store their own meta data about the files and can therefore provide much easier and more efficient sorting). If you've used anything like Apple's <a href="http://www.apple.com/ilife/iphoto/" title="Apple: iPhoto">iPhoto</a> or <a href="http://www.apple.com/aperture/" title="Apple: Aperture">Aperture</a>, Adobe's <a href="http://www.adobe.com/products/photoshoplightroom/" title="Adobe: Lightroom">Lightroom</a>, or even Google's <a href="http://picasa.google.com/" title="Google: Picasa">Picasa</a>, you're familiar with the basics. Media goes further in that you can build up all kinds of ways of looking at photos, including adding custom fields (e.g.: a pro photographer might add price to track how much to charge for her images), and build collections for quick access (e.g.: all potentially good backgrounds in one area). It looked like an excellent media catalogue and something that we might make use of to store assets from different clients for easy retrieval by all of our Professional Services team members. There was some discussion about how much support was included for sharing the library files (could they be checked into a version control system? read of a network mount?) which I think was left open, so if any of the Microsoft folk know the answer, please feel free to leave a comment.</p><h2 style="clear: left;">Final Expressions</h2><p>I really had to work at putting myself in the mindset of a potential purchaser/user of the software since our Mac bias basically rules us out. Someone did ask Erich Zocher if there were plans to do Mac versions and there clearly aren't, which I think is a real shame. We spend a lot of time in the trenches of this industry and we're seeing more and more glowing Apples while we're down there - particularly amongst the <a href="http://en.wikipedia.org/wiki/Digerati" title="Wikipedia: digerati">digerati</a> whose influence reaches far and wide</p>. Although we know some web shops who work on Windows, the vast majority are Mac-based or are in the process of switching over, so they are increasingly unlikely to use products like Design and Web. That said, if we were a Windows-based shop and we built sites and applications on ASP.NET and the .NET Framework (which sounds like a weird techno band), we would almost certainly use Expression. I return to something I said way back on Monday - in the end, they're all just tools - and if you buy into the Microsoft way, these looked like great tools.<p></p><br /><br /><p>That's it for Day 4 - tune in tomorrow for the <strong>big wrap up</strong>!</p>]]></description>
				<category>Trip Reports, User Experience, Taking Care of Business</category>
				<pubDate>Thu, 15 Mar 2007 09:00:00 GMT</pubDate>
			</item>
		
	</channel>
</rss>