public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Elijah Meeks <elijahmeeks@yahoo.com>
To: Andreas Bringedal <anbring@online.no>, xconq7@sources.redhat.com
Subject: Re: Three thoughts
Date: Fri, 20 Aug 2004 22:03:00 -0000	[thread overview]
Message-ID: <20040820212846.86901.qmail@web13126.mail.yahoo.com> (raw)
In-Reply-To: <00b201c486e4$5b750e40$8af74382@Rufus>


> > On Fri, 20 Aug 2004 mskala@ansuz.sooke.bc.ca
> wrote:
> >
> > > * If firing at specific units were to be a big
> part of some game, then it
> > > would be nice if it were easier to designate
> specific units when there are
> > > many of them, or nested occupant/transports, in
> a cell.  As it is, even at
> > > the deepest level of zoom it's quite difficult
> to click precisely on one
> > > unit if there are a lot of them in the cell. 
> One way to deal with this
> > > might be for an interface to be able to give me
> a dialog box with a list
> > > of units in the cell.
> 
> I've never understood why the interface has been so
> low on the priority list.  Back when I played Xconq
> 5.4 the interface was ok.
> Today I can't bring myself to play the game anymore
> due to the interface and to a lesser degree the high
> dencity of cities.  But
> since I don't program I can't really complain.  I
> just wanted to say that with a better interface
> you'd get a whole lot more players
> and perhaps programmers.


I know the feeling.  I didn't include city
improvements in Opal, even though they'd improve the
game, just because they end up making it look so
cluttered*.  And the TCL/TK interface is, let's face
it, so ugly in comparison to the Mac interface and
even the stripped down SDL interface (Which I'm still
in love with.  Really.  When I play XConq in SDL, it
looks like a *game*).

Another thing to think about is the opening screen,
which relates especially to Eric's game-image feature.
 If we could revamp that, then players would probably
have an easier time choosing games and seeing
something they like.

*This, like Eric's items, would be fixed by an
occupant dialog box.  I've tried to work with units as
items, though, and found difficulty with setting the
game up so that a unit could pick up another unit.  It
seems like I have to give Item units ACP and movement,
which is an annoyance to the AI and player and uglier
gameplay.  Anyone have any suggestions?  I'd love an
item-demo.g and, of course, if Eric throws in static
improvements, I can rewrite Cast Iron Life, and even
change the experience system in AWLS so that a unit
carries an Experience unit that provides bonuses,
rather than have five different units for each
experience level.  But that would probably necessitate
an AI-recommendation table for building and and and...
 Ah, being a needy XConq designer sure is the life.




		
__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail

  parent reply	other threads:[~2004-08-20 21:28 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-20 16:22 mskala
2004-08-20 18:34 ` Eric McDonald
2004-08-20 21:17   ` Andreas Bringedal
2004-08-20 21:28     ` Eric McDonald
2004-08-20 23:57       ` Andreas Bringedal
2004-08-21  1:21         ` Eric McDonald
2004-08-21  4:35           ` Jim Kingdon
2004-08-21 20:38           ` Jim Kingdon
2004-08-20 22:03     ` Elijah Meeks [this message]
2004-08-20 23:27       ` Eric McDonald
2004-08-21  1:17         ` mskala
2004-08-21  2:31           ` Eric McDonald
2004-08-21  4:33             ` mskala
2004-08-22  3:09 ` Hans Ronne
2004-08-22  6:38   ` Item Units Elijah Meeks
2004-08-22  9:37     ` Eric McDonald
2004-08-24  1:43       ` Lincoln Peters
2004-08-24  2:38         ` Eric McDonald
2004-08-24  2:51           ` Lincoln Peters
2004-08-24  3:32             ` Eric McDonald
2004-08-22 14:00   ` Three thoughts mskala
2004-08-22 18:56     ` Hans Ronne
2004-08-22 19:16       ` Lincoln Peters
2004-08-23  4:31         ` Jim Kingdon
2004-08-23 13:04           ` Elijah Meeks
2004-08-24 18:07             ` Eric McDonald
2004-08-24 20:59               ` Elijah Meeks
2004-08-25  0:54                 ` Unit-Image Bug Elijah Meeks
2004-08-25  4:58                   ` Eric McDonald
2004-08-23 16:48         ` Three thoughts Eric McDonald
2004-08-24  0:55           ` Lincoln Peters
2004-08-24  2:09             ` Eric McDonald
2004-08-24  3:02               ` Lincoln Peters
2004-08-24 18:12                 ` Eric McDonald
2004-08-25  5:34                   ` Jim Kingdon
2004-08-25 17:16                     ` Lincoln Peters
2004-08-25 22:09                       ` Jim Kingdon
2004-08-26  2:15                         ` Eric McDonald
2004-08-26  6:17                           ` Jim Kingdon
2004-08-26 19:12                             ` Eric McDonald
2004-08-26 22:08                               ` CXP??? Elijah Meeks
2004-08-27  1:50                                 ` CXP??? Lincoln Peters
2004-08-27  5:10                                 ` CXP??? 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=20040820212846.86901.qmail@web13126.mail.yahoo.com \
    --to=elijahmeeks@yahoo.com \
    --cc=anbring@online.no \
    --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).