Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Is one concrete Class per Class Lib a poor/good idea?
Message
From
23/06/2004 18:54:08
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
 
 
To
23/06/2004 17:31:59
General information
Forum:
Visual FoxPro
Category:
Classes - VCX
Miscellaneous
Thread ID:
00916585
Message ID:
00916668
Views:
48
>So far on this ‘mailing list/BBS’ and others no one has shown me a good reason not to split the classes into many VCX, and in fact given several good reason why it should be done, especially when dealing with multi-developers.
>
>So looks like that will be the avenue we will travel, assuming the development manager OKs it.

The only exception to this one-class-one-lib scheme would be if your form class has some control (which is a class of its own) which is very unlikely to be used anywhere else; then it makes sense to put it into the same classlib.

A half-way approach that I've seen was grouping similar forms into the same classlib. That was limited to the small forms used to enter selection criteria for reporting, so one group of reports would have all of its forms in one VCX. And then when there was something to do with these forms, it was quite often to be done on the whole series, and then one developer gets to do the whole group.

The corollary to this is: it's OK to group them into one classlib if you're sure you won't ever need two guys working on that group at the same time.

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform