i'm headed out on holiday for about a week. i haven't taken one in a long while and this will be good for me (hopefully). i'm also headed to europe where i've never been, so i'm pretty excited. i'm leaving the cell phone behind, so no twitter, etc. i am equipped with a windows mobile gps-enabled handset and skype. i'm looking forward to that experience and being able to use my custom application that i wrote to plot my points so my family can track us on virtual earth.
anyhow, likely no posts for a week (not that you care). when i get back i'll tell you all about the plans for The Code Trip, but in the meantime, feel free to peek.
yo, check it. expression design has released a service pack.
what!? i know how can that be? a service pack < 8 months after its release? i say awesome. i've been wanting microsoft teams to continue to become more and more agile especially with regards to very helpful features or great improvements of existing features based on user feedback.
one such point of feedback that is implemented in expression design is that of xaml generation of the layers and/or complete surface. you didn't know design can generate xaml? shame on you. i did a podcast (you should really subscribe to the podcast feed on the left of my blog or just use this link) talking about using vector images (svg) and importing into expression design and getting xaml that you could use in your applications.
there are essentially two ways of doing this in expression design:
- if you only want pieces of your design file to be xaml (i.e., you want to xaml-ize a fragment of the design), you can select the layer(s) in your design file and go to the edit menu and choose 'Copy as XAML' and bam, you now have xaml for those selected fragments in your clipboard. go forth and develop.
- if you want the entire design surface to be a xaml representation, you would use the file menu and choose export. from there you'll be presented with what looks like a typical 'save as' dialog box. change the file type to xaml and after choosing location/name click ok. you'll now be presented with a much improved options window (in service pack 1):
in previous versions the options weren't exactly clear. for instance the xaml type you wanted (either WPF or silverlight) was in a different tab). i really like this improved export user interface. i especially like the option of converting text to paths. this really helps when you don't want to (or can't) redistribute any type faces. upon export, you will get all the xaml plus (if you chose that option) path data for your text areas. very cool.
so if you have design files or vector files that you would want to use in silverlight, this is the perfect tool and function to create the xaml representation of that data. so go get service pack 1 for expression design and you'll be happy.