> Hmm...everyone seems to have different ideas about how to they want to
use
> their frameworks... Many of them I have considered myself. The only
> question is, how often do 'fixes' or 'additions' to the global class
> libraries propagate new errors into older applications, which will appear
> on the next compile?
this is why encapsulation is important
you have to make sure that
a. object are self contained
b. if you make a change you have to leave support for the older interface
btw - other probably said something similar - but whayI have is as follows
I have several levels of subclasses
for the basic framework I have base.vcx which are subclasses of most of
VFP's controls - with my additions. Then there are controls, forms,frames,
toolbars, non-visual etc. class libraries (all subclassed from my base
classes)
I also have other common componnents like login scheme , user preferences
(for toolbars,forms and grids) database, user management system etc.
each new project has subclasses of the above and its own classes - if
something turns up significant./general enough it is moved (added) to the
general framework (usually this happens with new controls that clients
request)
Arnon
Précédent
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement