I'm new to this field so my language may not be quite up to par with
conventions, but hopefully this makes some sense and some of you may have
some advice for me.
I'm working on a school project with the task of designing an interface for
a digital frame where the user can directly insert a memory card into the
frame, and then complete all functions with a touch-screen interface. (My
instructor could very well be reading this list...if so, Hi, Paul!)
It is expected that typical users will be amateur photographers with
moderate computer skills, so they would probably want to be able to complete
some basic photo editing functions on the frame itself, but anything more
advanced than say adjusting brightness and contrast, they would probably do
with photo editing software on their computer. The frame itself could hold a
series of photographs, and users would be able to edit a slideshow feature
all just by using the interface of the frame (which is only 6 x 4").
What I'm debating right now is to what extent should I make the interaction
a sequence of steps vs. providing short-cuts to all potential functions in a
more "free-flowing" manner, for example with a horizontal menu tab at the
top of the interface. My thinking right now is that making it a set of
sequential steps for importing, editing images, and then editing the
slideshow will increase learnability for new users. But more experienced
users will benefit from increased efficiency by being able to jump from one
set of functions (e.g. image editing) to another (e.g. slideshow editing)
without the constraints of "steps".
At the same time, there are a limited number of tasks users would complete
given the device has very specific functions, so in this sense it could be
feasible to allow users to select one of these functions and then within
that follow specific steps (e.g. the user taps on the "Edit Images" tab on
the top horizontal menu and then proceeds through a sequence of steps).
> My suggestion as well would be a d-and-d suggestion, so long as your > elements have obvious grabbers, and possibly a menu item on the portlet bar
> called "move" ... This can "pop loose" the portlet making it more visibly > obvious that the user can grab it and drag it. There should also be an > indication of when the user released where the portlet would go. > > Yes, you can do intra-browser d-n-d in both IE and Netscape ... Even in > Netscape 4 ... But the code is very different for the Netscape 4. IE 5+ and
> Netscape 7 you could probably do in a single code line. > > -- dave > > > > _______________________________________________ > Interaction Design Discussion List >discuss at interactiondesigners.com > -- > to change your options (unsubscribe or set digest): http://discuss.interactiondesigners.com
> -- > Questions: lists at interactiondesigners.com > -- > Announcement Online List (discussion list members get announcements already)
>http://interactiondesigners.com/announceList/ > -- >http://interactiondesigners.com/ >