From kde-core-devel  Sat Oct 23 17:11:28 1999
From: weis <weis () stud ! uni-frankfurt ! de>
Date: Sat, 23 Oct 1999 17:11:28 +0000
To: kde-core-devel
Subject: Re: KGlobal (was: Re: caption stuff and embeddable components)
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=94069875122881

Hi,

KLibGlobal delegates some stuff to KGlobal.
So with the new KGlobal you must implement a flag
that tells KGlobal wether it is really global or just
global to a library.

But if it works, I dont care wether it is KLibGlobal or KGlobal.

Bye
Torben


On Sat, 23 Oct 1999, Simon Hausmann wrote:

> Hi,
> 
> OK, I just talked about this problem with David on IRC.
> What do you think about:
> - moving component/application attributes to KGlobal
>   (like name, icon, mini-icon)
> - removing KLibGlobal (and make components use *their* instance of KGlobal
>   instead)
> - providing KGlobal *KApplication::global()
>   (so the *current* KGlobal::foo() would become kapp->global()->foo() )
> - changing the KLibGlobal argument of functions like locate() to KGlobal
>   (and still using the 0L default argument) , and checking "inside" that
>   function for 0L and using KApplication::global() if the argument is 0L.
> 
> Opinions? Flames? :-)
> 
> Ciao,
>  Simon
> 
>