|
|
|
|
|
|
by mschaef
4263 days ago
|
|
|
XAML by itself is actually fairly easy to work with because it doesn't actually do that much: At it's core, XAML boils down to an XML-based mechanism for constructing objects. Squint your eyes just right, and it starts to look like the markup for an IoC container: http://www.codeproject.com/Articles/17188/Inversion-of-Contr... Where things start to get complicated are the objects that you create with XAML... (which is where the WPF framework comes into play.) Five or six years ago, I prototyped a system using XAML/WPF to build an HMI system for an industrial process control applications. The system served up XAML from a server that got loaded by a client to construct UI objects. It then inspected the Binding objects that the XAML created and started subscribing to the appropriate server-side data points. It came together within a couple days and really ran quite well. |
|
|