Apple's Dashboard is often compared to Konfabulator, but with the wealth of widgets that suck things off the Internet, it strikes me that it could also be seen as Pointcast done right or, perhaps more accurately, Windows Active Desktop reborn: compare and contrast.
I don't have any direct experience of Active Desktop, but Dashboard already seems to be generating more excitement than it did. What's the difference? Is it just that Internet bandwidth is cheaper and more people have an always-on connection now (people mostly used PointCast at work and HR often had to ban it because it hogged office bandwidth), or is it a GUI difference (maybe the simple fact that all the widgets live in a separate layer and go away when you don't need them) or ease of development? These people have been discussing this...
Having used Dashboard for a while, I think a key thing (actually shared by most predecessors) is that, dumb old Wired articles notwithstanding, it doesn't try to replace the browser. You can't do that much with a widget, nor would you want to. It's simple enough, and the Dashboard layer is unobtrusive enough, that you can just keep it up there all the time.
The good ones seem to be divided into two categories: widgets that just display some information with no regular user interaction, and widgets on the Dictionary model that have a search bar and a little display that windowshades down (often with a button to get more information in your Web browser if you need it). The third-party widgets that are nothing but a search bar that opens Safari seem less useful. If I just want to open a web page in Safari I'm not going to bring up the Dashboard first; I'll just put a bookmark in Safari.
I don't have any direct experience of Active Desktop, but Dashboard already seems to be generating more excitement than it did. What's the difference? Is it just that Internet bandwidth is cheaper and more people have an always-on connection now (people mostly used PointCast at work and HR often had to ban it because it hogged office bandwidth), or is it a GUI difference (maybe the simple fact that all the widgets live in a separate layer and go away when you don't need them) or ease of development? These people have been discussing this...
Having used Dashboard for a while, I think a key thing (actually shared by most predecessors) is that, dumb old Wired articles notwithstanding, it doesn't try to replace the browser. You can't do that much with a widget, nor would you want to. It's simple enough, and the Dashboard layer is unobtrusive enough, that you can just keep it up there all the time.
The good ones seem to be divided into two categories: widgets that just display some information with no regular user interaction, and widgets on the Dictionary model that have a search bar and a little display that windowshades down (often with a button to get more information in your Web browser if you need it). The third-party widgets that are nothing but a search bar that opens Safari seem less useful. If I just want to open a web page in Safari I'm not going to bring up the Dashboard first; I'll just put a bookmark in Safari.