From kde-core-devel Wed Aug 25 14:42:23 1999 From: Mosfet Date: Wed, 25 Aug 1999 14:42:23 +0000 To: kde-core-devel Subject: Re: Standard dialog margins. X-MARC-Message: https://marc.info/?l=kde-core-devel&m=93559232431468 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 ;-) On Wed, 25 Aug 1999, Stephan Kulow wrote: > Mosfet wrote: > > > > I don't see the problem with KGlobal. There is not dozens upon dozens of items > > in there, only ten... If you really don't want to load values in KGlobal then we > > also need to remove generalFont(), and fixedFont(), which I don't really see any > > reason to do. Actually, I think it should be extended to hold more items... > > > Yes, I think generalFont and fixedFont don't belong there necessary as > well. > The main word in your last sentense is _hold_. > > Greetings, Stephan > > -- > Better give your hours some more life than > your life some more hours. - anonymous -- Daniel M. Duley - Unix developer & sys admin. mosfet@mandrakesoft.com mosfet@kde.org mosfet@jorsm.com