ArticleslgStudy

science

Shadow (OS/2)

Shadow (OS/2) is a science topic covered in the lgStudy science library. This page brings together a partial reference excerpt, illustrations, worked examples, real-world applications and a short study plan, so you can understand Shadow (OS/2) rather than just read about it. In short: In the graphical Workplace Shell (WPS) of the OS/2 operating system, a shadow is an object that represents another object. A shadow is a stand-in for any other object on the desktop, such as a document, an application, a folder, a hard disk, a network share or removable medium, or a printer.

Key takeaways

  • Shadow (OS/2) belongs to science; place it in that map before memorising details.
  • Learn the definition first, then one example that makes the definition concrete.
  • Connect Shadow (OS/2) to a quantity you can measure, compute or draw — that is where exam questions come from.
  • Reproduce the core statement of Shadow (OS/2) from memory before moving on to harder problems.

Reference excerpt

In the graphical Workplace Shell (WPS) of the OS/2 operating system, a shadow is an object that represents another object. A shadow is a stand-in for any other object on the desktop, such as a document, an application, a folder, a hard disk, a network share or removable medium, or a printer. A target object can have an arbitrary number of shadows. When double-clicked, the desktop acts the same way as if the original object had been double-clicked. The shadow's context menu is the same as the target object's context menu, with the addition of an "Original" sub-menu, that allows the location of, and explicit operation upon, the original object. A shadow is a dynamic reference to an object. The original may be moved to another place in the file system, without breaking the link. The WPS updates shadows of objects whenever the original target objects are renamed or moved. To do this, it requests notification from the operating system of all file rename operations. (Thus if a target filesystem object is renamed when the WPS is not running, the link between the shadow and the target object is broken.)

Similarities to and differences from other mechanisms Shadows are similar in operation to aliases in Mac OS, although there are some differences:

Shadows in the WPS are not filesystem objects, as aliases are. They are derived from the WPAbstract class, and thus their backing storage is the user INI file, not a file in the file system. Thus shadows are invisible to applications that do not use the WPS API. The WPS has no mechanism for re-connecting shadows when the link between them and the target object has been broken. (Although where the link has been broken because target objects are temporarily inaccessible, restarting the WPS after the target becomes accessible once more often restores the link.) Shadows are different from symbolic links and shortcuts because they are not filesystem objects, and because shadows are dynamically updated as target objects are moved. Shadows are different from hard links because unlike hard links they can cross volume boundaries and because their names are always the same as those of their target objects.

Distinguishing marks On (and within nested folders on) the WPS desktop, shadows' "icon titles" can be set to one's preferred font color, independently of the preferred font-color assigned to other non-shadow WPS objects, although they share the font actually selected for that text. Like the icons for all other 'open' objects on the WPS Desktop, whether for folders or applications, Shadows' icons become diagonally hatched on 'opening' and remain in that state until closed/exited respectively.

Managing shadows There are several ways to create a shadow. One way is to select the target object and choose "Create Shadow" from its context menu. The desktop then prompts with a dialogue box allowing the user to specify where the shadow should be created. Another way is to employ drag-and-drop to create shadows, holding down the shift and control modifier keys whilst dragging. The dialog box opens initially with a view of currently opened folders on the "Opened" Tab (page) of the dialog, first of which is the current Desktop folder, allowing direct selection of the destination. There are a further four tabs for "Related", "Desktop", "Drives" and "Path", this latter allowing textual path specification including drive (volume), whereas the other three options display an expandable hierarchical tree of folders to select from.

References

Worked examples

Example 1 — a first encounter with Shadow (OS/2)

Start with the simplest possible case. Write down what Shadow (OS/2) claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In science, the smallest case is usually a single object, a single equation or a single measurement. Check that every symbol or term in your sentence has a meaning in that case.

Example 2 — changing one variable

Take the situation from Example 1 and change exactly one quantity: double it, halve it, or set it to zero. Predict what should happen to Shadow (OS/2) before you calculate. Comparing your prediction with the result is the fastest way to find out whether you understand the idea or only the words.

Example 3 — an exam-style question

Typical questions about Shadow (OS/2) ask you to (a) state it precisely, (b) apply it to given data, and (c) explain a limitation. Practise writing all three answers in under five minutes; the third part is what separates a full-mark answer from an average one.

Applications of Shadow (OS/2)

In research
Shadow (OS/2) appears in science research whenever the underlying quantities have to be modelled precisely. Papers usually cite it as a starting assumption and then explore where it breaks down.
In technology and industry
Engineering practice reuses Shadow (OS/2) in design rules, simulations and safety margins. Knowing the idea lets you read a specification sheet and understand why the numbers look the way they do.
In the classroom
Shadow (OS/2) is common in secondary-school and first-year university syllabi. It links to neighbouring topics Legacy systems, OS/2, so understanding it makes those chapters shorter.
In everyday life
Look for Shadow (OS/2) outside the textbook — in sport, cooking, traffic, electronics or the sky above you. An example you found yourself is remembered far longer than one you were given.
Ask Teacher Smith questions about this articleOpens your AI tutor with a question about “Shadow (OS/2)” →

Affiliate

Preply — study more efficiently by working with a personal tutor. 50% off.

How to study Shadow (OS/2) in 20 minutes

  1. Read the reference excerpt below once, without taking notes.
  2. Close the page and write down what Shadow (OS/2) means in your own words.
  3. Compare your version with the excerpt and mark what you missed.
  4. Work through the three examples above with pen and paper.
  5. Explain Shadow (OS/2) out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is Shadow (OS/2) in simple terms?

In the graphical Workplace Shell (WPS) of the OS/2 operating system, a shadow is an object that represents another object. A shadow is a stand-in for any other object on the desktop, such as a document, an application, a folder, a hard disk, a network share or removable medium, or a printer.

Why does Shadow (OS/2) matter?

Because it connects several science ideas at once: it gives you a definition you can apply, a quantity you can calculate, and a way to check whether a result is plausible.

How should I study Shadow (OS/2)?

Read the excerpt, restate it from memory, then work through the examples and applications listed on this page. The five-step study plan above takes about twenty minutes.

What does this page cover?

It gives you a compact reference excerpt plus original lgStudy explanations, examples, applications and study material on Shadow (OS/2).

Tags

  • Legacy systems
  • OS/2

Keep exploring