Featured Posts

WPF and the Event Routing Paradigm, with Bacon Since the first event-driven language came down from the mountain and became part of the software development vernacular, there has been a certain notion of how an event works. Subscribe...

Read more

How to stop Expression Blend 4 RC from crashing on... So you’ve downloaded Expression Blend 4 RC but when you start it up, Blend crashes hard.  It’s never done that before, right? What do you do?  Well, you can...

Read more

The WPF Must-Grok List Robert A. Heinlein defined the word grok as: Grok means to understand so thoroughly that the observer becomes a part of the observed—to merge, blend, intermarry, lose identity...

Read more

Yes, Virginia, TextBlock.Text Will Support MultiBinding One of the features introduced to WPF in version 3.5 SP1 is the StringFormat property. If you’re unaware, StringFormat allows you to bring the String.Format capability...

Read more

Why Are WPF Developers Trying to Kill Menus? Somewhere along the line, and I’m not motivated enough to research it, menus apparently became bad.  I don’t mean they ever stopped working or became unsuitable for the...

Read more

using System.Windows; Rss

Absent from my Grok List

Posted on : 02-11-2010 | By : Christopher Estep | In : Basics

2

It’s been suggested that my WPF Must-Grok List is “basically the whole WPF” so in my own defense, I thought I’d list a few items to illustrate how WPF is far deeper than my list:

  1. Attached Properties
  2. Visual & Logical Trees
  3. MVVM
  4. Prism
  5. Click-once deployment
  6. Browser apps
  7. Animation
  8. Graphics (2D)
  9. 3D Graphics
  10. Flow Documents & Text
  11. Ink
  12. Printing & XPS
  13. Media
  14. Adorners
  15. Custom controls
  16. Interop

And even this is not a complete list.

Remember, WPF is a new paradigm in software UI development. It does have a significant learning curve and it is a huge mistake to oversimplify it.

Popularity: 26%

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • DotNetKicks
  • StumbleUpon
  • LinkedIn
  • Facebook
  • TwitThis
  • Digg
  • DZone
  • Reddit
  • Technorati
  • email
  • Print

Comments (2)

i must admit, my twitter post was a bit harsh and communicated the wrong thing.

here’s the background: around 30 or so minutes before you made your post, i was scouring the web for nice noob introductions to WPF i can use to train developers.

then your post came up and i replied (with that frame of mind).

> It does have a significant learning curve
> and it is a huge mistake to oversimplify it.

And this is the same thing I arrived at this morning. I’ve given up on finding a nice-and-slow learning path for WPF.

[...] And a follow-up post [...]