- XAML (rhymes with Camel)
- Ummm…there is no 2. XAML is the big thing about WPF.
- Actually, I lied there is a number two and several points after but they all point back to 1.
- Okay that’s wrong too there are other highlights in WPF that aren’t directly tied to XAML but they are a bit more technical than I care to go into now. (Again, I’ll point you to Greg Schechter for more technical discussions.)
XAML or eXtensible Application Markup Language, is basically the representation of UI in XML. XAML brings the power of declarative UI programming to Windows desktop applications. I say desktop applications because ASP.Net apps already have a similar feature called html.
One major feature of ASP.Net development is that logic is CLEARLY separated from presentation. Well it is possible to have scriptlets of logic within an ASP.Net page and to imperatively create HTML elements in a code-behind file; but for the most part ASP.Net supports a model of separation, leaving UI Design to designers and business logic to coders.
WPF gives desktop applications a similar development model with XAML. Of course, a developer is free to create his (or her) WPF application using all imperative code. He would also be free to create his web app using only ISAPI.
This is the big deal regarding WPF. For the first time, designers can create their mockups using a tool that is targeted toward designers (namely Expression Interactive Designer) and have it immediately useful for developers. The reverse is also true. Developers can create a basic UI for their application in Visual Studio and a designer can use the same files to enhance the UI in Expression. Gone are the days of designers creating mockups in a graphics tool and developers having to translate that look into a windows form. XAML creates a bridge between developers and designers that simply did not exist before. If you’re not excited yet, you should check your pulse.