Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Framework Changes
Message
De
03/07/1998 11:51:17
Bob Lucas
The WordWare Agency
Alberta, Canada
 
 
À
Tous
Information générale
Forum:
Visual FoxPro
Catégorie:
The Mere Mortals Framework
Titre:
Framework Changes
Divers
Thread ID:
00114094
Message ID:
00114094
Vues:
46
Kevin;

Here are some suggestions I have for upcoming changes. I suspect some of them will already be incorporated.

[1] Remove the session environment object from the kibzobj. Logically, it belongs on the form, because the form defines the private data session.

[2] Suggested change for csessionenvironment. A new property called oglobalenvironment that identifies the global environment object. An update to the set method to retrieve default settings from the global object. These could be overridden on an exception basis. I think this object should be part of the bizness object form and not created by the abstract factory. This is in case you have a need to modify a setting and want to do it at design time.

[3] The global session object should perhaps be an object in the application object container (not created by the factory or addobject). This would allow application specific settings to be altered at design time and not require a second call to set() after modifying the properties after instantiation. I don't see a need to subclass this object because the only alterations are likely to be property changes.

[4] Change all other addobjects to the abstract factory calls. These are mostly in the application object, I think.

There doesn't seem to be a hard and fast rule between sub-classing and using the abstract factory. I think the factory pattern is useful when the subclass doesn't need to change. Having an object within a container (the alternative) is useful when you know that design time changes are required. Otherwise, you will have to code the changes into the init after the object is created.

I am not sure there is an easy answer to this. If you add an object to a container within the framework, then we are 'stuck' with that object although we can modify methods and properties at design time. On the other hand, if the object is added by the abstract factory, we can change the class at will, but it means we lose the ability of making design time changes (but can sub-class to our hearts content.)

I have a test csessionenvironment object that adds the new property and gets its values from the globalenvironment object. I could post the code if you like.
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform