Re: UI Guidelines: Dialogs



thristian atdot org wrote:
> > It's not a bad idea, my only reservation would be what I touched on in
> > my last post-- druid buttons and web browser buttons don't do *quite*
> > the same thing.  But maybe the distinction is too subtle to bother the
> > average user... something else to usability test  :)
> 
> I'm not sure if this is offtopic or not... *how* would you test such a
> thing? The combinations to be tested are (I guess) Back/Forward,
> Back/Next, Prev/Next, Previous/Next, Prev/Forward, Previous/Forward
> and any others we think of.

I think using abbreviations is just totally stupid. We're not lacking
screen estate in a druid, and using abbreviations often makes it more
difficult to understand for the user, and makes translation harder, and
sometimes even impossible.

That leaves the alternatives Back/Forward, Back/Next, Previous/Next,
Previous/Forward.

I think of druids as a set of "pages" or "screens" asking questions that
help me do what I want. That makes me speak of "going to the previous
page/screen" or "going to the next page/screen". So I prefer
Previous/Next.
Of course, this depends on what analogy is used in druids, but I think
the "pages" analogy or "screens" analogy is rather commonly used.


Christian




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]