I am sure being the slow person I am, I am stating the obvious here, but I can see where Microsoft seems to be heading with XAML. This looks to be a avenue for the serialization of all interfaces to XML code. This is similar to the way NeXT did there interfaces. You would build your interface in a program called “Interface Builder” which would create “.nib” files (Which stands for NeXT Interface Builder, FYI) It would then serialize or “archive” the interface objects to the “.nib” file or un-archive them when receving an awake message. I believe that is how it works. I am going to get flammed by some Mac OS Cocoa programmers anytime now. I have read about all this stuff but never actually programmed any Cocoa Framework apps my self. Sorry if I totally mutalated the explanation.
XAML looks very interesting to me. This would allow your VS.NET environment to serialize all your forms to XAML. When it loads the XAML interface code it then hooks or binds all the interace code to the “code behind” code.
It will be interesting to see where it all goes.
What are some of your initial thoughts on XAML?