>>The very problem with classes being not shared or even sharing it as readonly is that not every member of the development team could use it in setting default forms or in mapping fields. That said, it breaks the essence of OOP methodology.
>
>Jess,
>
>This is not realy true. A programmer should not need to see the source code for a class to be able to use that class. The documentation for the class should describe how to use it and what it does.

I agree with you here. However, sharing it does not necessarily mean it is a must for the programmer to see and do something on it. But how are they going use it if the class is readonly.

>Hiding source code is not against anything about OOP

Yes, bu how can you hide it totally? It is hidden when using them as subclass but opening the based class, source codes are still exposed.

Sharing the classes as "readonly" gives an error. In order for it to be usable, it must be shared as "arhive." Now, if it is archive, any programmer can access the classes, therefore, they can do anything what they can no matter how documented it is. We can not say to them "avoid opening the classes".