Hi Steve,
We don't pretend that we'll ever achieve designer coverage for the full fidelity and expressiveness of XAML, nor do we believe it's interesting to do so. We do, however, want to make sure that useful capabilities and constructs of WPF are exposed in the designer.
One of Cider's goals is to elminate the need to understand, edit, and troubleshoot XAML for certain scenarios. So for example, we'll have some basic things covered in the first release, e.g. control creation, layout, properties, styles and templates, etc.
We will expand the scenarios that are supported, and the additional breadth will come in two ways. First, Cider will cooperate with other tools, like the Expression Interactive Designer (Sparkle), to fill out additional scenarios and areas of specialization that are outside of what typical developers typically do.
Second, time will help -- future releases of the Cider designer and the VS toolset will address additional kinds of capabilities and scenarios. This part prolly goes without saying :-)
So again, we ultimately want to deliver a XAML-free experience for the things people really need to do with WPF. That said, we're going to be pragmatic about our delivery, and will strive to be tolerant of XAML that has been manually edited or pasted in from other sources.
Hope this helps... chad
chad royal | project cider | microsoft | as is, no warranties, no rights |