Hi Jim,

Thank you for your anwer. We made our mind. We just copy the framework to the directory of the new application and the go on with it. We think that it is to dangerous to keep the classes at a central place.

Greetings,

Afier Appelman

>Hi Afier,
>
>>Now we would like to know if it is better to copy all the framework-classes to the new application or that we will use the classes from the framework directory<
>
>It looks like my opinion is going to be different from everyone else's. <g>
>
>I believe in more strict adherence to OOD/OOP principles. If you design your framework right, then you can have a base set of classes from which ALL app classes are subclassed. The first thing you would do for each new app, is to create a set of sub-classes from all your base framework classes. This way, if you have make any bug fixes/enhancements to your framework, you only have to make the change in one place. Of course, all changes to the base framework are carefully reviewed and exhaustively tested before releasing to your production framework.
>
>IMO, making copies of classes breaks the OOP methodology.
>
>Another way to look at it is from the old procedural POV. Most developer's I know maintained a library of common procedures/functions that were generic enough to be used in most any app. I can't imagine maintaining a separate copy of my procedure lib for each app. This would be a maintenance nightmare.
>
>Best Regards,
>jmu