>>The other reason is the so-called "outrage fatigue". So the Prez approved a leak, so what... whatever sort of thread gets started on that, I already know what's which side going to say. Why bother reading, why bother writing.
>
>Excellent! Then you should have more spare time to explore the component gallery with Arto and me. Please see thread ID: 1111445! ;)

I've actually done some work on the CB back in the end of 2003, while I was jobless and interested in writing a few cool builders. I actually wrote a fix for the part of CB which exports code, to include the full hierarchy of the object when churning out its code (and I've sent it to JohnK and it eventually was included in VFP9 CB), because I needed it for the builder which would create a visual class from exported code (which worked in the end, but you had to have the complete Set("Classlib") set for it to work).

The trouble came when I got this job and didn't have the time, nor will, to write any more articles, so this fix and this builder never came to light.

So that's as much as I got into this. But after I've read the thread, I see where you're going with it. Even in my current environment, where there's pretty much always one class - one classlib, I'd often want the code in the PM grouped not by its form (is it a vcx or a prg or what), but by its place within the project. I'd like to arrange these into a hierarchy - module, and a group within a module... A module would be anything that goes into the same popup off the main menu, and a group would correspond to the popup's bar. Because that suits my environment: I could have all the forms in the module I'm currently working on, while collapsing the rest, and for any particular form I could see its vcx, de*.prg, bz*.prg, and rpt*.prg in one place. Framework stuff would be another module. Someone else may just group this in a different manner. And we could (isn't this one of the cool things we were supposed to have in the CG anyway) have the same things appear in multiple places - so I could have the frmbase class with each module if I want, and with the framework as well. That'd be cool - and we'd only need to write a different shell form for the component gallery. As it is now, it's quite confusing, and, sincerely, I've never used it. Tried a few times, and it never worked for me.