TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
When I think of something being transparent to the user, I think of it
as an operation that may be necessary for the user to complete other
tasks and it happens without the user's knowledge or intervention.
>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 weird.
WEBWORKS FINALDRAFT - EDIT AND REVIEW, REDEFINED
Accelerate the document lifecycle with full online discussions and unique feedback-management capabilities. Unlimited, efficient reviews for Word
and FrameMaker authors. Live, online demo: http://www.webworks.com/techwr-l
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 http://www.techwr-l.com/techwhirl/ for more resources and info.