Re: KDE's implementation of various GUI bits, problems with MacOSX

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Jan 20, 2004, at 12:27 AM, John Davidorff Pell wrote:

> I'm a little concerned about why we are having these issues in the 
> first place... There has to be a good reason why things are done in 
> KDE so strangely, right? Last time I posted on one of the KDE lists 
> about doing things "through qt", I got back a "once upon a time (1.x) 
> it was broken, and now we don't care about non-X11 users" response. 
> last I heard, the qt-only patch to KDE was mostly backed out too...
>
> If we try and "fix" KDE, to do it properly, then it would need a lot 
> of things re-written...
>
> the build system comes to mind... its a complex, yet functional, 
> system that should have been done with qmake... which, iThink, would 
> have made the whole app-package deal a whole lot easier. why wasn't 
> it? cuz once upon a time, qmake wasn't that great... Go Figure™
>
> also, the organisation of kdelibs and kdebase. These packages are 
> BLOATED like nobody's business! And, they're radically different based 
> on what dependancies are available at build time! kdelibs should be 
> like 4+ separate packages, and kdebase should be like 400+...
>
> So, to make the porting easier, lets fix KDE, ok? ;-) :-D
>
> ok, i'm done ranting...
>
> JP
>
>
I can only speak for myself, but I am sure it would be echoed by some 
others who have tried to help out, I think the quote was "I'm no 
programmer, but I can #ifdef the hell out of some stuff"
Thank pretty much sums it up for me.

My 2 centavos
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)

iD8DBQFADV7DEzC4Fc844K8RApnnAJ4vfExcp2w7kwNECQHASZz5xhny4ACbBcAS
RQO0iC2VYlPDhCQF8zm+oK4=
=QGdQ
-----END PGP SIGNATURE-----