Did you ever write a .NET Windows service? What I really dislike about it is that though the framework provides the
System.ServiceProcess.ServiceInstaller class, you still have to use the external installutil tool.
Well, at least until today.
Why didn't Microsoft document that way? (Ok, they doc'd
TransactedInstaller, but if you don't know where to search... )
In Explorer, you can right-click the icon in the caption to get the context menu for the folder you are viewing. (Very handy for "Search" or "Command Prompt Here".) Apparently enough enough people realize this. In Windows 95, we tried to make it so most icons on the screen did something interesting when you right-clicked them.
However, I think the most important fact in the post is hidden in the second footnote:
Users being too busy is one of the basic rules of UI. Users aren't stupid, they aren't blind, they aren't incapable: they are just too busy to learn your UI. Humility is good for user experience.
- Users don't have the manual, and if they did, they wouldn't read it.
- In fact, users can't read anything, and if they could, they wouldn't want to.
I really recommend that book.
WinInformant says, that the PDC's Pre-Beta Longhorn supplied to the attendees will have the new GUI component Aero removed:
What developers will receive at the PDC, however, is very interesting. For the past several weeks, the software giant has forked the code for Longhorn, developing a special PDC build that is separate and distinct from the main code fork. This build will include virtually every Longhorn technology except Aero, and will include a new, darker theme that supplants the lackluster Plex visual style seen in alpha Longhorn builds. Microsoft is currently struggling to complete this special PDC build in time for the show, which will be held in late October.