Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Microsoft Vista User Interface Guidelines Published

Posted by Zonk on Sat Sep 23, 2006 12:56 AM
from the looks-better dept.
SEMW writes "Microsoft has published the preliminary Official User Interface Guidelines for Windows Vista. Highlights include Top 12 Rules for the Windows Vista User Experience — and the use of screenshots from Windows XP as examples of what not to do. The full guidelines are as yet incomplete, but what is there makes for interesting reading."
This discussion has been archived. No new comments can be posted.
Display Options Threshold:
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • Breaking your own rules (Score:3, Insightful)

    by Allicorn (175921) on Saturday September 23 2006, @01:00AM (#16165251)
    (http://www.peppermill-marketing.com/)
    So I guess we can take these rules as a fairly good indicator of what interface features the next version of Office will NOT follow. It's been my impression that whatever interface guidelines MS publish, they always seem to very rapidly diverge from them in the own applications.
  • Rule 11 (Score:1)

    by aedan (196243) on Saturday September 23 2006, @01:01AM (#16165259)
    (http://www.aedanmcg....ch/win_switcher.html)
    More than 10 and it's "Rule 11: Use notifications judiciously" which is a great change. Those things bug the hell out of me.

    What about "Everyone is called Bruce."?
    • Re:Rule 11 by Anonymous Coward (Score:1) Saturday September 23 2006, @02:18AM
    • Re:Rule 11 by commanderfoxtrot (Score:2) Saturday September 23 2006, @05:58AM
      • Re:Rule 11 by Fred_A (Score:2) Saturday September 23 2006, @06:01AM
    • Re:Rule 11 (Score:5, Funny)

      by UnknowingFool (672806) <minh_duong @ y a h o o .com> on Saturday September 23 2006, @09:02AM (#16166771)
      Use notifications judiciously" which is a great change

      But will MS follow their own rules? Hold on a sec . . .

      I see that you are posting a reply. Would you like me to open a search on MSN? <Yes><No> Clicks No

      Anyway, given the many complaints on Vista's security, it would seem MS isn't following their own rules--
      You are posting a remark disparaging Microsoft. Would you like to learn more about the great company Microsoft? <Yes><No> Clicks No

      While there maybe good reason to lock down Vista, you would think that MS would make it less annoying--
      You maybe posting information which may harm security. Would you like to continue to do so? <Yes><No> Clicks Yes

      You have insufficient privileges to post this reply. Please contact the network administrator for privileges.

      WTF? %$%#&@!
      [ Parent ]
    • Re:Rule 11 by andyatkinson (Score:1) Saturday September 23 2006, @10:56AM
    • Expando button by swankjesse (Score:1) Saturday September 23 2006, @01:07PM
  • This made me laugh. (Score:5, Funny)

    by radicalnerd (930674) on Saturday September 23 2006, @01:04AM (#16165267)
    Be polite, supportive, and encouraging. The user should never feel condescended to, blamed, or intimidated.
  • The Rules: (Score:5, Informative)

    by iluvcapra (782887) on Saturday September 23 2006, @01:08AM (#16165281)
    (http://www.soundepartment.com/)
    (emphasized elaborations mine)
    1. Use the Aero Theme and System Font (Segoe UI)
    2. Use common controls and common dialogs
    3. Use the standard window frame, use glass (transparency) judiciously
    4. Use icons and graphics consistent with the Windows Vista style and quality
    5. Use task dialogs for new or frequently used dialog boxes and error messages
    6. Use Aero Wizards
    7. Use Explorer-hosted, navigation-based user interfaces, provide a Back button
    8. Use the standard Windows Search (have a little iTunes style search box in your window's corner when appropriate)
    9. Use the Windows Vista tone in all UI text (use a professional writing style in you informative text)
    10. Clean up the user interface
    11. Use notifications judiciously
    12. Reserve development time for "fit and finish"!
    • Re:The Rules: (Score:5, Interesting)

      by iluvcapra (782887) on Saturday September 23 2006, @01:36AM (#16165387)
      (http://www.soundepartment.com/)

      My thoughts:

      Use the Aero Theme and System Font (Segoe UI)

      Good, but obvious.

      Use common controls and common dialogs

      ibid

      Use the standard window frame, use glass (transparency) judiciously

      Good good. If MS keeps making such a big deal about transparent UI tho, silly developers are gonna use it everywhere.

      Use icons and graphics consistent with the Windows Vista style and quality

      Good. If you follow this suggestion closely enough, maybe we can convince the users at home that your application comes from Microsoft, too.

      Use task dialogs for new or frequently used dialog boxes and error messages

      Good.

      Use Aero Wizards

      If you're replacing a 97 Wizard, you should use an Aero wizard. If you're writing a new app, please do not use a wizard. They're obnoxious, and send the message: "We didn't know how to organize your options in any sort of logical way, so here's a powerpoint that lets you fill in the blanks, masquearding as a UI."

      Use Explorer-hosted, navigation-based user interfaces, provide a Back button

      In short: Consider making programs that aren't web browsers behave like web browsers, since people use those alot. This is interesting, but at some point you have to explain the difference between the "Back" button and the "Undo" button, and you might just end up making your program into a wizard

      Use the standard Windows Search (have a little iTunes style search box in your window's corner when appropriate)

      A total dig on my part, and I apologize, but that's basically what they're saying. Apple makes the same recommendation, and give a very slick API for making it work. So good suggestion.

      Use the Windows Vista tone in all UI text (use a professional writing style in you informative text)

      From Microsofts mouth to ghod's ears.

      Clean up the user interface

      On their page they list all kinds of things you can do to make your program more ergonomic, but they put it at the end of the list, and phrase it in such a way as to suggest that it should be something you do at the end of development, as opposed to at the beginning, when you're designing your windows on a whiteboard. "Organize your command (sic) into a simple, predictable, and easy to find presentation" is something you do before you start writing code- it is not something you do while "cleaning up".

      Use notifications judiciously

      Or not at all. The list makes no suggestion about keeping your damn icons out of the systray.

      Reserve development time for "fit and finish"!

      Fit and Finish has quickly become my least favorite phrase. Sorry, just snarky, I agree with this point. But I would say "Hire a designer" as opposed to "reserve development time", mainly because it will allow collaboration with someone who always has their eyes on the UI and can give the developers continual feedback on how their code is totally rocking for the user ... experience, or totally deviating from reality.

      [ Parent ]
      • Re:The Rules: by adpsimpson (Score:3) Saturday September 23 2006, @04:07AM
        • 1 reply beneath your current threshold.
      • Re:The Rules: by Haeleth (Score:1) Saturday September 23 2006, @04:45AM
        • Re:The Rules: by grammar fascist (Score:2) Saturday September 23 2006, @05:49AM
          • Re:The Rules: by mabinogi (Score:2) Saturday September 23 2006, @07:00AM
        • Re:The Rules: by AaronLawrence (Score:2) Saturday September 23 2006, @09:04AM
        • Because... by DragonWriter (Score:2) Monday September 25 2006, @12:39PM
      • Re:The Rules: (Score:4, Insightful)

        by kestasjk (933987) on Saturday September 23 2006, @07:55AM (#16166517)
        (http://kestas.kuliukas.com/)
        If you're replacing a 97 Wizard, you should use an Aero wizard. If you're writing a new app, please do not use a wizard. They're obnoxious, and send the message: "We didn't know how to organize your options in any sort of logical way, so here's a powerpoint that lets you fill in the blanks, masquearding as a UI."

        Wizards are like many UI constructs; they are often abused but they can be very useful. Access data import Wizards, installation Wizards, Visual Studio database creation Wizards, etc.
        Whenever you need the user to enter a series of logically grouped options before you can begin to do what the user wants a Wizard is the way to go. It's either going to be a Wizard, or a large unwieldy dialog box.


        I think Microsoft's suggestions here are all good, but of course if you're the sort of developer that has to read them you're probably the sort of developer which doesn't care about the UI and won't implement them anyway. Which is a shame, because the UI can go a long way to make your program better.
        [ Parent ]
        • Re:The Rules: by waveclaw (Score:2) Saturday September 23 2006, @02:26PM
      • Re:The Rules: by nametaken (Score:2) Saturday September 23 2006, @05:22PM
        • Re:The Rules: by iluvcapra (Score:2) Sunday September 24 2006, @01:14AM
        • Re:The Rules: by iluvcapra (Score:2) Sunday September 24 2006, @01:17AM
      • Re:The Rules: by angulion (Score:1) Saturday September 23 2006, @06:37PM
      • Re:The Rules: by x-caiver (Score:2) Sunday September 24 2006, @03:09AM
      • 1 reply beneath your current threshold.
    • Re:The Rules: by Nic-o-demus (Score:2) Saturday September 23 2006, @03:23AM
    • Mmmm! marketing by doesnothingwell (Score:1) Saturday September 23 2006, @02:08PM
    • 2 replies beneath your current threshold.
  • Wow... (Score:5, Funny)

    by ResidntGeek (772730) on Saturday September 23 2006, @01:09AM (#16165287)
    That's a really bitching Notepad icon. They've clearly been hard at work.
    • Re:Wow... by nacturation (Score:2) Saturday September 23 2006, @02:36AM
  • Motivation (Score:1, Funny)

    by Lord Aurora (969557) on Saturday September 23 2006, @01:13AM (#16165303)
    FTFA:

    Reconsider using tree view controls. Trees are intended to organize data and make it easy to find, yet it's difficult to make data within a tree easily discoverable. Having hierarchically arranged data doesn't mean that you must use a tree view. Very often a list view is the better, simpler choice.

    They really did this because of the copyright issues [slashdot.org] concerning tree views...good old Microsoft. Always watching their ass. (^_~)

    • Re:Motivation by Spad (Score:2) Saturday September 23 2006, @01:36AM
      • 1 reply beneath your current threshold.
  • Guideline #1... (Score:4, Funny)

    by TheDarkener (198348) on Saturday September 23 2006, @01:14AM (#16165305)
    (http://youtube.com/thedarkener)
    "Keep the user guessing."
  • user Rule #1 (Score:5, Funny)

    by Quiet_Desperation (858215) on Saturday September 23 2006, @01:15AM (#16165309)
    Do not install Vista. :)
  • Lots of pointless rules... (Score:3, Insightful)

    by Bones3D_mac (324952) on Saturday September 23 2006, @01:19AM (#16165325)
    It seems these "guidelines" focus more on drawing attention to the user's choice of OS, rather than actually doing anything to productively assist the user in their work without becoming an annoyance in the process. Granted, a couple of these rules are borrowed from the original Apple Human Interface Guidelines, but the majority of them actually contradict the ideals Apple tried to enforce back in the early days of the Macintosh. (That's not to claim Apple has been any better about this in Mac OS X, which changes its look in every other major update.)

    If you thought Clippy was bad before, just wait until he *becomes* the OS that is Windows Vista.
  • Restart now? (Score:5, Funny)

    by DuranDuran (252246) on Saturday September 23 2006, @01:24AM (#16165351)
    > examples of what not to do

    Updates complete. Restart now?
    What about now?
    Now?
    Now?
    Now?
    Just wanted to know if I should restart now?
    What about now?
    Are you ready to restart?
    Shall I restart now?
    Should I not restart later?
    I think I should restart now.
    Wouldn't it be good if I restarted now?
    Who's up for a restart??
    • Re:Restart now? (Score:4, Informative)

      by PygmySurfer (442860) on Saturday September 23 2006, @01:36AM (#16165391)
      They actually added something semi-useful to that dialog - now, you can select when it updates you again, up to 4 hours later. It also doesn't seem to eventually force you to reboot like the XP one.
      [ Parent ]
      • Re:Restart now? by The MAZZTer (Score:2) Saturday September 23 2006, @02:06AM
      • 1 reply beneath your current threshold.
    • Re:Restart now? by uncommonlygood (Score:1) Saturday September 23 2006, @03:04AM
    • Re:Restart now? by Tim C (Score:2) Saturday September 23 2006, @05:44AM
    • Re:Restart now? by Prof.Phreak (Score:2) Saturday September 23 2006, @11:27AM
    • Re:Restart now? by loraksus (Score:2) Saturday September 23 2006, @03:44PM
    • 1 reply beneath your current threshold.
  • To do it right... (Score:5, Insightful)

    by jcr (53032) <jcr@nospAM.idiom.com> on Saturday September 23 2006, @01:39AM (#16165409)
    (Last Journal: Sunday November 05 2006, @05:31AM)
    Step One: write an app for the Mac.
    Step Two: get your UI reviewed by Apple's user interface evangelist, John Geleynse.
    Step Three: make all the changes recommended by Apple.
    Step Four: write a windows app that comes as close as you can get to your Mac version.

    Or, you can do what the people who wrote Visio or that guy who ripped off Delicious Library did, and just laboriously copy an existing app knowing that you'll never make it quite the same on Windows.

    -jcr
  • Thank You Microsoft! (Score:5, Interesting)

    by netsharc (195805) on Saturday September 23 2006, @01:51AM (#16165449)
    Put only program shortcuts on the Start menu. Never put shortcuts to the following on the Start menu:
    • Program uninstallers. Users access uninstallers through the Software Explorer control panel.
    • Help files. Users access Help topics directly from your program.
    • Control panels. Users access control panels from the Control Panel home page.
    • Program options. Users access program options from the Options command, usually found on the Tools menu.
    • Readme files. Reconsider the need for a Readme file because most users rarely look at them. If you do need a Readme file, let users access it from your setup program.
    • Web sites. Users access Web sites through appropriate links in your program. Exceptions are Microsoft Update and Windows Catalog.

    How I hate software that install all of that in their Start Menu entries. Or programs that insist they go into "C:\Program Files\My Stupid Software Company Inc\My Stupid Program".

    Talking about reform, I find the most illogical thing of user interfaces is the menubar.. how do you exit? Go to "File". Where are the options? Under "Tools".. why can't somebody offer a totally new way of making the menu. Start with "Program", where you have "Options" and "About" (maybe "Help" too), then "Document" or "File", and then "Edit", etc.. We're so used to File -> Exit that we stop thinking how illogical such a construct is... exit the file?
  • Integrity? (Score:4, Insightful)

    by medoc (90780) on Saturday September 23 2006, @02:01AM (#16165487)

    From the article:

    Perception is reality, and if your customers don't experience quality in your product throughout, they may conclude there is lack of quality everywhere. A visual bug seen by all your customers might do more damage to your program's reputation than a rarely occurring crashing bug.

    Mind your icons, not your buffer overflows. Great! Will exploits follow the Vista guidelines too ?

  • Two things catched my eye (Score:5, Insightful)

    by Sun (104778) <slashdot@sun.con ... l ['ume' in gap]> on Saturday September 23 2006, @02:07AM (#16165513)
    (http://www.lingnu.com/)
    The first - the design guidelines (10 out of the 12 listed) are focused on appearance rather than on functionality. Making sure your icons look great (#4) comes long before producing a clean interface (#10).

    The second is that this document carries a severe undertone of "make sure your app only works on Vista, and looks out of place on anything other than Aero". The entire document keeps saying "use Vista only API whenever you can" and "visually design the application to look out of place when not using the Vista UI" (with a few exceptions).

    I guess this is how MS are trying to fight the competition formed by previous OSes being good enough. They try to make sure new applications don't work on them any more.

    Shachar
  • Just wrapped it up tonight (Score:4, Insightful)

    by sporkme (983186) * on Saturday September 23 2006, @02:20AM (#16165557)
    (http://www.imwithfred.com/)
    Vista user experince... for crap. I spent the past couple of months testing this OS, and when my gaming XP boot feels like a safe haven, I know that something is definitely wrong. For migrating XP users, the interface feels counter-intuitive. Even more telling, my college-going roommate has only ever known Red Hat (thank you very much, he has only ever known linux on the front-room computer), and for him the simplest task, like installing Firefox (where's the package?) was torture (not to say there has been a change here). I became so frustrated with ctrl-esc,r yielding a "r" in the ever-so-laggy search sub-start dialogue (instead of a run window) tonight that I just blew out the whole partition. I actually wanted to run iexplore for once! I am downloading Mandrake 64 now, thank the creator.

    I found Vista to be too heavy on the eye candy, and it seemed that "power tools" and control panel received heavy design attention, while the ~deeper~ apps like regedit and msconfig are the same old barf. Vista = skinned XP != new OS. Meh. Shiny? Yes. New? No.
  • by NerveGas (168686) on Saturday September 23 2006, @02:31AM (#16165601)

    "For all controls, select the safest (to prevent loss of data or system access), most secure value by default."

    In other words, treat the user like they don't know what they're doing. Slow *everyone* down, in order to save the idiots.

    I really like knowing that when a dialog box pops up, the enter key will usually complete the task that I requested in the first place.

  • Boring (Score:1)

    by krajo (824554) on Saturday September 23 2006, @02:41AM (#16165623)
    Did anyone else feel that if everyone followed these rules, using the computer will become incredibly boring ?

    bye, krajo

    • Re:Boring by misleb (Score:2) Saturday September 23 2006, @03:43AM
      • Re:Boring by DragonWriter (Score:2) Monday September 25 2006, @12:15PM
    • Re:Boring by GaryPatterson (Score:2) Saturday September 23 2006, @07:07AM
  • Prime Directive... (Score:3, Funny)

    by creimer (824291) on Saturday September 23 2006, @02:42AM (#16165627)
    (http://www.creimer.ws/ | Last Journal: Friday January 26 2007, @12:40PM)
    Do no evil interface design... Oh, wait a minute, that's the Google guidelines.

    *cough*

    Evil interface design acceptable if you're writing an application, virus or spyware.
  • Self Help Document (Score:1)

    by aaronwormus (716976) on Saturday September 23 2006, @02:44AM (#16165631)
    The guidelines also double as a course in zen buddhism
    • Don't restart progress.
    • Omit the main instruction only if the only thing you can say is completely obvious.
    • Focus on efficient decision making. /ul
  • by pubjames (468013) on Saturday September 23 2006, @03:20AM (#16165733)
    Notice that in Rule 1, the word "aero" is not in the font they say you have to use...
  • Now if only they followed these "rules" themselves, Vista wouldn't be such a nauseating, gaudy, broken piece of shit.
  • by SanderDJ (1004445) on Saturday September 23 2006, @03:53AM (#16165843)
    That's a rule that MS has always followed.

    I myself have always looked for the button/menu to change this level to low. Haven't found it sofar. Will let you know when I do.

  • the best bit (Score:5, Funny)

    by joe 155 (937621) on Saturday September 23 2006, @04:03AM (#16165861)
    (Last Journal: Wednesday September 20 2006, @10:30AM)
    I just loved this bit;

    "# Focus on what users really need to know. Don't avoid important text--be explicit whenever necessary--but don't be redundant or verbose. Because users often scan text, make every word count. Simple, concise text not only saves screen space, it most effectively conveys an important idea or action.

    # Remove redundant text. Look for redundant text in window titles, main instructions, supplemental instructions, content areas, command links, and commit buttons. Generally, leave full text in instructions and interactive controls, and remove any redundancy from the other places.

    glad to see MS don't break their own rules!
  • by WWWWolf (2428) <wwwwolf@iki.fi> on Saturday September 23 2006, @04:04AM (#16165867)
    (http://www.iki.fi/wwwwolf/)

    "Present choices and settings in terms of user goals, not technology"

    ...and in the example, it turns "Enable Internet Connection Sharing Host" and "Manual duplex" to "Allow other network users to connect through this computer's Internet connection" and "Print on both sides of the paper".

    I agree on the principle, but it's funny how they chose both bad example and good example on how to use this rule.

    "Manual duplex" is a bad way of saying "Print on both sides of the paper", it doesn't mean much if you take it out of context (my first thoughts were "there's still modems where you need to switch sending and receiving manually?"). But the ICS example is just too simplified. It's hard to read. Imagine hunting for the ICS option from a huge dialog. You need to read a lot of these "easy explanation" options. Too many words. "Share this computer's Internet connection" would be better.

    The task-based language is okay, but in a lot of places in XP, I've found Microsoft is overdoing it and making the thing harder to use, rather than easier. Task descriptions just shouldn't get too wordy. If a longer explanation is needed, tooltips are there.

    Use the first person (I, me, my) to let users tell the program what to do.

    Ah, so Microsoft's stated goal of using my-spam is to create a friendlier atmosphere. I'm thinking they kind of succeed too well on that.

    Must... refrain... from... joking... MyComputerMyFilesMyDuploBricks! Arrrrggggh. Sorry.

  • Security First? (Score:1)

    by ph0enix (87965) on Saturday September 23 2006, @04:12AM (#16165893)
    "Scheduling time for a visual clean-up at pixel level, layout corrections (alignment, spacing), and other visual "fit and finish" is as important as it is to schedule time for bug fixing and other types of quality control.
    Nice to see that Microsoft is commited to putting security first; No, they've definately given up compromising security and stability for eyecandy and features. </SARCASM&gt
    • 1 reply beneath your current threshold.
  • Shneiderman's Eight Golden Rules (Score:3, Insightful)

    by Alioth (221270) <dyls@alioth.net> on Saturday September 23 2006, @04:44AM (#16165961)
    (http://www.alioth.net/ | Last Journal: Friday November 09, @03:53PM)
    Shneiderman's Eight Golden Rules for user interface design has been around for years (pre-dates Windows 3.x, in any case). Any UI designer should be conversant with these rules:

    http://www.cs.utexas.edu/users/almstrum/cs370/elvi sino/rules.html [utexas.edu]

    Am I the only one who doesn't want a "user experience"? If I'm getting an "experience", the damned user interface is getting in my way. I just want to get the job done, not have an "experience".
  • From TFA:
    "For programs that create or view documents, use the standard menu categories such as File, Edit, View, Tools, and Help." (part of rule 10).

    From the shell blog (posted to /. a few days a go):
    "However, menus can be used inappropriately - particularly when developers slavish follow the File/Edit/View//help pattern. These standard menus are really designed for document-based applications, where there is a lot of saving, printing, cutting, pasting, and window management going on."
    http://shellrevealed.com/blogs/shellblog/archive/2 006/09/20/What-happened-to-the-menu-bars_3F00_.asp x [shellrevealed.com]


    Bit of a contradiction there, but I can see the argument for both. 'File' has become the generic application menu, e.g. web browsers - which only deal with files in a limited way - have a file menu, so does basically any other app. It's just a badly named menu entry. As ever OS X gets this right (the first menu entry is named after the app).

    To be fair to MS, one is the official useability guidelines, the other is an informal blog, it's probably better than MS not allowing their staff to blog incase such contradictions come out.

  • by g051051 (71145) on Saturday September 23 2006, @05:49AM (#16166119)
    They could have saved a lot of typing by just linking to the Apple Human Interface Guidelines [apple.com].
  • A funny Vista UI picture. (Score:3, Informative)

    by master_p (608214) on Saturday September 23 2006, @05:52AM (#16166129)
    I found this:

    http://www.marcorolandi.com/imgs/just4fun.jpg [marcorolandi.com]

    I don't know if the meaning of word 'consistency' has been changed lately...do you?
  • by Burning Plastic (153446) on Saturday September 23 2006, @06:18AM (#16166215)
    (Last Journal: Thursday October 03 2002, @10:12AM)
    Ensure your user interface is CORRECTLY using the Windows Vista common controls (ComCtl32 v6). (my emphasis)

    Do the guys writing this understand English or do they just not care about writing coherent sentences / proofreading?
  • Yes/No dialogs again (Score:5, Insightful)

    by roskakori (447739) on Saturday September 23 2006, @06:45AM (#16166295)

    One of the worst misfeatures of Windows (and its developer community) is the retarded design of dialogs. AFAIK the pre-Vista API has a bunch a simple functions to do Yes/No and Ok/Cancel dialogs, but nothing to label buttons sensibly. So it's quite common to have a dialog with "Yes" and "No" buttons, and and huge text explaining what these options mean. Despite the fact that every at least semi-decent article or book about dialog design recommends to use verbs for button labels.

    I recently read [msdn.com] that Vista finally offers an API to easily change the button labels. Yeah! And guideline 5 (Use task dialogs for new or frequently used dialog boxes and error messages [microsoft.com]) specifically recommends:

    Use positive commit buttons that are specific responses to the main instruction instead of generic labels (such as "OK"). Users should be able to quickly grasp the options by reading the button text alone. Always start commit button labels with a verb.

    Yeah again!

    However, above this guideline we can see a screenshot of the classic, super retarded Windowesque "Save changes? Yes/No/Cancel" dialog.

    I suggest for the final document they just copy this dialog from any random Mac OS application and put a Vista theme on it.

  • I have one for Microsoft (Score:4, Insightful)

    by Greyfox (87712) on Saturday September 23 2006, @07:08AM (#16166351)
    (http://www.flying-rhenquest.net/)
    Don't let the application handle the window frame. Even their latest OS feels sluggish and unresponsive when retarded applications (Like Outlook) stop processing Window frame controls because they're syncing from the network or some other bullshit. I should always be able to move, minimize and close an application immediately no matter what that application is doing. This has been a pet peeve of mine ever since I was first exposed to Windows back in the 3.0 days. OS/2 actually had the threaded OS before Microsoft did and you could always tell the shoddy knock-off ports of Windows 3.1 software from the code that was actually written for OS/2 because proper OS/2 code at least made an effort to process events in threads, while the knock-off ports would hang the entire OS up when they stopped processing events to index disk and stuff and the system input queue filled up. At least Microsoft got that right and most of the time a misbehaving application will only lock up its own window.

    Now if an application were written properly this wouldn't be an issue -- the application would have a thread dedicated to UI work and in theory the interface should be highly responsive, but you're trusting all the application developers to implement their programs properly and not even Microsoft is capable of setting a good example. Their OS would almost not suck if they'd just fix this one design flaw and I'm going to keep blowing this horn until they do.

  • Still, they make the same error (Score:4, Informative)

    by tetrode (32267) on Saturday September 23 2006, @07:18AM (#16166363)
    (http://contact-centers.blogspot.com/)
    Their common dialog box is still yes no cancel. While gnome and kde (i think) has adopted a different and in my opinion far better strategy.

    People are afraid of doing things wrong. Especially at a computer, as they have learned that a computer is *VERY* unforgiving. Turn it off, and your document isn't saved, you get chkdsk errors, your operating system does not start, you have to pay your local guru big bucks or a bottle of wine to keep the damn thing running. Turn the TV off and on again and it all works. You need to treat the computer with respect. So you say (err - click) yes to it - all of the time.

    Do you want to save the document: Yes
    Do you want do delete the folder: Yes (o shit)
    Do you want to uninstall this application: Yes (where were these disks again)
    Do you want to format this disk: Yes

    Now, look at gnome. That interface is talking to you in a quite different way. When you close gedit (the notepad equivalent) without saving, it will tell you

              Do you want to save the document 'xyz'
              If you don't save it, your changes of the last n seconds will be lost

              [Don't Save] [Cancel] [Save]

    Now that is informative, and i really have to make a meaningful choice. I need to choose between Save and Don't Save. Or I pick cancel which will surely take me back to the previous state.

    Much better than the windows common control, which has been devised in Windows 2.0 (I kid you not) and still in Windows fscking Vista, noone has had the courage to reread 'About Face' and reshape it.

    Sigh

    Mark
  • by Tsu Dho Nimh (663417) <<abacaxi> <at> <hotmail.com>> on Saturday September 23 2006, @07:20AM (#16166369)
    So ... three months before plnned release, they FINALLY get around to releasing guidelines. And they are going to whine when nobody's software complies.

    And they aren't even the final version.

  • Here's one for everyone, including Apple:

    Be consistent in the use of the UI:
      - Apple screwed up badly in recent times, with having a mixture of Aqua, Metal, new Aqua and whatever else.
      - Microsoft also screwed up in Windows XP with having a mixture of different open dialogs, for essentially doing the same thing.

  • Present choices * and settings in terms of user goals, not technology. Use everyday words when you can. This is especially
    effective if you are explaining a complex technical concept or action. Imagine you are looking over the user's shoulder and explaining how to accomplish the task.

    Technology-based:
    * Enable Internet Connection Sharing host
    * Manual Duplex

    Goal-based:
    * Allow other network users to connect through this computer's Internet connection.
    * Print on both sides of the paper.


    This tendancy annoys me more and more with ever release of Windows, for many reasons:
    1) Most everybody knows what "duplex" means. Why not let those who don't learn what it means instead of pretending the word doesn't exist, and encouraging people to forget.
    2) When I am on the phone with a user, I can say "look for the options that says something like "Internet Connection Sharing". Most users will not find the goal-based option, as it does not include the word "sharing".
    3) I know what I'm looking for. I know what it was called in NT4, 2000, and 2003 server. Now I have to read paragraphs and guess that "Allow other network users to connect through this computer's Internet connection" is Internet Connection Sharing and not Web Proxy.
    4) It encourages the user to not learn about the very complex piece of equipment he just bought. If you provide a good searchable manual instead of dumbing everything down, the program will be easier to use, and the user will learn more.

    Imagine if your grill didn't say "Ignite" above the red button, but "Make the fire start", or if your toaster didn't say "Toast", but "Make your bread crispy", or if your car didn't say "ABS", but "Automatically remove and reapply pressure on the brake so your car doesn't skid. Don't pump your brakes".

    This is slashdot, so I need to reference either Orwell or Rand:
    Or are they trying to reduce English to a smaller set of simple words that everybody can understand? Double-plus ungood.
  • LMAO, DRM Etiquette (Score:1, Troll)

    by twitter (104583) on Saturday September 23 2006, @10:46AM (#16167477)
    (http://lists.clickers.org/linuxsig/index.html | Last Journal: Friday November 09, @11:00PM)
    from what not to do,

    Be polite, supportive, and encouraging. The user should never feel condescended to, blamed, or intimidated.
    Acceptable: Cannot delete New Text Document: Access is denied.
    Better: This file is protected and cannot be deleted without specific permission.

    There you go, you need to be polite and supportive when you tell the user they can't do what they want to do. Instructions won't do any good because there is no way to get the thing done. The user then only has to remember the sounds of crashing chairs and "I'm going to fucking kill Google! I've done it before and I'm going to do it again."

    Don't foreget that when your computer is really slow, pops up images of American Express Cards and naked ladies at random, it's all your fault, you stupid little shit, you visited the wrong site and downloaded things you should not have. Please don't feel condescended to, blamed, or intimidated as company representatives tell you this over and over.

    What a bunch of double talk.

  • so can (Score:1)

    by marafa (745042) on Saturday September 23 2006, @11:04AM (#16167613)
    (http://www.in-egypt.net/ | Last Journal: Wednesday January 31 2007, @09:10AM)
    so can those working on the portland project read this disclosure or will that compromise the Gnu/Linux User Interface project?
  • by Monte (48723) on Saturday September 23 2006, @11:22AM (#16167763)
    After reading the guidelines I got the distinct impression that they were trying to instill Vista with Genuine People Personality(tm).

    "Happy Service!"
  • Rule 9 (Score:1)

    by consumer_whore (652448) on Saturday September 23 2006, @11:28AM (#16167815)
    I like how Microsoft is telling us not to be arrogant.
  • by Carcass666 (539381) on Saturday September 23 2006, @12:36PM (#16168249)

    I wish Microsoft would expand the scope of the article to not only how to write applications to leverage the "Vista experience", but also to author your applications so that they will properly levergage any updates to standard libraries (current and forthcoming) so that if your applications is loaded onto Windows 2K, XP or Vista; the user will have a consistent experience.

    In Microsoft's view of the world, all corporations will update to Vista the day after it is released. In reality, many are still running "legacy" OS's. Letting us know which standard libraries, fonts, etc. will be propogated to older OS's that are still in use will help developers create applications that an organization can deploy without fear of incompatibility.

    One example is the new Aero wizard. Will versions of this control be available on XP/2K? Or are we supposed to build different versions of an app for different OS's? (disclaimer, I have not yet done any research on this, so if this is a poor example, appologies in advance)

  • Icon problem (Score:1)

    by ignivs (1004743) on Saturday September 23 2006, @12:47PM (#16168349)

    Select icons based on meaning, not appearance. Make sure that your icons have consistent meaning throughout your application and don't conflict with existing icons or conventions in the system, or in other commonly used Windows-based applications.

    Please MS. folk, read this and switch IE incon for any kind of bug... a fly fits perfectly!!!
  • by ffejie (779512) on Saturday September 23 2006, @01:38PM (#16168745)

    Finally, they're taking aim at something I despise on Windows XP.

    "Create a product folder if your product is a collection of individual programs (three or more), and users think of your product in terms of that collection. Use only a single-level folder for this purpose."

    I hate when applications make trees to put one program into it. Useless! Now we just need the designers to follow this spec.

  • by KIFulgore (972701) on Saturday September 23 2006, @01:40PM (#16168759)
    "Don't use notifications for feature advertisements!"

    Clippit, anyone?
  • Links don't take access keys. Links are accessed with the Tab key. Traditionally, hyperlinks are underlined, so the access keys aren't visible, and often there are too many links on a page for access keys to have any value. Exception: Command links take access keys and have a default selection state. While command links look like links, they behave like command buttons.

    Say, what?
  • Good guidelines (Score:1)

    by doni77 (989316) on Sunday September 24 2006, @06:42AM (#16173819)
    I just don't see Windows (ui) developers to change some of their habits. Using standard UI components is often seen boring and restricting. And so sacrificed to make some cool(?) interface like Winamp, ICQ ect. "Look at all the tricks I can code" often overshadows all these fancy guidelines. At least for small scale freeware/shareware software.
  • Re:Lovely (Score:2)

    yeah, it's hilarious that pretty much everyone of these rules, XP violates in hideous ways, from the annoying 'notifications' on down.

    i'm wary that they are encouraging developers to pop up yet more of these stupid balloon notification messages though...they're annoying enough in XP, can't wait until every 2 seconds you have a balloon popping up asking one thing or another.

    the other hilarious thing is microsoft trying to tell people what 'cool' is in respect to application design. yikes
    [ Parent ]
  • Re:Media player (Score:3)

    by westlake (615356) on Saturday September 23 2006, @12:28PM (#16168211)
    For example, Windows Media Player is a core user experience, whereas Sound Recorder is not.

    let me know when you find a linux distro for home users where media play is not part of the core experience

    [ Parent ]
    • 1 reply beneath your current threshold.
  • Re:Any They Missed (Score:2)

    by Guy Harris (3803) <guy@alum.mit.edu> on Sunday September 24 2006, @05:33AM (#16173593)
    Mine is Dont have selection boxes with just yes no and canel on them, make them more informative such as is in linux, ie Save File and Discard, Don't Close and Save.

    ...which was, I think, recommended by Apple [apple.com] before being popular on other systems. (See "Buttons for addressing the alert".)

    Of course, "on Linux" in this context really means "in GNOME" or "in KDE" or ..... The GNOME Human Interface Guidelines [gnome.org] make the same suggestion about button labels [gnome.org], which I think they took from the OS X HIG. The KDE HIG [kde.org] also suggests buttons with verbs. I don't know what other DEs or toolkits recommend (if anything) or support.

    Then again, even one of Microsoft's HIGs [microsoft.com] suggests that, albeit not as strongly (look for "Dialog Box Commands"). For that matter, so does the Vista HIG [microsoft.com] (look for "Use positive commit buttons").

    [ Parent ]
  • Re:Any They Missed (Score:1)

    by tehcyder (746570) on Monday September 25 2006, @09:25AM (#16184869)
    (Last Journal: Wednesday February 25 2004, @11:29AM)
    Save File and Discard, Don't Close and Save
    Well, the third one's clear enough, I'll give you that.
    [ Parent ]
  • 13 replies beneath your current threshold.