Hi Roxanne,

Website for Ken Levy's SuperClass Tool ?

Thanks.
Michel.

=================== Original message follows ===================

>>It is true that inheritance is probably the single most overused feature (snip)
> However, they, like many VFP developers, tend to be the "one man show." Thus, from my perspective of team development, I still believe that I have a valid point. It's easier to bring in new team members, both experienced and new to VFP, without providing much instruction on the inner workings of the class libraries in use...
>
>Jack,
>I'm in a team environment, and happily left the one-man-show era behind recently. In this current environment, I've had plenty of opportunity to experience the pitfalls of being new kid on the block and not knowing my class heirarchy intimately (in an in-house framework that was very complicated to boot). So I respect your original point, but I dont think it's as big of deal and here's why...
>
>Get your new employees using Ken Levy's superclass tool, it lets you see exactly what your inheriting and is an easy no-brainer habit to get into.
>
>If you utilize alot of class libraries developed in house, then you either got take the time to train new hires OR take the time to compile good documentation. IMHO, getting familiar with class heirarchy is a thing best not done left to newbies to tackle alone. To get the results you desire, it's going to take some kind of time investment and your not going to be able cut corners on that as long as your using OO development tools. When you do cut corners on that initial time investment, you end up exactly where you were when you started this thread.
>
>And even better, go with a commercial framework that comes well documented instead of only using specialized in-house libraries. That way you don't waste time doing the necessary documentation, you get babysitting tutorials and examples, and you can just dump the manual on the new hire and they got a much better chance at the sink or swim game with minimal time investment.