Windows Vista Sidebar Gadgets and the Temperature-Converter Gadget, Explained

One of the friendliest ideas Windows Vista shipped in 2007 was the Windows Sidebar and its desktop gadgets — a strip of tiny, single-purpose tools that lived at the edge of your screen. A gadget did one thing well: showed the time, the weather, a stock ticker, your notes, a feed of headlines, or a quick unit conversion. The temperature-converter gadget that this page grew out of belonged to that last group: type a number, get the same temperature in the other scale, without opening anything else. This guide explains what the Sidebar and gadgets were, how a gadget like the temperature converter was put together, how you added and removed them, and what became of the whole platform on modern Windows.

What the Windows Sidebar was

The Windows Sidebar was a vertical pane, docked by default to one edge of the Vista desktop, that hosted small mini-applications called gadgets. Each gadget was effectively a little web page: it was built from the same technologies as any website of the era — HTML, CSS and JavaScript — and rendered by the Windows web engine rather than compiled as a traditional desktop program. That is why gadgets were so easy to make and share: if you could build a small web widget, you could build a gadget.

Windows shipped with a set of built-in gadgets that most Vista users will remember: a clock, a weather panel, a calendar, a slide show of pictures, a CPU/RAM meter, a currency converter, a notes pad, a contacts panel, and a feed headlines reader for RSS. Beyond the built-ins, anyone could write and distribute their own, and a large community of hobbyist gadgets sprang up — unit converters, system monitors, search boxes, countdown timers and countless novelty widgets among them.

Gadgets did not have to stay in the Sidebar. You could drag one out onto the open desktop, where it floated on its own; some had a compact "docked" look in the Sidebar and a larger "undocked" view with more detail when pulled out. In Windows 7 that flexibility went further — the fixed Sidebar pane was dropped and gadgets simply lived anywhere on the desktop — but the underlying gadget format carried over.

The temperature-converter gadget

A temperature-converter gadget did exactly what the name promises: it turned a temperature you typed into the same temperature on the other scale — Fahrenheit to Celsius and Celsius to Fahrenheit — right there on the desktop. Instead of reaching for a search engine or a calculator, you glanced at the Sidebar, typed a number, and read the answer.

The original Windows Now gadget that this page expands worked with a simple keyboard flow. You typed a value into the gadget and then pressed a key to convert it:

• To convert Fahrenheit to Celsius, you typed the value in and pressed Shift-Tab.
• To convert Celsius to Fahrenheit, you typed the value in and pressed Tab.

The author also noted at the time that a follow-up version was in the works to add different visual styles and live updating of the fields as you typed — the way the built-in currency gadget recalculated on the fly — rather than requiring a key press. That is a good illustration of how gadgets evolved: because they were just small bundles of HTML and script, an author could iterate quickly and re-share an improved build.

The maths behind such a gadget is trivial and worth stating plainly, because it is the entire "engine" of the tool. Celsius from Fahrenheit is C = (F − 32) × 5 / 9; Fahrenheit from Celsius is F = (C × 9 / 5) + 32. Everything else in a converter gadget is presentation: an input field, a place to show the result, and a little script to run one of those two formulas when you act.

How a gadget was structured

A gadget was distributed as a single file with a .gadget extension. That file was really a compressed archive — a normal ZIP package under a different name — and inside it was an ordinary folder of files. In broad terms a gadget package contained:

• an HTML file that defined the gadget's interface and layout — for a temperature converter, the input box and the result display;
• a manifest file that had to be named gadget.xml, holding the gadget's metadata — a root <gadget> element wrapping children such as <name>, <version>, <author> and <description>, while the HTML file that provided the interface was declared by a <base> element (with type="HTML" and a src attribute) inside the <hosts> / <host> section;
• scripts — the JavaScript that did the actual work, such as running the conversion formula when you pressed a key;
• images and styles — the icon shown in the gadget picker, plus any background art, CSS and other assets the interface referenced.

Because the pieces were plain web files in a plain folder, building or inspecting a gadget was approachable: you could unzip a .gadget, open the HTML and script in any text editor, and see exactly how it worked. That openness was a big part of the appeal — and, as it turned out, part of the security problem discussed below.

Adding and removing gadgets

Installing a gadget you had downloaded was as simple as double-clicking the .gadget file. Windows would ask you to confirm that you wanted to install and run it, then add it to your available gadgets and place it on the Sidebar or desktop.

To add a gadget that was already available on the system, you opened the gadget picker — by right-clicking the Sidebar or an empty part of the desktop and choosing the option to add gadgets, which opened a gallery of installed gadgets — and then dragged the one you wanted onto the Sidebar, or double-clicked it. Many gadgets exposed a small options or wrench control when you hovered over them, so you could configure things like units, refresh interval or appearance.

Removing a gadget from view was equally direct: you hovered over it and clicked the close button that appeared, which took it off the Sidebar or desktop without deleting the underlying gadget from your machine. To remove a gadget entirely you used the gadget gallery's uninstall option so it was no longer offered at all. None of this required editing the registry or touching system settings for everyday use.

What happened to gadgets

The gadget platform did not survive the transition to modern Windows, and the reason was security. Each gadget ran as local HTML and script with the privileges of the signed-in user, and there was limited isolation between a gadget and the rest of the system. A malicious or compromised gadget — or a legitimate one with an exploitable flaw — could therefore be abused to run code on the machine. Microsoft ultimately advised users to disable the Sidebar and gadgets on Windows Vista and Windows 7, and the feature was removed from Windows starting with Windows 8. Later versions of Windows shipped with no built-in gadget platform at all.

The idea of glanceable desktop widgets came back, though, in safer forms. Windows 11 introduced a dedicated Widgets board — a panel of cards for weather, news, calendar and similar information — that runs inside a maintained, sandboxed framework rather than as loose local files. More broadly, installable web apps (progressive web apps) now let a small, single-purpose tool live on your desktop or taskbar while running in the browser's security sandbox. A temperature converter today would most naturally be a web app or a widget card, not a downloadable .gadget — but the goal is the same one the Vista Sidebar had: a small, focused helper a glance away from your desktop.

Why this old post still matters

Little tools like the temperature-converter gadget are a good snapshot of an optimistic moment in Windows history, when the desktop was opening up to lightweight, web-built add-ons that anyone could make and pass around. The platform is gone, but the pattern it pioneered — tiny widgets built from web technology, sitting at the edge of your screen — is very much alive in Windows 11's widgets and in web apps. Understanding how the original gadgets were packaged and installed makes it easy to see both the appeal that made them popular and the security thinking that eventually replaced them.