Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
OOP recommendations, please
Message
 
 
À
24/06/2000 18:13:08
Information générale
Forum:
Visual FoxPro
Catégorie:
Programmation Orientée Object
Divers
Thread ID:
00383528
Message ID:
00384450
Vues:
25
Alex,
I agree with Craig's suggestion to break out UI and non-UI classes.

And to expand alittle on that subject, I would have several business object class libraries instead of grouping them under one large library. The reason for this is team development. If all the business objects are in one class library then only one developer can work on that library at a time. If you break them out in to different VCXs, development time can be used much more efficiently (IMO).

You could have a master business object class in the _abizlib library (opr you could add this class to the framework level library. Then all your business objects would subclass from it.

>Hi Cindy, Craig, Larry and Alex,
>
>Thinking about this subject makes me conscious how A/R I am about nomenclature and classifications. I am otherwise pretty disorganized. However, in order to get off on the right foot in this matter I'd like you opinion.
>
>What do you think of this organization for class libraries/classes:
>
>1) _base.vcx. Contains first level classes. (_txt, _frm, _cmd, etc)
>
>2) _framework.vcx. Contains classes that remain the same from project to project: for example, _app, _frmDataEntry, _report, _ds (data services), _biz (the base business object class).
>
>3) _aframework.vcx. Contains equivalent classes to those in _framework.vcx, but subclassed for this application. (_aapp,_afrmDataEntry, _areport, _ads, _abiz)
>
>4) _abizlib.vcx Contains business objects for this app. e.g. _bizEmployee, _bizTransaction, etc.
>
>Values that need to be easily accesible throughout app would be oApp properties.
>
>Thank you.
>
>Alex
>
>>Alejandro,
>>
>>One thing no one else has mentioned is the global variables. First, any variable initialized in the main program, though private by default, will function as a global variable because it will be visible to the whole application which runs from there on down.
>>
>>Many people use an application object which holds these variables as its properties.
>>
>>
>>>Lastly, I use global variables to hold some frequently used values that I do not wish to fish repeatedly from the parameter table.
Larry Miller
MCSD
LWMiller3@verizon.net

Accumulate learning by study, understand what you learn by questioning. -- Mingjiao
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform