From: Eric McDonald <mcdonald@phy.cmich.edu>
To: xconq7 <xconq7@sources.redhat.com>
Subject: Another Possible Solution to the Occupants Display Problem
Date: Mon, 06 Sep 2004 19:42:00 -0000 [thread overview]
Message-ID: <413CB191.4060205@phy.cmich.edu> (raw)
Another thought just occurred to me as to how we might solve the
occupants display problem:
Transport occupied with 2 units:
|------------|
| TTT |
| T |
| T |
| |
| OOO OOO |
| O O O O |
| OOO OOO |
|------------|
Transport occupied with > 2 units:
|------------|
| TTT |
| T |
| T |
| |
| |--------| |
| | Occs | |
| |--------| |
|------------|
Big "T" is transport unit. Big "O" is an occupant unit. Figures not
drawn to any sort of scale or proportion. "Occs" is a button that brings
up a popup containing images of the occupants.
This would be for an 88x88 (64x64) or 44x44 (32x32) view. For 22x22
(16x16), it might be necessary to abbreviate down to "OV" or maybe just
a plain rectangle with no text, since even the small font might be too
tall to fit. For 11x11 (8x8), clicking anywhere in the transport should
probably bring up the occupant view popup.
As to how the occupant view popup would present information, that is
still an open question. I would suggest that it be centered over (and
obscuring the transport), and should always present occ images at least
at 44x44 (32x32), and that the transport's name, location, and
similarly-sized image should be near the top of the popup. This means
that the popup would be variably-sized according to the number of occs.
The benefit is that all of the occs would be shown clearly and in easily
clickable spatial regions. The popup could be dismissed by either
clicking a close box in its upper, right corner, or by hitting the
escape key. Popups could be layered for transports inside of transports.
|----------------------------------------|
| |X X|
| TTT Your transport "Foo" | X |
| T in plains at (x,y) |X X|
| T ----|
| |
| |---| |---| OOO OOO |
| |T | |T | O O O O |
| ||-|| |O O] OOO OOO |
| |---| |---| |
|----------------------------------------|
In the above example, the popup for transport "Foo" shows 4 occs, two of
which are transports as well. The leftmost occ has a popup button in the
lower part of its transport box because it has more than 2 occs. The occ
to the right of it (second from left) only has 2 occs and so they are
displayed as is. The big "X" in the upper, right corner is the close box.
Thoughts?
Eric
next reply other threads:[~2004-09-06 18:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-06 19:42 Eric McDonald [this message]
2004-09-06 20:49 ` Jim Kingdon
2004-09-06 22:09 ` Eric McDonald
2004-09-07 17:03 ` Jim Kingdon
2004-09-08 1:29 ` 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=413CB191.4060205@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).