|
|
|
|
|
|
|
|
|
|
|
|
|
|
GETTING HELP
Creating context sensitive field help with dialog boxes
By Chris Doig
How many times have you been clueless when completing a field on a form? You clicked on a pick list or combo box and were faced with an almost meaningless list of choices. The unsaid things that were so obvious when the program was created have been forgotten. While this gets embarrassing when you're the program author, the real problem is that the context has been lost. You feel a bit like Bill Gates when those ancient emails were resurrected in court. What was unsaid and forgotten (i.e., the context) was just as important a part of the communication as that which was said.
The usual solution to this problem is context sensitive field help. Developer tools for writing user help in Notes have improved over the years, but field help is still pretty dismal. While the main advantage of Notes field help is that it's tied programmatically to the field, it has several problems:
- You often need a lot more space than the 70 characters that field help provides. If you write multilingual applications, you're advised to limit this to 55 characters;
- The user might have field help turned off;
- Even if field help is turned on, the user might not notice it because there's no visual connection with the field;
- If you use a computed field with, say, a button to set the field values, the user can't get at the field help;
- Field help doesn't work on the Web.
In this article, we'll explore the idea of using dialog boxes to solve the context sensitive field help problem in the Notes client. I'll show some examples to give you an idea from the usability perspective. Then I'll show you how to construct a help form and the code used to call it. Along the way, we'll cover design techniques and conclude with a few ideas for enhancements.
Pros and cons
The help dialog approach has several powerful advantages, but, like most things in Notes, there are significant trade-offs. One of the first things you'll notice is that dialog boxes are modal, which means the user can't complete the form with the dialog box open. To solve this, we use the fact that a dialog box opens the current document with a different form. So you can put the actual document field on the help form, right next to your explanation. This really holds the context together. The user opens the help, completes the field, and presses OK. Then the user is returned to the main document with the field updated.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
-- Advertisement --
Navigate the Document 'SharOllaboraGement' Universe
More than 60% of organizations are dealing with 'Content Chaos' -- Out of control Documents and Content.
Unfortunately, over 50% of those will rush into the wrong solution and ultimately fail.
The Document & Content Management Decision Matrix is a free tool for navigating the broad 'Document Sharing, Collaboration and Management' technology universe.
Use it to help you make the right decision based on your organizational preferences and needs.
Tap to download this complementary tool. |
-- Advertisement --
Want the top Lotus experts by your side without paying hefty consulting fees?
Look no further.
Like having a team of consultants by your side -- ones who have all the answers and never make mistakes -- THE VIEW gives you immediate access to field-tested instruction, guidance, and best practices from the brightest Lotus professionals around.
See the new instruction, advice, and best practices added to THE VIEW this week. |
|
|
|
|
|
|
|
|
|
|
