Discussion Archive: November 2005

Guide to very complicated dialogue

Guide

We are working on a web-based solution that triggers a windows dialogue
which is very complicated and impossible to change. The user then have
to finish this dialogue to download and install a Key so that they can
access certain services later on. So, as usual we have to come up with
the best possible solution knowing that it will not be very usable.

To guide the users through the dialogue, they need help. We want to give
them the possibility to print out an instruction, open a demo etc. But
context specific help is best.

Senior UI Designer- Seattle - Amazon.com -Full-Time

> Senior UI Designer - Amazon.com - Seattle
> Amazon.com is seeking an enthusiastic, innovative designer skilled in the areas of visual, user-interface, and web-specific design to join the Retail Design Team. The Retail Design Team is responsible for the customer experience on the web site, specifically as it relates to our various product offerings. You will be responsible for designing the usability and aesthetics of new product lines on our Website, as well as enhancing existing features and developing new features.

applets and windows

I'm wondering if anyone knows of established guidelines for when a
window (dialog,etc) opened by an applet should be bound to the applet
(does not draw outside the applet area), and when the window should
be drawn as a normal window.

As many are nowadays, we are working on some hosted applications that
straddle the space between desktop app and web app. My initial
reaction to this problem is to restrict the dialogs that interact
only with the data on the web, and float dialogs that interact with
the filesystem, like import, export and so on.