blogs.conchango.com

welcome to the conchango blogging site
Welcome to blogs.conchango.com Sign in | Join | Help
in Search

Hiljamaria Immonen's Blog

  • Designer/developer workflow in WPF and Silverlight

    Here are couple of thoughts on what's great about the new Microsoft technologies: WPF and Silverlight. It's making it easier for both designers and developers to create good quality work, and to produce it faster!

    Current scenario vs WPF approach

    Typical current scenario:
    Designer creates a design in Photoshop, passes it over to a developer, who in turn translates it into code.

    WPF approach:
    Designer creates the layout, controls, interactions and animation in Expression Blend. Developer can open the same project in Blend and add the back end code. At no time the developer needs to touch the actual presentation layer, designer remains 100% in control. This also saves time, as developer doesn’t need to recreate any elements.

    “Developers no longer have to try to recreate them; play the hero and rid the world of "developer art." “ as Microsoft puts it on the Expression Blend website.

    As there are no built in source safe features in Expression Blend currently, something like Visual SourceSafe is pretty handy to use.

     

    What's my role, and what's yours? Shall I just pass it over to you when I've finished?

    No you shouldn't! A designer and a developer should work together throughout the whole project as much as possible. There is plenty of going back and forth and it’s beneficial for both the designer and developer to have the support from each other. Obviously if there is a huge amount of back end development with really simple interface, this will not apply.

    It is hugely important to get the whole project working in Expression Blend, this makes the process much more seamless and faster. It saves everyone time, effort and money! If some of the front end parts of the code are not compatible with Blend (this should be avoided as much as possible!!!), it makes it very tricky for the designer to work on that area of the project. In this case coding skills will come in handy, but obviously most designers will not have the experience/willingness to delve deep into this area!

    Great opportunities for everyone

    The ideal workflow and roles will become more clear with more time and experience, trial and error. This technology and brand new designer interface tools provide great opportunities for everyone in the industry. Designers who want to learn/deepen their understanding of XAML coding, this is a fantastic opportunity to do so. People with Flash and Director design/development skills will love WPF, as the requirements are very similar. Animations and interactivity are at the heart of Expression Blend. Similarly developers are able to better understand the presentation layer, as the whole project can be controlled and previewed from the same interface.

    After all, the more members of the team understand about each other’s areas, the easier the process is, and the better the experience for the end user!

  • Expression Blend - Thoughts on WPF design from a web designer’s point of view

     

    I’ve been working with Microsoft Expression Blend “the professional design tool to create engaging web-connected experiences for Windows” since the beginning of this year. It’s a new program (formerly known as Interactive Designer) from the Windows Presentation Platform (WPF). The software is currently in Beta 2 which can be downloaded for free. The completed product is due to be launched later on this year.

     


    Similar Features to Other Programs

    I’m a web designer from a creative background, and I’ve also being using HTML and CSS for front end coding. It’s been very interesting learning Blend. I found many aspects familiar as it has similar elements to other programs I’ve used; Photoshop (similar colour palette), Illustrator (effective vector drawing tools), Flash (animation capabilities) and Dreamweaver (creating layouts, toggling between Design and Code views).


    Blend design view:



    Blend code view:

     



    Creating Layouts and Assets

    There is an Asset Library with plenty of System Controls, such as Button, CheckBox, ComboBox, ListBox, RadioButton, ScrollBar, Slider, TabControl, GridSplitter etc etc. These are prestyled with basic styles, and can be simply drawn onto the canvas – it’s very quick and easy. If there is no budget for any design effort, developers can use the prestyled controls, which don't look too bad. When designers are involved, they are able to change the styling on controls completely. They can change the shapes and colours. Elements can be animated. Buttons can have animated rollover states. The software gives designers endless opportunities to create the exact look and feel they are after.


    Asset Library:



    Layouts can be controlled from the Layout Panel. Items can be Stacked, Wrapped or Docked, placed in a Grid, or a Listbox. The most freedom is provided by the Canvas, where shapes and pictures can be drawn onto.

     

    Layout Panels: 

     



    3D integration

    Expression Blend provides great 3D integration capabilities. Complex 3D objects can be created in external applications, and imported into Blend. The sample object below has been created in ZAM 3D - “A New 3D XAML Tool for Microsoft Windows Vista Application Development. The beta version can be downloaded for free and there are great easy-to-follow video tutorials on the website. I haven’t got much experience working with 3D elements in the past, but this program made it really straightforward.

    3D object imported into Blend from ZAM3D:


    ZAM3D interface:




    Design vs Development – what’s my role

    Blend is a very powerful tool for creating applications. The idea is that designers and developers can use the same program, giving designers total control over the design. There is no duplication of effort, as the developers don’t need to replicate any of the design work. When designers create the designs in Blend, it’s already in the correct format for Developers to add their code to.


    Currently there are a great number of books aimed at WPF developers teaching XAML coding. There are Blend books for designers in production, but they are yet to be published. They will not be out until the summer. The only way for designers to learn the program is from books aimed at developers and online tutorials and forums. This definitely adds an extra challenge to the mix. Good sites to go onto are www.expressionblend.com, www.contentpresenter.com, http://blogs.msdn.com/expression/ and http://msdn2.microsoft.com/en-us/library/ms754130.aspx.


    One of the biggest challenges there are, is to establish where the designer’s role ends, and the developer’s role begins. There is a large area where these two overlap. The role division greatly depends on the designer’s ability to understand and learn XAML code. The more the designer understands the code, the easier it is for them to use it. Expression Blend has great capabilities, but at the same time it is a pretty complex software to use with a steep learning curve in the beginning. If you’re up for a new challenge, this is a great and rewarding one!

Powered by Community Server (Personal Edition), by Telligent Systems