From: Rando Christensen <rando@babblica.net>
To: "Dr. David Alan Gilbert" <gilbertd@treblig.org>
Cc: neroz@iinet.net.au, rlievin@free.fr, linux-kernel@vger.kernel.org
Subject: Re: Kconfig (qt) -> Gconfig (gtk)
Date: Sat, 2 Nov 2002 18:15:11 -0700 [thread overview]
Message-ID: <20021102181511.46583a34.rando@babblica.net> (raw)
In-Reply-To: <20021102203608.GB731@gallifrey>
Sat, 2 Nov 2002 20:36:08 +0000: Dr. David Alan Gilbert ("Dr. David Alan
Gilbert" <gilbertd@treblig.org>):
> Oh please....
> Wouldn't it be more helpful to iron the (few) small glitches out of
> the qt based one than write a new one just because you don't happen to
> like the library?
Maybe; however, there's a big difference between gtk+ and qt- gtk 1.2
take about 5 minutes to compile. The last time I compiled qt, it took
about 3 hours on my duron 800.
GTK is a lot smaller of a platform, and a lot of users prefer to use it
instead. If someone is willing to write (and maintain) a GTK+
(especially if it's ait gtk+-1.2.x. gtk-2.0 is getting a bit more
bloaty) version of it, I know quite a few people who would gladly use it
instead of the QT.
If people are willing to support both a QT and a GTK version, then there
should be no real problems.
--
< There is a light that shines on the frontier >
< And maybe someday, We're gonna be there. >
< Rando Christensen / rando@babblica.net >
next prev parent reply other threads:[~2002-11-03 1:09 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-25 22:21 Kconfig (qt) -> Gconfig (gtk) Romain Lievin
2002-11-02 7:03 ` Nero
2002-11-02 20:36 ` Dr. David Alan Gilbert
2002-11-02 17:00 ` Jon Portnoy
2002-11-02 22:19 ` bert hubert
2002-11-02 19:45 ` Nero
2002-11-02 20:42 ` Xavier Bestel
2002-11-02 21:12 ` David B. Stevens
2002-11-02 21:07 ` Russell King
2002-11-02 22:43 ` Marek Habersack
2002-11-02 22:48 ` Sam Ravnborg
2002-11-02 21:25 ` Dave Jones
2002-11-02 21:59 ` Alan Cox
2002-11-02 21:57 ` Patrick Finnegan
2002-11-02 22:06 ` Russell King
2002-11-02 22:33 ` Roman Zippel
2002-11-02 22:34 ` Russell King
2002-11-03 3:18 ` Gerhard Mack
2002-11-02 22:47 ` Sam Ravnborg
2002-11-02 23:03 ` Roman Zippel
2002-11-02 22:56 ` Alan Cox
2002-11-02 23:07 ` Patrick Finnegan
2002-11-03 4:07 ` Matthew D. Pitts
2002-11-04 4:57 ` Stefan Traby
2002-11-04 6:21 ` Sam Ravnborg
2002-11-02 23:28 ` Dr. David Alan Gilbert
2002-11-02 22:43 ` Nero
2002-11-02 23:59 ` Roman Zippel
2002-11-03 0:06 ` J.A. Magallón
2002-11-02 23:16 ` Nero
2002-11-03 1:30 ` Alan Cox
2002-11-03 3:09 ` Christoph Hellwig
2002-11-03 9:47 ` Geert Uytterhoeven
2002-11-03 12:56 ` Christoph Hellwig
2002-11-03 4:42 ` Randy.Dunlap
2002-11-03 0:07 ` Patrick Finnegan
2002-11-03 3:53 ` George Staikos
2002-11-03 9:08 ` Nero
2002-11-06 0:45 ` Bill Davidsen
2002-11-06 1:25 ` Mariusz Zielinski
2002-11-03 1:15 ` Rando Christensen [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-31 13:43 Where's the documentation for Kconfig? Matthew Wilcox
2002-10-31 14:43 ` Roman Zippel
2002-11-01 12:52 ` Russell King
2002-11-01 13:50 ` Roman Zippel
2002-11-01 19:31 ` Russell King
2002-11-01 20:35 ` Roman Zippel
[not found] ` <20020625221306.GA439@free.fr>
[not found] ` <Pine.LNX.4.44.0211021254420.6949-100000@serv>
2002-11-02 13:20 ` Kconfig (qt) -> Gconfig (gtk+) Romain Lievin
2002-11-02 14:45 ` Roman Zippel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021102181511.46583a34.rando@babblica.net \
--to=rando@babblica.net \
--cc=gilbertd@treblig.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neroz@iinet.net.au \
--cc=rlievin@free.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox