[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: [PATCH] KPassivePopup eye-candied "replacement"
From:       Sascha Cunz <sascha.cunz () tiscali ! de>
Date:       2005-05-11 6:47:49
Message-ID: 200505110902.38987.sascha.cunz () tiscali ! de
[Download RAW message or body]

Hi,
On Wednesday 11 May 2005 01:14, Aaron J. Seigo wrote:
> adding another class is sub-optimal here on several fronts IMHO:
>
>  - it opens the way for more visual incompatibilities with some using
> KPassivePopup, others using KBalloonPopup
right

>  - it requires developer retraining
right, though it's source compatible.

>  - it isn't extensible (we can't just add a new class everytime we want to
> change this behaviour =)
right

>  - it adds to the number of symbols in the library that would need to be
> linked at run time (bad for start up times)
right

> extending KPassivePopup would be the preferred route here IMO.
yes, were my first intentions, too. 

> Sascha: is your goal 3.5 or 4.0 with this?
Well, as i convinced myself finally to make it public, i think it should also 
get into 3.5.

Merging both classes, shouldn't be that much work.

Sascha
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]