On Fri, Nov 5, 2010 at 11:20 PM, Rob Ross <[email protected]> wrote:
> > > By the way, I think you are misusing the term "modality", which might be > why we seem to be in disagreement on this issue. > > I'm using it in the simplest possible way to describe a human/computer > interaction where the human has to keep a state model in his/her head as the > software is used. That's what I figured. The more traditional meaning of "modal" is something that forces you to act on it before you can resume other activities, such as a "modal dialog". They are sometimes necessary but by and large, modern applications are moving more to a "modeless" model where the actions you need to do are typically moved away from the main document so you can act on either any time you like. You are probably more talking about "context", and again, my experience has shown that most users have no problems remembering a stack of three-four past activities (and if they make a mistake, they can always undo it by going "forward", which is another strength of this model). > The simplest example is something like Photoshop, where depending on your > current mode (i.e., which tool is selected), clicking an object or using the > keyboard can produce vastly different results. > > A more modeless example would be a simple text editor. Now that I read this, I think you are simply confusing "model" and "modal". -- Cédric -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
