From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25546 invoked by alias); 31 Oct 2004 18:23:13 -0000 Mailing-List: contact xconq7-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: xconq7-owner@sources.redhat.com Received: (qmail 25478 invoked from network); 31 Oct 2004 18:23:10 -0000 Received: from unknown (HELO sccrmhc11.comcast.net) (204.127.202.55) by sourceware.org with SMTP; 31 Oct 2004 18:23:10 -0000 Received: from [192.168.181.128] (unknown[67.176.41.158](misconfigured sender)) by comcast.net (sccrmhc11) with ESMTP id <200410311823100110031ohke>; Sun, 31 Oct 2004 18:23:10 +0000 Message-ID: <41852D84.6010802@phy.cmich.edu> Date: Sun, 31 Oct 2004 18:26:00 -0000 From: Eric McDonald User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) MIME-Version: 1.0 To: cstevens@gencom.us CC: xconq7@sources.redhat.com Subject: Re: SDL Interface Development References: <41841290.3040905@phy.cmich.edu> <200410310637.52853.cstevens@gencom.us> In-Reply-To: <200410310637.52853.cstevens@gencom.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004/txt/msg01377.txt.bz2 D. Cooper Stevenson wrote: > Ideally the SDL GUI builder would compile the SDL code such that only libsdl > were required for Xconq (save libpng, etc.) If the hacker cost of entry were > a bit high, I think that's okay if we discipline ourselves, as you outlined, > to provide Howto documentation to facilitate them. I am willing to commit to > writing this documentation. Excellent, thanks. I do not expect it to be too troublesome, since all the packages in question are autoconffed, IIRC. And, for MinGW32 developers, I am willing to create installers that would drop precompiled libs, headers, etc... into the appropriate places in their existing MinGW32 hierarchy. Also, it is probably not necessary that we upgrade every time a new version of a prereq is released, _only for bugfixes which are relevant to the interface development. > Oh, of course. Their will certainly be bumps. I think that getting some > interfaces up that really look sharp-even if they are in development-could > definitely attract quality developers. This irons out bugs quicker and the > cycle repeats itself by attracting more developers. 'Twould be nice if this was the spark that finally ignited the developer cycle.... Xconq is a fairly big project, and if you have a stack of papers and text files like I do, which have feature ideas and known bugs, it can seem like a long, weary road at times. Eric