Windows Presentation Foundation introduces a new set of document and print technologies. Applications that need to persist data to a local store can use the Open Packaging Conventions, a ZIP-based packaging convention shared with Office 2007 that supports core properties and custom metadata, digital signatures and rights management functionality. For applications that want to share documents for collaboration across multiple machines, even without the application installed, the XML Paper Specification allows visuals to be fixed in a printable, portable format
So just to reiterate from the previous post
• Built-in support for UI, media (2D, 3D, audio, video, animation, sound, etc.), text (fonts), document services (XPS), and interactive data visualization
• Hardware acceleration that consumes GPU cycles, and leaves CPU cycles for other tasks
• Vector graphics and resolution independent graphics engine lets you scale the UI to different form factors with varying DPIs (desktop, laptop, tablet PC, big screen TV. Note: Doesn’t apply to devices)
• Leverage a subset of WPF user experience to X-platform, X-browser and devices using WPF/E
Windows Presentation Foundation introduces XAML (eXtensible Application Markup Language), an XML-based language for instantiating and populating nested object hierarchies. While XAML isn't exclusively tied to Windows Presentation Foundation, it is inherently suitable for tasks such as UI definition and construction.
The design of XAML allows applications to parse and manipulate UI logic at run-time for dynamic workflow scenarios. Importantly, the XAML / code-behind model embodied in Windows Presentation Foundation allows designers and developers to work collaboratively on client application design and development
You don’t have to learn about the entire platform at once to get started. Contrast to Dx, where you need to know everything about lighting, surfaces, shaders, etc. WPF let’s you start with simple parts of the framework for simple layouts, then you can incrementally learn more as you want to get fancier.
• It provides an XML-based way to specify declaratively a hierarchy of objects with properties and logic.
• XAML is a user interface design language, because it is ideal for generating the kind of code that traditionally resided in a hidden #region area and was hard to maintain by both developers and tools. It can be rendered in client WPF applications or in a browser-based application for browsers that support it.
• If you've ever wanted to edit the auto-generated blocks of code created by Visual Studio but been dissuaded by the warning comments, or you've gone ahead regardless and been burnt badly when your tools refused to load your changes, you'll appreciate XAML.
• With XAML, gone are the days of boring gray buttons and poorly designed applications: with the declarative programming model enabled by XAML, you can split off presentation UI and client-side logic in the same way as with a Web application.