RE: [External] : Re: Would you say this information window is well designed?

[Stefan Kangas]

Drew Adams <drew.adams@oracle.com> writes:

> In the design I use (one example; I don't claim
> there is no better approach):
>
> * A user can choose to never provide such links.
>
> * Otherwise:
>
>   . If a user doesn't want to pay a time penalty
>     of finding out beforehand whether a given
>     symbol is actually covered in (some set of)
>     manuals (the set being decidable by the user),
>     the action of the link is called out as
>     _checking_ for the symbol in the manuals.
>     IOW, the link is, in effect, a _search_ link.
>
>   . If a user wants to pay a penalty of checking
>     beforehand, a link is created only if a target
>     is known.

That sounds like a reasonable way to work around the performance impact.

Another way to solve this is to remove the performance impact.  Then the
user don't have to make any choice: the link is shown when its relevant.

(We could still make showing the link optional, of course, if we think
some users will want to disable it.)