Hi Paul > Message: 10 > Date: Mon, 17 Dec 2007 13:27:51 +0000 > From: Paul Newton <[EMAIL PROTECTED]> > Subject: > To: [EMAIL PROTECTED] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="us-ascii" > > Eurico > > I'm going to do exactly what the he wants (he's the boss and the boss is > always right, right ?) > > But I am very worried that we are going end up in a mess ...
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 don't know why it's so often the case that more than one physical file is in one physical container at design time 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. Mike _______________________________________________ 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.
