>Now I got myself so confused that I can't figure out why I need to subclass the framework!

Isn't this fun?

You might want to subclass if you need to add functionality of your own or override certain framework behavior.

For example, you might want all the textboxes in all your apps to use timesroman instead of arial.

In this case you would subclass the framework's textbox classes and create your own.

That's the traditional reason for subclassing the framework.

If you're subclassing objects that are already part of a complex hierarchy (forms, for instance), you will need to do some thinking before going ahead with the change.

Another option is to modify the framework classes, but you MUST document these changes in a separate document or you will loose them with the next version of the framework.

Alex