From: Eric McDonald <mcdonald@phy.cmich.edu>
To: xconq <xconq7@sources.redhat.com>
Subject: Re: growth agendas and OO
Date: Thu, 20 Nov 2003 17:24:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0311201144590.3520-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <OOEALCJCKEBJBIJHCNJDMEBFGMAB.vanevery@indiegamedesign.com>
On Thu, 20 Nov 2003, Brandon J. Van Every wrote:
> Do you understand why Xconq won't get any bigger without certain
> infrastructural layouts?
The C infrastructure is pretty good (as Peter points out in a
later message); in fact, it is good enough that Xconq has gained 2
developers in the past 5 months. Not bad....
As far as building the game goes (since that is actually the
question at hand), the answer is: sure, it would be nice to have
some additional infrastructure. You seem to have this "me vs.
them" mentality though. When I suggested that _you_ could
contribute your VS project, you became rather defensive, thinking
that I somehow doubted your efforts. It would be nice if you would
understand that, within the open source community, there is a kind
of "altruism", that if you accomplish something positive then you
share it with others.
I didn't build this particular piece of infrastructure because I
didn't *need* it.
>But... some have a growth agenda, and others don't.
I have a personal growth agenda for Xconq. It goes something like
this:
Pre-7.5:
(1) Fix all known stability issues and crashing bugs.
(2) Verify documentation correctness and add more exposition
where necessary. Possibly spiff up the HTML version of the
manuals.
(3) Make sure that all the test cases pass muster. Possibly
enhance the testing system. (Although the normal use of skelconq
is to be invoked with arguments, it should probably not assume
that this is the case, as you pointed out and as I also noticed
some time ago.)
Post-7.5/Pre-7.6:
(1) Make a badass AI.
(2) Do some work with the tasking/planning system (related to
AI work, but some make-user-life-easier things also).
(3) Possibly extend GDL.
(4) Possibly extend the standing orders syntax.
(5) Possibly work on SDL/? interface.
> I am willing to contribute to the OO-ification of Xconq, if you want to
> pursue that agenda. If you think that agenda is misguided, then it's
> best to find out now.
I don't think that this is necessarily misguided in the long term.
But the C infrastructure works pretty darn good at present. We
even have some "polymorphism" due to nifty macro magic....
Xconq currently attempts to be at a C89 compliance level to make
sure that we are supporting as many platforms as possible. If you
say that we should just ditch those platforms, then you are simply
stating an opinion which is not even all that pragmatic. I
actually did put out a feeler a while ago, to see about moving the
compliance level to C99; the conclusion I reached is that the
time is not right yet.
Eric
next prev parent reply other threads:[~2003-11-20 17:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 2:15 Xconq UI thoughts Stan Shebs
2003-11-20 2:26 ` Brandon J. Van Every
2003-11-20 2:57 ` Eric McDonald
2003-11-20 9:45 ` growth agendas and OO Brandon J. Van Every
2003-11-20 10:49 ` Bruno Boettcher
2003-11-20 10:59 ` Brandon J. Van Every
2003-11-20 11:51 ` Jakob Ilves
2003-11-20 12:05 ` Brandon J. Van Every
2003-11-20 17:57 ` Jim Kingdon
2003-11-20 17:24 ` Eric McDonald [this message]
2003-11-20 17:51 ` Eric McDonald
2003-11-21 1:59 ` altruistic VS 2003 Solution files Brandon J. Van Every
2003-11-21 4:17 ` Eric McDonald
2003-11-21 9:02 ` So let's get right to the point Brandon J. Van Every
2003-11-21 23:14 ` Lincoln Peters
2003-11-22 0:06 ` Why Eric doesn't like my personal style Brandon J. Van Every
2003-11-23 11:13 ` Mark A. Flacy
2003-11-23 14:22 ` Brandon J. Van Every
2003-11-22 0:07 ` So let's get right to the point Brandon J. Van Every
2003-11-21 2:01 ` growth agendas and OO Brandon J. Van Every
2003-11-20 10:31 ` Xconq UI thoughts Andreas Bringedal
2003-11-20 10:37 ` keys and menus Brandon J. Van Every
2003-11-20 10:58 ` Xconq UI thoughts Bruno Boettcher
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=Pine.LNX.4.44.0311201144590.3520-100000@leon.phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--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).