public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Hans Ronne <hronne@comhem.se>
To: Elijah Meeks <elijahmeeks@yahoo.com>
Cc: xconq7@sources.redhat.com
Subject: RE: UI proposal
Date: Wed, 19 Nov 2003 19:01:00 -0000	[thread overview]
Message-ID: <l03130300bbe165578c6f@[212.181.162.155]> (raw)
In-Reply-To: <20031119175739.55341.qmail@web13103.mail.yahoo.com>

>I think this is a great idea, specifically the
>occupant and build windows and especially the option
>to show only what can be built by the current unit.
>This would clean up my games, for sure.

If you check out the Mac interface, you will find that several of the ideas
discussed already are implemented there.

1. A unit list can be brought up in a separate window, which contains much
more information (plans, tasks, build status, materials etc) than the tcltk
unit list.

2. By right-clicking on any unit you bring up a small floating window with
all the information you find in the unit info pane in the tcltk interface.
Plus images of occs or transports. Clicking on these bring up new floating
windows with information on those units. And so on. There is also direct
access to the relevant help node through a help button in each floating
window.

3. When a unit needs a new build task a small floating window pops up with
a menu that shows only what can be built by that unit. Picking an item
closes the window and sets the build task.

The key thing here is that stuff like this pops up only when you need it
(or ask for it). The Mac interface is similar to the SDL interface (and
differs from the tcltk interface) in that emphasis is put on a whole-screen
heads-up display. The map covers the entire screen. Lincoln's proposal
included a lot of useful stuff, but there was not much space left for the
map. And the map is the most important part of a game like this.

Hans


  reply	other threads:[~2003-11-19 18:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-19 18:37 Elijah Meeks
2003-11-19 19:01 ` Hans Ronne [this message]
2003-11-19 19:49   ` Lincoln Peters
2003-11-19 20:03     ` UI proposal (more screenshots) Lincoln Peters
2003-11-19 20:04     ` UI proposal Eric McDonald
2003-11-19 20:36   ` Elijah Meeks
2003-11-20  9:33   ` Andreas Bringedal
  -- strict thread matches above, loose matches on Subject: below --
2003-11-19  8:22 Lincoln Peters
2003-11-19 12:15 ` Brandon J. Van Every
2003-11-19 19:02   ` Lincoln Peters
2003-11-19 14:51 ` Peter Garrone
2003-11-19 14:51   ` Erik Jessen
2003-11-19 15:24     ` Bruno Boettcher
2003-11-19 17:25       ` Eric McDonald
2003-11-20  0:35       ` Brandon J. Van Every
2003-11-19 17:09   ` Eric McDonald
2003-11-19 19:07     ` Lincoln Peters

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='l03130300bbe165578c6f@[212.181.162.155]' \
    --to=hronne@comhem.se \
    --cc=elijahmeeks@yahoo.com \
    --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).