[Techtalk] dah, what's transparent?

[Diggy Bell]

Ok, seriously now...

An application will generally have things that the user sees like a user
interface and reporting, but it may also have something else that goes on
'behind the scenes".  If we don't want the user to even know it exists, we
call it transparent.

I'm working on one particular project that integrates a PalmOS device with a
PHP-based web site.  I don't want the user to even be aware of the part of
the system that transfers the data between the server and the PalmOS device.
When I have to sit down and write the marketing documentation for the
product, I'll probably describe the synchronization/communication components
as transparent because the user won't even know they exist unless they read
the user manual.  (Do users really do that?)

----- Original Message ----- 
From: "ed orphan" <millward at Ms.UManitoba.CA>
To: <techtalk at linuxchix.org>
Sent: Tuesday, January 27, 2004 1:42 PM
Subject: [Techtalk] dah, what's transparent?


> When reading technical manuals and computer
> magazines, once in a while something is
> referred to as "transparent".
> "This process is transparent to the user."
> "It is essential that this code be transparent."
>    What are they talking about?
> Can you wrap sandwiches in it?
>
> _______________________________________________
> Techtalk mailing list
> Techtalk at linuxchix.org
> http://mailman.linuxchix.org/mailman/listinfo/techtalk
>
>