Re: "Transparent to the User"

Subject: Re: "Transparent to the User"
From: Susan W. Gallagher <sgallagher5 -at- cox -dot- net>
To: "TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Thu, 7 Apr 2005 12:34:36 -0400

I know I come into the game from the techie side rather than
the end-user side, so I tend to see things a little differently.

To me a "transparent" task is one that the user can see
through - that it does not get in the way of the task at

If I told a developer that a process was "transparent to
the user", I would be saying that the process could be
implemented without inconveniencing the user or taking time
away from the user's primary task.

Makes perfect sense to me. But I guess that's because I'm

-Sue Gallagher
> From: tech -dot- writer1 -at- verizon -dot- net

> I have come across this phrase in a system description I am editing: "The
> creation of index files is transparent to the user."


Accelerate the document lifecycle with full online discussions and unique feedback-management capabilities. Unlimited, efficient reviews for Word
and FrameMaker authors. Live, online demo:

You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit for more resources and info.

Previous by Author: Re: Re: Exempt vs. Non-Exempt
Next by Author: Re: writing an SDK
Previous by Thread: Re: "Transparent to the User"
Next by Thread: RE: "Transparent to the User"

What this post helpful? Share it with friends and colleagues:

Sponsored Ads