To read all comments associated with this story, please click here.
That's a *good* thing.
Office does whatever it wants, and the Windows team follows.
Generally, Office implements their UI, ignoring Windows "guidelines", then widgets based on Office UI make their way to 3rd party dev tools and Visual Studio, and eventually those become standard widgets in Windows. For example, that's what happened with Office97's command bars (allowed for detachable menus, "flat" toolbars, and whatnot). Office hasn't used standard menus for years (since Office97).
There's already 3rd pary libraries implementing the Office 2007 "Ribbon" (well, they're *trying* to, anyway). I'm sure the Ribbon will become a standard Windows widget in the future.
As for Office 2007 removing the nonclient area and rolling their own, more power to 'em! They know more about UI than the Windows team does. Other apps can roll their own UI as well, but most don't have the talent and/or will to do so.
We'll see more of this with WPF; it seems to encourage "non-standard" UI; basically standards go out the window. This will lead to garish UIs at the beginning before things settle down (like what happened when VB 1.0 was released).




Member since:
2005-10-01
I loved this:
It's like an old joke that never tires me.
Q:
So how does Office maintain glass while also drawing over the glass, e.g. titlebar text and the round Office button? And even arbitrary buttons in their quick access toolbar?
...
A:
Office completely removes the non-client area, and renders everything in its client area, so it doesn't have a caption (except a fake one).
Notice how the glow and the text are different, it's because they're not rendered by the DWM.
The ancient tradition of having a nominally standard GUI, but their own major application suite doing things its own way lives on!