I would rather have the selections fore accessible with less clutter and
work for the gamer. I would go for option 2, because, if there are 60 to
choose from, and you find it on the second screen of 20, there's no need to
go further. Another possibility: If you know the one that you want, is it
possible to use first letter navigation to locate it? Or control home or
end to quickly navigate from top to bottom and then work from there using
the up or down arrows ot tab and shift tab?
--
If guns kill people, writing implements cause grammatical and spelling
errors!
----- Original Message -----
From: "Thomas Ward" <thomasward1...@gmail.com>
To: "Gamers Discussion list" <gamers@audyssey.org>
Sent: Thursday, August 29, 2013 7:13 AM
Subject: [Audyssey] A Question About the Best user Interface
Hi everyone,
I have a quick question I thought I'd throw out here to the community
to see what you thought about this. As many of you know for a while
now I have been developing a WWE wrestling game in Python, that is
largely text based, but one problem is not all the performers can fit
on the same screen when selecting the challenger or the opponent for
the match. As the database of male and female performers grows this
problem will only get worse. Now, there are two ways of handling this
issue.
The way a sighted developer would handle this is they would table all
the options on the screen into columns and rows rather than put them
in a vertical list like this.
Select the challenger.
1. Steve Austin 2. Daniel Bryan 3. John Cena 4. Christian
5. Ted DiBiase Jr. 6. Edge 7. Mark Henry 8. Kane
Now, obviously the advantage of doing it this way is I could
conceivably squeeze a huge database of performers onto a single screen
simply by placing them into a table instead of a vertical list. I
should be able to place somewhere between 50 and 60 performers onto a
single screen. My concern though is that it will take more work
reviewing the screen to find the option for the performer you want to
play as you'd basically have to examine the entire table to find out
that a certain performer is number 36 out of 50 possibilities.
The alternative is I could create a vertical list of performers, but
split it up over several screens. That means if a database of
challengers had 60 performers you would get the first 20, press enter,
see the next 20, press enter again, and get the last 20 performers. In
some aspect sits more accessible, but I don't like it because I'd
rather see as many performers as possible on the same screen.
So any thoughts, suggestions, or ideas?
Thanks.
---
Gamers mailing list __ Gamers@audyssey.org
If you want to leave the list, send E-mail to
gamers-unsubscr...@audyssey.org.
You can make changes or update your subscription via the web, at
http://audyssey.org/mailman/listinfo/gamers_audyssey.org.
All messages are archived and can be searched and read at
http://www.mail-archive.com/gamers@audyssey.org.
If you have any questions or concerns regarding the management of the
list,
please send E-mail to gamers-ow...@audyssey.org.
---
Gamers mailing list __ Gamers@audyssey.org
If you want to leave the list, send E-mail to gamers-unsubscr...@audyssey.org.
You can make changes or update your subscription via the web, at
http://audyssey.org/mailman/listinfo/gamers_audyssey.org.
All messages are archived and can be searched and read at
http://www.mail-archive.com/gamers@audyssey.org.
If you have any questions or concerns regarding the management of the list,
please send E-mail to gamers-ow...@audyssey.org.
