>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. Hiding source code is not against anything about OOP, as a matter of fact, a strong argument could be made to say that if you need to read the source code for a class it is poorly designed because it is not a black box object.