Hi,

thanks for your reply!

>>Wouldn't an intermediate layer in the framework be usefull here? Or any other predefined places where I can put my code (e.g. Hook-Objects)?
>We discussed that a few weeks ago and my first enthusiasm of this idea disapeared. For me this only solves half of the problem. If you only do one project this would really be the way for you. If you would do two projects or more you will find out that it would be helpful to have a base i-layer (for all stuff ok for all projects) and a project specific i-layer under that one. Next one will come in and say, oh i need 3 i-layers....

1) C-Layer (generic changes here in the MM classes)

2) I-Layer for all FW classes (can be changed for different projects by keeping the classes in different project specific I-Layer directories).

How about that? This wouldn't be the solution for every problem you mentioned, but this way we would have 2 layers. One common for all projects and one for each specific project.

We still would have to make changes in the FW classes directly (see my reply to Chris). And what would still be missing: If we have several applications in one project and would like to have different behaviour in them. But here I think, we could put those things into the project specific I-Layer (making the behaviour configurable), since application specific control behaviour in the same project won't be needed very often.

So an I-Layer won't be that bad, wouldn't it? But nevertheless, this is not a very elegant solution.

Armin