All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nero <neroz@iinet.net.au>
To: George Staikos <staikos@kde.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kconfig (qt) -> Gconfig (gtk)
Date: Sun, 3 Nov 2002 20:08:01 +1100	[thread overview]
Message-ID: <200211032008.01807.neroz@iinet.net.au> (raw)
In-Reply-To: <200211022253.07606.staikos@kde.org>

On Sun, 3 Nov 2002 02:53 pm, George Staikos wrote:
> On November 2, 2002 17:43, Nero wrote:
> > thing. If you absolutely hate GTK+, there is menuconfig, and IIRC KDE
> > have their own [external] kernel configurator utility.
>
>    Please contact myself and/or Malte Starostik (kcmlinuz author) regarding
> the KDE kernel configurator.  We have full intentions to support the new
> system once it is in widespread use.  Support for the new system will not
> be in KDE 3.1 but it should be in KDE 3.2 if all goes as planned.
>
>    If anyone has some feedback regarding the design we would also be
> interested in that.
>
>
>    Additionally, to those who complain about Qt's size and dependencies:
>    1) The 16MB Qt .gz (13MB .bz2) contains much more than just the library.
> it contains Qt Designer, example code, full and complete documentation for
> the entire library, etc.  That's not obscene in comparison with gtk+ and
> all accompanying RAD tools etc.  If for some reason 16MB vs 8.5MB really
> hurts, contact Trolltech and ask them if they will split the package up for
> you.
>
>     2) Exactly what dependencies other than g++, yacc, and X11 devel
> libraries are you concerned about?  I'm not sure there are any others.  If
> you're really afraid of C++, I can assure you that it's not so scary, and
> you don't even have to look at the C++ code.  However if you must, there
> are tutorials available online.
>
>    Anyhow, I think it's great to see a kernel config system that can have a
> GUI implemented with stdio, curses, Xlib, GTK and Qt.  That's clearly the
> best plan and they should all be available to choose from.
>
> Thanks

I'm not scared of C++. Reducing dependancies on the kernel is important 
though. If you're configuring a kernel, you already have a C compiler 
installed, but perhaps not a C++ compiler. This was the issue with CML2 as I 
understand it, depending on Python. Not exactly the same issue, but it is the 
same idea. Many people often ask me why make menuconfig doesn't work - it's 
always because they didn't know they needed the ncurses library for it to 
work (it's a common question on IRC). More dependancies != Good. Once again, 
the only reason I think Qt is not a good choice is because it (for the 
moment) is a large download, takes a long time to compile, requires C++, and 
is not as common as Gtk 1.x yet. (I also don't see a problem with shipping 
both, but I'd say Linus wont like that idea).

  reply	other threads:[~2002-11-03 10:02 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 [this message]
2002-11-06  0:45         ` Bill Davidsen
2002-11-06  1:25           ` Mariusz Zielinski
2002-11-03  1:15     ` Rando Christensen
  -- 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=200211032008.01807.neroz@iinet.net.au \
    --to=neroz@iinet.net.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=staikos@kde.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.