A Day In The Life Of A WPF/SL Integrator

9,817 views

Published on

This session proposes an insight in the life of an integrator (sometimes called User Experience Developer or “Devigner”). How do we translate a creative designer’s vision into code, transforming it into interactive applications? What tools do we use, what tricks did we learn? This session will show you how to start from scratch and coordinate designers and developers to create a new rich application in Silverlight or Windows Presentation Foundation. We will see how to architect and structure the application according to the best practices in the field, and what workflows are involved. We will also see how to create and integrate XAML assets into the user interface. You will leave with a much better understanding on how the new integrator role is changing the way that client applications are developed.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
9,817
On SlideShare
0
From Embeds
0
Number of Embeds
18
Actions
Shares
0
Downloads
35
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Import from PhotoshopExport from IllustratorKaXamlShazzamSnoop (execute on Blend)SilverlightSpyRoolerCalipers
  • Show import of “bubble” SeesmicImporting shape, combineOverlay is hard,  Change gradient brush, explain reduction of visual treeShow button, create styleMeasure, zoom in, compose template
  • Show import of “bubble” SeesmicImporting shape, combineOverlay is hard,  Change gradient brush, explain reduction of visual treeShow button, create styleMeasure, zoom in, compose template
  • A Day In The Life Of A WPF/SL Integrator

    1. 1. A day in the life of an Integrator Laurent Bugnion Senior User Experience Integrator IdentityMine http://[blog|www].galasoft.ch
    2. 2. Why do we need a new role?
    3. 3. The Integrator role 1. Communicator and Translator 2. Coach and Trainer 3. Bottle neck? 4. Domain expertise: a. User experience (Production designer) b. Expression Blend c. Understanding designers tools d. WPF/Silverlight infrastructure
    4. 4. The Integrator role
    5. 5. Blendability • “The ability to be edited in Blend” • (and Visual Studio designer…) • Differentiate code in design and runtime • Create design time data
    6. 6. Blendability
    7. 7. In case of “No Blendability” • It kind of sucks… • More XAML edition (manual) • More runtime testing • Edit, Run, Measure, Edit… • Isolate the issue • New application in Blend
    8. 8. Working with tools
    9. 9. Working with tools • Importing XAML • Import from Photoshop, Illustrator (Blend) • Export from Fireworks • http://www.granthinkson.com/tools/fireworks/ • Export from Design • http://www.microsoft.com/expression/products/Desig n_Overview.aspx
    10. 10. Working with tools • Previewing • Kaxaml • http://kaxaml.com/ • Shazzam • http://shazzam-tool.com/
    11. 11. Working with tools • Inspecting • Snoop (WPF) • http://snoopwpf.codeplex.com/ • Silverlight Spy • http://firstfloorsoftware.com/silverlightspy/
    12. 12. Working with tools • Measuring • Rooler • http://blois.us/Rooler/ • Calipers • Various
    13. 13. Working with tools • Cleaning up • Pistachio • http://www.granthinkson.com/2007/11/08/announcin g-pistachio-wpf-resource-visualizer/
    14. 14. Pistachio
    15. 15. Pistachio
    16. 16. Importing assets
    17. 17. Nathan Dunlap http://www.designerslove.net/ Robby Ingebretsen http://nerdplusart.com/ Me (@LBugnion) http://blog.galasoft.ch

    ×