Update to object code entry design

[James William Yoon]

Hello all,

I've made a couple of small changes to the object code entry design of draft
9 (http://wiki.fluidproject.org/display/fluid/Mobile+wireframes%2C+draft+9):

1. Colin suggested that instead of having the "invalid code" status fade out
after a few seconds, it should persist until the next code has been entered.
This is both to maintain accessibility and cater to users whose attention
might be elsewhere for the duration of the status life (which was envisioned
to be a couple of seconds). I think this is a good idea. The changes have
been reflected in both the wireframes and storycards.

2. To adjust to the chrome we have in 0.3 (see Colin's email of January 31,
'10), I've squished some of the elements on the screen while maintaining the
size of the keypad (which I feel can't be made smaller without sacrificing
usability). Implementing the aforementioned change also gave us a bit more
space to play with. Note that I've taken the worst case scenario wrt to
chrome--that is, I assumed that we would need to deal with both the top and
bottom browser chrome (address and action bars). This alternate chrome case
has been reflected in separate wireframes.

We're going through the rest of the wireframes now to see where chrome might
break functionality/usability in a really bad way, and may be making more
adjustments soon. (I suspect though that "object code entry" was the biggest
victim, as the previous wireframes relied wholly on a full-screen
experience)

James
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20100201/6c813891/attachment.html>