Think of Tiger’s new Dashboard feature as a constantly running pseudo-application. It is constantly running in the sense that you cannot quit it; it is a pseudo-application in the sense that it isn’t a distinct process (it’s really an aspect of the Dock) and in the sense that (like the Dock) it behaves differently from any other application.
Dashboard is always in one of two states. When it isn’t the frontmost application, it is invisible and inert. When it is the frontmost application – you can summon it either by pressing a user-configurable keyboard shortcut (F12 by default) or by clicking its Dock icon – it takes over the entire screen, covering all windows, the Desktop, and the menu bar with a dark haze, rather like London in a Sherlock Holmes episode. Gleaming in front of this haze are some roughly rectangular areas of bright color: these are the Widgets to which Dashboard plays host. All you can do when Dashboard is frontmost is interact with a Widget – look at one, drag one around, click one. All the while, your other applications remain active in the background. When you’re done using Dashboard, you click somewhere in the haze, and it and all the Widgets vanish, and you can proceed to use your computer in the normal way.
Your installed Widgets constitute a smorgasbord from which to choose; which ones actually appear when you summon Dashboard is up to you. You click a big "+" at the lower left of the screen to reveal the Widget Bar; it displays icons for all your installed Widgets, and you click or drag an icon to instantiate it in the Dashboard main area. Similarly, when the Widget Bar is showing, Widgets in the main area have an "x" that you can click to dismiss them (and when the Widget Bar is not visible, you can reveal a Widget’s "x" by holding the Option key and hovering the mouse pointer over that Widget). It is legal and useful to instantiate a particular Widget more than once. For example, the Clock widget shows a clock set to a specific time zone, so to show the time in, say, both Los Angeles and Indianapolis, you instantiate the Clock widget twice, and set one instance to Pacific Time and the other instance to, uh, whatever weird time zone they think they’re in in Indianapolis.
The Dashboard architecture – where either Dashboard is absent and you can’t work in it at all, or else it is frontmost and you can’t work anywhere else – may seem rather restrictive, especially in comparison to Konfabulator, which permits its Widgets to be interleaved with ordinary application windows. However, it all makes more sense if you think of a Dashboard Widget as something you glance at, or work with for a just a moment, and then dismiss. If you always need to see a clock, use the System Preferences (Date & Time) clock. If you need to glance at a clock now and then and then get back to work, use the Dashboard clock. From this perspective, users may well be pleased that when Dashboard is not frontmost, its widgets occupy no screen real estate (like a window), no Dock slot (like an application), no menu bar space (like a status menu), and no CPU time. On the other hand, the single-layer architecture decidedly favors user with big monitors; my 12-inch iBook feels crowded when just half a dozen Widgets are present.