Crackers or nuts?

As I mentioned earlier, I have just purchased Adam Nathan's Windows Presentation Foundation book (upon several recommendations) and I'm eager to do a deep dive on a new technology.

.Net is increasingly becoming the development framework of choice and keeping up with the latest technologies is hard when they are coming so fast and furious. I've decided to pick one, become knowledgeable in it to ensure that I keep my brain ticking over, even if I'm filling "post-technical" roles in my day job.

Things that I want to get out of the book:

* What is WPF?
* Where does it fit into the .Net framework?
* Is it really "Flash for .Net"?
* Is XAML too complicated to use as a GUI creation mechanism?
* Is XAML the next generation of XUL?
* How hard is it to put code behind the XAML building blocks?
* How does WPF work for desktop applications versus browser applications?
* Can I convert existing apps to the WPF framework?
* Why would I recommend WPF over anything else to a client?
* Does WPF help make a compelling argument for choosing .Net as a framework?

Submerging......