>Gentlemen!
>
>Let's use this thread to see where developers are most interested in having a "TI" layer...Paul has already mentioned a few places...I'd like to have a broader picture of what developers are interested in before I implement anything (sounds suspiciously like a use case < s >).
>
>Regards,

Like I mentioned, I really need a layer where I can add properties and methods and be sure they'll show up in all my subclasses and in all the composite classes. Armin mentioned that this would only solve 20% of the problem, but for me, that 20% is the most important. The resizer class I sent you is the best example of why (and what) I'd like to be able to do.

In addition to the classes already mentioned, the CMenus class might be another candidate for additional layer(s). I think the UI classes are the most important because you can build composite classes out of them (then you can only add properties and methods to the container). In some places, you can't even easily add them to the container because the container is used inside of framework forms. Your only choice is to move methods up to the form level, where they don't always belong, or to create your own versions of each of the framework form classes. That still doesn't solve the problem of being able to easily make changes to existing applications where this wasn't done. Ideally, at each level of containership, you'd be able to augment the class via an intermediate layer.

Hopefully that helps...