Hi Mike

Mike yearwood wrote:
> I've been advocating exactly the opposite of this guy for years. One
> class in one vcx, unless the main class has subclasses built into it.
> Then those subclasses should be in with the main class' vcx. The scx
> is done that way. One main scx with contained components. No scx file
> contains several screens.
>   
I'm not sure I understand - you mean one SCX can contain more than one 
screen ?  Would that be a formset ?
> I don't know why it's so often the case that more than one physical
> file is in one physical container at design time ...
You've lost me, I'm afrid
> when at runtime "The
> goal is to create routines with internal integrity (strong cohesion)
> and small, direct, visible, and flexible relations to other routines
> (loose coupling)." -- Steve McConnell
>
> Also if this guy is a good boss you should be able to explain things
> to him, especially with the input from this thread. However it's
> unfortunately been my experience that the Peter principle applies to
> programmers - good programmers get promoted to being lousy bosses.
>   
I'm not about to be critical of my boss - he has (at least, 
historically) good reasons for doing things the way he has - and to 
break out the classes from the one VCX would be a massive amount of work 
and would have lots of ramifications throughout the system because of 
the way it is all tied in with product licensing issues ...  but I want 
to be aware of the issues and to at least voice my concerns

Paul Newton


_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED]
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to