Hi Dragan,

>>>Do you agree a bunch of unrelated functions or classes collected into a single PRG or VCX is nothing more than coincedental cohesion?
>>
>>It depends on the definition of unrelated. For example you've got a number of functional cohesive libraries, and you're left over with a number of unrelated functions or classes that are specific to the application and put them in one file, you might speak about logical cohesion in stead.

>Agree - the definition of "related" is in the eye of the user. I remember working with VFE, which is another CodeBase framework, where yes, the controls are in iControls.vcx, forms are in iForms.vcx etc, but then I had hard time when I needed to subclass the login form, because it was before the CodeReferences tool and I had no idea where to look for it.

>It was, if I remember correctly, somewhere in security vcx, or in some utility vcx. The last place I was looking for it.

>Now to someone else, who has the mindset closer to that of the framework's authors', that may be a really logical place to put it, as that's related. To me, it's unrelated, or else I would have found it faster.

>IOW, this is more an issue of readability (i.e. would the name of the classlib tell me which classes are inside) than of any logic in the packaging.

As I mentioned to Mike before, if you are looking for a certain class of which you know it is there, but forgot the exact name (CryoSearch vs SearchInCryo vs dlg_cryosearch vs frm_cryosearch, vs tlb_cryosearch etc), but its used to login a user into the application the name of the classlib should give you a pretty good hunch where to look in. In the case of having just unreleated classlib, you'll be too searching your butt of to find it.

However, I totally agree that you should put classes in a logical place in order to find it quickly.

Walter,