Stories
Slash Boxes
Comments

NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

use Perl

All the Perl that's Practical to Extract and Report

Are You Sure You Want To Do That Which You Don't Understand? More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Design habit. (Score:1)

by clintp (2) on 2005.05.10 8:28 (#40289)

I know it's a design guideline for the Windows teams (long web page about this somewhere, can't find at the moment) that basically says: if the user won't understand the message and/or there's nothing they can do about it, there's no point in prompting them.

The discussion came out of the installer asking questions like "I've found a different version of FOO.DLL, would you like to replace it?". Grandma isn't going to understand that. Even someone with experience might not be sure how to answer that. (If I say yes, then I *might* break existing packages. If I say no, the package I'm installing surely won't work. WhatdoIdo?)

Around here, I'm all for little-or-no prompting just keep good records of what happened.

Reply to This

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.