Re: Kconfig (qt) -> Gconfig (gtk)

[Nero]

On Sun, 3 Nov 2002 11:06 am, J.A. Magallón wrote:
> On 2002.11.03 Roman Zippel wrote:
> > Hi,
> >
> > On Sun, 3 Nov 2002, Nero wrote:
> > > OR, we could use the logical choice. GTK+ is on most systems, has
> > > hardly any dependancies, is relatively small (compared to Qt) and
> > > doesn't require a C++ compiler. Really, I think the only people being
> > > religious here are the ones voting for Qt, as it just doesn't make
> > > sense to use it for such a thing.
> >
> > Show me the source and we can continue this discussion. Right now qconf
> > is included as replacement for the old xconfig. It shouldn't take to much
> > effort to package it seperately. As soon as someone is interested in
> > doing this for a distribtion I'll add the few missing bits.
>
> As I see it, the onle thing that should be included in a standard kernel
> would be something like a kconfig-xaw, that is sure to be on every box that
> has X, and could be a reference implementation.
>
> And you could face one other religious war: qt2 or qt3 ? So as gtk1 or
> gtk2...

Gtk1 is going to be around for quite a while because so many apps wont be 
ported over to Gtk2 at all [dropped projects], and Gtk2 is not yet as 
widespread as 1.x either, so using Gtk1 is obvious. Qt2 vs. Qt3 - people tend 
to have the latest KDE if they run it, which means the latest Qt. Nearly all 
of the major distros ship with KDE3 now too (debian is still on KDE2 for some 
annoying reason, and Xandros (major?) have a hacked-to-bits KDE2).