“Acropolis” uses Xaml to define business logic components
An excerpt listing the benefits of XAML for Acropolis:
- Using XAML gives you a very concise way to express the structural aspects of your component – not just the external ‘class interface’, but how it is structured internally. For example, it allows you to cleanly define how any child components or services that your component uses are configured or interact with each other.
- It allows you to concentrate more on the code that defines the actual implementation of your component. In other words, we want to make it so that 99%+ of the code that you do write is the actual code that will solve your business problem and not plumbing or glue code.
- It is much easier for us (or you) to build visual designers or other tools (including test tools) for your component since its structure is more easily ‘machine-parsable’. It also allows for a looser coupling between the application model and the tools allowing each of them to evolve more quickly.
The 3rd point is an interesting observation. I don’t think I have heard that benefit before…
To see some sample Xaml that Acropolis tools create, one place to look is the Walkthrough: Building an Acropolis RSS Reader Application.