On Wed, 25 Aug 1999, Mosfet wrote:

> What is the problem with the loading of variables to get the inital
> value? Is it just a style preference? My main objection to splitting the
> classes is that we will end up with two different classes with very few
> methods and similar function... I think it is a inconvenience to the app
> developer to be doing this based solely on if the values are read from
> KConfig or done via a new allocation of another object (which is
> probably reading KConfig anyways).  KGlobal is for global variables,
> period, IMHO of course ;-)

KGlobal was born due to the same problem with KApplication becoming a
dumping ground for dozens of otherwise unrelated variabless. I'd hate to
see that happen to KGlobal too! The idea is to group variables as much as
possible and use KGlobal to access the _groups_ rather than the
variables/constants directly. Believe me, adding one or two globals every
now and then adds up, and before you know it KGlobal will become as messy
as KApplication.

-Taj.

Sirtaj S. Kang       taj@kde.org         ssk@physics.unimelb.edu.au
Univ of Melbourne	The "gui" in "Penguin" is pronounced "K-D-E"