Windows Presentation Foundation By Jayesh Chudsama


Windows Presentation Foundation : Engine and Programming Framework
September 30, 2006, 8:47 pm
Filed under: Blogroll, Books & writing

Windows Presentation Foundation is Microsoft’s unified presentation subsystem for Windows.

Simple definition for Windows Presentation Foundation would be WPF = Engine + Programming Framework

WPF engine is built on top of Microsoft DirectX(r). Now unlash the power of the modern computer’s graphics hardware and take advantage of advances using WPF framework to delivers solutions for media, UI design, and documents. Now it’s no tougher job for developers to create rich and eye catching applications using WPF.

WPF engine aims to put together the way developers and designers experience documents, media, and UI, providing a single runtime for browser-based experiences, forms-based applications, graphics, video, audio and documents.

For example, Windows Presentation Foundation’s vector-based rendering engine enables applications to scale to take advantage of high-dpi monitors without requiring extra work on the part of the developer or user.

The Windows Presentation Foundation Framework is designed for extensibility enabling developers to create their own controls on top of the Windows Presentation Foundation engine from scratch or by sub classing existing Windows Presentation Foundation controls. Windows Presentation Foundation framework brings controls for shapes, documents, images, video, animation, 3-D and “panels” in which to place controls and content.

XAML (short for Extensible Application Markup Language, and pronounced “Zammel”) is the user interface markup language for the Windows Presentation Foundation, which is one of the “pillars” of the .NET Framework 3.0 API.

XAML is a declarative XML-based language optimized for describing graphically rich visual user interfaces. When a developer creates an application in Windows Presentation Foundation, almost code is written and implemented in XAML.

XAML is faster, easier to implement, and easier to localize, making it a better choice than the equivalent procedural code. Further while using XAML there is no performance punishment as it is an XML-based representation of the object model.

Each XAML tag corresponds to an object model class. A tag also usually has a collection of attributes that corresponds to the properties of the tag’s associated class. At compile time, the parser converts the XAML into a partial class that contains equivalent procedural code. Each XAML tag becomes an instance of the corresponding object model class, and the tag’s attribute values are assigned to the corresponding object properties. Then the partial class that is created from the parsed XAML is combined with the page’s code-behind file by the common language runtime compiler to create an object for the page.

Advertisements

Leave a Comment so far
Leave a comment



Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s



%d bloggers like this: