From: Eric McDonald <mcdonald@phy.cmich.edu>
To: cstevens@gencom.us
Cc: xconq7@sources.redhat.com
Subject: Re: SDL Interface Development
Date: Sun, 31 Oct 2004 18:26:00 -0000 [thread overview]
Message-ID: <41852D84.6010802@phy.cmich.edu> (raw)
In-Reply-To: <200410310637.52853.cstevens@gencom.us>
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
next prev parent reply other threads:[~2004-10-31 18:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-30 23:28 Eric McDonald
2004-10-31 4:10 ` Lincoln Peters
2004-10-31 6:13 ` Eric McDonald
2004-10-31 6:34 ` Elijah Meeks
2004-10-31 7:34 ` Lincoln Peters
2004-10-31 18:39 ` Eric McDonald
2004-10-31 18:23 ` Eric McDonald
2004-10-31 6:54 ` D. Cooper Stevenson
2004-10-31 18:26 ` Eric McDonald [this message]
2004-10-31 16:28 ` Skeezics Boondoggle
2004-10-31 19:04 ` Eric McDonald
2004-10-31 19:04 ` Lincoln Peters
2004-10-31 19:50 ` Skeezics Boondoggle
2004-11-07 8:29 ` Publicity Test Run Elijah Meeks
2004-11-13 23:23 ` New Source Tarball and Windows Installer (was Re: Publicity Test Run) Eric McDonald
2004-11-13 23:55 ` Publicity Test Run Lincoln Peters
2004-11-14 0:54 ` Eric McDonald
2004-11-14 22:31 ` Lincoln Peters
2004-10-31 17:45 Re: SDL Interface Development ejessen
2004-10-31 18:08 ` D. Cooper Stevenson
2004-10-31 18:57 ` Lincoln Peters
2004-10-31 19:09 ` Eric McDonald
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=41852D84.6010802@phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=cstevens@gencom.us \
--cc=xconq7@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).