public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: "D. Cooper Stevenson" <cstevens@gencom.us>
To: xconq7@sources.redhat.com
Subject: Re: Progress with ParaGUI
Date: Sun, 07 Nov 2004 19:29:00 -0000	[thread overview]
Message-ID: <200411071614.54895.cstevens@gencom.us> (raw)
In-Reply-To: <418DDCEA.1060404@phy.cmich.edu>

Dear Eric,

Your SDL progress is really tops; canning the SDL library installation process 
is no mean feat. this is because once you have the ParaGUI setup "canned" for 
the platforms then the rest is history; an application designer need only 
think about the SDL interface when designing for Xconq.

Noteably, This helps confirm what I had suspected regarding the "noise level" 
this last week: it was quiet because we all had our heads down working!

I will create a setup document as soon as the tarball is out of the oven.

Note to Elijah: please consider warming up the controls on your "publicity 
engine" over the next couple of weeks as it looks like we're making good 
progress at least three fronts: SDL, graphics, and GIS. If there's anything 
you need here, please let me know. Don't worry about bandwidth; I have it 
covered. 

Also, would you please send Gpeterz an email on my behalf and let him know 
that I think his unit portrait artwork is excellent?

In short, when I think about the progress we're making it makes me shake my 
head a little and thing, "it's a good thing." This is sweet, Eric!


-Coop

On Sunday 07 November 2004 08:29, Eric McDonald wrote:
> Hello Xconq Developers,
>
>    I am making good progress in preparing Xconq to use the ParaGUI
> toolkit for the SDL interface. The Linux side of things is essentially
> taken care of; I have already made RPM packages for ParaGUI. Most of the
> Windows preparation went pretty smoothly. I have had to fight a few
> compilation issues here and there, but I think that things are almost
> taken care of. I will try to finish up that battle later today so that I
> can go ahead and create a Windows installer for the ParaGUI libraries
> and headers (for developers and others who are interested in building
> the soon-to-be SDL/ParaGUI interface from sources). I have already
> documented where existing Windows installers for the various ParaGUI
> dependencies can be found (and the recommended way to use them), and I
> will make that document available later today after I get some sleep.
>
>    Regular players and game designers should not notice much change with
> the SDL interface, at least not until next weekend.
>
>    Regards,
>      Eric

  reply	other threads:[~2004-11-07 16:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-07 16:12 Eric McDonald
2004-11-07 19:29 ` D. Cooper Stevenson [this message]
2004-11-08  3:04   ` Eric McDonald
2004-11-08  5:44     ` Eric McDonald
2004-11-08 13:44       ` GIS Update [Was: Re: Progress with ParaGUI] D. Cooper Stevenson
2004-11-09  3:59         ` Eric McDonald
2004-11-07 20:21 ` Progress with ParaGUI Tom Low-Shang
2004-11-07 23:44   ` 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=200411071614.54895.cstevens@gencom.us \
    --to=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).