Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 9 Oct 2002 10:50:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 9 Oct 2002 10:50:27 -0400 Received: from smtpzilla1.xs4all.nl ([194.109.127.137]:49669 "EHLO smtpzilla1.xs4all.nl") by vger.kernel.org with ESMTP id ; Wed, 9 Oct 2002 10:50:26 -0400 Date: Wed, 9 Oct 2002 16:55:43 +0200 (CEST) From: Roman Zippel X-X-Sender: roman@serv To: Brendan J Simon cc: Linus Torvalds , linux-kernel , kbuild-devel Subject: Re: [kbuild-devel] Re: linux kernel conf 0.8 In-Reply-To: <3DA43C3A.2060608@bigpond.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1171 Lines: 27 Hi, On Thu, 10 Oct 2002, Brendan J Simon wrote: > As you can see there are soooooo many guis to choose/use and everyone > has there favourite. I suggest that the real work be done outside of > the GUI program. ie. seperate GUI and application guts as much as > possible. I would use python as the main language but C or even C++ > could be used instead as a lot of people hate interpreters, or hate > python (prefer perl, php or something else). > > I'm pretty sure there is no one solution and it comes down to the > politics and preferences of the final decision makers up the heirarchy. Because of this I'm planning to make the config backend available as shared library, so it can be loaded by external programs. My QT app then would be basically just the reference implementation. I also want to add a SWIG interface file, so you can even access the config database with your preferred script language. bye, Roman - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/