Slashdot Mirror


Apple Explains Interface Differences

WCityMike writes "This switch document for developers details the interface differences between Microsoft Windows and the Aqua interface used in Mac OS X. Written on a layman's level, it actually makes for pretty interesting reading!"

764 comments

  1. That's simple. by decaheximal · · Score: 3, Funny
    ...details the interface differences between Microsoft Windows and the Aqua interface used in Mac OS X. Written on a layman's level, it actually makes for pretty interesting reading!
    That's simple. Explorer.exe. Oh, on a layman's level? "Your internet won't break," basically.
  2. Aqua by Anonymous Coward · · Score: 0

    Aqua, Darwin, Cocoa, what's the difference?
    Give me Gnome any day.

    1. Re:Aqua by Anonymous Coward · · Score: 0

      aqua => the look and feel of OS X's window manager
      darwin => apple's fork of FreeBSD
      cocoa => an object-oriented API to GUI features

  3. the part about the dialog box is wrong by Anonymous Coward · · Score: 0

    the Windows dialog box looks much better because it is not thrown together into a tight space. You should attempt to use two widgets with 4 pixels between them and 50-80 pixels betwen them. big difference. Every part of Windows UI was under heavy research and it was proven that this layout is better than any other one, including the tight Mac OS X layout.

    1. Re:the part about the dialog box is wrong by Jeremy+Erwin · · Score: 1, Troll

      heavy research. proven. better. These words imply that you have citations to provide. Provide them.

    2. Re:the part about the dialog box is wrong by Tub-o-Guts · · Score: 3, Insightful

      UI research is precisely the kind of thing Microsoft thought was a waste of money until a couple years ago. Apple did alot of the basic research on usability throughout the 80's and 90's. Microsoft did not. They have turned that around and are spending on research in a big way now, but to say that a UI is tested and usable simply because it is running under Windows is a bit of a stretch. Some Windows apps are great, but the Windows universe of apps sorely lacks consistency.

      --
      "I don't mind the swelling, it's the itching I could do without."
    3. Re:the part about the dialog box is wrong by mad+flyer · · Score: 0, Flamebait

      Yes it was proven too that we need your mother to finish you... it was proven it was proven well fine ... how and when give us facts instead of rethoric to impress pompom girls...

    4. Re:the part about the dialog box is wrong by SampleMinded · · Score: 1

      The Windows version is better, but not for your stupid reasons. First look at the tabs, like the dock the dumb-asses but them in the center, breaking fitz Law. Next their design is actually bigger than the Windows version, although you would almost not notice based on the scaling of the images. Third, they waste even more space than the windows dialog, its a window in a window. Basically all their critiques are wrong. Plus they violate the same principles in thier design. The only thing that is better in the apple dialog is the radio button for never. This lets the user know this option is there while the first only indicates that other times will be listed in the drop-down selector.

    5. Re:the part about the dialog box is wrong by Anonymous Coward · · Score: 0
      Actually, a lot of MS's GUI "research" ammounts to buying widgets and elements they like from Apple. This is why XP looks more like the Mac OS than ever. The ammount they pay to Apple for this is "undisclosed" as part of the lawsuit settlement that came a few years ago.

      We all know that Apple was always the unofficial R&D department for Microsoft. Their recent agreements just made it an above-the-table transaction, instead of outright theft.

    6. Re:the part about the dialog box is wrong by Anonymous Coward · · Score: 0

      I call bullshit.

      MS is mean, cruel, evil, and vicious, but they are not dumb. MS does do research, lots of it. Tons and tons of it. Thier research is not focused on asthetics but productivity, and ease of use, and quite simply they won. All the complaining about preloading interface elements, and adding extensions, is just complaining. MS has a nice system. MS added the absolutely wonderful wheel to mouses. MS added some very useful keys to the keyboard. MS has always chosen productivity. The similiarties between OS X and XP are mostly superficial. In actual use they play out very very differently.

    7. Re:the part about the dialog box is wrong by MoneyT · · Score: 2

      Still, most setting boxes in windows have multiple save/OK buttons, and it's not always clear which ones do what. Not to mention the OK and Apply buttons. Some apps, OK means apply and close, some OK means close just like cancel does, other won't let you click OK till you've clicked apply. That gets annoying.

      --
      T Money
      World Domination with a plastic spoon since 1984
    8. Re:the part about the dialog box is wrong by MoneyT · · Score: 3, Interesting

      Productivity and ease of use? The whole purpose of Apple's Interface Guidelines is to make things easier to use and more productive. Take for example having one menue bar. The location of everything the you ned to access commands is in one spot, always. Or what about even something as simple as the window controls. In windows, all the menue commands are on the left, but all the window controls are on the right. How is that efficient? Or even the save dialouges. THe Don't Save button is off to the left and further spaced than all the other buttons. Why? Because it is the most destructive of the option, and because most people are right handed so they tend to look for the best options on the right (or something like that, it's psycological).

      I don't know about the scroll wheel, whether M$ did that first or not, but I have not come aross a single button on M$ keyboards that is so useful it boosts my prouctivity.

      You're right, they do play out differently. And in 99% of the cases, the mac OS is easier, more intuitive and faster.

      --
      T Money
      World Domination with a plastic spoon since 1984
    9. Re:the part about the dialog box is wrong by dadragon · · Score: 2, Funny

      ... I have not come aross a single button on M$ keyboards that is so useful it boosts my prouctivity.

      I certainly have.. ctrl-alt-del :)

      --
      God save our Queen, and Heaven bless The Maple Leaf Forever!
    10. Re:the part about the dialog box is wrong by foo12 · · Score: 1

      The Dock isn't larger than the task bar --- by default it is, but I can squish my dock down to a height of 32px.

  4. The difference by Anonymous Coward · · Score: 2, Insightful

    Aqua et al have been DESIGNED by professionals. Gnome was thrown together as a hack job by retards too stupid to comprehend how a real GUI should work.

    1. Re:The difference by Anonymous Coward · · Score: 0

      I've found that the good news about Gnome is that it is remarkably easy to customize nearly all the elements of the GUI. The bad news is that you must do so in order to make the GUI even usable, because it defaults to some really poorly thought-out settings.

    2. Re:The difference by Anonymous Coward · · Score: 0

      Easy? It took me 25 minutes to find the sawfish window manager config page, and that still didn't have the setting I wanted to change. Poorly thought out? Yes!

    3. Re:The difference by Anonymous Coward · · Score: 0

      You mean you don't like the useless anti-aliased Nautilus app opening up and making your 1.8 Ghz machine seem like a P120?

  5. Jesus christ. by Taylor_Durden · · Score: 0, Flamebait

    There are way too many 'common sense' articles posted on Slashdot. Why do we need apple to tell us that we should only use one menu bar in Mac apps? Half of their 'tips' are suggestions such as hiring a company that pays Apple a commission to recommend them, or saying to conform to what Apple wants your app to look like. Big fucking deal. Any Mac developer worth his salt should know this stuff anyway. My only hope is that somehow all the /. geeks can somehow slashdot Apple. Then all the Apple sysadmins have to stop smoking the 'peace pipe' and put the web site back up.

    1. Re:Jesus christ. by Golias · · Score: 5, Interesting
      Why do we need apple to tell us that we should only use one menu bar in Mac apps?

      "We" don't. (If be "we" you mean "clueful programmers".) This article wasn't written for "any Mac developer worth his salt." It was written for very smart developers of other platforms that want to be aware of what the need to know to succeed on the Mac platform.

      The article is interesting reading to see what Apple is currently telling coders who are new to doing a Mac port. Many companies have ported apps to the Macintosh without paying attention to Apple's UI guidelines, and were stunned to discover that the entire Mac community thought their app, which was a modest success in the Windows market, was universally dismissed as utter crap by Mac users. This info can help companies avoid repeating that mistake. It's not about conforming to what Apple wants it to look like nearly as much as what Apple users have come to expect from their apps.

      One of my favorite differences is that I almost never see a dialog box with a button that only says "Yes" or "No" on it when I'm using the Mac. (Mozilla is one of the exeptions. The Mac 1.0 version is still lacking a lot of Mac-ness, but it pulls up /. pages a lot faster than IE, and doesn't break on as many sites or nag me for money the way OmniWeb does, so I'm not going to bitch too much about a "capitol-F" Free software product.) There are far too many Windows apps that pop up dialog boxes saying stuff like "You are launching proceedure $FOO without condition $BAR being properly set. Do you no longer wish to avoid autocorrecting the object status and reimplementing the enterprise settings? [Yes] [No] [Cancel]"

      --

      Information wants to be anthropomorphized.

    2. Re:Jesus christ. by Anonymous Coward · · Score: 0

      That's one thing I really like about Open Office; is that a dialog box makes sense. My boss was on my computer and was actually somewhat confused by two options "Discard" and "Cancel". Apperently after seeing that one word wasn't "yes" he actually read the confirmation dialog. The whole yes/no/cancel thing is just a UI stupidity that shouldn't be.

    3. Re:Jesus christ. by cioxx · · Score: 1
      Why do we need apple to tell us that we should only use one menu bar in Mac apps?


      Did you even read that article? It was nearly a recommendation to the software developers/porters to maximize the impact of the application through the GUI. They are giving away free tips on the niche market which they helped to create. At least be thankful they give a rats ass about the developers and users.
    4. Re:Jesus christ. by Troy · · Score: 1

      "You are launching proceedure $FOO without condition $BAR being properly set. Do you no longer wish to avoid autocorrecting the object status and reimplementing the enterprise settings? [Yes] [No] [Cancel]"



      Uh, yes????
      [Click]
      NO! NO! I meant NO!
      ....
      SHIT!

      [Alt-F4]
      [File....New]

    5. Re:Jesus christ. by Phroggy · · Score: 2

      Slightly more realistic dialog boxes:

      Do you want to save changes before closing? [Yes/No]

      Are you sure you want to close without saving changes? [Yes/No]

      I haven't noticed Mozilla giving me Yes/No buttons; I've noticed giving me Mac-like Don't Save/Cancel/Save buttons just like the Mac standard, even on Windows and Linux. Not to mention the Edit/Preferences standard (Mozilla/Preferences on OSX).

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
  6. Hire Professional Help by Anonymous Coward · · Score: 1, Funny

    Rule 3: Hire Professional Help

    Well, at least they got one thing right. If you think you can make money developing MacOS software, you really should get professional help!

    1. Re:Hire Professional Help by sg3000 · · Score: 4, Interesting

      I know that you meant it as a joke, but I think Apple's statement makes sense.

      The days of the skilled programmer (but unskilled UI designer) putting together the icons and user interface are over. Well designed applications are the key to making an application useful. I think SoundJam and iTunes are a great example.

      Cassidy and Green built the original SoundJam MP3 application, and while it was full-featured, it was a bit of a pain to use, particularly the custom playlist feature. In fact, I never really used the feature since it was such a pain to create the playlist with customized criteria and keep it in synch with the songs I had in my collection.

      When Apple bought SoundJam from Cassidy and Green, they renamed it as iTunes, and stripped the functionality down. The most important thing they added was the live searching feature, and the ability to support integrated playlists. Suddenly, the overwhelming SoundJam application became the much more friendly iTunes, accessible to any user. iTunes 1.0 had fewer features than SoundJam, but since its user interface was better, the application was better.

      Icons are the same way. When you look at just the icons of 10 years ago, you can see how far we've come. Look at the winners of Icon Factory's Pixelpalooza competition, you can see how even the winners' icons from just five years ago, you can see although they were cute and clever for 1997, they look unprofessional compared to the look of the icons delivered with Mac OS X 10.2.

      --
      Insert simplistic political, ideological, or personal proselytization here.
    2. Re:Hire Professional Help by uberjon · · Score: 0

      Have you ever heard of Photoshop?

      --
      Dick Laurent is dead.
    3. Re:Hire Professional Help by Anonymous Coward · · Score: 0

      UI design is more than Photoshop.

    4. Re:Hire Professional Help by Anonymous Coward · · Score: 0

      If you are not skilled, invest some time and become so. In future, keep your opinions to yourself.

    5. Re:Hire Professional Help by Anonymous Coward · · Score: 0

      "In future, keep your opinions to yourself."

      Thanks for your opinion.

    6. Re:Hire Professional Help by gig · · Score: 2

      > Hire Professional Help

      This is SO IMPORTANT for independent coders to understand before porting to the Mac. Hire an artist or make a collaboration with an artist or designer. GET ARTISTS TO MAKE THE ARTWORK! Sheesh. You might have the best algorithms and amazing data, tight code that runs fast and doesn't crash, and functionality that is in high demand, but it will go for nothing in the Mac market if your application doesn't have an interface that respects the history and experience of the Mac user base. If your app has a Find command and it isn't Command+F, you might be the only such app that a particular user has ever run into that does that. They have 20 apps that all do Find when you press Command+F, and yours doesn't. They are not going to assume that you chose another key shortcut, they're going to assume your app is broken. They're going to write you and try to be helpful in reporting a "bug" and then you're going to write back all haughty with a developers-know-all attitude that vi uses something else for Find and so that's what your app uses and you're just plain going to alienate users. If vi users are also important to you, make a Preference such as "use vi shortcuts" so that a user can enable. There are a couple of apps that already handle key shortcuts this way on Mac OS X.

      Pixelated graphics and icons are another strike because Mac OS has had system-wide high-quality anti-aliasing and full-color icons since 8.5 (almost 5 years). Users expect from experience that graphics will be smooth and colorful and text will have "no jaggies". If you graphics are not anti-aliased on Mac OS X, it sticks out like old stock war footage in a movie about WWII. There's no excuse these days. The average coder can find a half-decent artist on the Web in NO TIME AT ALL and get some better graphics. Some coders have simply shipped a beta with bad graphics and icons along with the message that they are open to user contributions, and within a week they will get icons and toolbars and logos in email. In other words, there's just NO EXCUSE for bad graphics. Half-decent graphics are FREE, and good graphics are CHEAP.

      Another reason to respect the Aqua GUI is that if you let Apple manage this stuff, you don't have to. You start Interface Builder and you get a menubar with File, Edit, View already on it and lots of stuff already filled in where it is expected to be. Hook that up to your code and data and functionality, and if you need to modify something there, find out how somebody else has already solved that so you can stay consistent.

      It's such a drag when you find a good app with good functionality that you end up putting in the Trash because you simply don't have the time or patience to adapt to it every time you use it. I don't want to think about what app I'm in, just what document I'm working on, so having one app not work as expected gets in the way of my whole workflow.

      The stuff in this document is the real reason people use Macs. It's not because they're prettier, it's because compared to other systems, with the Mac, it's like you only have to learn one application ("Macintosh"), and then there are thousands of plug-ins for that app that add other functionality. From the user's perspective, it's very, very empowering. You're not afraid of a new app, because you "already learned most of it", and the interface fades into the background along with the computer and you only see your WORK (song, story, poem, artwork, movie, code, memo, whatever). These days the stability and proper security and also standards support are other big reasons, but the Mac is still around basically because other systems all still have shitty interfaces.

      It's funny to see UNIX geeks bashing this document ... imagine a command-line app that used ":" instead of "/" as the separator for directories and you'll understand why a Mac user resents the "wrong" key shortcuts or window or menu behavior. YOU JUST INTERRUPTED MY WORK. Think about it.

  7. Some things are misleading by ajiva · · Score: 1

    Look at the screenshot of the power settings in Windows. The reason it looks like that is because the computer that Apple happened to use for the screen shot did not have the "turn off disk", "standby", and "hibernate" features and as such those things were missing from the screenshot. Had those things been there, then the screenshot would have looked full. Just a little misleading

    1. Re:Some things are misleading by Jonathan · · Score: 5, Insightful

      Look at the screenshot of the power settings in Windows. The reason it looks like that is because the computer that Apple happened to use for the screen shot did not have the "turn off disk", "standby", and "hibernate" features and as such those things were missing from the screenshot. Had those things been there, then the screenshot would have looked full. Just a little misleading

      Well, why didn't the size of the dialog shrink if those features weren't there? That's Apple's point.

    2. Re:Some things are misleading by Anonymous Coward · · Score: 0

      With all the wasted screen space in aqua I dont think apple has a point to make about screen efficiency.

    3. Re:Some things are misleading by henele · · Score: 1

      (Standard apple geek reply)

      Or another example of the usefulness of Apple's Hardware/software control/unity...

      (/SAGR)

    4. Re:Some things are misleading by AnyoneEB · · Score: 1

      May I please see the software hack Apple used to remove those options? They are always there as far as I have seen.

      Also the other tabs take up the full space. Should the box resize when you switch tabs?

      --
      Centralization breaks the internet.
    5. Re:Some things are misleading by Anonymous Coward · · Score: 1, Interesting

      You've got to be kidding. So when I switch tabs in the dialog, the window which contains the tabs should change size?

    6. Re:Some things are misleading by Anonymous Coward · · Score: 0
      You've got to be kidding. So when I switch tabs in the dialog, the window which contains the tabs should change size?

      If you are writing for the Mac, then yes.

      Lucky for you, the mac Interface Builder sets up most of that for you, so you don't need to re-invent the wheel to perform this little trick. Just use their interface tools, and tweak as needed.

    7. Re:Some things are misleading by Golias · · Score: 2
      If you read the caption underneath, you would understand that they are not trying to point out that this particular Windows dialog box is crap, but rather "this is an example of a crappy dialog box". Their complaint was about more than the empty space (which was probably photoshopped in for demonstration purposes... we've all seen other dialog boxes with that problem, but they wanted a single image to demonstrate several problems). They also pointed out "superfluous group boxes and horizontal separators clutter the dialog."

      This is why they caption calls it a "Windows-like dialog box," and not "a dialog box from Windows." It's just an example of things they are saying you should avoid.

      --

      Information wants to be anthropomorphized.

    8. Re:Some things are misleading by YU+Nicks+NE+Way · · Score: 2

      The dialog didn't autosize because there is a tradeoff between attrctiveness and usability. The Apple design assumes that users don't care what's underneath the window they're looking at. Basically, that design depends on the assumption that if my application has a modal dialog up, then you should look at the dialog, and not at the underlying app.

      Fair enough -- except that it turns out to not be true. One frequent action that users take is to move a modal dialog out of the way in order to look at their document, and then navigate the dialog based on what's on the screen. Having dialogs of constant size facilitates that user operation; altering dialog height to fit the dialog's contents its workability inhibits it.

    9. Re:Some things are misleading by usermilk · · Score: 1

      It resizes for you in OS X.

    10. Re:Some things are misleading by Anonymous Coward · · Score: 0
      Well, why didn't the size of the dialog shrink if those features weren't there? That's Apple's point.

      No, that's not Apple's point. If that were Apple's point, they would have said so, or at least shown the Windows dialog with and without those options. Further, the #1 rule of tabbed dialogs is that the size of the dialog remains the same as you switch tabs. That's true of every platform I've seen that uses them, including MacOS X.

    11. Re:Some things are misleading by Anonymous Coward · · Score: 0
      You've got to be kidding. So when I switch tabs in the dialog, the window which contains the tabs should change size?

      If you are writing for the Mac, then yes.

      No, that's not true. Tabbed dialogs never change size in MacOS X. Other dialogs sometimes do, but every tabbed dialog I've run across so far has kept it's size as you switch tabs. Which IMHO is the way it should be, otherwise the tabbed interface would get annoying real fast. If you can point me to a single tabbed dialog in OS X that changes size when you switch tabs I'll be impressed.

    12. Re:Some things are misleading by Anonymous Coward · · Score: 0
      If you read the caption underneath, you would understand that they are not trying to point out that this particular Windows dialog box is crap, but rather "this is an example of a crappy dialog box". Their complaint was about more than the empty space (which was probably photoshopped in for demonstration purposes...

      That strikes me as playing dirty pool. They wanted to bash the Windows interface, but couldn't find any suitable examples of bad dialog design, so they hand crafted their own example and passed it off as the real thing.

      They also pointed out "superfluous group boxes and horizontal separators clutter the dialog."

      Of course, they wouldn't have cluttered the dialog if they had left the original content in.

      This is why they caption calls it a "Windows-like dialog box," and not "a dialog box from Windows."

      Very slimy.

    13. Re:Some things are misleading by Golias · · Score: 1
      They wanted to bash the Windows interface, but couldn't find any suitable examples of bad dialog design, so they hand crafted their own example and passed it off as the real thing.

      If this was a "why OS X is better than Windows" article, you would have a point. Since this was a "common UI mistakes to avoid when porting your program to our platform" article, I think you are being a little hypersensitive.

      --

      Information wants to be anthropomorphized.

    14. Re:Some things are misleading by mrjohnson · · Score: 1

      It is a little misleading. The power options there are what most people probably look for, but what they don't mention is there is a "details" button that grows the entire window larger to fit the disk and sleep options you speak of....

    15. Re:Some things are misleading by Anonymous Coward · · Score: 0
      One frequent action that users take is to move a modal dialog out of the way in order to look at their document

      Apple solves this problem by making the dialog box translucent, so you can still see the document through the dialog box.

    16. Re:Some things are misleading by Golias · · Score: 2, Interesting
      Funny think is, I usually only hear Windows geeks talk about the advantages of integrated hardware. Apple users tend to take it for granted, mostly unware of the headaches they are avoiding.

      A Windows geek sees something he likes in the Mac OS, and says, "a good example of the advantage of having integrated hardware. However, I prefer the flexibility of being able to buy motherboard swaps on pricewatch."

      A Mac user sees the same feature and says, "an example of good software design, which is why I put up with the vendor lock-in of buying an Apple."

      --

      Information wants to be anthropomorphized.

    17. Re:Some things are misleading by YU+Nicks+NE+Way · · Score: 2

      Translucence doesn't solve the problem -- in fact, it doesn't even help. The contents of the underlying document are obscured and distorted, and the user is not in control of what is shown on the screen.

    18. Re:Some things are misleading by EvanED · · Score: 2

      Exactly. I went to the PA Governor's school for IT two summers ago where I had a course on Human-Computer Interaction, and one of the things we discovered was out of the entire class, no one liked windows auto-sizing like what Apple suggests. I'll agree that the extra space is moderatly annoying, but it's still FAR less annoying than having the window change size on you. Apple is usually better at intuitive UI stuff (the "verb button" suggestion is a very good one and one I'll be using henceforth), but in this case they're wrong.

    19. Re:Some things are misleading by alangmead · · Score: 1
      Apple solves this problem by making the dialog box translucent, so you can still see the document through the dialog box.
      Actually, Apple's solution to application modal dialogs are sheets. Essentially document modal, rather than application modal dialogs. They do obscure the current document, (so if you need to see what has changed before you can decide "Save" or "Don't Save" to "Do you want to save changes to this document before closing", you need to pick the third choice, Cancel.) You do have access the the rest of the application, though.
    20. Re:Some things are misleading by Bobartig · · Score: 1

      They wanted to bash the Windows interface, but couldn't find any suitable examples of bad dialog design, so they hand crafted their own example and passed it off as the real thing.


      Exactly, but not as dirty as you think. What they most likely did was design a simple control panel with a desired feature set using each OS's UI development packages. THey couldn't use real examples, first for legal reasons, and also because none of the control panels from windows exactly (or even closely) matches the equivalent OSX pane (and there is no "Power Options Properties" in OS X). Their point is that Window's control panels are fixed in size, and mac ones (under OSX) will dynamically fit any rectangular configuration, and perhaps that they prefer useful default settings to be layed out conveniently.

      --
      This is where I get my recommended daily allowance of "Foot in Mouth."
    21. Re:Some things are misleading by Anonymous Coward · · Score: 0
      It resizes for you in OS X.

      Actually, no. While most dialogs do size themselves dynamically, tabbed dialogs stay the same size as you switch tabs.

    22. Re:Some things are misleading by Snardly+Dinkerton · · Score: 2, Interesting

      To defend Microsoft, which is a rare event for me... The window is the proportion the Golden Rectangle, as is most of Microsoft's objects and pattern. The standard Push button falls into this category.

    23. Re:Some things are misleading by MoneyT · · Score: 2

      How many times do users loose these dialouge boxes behind other windows though? I can't tell you how oten I've been working in a document, called up a dialouge, had to check a couple other things, and never found the dialouge again till I minimized all windows. That to me is not efficient

      --
      T Money
      World Domination with a plastic spoon since 1984
    24. Re:Some things are misleading by cookd · · Score: 1

      Umm, no. I agree with you that the "main idea" of this article is about UI design for the Macintosh. But that doesn't excuse this kind of behavior. They repeatedly comment on how much better the Mac UI is than the Windows UI. That immediately reveals a secondary (or perhaps primary?) hidden agenda.

      They happened to take a Windows UI element for every example of "Bad UI" and a Mac element for every example of "Good UI." Even when they have to construct the bad UI example for themselves (i.e. make up a dialog box that doesn't really exist), they do it with Windows controls and style, and even start with a REAL Windows dialog so that people will think it IS the real thing. That, my friend, is playing dirty.

      --
      Time flies like an arrow. Fruit flies like a banana.
    25. Re:Some things are misleading by susano_otter · · Score: 2

      I think the re-sizing thing is supposed to make sense because Apple dialogs favor a "center-biased layout" standard. Visually, the important stuff is always or near the center of the dialog, right where your eyes expect it to be and can most easily recognize it.

      The dialog can safely resize to eliminate wasted screenspace (by only taking up enough space for the relevant options) because the information you're looking for is always in the same location regardless of dialog size.

      In theory, anyway. Dislike of window autosizing may have been due to Microsoft-centric habits, lack of time to truly familiarize onself with Apple's way of doing things, and limited understanding of Apple's design goals in this context.

      Knowing what I know now, I'd happily accept autosizing dialogs, and blithely spend the few cycles necessary to become used to them.

      Of course, it would also be nice if Apple's OSX platform (the hardware) was reasonably affordable, user-moddable, compliant with my employer's corporate technology standards, and able to run the games I like to play...

      --

      Any sufficiently well-organized community is indistinguishable from Government.

    26. Re:Some things are misleading by Killean · · Score: 1

      The dialog can safely resize to eliminate wasted screenspace (by only taking up enough space for the relevant options) because the information you're looking for is always in the same location regardless of dialog size.

      Umm.. no. I would assume (since I haven't actually seen it happen) that when the dialog resizes to accomdate the current tab, the "Cancel" and "OK" buttons move to a different location. Therefore the user would have to spend extra time looking for the new location of these buttons...

      --
      My new catch phrase is: "I NEED A NEW CATCH PHRASE, BABY!"
    27. Re:Some things are misleading by lemkebeth · · Score: 1

      auto-resize is only used for thing like perforeence panes on MacOS X.

      It is not used in tabbed dialogs.

      Also model dialogs on MacOS X are supposed to be sheets (attached to the Window that spawned it)

      For example, if you are in TextEdit and click the close button a sheet will slide out of the tittle bar of the window and wil be attached to that particular edit window. This does not prevent you from using other Windows in TextEdit.

    28. Re:Some things are misleading by Anonymous Coward · · Score: 0
      In theory, anyway. Dislike of window autosizing may have been due to Microsoft-centric habits, lack of time to truly familiarize onself with Apple's way of doing things, and limited understanding of Apple's design goals in this context.

      The only real design goal responsible for this is the desire for visual flair. Having dialogs dynamically resize on you while they're open is just a gimmick. Unlike some other gimmicks in OS X, like having window contents update during the genie effect so Steve Jobs can make a neat demo by iconifying a Quicktime window, this gimmick is annoying. First of all, because the dialog resizes with a smooth animation that takes about a second to complete, you have to wait in between mouse clicks. It really breaks up my rhythm. Also, and this is the worst part, the controls move on you. That totally blows away the use of muscle memory to enhance productivity, one of the keys principles of the old Mac OS.

    29. Re:Some things are misleading by Anonymous Coward · · Score: 0
      If you don't like Jews, I highly recommend the following mp3 download:
      Learn About The Jews
      Download it, listen, and enjoy a real rip-roaring analysis of the Jewish Problem.
    30. Re:Some things are misleading by gig · · Score: 2

      On a Mac, the dialog would have shrunk down if there are options that aren't needed on that system. That kind of stuff is accounted for. The

      What the user uses is where the buck stops, though. If I'm sitting at that system, I'm going to see that dialog box. This is not a mock-up of a Windows dialog box, it's a real Windows dialog box. You think that kind of shoddy interface is fine because you're 1) used to it, 2) you know the technical excuse for it. Mac users 1) are not used to it, and 2) don't care about the technical excuse for it, or don't believe the excuse since they've already seen it done better by other apps. GET OVER IT.

    31. Re:Some things are misleading by gig · · Score: 2

      Ha ha ha. All the inconsistencies in Windows (95, 98, NT, Me, 2000, XP) on all the different hardwares, with all the different shitty drivers, and you guys think that an inconsistency in a screenshot in a tech paper is more likely to be "Photoshopped in" by Apple?

      MICROSOFT DOES NOT NEED APPLE'S HELP TO MAKE SHITTY DIALOGS. Apple does not need to use Photoshop to display examples of strange dialog boxes in Windows applications. In fact, this comparison is rather tame. They are taking care not to insult the reader, who is likely to be a Windows developer who has made his or her share of shitty, shitty dialogs. They also use Microsoft's own apps here. They are not even using other developer examples to display the inconsistencies. Why don't they show a Borland app written for Windows 95 running on Windows XP? Users are running into that kind of shit all the time.

    32. Re:Some things are misleading by gig · · Score: 2

      This article is about porting software from other platforms to Mac OS X. That is the reason they took an arbitrary Windows dialog box and recreated it as a Mac dialog that doesn't actually exist on the Mac. PORTING.

      It would have been better if the dialog they showed was from CorelDRAW or something, then you would get the picture that we're talking about porting an app between systems. I guess they wanted to use Microsoft's own stuff, though.

      Also, on the Mac, System Preferences is just an application that modifies XML preference files. Showing a Windows Control Panel to a Windows user is like showing them a "system" thing, though ... the dividing lines are not clear on Windows. You might not think of Windows' Control Panels as apps, but they are and their interfaces SUCK ASS.

  8. It is quite interesting, but... by gowen · · Score: 2, Interesting
    I can't agree with some of them. For example :"Don't use non-standard controls".

    Now, a developer may appreciate a large stock of standard controls, but sometimes the best controls are non-generic. I light my gas oven by turning the dial and pushing it in. This is not how I operate my toaster (single dial and slider to depress bread) or microwave (timer dial with separate on/off/pause button) or my fridge (single slider for thermostat, built in switch for the light.)

    Do you know something? Despite their proximity in the kitchen, I don't find this plethora of different user interfaces confusing. I didn't even have to read the manuals, even though my new toaster is quite different from the old one. Contrary to what interface designers tell us, we can cope perfectly well with this sort of complexity.

    --
    Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
    1. Re:It is quite interesting, but... by ChrisJones · · Score: 5, Insightful

      Most application interfaces are just a little more complex than a toaster.
      Consistency is the most important part of a UI - a user will get used to the behaviour of certain controls/widgets, if your app comes along and uses it's own that behave differently, you just broke consistency and the user will have to waste time deducing the behaviour rules of your control.
      Windows has become a hive of confusing and inconsistent interfaces, not only because people like Adobe write their own tab controls, but people like Creative and whoever wrote BlackIce discard the standard interface entirely and use their own hideous bitmap based monstrosities.
      Not to mention the fact that using standard controls saves a hell of a lot of time developing custom ones. Obviously some controls simply won't exist and you'll have to make them yourself, but with a reasonable set of standard ones and a good canvas control you have most things covered.

      --
      Chris "Ng" Jones
      cmsj@tenshu.net
      www.tenshu.net
    2. Re:It is quite interesting, but... by avalys · · Score: 4, Insightful

      Apple is just trying to ensure that their OS's reputation of being user-friendly isn't damaged by overzealous developers. New users don't know enough to distinguish between the OS and the applications that run on it, so an app that's hard to use reflects negatively on their OS.

      --
      This space intentionally left blank.
    3. Re:It is quite interesting, but... by gowen · · Score: 1
      the user will have to waste time deducing the behaviour rules of your control
      Thats true, but if your new custom is well designed for its specific use, rather than merely cobbled together from generic components then any initial time-wasting will be saved, because a well designed widget is easier for the user to use -- once they get the hang of it. And if they use it everyday for a year, the time saving overpowers any initial learning curve.

      People put far too much creedence on "intuitiveness" (usually -- and wrongly -- defined as "similarity to what you've seen before") and not enough on "does this enable the skilled user to do the job efficiently".

      By all means take the familiarity and the initial learning curve into account, but it is not the be-all-and-end-all of good interface design, as many make it out to be. Needles and cotten are intuitive and familiar, but if I want to sew every day of my life, and going to learn to use a sewing machine.
      --
      Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
    4. Re:It is quite interesting, but... by elindauer · · Score: 4, Informative

      I can't agree with some of them. For example :"Don't use non-standard controls".

      I agree with you, however... I suspect the reason Apple makes this suggestion is that most developers over estimate their expertise in designing user interfaces. They think, "it makes sense to me" and they write a control that makes no sense at all. Their intimate familiarity with the product and it's intended use makes it difficult for them to imagine the thought process of a new user.

      Designing user interfaces is pretty complicated, and requires a lot of thought. Even with this time investment, you still need to do user testing etc on your new control to see if it gets used the way you had hoped. This is true of any new interface, but especially true if that interface is full of non-standard controls. Most software products don't have the resources to devote to this aspect of development.

      So yes, an intelligent design with non-standard control *can* work. But you won't go far wrong with the ones that have been carefully thought out and provided for you. As soon as the article say something like "most developers will do better with the standard controls", every developers suddenly feels like he is part of the group that doesn't fall into that category. (Everyone overestimates their own ability.)

    5. Re:It is quite interesting, but... by Anonymous Coward · · Score: 2, Insightful

      I can't agree with some of them. For example :"Don't use non-standard controls".

      Please remember this:

      People are stupid.
      Programmers are people.

    6. Re:It is quite interesting, but... by Webz · · Score: 1

      The thing you have to realize about computer interfaces is that a computer can do many more things than most physical objects. In addition, they have many more ports of entry. For example, a toaster can (should) only toast bread, with its slots for bread and slider to depress the bread. But, a CD-burning program like Toast (heh) can be accessed via the shell, with a keyboard, a mouse, etc. It can author all different kinds of CDs (mp3, VCD, etc), each possessing their own quirks, much unlike different shades of toast.

      Also, standardized interface elements are some of the most powerful tools available to software designers. Real world objects, in their limited context, can afford to have different interfaces because they only do One Thing and One Thing very well. Since some software can run an entire three ring circus (in addition to noting the myriad of software products out there already), the compromise developers have to make is to use standardized software components...

      Standardized UI elements are always expected, accessible, and skinnable. By using the same dial, button, checkbox, anything, across different programs, a user will immediately know what is what. Don't forget that most people have grown up learning what a toaster is, while many have yet to learn how to use their PCs properly... Standard UI elements are always accessible, as governed by the OS... For instance, all standard text boxes in OSX have immediate access to a built in spell checker (I think), as well as input from Inkwell (or whatever).

      I can get into an entire holy war about why Mozilla will always remain a second-rate browser for its complete lack of native UI (that's what Chimera is for)... Anyway, standard UI elements are almost always skinnable. Jaguar's UI had a facelift, and all Aqua compliant apps will benefit from that. But the most depressing part about the Windows world is that people don't care about Luna... Luna, however ugly you think it is, is all about the 6th generation of window controls... They are skinnable, visually responsive, and accessible. I hate Windows apps that aren't skinned properly. It isn't as obvious as an OSX app that isn't Aquified, but if you're a fan of Luna, it will stick out like a sore thumb...

      And no, I don't think anyone should live with any degree of complexity. Note, I'm not saying devices shouldn't be capable of powerful, complex things, I'm just saying interfaces should be intuitive and obvious.

    7. Re:It is quite interesting, but... by Webz · · Score: 2, Interesting

      The most interesting part about inconsistent interfaces on Windows is Microsoft's behavior... Somewhere deep inside MSDN, they advocate using their new Luna-compatible controls, as well as recommending more subtle XP-style conventions like cartoony icons, akin to Apple's UI guidelines...

      However, with each version of Office to date (I think...?), Microsoft has never used Windows's native control set. A perfect example of this is Office XP. Office XP, although XP branded, supports none of XP's skinning abilities. Office XP definately sports that flat look, rather than the fluffy, colorful look that Windows has. Although Microsoft has always made sure that the Office controls are an accessible super set of whatever Windows can do, this strategy is a waste of time and money.

      How can anyone take Microsoft seriously if they aren't even following their own advice? It's as if they want Office to be its own operating system...

    8. Re:It is quite interesting, but... by MrWa · · Score: 1
      Do you know something? Despite their proximity in the kitchen, I don't find this plethora of different user interfaces confusing. I didn't even have to read the manuals, even though my new toaster is quite different from the old one. Contrary to what interface designers tell us, we can cope perfectly well with this sort of complexity.

      But you just contradicted yourself. That new toaster had consistent controls, no? It is very seldom that software will require special controls and, as another poster pointed out, it is the useless, extraordinary changes that confuse and anger users.

    9. Re:It is quite interesting, but... by tgibbs · · Score: 2
      I can't agree with some of them. For example :"Don't use non-standard controls".

      More accurately, it says not to use non-standard controls unless the application really needs them--in particular, don't create a non-standard version of a control that is already available in a standard form.

    10. Re:It is quite interesting, but... by IIRCAFAIKIANAL · · Score: 2

      Not only that, but custom interface controls cannot be over-ridden by windows configurations, such as increasing the window button font size for people with vision problems.

      It's like when someone uses CSS and puts '!important' in every element - some developers just can't accept that the UI should not be 100% under their control (ie/ some users need to be able to override).

      --
      Robots are everywhere, and they eat old people's medicine for fuel.
    11. Re:It is quite interesting, but... by stevey · · Score: 1

      You might be interested at a look at the User Interface Hall Of Shame then - it's full of examples of developers perverting normal controls to use them for other things, or coming up with their own widgets to replace `normal` controls.

      Even Apple aren't immune. (Though to be fair that was quicktime 4 which is quite old).

    12. Re:It is quite interesting, but... by gowen · · Score: 1
      That new toaster had consistent controls, no
      Consistent with what? Other toasters? No, it doesn't. One has a dial, one a slider, one had an "emergency eject" button, the other was brute force ... one had two slots, the other one long slot. Yet I still figured it out.
      --
      Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
    13. Re:It is quite interesting, but... by Etcetera · · Score: 2


      Isn't it nice how you can get into almost anyone else's car and you pretty much know how to drive it? How the accellerator is always on the left, the gearshift is somewhere in the middle?

      That's called standardization, and it's good.

    14. Re:It is quite interesting, but... by gowen · · Score: 1
      Not only that, but custom interface controls cannot be over-ridden by windows configurations
      Well, they can in X. No-one is suggesting that custom widgets should be hard wired. Theres no reason why a well designed my-custom-dialog box shouldn't honour global preferences in exactly the same way as your-generic-dialog-box does. This is a strawman.
      --
      Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
    15. Re:It is quite interesting, but... by MissMyNewton · · Score: 1
      Dude, hope I'm never on the same road as you!


      The accelerator pedal is on the RIGHT.

      --

      ---

      Information wants...you to shut your pie hole.

    16. Re:It is quite interesting, but... by gowen · · Score: 1
      How the accellerator is always on the left
      Except, here in the UK its on the right. And as anyone who has ever driven both left and right hand drive cars will tell you, whilst it initially takes a little getting used to, within no time at all it becomes second nature to you, even though its not the same. Which is exactly my point. People aren't stupid.
      --
      Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
    17. Re:It is quite interesting, but... by Etcetera · · Score: 2


      D'oh! Maybe I should wake up before I post :)

    18. Re:It is quite interesting, but... by archen · · Score: 1

      Actually I don't think that would be much of a problem. If he's hitting the left pedal to accelerate, he's either hitting the clutch, emergency brake, or the brake. In any event he's not going anywhere fast.

    19. Re:It is quite interesting, but... by Etcetera · · Score: 2


      Actually, it's on the right in the US too (I'm just dumb.)

      Never having driven a left-hand car, or on the left side of the road, I can't speak from personal experience here. But the few British people I've known here in the States have ranted for a quite a while about having to switch back and forth and it taking getting used to.

      And in an emergency, it had *better* be second nature!

    20. Re:It is quite interesting, but... by billatq · · Score: 1

      "Microsoft has never used Windows's native control set. A perfect example of this is Office XP. Office XP, although XP branded, supports none of XP's skinning abilities...It's as if they want Office to be its own operating system"

      Amusing that you should say that, because Microsoft has different teams that do each (The operating system team and the office team) which have different ideas about how one should do UI. Office XP has it's own special UI compared to the Windows UI and the developers don't really care about the operating systems team.

    21. Re:It is quite interesting, but... by Ed+Avis · · Score: 2

      Apple's guidelines are the direct opponent of all those developers for Mozilla, Java, StarOffice, and so on who go to a lot of trouble to make sure their app looks the same on all platforms. Even reimplementing a whole widget set from scratch, in the three examples above. Now, which philosophy do users prefer - make it consistent with the rest of the platform, or make it consistent with the same app on other systems?

      --
      -- Ed Avis ed@membled.com
    22. Re:It is quite interesting, but... by go-low · · Score: 1

      Yes, This is interesting, but...

      If you're using an application on a regular basis (Because I does what you need it to do) then you will learn it's user interface regardless of how unfreindly it is on first glance.

      Don't get me wrong, consistency is desirable, it's just not essential.

      For example if you look at a complex application such as Primavera project planning software (please excuse the non-user-freindly URL!) http://www.primavera.com/products/p3.html despite it's tricky user interface, it is the de-facto constructionn industry planning tool. It's ugly, but to coin Apple's catch phrase, 'It just works'

      Having said that, I would be a happy planner if they ported it to OS X! :-)

    23. Re:It is quite interesting, but... by DavidRavenMoon · · Score: 2
      This is not how I operate my toaster (single dial and slider to depress bread) or microwave (timer dial with separate on/off/pause button) or my fridge (single slider for thermostat, built in switch for the light.)

      A toaster is not a microwave, so we don't expect them to work the same way. But if you are used to using one certain toaster, and then you use a different toaster and the controls are laid out differently, you have to stop and learn the layout. It only takes a moment, but Apple is trying to avoid that moment altogether. And as the complexity of the application grows, the longer the learning curve.

      I think we've all seen appliances with bad UI. Maybe the readers of Slashdot don't have problems with working their microwaves, or setting the clocks on their VCRs (and microwaves), but look how many people do!

      Another example is cassette tape recorders. It would seem that manufacturers can't make up their mind about what order the control buttons should be placed, so on one machine play might be the first button, followed by stop, but on the next it might be rewind followed be record. If you have a few tape decks you have to stop and look before you press buttons.

      Windows dialogs can be confusing. And pull down (pop up?) menus have the same appearance as a text input field, but you can't enter text. Plus having to press the detail button just makes for more steps.

      --
      -- if it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic - Lewis Carrol
    24. Re:It is quite interesting, but... by DavidRavenMoon · · Score: 2
      Consistent with what? Other toasters? No, it doesn't.

      Yeah, but you know all toasters have a control for how brown the toast gets, and something to start the toast cycle.

      The controls might look different... a slider instead of a knob, and maybe numbers or colors, or even push buttons, but they still should make sense.

      If your toaster had instead of say, 1 to 9 for the toast timer, and had a slider going from blue to green, you wouldn't have any idea what that did until you either read the manual, guessed, or tried it out. Or maybe a knob that pulled out that had no indication of function. People wouldn't enjoy using that toaster because they would perceive it as hard to use.

      I don't think Apple cares if you use a slider, or a pulldown with numbers to change a value, just as long as you use native widgets.

      --
      -- if it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic - Lewis Carrol
    25. Re:It is quite interesting, but... by EvanED · · Score: 2

      I vote making it look consistant with other apps on whatever platform you're running. Most people don't switch between platforms, so making it consitant with what the user is used to is more important. If they do switch, either they are doing work on one and have another at home (in which case only "simple" applications - email, web browser, etc. - are likely to be used on both) or are computer geeks dual booting Windows and Linux or something (in which case they'll figure it out anyhow).

      Don't get me wrong, I don't think that developers should go placing commands in different menus on different platforms or something, but I don't think they should even begin to try to make it look ther same on all platforms. Use the Windows tabs on Windows systems, Mac tabs on Macs, X tabs on X, etc.

    26. Re:It is quite interesting, but... by Arandir · · Score: 2

      That's your kitchen. All of the appliances are simple. They might (just might) be even simpler with standard controls. Imagine if your convection and microwave ovens both had the same style of controls. Or what if your TV, VCR and DVD player had the same kinds of controls?

      No rules are written in stone, but if you're going to create you own custom control, you should have demonstrable reasons for doing so.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    27. Re:It is quite interesting, but... by Elwood+P+Dowd · · Score: 2

      Since you get physical feedback from all of those kitchen devices, they've got natural advantages over computer interfaces.

      Also, different programs are not different devices. If the knob on your gas range started working differently depending on the type of food, it'd be damn confusing.

      And there, now I've taken the metaphor way way too far. Every time someone starts doing computer interfaces like physical interfaces, things go horribly wrong. For evidence, I submit: All non-Apple software DVD players.

      --

      There are no trails. There are no trees out here.
    28. Re:It is quite interesting, but... by Arandir · · Score: 2

      I recently wrote a widget style for KDE, and custom widgets are a pain in the butt. That's one way I can detect custom widgets: they stick out like a sore thumb when I apply a non-default style. If a style developer has problems setting their look, how the heck can a user do it through global preferences?

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    29. Re:It is quite interesting, but... by WiggyWack · · Score: 1

      Yes, but whether you're in a Ford or Toyota, gas is on the right, break is in the middle, and you turn the car with a round "steering wheel".

      --
      Macintosh humor! MacComedy.com
    30. Re:It is quite interesting, but... by Gumber · · Score: 2

      if your app comes along and uses it's own that behave differently, you just broke consistency and the user will have to waste time deducing the behaviour rules of your control.

      It isn't just that. If your control looks superficially like a common control, the user will also have to remember that your control behaves differently and how to react accordingly every time they use your application.

      For most people, this is a major source of ineffciency. Even hard core geeks stumble over this sort of thing, whether they are willing or able to admit it to themselves.

      It seems to me that geeks wouldn't be too happy with API calls that do something similar and yet have totally different semantics, why are such inconsitancies acceptable, or even desirable, when we are talking about a User Interface as opposed to an Application Programmer Interface?

    31. Re:It is quite interesting, but... by MoneyT · · Score: 2

      personaly speaking, if you're going to do complete consistancy across all platforms, you should try following the design layout of KDX (www.haxial.com)

      --
      T Money
      World Domination with a plastic spoon since 1984
    32. Re:It is quite interesting, but... by vincent99 · · Score: 1

      Right.. then your UI could look equally crappy on all platforms.

      --
      -- V
    33. Re:It is quite interesting, but... by Anonymous Coward · · Score: 0

      Remember though, the people that will be using these applications are MAC users. They're not accustomed to thinking.

    34. Re:It is quite interesting, but... by Jace+of+Fuse! · · Score: 1

      people like Adobe write their own tab controls, but people like Creative and whoever wrote BlackIce discard the standard interface

      While I certainly AGREE that standard UIs are a generally GOOD thing, and I agree sometimes the ability to deviate leads to some horrendous efforts, for the bad examples mentioned there are an equal number of really GOOD non-standard interfaces.

      Can anybody honestly tell me that they don't like WinAMP 2.X? I know 3.x gives skinners even more power to deviate -- but even still, some applications really do well to have non-standard interfaces.

      I love Trillian, one of the best Windows messengers around. It's choice of skins as excellent, even if I do tend to use XPSilver most of the time I like the fact that I chose that look, and wasn't forced into it.

      In short, I think having a broad and standard UI is a great thing. But I think being able to deviate from time to time is just as much a good thing.

      --

      "Everything you know is wrong. (And stupid.)"

      Moderation Totals: Wrong=2, Stupid=3, Total=5.
    35. Re:It is quite interesting, but... by susano_otter · · Score: 3, Insightful
      If you're using an application on a regular basis (Because I does what you need it to do) then you will learn it's user interface regardless of how unfreindly it is on first glance.

      It's not a question of being "unfriendly at first glance"--most new interfaces are (that's what makes them "new"). It's a question of being unfriendly throughout the lifetime of your interactions with it, due to bad design decisions made at a deep level. Your statement gives developers permission to punish end-users for needing to use the app. This is good news if you're a monopoly, but bad news if you have competitors.

      --

      Any sufficiently well-organized community is indistinguishable from Government.

    36. Re:It is quite interesting, but... by ChrisJones · · Score: 2

      Probably because just about anyone can bash out some code that does something, but making a really good interface takes a lot of planning, consideration and skill. It's something that a coder either can't do, or they didn't pay any attention to it for time/money/commitment reasons.
      It's a pity that all the extra time spent using interfaces during development, thanks mainly to Visual development tools, hasn't lead to a large improvement ;)

      I wonder how far you could lint-a-like a glade xml file, flag up layout mistakes that don't meet the ui guidelines required of them (e.g. for inclusion into Gnome).

      --
      Chris "Ng" Jones
      cmsj@tenshu.net
      www.tenshu.net
    37. Re:It is quite interesting, but... by Bishop · · Score: 2

      Can anybody honestly tell me that they don't like WinAMP 2.X?

      I hate the WinAmp 2.x interface. It is too small on big monitors. The fonts are terible. There are a bunch of little faded out letters that do important things but they are too small to use. The colours are miserable. The fonts in the playlist are too small. I think you get my point.

      WinAmp 2 used a bitmapped UI. Bitmapped UIs suck. All the skins could do was add a different picture to a bad interface.

    38. Re:It is quite interesting, but... by Anonymous Coward · · Score: 0

      Its also interesting to note that the winamp GUI came from MACAMP which came way before it...

    39. Re:It is quite interesting, but... by EastCoastSurfer · · Score: 2

      Office XP, although XP branded, supports none of XP's skinning abilities.

      I wonder if it is because Office XP, IIRC, will run on win98/win2k/winxp. The office team has to code to the lowest common denominator there and attempt to get the same functionality out of it as they will from xp. In contrast, OSX apps will run on only OSX and not also have to run on other OS's that may or may not have the UI controls natively installed.

    40. Re:It is quite interesting, but... by antijava · · Score: 1

      That's the one thing I hate about Mozilla. It works well enough (well compared to the alternatives anyway). It's just butt-ugly. I haven't found a the yet to make it clash less with Aqua. Even if it LOOKED 100% Aqua, it still would behave odd though.

      Does anyone know how to make Mozilla use my preferred e-mail program instead of Mozilla when I click on a mailto: link for instance?

    41. Re:It is quite interesting, but... by jx100 · · Score: 1

      if it's too small, you could've just used the Doublesize option (makes everything twice as big)

    42. Re:It is quite interesting, but... by Zeinfeld · · Score: 3, Insightful
      I can't agree with some of them. For example :"Don't use non-standard controls".

      Actually as a Windows user who loathes the Mac look and feel it was one of the few pieces of advice I agreed with as a general matter.

      When Mosaic first came out the most noticable thing about it was that it was the first browser for X-Windows that did not have an amateur DIY look and feel, it was plain Motif with the standard SGI fonts.

      I don't much like using Adobe products because they insist on inventing their own UI techniques rather than providing the user with something consistent. At one point I used photoshop on a daily basis, then I stopped using it for a couple of months and found that I had forgotten how to use most of the commands. These days I just can't be bothered with it.

      My pet peeve is MP3 players. For some reason these programs seem to be insist on morphing into the most unusable shape possible. Skins are cute as an option but just why does nobody - including Microsoft make an MP3 player with standard Windows look and feel?

      The other point that is quite noticable in the document is that the Apple designers appear to be making most of their comparisons to the Windows 95 look and feel rather than XP.

      It is also quite noticable that the example they give of an application with 'only one' menubar on Aqua actually has at least four visible command bars. The IE window has its own menu and shows a page with yet another menu.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    43. Re:It is quite interesting, but... by philovivero · · Score: 2
      Spoken like someone that hasn't used a 1600x1200 screen before. I've used XMMS in both sizes, normal and double. Double is ugly and bitmapped hell. The interface is still as difficult, and the app is 50% too big. Yep, bitmapped interfaces suck.

      There's a real good argument for using standard widgets: when I, the user, decide I want purple Dubblix Italic 92-point antialiased fonts for all my buttons, and a lime-green background, I can have it.

      All these lame-ass GTK developers hardcode the backgrounds of their widgets as grey, and half the time my app looks right (purple on lime-green) and half the time they look like shit (purple on grey).

      Just make the goddamn widgets standard and let me choose the colours, font styles, sizes, and whatever else I choose because, believe it or not, I actually know better than you what I want to see.

      Sorry to rant at you jx100 -- I'm responding to not just you but a lot of other replies in this thread. But I do rant at you to tell you the doublesize option doesn't fix the inherent lame ugliness of the XMMS/WinAMP interface.

    44. Re:It is quite interesting, but... by jx100 · · Score: 1

      I actually am using a 1600x1200 screen right now, and have been for quite awhile. This is just personal preference, but I don't happen to mind the highly aliased interface under Doublesize. I never really cared much for a pretty interface, as long as it is usable. Granted I'm not a huge fan of the bitmapped interface as an idea, but the underlying interface of XMMS/Winamp happens to be pretty usable for me.

    45. Re:It is quite interesting, but... by Anonymous Coward · · Score: 0

      Where are you getting your cassette recorders?

      I've only seen Record, Play, FF, Rewind, Stop/Eject, and Pause. Well, I take that back, a few have a separate eject button, and a few have no pause option.

    46. Re:It is quite interesting, but... by roqetman · · Score: 1

      I agree, we humans are quite adaptable creatures. UI designers constantly downgrade our intelligence due to the few who are not adaptable. Most problems adapting are due more to stubborness and habit than misunderstanding.

    47. Re:It is quite interesting, but... by Anonymous Coward · · Score: 0

      Double-size (in WinAmp anyways) is the most useless thing. Great, a double-sized player window! And, graciously, the Equalizer can be double-sized as well! WTF?! Anyone actually uses the Equalizer? Often enough to display it at all times? What about something more important, like a double-size PLAYLIST!? Nullsoft fuckwads.

    48. Re:It is quite interesting, but... by gig · · Score: 2

      Don't use non-standard controls unless you REALLY, REALLY have a good reason. Don't interrupt the user and ask them to learn something new just so they can theoretically be a little faster next time.

      What I see from non-Mac developers is that they develop as if their app is still the only one running on the PC. They think it is fine to "teach" the user any old thing, because the coder imagines that the user will learn it the first time they run into it, and then remember it forever after, as they go on using that app 24/7 all day long. What really happens is that you interrupt and/or annoy the user with what to them is trivial shit, and then that happens two days later again when they need your app again. It happens when they switch over to your app briefly from other apps they use more often. So time and time again you are interrupting the user. This has gotten so bad on Windows that it's killing the PC industry itself. People are using their old computers less and less and then not buying new ones, because the experience with pop-up windows, modal dialogs, and non-standard interfaces is not productive. It's fucking horrible, actually. The PC is cheaper than ever, but it's also shittier than ever. It's like a cable box ... it's so bad it should just be free with the services, but you're also supposed to pay for it and troubleshoot it. Wow.

    49. Re:It is quite interesting, but... by gig · · Score: 2

      Either do it the right way, or do it completely differently because you have a good reason to. The thing you really want to avoid is doing it "any old" way, or just not giving a shit about it.

      I have two kinds of apps (UI-wise) in Mac OS X: ones that follow the standard conventions precisely, and ones that go totally against it in an obvious way and for good reason. The standard apps are legion, but here's an example of one that went against the grain: Emagic EXS24

      Here's a screenshot of the EXS24's interface itself: EXS24 UI.

      The key is that it's very hard to confuse the typical UI with a way-out one ... when I open the EXS24 I get the picture right away that I'm not in Kansas. It's more of a musical instrument, or a self-contained "device". I can work with it by just moving sliders and discovering sounds. That's much, much, better "non-standard" behavior than when you press Command+F and you don't get the app's Find command, when that works in EVERY other app.

    50. Re:It is quite interesting, but... by gig · · Score: 2

      >> Office XP, although XP branded, supports none of XP's skinning abilities.

      > I wonder if it is because Office XP, IIRC, will run on win98/win2k/winxp. The office team
      > has to code to the lowest common denominator there and attempt to get the same
      > functionality out of it as they will from xp. In contrast, OSX apps will run on only OSX
      > and not also have to run on other OS's that may or may not have the UI controls natively
      > installed.

      Many (most?) Mac OS X apps also run on Mac OS 9. Geeks know how different Mac OS 9 and Mac OS X is from top-to-bottom, but they both have a Carbon API and you can code one app that runs in both places and looks good in both places. If you skin Mac OS 9, these apps even skin.

      So, I think you came up with the excuse (what MS might tell you) rather than the actual reason. The reason that Office XP doesn't match Windows XP is simply "poor quality". Microsoft has not made this happen, and adding skins to the OS simply exposed another seam for the Windows user. Apple already tried a skinnable OS with Mac OS 8 and once it was up and running these kinds of slippery slope problems all appeared and they gave up. If Apple can't make a feature seamless enough for them, imagine how little chance MS has of making it seamless given the variety of other systemic problems Windows has.

    51. Re:It is quite interesting, but... by gig · · Score: 2

      Rules are best when exceptions are allowed, even encouraged. You can check a single checkbox in Apple's developer tools and your app's Aqua windows change into brushed metal (like iTunes). Audion (MP3 player) has GREAT skins (all anti-aliased, all with drop shadows, even on Mac OS 9), but even though it can always look different, the controls still have play, pause, etc.

      Pro audio plug-ins often have an interface that looks more like a hardware device than a computer UI, and these are also encouraged by Apple (they even own Emagic, who have some of the best examples of this kind of "non-standard" UI design). What they say about controls is either use ours or use your own, but don't use some of ours plus some of yours that look like ours but may not always act like ours.

      There are very few things in life that are 100%, if there are any at all. To me, it seems much more like 90/10. Most apps should look and behave in perfect Aqua on Mac OS X, and some smaller percentage should work totally differently, and for good reason.

    52. Re:It is quite interesting, but... by gig · · Score: 2

      Users prefer it to be consistent on their own computer. If I tell the Mac OS X speller that "Slashdot" is not a spelling mistake, and then I launch MS Word and have to tell MS Word that "Slashdot" is not a spelling mistake, then that's something that's broken on my computer. I don't care that MS wants me to use the Office speller, I care that I had to tell the computer how to spell "Slashdot" more than once. That sucks ass, and it's the kind of situation that happens much, much less on the Mac, because Apple has typically been willing and able to make decisions and take a leadership position that's good for the whole platform, which prevents us all from going down dead ends all the time.

    53. Re:It is quite interesting, but... by gig · · Score: 2

      There are rules and there are exceptions. QuickTime Player is not an app that someone uses all day long for productivity. Even with a round volume slider it is not that bad to watch movies or listen to audio in QuickTime Player 4. It is meant to call to mind a stereo component or a device of some kind, and remind you that your focus is very much in the one window. It's meant to be "less computery" and help people to focus on the media, the content. Now, if you give the QuickTime Player 4 treatment to Photoshop, you will be able to feel shockwaves in the economy as far less graphics are turned out in various industries.

      Also, when QuickTime Player 4 shipped, it was on Mac OS 9 and everything about it was atypical. Now, the metal look is a standard GUI thing you can get with one checkbox in Interface Builder on Mac OS X, and QuickTime Player uses a standard Aqua slider for volume.

    54. Re:It is quite interesting, but... by Ed+Avis · · Score: 2

      It would be good if Linux distributions did things like having a single system-wide speller - unfortunately that means changes to applications, and distros tend to get flamed by weenies if they ship 'non-standard' versions of packages. More importantly, there just isn't the time for the packagers to modify all the apps to behave nicely. Distributions like Lycoris where there is just *one* mail client, web browser, drawing program etc etc are closer to achieving this.

      FWIW, it would be okay if MS Office included a spellchecker that _replaced_ the system standard one (optionally, but if it really was better then you'd say 'yes'). Then you'd have both consistency and the improved features. Office sounds like it is doing things the Windows way where each app has to drag a kitchen sink with it, rather than implement a service centrally.

      If MS Office's source code were available then Apple would be able to modify it to use the system spellchecker. That's a new argument for source disclosure as far as I'm aware: it helps enforce consistency among applications.

      (My personal favourite example: why do web browsers have disk caches? Why not install a single proxy server package, not necessarily a big one like Squid but something small and serving the local machine, and then have the browsers connect to that?)

      --
      -- Ed Avis ed@membled.com
    55. Re:It is quite interesting, but... by schvenk · · Score: 1

      You can't extrapolate from a simple example like that to negating a basic tenet of User Interface Design.

      That's not to say you shouldn't think about it. But it's not that simple, and my vehemence in responding comes from being a UI designer and facing clients or managers who believe things are fine and that the established design principles are silly.

      Why are the controls on all your kitchen appliances different? Are they really unique or are they perhaps familiar types of controls, each different from the others because of a slightly different purpose? My guess is these are all fairly standard controls, or twists on standard controls, and the differences among them are offset by the general familiarity you already had with each type.

      User interfaces of any type benefit from familiar controls, because the focus is shifted from figuring out how to work the controls to performing the task for which the UI was intended. Obviously custom controls are called for sometimes, but the more they can draw on the appearance and functionality of established controls, the easier they'll be to learn.

    56. Re:It is quite interesting, but... by philovivero · · Score: 2

      Double-sized playlist? Oh... I'm using XMMS, so I can't speak for the "nullsoft fuckwads," but in XMMS, you can pick the playlist font.

      But you can't pick the font for the display of the song. Well, actually, you can, but it doesn't resize the display in which the font is... er... displayed. So it looks like shit.

      Yeh, Winamp/XMMS UI sucks. Unfortunately, I've found nothing under Linux that's better. I'm sure there's something, but I'm unaware of it. Maybe someone would reply to me and show me the error of my ways.

    57. Re:It is quite interesting, but... by EastCoastSurfer · · Score: 2

      Many (most?) Mac OS X apps also run on Mac OS 9.

      From reading the apple site it seems that it is the other way around - most Mac OS 9 apps will run on OS X.

      Geeks know how different Mac OS 9 and Mac OS X is from top-to-bottom, but they both have a Carbon API and you can code one app that runs in both places and looks good in both places.

      While Carbon is a nice api to help the migration to OS X even apple says that not all Carbon features are supported on each platform. It seems that if an app is coded to use all of the OS X features then it will only run on OS X.

      So, I think you came up with the excuse (what MS might tell you) rather than the actual reason.

      I don't really see how it was an excuse, but a possible valid reason as to why a piece of software acts the way it does. Additionally, with all the fluff that MS likes to put into their products, if they had gotten skins working and were still able to have office XP installed on all the various platforms they must support I'm sure they would have done it.

      Apple already tried a skinnable OS with Mac OS 8 and once it was up and running these kinds of slippery slope problems all appeared and they gave up. If Apple can't make a feature seamless enough for them, imagine how little chance MS has of making it seamless given the variety of other systemic problems Windows has.

      If apple can't do it no one can? LMAO! Steve...is that you?

  9. Booo for Mozilla by Anonymous Coward · · Score: 0

    Tabs constitute MDI and as such are hereacy. To the trash can with it! (nevermind how well they work)

  10. good UI design by oliverthered · · Score: 1

    1: always use the users default colours and fonts
    don't use things like:

    body BGCOLOR="#FFFFFF" ALINK="#008000" VLINK="#800080" LINK="#000099" MARGINHEIGHT="0" MARGINWIDTH="0" TEXT="#000000" TOPMARGIN="0" LEFTMARGIN="0"

    2: avoid making you windows fixed width.

    3: aviod using graphics to represent text (expecially in menus)

    I may not agree with Apples 'legendary design' but the windows to mac porting document seems quite good (even if it's poorly designed)

    I believe that QT has a equivilent document

    oh an 4: never spell check, it hides you thought pattern.

    --
    thank God the internet isn't a human right.
  11. Reading in the mirror. by red_gnom · · Score: 0, Offtopic


    If only someone could make reversed fonts.

    1. Re:Reading in the mirror. by avalys · · Score: 1

      Wrong story, buddy.

      --
      This space intentionally left blank.
    2. Re:Reading in the mirror. by heptapod · · Score: 1

      There is a reversed font, it's called RSTimesMirror

  12. Some good points by GaveUp · · Score: 3, Insightful

    Many of the points brought up in the article are good points, that could be applied to any program not just one for Mac OSX. One of the complaints I have with a lot of open source software is that it has a sometimes cluttered, non-intuitive, and unprofessional/unpolished feel. If developers in general followed general guidelines like this: use informative error messages and debug messages, or dont cluter the application with lots of small undescriptive icons, but instead make panels grouped together then this would make, I think, the entire computer experience a lot more enjoyable. You wouldn't have to spend as much time learning a particular applications layout and interface just to be able to do something useful.

    1. Re:Some good points by justsomebody · · Score: 3, Insightful

      You should probably read Gnome human interface design, it may make the same interest on you as this one.

      Not to be trolling. But Apple made few mistakes.

      Like first. From users point of view, they are addressing that grey is out and they posted completely white screenshot. That could be painfull for eyes. I know I was having troubles with MOX on my Powerbook. Everything is too white and bright.

      Second point. They are addresing that you need to use big photorealistic icons. Not true. Photorealistic icons are not simple and preety. I agree, first look is gorgeous, but from users point of view, carton like friendly icons are much closer to non-pro user. Second the sizes needed to look cool for photorealistic icons are automaticaly bigger that sizes needed for handdrawn ones. It's the question of on-screen space and memory needed for program. Programs with larger images are automaticaly slower.

      Thrird point. Constant use of controls. I agree but, why the hell QT and iTunes looks completely different than other ones.

      Fourth point. Drop down dialogs out of captions are not as good as they seem to be. Apple suggests that ok, cancel, etc should be put on bottom of dialog. So you get two ok and two cancel buttons. Without some visible border between.

      Fifth point. They forgot to take in consideration points of no happenings. While Aqua constantly freezes while you're waiting on something, there is no visible progress (at least as I checked out in 20%). This point is very good described in Gnome human interface design.

      Sixth point. Suggested spaces between controls are too big. this forces them to use pager controls. Bad design Steve. On my powerbook, well simple dialog and screen was full.

      Seventh point. Gray is not out. Aqua is not in. As much as I dislike Windows, there at least is option to choose non gray colors. On MOX, well no, it's WHITE. Skin interface rules.

      Eight point. MDI is usable. It's just a point of usage (sometimes yes, sometimes not). Having hundred windows belonging to same application on screen all thrown up there on desktop is not really friendly. This point is nicely addressed in Gnome human interface design.

      Well I could go on and on. But it should be enough.

      --
      Signature Pro version 1.13.2-3 release 83.5 beta3try7 after-breakfast edition
    2. Re:Some good points by Anonymous Coward · · Score: 1, Informative

      As a long time MacOS X user (since the public beta... no the first beta, before 10.0), a longer time Mac user (since the Mac Plus), and a sometime Cocoa developer, I think you made a few mistakes too (see, nobody's perfect... I'll probably make a few right now).

      1) Gray/White/Aqua - While I agree that having White all over the screen can be annoying, gray is worse. Consider two situations: the desktop, and the laptop. If you're using a desktop, you're probably someplace where you can control the amount of ambient light in the room and keep it somewhat consistent. This means you can set the brightness of your monitor so that the white doesn't hurt your eyes. If you're using a laptop, and you're inside, you can do this also. But have you ever tried to use your Powerbook outside, in the sun? There's just no way to get the screen bright enough. Even with the brightness all the way up, I had to squint to see the black on white of the dialogs and windows. If it had been black on gray, I would have packed up and gone home.

      2) Big, pretty, photorealistic icons - Most users want to know they're using a program designed by a professional. Even if it wasn't, they should feel like it was. Cartoon-like icons may be perfect for children's titles, or even some games, but for a real program, the icon for TextEdit is about as cartoon-like as I would want to get. Since the icons all auto-size to either user-preferences or available space, your point about on-screen space is mostly moot. And I'm sorry, but a 128X128 pixel icon, with 24 bits per pixel takes the same amount of time to render to the screen no matter how it was drawn - photorealistically or by hand.

      3) QuickTime and iTunes - All the controls in both of these programs are standard buttons, and sliders, except for the faux-LCD like display that they have in common. The other major difference is the brushed-metal background. I'm sure part of the reason for this is history (both programs existed in MacOS 9, or earlier) and Apple Carbonized them to run on MacOS X and MacOS 9. But you're right, these two programs do kind of fly in the face of the Aqua guidelines.

      4) Drop Down Dialogs - I'm assuming by "drop down dialogs out of captions" you mean "drop down sheets out of dialog windows". If such a dialog ever existed where the sheet and the dialog were the exact same width, and the sheet just happened to cover up everything but the "Cancel" and "OK" button on the dialog below, I haven't seen it yet. But even if it did, only the drop down sheet on top would have a colored and pulsing default button, and there is still the border of the sheet (a 2 or 3 pixel black line with a drop shadow behind it) to differentiate between the two.

      5) "No happenings" - First, huh??? I guess you mean "when a program is busy, there's no progress bar". This is actually a common design flaw in many programs (Windows, UNIX, and MacOS X). I've seen the problem much more often in Widows than the other two though. Apple's Finder uses progress bars for copying and moving files. I agree with you that programs should make better use of progress monitors, but this is an Application design problem, not an overall UI problem. The Aqua guidelines do talk about their use.

      6) Big controls - Consider the fact that both Apple and Microsoft increased the size of their controls in the latest versions of their OS. I can't imagine they would have done this unless there was some research behind it that said "Larger controls gives the user and easier time". But, from my own experience, I know many people who didn't set their display as large as it could go because they would have a hard time reading the menus. If increasing the size of the controls by 10% lets the user add 25% more pixels (1600X1200 instead of 1280X1024), they've just gained usable space, not lost it.

      7) Skinning - While this is a neat option, it is exactly what the Aqua guidelines are trying to minimize: differences in applications. It's maybe not so bad if Photoshop and MS Word have some differences... but if I know how to use MS Word on my Mac, I don't want to have to relearn it just so I can use it on your Mac with a different skin. In my opinion, skinning is the ultimate eye-candy, and generally doesn't add any value to a program. Besides, how could Apple possibly provide support for their programs if custom skins were allowed? When's it a bug in the program? When's it a bug in the skin?

      8) MDI - Windows is the only OS I know of that uses MDI. UNIX doesn't. MacOS doesn't. Java has the option, but I can't think of a program that I've ever seen using it. I recall seeing some research that described how bad it is... maybe Jef Raskin's book "The Humane Interface" would have it? I forget where I saw it though. Basically, MDI limits where you can put your document windows, and can make looking at a document in one application while working in another into a huge headache. MDI promotes wasted screen space, and hides open documents from the user when one document is maximized in the application's window (you have to click on the app, then use the Window menu to bring the document forward). In the end, MDI is probably like the "goto" statement. Sometimes it is useful, but 95% of the time, or more, it's a really bad idea.

      I ran long... sorry folks. I'm not going to say that Aqua is the best interface possible... I hope it isn't, or I won't have much chance of getting a Ph.D. in HCI (I'm starting work on it this fall). All I'm trying to get at is that some smart people, one or two very smart people, and probably a couple of morons too, put a lot of time and energy into figuring out how they could improve the usability of the MacOS. While they're decisions may not be the perfect choices for you, you may not be the common case... and that's who they were trying to design for.

    3. Re:Some good points by 2nd+Post! · · Score: 2

      "Like first. From users point of view, they are addressing that grey is out and they posted completely white screenshot. That could be painfull for eyes. I know I was having troubles with MOX on my Powerbook. Everything is too white and bright. "

      You're right, it might be too painful on the eyes, but Apple doesn't provide a method to modify the default luminance, so for now everything is white and bright; that IS the HIG for the OS X UI.

      "Second point. They are addresing that you need to use big photorealistic icons. Not true. Photorealistic icons are not simple and preety. I agree, first look is gorgeous, but from users point of view, carton like friendly icons are much closer to non-pro user. Second the sizes needed to look cool for photorealistic icons are automaticaly bigger that sizes needed for handdrawn ones. It's the question of on-screen space and memory needed for program. Programs with larger images are automaticaly slower."

      They never said 'photorealistic icons'. To quote: "Your application icons should be vibrant and inviting, and should immediately convey your application's purpose. It is often useful to use a realistic rendering of the media and tool that the application represents or works with."

      So your desire for rich, cartoony, friendly icons do not conflict at all with Apple's guidelines.

      "Thrird point. Constant use of controls. I agree but, why the hell QT and iTunes looks completely different than other ones."

      They claim it's consistent. They have *two* interfaces available in Interface Builder, brushed metal and white, which actually is the same as the difference between the PowerBook and the iBook, isn't it? Anyway, they seem to suggest that anything 'digital lifestyle' should be brushed metal and everything else is white.

      "Fourth point. Drop down dialogs out of captions are not as good as they seem to be. Apple suggests that ok, cancel, etc should be put on bottom of dialog. So you get two ok and two cancel buttons. Without some visible border between."

      Where do they say that you should have two pairs of ok and cancel buttons? What's a caption, btw? Sheets dropping out of dialogs, you mean? They don't suggest that you interrupt a dialog with a sheet, anywhere. Sheets are used in lieu of a dialog when you want to interrupt the user *and* keep the interruption attached to the document, instead of freezing the UI with a permanently on top dialog.

      "Fifth point. They forgot to take in consideration points of no happenings. While Aqua constantly freezes while you're waiting on something, there is no visible progress (at least as I checked out in 20%). This point is very good described in Gnome human interface design."

      The spinning beachball only appears on applications that are busy. Move the cursor off to another application, and the beachball goes away, indicating that the system is still usable.

      "Eight point. MDI is usable. It's just a point of usage (sometimes yes, sometimes not). Having hundred windows belonging to same application on screen all thrown up there on desktop is not really friendly. This point is nicely addressed in Gnome human interface design."

      Hmmm, well, if I recall my history correctly, MDI was designed to correct for the problem that Windows does not have a single menubar interface.

      As another point of contention, having a hundred windows up in the first place... is sort of unusable. A very nice alternative to MDI, I find, is tabbed.

    4. Re:Some good points by justsomebody · · Score: 1, Flamebait

      1) It's painfull if you're forced to have color matching. Your case of using brightness and contrast is out. Laptop on the sun is unusable, white, greay, red or black.

      2) Wrong, I wasn't pointing out rendering time of photo or HDrawn icons. I said that resolution of photo icon is forcing you to bigger icons. Handdrawn icons are made for resolution they are drawn and they are simified to look better on smaller resolutions. Try to size down photo icon and you'll know what I mean.

      3) Not the controls. View design and interface design of these applications. All others are white or white with gray stripes. Qt and iTunes are gray (with texture fill). Look better, don't use laptop on the sun. If they say in their design paper, use this, why don't they.

      4) Not necesarilly everything, there are two ok and two cancel buttons and that's the fact

      5) I guess you don't realise I'm talking about paper, not applications. Paper forgot to mention suggested actions.

      6) You say people don't go where they could. Heh, Why are they selling iBooks with 1024x768. Ever tryed to run MOX on that? I guess people don't all have 22" displays, and yes MOX beggins to be usable at 1600x1200

      7) They made Qt and iTunes skin look different? That's why. But still read my comment. I was talking about selecting colors

      8) I guess you have completely missed representation what MDI is. MDI can be used the way mozilla does. MDI can be pager with options to choose which document.

      Neither am I a moron, and probably neither are you. But if you wanna get your PhD I guess you should better start considering staying at the topic.

      1. Talk is about paper that is describing how to make a software to run on Apple hardware
      2. This paper should make a picture of this systems perfection
      3. System is the first thing that should use that paper
      4. If system is not following this paper correctly, why should others?
      5. All examples I used are Apple designs for MOX and Apple hardware
      6. All you've described is sad reality and lame excuses

      And yes we agree. Aqua is not the best interface.

      --
      Signature Pro version 1.13.2-3 release 83.5 beta3try7 after-breakfast edition
    5. Re:Some good points by DavidRavenMoon · · Score: 2
      Fifth point. They forgot to take in consideration points of no happenings. While Aqua constantly freezes while you're waiting on something, there is no visible progress (at least as I checked out in 20%). This point is very good described in Gnome human interface design.

      This isn't true. First off Aqua doesn't freeze while you are waiting for something. If the task is busy, you get the spinning color disk, and you can move on to another task while you wait. But the Finder in Jaguar is multi threaded, so even if I'm copying 5 files, emptying the trash, and getting info on four other files, I haven't had any spinning disks of death. If it's an action like copying a file, you get a progress indicator. Many applications show either the pre Jaguar "chasing arrows" or the new spinning progress indicator in Jaguar.

      Seventh point. Gray is not out. Aqua is not in. As much as I dislike Windows, there at least is option to choose non gray colors. On MOX, well no, it's WHITE. Skin interface rules.

      I have to agree that OS X (NOT MOX) was too bright in the beginning, but I got used to it. Documents are usualy white anyway, and the window borders dont take up much room. Who stares at the window borders anyway? I look at what I'm working on. Apple doesn't want users to change the GUI. It makes things more consistent, which is what this article is about.

      Eight point. MDI is usable. It's just a point of usage (sometimes yes, sometimes not). Having hundred windows belonging to same application on screen all thrown up there on desktop is not really friendly. This point is nicely addressed in Gnome human interface design.

      If your document window is inside the application window you are stuck having that whole mess on your screen when you want to look at the one document.

      The thing I really like about OS X, as compared to OS 9, is the window interleaving. I can have two different documents on screen next to each other from two different applications, without looking at all the other parts of either apps UI. I do this all the time too.

      --
      -- if it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic - Lewis Carrol
    6. Re:Some good points by justsomebody · · Score: 2

      Spinning disk. I hope you'll sometimes run a recovery or database transaction or something and watch your spinning disk not knowing where you are. What I said is there is no guidelines how and when to handle such actions.

      You know it makes a huge difference of how much white light is facing you. So borders and toolbars are in question.

      MDI is usable, just not as Windows proposed it. Tabbed interface on the other hand is very usefull way of MDI

      --
      Signature Pro version 1.13.2-3 release 83.5 beta3try7 after-breakfast edition
    7. Re:Some good points by Anonymous Coward · · Score: 0

      The real tragedy here is that English is probably your first language.

    8. Re:Some good points by 0x0d0a · · Score: 2

      1) You don't like white all over the desktop. This is a fairly interesting topic, and one that I have strong feelings on.

      There is a strong tradition, dating back from the times when we had only monochrome monitors, or maybe video cards with 16 or so colors, to use fully saturated, high value colors. Use #0000FF if you want a blue. Use #FF0000 if you want a red. Use #FFFFFF if you want white. Users set their monitor to where it's comfortable to have white be the background to an entire window and work away.

      The problem is that this isn't quite right. I have my monitor's white set to sort of a light gray to deal with this -- way too many UI elements require the use of white. Yet this "caps" the monitor at the white of paper. Want to see a sun on the screen? You can't -- it can't get too bright. Same goes for car headlights, etc. In real life, light reflected from paper isn't the brightest white we look at -- yet we've been accustomed since the days of monochrome monitors to have our screen paper color be "full, 100% white". And so we prevent ourselves from really experiencing the dynamic range that our monitors have to offer.

      Furthermore, this is very, very difficult to break away from. #FFFFFF has been used so long in standard UI elements that trying to convince everyone to use, say, #AAAAAA for paper means that people would have to set their monitors to either have old games/software be painfully bright or have their new software look dingy. It may someday be possible by having all windows passed through a realtime brightness/contrast/gamma filter on a per-application basis, but until then, our monitors are not capable of rendering a realistic-looking world.

      2) You dislike big photorealistic icons. I again disagree. These are good ideas. At the moment, these big icons aren't that great. However, screen resolutions keep increasing. Take a look at high end laptop screens, steadily moving down in price towards the consumer. Bitmaps (we still haven't quite hit the vector revolution, though GNOME and KDE both support vector icons) will be smaller and smaller on screen -- already, middle-aged people often complain about "tiny" 16x16 Windows toolbar icons that were quite large back in the day. Apple took an approach of using real-time scaled icons with large master bitmaps. That means that as resolutions increase, MacOS programs will keep looking good, hopefully on through the next decade. At some point in that time, MS is going to have a much rockier time convincing Windows developers to move to larger graphics.

      Also, you may not like photorealistic graphics, but at long, *long* last, computer users can be assumed to be using 32-bit color. The pain and suffering caused to application developers and end users by the least common denominator graphics system being paletted are long gone -- 16 color icons can finally die.

      3) Your third point, that QuickTime and iTunes are not consistent or well-designed, is quite good. Many, many people have complained, and both have earned their places in the Interface Hall of Shame. It's particularly embarrasing that Apple, a major HCI leader at one point, would come up with this unusable, nonstandard crap. This is particularly bad because QuickTime 2 was one of the more impressive Mac UI designs, packing lots of usability into a very small space. QT 3+, OTOH, looked awful and worked worse.

      5) I've seen some good suggestions that windows should have an "unavailable" indicator in their title bar if they're working on something that's blocking the UI. I think there is even a standard window manager hint for this under Window Maker, though I could be wrong.

      Better, of course, would be the at-first-startling ultra-modelessness of the GIMP. The GIMP UI is almost *never* blocked, and there are no modal dialogs. You can flip to whatever window you want and do whatever. At first, some people feel uncomfortable, like the program is giving them too much freedom, but once you get used to it, you never, ever want to go back.

      8) I disagree about MDI being a good idea. It's a hack left over from a UI workaround MS made to avoid the flawed VM in Windows 3.1. People have, unfortunately, gotten used to it. However, if you really want to, you can throw at least Classic MacOS (and presumably OS X) into a systemwide MDI mode where when you open an application from the Finder, the Finder becomes hidden.

    9. Re:Some good points by 0x0d0a · · Score: 2

      5) No happenings.

      MacOS software conventionally (not by Apple dictate, IIRC -- this is not part of the Human Interface Guidelines) uses a "sideways barber pole", a striped, infinitely moving horizontal progress bar to represent an operation in progress with an unknown time of completion.

      I've seen a few tries at this, and of the various sorts, I like the MacOS approach the most.

      Wget, when downloading a file from a server with an unknown file size, "bounces" a few characters back and forth across the screen.

      The MacOS has its "sideways barber pole".

      Windows tends to use animated icons, which I don't much like. They aren't standardized or as immediately recognizable, many of them aren't that obvious, and a lot of the icons are downright ugly -- plus, little objects moving around is kind of distracting.

    10. Re:Some good points by 0x0d0a · · Score: 2

      8)...MDI can be pager with options to choose which document.

      And I've never thought that tabbed interfaces are the greatest idea in the world, either. They don't scale to large numbers of documents, they're *incredibly* annoying if you go to a viewport-based system (a la X with most window managers), and they prevent you from looking at multiple documents at once.

      Dockable tabs are an interesting idea -- you can "tab" and untab documents by dragging them around. However, no PC UI that I know of has a standard set of conventions for doing this from the keyboard, which is a serious drawback.

    11. Re:Some good points by Anonymous Coward · · Score: 0

      You obviously haven't looked at the Aqua UI guidelines. The metalic look of iTunes, QuickTime and other apps in 10.2 is a STANDARD in the current UI guidelines. It's used for single-window applications, things with a real world metaphor, etc.

      Also, a quick look at the icon section would tell you that 32x32 & 16x16 icons should be HAND-DRAWN, not simply scaled 128x128. Aqua's not perfect but it's very good, putting most Windows applications or (lord knows) Open Source apps to shame. I predict the Mac OS X version of OpenOffice.org will have the finest interface. :)

    12. Re:Some good points by justsomebody · · Score: 2

      in fact not, it's fourth and I never sleep bad if I have a bad grammar. If you have a problem with my English, well I have no problem with you having a problem with my English, so I don't bother. ;-)

      --
      Signature Pro version 1.13.2-3 release 83.5 beta3try7 after-breakfast edition
    13. Re:Some good points by DavidRavenMoon · · Score: 2
      Spinning disk. I hope you'll sometimes run a recovery or database transaction or something and watch your spinning disk not knowing where you are. What I said is there is no guidelines how and when to handle such actions.

      Yes, there are guidelines. The spinning disk is just like the watch or hourglass indicators used by other OS's. And in fact applications in OS X can, and should show a progress indicator in their Dock icon. Toast does this when you are burning a CD. BBEdit also has this feature.

      Name a few applications in OS X that do now show a progress indicator while executing a task. I can't think of any. Every application I run on a day to day basis shows progress indicators with such common tasks as opening and saving files, performing an action on files, sending and downloading, etc. Mail even has a mutithreaded task window showing what it's doing at any given monument.

      You know it makes a huge difference of how much white light is facing you. So borders and toolbars are in question.

      Only if you are sitting in the dark, and you should have some low ambient light just for that reason. I have a red flylight keyboard light for this reason. OS X really has no window borders, and tool bars can be collapsed. Use a dark desktop background and you are all set! Or just press Control-option-command-8 in Jaguar. Nice and dark!

      MDI is usable, just not as Windows proposed it. Tabbed interface on the other hand is very useful way of MDI

      A tabbed interface is better that a parent child UI, (such as with Limewire in OS X) but you still have to have the entire application's UI in front of you, even if the document is small. Maybe I want to have a Word document open along side Photoshop, so I can copy and paste text or whatever. This would be a pain if I had to have Word's toolbars follow the doc.

      --
      -- if it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic - Lewis Carrol
    14. Re:Some good points by Etcetera · · Score: 2


      Also, you may not like photorealistic graphics, but at long, *long* last, computer users can be assumed to be using 32-bit color. The pain and suffering caused to application developers and end users by the least common denominator graphics system being paletted are long gone -- 16 color icons can finally die.

      I just hope that this doesn't lead to a garish display of color akin to the Win 3.1 era. One of the cool things about Systems 7-8.1 is that icon designers had a relatively limited but *consistent* pallette to work from. So all icons had a somewhat related look to them (since they were working from the same palette). In OS 8.5 they allowed 32bit icons, but most were just subtle re-shadings of the existing icons with the existing palettes.

      I guess now Apple is aiming for visual consistancy just *form* instead of form and color (aside from the recommendation for Utility icons - all greyscale).

    15. Re:Some good points by Arker · · Score: 2

      I agree with you mostly. But not entirely, of course.

      Quicktime and iTunes, well, you admit they are screwed up, but you discount it. It's a major black-eye to Apple in terms of their credibility with developers when they violate their own rules so flagrantly. QT and iTunes are the motes that Apple needs plucked out of their own eye before they criticise anyone else. Really, they're textbook examples of what NOT to do, and they're flagship applications!

      I also disagree with you, and with Apple, on MDI. MDI has its place, when used properly it's a great boon to usability. I will grant it's easy to misuse (look at excel) but programs where it is appropriate should definately use it. Web browsers are the most obvious example - Opera in windows (sadly the Mac version is not up to snuff yet) or Mozilla's 'tabbed browsing' are great examples, they allow the user to have a number of different browsers open with their own state and content without it becoming such a massive cluttered unusable mess, as it does in browsers without MDI.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    16. Re:Some good points by usr122122121 · · Score: 2
      Thrird point. Constant use of controls. I agree but, why the hell QT and iTunes looks completely different than other ones.
      The Aqua Human Interface Guidelines state that the brushed metal look should be used on programs that are used primarily for "Digital Lifestyle" purposes. QT and iTunes fit that description [well, iTunes certainly does...]
      --

      -braxton
    17. Re:Some good points by 90XDoubleSide · · Score: 2
      What I said is there is no guidelines how and when to handle such actions.

      There are indeed guidelines for long tasks. The system automatically displays the busy cursor if the application the user has the cursor over hasn't been responding to events for at least two seconds, and the HIG covers when you need to use the chasing bars or a progress bar for longer tasks.

      --
      "Reality is just a convenient measure of complexity" -Alvy Ray Smith
    18. Re:Some good points by yasa · · Score: 1
      Second point. They are addresing that you need to use big photorealistic icons. Not true. Photorealistic icons are not simple and preety. I agree, first look is gorgeous, but from users point of view, carton like friendly icons are much closer to non-pro user. Second the sizes needed to look cool for photorealistic icons are automaticaly bigger that sizes needed for handdrawn ones. It's the question of on-screen space and memory needed for program. Programs with larger images are automaticaly slower.


      As a passionate hobby cartoon drawer I have to disagree with you on this point. Yes, cartoon like icons maybe look like it's for children, but IMHO the look of a icon is only the second point. The more important point is to describe what this button does. Cartoons tends to focus more onto the action/situation than the look.Cartoons reduces the action to the most important part of the action, while photorealistic stuff usually has a stronger point in interpretation / imagination than cartoons (which I realy like too, but not in this context). The art of UI-Design is to show the user what's the situation and the possible actions without distracting them from the real work with nifty photorealistic graphics that depends on interpretation.

      - Yasa
    19. Re:Some good points by Dixie_Flatline · · Score: 3, Insightful

      I run OSX on my older G3 powerbook at 1024x768, and I've never felt that I'm out of space because of the controls.

      As for control size, the guy that you responded to has a good point. Control sizes have increased because of Fitts' law, that directly relates control size and distance to the control from your current point to the amount of time it takes the average user to actually hit the control. Windows menus are actually terrible because they're so small, the Apple menubar at the top is brilliant because its effective size, being up against the side of your monitor, is much larger. If you have larger controls (which is a good idea) you probably also want a bit more space between them. Crowding controls together effectively REDUCES their size, because it's too easy to accidentally slop into another one, I problem that I have all the time with Window control buttons.

    20. Re:Some good points by Brat+Food · · Score: 2

      1-brightness
      the UI is the color sceme it is to maintain contrast among the ui elements, and in my experience on a FS imac for a week, it works exceptional in ANY lighting conditions.

      2-icons
      First, the OS was made to handle the large icons, its a neglegable amount of memory these days, and if made well, they scale wonderfully down to 16x16 thanks to OSX's exception scaling algorythems. Also, you will note that apple guidelines change slightly depending on the kind of app.. i wont repeat it hear, but bottome line is - the work. I dont know whay people are scared of good graphic design.

      3-consistancy
      QT, iTunes,iPhoto, iDvd.. notice something in common with all these apps? Really, if you htink for a minute about it, not only are the completly consistant with each other, BUT, they are also a special kind of application. Notice, there is only ONE window containing all the functionality in the app? You wont see Word using the brushed metal interface.... but i can guarentee the next iApp will. They are simeple, single function programs, that are very good at what they do.

      -Fourth point. Drop down dialogs out of captions are not as good as they seem to be. Apple suggests that ok, cancel, etc should be put on bottom of dialog. So you get two ok and two cancel buttons. Without some visible border between. -- i really have no clue what you mean.

      5-taken care of in jaguar. This was a holdover from OpenStep. The icon didnt even change in 5+ years hehe.

      6-if you were less then 1024x768, i wouldnt be running OSX in the first place. Ive never seen something that sounds as obtrusive as what you mention seems to be. Steve got it right- be consistant.

      7- i have ONE thing to say about this... ive NEVER, ever, ever, never, ONCE used a skin for ANY application that made it more useable. And ive tried a lot of skinning.

      8-Well, per your rebuttle, ill say this - tabbed interfaces are not MDI. At least not in the sence that apple refers to it. Apple is clearly against MDI as defined by the windows gui. And it, is a vastly stupid way of working (prolly my BIGGEST peeve about windows)

      OSX gets some stuff wrong, but you mention most of the things they got right.

      --

      "Stuff... In my home!? NEVER!" - Zim on Invader Zim
      "I want the toilet seat!" - Little Dog on Two Stupid Dogs
    21. Re:Some good points by Anonymous Coward · · Score: 0
      Hmmm, well, if I recall my history correctly, MDI was designed to correct for the problem that Windows does not have a single menubar interface.

      Nope. MDI was designed to correct the problem of switching between applications back in Win 3.1 when changing tasks required minimizing windows or hitting alt-tab a bunch of times. MDI reduced the number of alt-tabs and windows that needed to be minimized to view the desktop by grouping windows into one unit.

      P.S. Apple's unified menu system sucks ass. I can't stand it when I try and click a menu item and find its not there because a different application than what I thought was currently active. Also, have you ever logged out only to get a popup window saying you need to close x, y, and z applications-- they are still running even though they have no windows open. Don't get me started about blindly brandishing Fitts' Law either. The menubar at the top may be fast to access, but you get hit when after selecting a menu item and moving the mouse back into the window to continue working. If the menubar is all the way at the top of the screen, disconnected from the application, the use must move the mouse cursor farther than if the menubar was attached to the application, thus taking more time to return the mouse cursor back to the application.

    22. Re:Some good points by 2nd+Post! · · Score: 2

      That's the first good argument against Fitts and single menubars I've heard :)

      On the other hand, a large window makes a much easier target to hit than a small menubar, so that menubar on top + application window should still hold an advantage over menubar attached to window because in the end the user will still have to switch from menu to app in both situations.

      Not all situations, of course.

      Anyway, no, I guess I haven't forgotten which app I'm in; OS X prints the app name in bold in the menubar, so it's sorta hard to not notice. And as for closing apps x, y, and z; they all have active indicators in the Dock telling me they're still around, even with no windows open.

      Besides which... logging out will close all active programs (it'll ask you first of course), so I dunno what the problem is?

    23. Re:Some good points by hype7 · · Score: 1
      I agree with you mostly. But not entirely, of course.

      Quicktime and iTunes, well, you admit they are screwed up, but you discount it. It's a major black-eye to Apple in terms of their credibility with developers when they violate their own rules so flagrantly. QT and iTunes are the motes that Apple needs plucked out of their own eye before they criticise anyone else. Really, they're textbook examples of what NOT to do, and they're flagship applications!


      There is a reason for this. The "brushed metal" interface is available for "digital hub" apps. That means iTunes, iPhoto, QuickTime, etc

      There is an interface standard for it.

      -- james
    24. Re:Some good points by Arker · · Score: 2

      I realise that. And it's not only available to 'digital hub apps' - you can get most applications to use it with some minor hacking.

      It's still a textbook example of what not to do, and a very bad decision from Apple.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    25. Re:Some good points by stux · · Score: 2

      Furthermore, this is very, very difficult to break away from. #FFFFFF has been used so long in standard UI elements that trying to convince everyone to use, say, #AAAAAA for paper means that people would have to set their monitors to either have old games/software be painfully bright or have their new software look dingy. It may someday be possible by having all windows passed through a realtime brightness/contrast/gamma filter on a per-application basis, but until then, our monitors are not capable of rendering a realistic-looking world.


      Hmmm, sounds like exactly the job for QuartGL... erm... QuartzExtreme :)

      You know, the technology where everywindow is rendered as a textured GL quad with GL transparency (and perhaps gamma correction)

      --

      ---
      Live Long & Prosper \\//_
      CYA STUX =`B^) 'da Captain,
      Jedi & Last *-fytr
    26. Re:Some good points by hype7 · · Score: 1
      I realise that. And it's not only available to 'digital hub apps' - you can get most applications to use it with some minor hacking.

      It's still a textbook example of what not to do, and a very bad decision from Apple.


      see, here I disagree with you. You know how consumer "white goods" are almost always white (like fridges and washing machines) but hifi equipment and TVs are almost always black or silver? I think it's the exact same thing.

      Apple has taken a paradigm and applied it to the desktop. Again. It makes sense, when you think about it.

      -- james
    27. Re:Some good points by Arker · · Score: 1

      Oh, we don't disagree that this is what they have done. What you're apparently not grasping, however, is that this is precisely what they've been telling developers NOT to do all along. And, IMOP, they've been right all along. But they can't have it both ways. They criticise, for instance, winamp, and rightly so - but then they build the same mistakes they point out in winamp into QT.

      This is what their designers call a 'consumer interface' and the major problems are two. The thinking behind such interfaces, of course, is that since they are copied from common interfaces outside the computer world, the average person will recognise them and apply their knowledge seamlessly. But this doesn't always happen - the consumer may just as likely NOT recognise the similarities with the meatspace equivelants, since they are symbolic, not actual, and will obviously not be able to transfer the UI knowledge built from the otherwise consistent Mac interface to them, since they don't share that interface either. Furthermore, the interface that copies from meatspace inevitably is limited artificially, since it copies from an interface built in part in response to limitations that don't apply to the computer.

      Of course, QT 4 was the epitome of these mistakes, and the current version has retracted many of them - it does now have a menu bar, and the stupid thumbwheel has been replaced with a slider bar, for instance. Several of the most glaring and unforgiveable errors in the QT 4 design have been quietly retracted, and that's for the good, but if you read this critique of the QT 4 interface with QT6 up to compare with, obviously some of the criticisms are still very valid.

      It's a good thing, of course, that the worst of the problems have been fixed, I was just pointing out, and I think it needs to be said, that Apple is still being quite hypocritical in this case - they are still not practicing what they preach. Every designer thinks they know a better way, and Apple needs to maximise their credibility when they tell them to repress their urges in that regard and make their interfaces standard and consistent - when Apples own interfaces are less than perfect in that regard it just sends a signal to the designers that it's fine to be less than perfect themselves. Which, I would think, is the last signal Apple should really be sending them.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    28. Re:Some good points by jafac · · Score: 2

      MDI is usable, just not as Windows proposed it. Tabbed interface on the other hand is very usefull way of MDI

      - - - -
      So few people remember Compaq's "Tabworks" - an alternate shell interface to Windows 3.11. I loved it - but unfortunately, I think I was the only one. Also, many apps didn't like it very much either, but with a basic set of a few apps, and the Compaq-provided app hooks, it worked great.

      --

      These are my friends, See how they glisten. See this one shine, how he smiles in the light.
    29. Re:Some good points by 0x0d0a · · Score: 2

      Is it really every window?

      I had assumed (again, I'm a bit out of things with OS X) that for efficiency reasons, the background would exist as a quad and only the window being dragged is rendered as a quad.

    30. Re:Some good points by gig · · Score: 2

      > But you're right, [iTunes and QuickTime Player] do kind of fly in the face of the Aqua guidelines.

      No, they don't. The metal appearance is part of Aqua, and can be enabled for any window by the developer, and they quite specifically state that if you are making a single-window media player or an application that calls to mind a device of some sort, then you might want to do your own thing a little more. It's more important for iTunes to look good than for Photoshop to look good, because in iTunes you stare at iTunes, in Photoshop, you stare at your own documents, your own work. Most apps are like a paper and pen: a document and tools and the real magic is what you make with it ... these apps should use standard conventions. Some apps are emulations of some real-world object, like a jukebox, and the real magic is that you can enjoy the same entertaining experience with a software app that you can with a real jukebox (at least this is true for iTunes) and also have digital benefits (like copy the whole library to your iPod and take it with you).

      Also, no matter how "weird" an app might look, Apple always encourages the developer to enable proper drag and drop and such. For example, I can drag a photo from iPhoto to Photoshop's icon in the Dock or Finder and the image is opened in Photoshop. If I drop the photo in the Finder, a new file is created there. There are still conventions being followed, even if the app looks unconventional at first glance.

    31. Re:Some good points by gig · · Score: 2

      There are four icon sizes in a Mac OS X icon: 16 (small), 32 (large), 48 (huge), and 128 (thumbnail). Many developers are still using basically the same 16 and 32 pixel icons that they've always used, but with some higher-quality rendering, anti-aliasing, and sometimes with some kind of Aqua touch like a "gel" color or something. Finder and other apps are smart enough to choose which icon to display based on the situation. They scale down the big image until they get to one of the others and then use that. Works pretty great. You can always find an example of bad icon design if you want to, though. Some developers leave out some icon sizes or make lousy images. Hence, the reason this article was published.

      Also, Mac icons have been 32-bit (24-bit true color image with an 8-bit grayscale mask that defines translucent or transparent portions) for years and years. There's no excuse these days for a user seeing jagged edges ... a modern NVIDIA or ATI card can do better than that. I'm using a PowerBook right now, and everything on the display is done with OpenGL in the graphics hardware. Apple planned ahead on the icons so the platform has icons that better match today's hardware. Guess what? MS didn't. Not surprising.

    32. Re:Some good points by gig · · Score: 2

      > 5) No happenings.

      Cursors have been animated for a long time in Mac OS, so the developer can show a spinning ball for a cursor if they want. There is also two little arrows chasing each other in a circle, which in 10.2 has changed a sort of clock face with no numbers where the lines take turns pulsing. You see it at boot time and at shutdown, too.

      If a Mac OS X app takes more than 2 seconds to do something, the system automatically puts up the spinning beachball cursor.

    33. Re:Some good points by gig · · Score: 2

      > You're right, it might be too painful on the eyes, but Apple doesn't provide a method
      > to modify the default luminance, so for now everything is white and bright; that IS
      > the HIG for the OS X UI.

      Check out "ColorSync". You can change the gamma all you want. Traditional Mac and print default is 1.8, while PC's and TV's are 2.2. If you want all the white on your display to have the brilliance of old newsprint, then you can have that easily. This is THE publishing platform, remember?

      There is also an app called "Black Light" that demonstrates the range of possibilities that are possible with Mac OS X's graphics engine. There are many more levels of processing than what Windows has, so even if you have only one "theme", you can change the colors with a filter applied when the display is composited. In Photoshop, you can spend all day painting new colors into photos with the little bucket, or you can use a filter or blending mode and get the result you want applied to every pixel in the image in one step. Windows is like the little bucket, working hard but not smart, having to have everything prepared before-hand. Mac OS X's UI is called Aqua partially because it is scaling and modifying and compositing and creating the best display it can for you in all kinds of ways. For example, if you put a Classic app in the Dock, the 32x32 icon is scaled up if necessary (there is no 128x128 icon in an old Classic app), and then it is also anti-aliased and smoothed so that it looks more like a regular 128x128 Mac OS X icon. Apple goes the distance to do things right.

      It's unfortunate that the screen captures in this article are so bad. I don't think I've ever seen an all-white desktop on anyone's computer, anywhere, and the desktop is also missing completely from the Windows shot where the desktop icons are sort of floating out there. Mac OS X starts out with the blue swooshy graphic you see on most of the screen captures on Apple's site, and includes about 50 other high-quality desktops, as well as being able to use any picture that QuickTime can understand (which is pretty much all of them), or any photo from iPhoto.

    34. Re:Some good points by gig · · Score: 2

      When you choose a Mac menu, you don't have to crawl up there like MS Windows users do, moving your hand slowly so you can stop on that teensy little MS Windows menu heading. We Mac users "slam" the cursor into the menubar, because you CAN'T OVERSHOOT IT ... it's on the edge of the display. Once you get the hang of this (takes an hour, or a day), you don't even think about accessing the menus, you just think File > Save and your hand does it for you. You sort of flick the mouse cursor up there and all you have to aim is horizontally.

    35. Re:Some good points by 0x0d0a · · Score: 2

      Ah, thanks. I'd been working off Classic knowledge.

    36. Re:Some good points by hype7 · · Score: 1
      Oh, we don't disagree that this is what they have done. What you're apparently not grasping, however, is that this is precisely what they've been telling developers NOT to do all along. And, IMOP, they've been right all along. But they can't have it both ways. They criticise, for instance, winamp, and rightly so - but then they build the same mistakes they point out in winamp into QT.


      it's nice to have these running debates way after the topics off the main page. thanks for the chat, Arker.

      I still dispute that QT6, iTunes, etc has a poor interface, or even a non-standard one. It has a non-standard background - yep, it's silver instead of white (or whatever) - but other than that the interface follows Apple's guidelines and is entirely intuitive (also note, I'm using Jaguar, not Windows. I'm not sure what it looks like with Windows).

      Changing your dvd remote from black to silver or white does not change how easy it is to use (assuming you change the colour of the text as well). I think that's what I'm getting at - people criticise the iApps just because they're metallic. I don't have a problem with that - it's just designating them as a different kind of app IMO

      -- james
    37. Re:Some good points by stux · · Score: 2

      I believe its every window.

      If you think about it, a quad is two triangles... and these game cards these days can output millions of triangles per second...

      Most people aren't going to stress their video card that heavily :)

      The biggest problem will be when you have more textures than will fit in the video cards VRAM (but that is a problem with games too)

      BUT, once you get to that point, there might be some intelligence in the CPU side compositor so that it won't send the textures across the AGP bus if they're completely obscured (or is that already part of the OpenGL spec... I suppose it would be :))

      --

      ---
      Live Long & Prosper \\//_
      CYA STUX =`B^) 'da Captain,
      Jedi & Last *-fytr
    38. Re:Some good points by 0x0d0a · · Score: 2

      ...and these game cards these days can output millions of triangles per second

      Oh, I'm not thinking of trangle rate fill.

      The biggest problem will be when you have more textures than will fit in the video card's VRAM (but that is a problem with games too)

      Yup, I'm thinking of texture memory.

      BUT, once you get to that point, there might be some intelligence in the CPU side compositor so that it won't send the textures across the AGP bus if they're completely obscured (or is that already part of the OpenGL spec... I suppose it would be

      I'm fairly sure that OGL doesn't do that, just because if you wanted to have reasonable latency over-the-network OGL display (remember, SGI made this), you'd really *want* textures to go over when you ask them to do so. And once they're over, they stay over...they don't get resent to the card each frame.

      My objection comes in if you have, say, a bunch of semitransparent windows. A fullscreen window is a lot of VRAM -- 1600x1200x3 bytes = 5.5 megabytes. Most Mac users don't have viewports or pagers or anything, so you're looking at a fair amount of hit. Hmm...still, you're right. That may be low enough that it isn't an issue any more. Scary.

  13. A bit hypocritical... by stubear · · Score: 2, Insightful

    ...for an Apple Dev site to chide "poor" UI designs when their own site needs dome fixin'. For starters, the tips menu items hang over the boundaries of the box beneath them. Also the text is forced to a smaller size than is comfortable to read on screen and by using this size text the bold headline sbecome blurry and even more difficult to read. To be fair, I'm guessing they designed their site to be viewed on Apple systems and there is a difference in screen metrics because Macs are basedon a 72dpi resolution while PCS use 96dpi (though they can be changed to anything from 72dpi-144dpi).

    I'm not even going to get into some of the innacuracies used to make the Mac UI look better or the complete lack of professional advice being utilized. Much of these arguments are based on the premise that "Mac users like it this way" and assuming that the typical Mac user is a UI expert.

    1. Re:A bit hypocritical... by Anonymous Coward · · Score: 0
      Also the text is forced to a smaller size than is comfortable to read on screen and by using this size text the bold headline sbecome blurry and even more difficult to read.
      You really need to learn stylesheets. Any website can be suited to your liking with a personal CSS file. Couple that with Mozilla's minimum font size, and you'll never encounter an illegible website again.
    2. Re:A bit hypocritical... by upstairs · · Score: 2, Insightful

      Much of these arguments are based on the premise that "Mac users like it this way" and assuming that the typical Mac user is a UI expert.
      Remember that this is written for Mac Developers, who do stuff for macs, which the mac user uses.
    3. Re:A bit hypocritical... by DavidRavenMoon · · Score: 5, Informative
      ...for an Apple Dev site to chide "poor" UI designs when their own site needs dome fixin'. For starters, the tips menu items hang over the boundaries of the box beneath them.

      Not on my system it isn't. I'm viewing it in Mozilla, and the text is inside the boxes.

      Also the text is forced to a smaller size than is comfortable to read on screen and by using this size text the bold headline sbecome blurry and even more difficult to read.

      Assuming you are using Windows, I find text is far more legible on Macs.

      To be fair, I'm guessing they designed their site to be viewed on Apple systems and there is a difference in screen metrics because Macs are basedon a 72dpi resolution while PCS use 96dpi (though they can be changed to anything from 72dpi-144dpi).

      That's not the problem. Mac monitors are no longer 72 dpi if you run them at high resolutions. I'm using a 19" Sylvania monitor set at 1280 X 1024. Mozilla's display resolution is 96 dpi, same as on PCs. IE also defaults to 96 dpi.

      The real issue is not screen resolution, but the size of fonts on Windows.

      A 10 pt font is expected to be 10 points. There are 72 points to an inch (or 2.54 cm). Windows fonts are too large, with 10 points closer to 12 points. I know this because I work in pre-press. This is why the text on websites made on PCs often looks too small on Macs, and vice versa.

      --
      -- if it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic - Lewis Carrol
    4. Re:A bit hypocritical... by foo12 · · Score: 1

      To be fair, I'm guessing they designed their site to be viewed on Apple systems and there is a difference in screen metrics because Macs are basedon a 72dpi resolution while PCS use 96dpi No, they aren't. Mozilla (and derivates), Explorer, OmniWeb, and iCab all ship with defaults set to 96 ppi.

    5. Re:A bit hypocritical... by gig · · Score: 2

      > "Mac users like it this way"

      That's the whole point of the document. There may be 10 correct ways to do one thing, but if in the Mac community they decided on one way of doing a particular thing 20 years ago, then it's good to know that BEFORE you go in there telling them that GNOME is GUI done right. There are all kinds of parties, and although you CAN wear absolutely anything you want to any party, even nothing, or a crazy costume, if you know what you are expected to wear, then you at least will know what kind of reception you will get when you get there. What Apple is saying here is that the Mac is a formal party, and most apps wear black tie. If you want to show up dressed as Superman, then that's great, but expect to have more people ask you why you're dressed that way than if you were at a costume party. Now, if you ARE Superman, and then you can go to a formal party dressed as Superman then you are totally doing the right thing. Exceptions prove the rule.

    6. Re:A bit hypocritical... by schvenk · · Score: 1
      Much of these arguments are based on the premise that "Mac users like it this way" and assuming that the typical Mac user is a UI expert.

      No, the arguments are based on the premise that "Mac users will expect it this way," which is the whole point of the document. Any GUI has a set of user interface guidelines to ensure consistent user experience and look & feel. Mac users expect their apps to look like Mac apps, just as Windows users expect theirs to look like Windows. The typical Mac user may not be a UI expert, but he'll notice if one of his apps doesn't act like the rest.

  14. lefties by oliverthered · · Score: 1

    I once had 'ONCE', a cooker that could only have been designed by a left handed person.

    the dials were left handed (clockwise i think), and the four dials didn't operate the expected plates on the hob.

    As you can imagine, a could of nobs were broken by somoen turing them the wrong way, and somone finilly killed the cooker by turning on the wrong hob plate and setting somthing alight (no more cooker).

    --
    thank God the internet isn't a human right.
    1. Re:lefties by Anonymous Coward · · Score: 0


      I have no idea what any of that means.

      help.

    2. Re:lefties by oliverthered · · Score: 1

      What it means is that someone designed a cooker that worked for them, but apparently didn't look at all the other cookers to see how they worked. because the nobs were in un-expected possitions and they turned clockwise instead of anti-clockwise.
      The userinterface to the cooker was un-expected to the effect that somone turned on the wrong hot plate and set it alight!

      --
      thank God the internet isn't a human right.
    3. Re:lefties by gig · · Score: 2

      I think he's responding to the guy who pointed out that his kitchen appliances all had different controls ... stove and toaster, etc. This post makes the point that certain conventions are still being followed, such as turning a knob clockwise to increase a setting. A knob that goes the "wrong" way is not another kind of control altogether, just a faulty knob.

      Do the expectations of the users matter, or do you just sit there and design in a vacuum? If you think of the users, it will be a cinch to use the standard Mac conventions that they already know and let the user get IMMEDIATELY on to utilizing the distinctive features and functionality of your software.

      On the PC, there are like 10 ways to do everything (IBM vs. MS vs. Apple key shortcuts, for example), while on the Mac there is often only one way that's been agreed upon long ago. What Apple is saying is that before you introduce a second way, make sure that you have examined the value proposition from the perspective of a user who has been hitting Command+P to Print from their GUI apps for almost 20 straight years. These conventions are just as valuable as "/" and "|" are to command-line UNIX. Just as MS turned "/" to "\" they also turned Apple GUI stuff into Windows. It's the same method for cutting out actual design or innovation: take someone else's work and modify it just enough to call it your own and then sell it cheaper, or give it away, and make more of a profit because you didn't have to actually pay to invent it or build it or design it or test it.

  15. #5 Menu Bar is enough reason to not change by jtaylor72 · · Score: 0, Flamebait

    I have switched to Mac, from Windows, and I'll tell you one of the reasons I might switch back is that single Menu bar. It is so annoying to have a window open on the lower half of the screen, or on a second screen on my dual monitor setup, and have to navigate all the way to the top left of the screen to get to the menus. I don't know how Apple can think this is better. This and the fact you can only resize a window in the bottom right have to be two of the most annoying things about an apple, enough that I will probably sell this crapintosh on eBay and buy 3 pcs with the money.

    1. Re:#5 Menu Bar is enough reason to not change by moshek · · Score: 4, Informative

      Apple has found that using one menu at the very top increases productivity. "What? You're crazy!" you say. No seriously, the theory is (and it is not Apple's theory, they just adhere to it) is that in order to get to a menu item a user can simply throw their cursor to the top of the screen and 'overshoot' the menu because it is at the very top, in this sense the menu is located at a place of infinite height and is very easy to get to. Now think about a Windows setup where the menu is at the top of any respective window, a user must provide a bit of care/control to get to the menu item because it is possible to overshoot the menu. It doesn't take EXTREME care, it is a minor point, but even with distance and proximity involved (menu at top of screen vs. menu at top of window), you'd have to agree that it is easier to simply 'throw' your mouse to the top of the screena and not worry about overshooting it.

    2. Re:#5 Menu Bar is enough reason to not change by Psiren · · Score: 2

      I agree to a point, I've never been a fan of it either. The one good thing about it though, is that you can just shove your mouse pointer to the top of the screen and you'll *always* be on the menubar. Having to aim for a specific area in a window does take longer.

    3. Re:#5 Menu Bar is enough reason to not change by big.ears · · Score: 5, Informative

      The decision was made because of considerations about aimed movement, which was originally codified as a mathematical relationship by Paul Fitts, who stated that times for aimed movements were related to the distance and size of the target in a logarithmic fashion. "Fitts's Law" is not about infinite height, however. It is about the mathematical relationship, and for any new application of the law, the coefficients of the formula need to be estimated. These coefficients will depend on many things, including the acceleration and rate settings on the mouse, the experience of the user, and probably things like how bright things are, the color scheme, how big the monitor is, and how far they are away from the monitor. Thus, it may be possible that in the days of black-and-white ten-inch monitors with big clunky mice, the parameters of Fitts's Law worked out so that you would get an advantage for edge menus. In todays world, with optical mice, 21" LCD displays, multiple monitors, and mouse acceleration, the parameters would be different, and there may no longer be an advantage for edge menus. And if you change your mouse rate, you might just negate any benefit for these menus as well. Of course, the formula is also affected by target size, meaning that the larger icons probably do more for 'productivity' than anything else.

      The point is that the research and user testing this design decision was based on is from a different age and time. To believe that it is still a good decision, one would have to show that today's users with today's technology have an advantage. This must be done empirically, because without such testing, we are all just speculating.

    4. Re:#5 Menu Bar is enough reason to not change by Golias · · Score: 2, Insightful
      I found that most Windows switchers enjoy their new Mac more when they pick up a multi-button mouse. (The Microsoft Intellipoint, or whatever the hell it's called, is probably the best out there, but Kensington and Logitech make some good ones if you are an MS hayta'). Windows users have conditioned themselves to right-click for contextual menu functions. Most of the time, and OS X lets you do so. (ctrl-click or click-and-hold does the same thing as a right-click, if you like the "buttonless" Mac mouse.)

      On the other hand, if you just let yourself get used to the idea that everything you need to do is on the top of your screen (and always in the same order: Apple, Application, Edit, View, App-specific stuff, Window, Help) you might find that Mac users worship the top menu concept for a reason. It makes your life easier, in the long run.

      --

      Information wants to be anthropomorphized.

    5. Re:#5 Menu Bar is enough reason to not change by justsomebody · · Score: 2

      Here is one example where they've gotten it wrong. Having two 22" monitors. Traveling to menu bar from second monitor ... ... ... it's aaa looooong waaaaay toooooo goooooo.

      And if I'm not wrong. Most of my Mac users have two monitors. I have four on Xinerama on my Linux workstation, so personaly I can't imagine my self travelling all the way to menu bar. It would be the same as buying airline ticket to select a menu or a lot of 'throwing' in the next room.

      --
      Signature Pro version 1.13.2-3 release 83.5 beta3try7 after-breakfast edition
    6. Re:#5 Menu Bar is enough reason to not change by Enonu · · Score: 2

      The point is moot since everywhere else, which is probably 9 times out of 10, you have to aim. Simple as that. If a user doesn't have the dexterity to aim without thinking about it, he or she shouldn't be using a computer, or perhaps even driving or using public restrooms. I'm serious.

    7. Re:#5 Menu Bar is enough reason to not change by Anonymous Coward · · Score: 0

      I use both platforms all the time and I don't have a problem with the menu being at the top of the screen. The menu is for low-frequency tasks anyway and I usually just use keyboard short-cuts.

    8. Re:#5 Menu Bar is enough reason to not change by Anonymous Coward · · Score: 0
      Apple has found that using one menu at the very top increases productivity.

      They found that out 20 years ago using a tiny 7" screen and a GUI that only allowed one application on the screen at the same time, with test subjects who had never been exposed to a WIMP interface before. I would have to say that research simply does not apply in current times where multitasking operating systems are standard, all current GUIs display more than one application at a time, and even the cheap 15" displays support 1024x768 pixels of screen resolution. The single menu bar is an annoying relic.

    9. Re:#5 Menu Bar is enough reason to not change by droleary · · Score: 2

      To believe that it is still a good decision, one would have to show that today's users with today's technology have an advantage.

      Now that you mention it, I do notice that when I go up to the menu, my mouse is more often at the very top of the screen than elsewhere in the menu. I also recall that the Dock used to have a 1 pixel "edge" in an early incarnation of OS X, but they pushed it all the way to the edge because of the number of user complaints. It seems clear to me that the Apple advantage is still there.

    10. Re:#5 Menu Bar is enough reason to not change by dalamar70 · · Score: 1

      Ha I must be the only doofus in the world who consistently undershoots the top menu bar. I probably shouldn't even be admitting this in public. Haven't adjusted to the iBook trackpad yet I guess. Anyway if I undershoot but accidentally click, then usually some other app becomes active (I most commonly end up clicking in the desktop, making the Finder active) and its menu bar takes over from the original app. Then I have to mouse back down to the Dock, or to ASM on the right, or install FruitMenu, or hit Command-~ just to get back to the original program. That's my (opposite) annoyance with top menu bars...

    11. Re:#5 Menu Bar is enough reason to not change by ejaw5 · · Score: 1

      must be just a matter of opinion. I see the single menu bar as somewhat counter-productive. I've used Macs on occasion, and it gets annoying because I have to ensure the correct window (if you call it) is on Focus before navigating the Menu. Ever try saving a document, only to find out you got another window selected instead? I *THINK* KDE (2.2) had an option of a single top menu, and it wasn't for me.

      --

      $cat /dev/random > Sig
    12. Re:#5 Menu Bar is enough reason to not change by tgibbs · · Score: 2

      The consistent menu bar at the top of the screen is probably the single aspect of the Mac interface that I most appreciate. When I want a menu, I don't even have to look for the appropriate menu bar--I just whip my mouse up blindly, and I know that the pointer will end up in a menubar that is appropriate for the window that I was just working in.

    13. Re:#5 Menu Bar is enough reason to not change by tgibbs · · Score: 2
      In todays world, with optical mice, 21" LCD displays, multiple monitors, and mouse acceleration, the parameters would be different, and there may no longer be an advantage for edge menus.

      Nope. Still works. Even with the largest monitors, Apple's mouse acceleration parameters are such that a flick of the wrist puts the pointer instantly in the menubar from anywhere on the screen.

    14. Re:#5 Menu Bar is enough reason to not change by Juggle · · Score: 1

      Thank God...I was afraid I was the only one.

      It took me a couple of years of forced mac use in college before I realized this one my #1 complaint about the single top menu bar. I knew I hated it just couldn't figure out why.

      The problem is if you misclick all the rules suddenly change - at least in OS's with menus within their respective windows everything dosen't shift on you.

      The single menu works OK if you're not multi-tasking (like original macs) but once you start running multiple apps simultaneously (something most mac users still don't seem to do probably because the OS makes it inconvienant) it's a MAJOR burdon and creates a LOT of confusion.

      I've seen quite a few experienced and inexperienced users trying to figure out what happened after misclicking on a mac.

      --
      --- Juggle juggle@hitesman.com
    15. Re:#5 Menu Bar is enough reason to not change by tgibbs · · Score: 2
      If a user doesn't have the dexterity to aim without thinking about it, he or she shouldn't be using a computer, or perhaps even driving or using public restrooms. I'm serious.

      It's not a matter of consciously thinking about it. Even if it goes on at a subconscious level, hitting a particular point takes more cerebral processing time than simply snapping to an edge. In fact, it is the unconscious nature of the processing that makes it insidious--because we aren't aware of "aiming," we don't perceive how much it slows us down, although objective tests show it.

    16. Re:#5 Menu Bar is enough reason to not change by Kevon · · Score: 1

      I was going to respond that it didn't sound that convenient to me, but then I remembered that this is just one of those personal preference things that some people will like and some will not, so why try to convince someone they're wrong.

      So oh well, another long, thoughtout email cancelled after being typed...

      I say...Enjoy your top of screen menu if you want!!!

      Kevin

    17. Re:#5 Menu Bar is enough reason to not change by madmancarman · · Score: 2
      Apple has found that using one menu at the very top increases productivity. "What? You're crazy!" you say. No seriously, the theory is (and it is not Apple's theory, they just adhere to it) is that in order to get to a menu item a user can simply throw their cursor to the top of the screen and 'overshoot' the menu because it is at the very top, in this sense the menu is located at a place of infinite height and is very easy to get to.

      I've had the (dis)pleasure of training a lot of the staff members in our school district to use our collaboration software, for which there are Mac and Windows versions (and soon, a Linux version!). Whenever I tell them to use a certain menu (i.e., the "Connection" menu to change their password), people using Windows look all over the screen to find out which window they're in, where the menu bar is, etc. On the other hand, Mac users always instinctively look to the top of the screen and find the proper menu, where it always was and always has been.

      The breaker in this deal, however, is how Mac OS X changes the standard Mac UI to get rid of the application menu in the upper-right corner of the screen in favor of an application-specific menu in the upper-left corner of the screen (next to the now-nearly-useless Apple Menu). This makes it only slightly less obvious which application you're currently running, although Aqua uses lots of subtle hints to try to make it stand out (putting the new application-specific menu in bold, making all of the other window title bars in the background slightly translucent, adding drop shadowing to windows). I wish they'd just make the active application icon pulsate or glow in the Dock - then there would be no question.

      Anyway, if you ever wonder why User Iterface guidelines seem so silly and written for the lowest common denominator, you should spend some time teaching computer-illiterate people how to drag-and-drop an attachment onto an email message. The more consistent the UI, the better.

      First they ignore you, then they laugh at you, then they fight you, then you win. -- Gandhi

      --
      First they ignore you, then they laugh at you, then they fight you, then you win. -- Gandhi
    18. Re:#5 Menu Bar is enough reason to not change by arn@lesto · · Score: 1

      Appple assumes that the mouse has only one button. In that case a single menu at the top of the screen might be more productive.

      Two buttons allows instant access to a menu without moving the mouse. If this was standardized like the menu bar layout then I would expect the right mouse button menu to be much faster than the one menu at the top.

      --
      - AndrewN
    19. Re:#5 Menu Bar is enough reason to not change by Anonymous Coward · · Score: 0

      yes!

      NeXTSTEP optionally made it possible to use the second mouse button to open the application menu right in place and navigate through it. The menu was organized vertically rather than horizontally. Very very very conveniant. I miss it so much...

      Raph

    20. Re:#5 Menu Bar is enough reason to not change by dalamcd · · Score: 1
      Right-click (or control-click) opens a contextual menu. i.e., it opens a menu in context to what has been clicked. If you right-click on a word or a selected sentence, it would bring up a menu for copy/paste, spelling, etc. Right-click on a lick in your web browser, it might bring up different ways to follow the link.

      Some of these are in the menu at the top of the screen, some aren't.

      Either way, contextual menus don't replace the main menu.

      dalamcd

      --
      moer liek CELtroid prime!!@1!
    21. Re:#5 Menu Bar is enough reason to not change by daffmeister · · Score: 1

      And in an astounding piece of dumbheadedness, Windows retains that one pixel edge in a few places.

      Maximize a windows (IE will work) and move to the slider on the right-hand side. You have to carefully move in a couple of pixels from the edge to hit it.

    22. Re:#5 Menu Bar is enough reason to not change by jimbolaya · · Score: 2
      Microsoft realized you quite often need a single, application-wide menu bar, and thus, the God-awful MDI was born. MDI is perhaps the most annoying thing ever to come out of Microsoft. Apple's article points out flaws with this approach, including having window sizes confined by the parent window. Further, one of the advantages of Windows, that is now available in Mac OS X, is that you could easily display one window from one application, and another window from another window. However, MDI negates this, because the MDI parent window essentially takes over the screen. Most people I see using an MDI application, such as one of the Office, maximize the application. If they want to view something in Word, say, while simultaneous viewing something in Excel, they have to go through awkward resizing of parent and children windows.

      What does this have to do with a single menu bar? The MDI parent window is there primarily as a container for the application menu bar (and perhaps to hold a bevy of toolbars, which Apple rightfully dismisses). It's also there because a non-MDI application in Windows does not remain running when there are no open documents. In Mac OS X, this is no problem, since the menu bar itself indicates which application is in the foreground.

      If what I say doesn't make sense to you, hold on to that Mac for a bit longer before you hawk it on eBay. I'll bet you will grow to appreciate the benefits a shared menu bar provides.

      --

      There ain't no rules here; we're trying to accomplish something.

    23. Re:#5 Menu Bar is enough reason to not change by overunderunderdone · · Score: 2

      "Fitts's Law" is not about infinite height

      No I suppose not directly BUT that "infinite height" obviously has the advantages of large size that (more than? partially?) compensates for the lack of proximity under Fitt's law.

      It is certainly not emperical research but I just spent a few minutes experimenting with hitting screen-top menu items as opposed to window-top menu items (the home and back buttons on my browser) And I played around with my mouse settings. I found that unless my mouse was set to be quite slow or I was at the very bottom of the screen a single careless flick of the wrist got me onto the top menu and usually right onto the menu I was aiming for. By contrast unless I was painfully slow and deliberate in my movements I always overshoot the window-top buttons which take up twice as much screen real-estate. And if my window was near the top of the screen (where they usually are) that overshot was almost always onto the screen-top menu bar (recalling the billboards saying - "if you lived here you'd be home by now")

      Changing my mouse settings to be much "slower" than I usually set them or disabling acceleration I did lose much of the advantage of a screen-top menu. It took two or more mouse movements to hit the top menu bar. The slow speed also seemed to help a little in not overshooting the window-top elements. So certainly mouse settings & screen size could destroy any "Fitt's law" size advantage the screen-top menu has by making the proximity effectively much farther away. However for me at least the easiest of all combinations was to hit a screen-top menu with the mouse configured fast enough to do so. I found a mouse that was set so slow as to decrease the edge menu's "proximity" enough to negate the edge menu's "size" advantage was also inconvenient on a large screen for other reasons. I suppose If you are using a large screen for many different apps that you are NOT working with at the same time - each one in it's own quadrant there might be advantages to setting you mouse slower and having all your menu's at the top of each window. My guess is that this is a relatively rare way of using computers but I could be wrong, my own use of a large screen is so I can use all of that screen at once not a piece of it at a time - a situation for which multiple smaller monitors seems better suited than a single large monitor.

      I don't have multiple monitors at the moment BUT I think this is the one scenario that Apple does NOT address well. But that has nothing to do with the placement of the menu bar at the top of the screen but that it is only at the top of ONE of the screens - duplicating the screen-top menu at the top of each screen would work nicely.

    24. Re:#5 Menu Bar is enough reason to not change by gig · · Score: 2

      >> Apple has found that using one menu at the very top increases productivity.

      > They found that out 20 years ago using a tiny 7" screen and a GUI that only allowed one
      > application on the screen at the same time, with test subjects who had never been exposed
      > to a WIMP interface before. I would have to say that research simply does not apply in
      > current times where multitasking operating systems are standard, all current GUIs display
      > more than one application at a time, and even the cheap 15" displays support 1024x768
      > pixels of screen resolution. The single menu bar is an annoying relic.

      Apple quite publicly remade itself between 1997 and today. Mac OS X is a complete rewrite. I am sure the single-button mouse and single menubar were the subjects of many conversations and much research and demonstration inside Apple between then and now. What went on in the 1980's may still be important to you, but I doubt it had too much influence on Steve Jobs et al as they planned Apple's place in the world in the 21st century. Steve Jobs was fired from Apple in 1986, remember? He left with Apple's "Big Mac" project and turned it into NeXTSTEP. For the single menubar to survive the OpenStep > Mac OS X transition means it must have impressed somebody recently. They didn't do all this work to get to now and suddenly say "oh, shit, the MENUBAR! How did we miss that?". If you've USED both methods, the Mac way will likely feel better to you. It's also AMAZING for newbies (you teach them where the File menu is ONCE) and right now most of the world barely qualifies as newbies when it comes to computers.

      I don't buy that there's a single thing in Mac OS X that isn't either how Steve wants it or it is on its way there. You can say you don't like it, but I don't think you can say it has anything to do with the 1980's. All the widgets and controls changed their appearance between 10.1 and 10.2 ... so much has changed in the last few years that I can't believe there was any impassable technical obstacle that kept them using a single menubar. The Mac didn't really used to have toolbars, and now there is a standard toolbar available for any window to use ... couldn't they have provided a menubar there, too? An optional one, maybe? I really don't think anything stopped them from going with multiple menus except that it is not better in real use. When I see someone working on Windows today they look very cautious in their mousing to me ... they are carefully targeting everything, they are looking a lot and waiting and then clicking ... they are not operating in the intuitive, playing-a-musical-instrument way that I and others do on our Macs.

    25. Re:#5 Menu Bar is enough reason to not change by gig · · Score: 2

      When my wife switched to a Mac, she got a two-button mouse and tried to do all the same things as in MS Windows until I told her that all of the commands are just in the menus at the top. She expected that only some commands would be there and some wouldn't. She started using a one-button mouse and going to the menus for every command and she was much faster and happier with that. You don't have to pick a method first, and the mouse hand just points and clicks so it gets a "mind of its own" (our hands have more brains in them than many animals, actually) and the cursor starts to seem like it just appears in the menubar when you want it. She is totally disinterested in context menus and key commands now. It's all menubar and drag and drop, which were both invented by Apple and were both in the original Mac.

  16. and the difference is... by Anonymous Coward · · Score: 0, Informative

    Windowws XP has an option to turn the faggish appearance off.

    God damn, this is like the 3rd Apple story this morning. Can Slashdot PLEASE remove its lips from Steve (Blow)Jobs dick?

    1. Re:and the difference is... by MoneyT · · Score: 1, Flamebait

      Once again with the sad and pathetic attempts by lonely dead ednd slashdot posters to associate sexuality with a computer. TH emore I see these posts, the more I think it's a reflex of die hard Wintel weenies to deny that it's actualy becoming cool to once again own a mac.

      --
      T Money
      World Domination with a plastic spoon since 1984
  17. They Forgot.... by joel8x · · Score: 1

    They forgot to mention that OS X does not have the most confusing design flaw of Windows: In order to shut down, you need to go to "Start" then "Shutdown". Mentally its like telling a driver "In order to turn off your vehicle, step on the accellerator" (previous versions of Mac OS had the similar design flaw because to shut down you had to go to the "Special" menu, which to me didn't make much sense either - OS X is the most sensible of all - much like Gnome & KDE).

    --
    Sound waves should be free!
    1. Re:They Forgot.... by TheSunborn · · Score: 2, Funny

      Am I really the only one who think that it make sence to "start a shutdown" ?

      Martin Tilsted

    2. Re:They Forgot.... by Powercntrl · · Score: 1

      I always think of it as the dialog from Spaceballs.

      "Driver, prepare to move out."
      "What are you preparing for? You're always preparing, just go!"
      "Just go. Sir, shouldn't you sit down?" (Said just as darth helmet falls into the seat)

      So "prepare for shutdown" makes sense... Now having a "Stop" button exclusively for shutdown would just be a waste of screen real estate. Not that it matters anyway, a properly configured PC will start the shutdown process when you press the ATX power button on your case. :)

      --

      ---
      DRM is like antifreeze, to the MPAA/RIAA it's sweet, to the consumers it's poison.
    3. Re:They Forgot.... by greenius · · Score: 1, Troll

      This is to match the equally confusing "Press ctrl-alt-delete to login" to some versions of Windows NT.

      --
      I copied this sig from someone else (but where did they get it from?)
    4. Re:They Forgot.... by Anonymous Coward · · Score: 0

      They forgot to mention that OS X does not have the most confusing design flaw of Windows: In order to shut down, you need to go to "Start" then "Shutdown".

      Please spare us your "everyone's an complete idiot" argument...

      It's not as counter-intuitive as you claim.

      You only have to figure this out once.

      Clueless users typically watch the tutorial.

      Anytime you press "Start", you see the word "Shutdown" as an option.

      You can also shutdown by hitting ctrl-alt-delete.

    5. Re:They Forgot.... by Anonymous Coward · · Score: 0

      Yes i'm with you, it's easy to make a joke but it makes perfect sense, Start is not as in turn on, it's as in start to do something, "start to shutdown" "start a program" if there is something you want to do you have to start someplace, as it is you go to the start button to start to do things. Makes a ton of sense.

    6. Re:They Forgot.... by Lars+T. · · Score: 2

      Actually, this all makes me want to throw My Computer into the Recycle Bin - but they won't let me.

      --

      Lars T.

      To the guy who modded me down from perfect to terrible Karma - Apple haters still suck

    7. Re:They Forgot.... by chippcom · · Score: 1

      Oh, and dragging a disk to the trash can to eject it makes perfect sense...

    8. Re:They Forgot.... by joel8x · · Score: 1

      I just don't agree with calling the button "Start". It would make more sense to be like KDE or Gnome, who have the same kind of button, but its not called "Start". Why not the Windows button (would make more sense of those windows buttons on the keyboards).

      --
      Sound waves should be free!
    9. Re:They Forgot.... by CrTwentyFour · · Score: 1

      In Apples defense, they did fix that in OS X. When you drag a disc or disk image, the trash icon changes to a stereo/vcr style "eject" icon.

    10. Re:They Forgot.... by DavidRavenMoon · · Score: 2
      I just don't agree with calling the button "Start". It would make more sense to be like KDE or Gnome, who have the same kind of button

      Or Apple? Let us not forget where this came from... the Apple Menu, which is where you shutdown and reboot in OS X.

      --
      -- if it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic - Lewis Carrol
    11. Re:They Forgot.... by DavidRavenMoon · · Score: 2
      Oh, and dragging a disk to the trash can to eject it makes perfect sense...

      You can still do this, but you can also press Command-E for eject, choose Eject from the File menu, or press the Eject toolbar button, if you added one.

      The point is that you are unmounting a volume, not putting the contents in the trash. Once new Mac users got past the first instance of dragging a disk icon to the trash they knew what it did. I think Apple leaves it there because old timers are used to it.

      It also makes no sense to drag a DiskBurner CD icon to the trash to burn the disk, but the icon does change to show its state, so it's really no longer the trash.

      --
      -- if it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic - Lewis Carrol
    12. Re:They Forgot.... by cscx · · Score: 2

      Umm, that's in all versions of NT, including 2000 and XP. (Not sure about 3.51 though.)

      The reason for that is to keep your password secure. Let's say someone is running a "fake" login dialog box that will capture your username/password. Well, they can't because ctrl-alt-del is written into the keyboard driver, WinNT always intercepts it, so NT's dialog box will be the only program that can be activated by ctrl-alt-del. Make sense?

    13. Re:They Forgot.... by Anonymous Coward · · Score: 0
      In Apples defense, they did fix that in OS X. When you drag a disc or disk image, the trash icon changes to a stereo/vcr style "eject" icon.

      Now that's just the kind of confusing modal interface that their own guidelines warn against. They haven't fixed anything, they just changed one senseless interface to a different senseless interface. Thankfully, Apple keyboards have an eject button, so at least there is an alternative interface that makes sense for physical media. But the issue is still there when it comes to disk images, which by themselves are hopelessly confusing for newbies.

    14. Re:They Forgot.... by Anonymous Coward · · Score: 0


      You have obviously never used OSX. When you select a disk, the trash can changes to an eject icon.

    15. Re:They Forgot.... by Anonymous Coward · · Score: 0

      "It would make more sense to be like KDE or Gnome..."

      Yeah. Cause Foot->Shutdown or K->Shutdown makes a lot more sense.

    16. Re:They Forgot.... by Anonymous Coward · · Score: 0
      Am I really the only one who think that it make sence to "start a shutdown"?

      What, is somefink rong wif "initiating shutdown"?

    17. Re:They Forgot.... by gig · · Score: 2

      The reason for that is to keep your password secure. Let's say someone is running a "fake" login dialog box that will capture your username/password. Well, they can't because ctrl-alt-del is written into the keyboard driver, WinNT always intercepts it, so NT's dialog box will be the only program that can be activated by ctrl-alt-del. Make sense?

      That's the excuse, not the reason. The reason is that the PC's firmware is decades old in some places and can't prevent a false login box. Open Firmware (IEEE 1275) on Apple, Sun, and other machines doesn't suffer from this problem.

  18. Nothing new by psicE · · Score: 2, Flamebait

    In addition to this being common knowledge among Apple developers well before now, everything said here was said better by MacKiDo. Take a read here. It describes very well how the Mac interface is better than just about any other.

    Of course, if you go to MacKiDo's main page, you'll also notice an introduction note; in summary, it says that OS X was a mistake, as Apple's primary focus is no longer on the UI. And you know what? I couldn't agree more. Say all you want about OS X bringing Unix to the masses, but the fact is, the masses would have been better off without Unix. OS 9, despite having less eye candy than OS X, was architecturally better for the home user in just about every way than OS X - the only significant development X had was Cocoa, and that could easily have been ported into an OS 9 upgrade instead.

    By switching to OS X, Apple threw out 15 years of hard work, just to release an OS with an inferior UI on an inferior kernel. And their interface in many ways no longer follows the principles that Apple themselves set out so brilliantly back in 1984, and others tried to emulate with varying degrees of success (don't even get me started on the Dock).

    I still love the PPC platform; it's no Alpha, but it is the most popular RISC platform for the desktop. IBM, at one time, had the CHRP platform; it was the PPC answer to x86's open hardware, and it would have allowed a PC user to upgrade to PPC by simply throwing a new motherboard and processor into their existing case using their existing components and peripherals. If IBM releases their new Power4 processor for CHRP, I'll be the first to buy it, and install PPC Linux. And if the planets are all in alignment, and Apple decides to design OS XX based on a completely new design, scrapping all development environments but Cocoa and going back to the old OS9-style user interface, then I'll buy a Mac.

    But there's absolutely no point in buying a closed platform when the software, specially designed for that platform, sucks. At least with PCs, I can run BeOS on a laptop; with Macs, such is no longer an option.

    1. Re:Nothing new by banky · · Score: 5, Insightful

      >By switching to OS X, Apple threw out 15 years of hard work, just to release an OS with an inferior UI on an inferior kernel.

      Yes, a kernel that rarely crashes is indeed inferior. Likewise, a kernel that allows developers to build applications based on standards is a poor choice.

      --
      ZOMG I WOULD LOVE TO KNOW ABOUT YOUR FEELINGS ON MACINTOSH VERSUS WINDOWS, VI VERSUS EMACS, AND HOW YOU'RE NOT A DORK
    2. Re:Nothing new by thatguywhoiam · · Score: 5, Insightful
      Of course, if you go to MacKiDo's main page, you'll also notice an introduction note; in summary, it says that OS X was a mistake, as Apple's primary focus is no longer on the UI. And you know what? I couldn't agree more. Say all you want about OS X bringing Unix to the masses, but the fact is, the masses would have been better off without Unix. OS 9, despite having less eye candy than OS X, was architecturally better for the home user in just about every way than OS X - the only significant development X had was Cocoa, and that could easily have been ported into an OS 9 upgrade instead.

      No, actually he does not say that. What I read there is that he doesn't necessarily agree with Apple's "new direction", and has decided that the difference between PC and Mac interfaces is now negligible. Obviously, a lot of people disagree.

      Cocoa could not, no-way-no-how, have been ported to OS 9. While I miss my old spacial Finder too, I realize that it does not scale at all for the large numbers of files UNIX - and indeed, things like digital photography/music collections - requires.

      By switching to OS X, Apple threw out 15 years of hard work, just to release an OS with an inferior UI on an inferior kernel. And their interface in many ways no longer follows the principles that Apple themselves set out so brilliantly back in 1984, and others tried to emulate with varying degrees of success (don't even get me started on the Dock).

      Inferior kernal? Smoke another one, buddy.

      I've heard these arguments over and over about the Dock. No one has a problem with the dock unless they are already thoroughly entrenched in some other mechanism. I'm convinced that it is the pain of un-learning something else that makes people hate the Dock. Try this - put some newbies in front of Mac OS 9 and tell them to launch the browser. They won't be able to do it. Where is the browser? 4 levels down, inside the Apps folder, with no visible way to get there. OS X solves this. The dock may have some significant limitations, but it's hardly the disaster some make it out to be.

      As for throwing out 15 years of work, if you'll check the aforementioned Aqua UI guidelines, you'll see that it's not true. They have built upon that foundation. It's practically identical. I still have the original 10-book set of UI guidelines, and it really hasn't budged. If anything they've added to it - such as the new mode for dialogs (status, reason, action). Things like 'verb' button-labels remain.

      But there's absolutely no point in buying a closed platform when the software, specially designed for that platform, sucks. At least with PCs, I can run BeOS on a laptop; with Macs, such is no longer an option.

      You know, that is an opinion.

      .r

      --
      If Jesus wants me it knows where to find me.
    3. Re:Nothing new by psicE · · Score: 2

      Oh, come on. Even people who think POSIX is the best thing since sliced bread agree that Mach sucks. The least Apple could have done would be to use a better microkernel, or to design a POSIX-compatible kernel from the ground up that was legacy-free and more similar to how Macs have always worked, no?

    4. Re:Nothing new by dhovis · · Score: 3, Interesting
      I've been reading a lot lately about how MacOS X doesn't really use a Mach microkernel. The kernel that Darwin uses is actually called xnu, and is more of a hybred micro/macrokernel, as appropriate.

      Apple's Developer site has more info. In fact, they say that xnu is not strictly a microkernel.

      --

      --
      The internet is the greatest source of biased information in the history of mankind.

    5. Re:Nothing new by mrjohnson · · Score: 1

      "OS 9, despite having less eye candy than OS X, was architecturally better for the home user in just about every way than OS X"

      Heh. Granted we're talking about home users here, who don't require five nines availability, but one of the major barriers to the Mac's acceptance has always been its crashiness.

      Cooperative multitasking was a mistake when they built the first Mac, and it's was a mistake all the way up to OS 9.

    6. Re:Nothing new by kubrick · · Score: 1

      Try this - put some newbies in front of Mac OS 9 and tell them to launch the browser. They won't be able to do it. Where is the browser? 4 levels down, inside the Apps folder, with no visible way to get there.

      Last I knew, the default install put aliases for browser, mail and the "Connect to the Internet" setup script on the Desktop. (This may have been in the 8.6 days, but I can't see why they would have changed that up to 9.2...)

      --
      deus does not exist but if he does
    7. Re:Nothing new by Etcetera · · Score: 2


      Heh. Granted we're talking about home users here, who don't require five nines availability, but one of the major barriers to the Mac's acceptance has always been its crashiness.

      I would rather have a machine that crashes occasionally rather than one that I don't understand how to use. The classic Mac OS had an easy, gradual curve from new user to power user. This means that with a *little bit* of effort, a user was eventually empowered to administer and customize their own system.

      Windows by compariason has a hard curve for learning how to administer a system. Indeed, it seems to be designed to prevent newer or regular users from being about to effectively diagnose or administer a system without having to hit the books.

      That's the difference. And that's why Mac OS 9 was great.

      Cooperative multitasking was a mistake when they built the first Mac, and it's was a mistake all the way up to OS 9.

      How many home users truly need pre-emptive multitasking? Home users (until broadband internet came about) are not running servers and don't have to deal with massively parallel processes cause by hundreds of users. As a home user, I want my computer to figure out that the video app I'm messing with in front should take priority over other apps, without having to mess with "nice" values manually.

      "Multitasking" in the MultiFinder sense is important, sometimes the apps know what a better division of resources is than the OS does.

    8. Re:Nothing new by Cadre · · Score: 3, Funny
      By switching to OS X, Apple threw out 15 years of hard work, just to release an OS with an inferior UI on an inferior kernel.

      Ah yes! Damn thee the to hell, Xnu[0]! I can no longer press the mouse button to pause the operating system...

      [0]- Xnu is the name of the new kernel.

      --
      All editorial writers ever do is come down from the hill after the battle is over and shoot the wounded.
    9. Re:Nothing new by Anonymous Coward · · Score: 0
      How many home users truly need pre-emptive multitasking? Home users (until broadband internet came about) are not running servers and don't have to deal with massively parallel processes cause by hundreds of users.

      this home user truly needs preemptive multitasking. but that may be because i'm running X Windows, which lets me use virtual desktops (does MacOS have those yet? no? then i'm not switching), which is the one feature that lets me run several applications simultaneously.

      and i will often kick off one application doing something i know will take time, only to flip over to another desktop and do something else with another app while i wait. sometimes i have three ongoing slow processes bogging down my poor little processor while i read a web page in a fourth desktop. without good multitasking, i could not possibly be productive. unless MacOS will let me be productive, my way, what's my incentive to switch?

      home users usually don't get massively parallel, because their home PCs don't have the processing power to handle that anyway. but it's trivial for a home user to get surprisingly parallel and not even know it, just because modern applications are all written to this weird and crazy "threading" model. that, and older apps (ones designed for OSes with good multitasking, anyway) often make use of background "helper" processes. even if three-fourths of the processes running on my home unix desktop aren't needed, i'm still running over a dozen parallel processes, no sweat.

      As a home user, I want my computer to figure out that the video app I'm messing with in front should take priority over other apps, without having to mess with "nice" values manually.

      as a home user who hasn't messed with "nice" values, how do you know that that video app isn't already taking priority? it, or its background number-cruncher processes that are actually doing the work you asked it to do. looked at how many other, unrelated processes are already swapped out? that would be but one indicator.

    10. Re:Nothing new by Cid+Highwind · · Score: 0, Flamebait

      How many home users truly need pre-emptive multitasking?

      Anyone who wants their MP3s to play without skipping whenever they scroll down a page in netscape, anyone who wants to do something other than watch progress bars crawl while copying files, anyone who wants to use the computer for other things while 3d studio renders in the background.

      "Multitasking" in the MultiFinder sense is important, sometimes the apps know what a better division of resources is than the OS does.

      That's nice, assuming your apps are all perfectly written. The problem is when an app crashes in an infinite loop, the OS never gets a chance to recover.

      I would rather have a machine that crashes occasionally rather than one that I don't understand how to use.

      That's your opinion. Good thing Apple was smart enough not to bet the corporate farm on a few stick-in-the-mud users who would be just as happy if Apple kept shipping System 7.x on Mac LCs for the forseeable future.

      --
      0 1 - just my two bits
    11. Re:Nothing new by JordanH · · Score: 1
      • The least Apple could have done would be to use a better microkernel...

      You are all over the place here. First, the problem was that they were focussing too much on developing the kernel and ignoring GUI standards and development, but now you want them to spend more on developing a "better" microkernel.

      I think you just want to complain.

    12. Re:Nothing new by Elwood+P+Dowd · · Score: 2

      +1, Funny

      --

      There are no trails. There are no trees out here.
    13. Re:Nothing new by Etcetera · · Score: 2


      Anyone who wants their MP3s to play without skipping whenever they scroll down a page in netscape, anyone who wants to do something other than watch progress bars crawl while copying files, anyone who wants to use the computer for other things while 3d studio renders in the background.

      I've *never* had a problem with skipping MP3's in the background on any halfway decent hardware. My beige G3 puts along just fine playing in the background while I do other stuff. Likewise, since OS 8 (and especially OS 8.5) I routinely copy files in the background while doing other stuff in the foreground.

      How many home users are rendering 3-D Studio scenes? If you're doing that, you're probably using a render farm of some type, in which case you'll want it to be done ASAP, in which case you're not going to be doing other stuff on the machine and you actually *want* the app to hog the entire CPU.

      That's nice, assuming your apps are all perfectly written. The problem is when an app crashes in an infinite loop, the OS never gets a chance to recover.

      While I agree there were stability problems, that particular one could usually be solved by a Force Quit (Cmd-Opt-Esc IIRC). In any event, that was no worse than Win9x.

      >> I would rather have a machine that crashes occasionally rather than one that I don't understand how to use.

      That's your opinion.

      Actually, judging by the upgrade rate, that's the opinion of a lot of other Mac users too :/ Moving to OS X for daily use means "re-learning" a lot of that power user ability they'd built up.

    14. Re:Nothing new by psicE · · Score: 2

      My problems are twofold.

      First, that Apple took 15 years of hard work on their interface and threw it out the window. Why couldn't Apple have ported the OS 9 interface to the X API, instead of completely rewriting it and making it worse?

      Second, that Apple spent a huge amount of time improving the Mach kernel. As long as Apple was going to spend so much time improving a kernel, why couldn't they have done work on L4, or another nanokernel? It wouldn't have been any harder, it wouldn't have delayed the production of OS X at all; yet Apple had its programmers work on Mach instead, in my opinion a colossal waste.

      Everything else about OS X is great. Quartz, Cocoa, etc. are all the best implementations of their kind that I've seen anywhere. But I still don't see why Apple had to start almost from scratch with Aqua.

    15. Re:Nothing new by Elwood+P+Dowd · · Score: 2

      I would rather have a machine that crashes occasionally rather than one that I don't understand how to use. The classic Mac OS had an easy, gradual curve from new user to power user. This means that with a *little bit* of effort, a user was eventually empowered to administer and customize their own system.

      I couldn't disagree more.

      When I was four years old, my dad bought a Mac 128K. I've been using Macs since then. Do you remember how hard it was for them to shoehorn a tcp/ip stack into that kernel? It took them a _long_ _time_ to get it right. We were in the cold even longer for an MP3 player that didn't crash the computer. If the user started doing complicated stuff with the machine, it started crashing more. It was just that simple. And when a user is starting to do more complicated things, they probably care about the crashing even more.

      --

      There are no trails. There are no trees out here.
    16. Re:Nothing new by re-Verse · · Score: 1

      By inferior do you mean "won't freeze all activity while a mouse button is held down" or "has its own protected memory" or some other strange parralel universe definition of the word?

      I don't agree with the site at all - it complains that people can set their own icon sizes, and that people may, god forbid, set their icons too large and waste space. Thats fine with me. When i set up my parent with OS X and gave her larger icons, she was very happy, since it was difficult for her to see and understand small icons.

      It seems a lot of people don't like OS X because its not )S 9.10... I for one am glad apple broke with some of their old methods and adopted a better way. Its the first Mac OS I have found useable at all, and I can now use a mac as happily as i use my BSD and windows boxen.

    17. Re:Nothing new by Elwood+P+Dowd · · Score: 2

      Right. That's what happens when it's their own new computer.

      However, when they sit down at *my* mac, they'd have been lost. If they sit down at my mac now, all I have to say is "The compass rose thing is the browser." They can figure out where the address book is, where the mp3 player is, where my mail program is, etc. If I had internet explorer on my computer, I wouldn't have to tell them anything.

      --

      There are no trails. There are no trees out here.
    18. Re:Nothing new by DavidRavenMoon · · Score: 2
      First, that Apple took 15 years of hard work on their interface and threw it out the window. Why couldn't Apple have ported the OS 9 interface to the X API, instead of completely rewriting it and making it worse?

      I have to disagree with you here. I have been using Macs since System 7.0, and I think Aqua is much nicer than OS 8/9 ever was. The 15 years of hard work turned out after a while to be how to try and make Mac OS do things it wasn't designed for. When they tried to upgrade it the way you want them to, they ended up with Copland, which turned out to be a big mess. The classic Mac OS didn't have all the features people are complaining are missing in OS X from the beginning. And many, like the menu bar clock, were shareware that Apple bought (SuperClock). OS X will continue to evolve the same way OS 7/8/9 did. I've been using OS X every day as my main OS since March 2001. I find I can do a lot more in X than in 9, and in that time I've crashed about 6 times. You are going to tell me OS 9 is better, or has a better kernel?

      Second, that Apple spent a huge amount of time improving the Mach kernel. As long as Apple was going to spend so much time improving a kernel, why couldn't they have done work on L4, or another nanokernel? It wouldn't have been any harder, it wouldn't have delayed the production of OS X at all; yet Apple had its programmers work on Mach instead, in my opinion a colossal waste.

      Apple bought NeXT. NeXT runs on Mach. Avie Travarian, the VP of Apple wrote Mach. You really think they are going to switch kernels?

      You need to think of OS X as the next version of NeXT/OPEN Step, because that's what it is.

      I suppose you would have liked they bought Be OS instead (and I was a former Be user as well, and really liked it). But we would have ended up with something even LESS like the classic Mac OS!

      Since you like all these other parts of OS X what don't you like about Mach? Apple programmers (or NeXT programmers actually) worked on Mach because it was already part of NeXT Step.

      --
      -- if it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic - Lewis Carrol
    19. Re:Nothing new by DavidRavenMoon · · Score: 2
      OS 9, despite having less eye candy than OS X, was architecturally better for the home user in just about every way than OS X

      Some examples please. My 10 year old son likes using OS X better than 9, even though his Mac runs 9 and so do all the Macs at school.

      At least with PCs, I can run BeOS on a laptop; with Macs, such is no longer an option.

      Ummm you can run OS X on laptops. I love BeOS, but let's be honest here. What are you going to run on it? There wasn't much software back when Be was still in business!

      And what are you going to do after it wont run on any new hardware you buy? So in five years I can still run OS X on a laptop, but Be?

      I make a living using Macs, and I sure dont see where any of the software sucks. BeOS was nice and fast, but the GUI was fairly hideous, and a lot of the apps were a joke. OS 9's GUI is dated and not all that exciting. You fear change, don't you? You are one of these people who think the awful OS 9 application menu is better than the Dock right?

      Talk about legacy... Mac OS 9 is dead, and so is BeOS.

      --
      -- if it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic - Lewis Carrol
    20. Re:Nothing new by DavidRavenMoon · · Score: 2
      I would rather have a machine that crashes occasionally rather than one that I don't understand how to use.

      How can you not understand how to use it? You turn it on, launch your application and work just as in OS 9. OS X is as easy to use as OS 9, easier I think. You just don't want to learn something new. Take the time, you figured out how to use BeOS, right? You need to stop thinking OS 9, and think OS X... it's a matter of adapting to new habits.

      How many home users truly need pre-emptive multitasking?

      Any one who is doing more than one thing at a time. It's nice being able to launch three apps at the same time. It's nice launching a big app like Photoshop and not having to sit and wait for it. It's nice being able to do something that takes a while and not being stuck behind a modal dialog. It makes the Mac far more usable to anyone, newbie or power user.

      I see people use Macs all wrong... They do things in these stupid convoluted ways. These are the people that can't get used to OS X. They complain that when they click on a window, only that window comes forward and they wanted to switch applications. Well, they did it the wrong way, and that wasn't even the way to do it in OS 9, so of course they are having problems. Just click on the damn Dock icon! Boy that was hard! :)

      --
      -- if it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic - Lewis Carrol
    21. Re:Nothing new by andrewski · · Score: 1

      Maybe it's time to learn a new UI. Quit sucking your thumb, get over the fact that the Apple menu is different, or shut up and remain an OS 9 user forever.

      It was high time that Apple evolved. It was either that or die.

    22. Re:Nothing new by vincent99 · · Score: 1

      I've *never* had a problem with skipping MP3's in the background on any halfway decent hardware.

      And the reason is because iTunes or SoundJam or whatever have each hacked in their decoder to work using system interrupts to guarantee themselves processor time.. try playing a MP3 in QuickTime (which doesn't) and you can easily make it skip.

      The point is that OS X does that for you, for every app, so that developers don't have to go hacking their own solutions.

      --
      -- V
    23. Re:Nothing new by MoneyT · · Score: 2

      MP3's played quite nicely in QT, what are you talking about?

      --
      T Money
      World Domination with a plastic spoon since 1984
    24. Re:Nothing new by MoneyT · · Score: 2

      Actualy, speaking as a mac user, I like being able to click one applications window and bring the entire app to the forefront. If I'm working with 3 or 4 windows in an app, it makes my job that much faster

      --
      T Money
      World Domination with a plastic spoon since 1984
    25. Re:Nothing new by DavidRavenMoon · · Score: 2
      Actualy, speaking as a mac user, I like being able to click one applications window and bring the entire app to the forefront. If I'm working with 3 or 4 windows in an app, it makes my job that much faster

      You can accomplish the same thing by clicking on the Dock.

      Same action, just a different target.

      --
      -- if it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic - Lewis Carrol
    26. Re:Nothing new by Macka · · Score: 2


      Make up your mind.

      First you complain that they toss out the aging OS9 kernel and replace it with one that is multithreaded, has preemptive multitasking, and a modern VM subsystem with protected address space .. .. then you about face by saying that they should have done that .. but you just don't agree with the Microkernel technology they chose to base the Darwin kernel on.

      You say that the Mach microkernel sucks, but don't back up your claim with an explanation as to why.

      Further more, you don't seem to know that Darwin isn't pure Mach. Like other successful Mach based Unix kernels (e.g. Tru64 Unix) it's neither a microkernel, nor a monolithic kernel, it's a hybrid. In Darwin's case, it's a blend of Mach and BSD technologies .. drawing from the strengths of both.

      Go have a read at some of the online docs.

      http://developer.apple.com/techpubs/macosx/Darwi n/ index.html

    27. Re:Nothing new by SoupIsGoodFood_42 · · Score: 1
      I've heard these arguments over and over about the Dock. No one has a problem with the dock unless they are already thoroughly entrenched in some other mechanism. I'm convinced that it is the pain of un-learning something else that makes people hate the Dock. Try this - put some newbies in front of Mac OS 9 and tell them to launch the browser. They won't be able to do it. Where is the browser? 4 levels down, inside the Apps folder, with no visible way to get there. OS X solves this. The dock may have some significant limitations, but it's hardly the disaster some make it out to be.

      The dock is a problem.

      1). The text only comes up when you hover over it. This isn't so bad for applications, but is silly for folders sitting in the dock, 5 folders sitting in a row with no idea what is what.

      2). Space waster. It takes up alot of space. Reducing the size of the icons makes it difficult to tell what is what since there is no text. You could hide it, but that has obvious problems. You could also turn on the magnify feature I spose, but that means you still have to hover over the icons anyway, not to mention that the animation may be off-putting.

      3). Lack of functionality. In OS 9, you have pop-up folders. This meant you could drag files onto shortcuts, or into the folder it's self. You could also drag stuff out of the folder. The view was also highly customisable, just like a normal folder.
      The dock has none of this, You can only drag things onto the icon, and that's it. If it did act like the pop-up folders in OS 9, you would have workaround for lack of sub-menuing on the dock.

      4). Memory muscle it useless. Since the whole thing is centered, and shortcuts are in the same section as permanent shortcuts, the shortcuts will quite oftern be in a differnt place.

      5). Lack of clarity between shortcut icons and apps that are open canbe confusing, not to mention it can be easy to overlook the status of an app/shortcut/icon.

      6). No sub menu for apps, this is a problem since the idea is not to use the Apple menu for custom apps anymore. You can create a folder with shortcuts, but read part on lack of functionality above.

      The windows taskbar has some major problems, but it got's alot of these right. Test labels, shortcuts stay in the same place, running apps are seperate, and are arragned by the order they are opened in. It's also left aligned, so apps already opened aren't affect by new apps opening.

    28. Re:Nothing new by kubrick · · Score: 2

      Is that Apple's fault or yours? You're the one who changed the provided default interface in this case.

      (Even if it wasn't a very good default interface in this case, I would argue that having 'training wheels that you can't take off' -- i.e. a browser icon that won't go away -- is an even worse idea. If I want new users to sit down at my computer and not be able to use a damn thing, that should be my choice -- after all, it's my computer. :)

      --
      deus does not exist but if he does
    29. Re:Nothing new by Maniakes · · Score: 1

      But there's absolutely no point in buying a closed platform when the software, specially designed for that platform, sucks. At least with PCs, I can run BeOS on a laptop; with Macs, such is no longer an option.

      You know, that is an opinion.


      Actually, it isn't. The last Mac system BeOS ran on was the PPC 604. The specs for the G3s and G4s were only made available to Apple, and Be didn't have the resources to reverse-engineer.

      Also, if you want to dual boot, you're out of luck if you want to use MacOS 9.0 or better. Since 9.0, MacOS hasn't played well with the Be bootloader.

      --
      A legparnasom tele van angolnaval.
    30. Re:Nothing new by Anonymous Coward · · Score: 0

      By switching to OS X, Apple threw out 15 years of hard work, just to release an OS with an inferior UI on an inferior kernel

      Yeah, just one thing about that 'inferior kernel' at least it multitasks

    31. Re:Nothing new by Elwood+P+Dowd · · Score: 2

      I still *can* change the default interface, but now I don't want to change it like that. Since Apple has made changes to their UI that make it more usable for me, a regular user, and also make it so a newbie would work better at my computer...

      Well then Apple had some room to improve. This follows because they improved.

      --

      There are no trails. There are no trees out here.
    32. Re:Nothing new by am+2k · · Score: 2
      Cocoa could not, no-way-no-how, have been ported to OS 9.
      Funny you mention this, since Apple ported YellowBox (which later became Cocoa) to Mac OS 8 in addition to the already existing Windows-port, which is still used for the WebObjects development tools.
      Afterwards they invented Carbon and scrapped the whole idea.
    33. Re:Nothing new by Anonymous Coward · · Score: 0

      "By switching to OS X, Apple threw out 15 years of hard work, just to release an OS with an inferior UI on an inferior kernel."

      They are DEAD!
      9.0 is DEAD!
      BeOS is DEAD!

      "OS 9, despite having less eye candy than OS X, was architecturally better for the home user in just about every way than OS X"

      As a home user I like the fact that I can install free industrial strength software that is just a curl away.

      If you really think that OS 9 was architecturally better, perhaps you should take up tree pruning.

    34. Re:Nothing new by Anonymous Coward · · Score: 0

      You don't even know what POSIX stands for.
      Get the fuck out of here.

    35. Re:Nothing new by Anonymous Coward · · Score: 0

      There's a more recent in-depth article from a web developer's perspective about the UI differences between OS X (version 10.2, aka Jaguar) and Windows XP. Highly recommended for anyone curious about why Mac users are such zealots.

      (Hint: some of us think computers should be usable tools to get things done and not merely overblown game consoles or platforms to show off your superior configuration skills.)

    36. Re:Nothing new by rjung2k · · Score: 1

      1). The text only comes up when you hover over it. This isn't so bad for applications, but is silly for folders sitting in the dock, 5 folders sitting in a row with no idea what is what.

      You can use customized icons for the folders, y'know. It's a bit annoying for windows, but at least 10.2 gives you little badges of their parent app to help.

      2). Space waster. It takes up alot of space. Reducing the size of the icons makes it difficult to tell what is what since there is no text.

      Really? I've got my Dock icons at 32 x 32, and I have no problem telling everything apart. That Quartz graphics engine is more than just PR hype.

      4). Memory muscle it useless. Since the whole thing is centered, and shortcuts are in the same section as permanent shortcuts, the shortcuts will quite oftern be in a differnt place.

      In my experience, this is false. Granted, I'm not minizing windows every five seconds, but in everyday use I find that Dock icons are where I've left them. I even have magnification turned on, and I find that dragging stuff to the Dock isn't as big of an issue as I thought it'd be, because the Dock keeps the current icon immobile -- the magnification effect cheats by moving the other icons around, while my target stays where it was.

      6). No sub menu for apps, this is a problem since the idea is not to use the Apple menu for custom apps anymore. You can create a folder with shortcuts, but read part on lack of functionality above.

      Just put your main Application folder in the Dock, and you'll have one-click access to all your apps, like the Apple menu of old.

      Have you actually used MacOS X?

    37. Re:Nothing new by rjung2k · · Score: 1

      How many home users truly need pre-emptive multitasking?

      This is a joke, right? I'm listening to streaming music over the internet and surfing sites with my browser, while iMovie is exporting my latest home video to a file, PhotoShop is running a series of filters on this kewl new picture I've drawn, and I'm printing out a news article I want to read later. No servers here, but damn straight I better have pre-emptive multitasking for all that.

    38. Re:Nothing new by Anonymous Coward · · Score: 0

      Admittedly, it is sometimes more difficult to do things in Mac OS X than in OS X. For example, OS X's new multi-user system only allows administrators to install software. However, from a technical standpoint, it is not fair to say that the kernel is inferior. Mac OS X's has a protected memory system, something that was never in any version of Mac OS, even 9.2. As for the UI, this is almost entirely subjective, and so I don't see any reason in arguing with you. Keep in mind that there are alternative "skins" for OS X (see http://www.resexcellence.com/).

      You are welcome to run Mac OS 9, Linux, or whatever other OS you want, and nobody will come to your house and arrest you for patent infringement. Apple stops OS 9 bootup in its newest macs? No problem. Just buy an old computer off of ebay.

      Have fun with your PPC computer.
      -- The Friendly Flamer

    39. Re:Nothing new by SoupIsGoodFood_42 · · Score: 1
      You can use customized icons for the folders, y'know. It's a bit annoying for windows, but at least 10.2 gives you little badges of their parent app to help.

      I still prefer text labels, they much more descriptive. Plus I (and others) Don't have time to customise folders all our folders.

      In my experience, this is false. Granted, I'm not minizing windows every five seconds, but in everyday use I find that Dock icons are where I've left them. I even have magnification turned on, and I find that dragging stuff to the Dock isn't as big of an issue as I thought it'd be, because the Dock keeps the current icon immobile -- the magnification effect cheats by moving the other icons around, while my target stays where it was.

      Unless you never open up apps that aren't on the dock as shortcuts, all the icons move since the dock is centered.

      Just put your main Application folder in the Dock, and you'll have one-click access to all your apps, like the Apple menu of old.

      But then you can't drag files onto them. Most of the time, this is how I open a file. I find it easier than navigating from the HD to the file again using the open file box.

    40. Re:Nothing new by Anonymous Coward · · Score: 0

      While I agree there were stability problems, that particular one could usually be solved by a Force Quit (Cmd-Opt-Esc IIRC). In any event, that was no worse than Win9x

      It's been my experience that all an attempted force quit does is pop up the force quit dialog. The force-quit success rate (defining success as killing the offending app, thus losing work in only one app rather than everything that was open) is somewhere on the wrong side of 25%. Nobody here was advocating win9x, BTW.

  19. Best suggestion by Jeremy+Erwin · · Score: 5, Informative

    was to kill off the windows MDI-- with it's horrendous, ugly grey root window. My ability to use a third party editor with a third party hex editor with my compiler shouldn't be hampered by one designers misguided attempt to use MDI.

    1. Re:Best suggestion by AnyoneEB · · Score: 1

      Isn't it already dead? Microsoft Office XP uses separate windows, which can get rather annoying on the amount of start bar space used.

      --
      Centralization breaks the internet.
    2. Re:Best suggestion by Sax+Maniac · · Score: 5, Insightful

      It's ironic how MDI gets trashed and praised, often by the same people.

      Tabbed browsing in Mozilla? Quicken's tabbed windows? That's MDI, too. And lots of people like it. It's MDI done right.

      The problem with old-style MDI apps (e.g., icons in a big empty window) that it was a one-size-fits-none policy that all apps could use. The in-app window management was usually horrible: icons that could be overlapped.

      The only different is that apps are using MDI nowadays and are customizing the in-app window management to the application. Most people love it; other control freaks don't (e.g., if you have a custom 9000-line .fvwmrc file).

      --
      I can explanate how to administrate your network. You must configurate and segmentate it, so it can computate.
    3. Re:Best suggestion by Anonymous Coward · · Score: 0

      9000-line .fvwmrc file? You sound like you've been there before... :-)

    4. Re:Best suggestion by Kashif+Shaikh · · Score: 1

      It's ironic how MDI gets trashed and praised, often by the same people.

      Tabbed browsing in Mozilla? Quicken's tabbed windows? That's MDI, too. And lots of people like it. It's MDI done right.


      And I agree. When I used to browse with IE, I simply hated the fact that all IE windows would appear on the taskbar. I mean, it cluttered everything! When you have one instance of Word opened with 10 instances of IE, window management becomes a chore. Even more worse is when XP introduced the option of grouping; now you have to scan through X amount of windows using two-clicks(one to open the group, the other to select) which equates to longer 'latency' trying to grab the window I want.

      This is why tabbed browing is a Good Thing or as you said "MDI done right". Applications know how to display multiple instances of themselves properly and nicely. A GUI's window manager on the other hand can't, as it's generic like process scheduling(if you get my drift).

    5. Re:Best suggestion by cscx · · Score: 2

      Office let's you choose whether you want MDI or not; it's in the options, I forget where, look for it.

    6. Re:Best suggestion by DavidRavenMoon · · Score: 2
      And I agree. When I used to browse with IE, I simply hated the fact that all IE windows would appear on the taskbar. I mean, it cluttered everything!

      This is where Apple's implementation of the Dock is a bit better. The Taskbar shouldn't be showing open windows unless they are minimized. This is the way the Dock works, and even the Dock can get cluttered if you minimized a bunch of windows.

      I just leave them open behind each other and use the Window menu, right-click on the Dock icon, or Command-~ to switch.

      I love Mozilla's tabs!

      --
      -- if it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic - Lewis Carrol
    7. Re:Best suggestion by Kashif+Shaikh · · Score: 1

      This is where Apple's implementation of the Dock is a bit better. The Taskbar shouldn't be showing open windows unless they are minimized. This is the way the Dock works, and even the Dock can get cluttered if you minimized a bunch of windows.

      This is how Window Maker dock tab works too. But the real question is, who's implementation of dock bar is better: Window Maker or Mac OSX? I know they both share the same heritage(NeXT), but there must be differences that makes one better than the other, no?

    8. Re:Best suggestion by spectecjr · · Score: 2

      This is where Apple's implementation of the Dock is a bit better. The Taskbar shouldn't be showing open windows unless they are minimized. This is the way the Dock works, and even the Dock can get cluttered if you minimized a bunch of windows.

      Sorry, but that just doesn't work. The moment you have more than about 6 open windows at once (say you're doing some work and researching multiple places), you NEED to be able to switch between them. And you don't want to have to minimize them to get that shortcut access.

      Simon

      --
      Coming soon - pyrogyra
    9. Re:Best suggestion by DavidRavenMoon · · Score: 2
      Sorry, but that just doesn't work. The moment you have more than about 6 open windows at once (say you're doing some work and researching multiple places), you NEED to be able to switch between them. And you don't want to have to minimize them to get that shortcut access.

      Yes, it does work, but maybe not in Windows. You can easily switch between open windows. If you right-click on the App's icon in the Dock you are presented with a list of that app's open windows. Plus every application has a window menu as an additional way to choose open windows without them cluttering up the Dock with icons.

      Plus in Jaguar if you hide the application the minimized icons are also hidden, but still show up in the window list.

      You have never used OS X, have you?

      --
      -- if it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic - Lewis Carrol
    10. Re:Best suggestion by DavidRavenMoon · · Score: 2
      This is how Window Maker dock tab works too. But the real question is, who's implementation of dock bar is better: Window Maker or Mac OSX? I know they both share the same heritage(NeXT), but there must be differences that makes one better than the other, no?

      You know, I used to use Window Maker, and AfterStep in LinuxPPC, but I dont remember... I haven't used Linux in over a year.

      --
      -- if it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic - Lewis Carrol
    11. Re:Best suggestion by tupps · · Score: 2

      That is what the window menu is good for. When you have 6 websites open all that start with the same name (eg surfing a portal site) you still have to click through the whole list. Have to admit Mozillas tab browsing rocks. UI done right for sure.

      --
      Go out and get sailing!
    12. Re:Best suggestion by angelo · · Score: 1

      Tabbed browsing is not an MDI. An MDI is a window space specifically designed for sub-windows of possibly differing sizes. Tabbed browsing is just layering the same information over the same space to save on interface elements.

      You can't view two Mozilla pages side-by-side unless they are in different windows, which is possible with MDI within the same window.

    13. Re:Best suggestion by Eil · · Score: 2


      I think the main problem is that MDI is useful for some things and horrible for others, and people on both sides of the argument seem to forget that. (As is common in most slashdot debates.)

      In instances where a single computer system is planned to be running only one application most of the time (such as a point-of-sale or other single-use system) MDI is good because it hides all of the stuff that's not applicable to the task at hand. (Such as the operating system's visual elements.) I won't elaborate much on the advantages of this, but it's clear to see

      But in a setting where the user is going to be using multiple third-party applications as well as parts of the operating system itself, MDI extremely hampers usability. Constrast a web developer trying to use Photoshop and the various MDI-laden Microsoft web development tools with a web developer on unix, who can have GIMP images, web browser windows, and xterms all separately accessable on the screen at the same time.

      Tabbed browsing in Mozilla?

      Yes, that's MDI but tabbed browser windows are not mandatory the way MDI is in most MDI-styled applications is. If I'm developing a web page and want to have multiple Mozilla windows open, I can. I can even have multiple Mozilla windows each with an arbitrary number of tabs. Also of note is that browser tabs don't have most of the annoyances commonly associated with MDI-style document management: The tabs are completely optional, and Mozilla never opens a window with no tabs and no document to display. (A blank page is still considered a document.)

    14. Re:Best suggestion by CaptnMArk · · Score: 1

      Tabbed Browsing is MDI (multiple document interface) in a loose sense.

      It is just slightly less annoying than window-in-window MDI.

    15. Re:Best suggestion by yason · · Score: 1

      The reason Windows embraces its horrible MDI is that it has lacked virtual desktops since the year 0. MDI is mostly about grouping related windows. As someone already pointed out, Mozilla does this with tabs and I think running Gimp on one desktop is comparable to running Photoshop in one MDI window.

      MDI is just the result of philosophy of MS Windows:

      Thou can run one app at a time, fullscreen, since our windowing management is so bad you can't efficiently operate with multiple windows at the same time -- oh yes, we didn't do multitasking either in the beginning so we had to "switch between applications" and reflect this in the UI.
      .
    16. Re:Best suggestion by Ninja+Programmer · · Score: 1

      Tell me, how do you quickly minimize all the documents opened by a single application, but nothing else? With MDI, that's exactly what the minimize button does -- without it, you hit minimize on each open Window one by one.

    17. Re:Best suggestion by RAMMS+EIN · · Score: 2

      IMHO the reason MDI is perceived as great is that
      1. There is one entry per _app_ on the taskbar instead of one per _window_
      2. Raising the main window raises all the child windows, bringing up all windows belonging to the application at once

      These two characteristics could just as well be realized by other means. For example, the window manager I use (WindowMaker), shows only one icon per app, and clicking that icon raises all windows belonging to that app. It's even more flexible than that: if I hide a window (though I hardly ever do), that window will get it's own icon, so that, effectively, WindowMaker provides your choice of MDI or SDI on a per-window basis, without apps having to know about it. Of course, WindowMaker is defated by apps providing their own MDI, as they keep all their child windows hidden from the window manager. With this background information in mind, it seems that Apple is doing the Right Thing by advising against app-level MDI.

      --
      Please correct me if I got my facts wrong.
    18. Re:Best suggestion by rjung2k · · Score: 1

      On the Mac, you hold down Option and click "Minimize" in one of the windows.

      In fact, on the Mac, you can hold down Option and use the window widgets to close and maximize all of the application's windows, as well. Rather convenient when you have 20 Photoshop files open that you want to close without quitting Photoshop...

  20. You guys really eat Apples PR up. Mindless sheep. by iPaqMan · · Score: 0, Flamebait

    As with any company sponsored propagada. They show you the gems of there interface compared to the most lackluster parts of thier competitors. I like how they toute there pleasing interface then compare it to a non-WinXP GUI. I admit the XP interface is nothing great but come on. I don't know how many Mac users I hear saying that the Mac "Launch bar" (name?) sucks.

    As John Stossel would say "Gimmie a break!"

    All I can say to all you zealots is Ba.....

  21. It's crap... by Kindaian · · Score: 0, Flamebait

    Why should i be interested in reading a interface manual for a system that doesn't run in my computer?

    Unless in doing a UI investigation, the doc is pure crap for the millions that have a x86/PC box...

    Cheers...

    1. Re:It's crap... by mccalli · · Score: 3, Informative
      Why should i be interested in reading a interface manual for a system that doesn't run in my computer?

      Because Apple's HCI guides work very well, no matter which OS you apply them to. Yes, some things will be specific to the Mac. On the other hand, I still stick by many of the principles outlined in the "Apple Human Interface Guidelines" book published circa System 6.

      Oh, and that's for Java, C/C++ apps and even web pages to a small extent. Haven't had a Mac since the original LC.

      Cheers,
      Ian

    2. Re:It's crap... by reallocate · · Score: 2

      So, don't read it.

      --
      -- Slashdot: When Public Access TV Says "No"
    3. Re:It's crap... by mad+flyer · · Score: 1

      Well, we don't expect pigs to read it either... Go play doom and think you're superior, at least when they play in the mud they don't think they're smarter than the farmer...

    4. Re:It's crap... by Anonymous Coward · · Score: 0

      And the worst part was the way they made you click on the link and read it, even though it was completely irrelevant for you!

      Oh, wait...

    5. Re:It's crap... by MoneyT · · Score: 2

      Because by learning different ways to approach a problem you are better able to make a better solution. Not to mention that most of the HIG are portable to other platforms and make a hell of a lot of sense. And if you ever want to continue to maintain the hope that someday maybe when hell freezes over that you will be able to run OS X on your computer, you better show Apple you and your fellow developes can conform to certain HIGs or your programs will fail miserably.

      --
      T Money
      World Domination with a plastic spoon since 1984
    6. Re:It's crap... by Anonymous Coward · · Score: 0

      Oh damn, we here at slashdot thought you were running a mac. Kindly update our information, please post and tell us what system you're running, so we can aim all our news toward you. Please include your state, as I'm sure news in other states wont interest you, asshole:P

  22. No MDI ? Say it ain't so ! by Anonymous Coward · · Score: 0

    From the article:

    The MDI tendency directly contradicts Mac OS X, in which windows are document-centric rather than application-centric. No parent application "main window" exists.

    So based on this recommendation, tabbed browsing is verboten... sorry, Apple, but that's holy ground you're treading on.

  23. Re:not...yea RIGHT!! dumb @ss by Anonymous Coward · · Score: 0

    http://themes.kde.org look at how many winblows users love Aqua. Well I guess you have to do something with that pile of cr@p they call

    e-x(P)tinct

  24. riiiiight.... by seriousness · · Score: 0, Flamebait

    i think that the images are /.ing themselves...soooo slow....huzzah! errr...ok. so you *want* dialogue boxes like that? and you *don't* like MDI? ok then.....i personally had nothing against the concept. i kinda like toolbars as well... the following redesign is better? only if that's the only option that you get. which, assuming that they are making it for a mac, it would be. did i read correctly that mac os x supports file name extensions? as in the things that windows/unix/everything else has had for years? is apple going back on part of its perfect operating system? are they stealing an idea from the rest of the world that they thought was good? why haven't i heard of this before? why can't they call their things normal names, that *humans* can understand quickly, not things like cocoa or peanut butter or whatever the fuck they want. java was a cute idea, but this is taking it too far. shut the fuck up, apple. just use a fucking acronym once in a fucking while. i'm sure that it won't hurt, unless you're too busy feeling superior to think about something. cunts. (sorry, i'm just a little angry tonight. ;))

    1. Re:riiiiight.... by Anonymous Coward · · Score: 0

      hahahaha loser.. you don't know anything hahahaha

      Just a loser

    2. Re:riiiiight.... by MoneyT · · Score: 2

      1) File extantions are a resul tof switching to the UNIX underlay.

      2) What does it matter wheather it's called COacoa, Carbon, Darwin, Java, C++ or Pearl. It's just a name. And acronyms are annoying more often than not because they aren't pronounceable so how do you indicate tham verbaly? i.e. GUI (yeah you can say Gooey, or G-U-I, so how is it worse that just saying Aqua?

      --
      T Money
      World Domination with a plastic spoon since 1984
  25. Use verb buttons instead of 'yes/no' by kiltedtaco · · Score: 4, Interesting

    Really nice idea I never thought of. Too bad I won't be writeing any OS X apps anytime soon. Are there more documents like this on UI design that arent' just about OS X, but more general?

    1. Re:Use verb buttons instead of 'yes/no' by upstairs · · Score: 1

      Theres lots of bloody expensive books on it thats for sure. One interesting book: The design of everyday things by Donald A Norman. Originally published in 1988, but speaks across the ages.

    2. Re:Use verb buttons instead of 'yes/no' by Tub-o-Guts · · Score: 2, Informative

      There are many books on UI design that are worth looking into, two of the more useful ones I have used:

      GUI Bloopers
      The Design of Everyday Things

      Also, the Macintosh Human Interface Guidelines (downloadable here: http://developer.apple.com/techpubs/mac/HIGuidelin es/HIGuidelines-2.html) is great for its sections on design principles like modelessness and user control. The Mac-specific stuff like where to put buttons is less relevant and can be skipped.

      I'd recommend focusing on the principles of good design that can be used on Swing, Windows, Mac or KDE and Gnome. Good UI principles will still be valid 10 years from now, when neither XP or Aqua will be around anyway.

      --
      "I don't mind the swelling, it's the itching I could do without."
    3. Re:Use verb buttons instead of 'yes/no' by Anonymous Coward · · Score: 0

      Yes. They are everywhere. Try Google.

    4. Re:Use verb buttons instead of 'yes/no' by Ozan · · Score: 3, Informative

      Really nice idea I never thought of. Too bad I won't be writeing any OS X apps anytime soon. Are there more documents like this on UI design that arent' just about OS X, but more general?

      Try the Interface hall of fame and hall of shame at Isys Information Architects

    5. Re:Use verb buttons instead of 'yes/no' by milovoo · · Score: 1

      there's a decent book

      the Art of Human-Computer Interface Design
      edited by Brenda Laurel

      It's apple-centric and a little dated, but
      the concepts are still well described and
      important to consider. I've gone through a
      couple of copies as I'm always loaning it
      to people who get started reading it and
      can't put it down, not bad for a tech-spec.

      -milo

    6. Re:Use verb buttons instead of 'yes/no' by schvenk · · Score: 1

      As a previous poster said, there are tons of books, but some may be costly. If you're looking for some pointers there are also Web resources. You could start at Jakob Nielsen's Web site (useit.com) and check out the archives for his Alertbox column, as well as the links he has to a bunch of other UI-related sites. For more researchy stuff check out the University of Maryland's Human Computer Interaction Lab at www.cs.umd.edu/hcil. I have a couple other links on my Web site at http://designtheworld.com/phi/links .

  26. Stuff that matters? Please... by Anonymous Coward · · Score: 0

    Nowadays all we see on /. is reposts (sometimes triple reposts within the same week) and completely irrelevant stuff about Macs. Macs are definitely not for nerds; they're for interior decorators and vegans. And this is definitely not 'stuff that matters' (either to the nerds or the interior decorators). What's next? An article about how McDonalds starts with "Mac"?

    I think this is partly why sites like Anandtech, Ace's Hardware, 2CPU, etc. (and even the hideous Tom's Hardware) are getting so many hits and so many posts in their forums, and are moving away from being hardware-centric sites to more generic IT-community sites. They even manage to have some interesting Mac-related news, and that's not an easy thing to achieve.

    Slashdot is braindead, and it's time someone either tried ressuscitation or turned off life support.

    1. Re:Stuff that matters? Please... by MoneyT · · Score: 2

      Define Nerd....

      --
      T Money
      World Domination with a plastic spoon since 1984
  27. Millions of colors? by Virtex · · Score: 1, Troll

    From the article:

    One of the most visible and important parts of the Aqua interface are high-quality icons. Mac OS X icons have rich visual characteristics: They are often displayed at a sizes varying from 128 x 128 pixels to 16 x 16 pixels, can contain millions of colors, have very realistic qualities, and are professionally rendered.

    Someone help me with this. If I have an icon that's 128x128, how can it contain millions of colors when it only has 16384 pixels? Does it have color cycling or something?

    --
    For every post, there is an equal and opposite re-post.
    1. Re:Millions of colors? by avalys · · Score: 1

      They mean the icons are in 24-bit color, so millions of colors are available for designers to use. They can't possibly use all the shades in one icon, but they have a much larger palette of shades to choose from. As a result, the icons look better.

      --
      This space intentionally left blank.
    2. Re:Millions of colors? by Powercntrl · · Score: 1

      Someone help me with this. If I have an icon that's 128x128, how can it contain millions of colors when it only has 16384 pixels? Does it have color cycling or something?

      It's a palette thing. Think about graph paper and a box of crayons. More crayons to choose from means you can make a more colorful picture.

      Want a better example? Run a 3D game that supports both 16 and 32 bit color at 640x480 (307,200 pixels) and compare 16 bit vs 32 bit color. Notice the difference now?

      --

      ---
      DRM is like antifreeze, to the MPAA/RIAA it's sweet, to the consumers it's poison.
    3. Re:Millions of colors? by BusterB · · Score: 2

      Geez, you know what they meant. The icon is rendered from a palette of millions of colors, e.g. each pixel uses at least 24 bits. You're just being pedantic.

    4. Re:Millions of colors? by bpbond · · Score: 1

      Multiple bytes encode the color information for each pixel, allowing it to have one of many (up to "millions") of colors. So what this is saying is that the icons colors can be chosen from this large palette, not that millions are simultaneously present in a given icon.

      --
      "Science is a tribute to what we can know although we are fallible" -Jacob Bronowski
    5. Re:Millions of colors? by Anonymous Coward · · Score: 0

      Yes, just like Palm and HP LYING about their ability to show colours on their handhelds. So instead of 24-bit colour macs are only 14-bit colour. I can't wait for the lawsuit, maybe I can get some of my money back for this lame jaguar upgrade.

    6. Re:Millions of colors? by Jeremy+Erwin · · Score: 2

      Instead of using the terms 24-bit color and 16 bit color, Apple, (and therefor mac users) uses the terms "millions" and "thousands". (For lower bit depths, older macs used "256 colors", "16 colors" "4 colors" and "Black and White")

    7. Re:Millions of colors? by tgibbs · · Score: 2

      This is a common misunderstanding. It wouldn't matter if it was only one pixel. It means millions of color choices, not millions of colors simultaneously. For truly high-quality color, you need more colors available than even the entire screen is able to display simultaneously.

  28. MacKiDo. by Anonymous Coward · · Score: 0

    Having read through some of the documentaion you pointed to, there seems to be a lot of crap in there. e.g. closing a window.

    It goes on about the window manager control box, you can double click it to close a window(not mentioned) the control box is for window control (not mentioned).

    There's too much referance to the evil MDI that no-one uses.

    It says that ctrl and alt keys are too close together, bolx!

    It fails to mention the task manager

    It fails to mention the task bar

    basicly it takes a lot of the UI out of context, and applies the num-brained user approach not the skilled use approach.

    Maximise is close to the close botton, not an issue, double click the top of the window frame to maxamise, normalise the window.

    I'm not saying that windows is well desogned, I'm just pointing out that the 'design' documentation is equally flawed.

    1. Re:MacKiDo. by MoneyT · · Score: 2

      The close button, like the most destructive button of any set of options, should be further away from the other options. I don't care for the new design in OSX nor for the design in window. Even less so in windows becasue the menu is on one side and the controls are on the other

      --
      T Money
      World Domination with a plastic spoon since 1984
    2. Re:MacKiDo. by rjung2k · · Score: 1

      To give credit to Apple, the window-control widgets in MacOS X are spaced apart, so you're not likely to press one by mistake. Compared to Windows' jammedUpNextToEachOther mess, X is better by far.

  29. Usability... by FyRE666 · · Score: 2

    I've never understood Apple's reliance on a single menubar for everything on the screen. Ok, it may make sense if you're only running one app on the screen but I always found it confusing, and other's I've shown it to have had the same problem. For instance, I open app A, and the menu appears - all well and good. Then I open apps B,C,D and E then click on the desktop by mistake - oops, the menu now has nothing to do with any app. This means going back to find it, click to give it focus, then go back up to the floating menu bar at the top of the screen.

    At least with a menu-per-window you know that that's the menu for that app; there's no confusion. The paradigm breaks with OS-X anyway, since they allow toolbars in the windows, which makes matters worse - is an option available here, or up at the top of the screen?

    Giving the OPTION of having the menus for each app in its window would go a long way toward helping people migrate from Windows, in my view.

    This is just my opinion though, I use OS-X,XP and KDE pretty regularly but if I had to order them by ease of use, I'd have to say XP,KDE then OS-X...

    1. Re:Usability... by Merlin42 · · Score: 3, Insightful

      Actually there were two very valid reasons for doing this back when the original Mac UI was being developed.

      The cheesy reason: It saves screen space, on a 3 or 4 inch low res monitor screen space is very valuable.

      The good reason: 'targetability' With the menu always at the top of the screen it has an effectivly infinite height making it easier for the user to get to the menu (ie a quick flick upwards of the wrist always gets the mouse over the menu).

      Clearly the first reason is no longer valid on todays systems, but the second still has some merit. But on the other hand if I wish to 'target' a menu item in a different document window things get much more cumbersome... I guess they just optimized for the common case at the expense of the uncommon one ... not neccisarily bad but still very confusing to those of us (myself inculded) coming from a[n] [X]windows background.

    2. Re:Usability... by singularity · · Score: 2

      You admit that the confusion comes into play if you click on something "by accident." I do not believe I can expect an OS to know what I want if I click places by accident.

      Either way, to get back to the application you want, whether the menu is at the top of the window or at the top of the screen, you have to either click on the window in question, or select the program from the dock.

      I also believe that allowing users to choose between two such radically different interfaces will only lead to confusion. Yes, it might be strange at first for people switching from Windows, but Apple cannot simply design their interface based on making it easy for Windows switchers. To do so would simply mean mimicing XP's interface.

      XP is easier for you just because you are used to it. The OS X environment is easier for me because that is what I am used to.

      --
      - (c) 2018 Hank Zimmerman
    3. Re:Usability... by Anonymous Coward · · Score: 0

      At least with a menu-per-window you know that that's the menu for that app; there's no confusion. Allow me to allay your distress. The top menu bar is a set of menus for the app that you currently have as your active window. It automatically switches to whatever window you are in. That wasn't so hard, was it?

    4. Re:Usability... by 3Ddgg · · Score: 1

      It comes from their useless memory/process management on earlier OSs. They had no multitasking, so they removed things from the window because you couldn't use them anyway. :-)

      --
      No warranty of any kind is offered as to the quality of this post.
    5. Re:Usability... by upstairs · · Score: 1

      I think targetability has a lot of merit. There should be one menu at the attention point (the top of the page) which can be changed by clicking the static icons located on the sidebar of the screen.

      Now if only there werent poor icon designers i wouldnt have to autohide the dock.

    6. Re:Usability... by Lars+T. · · Score: 2
      When you click on the Desktop, the menu now has to do with the app called Finder.

      And with menu-per-window you know that that's the menu for that window, not for the app as you say. Your app may have more than one window. And it wastes space. Especially when you also have toolbars.

      --

      Lars T.

      To the guy who modded me down from perfect to terrible Karma - Apple haters still suck

    7. Re:Usability... by FyRE666 · · Score: 3, Interesting

      XP is easier for you just because you are used to it. The OS X environment is easier for me because that is what I am used to.

      Precisely. I'm not saying that everyone's the same, but since it's in Apples interest to attract Windows users, it makes sense to make the transition as painless as possible.

      Is adding a menubar to a window really that radical a change? It's just an object - I'm betting the alteration to attach it to a movable window rather than fixed to the desktop is not a huge undertaking, and the apps wouldn't behave any differently aside from a thin strip across the top of the windows.

      Again, this could easily be a choice; a simple checkbox ("Dock menu to window"), and not the default, but maybe mentioned in a getting started guide for Windows migrants. People can then choose whatever works best for them. Be interesting to see the percentages in any case...

    8. Re:Usability... by Anonymous Coward · · Score: 0
      I think targetability has a lot of merit. There should be one menu at the attention point (the top of the page) which can be changed by clicking the static icons located on the sidebar of the screen.

      maybe it's just me, but i seldom pay attention to what's at the top of the screen. i pay attention to what's inside my windows, and more occasionally to what's around the edges of my windows. my attention points are all fairly close to what i'm doing, not way off at the top of my screen.

      in fact, my eyes are more likely to droop down towards the bottom of the screen. which may be why that's a good place for my gnome/kde panels, launchers and toolbars, and might have something to do with why i never seem to use that extra top-right corner panel i made in gnome that i thought would be so useful...

    9. Re:Usability... by chippcom · · Score: 1

      I doubt seriously if the Aqua UI guys were concerned about 'saving space.'

      A big criticism of OSX has benn there's never enough screen real estate with their oversize docking bar and larger than average dialogs.

    10. Re:Usability... by Etcetera · · Score: 2


      maybe it's just me, but i seldom pay attention to what's at the top of the screen. i pay attention to what's inside my windows, and more occasionally to what's around the edges of my windows. my attention points are all fairly close to what i'm doing, not way off at the top of my screen.

      in fact, my eyes are more likely to droop down towards the bottom of the screen. which may be why that's a good place for my gnome/kde panels, launchers and toolbars, and might have something to do with why i never seem to use that extra top-right corner panel i made in gnome that i thought would be so useful...


      That's because you're used to the Windows (and Win-clones like KDE, GNOME) way of doing things. Long-term windows users naturally gravitate towards the lower (usually lower-left) portion of the screen as a result of using the Start menu and task bar all the time.

      If you watch or talk to long-term Mac users, you'll find they naturally gravitate towards the upper portion of the screen for "control". (Side note: the Trash Can is purposefully placed far away from here (lower right) to prevent accidents.)

      Mac users will look to the upper-left corner for "control" of the machine (Apple menu, File menu) and the upper-right for disk access, process management, or Help (Default disk location, App Menu under OS 9, Help menu).

      Not necessarily "better" (except for the trash can thingy), just different. It does make a good reason to maintain the top-of-screen menubar though.

    11. Re:Usability... by Anonymous Coward · · Score: 0

      Options in a Mac?? You ask too much...

    12. Re:Usability... by Anonymous Coward · · Score: 0

      I'm sorry that you're used to OS X. :-D

    13. Re:Usability... by PythonOrRuby · · Score: 2

      I use Mac OS X at home, an Win2K at school.

      Have you tried actually using Mac OS X? Just click on the App/Doc separator in the Dock and drag up or down. The Dock resizes itself.

      As for dialogs... almost all of the dialogs I've seen in Windows have taken up more screen real estate than comparable dialogs in OS X. Those that don't are usually overly cramped and unreadable.

    14. Re:Usability... by Anonymous Coward · · Score: 0
      As a former exclusive user of Apple products, things like this annoy me to no end.

      Apple berates M$ for using nonstandard scroll bars. But it's OK for them to do the same.

      What Apple is doing is akin to a man with a 3 inch penis trying to convince women that big fat penises are no good because of the pain that they can cause. Even though 90% of women may prefer big penises, or 90% of the world may prefer something about the Wintel platform Apple is attempting to tell them that they really don't.

      Apple, your future looks dim for a reason. (most) People don't want to buy what you're selling.

      MacOS may have many technical advantages over Windows, just as the devices that run WinCE have advantages over the machines that run Palm OS. But both of the loses trail for other reasons. #1 Price. I can buy a refurbed Visor Deluxe for under $100. I can get a decent PC for less than the cost of an eMac. #2 Availability of software. I can get so much more software for a Palm OS or Windows machine so, in the great platform Jyhad. I choose the side based upon my computing needs. Not on my need to feel or think "different"ly.

    15. Re:Usability... by MoneyT · · Score: 2

      It would be difficult to implemnt. Suddenyl all programs have to behave one of two ways, either a single command reference, and the currently active window is where all commands are referenced. Or Window by window, in which the system has to keep track of multiple menus each with defferent sets of possiblbe instructions, and that's just within one program.

      --
      T Money
      World Domination with a plastic spoon since 1984
    16. Re:Usability... by MoneyT · · Score: 2

      Apple's future looks dim? Since when was time travel invneted, and tell me, is it wierd going back to 1996? YOu must still have time-lag, but let me bring you back up to speed. It's 2002 again, Apple is sucessful, selling many iMacs and G4s (compared to past years) and is one of the few tech companies that manage to turn a decent profit. LIke someone else here said, you can't innovate on a 2% profit margin.

      --
      T Money
      World Domination with a plastic spoon since 1984
    17. Re:Usability... by FyRE666 · · Score: 2

      I don't see why the apps would have to even know which method was in use. I've never written anything for OS-X, so I can't be sure which method is used to wire the menubar object up (callbacks,slots+signals,listeners or whatever), but wouldn't the app just build a menubar, and not care where it ended up as long as it performed the same functions?

      The "window manager" is the only part that would need to know how to display the menu - either changing the top menubar to the menu for the window, or having the menu permanently displayed at the top of all the windows.

      Not that Apple will ever do this of course, but I'd appreciate it if it did.

      Does the menubar also appear in a second monitor by the way, for the windows in that monitor? Please don't say you have to move the mouse back into the first monitor window to access the menu for a window in the second monitor! That would kind of blow the whole "Single menu is best" argument out of the water!

    18. Re:Usability... by carlfish · · Score: 2

      It's a pretty radical change. You're thinking like a programmer, "Oh, it's just an interface element, it can be drawn anywhere", not a UI designer.

      1. When you have a menu-bar at the top of the screen, it's general to the entire application. When you put a menu-bar in a window, it's specific to the contents of that window. Thus, you have to start worrying about what goes where, and in what context, and your application becomes hideously inconsistent.
      2. When the menu-bar is in the application, you still need the top-of-screen menu for things like the Apple Menu, the clock, and the system menu items like the volume/network controls (all of which are system-specific, not application specific). Thus you get a "Which menu?" confusion. For an example of this, run a Java application under OS X. (There's an option in OS X Java apps to move window menu bars up to the top of the screen, but in most Java apps that doesn't work because of problem #1)
      3. Most Mac applications are designed so that they can be accessed from the menu-bar when there are no windows open. Moving the menu into the windows would defeat this (or at least make it inconsistent as the menu pops up magically to the top of the screen when the last window closes)
      4. It's very, very easy to get used to the new menu-bar position. I was a Windows user for ten years before I got my Powerbook, and I got used to the menus in about two days.

      A User Interface is like a language. Every customiseable variant on the UI is a dialect of that language. Imagine you are writing a book, and you have to make it easy to translate into two dialects (English-Menubarian, and English-Windowmenuan). You have to do more work, and you have to avoid using any concept that won't translate cleanly into both dialects. A customiseable UI actually reduces the available expressiveness of applications, because it has to cater to, and be useable in, every dialect.

      --
      The more I learn about the Internet, the more amazed I am that it works at all.
    19. Re:Usability... by Dixie_Flatline · · Score: 2

      Hmm. I disagree. While it may make for a slightly steeper learning curve, the XP user switching to OSX has the advantage of knowing that everything is consistent. It may be different, but it'll always be the same. So, going to the menubar at the top of the screen is a pain at first, but he'll never be confused by one application doing it his way, and another application doing it Apple's way. Really, what you're describing is just a way to hinder his transition. Why would he ever actually change away from the method that he knows to the new one? There's no way to ween him off of the controls.

    20. Re:Usability... by PythonOrRuby · · Score: 2
      Apple berates M$ for using nonstandard scroll bars. But it's OK for them to do the same.


      Where are nonstandard scrollbars used in Mac OS X? Even in the alternate "brushed metal" interface, the scrollbars are the same widget used in Aqua interfaces. In fact, all of the widgets are the same.

      Speaking of the brushed metal interface, it *is* standard. It's not some hacked-up skinning kludge. It behaves almost exactly like the Aqua interface except that you can move it by clicking on the window background itself. I suspect this ability exists for Aqua windows, but has simply been disabled.
  30. forgive me.. by sjwt · · Score: 1

    I havent used Aqua at all..

    But is it realy fair to compare
    standerd save dialog with that of Notepad?

    --
    You have 5 Moderator Points!
    Which Helpless Linux zealot/MS basher do you want to mod down today?
    1. Re:forgive me.. by Etcetera · · Score: 2


      But is it realy fair to compare
      standerd save dialog with that of Notepad?


      Certainly... shouldn't Notepad be using the standard save dialog? (That's one of the other things mentioned. Why create your own dialog when the system-standard ones already exist?)

      Even SimpleText (the old Mac equivelent to Notepad) has this right.

  31. Apple clutters the interface by renerask · · Score: 0, Flamebait

    The part about not using MDI style applications is in my opinion _very_ wrong. I often have 3 or more applications open when working and I find it damn confusing to look at all of them at the same time. Ever hit something outside the program you are working in and then spend time finding your way back?
    Macs are just crappy to working with if you use more than one program at a time.

    The gui is just not designed to let me move around with speed and ease.
    Linux and Windows are much better at that.

    Bottom line_ Macs are too expensive and slow.
    I like my new dual mp 2000+. Cheaper and faster (and it runs linux properly!).

    1. Re:Apple clutters the interface by Jeremy+Erwin · · Score: 2

      Imagine coding a OpenGL application. You have windows for the compiler controls and debugger. You have source code in another couple of windows. In another app, you have a three-d rendering of some object that will be incorporated in to the app. In yet another app is a pdf rendering of some API reference. And, you have a third party hex editor that you're using to view a texture file.

      Without MDI, you can arrange the windows in any possible manner. With MDI, some applications are guaranteed to take up a rectangular are of screen. If the MDI application has more than one window, it's almost guaranteed that some screen real estate will be hogged by a empty, useless bit of root window.

      MDI assumes you want to work with only one application at a time. That's an assumption taht may or may not be true. On the mac, if you get confused, you can "hide" the extra apps, or minimize the windows into the dock...

    2. Re:Apple clutters the interface by renerask · · Score: 1

      I can resize the root windows to be side by side or overlapping. Easy and painless and usually only needs to be done once in a work session.
      With macs I don't have a choice to work in a way that works smoothly without too many interface arrangements.
      I can use alt-tab fast (in linux/windows). Going to the menu, hiding my current app, selecting to next app is time wasted.
      Time is what I want to use working, not clicking through the gui.
      A very clear example is browsing the internet on a os-x. Damn. You'll never find that window you had opened amongst the other 20+ windows. It's an absolute nightmare.

      I spend a lot more non-productive time on macs than on linux or windows. The mac interface is just designed, not designed for work.
      I'm not saying that just using MDI is solving all problems. That still takes a good program gui.
      There are countless other stupidies in OS-X.
      This desktop mess is just one of them.

      I've become very disappointed with OS-X and consider it a toy for home use.

    3. Re:Apple clutters the interface by tgibbs · · Score: 2
      The part about not using MDI style applications is in my opinion _very_ wrong. I often have 3 or more applications open when working and I find it damn confusing to look at all of them at the same time. Ever hit something outside the program you are working in and then spend time finding your way back?

      This is really something that depends upon whether your generally work in one program, or are always switching between programs. Apple really should have made this a System Preference. I use a shareware utility called ASM, which allows user control of this behavior.

    4. Re:Apple clutters the interface by MoneyT · · Score: 2

      Some hints. command tab switches apps, command ~ switches windows within the app. Hide an application by option clicking outside that app (i.e. on another applications window)

      --
      T Money
      World Domination with a plastic spoon since 1984
  32. Grey is bad? by Anonymous Coward · · Score: 0

    Point 7 is a good point for a mac from my point of view (since I never liked the classic interface), but this quote really gets to me :

    Windows XP has a more colourful and modern look and feel than older versions of Microsoft Windows

    Colorful? Yes. Like your kid sister is colorful when she first learns how to use make-up.

    1. Re:Grey is bad? by justsomebody · · Score: 1, Flamebait

      Personally I hate XP from my guts, as all Windows versions. But at least you have a choice to select colors. AQUA IS WHITE.

      --
      Signature Pro version 1.13.2-3 release 83.5 beta3try7 after-breakfast edition
    2. Re:Grey is bad? by chippcom · · Score: 1

      Yep, I'm with you. What's the strongest and most obvious graphic element of OSX? It's those blue glass scroll bars. My best thinking is that an OS should recede, not conflict visually with the application. I like the basic look and feel of OSX, I just wish it was 'skinnable'.

  33. wtf? by seriousness · · Score: 1
    i was just reading some of this, which one of you sluts posted earlier, and i noticed this bit:

    Microsoft users don't seem to understand that most basic concept; that the computer should adapt to THEM, and not make them adapt to it.

    the writer was complaining about the many ways to close a window in windows. don't they realise that by providing a variety of way to acomplish a task, the user can choose the way they like best? i.e. the user is not constrained by the computer?

    mac-philes are fucked up. sorry, but when it gets like this, it can be true.

    1. Re:wtf? by dhartshorn · · Score: 1

      You read the entire article and all you got was a complaint about having multiple means of closing a window? Then you just don't get it. There's nothing bad about multiple methods. There is something bad about inconsistency and complexity. The article showed, in great detail, just how inconsistent and complex something very simple can be.

      It's clear what's fucked up here.

    2. Re:wtf? by Anonymous Coward · · Score: 0

      So you're saying that Macs conform to the user because there's ONE WAY of doing something? What if I don't want to close the window by clicking the close box? Windows conforms to me by letting me close it in other ways. Mac doesn't. THAT is the point of the other poster.

    3. Re:wtf? by MoneyT · · Score: 2

      then hit command w, or go to file-> close. Or if it's the last window open in an app or you want to close all an apps windows, you could hit command Q. How many more options do you need?

      --
      T Money
      World Domination with a plastic spoon since 1984
    4. Re:wtf? by rjung2k · · Score: 1

      By your reasoning, a car with fourteen different accelerators would be vastly superior to a car with one.

    5. Re:wtf? by dhartshorn · · Score: 1

      No, that's not what I'm saying. At what point did I (or the article) say that having only one way to do anything is good. I could quote myself, but you should be able to find me in the original with no trouble. Read it this time.

      The article is about screwing up the methods Windows provides. The original poster missed that, an error I can only attribute to his desire to flame Mac users.

      FWIW, there are several ways to to most things on Macs. If you'd ever used a Mac instead of trolling /. for comments, perhaps we wouldn't be here.

      I will note, however, that I'm glad Windows retains its keyboard menu access. At least when the mouse driver dies, I can do a controlled reboot instead of simply pulling the plug.

      PS. Log in and let us know who you are, next time. If you don't have the guts to stand behind your comments, STOP SHOUTING them to the four winds.

  34. Uh... by miketang16 · · Score: 0, Troll

    What I got from that document:

    Please don't confuse our users with your fancy advanced Windows features.

    --
    -------
    "In times of universal deceit, telling the truth becomes a revolutionary act."
    -- George Orwell
  35. Doesn't acknowlege Windows' keyboard superiority by Paul+Carver · · Score: 5, Insightful

    They mentioned keyboard shortcuts, but the left out the most important thing that Windows gets right.

    I haven't used a Mac in five years, but I have used Linux and keyboard support sucks. Sure, if you never run X at all you can do anything from the keyboard, but type "startx" and you're screwed.

    In Windows you can do everything except specific drawing tasks without having a mouse. (Using Autocad I can actually do some drawing tasks without a mouse using keyboard coordinate entry.) And dialog boxes, I never reach for the mouse to answer a Windows dialog box.

    The very first version of Windows I used was 3.0 and it got this right. I've never seen a non-Windows GUI OS that matched the keyboard support of any Windows OS.

    Why can't Gnome and KDE developers adopt the simple standard of requiring a "hot-letter" for every menu item and every dialog box item including buttons and selection widgets.

  36. Actually, even MSes own programs have this problem by Unknown+Poltroon · · Score: 1

    I do user support of win 98 and MS Office, and the controlls arent the same across all of Offices programs. AS I recall, outlook is horribly inconsistant in how things are done, compred to the rest of the Office suite. ANd if you go from 98 to XP, they change all the interfaces around, generally for no good reason as far as i can tell. Walking users through doing something that they used to do on their own is really annoying, especialy when at the end, they wind up with the same interface screen as they had before, only there are 4 extra steps to get there. For a comparison, try setting up a new exchange server mailbox in outlook 98, then try it under xp.

    I dont even bother trying to explain Microsofts stupidity. My responses now are , well, its a bad design to confuse you and keep me employed, and It wasnt my decision to force this change on you, sorry.

    --
    All Troll + "offtopic" mods are meta moderated as "Unfair", because you abused the system.
  37. Mac OS vs XP vs KDE 3 by SuperDuG · · Score: 2
    Okay after taking a look at the latest gnome beta's, it doesn't get to play with the big kids for right now. I find it absolutely amazing to see where the GUI has come in the last 5 years. Does anyone else remember when a 3D button or smooth corner window was something that was only seen in science fiction movies?

    Which one is the best? I wouldn't know I use all 3 and I really like all of them, well I like Mac OSX and KDE3 a little better because they're a tad more customizeable, but with a little tweak XP and other tools it's all a matter of time before you feel at home with your box.

    The one thing that they are all missing is one very simple thing. Not everyone runs at 1200x1600 resolution. None of these new GUI's look good in 800x600. When the menu bar takes up 10% - 20% of your window then you really have problems. Win98 and MacOS 9 took low resolution into account and put less crap on the screen. I definantelly think that enlightenment and blackbox have the right idea about how to appeal to the entire market.

    But how does Linux and MacOSX make it possible for me to have my enlightenment or blackbox directly on top of the core OS? Simple they use standard tools and binary compatability, Linux and BSD. Windows however just plain sucks at anything less that 1024x768, but also windows XP's minimum requirements are a Geforce2 and like 512 megs of ram too, so windows assumes you also went out and barfed out another $300 for a monitor.

    I prefer Linux, but I don't mind Mac OSX and I get by using windows XP. All-in-all they are all starting to share a common theme. "Be appealing to the eye and place the common tasks within easy reach, with as little fluff as possible."

    --
    Ignore the "p2p is theft" trolls, they're just uninformed
    1. Re:Mac OS vs XP vs KDE 3 by Anonymous Coward · · Score: 0
      Even you would probably admit that file extensions are flat out wrong anyway. That is the worst misfeature of VMS too. It still gives me nightmares.

      The part about not using MDI style applications is in my opinion _very_ wrong. I often have 3 or more applications open when working and I find it damn confusing to look at all of them at the same time. Ever hit something outside the program you are working in and then spend time finding your way back? Macs are just crappy to working with if you use more than one program at a time.

      The gui is just not designed to let me move around with speed and ease. Linux and Windows are much better at that.

      Bottom line: Macs are too expensive and slow. I like my new dual mp 2000+; it's cheaper and faster (and it runs Linux properly!).

    2. Re:Mac OS vs XP vs KDE 3 by Anonymous Coward · · Score: 0

      "Does anyone else remember when a 3D button or smooth corner window was something that was only seen in science fiction movies?"

      You know, many of those scifi movies were just using Kaleidoscope (or Aaron) on a Mac at the time.

    3. Re:Mac OS vs XP vs KDE 3 by Anonymous Coward · · Score: 0

      XP doesn't take quite so much power. It runs swimmingly on 256 RAM on a Pentium 600, and thats only with a TNT2 video card. XP is not graphic intensive at all. Considering you can get 256 MB of RAM and a TNT2 for $100, thats nothing, less than the cost of the OS. Even a Geforce 2 MX is only $60 @ newegg or other retailers.

      Apple demands more pricey upgrades for their system, and proprietary often times at that. I'm not even going to touch the monitor bit because 1024x768 runs fine on a 17" and good 17 inchers are well below $300 at the moment.

  38. Re:You guys really eat Apples PR up. Mindless shee by Golias · · Score: 2
    They show you the gems of there interface compared to the most lackluster parts of thier competitors.

    This was not a Win vs. Mac OS comparison. It was an article for the specific purpose of telling developers what common Windows application misfeatures one should avoid when writing a Mac port. The fact that Win95 (which is where I assume where they pasted those images from) showcases some of these misfeatures was just convenient for them.

    I don't know how many Mac users I hear saying that the Mac "Launch bar" (name?) sucks.

    If you are talking about the Launcher, that was a shareware App that Apple liked and offered as an optional tool in System 7, as a way to let your young kid run apps on your Mac without being able to delete your system files. Since many schools who used Macs used the Launcher to lock down their desktops and prevent studens from hacking their boxen, a lot of teens in the 90's assumed that the Launcher is what MacOS was, and wrote long screeds on message boards about how "restrictive" the OS is.

    On the other hand, maybe you are talking about the Dock. The Dock is an application bar, which behaves a lot more like the one from NeXT than the menu bars from Windows and Gnome, which a lot of old-skool Mac users don't care for. I've grown to really love it, except I wish there was either an option for locking up the Dock's screen real-estate, or else a better implimentation of the window maximization feature, so windows would not sometimes extend under the Dock when I maximize them.

    --

    Information wants to be anthropomorphized.

  39. MDI by SiChemist · · Score: 1

    I tend to agree with you about MDI. On the other hand, I love Mozilla's tabbed browsing. Does that make me a hypocrite?

    1. Re:MDI by justsomebody · · Score: 2

      No, it just proves a point from Gnome human interface design. MDI should be used very rare with extreme prejudice. But when MDI is used that way (and it should be used), MDI rules.

      --
      Signature Pro version 1.13.2-3 release 83.5 beta3try7 after-breakfast edition
    2. Re:MDI by oliverthered · · Score: 1

      Mozilla's tabbed browsing isn't MDI in the clasical sense.

      You can open in another window if you want.
      With tabs all pages are always full window.

      MDI is ok if you're only going to look at one thing at once and it's full screened.
      MDI in visuaila studio and Microsoft management consol is just plain evil, like trying to find the buttons on a straight jacket.

      --
      thank God the internet isn't a human right.
    3. Re:MDI by Anonymous Coward · · Score: 0

      Only if you tile or cascade them. Well, you can't do that, so it's not MDI, it's just a multiple-document interface with no caps.

  40. File-name extensions by Door-opening+Fascist · · Score: 1
    14. Use File Name Extensions

    Why does it require filename extensions? If it is based on BSD, then why can't it use the file(1) utility, which can determine file type using algorithms rather than by something as malleable as three letters at the end of a name?

    1. Re:File-name extensions by Jeremy+Erwin · · Score: 2

      three letters? hah! At least in macosx, you can use more than that. For instance .pbproj is the extension for "Project Builder" project files.

    2. Re:File-name extensions by Anonymous Coward · · Score: 0

      Because it's too expensive. Imagine navigating a network drive looking for a file to open...

    3. Re:File-name extensions by sg_oneill · · Score: 2

      INTEROPERABILITY!!!!!!
      I maintain a site that has , a linux server, a coupla win pcs, a coupla linbox pc's and a shiteload of macs.
      One of the biggest problem is the mac's reliance on metadata to determain filetype.
      Far too often I've had one of the graphic designer fluffheads panic because the've saved , like, 1000 jpegs with no .jpg extension and it works fine on the macs, and as soon as it ends up on the linboxen or pcs the said machines just don't know where to start.
      Short of apache developing a mod to look in the .AppleDouble nests to find the right mime type, it just is a pain in the arse.
      3 letter file types solve this whole metadata problem perfectly.
      It's a perfectly good idea.

      --
      Excuse the Unicode crap in my posts. That's an apostrophe, and slashdot is busted.
    4. Re:File-name extensions by Anonymous Coward · · Score: 0

      Every modern OS supports long filenames and extensions, not just macosX. Some don't make a distinction between the filename and the extension.

    5. Re:File-name extensions by Dopefish128 · · Score: 1

      The thing is that it's not necessarily a file that has the extension. A .pbproj like mentioned in one of the replies is actually a folder, but it's treated like a file because of its extension. Same with application bundles. Run file on one and it returns that it's a directory.

      --
      "Knowledge is power. Power corrupts. Study hard. Take over the world."
    6. Re:File-name extensions by Anonymous Coward · · Score: 0

      Give it a rest already. Even the Win95 betas could have any number of letters in the extension.

  41. More good reading... by Etcetera · · Score: 2


    For those of you that missed the link at the beginning of the article, take a look at Apple's full Aqua HI Guidelines (or in PDF format). It has *tons* of specific examples and screenshots useful for some of the theory and design behind the current GUI.

    I have to agree with the earlier post that OS X is somewhat of a step backward in usability overall. Although I do appreciate some of the innovations (sheets,...) I still find the standard OS 8/9 "platinum" interface to be easier to understand. (It's an interesting comparasion.)

    I don't know -- once Apple gets its butt in gear and gives me a SPACIAL FINDER and uses METADATA PROPERLY I might feel different. :)

  42. I love Apple as much as the next guy... by rgoer · · Score: 1

    ...but their hipocracy gets, at times, a bit hard to swallow. This document speaks, rightly so, to the "simplistic-beauty-through-UI-consistency" factor of Mac OS X, thanks to the Aqua Human Interface Guidelines. And, it should be noted, I've got no beef whatsoever with the Aqua HIG as a concept, nor (for the most part) as far as the execution of that concept is concerned. However, did anybody else notice the glaring absence of any iApp from this Switch Document?

    The iApps (iDVD, iMovie, iPhoto, and iTunes) come together like Voltron to form the ease-of-use flagship of the iMac/Mac OS X/"Digital Lifestyle" movement. And do the iApps even remotely follow the Aqua HIG? Hell no!

    Apple dedicates a whole subsection to this point: "Avoid Custom Controls." However, each of the iApps contains, in the app package contents, its own .rsrc file full of bitmaps defining very, very custom interfaces! Sure, all the buttons are still Aqua, but they've got this goofy "brushed metal" .pict texture and they toss the button placement guidelines out the window.

    Just like Apple created all sorts of "special exceptions" to the rules of the Carbon layer for Finder.app, they seem to have written a myriad errata to the Aqua HIG pertaining to developing an iApp (but kept this updated copy of the Aqua HIG for themselves).

    Again, I should say that I would love to see Apple succeed with their "Switch" campaign... but for once I'd like to see some practicing to go with the preaching!

    1. Re:I love Apple as much as the next guy... by wadetemp · · Score: 2

      The article was obviously not meant to be a full HIG document for all Mac applications. Don't take it to be such.

      There is a separate guideline on the appearance of "device" applications. Apple's guideline is that any application that simulates or interacts with a hardware or "real life" device should have the aluminium look/feel, which can be applied to any application the developer in 10.2, from what I've read.

    2. Re:I love Apple as much as the next guy... by Anonymous Coward · · Score: 0

      jesus - I've seen this comment several times...

      You people are just idiots who can't (as usual) read.

      It says " If you must use custom controls, be sure to use them for unique interface elements; for example, avoid replacing a standard checkbox, for example, with a custom one."

      So, when there is no standard control element for what you are doing, it's OK to use a custom one. The basic gist of this is, don't re-invent the wheel each time. Also - a button with a picture resource is a STANDARD UI element. It's in Interface Builder - been there since NeXTStep (say, 1990).

      The goofy, "brushed metal" PICT texture is now part of the OS as a standard UI element, for better or worse.

      If I posted a half-informed comment about how Linux does such-and-such stupid, I would have a swarm of morons all over me in a hartbeat, pointing out that I shouldn't talk about things I don't know anything about.

      Apparently there's a bit of a double-standard going on.

      Moral of the story - don't spout off when you don't know what you are talking about.

    3. Re:I love Apple as much as the next guy... by wilson_c · · Score: 1

      As of 10.2, the brushed aluminum look is available systemwide. It is not a per-application custom control in any sense.

      The look is intended for applications that interface with real devices (iTunes -> iPod, iMovie->firewire camera, iPhoto->digital camera) or applications which replicate the functionality of physical devices (i.e. iTunes in its non-iPod-syncing, mp3 player capacity).

  43. Improves creen real-estate by SuperKendall · · Score: 2

    I like to think of it as improving scalability across multiple windows - if you have an app (like a browser) that has many windows open, then you loose the space the menu bar takes up in each window. That leaves you more room for things like tabbed interfaces!!

    The only thing I don't like about having the menu at the top of the screen is that I wish a menu bar would appear in each display an app is located in... or perhaps a "menu follows mouse into display" feature that would migrate the menu bar when the cursor changed screens. As it stands other monitors besides the primary are mostly good for storing palettes from active apps or apps that are pretty much self-contained on screen and need little menu interaction (like iTunes).

    Good keyborad acess helps a lot though. There are a number of apps I use where I almost never use the menu bar, so it's OK to be out of the way.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  44. this could be positioning for pc strategy by dwgranth · · Score: 1

    I know most of you guys are thinking that apple's PR machine is just cranking out the crap. Which could possibly be true... but after the post/article about apple maintaining an x86 version of OS X (http://apple.slashdot.org/article.pl?sid=02/08/31 /195208&mode=thread&tid=179) it makes me wonder why they are only comparing the UI of the two OSes. It's like.. wow.. the windows behave differently... which really doesn't matter to too many people. And their target audience(developers) don't care too much about the minor differences in UI.. just as long as someone pays them to develop applications. What I was surprised about was that Apple's article did not mention supposedly key differences in hardware that made Apple "so much faster"... which has been their key selling point before. And honestly, I wish OS X would be released for x86 platforms.. i would buy it.

    1. Re:this could be positioning for pc strategy by Anonymous Coward · · Score: 0

      This article is not new at all. It's just a revised (for OS X/"Switch") version of a document that has been around for (and modified over) many years.

  45. Photoshop doesn't conform. by upstairs · · Score: 2, Interesting

    It really irritates me that in photoshop for OSX Command-H doesnt hide the application. As displayed by the length of the apple usability documents, the priority for this OS should be usability, and adhering to the maintenace of vital functional key groupings throughout the entire OS.

    Great to see Apple promoting usability issues, something a certain competitor in the OS industry would do well to follow.

    1. Re:Photoshop doesn't conform. by dalamar70 · · Score: 1
      I don't use Photoshop but it's possible that CMD-H was already used by Photoshop since before OS X. This leaves Adobe with the choice of "breaking" the Aqua guidelines or "breaking" their own interface.

      BBEdit from Bare Bones faces such an issue. Their solution is to allow users to remap Command-H to whichever they prefer. See their FAQ about Command-H.

    2. Re:Photoshop doesn't conform. by freaq · · Score: 1

      possible? actual. at least in 3.0 (it isn't so 'must-have' for me to keep current) cmd-h is used to "hide" the marching ant effect on the border of whatever you may have selected. quite useful in conjunction with the undo/redo, you can see what the effect will be much more clearly without having to use your imagination or losing your selection.

      --
      united states nuclear device terrorist bioweapon encryption cocaine korea syria iran iraq columbia cuba
    3. Re:Photoshop doesn't conform. by Anonymous Coward · · Score: 0

      Actually, Photoshop 7 will respect Cmd-H for Hiding if you select Preferences->General->Use System Shortcut Keys. The bummer is that you can't do the same for Illustrator!

  46. Also... by billbaggins · · Score: 5, Informative
    They seem to have taken some pains to make sure it Does The Right Thing. At least, check out this part about file extensions from here...
    Any file with the hide extension flag set and a known extension has that extension hidden in the Finder. When users edit the name of such a file, they edit only the user-visible portion. If they explicitly type in a known file name extension for the file, either the Finder warns them that what they're doing may change the type of the file (if they enter a different file name extension), or the Finder changes the state of the hide extension flag to show the extension (if they enter a new file name with the proper, currently hidden extension for the file). In all cases, the Finder allows users to make the changes if they wish. What users see in the Finder is what they typed when renaming the file, whether or not they included an extension.
    In other words, if you want to see a file extension, you'll see a file extension. If you don't see a file extension, and you type one, you'll see the new one, and it will be used, and the old discarded if necessary. Contranst Windows, where if extension-hiding is on, and you type the name "index.html" for a file currently named "index.htm", the result is a file named "index.html.htm"... that is to say, the Wrong Thing.
    --
    "The best argument against democracy is a five minute chat with the average voter."
    --Winston Churchill
    1. Re:Also... by i_luv_linux · · Score: 1

      If the extension-hiding is on, that is means that you don't want to edit extensions. So what is wrong is that, giving this type of an example. In Windows this is a good choice. If you want to edit extensions you turn on extensions and edit them. Turning off extensions means less clutter on Windows Explorer, because you only see the file names, and the type of the files are obvious from the icons.

    2. Re:Also... by Anonymous Coward · · Score: 0
      So in order to change the extension of a single file, you need to do a global reconfiguration of the entire interface (twice, actually, since you need to change it back afterwards), where OSX is smart enough to realize you are trying to change the extension and just confirms your action is intensional.

      This why extension-hiding is useless as implemented in Windows, because you can't correctly change extensions when you need to, where in OSX you can. It makes the UI both easier to use and more powerful.

    3. Re:Also... by stripes · · Score: 3, Insightful
      And the part about not using MDI style applications is in my opinion _very_ wrong. I often have 3 or more applications open when working and I find it damn confusing to look at all of them at the same time.

      In 10.2 command-oprion-H is "hide all other apps"; don't want to see other apps? Use it.

      Prior to 10.2 the "hide all other apps" didn't have a consistant short cut, but it was always in the same place in the application menu (second manu on the bar, between the apple and the file menus).

      Personally I like having, oh, say, my IRC client up, and pushing the minimised iTunes controls between the IRC connect/notify windoes and the users window. Or maybe closing the users window and having a DVD play there. Or sticking the compile window from Project Builder below the chat area, or Backup's progress bar close to the...

      Ever hit something outside the program you are working in and then spend time finding your way back?

      No, never. That's not to say from time to time I don't click the wrong thing and get the app I don't expect, but I have found it trivally easy to "get back". Command-H always hids the current app in OS X, so if you didn't want the app up at all (say the pesky finder that unhides if you miss a window and click the desktop) Command-H hides it and switches you back to the last app. If you wanted that app un-hidden, you can return to the last app by doing Command-Tab in 10.2, or prior to 10.2 the shareware HotApp program let you use Opt-tab for that.

      Macs are just crappy to working with if you use more than one program at a time.

      Sure, if you spend zero time learning how to use them they are bad at stuff. Much like spending no time learning how to drive a car makes them bad transportation devices, and great devices for crushing expensave stuff, or spending zero time learning to interact with people in a bar makes it hard to get a date, but easy to wear a drink. Most stuff does require a little effor to learn! Sometimes the very tiny effort of finding someone who likes the thing and saying "er, why do you like it?", or "how do I do this?". Sometimes - the horror - the supreime effort of reading a book!

      The gui is just not designed to let me move around with speed and ease. Linux and Windows are much better at that.

      I'm not a big windows fan, but I do admit their GUI lets you madly rush about and has defaults that don't suck too hard. Linux seems about like all the other (non-Mac) Unixes and has random GUIs on top of it that conflict a bit, have defaults that suck hard, and after tons of effort in getting them tuned to how you like to operate, tend to work better then the out of the box configurations of Windows or MacOS. Or corse I expect if you spent the same effort to customise the other two you would get the same effect.

      Bottom line: Macs are too expensive and slow. I like my new dual mp 2000+; it's cheaper and faster (and it runs linux properly!)

      Well, they sure aren't cheap (except maybe the iBook, and maybe the DVD-writer iMac up agianst name brand PCs....definitly not as cheap as white box PCs though!).

      On the other hand they sure don't seem slow. I was happally writing CD-Rs for backups watchign an IRC channel and DVD, running iTunes and nothing seemed the least bit slow. Ripping CDs seems way way faster (and simpler) then Intel-ish PCs with 2x to 4x the clock speed! Compiles seem to go by just as fast as any other IDE system (laptop, so no SCSI option). Maybe for most tasks the slowest thing is not the CPU, but the memory wall, or the disk wall, or just plain the person sitting there doing work.

      Of corse I don't think I would go out and buy rack after rack of Xserve boxes for a render farm, then again, it would be one of the platforms I would evaluate. I kind of susspect the Intel-ish systems would win out there though.

    4. Re:Also... by King+Babar · · Score: 2
      OK, so I have an interesting situation. I've used Macs since 1984, but I'm a fast typist who does NOT want to be mousing around all the time. Given that background, the following things intrigued me:
      Prior to 10.2 the "hide all other apps" didn't have a consistant short cut, but it was always in the same place in the application menu (second manu on the bar, between the apple and the file menus).

      OK, so the one thing that continues to annoy me about even Mac OS X is that keyboard shortcuts are apparently not believed to be that important, despite the exhortation in this "Switch" document that you shouldn't, um, "innovate" there. Frankly, something that should be in every app should *certainly* have a keyboard shortcut. I know that's personally why this (very useful!) feature didn't bubble to the top of my "things to know" list.

      If you wanted that app un-hidden, you can return to the last app by doing Command-Tab in 10.2, or prior to 10.2 the shareware HotApp program let you use Opt-tab for that.

      You have made my week! :-) Seriously, this almost completely vanquishes my desire to have a virtual window manager available. One of the big pains of all time in the Mac interface has always been having to mouse around for other running apps. Not any more! Not only does Command-Tab give you back your last app, it actually cycles through all the apps you have running on the dock. At least, that's what it appears to do. I'm speechless with joy! I really am!

      But, to paraphrase Dr. Strangelove, this amazing feature only saves the world if Apple tells people about it! This wasn't on the top Anything list of groovy new Jaguar features people were touting, but it's worth *at least* $50 to me all by itself!

      I think the only thing that would make me happier is if there turned out to be an easy-to-use and universal method to navigate around buttons and fields in dialog boxes. That's something I still truly miss.

      --

      Babar

    5. Re:Also... by stripes · · Score: 2
      Frankly, something that should be in every app should *certainly* have a keyboard shortcut.

      Maybe...preferences are in every app, but I don't find a strong need for a keyboard short cut (even if command-; seems to be widely used). "About app", and "Check for update" as well. But maybe I'm just in a contrary mood. I do think "hide others" should have one (which is why I'm happy it does!) Apple is also starting to push a consistent short cut for "cycle windows" which is nice.

      I have some vagus suspicion that "hide others" didn't exist until after Apple removed "single user mode", and they just didn't test it long enough to decide it rated a command key. So until it got field tested they left it alone. Maybe.

      Not only does Command-Tab give you back your last app, it actually cycles through all the apps you have running on the dock. [...]But, to paraphrase Dr. Strangelove, this amazing feature only saves the world if Apple tells people about it!

      Well the command-tab goes-to-last-app I didn't see anywhere, but the command-tab cycles apps I definitely saw in one of Apple's flimsy almost useless documentation kits, maybe for 10.0, or "X Public Beta". I was unaware that it had changed to "go to last app then cycle" in 10.2 until I was telling someone how cool HotApp was and they said "dude command-tab does that!". Fortunately HotApp still gives the way-useful single press short cut for "copy selection to clipboard, switch to last app, paste". Amazingly useful.

      I think the only thing that would make me happier is if there turned out to be an easy-to-use and universal method to navigate around buttons and fields in dialog boxes.

      Does the "Full Keyboard Access" stuff found in System Preferences under keyboard settings count? If not how does it fall short? (I don't use it myself)

    6. Re:Also... by King+Babar · · Score: 2
      I think the only thing that would make me happier is if there turned out to be an easy-to-use and universal method to navigate around buttons and fields in dialog boxes.
      Does the "Full Keyboard Access" stuff found in System Preferences under keyboard settings count? If not how does it fall short? (I don't use it myself)

      The "full keyboard access" stuff can sort of do this, but it still seems to have some issues. In particular, with a busy dialog it can take you forever to cyle around to the (non-default) "cancel" button you really did want to hit, since the decided to optimize text entry/radio-button entry items over just plain buttons. That said, it's definitely possible I'm still missing some magic incantation. Documentation on most of this stuff, is, as you said, pretty flimsy.

      Anyway, my latest revelation was that my iBook did indeed have "page up" and "page down" buttons (fn arrow keys), which means that I can now cycle through Mozilla tabs. Woo hoo! (So does anybody see a pattern here? :-))

      --

      Babar

  47. Windows GUI... by Cyno01 · · Score: 2, Informative

    If you really hate the 'XP Look', but setting it to classsic seems too boring, try Windowblinds or Hoverdesk, two great apps that will skin your entire interface and hardly use any system resources, if you have the time you can make your own skins, or you can get one of thousands at sites like deskmod.com or lotsofskins.com, i change my windowblinds skin about biweekly just to keep things fresh, the great thing about windowblinds is you can have lots of extra buttons, i have some skins that have lock on top buttons, buttons to launch notepad or the screen saver and some even have winamp controls built in, another cool feature of all windowblinds skins is that you can roll the entire window up into just the top bar, saving some space without minimizing, i've never taken the time to configure hoverdesk, but its interesting, easily customizable, and makes your desktop nearly incomprehensible to anyone else, but if you love that aqua mac interface so much, theres a windowblinds skin called OSXP, http://deskmod.com/?state=view&skin_id=2643

    --
    "Sic Semper Tyrannosaurus Rex."
    1. Re:Windows GUI... by Anonymous Coward · · Score: 0

      Mod parent down. Both programs are NOT free.

    2. Re:Windows GUI... by Anonymous Coward · · Score: 0

      If you use Linux, there are Aqua-like themes for GTK and IceWM that are very nice.

      http://themes.freshmeat.net/projects/osx2/?topic _i d=923%2C951
      http://themes.freshmeat.net/projects/ liquid/?topic _id=925%2C952

  48. Re:Doesn't acknowlege Windows' keyboard superiorit by Sax+Maniac · · Score: 5, Insightful
    It's small, boring things like that that really piss me off about all almost open-source UIs. The reason why is this: keyboard navigation is hard to get right. Most developers seem to want to spend all their time play with time-wasting, usability-destroying "themes" than actually improve the usability of their app.

    It's hard, typically, because the second you change the wording of a menu or dialog dox, all the keyboard navigation letters have to change.

    The single best way to fix this stupid problem is for keyboard shortcuts to be automated but overrideable in GUI toolkits. When I write a menu item, it should scan the entire list of menu items, and generate keyboard mnemonics for everything. It's not a terribly complicated algorithm, but it is tedious to do by hand. Sometimes, it will come up with lousy results, and some menmonics can't be deduced from the text, but it would solve the problem of developers completely forgetting about them.

    We've put a ton of work on making nedit keyboard accessible. Almost everything you can do with the mouse, you can do with the keyboard. It's a huge amount of work, but we wouldn't have it any other way. Alomst every GUI item can be hit with the keyboard, and vice-versa.

    Want to know why I won't use Mozilla on Windows? When a yes/no dialog pops up, I can't type 'Y' or 'N' to dismiss it. Stupid things like this, problems that were solved 15 years ago, still plague us.

    --
    I can explanate how to administrate your network. You must configurate and segmentate it, so it can computate.
  49. Re:You guys really eat Apples PR up. Mindless shee by iPaqMan · · Score: 1

    Ok, then if its not a "Win v. Mac OS Comparison" then why not find some example in there own OS. Don't tell me that there are no faults in, current or past, Mac OSs to point out.

    This article is just put out as fodder for their "Switch" campaign! Am I the only one who sees this???

    I admit Apple does have some of the best PR people out there. Kudos to them. ;)

    And yes, I meant the dock.

  50. A 20 year old irony by tkrotchko · · Score: 1, Flamebait

    Apple's trash can.

    You don't eject disks, you throw them in the trash can.

    Doesn't that strike you as odd given Apple's criticism of virtually every other UI over the years?

    --
    You were mistaken. Which is odd, since memory shouldn't be a problem for you
    1. Re:A 20 year old irony by upstairs · · Score: 1

      Basically what the user wants is something that ejects a disk that is located where the bin and other application icons are (the dock). So therefore why dont you have a seperate eject and bin icon. Well imagine having those two buttons right near each other and by dragging a disk to that area you might accidently delete it rather than eject it.

      Furthermore, all current mac keyboards have their own eject button, dont see any other keyboard conglomerates with that function across all lines.

    2. Re:A 20 year old irony by wadam · · Score: 1
      You don't eject disks, you throw them in the trash can.

      Actually, you do eject disks in OS X. When you hold a disk and begin to drag it, the trash can on the dock becomes an eject icon. Similarly, when you hold a CD-R and begin to drag it, the trash can becomes a CD burning icon. I agree with you that throwing disks away was a UI problem in 9, but Apple has really cleared that up.

      Adam.

    3. Re:A 20 year old irony by WWWWolf · · Score: 1
      n'th time: You can eject disks in various different logical ways in Mac! The trashcan thing isn't the only way.

      The only real problem I have with Mac is the single menubar. It's always too far away - and I also think one menubar should do one thing, a single menubar that changes depending on active application is just confusing. =/

    4. Re:A 20 year old irony by hayne · · Score: 3, Informative
      Not anymore.
      1. Modern Mac systems have a hardware eject button.
      2. OS X provides an eject icon for the Finder window toolbar.
      3. There are keyboard shortcuts for ejecting a disk.
      4. The old drag-to-trash method still works (backword-compatibility) but the Trash icon changes to an eject symbol if you start dragging a disk icon towards it.
    5. Re:A 20 year old irony by Anonymous Coward · · Score: 0

      always made sense to me. anything you didn't want in the system anymore, you just chucked in the trash.

      want to get rid of a file? drag it to the trash.
      want to get rid a disk? drag it to the trash.
      want to get rid of some text in a document? highlight it and drag it to the trash.

      and so on but without deleting it.

      deleting, erasing, overwriting etc is a different (although related) process. dont know what its like in OSX, but in 9 those commands are nested somewhere else. erase disk, burn cd, empty trash are in the special menu.

    6. Re:A 20 year old irony by k_187 · · Score: 2

      Ummm, no. In OS X, when one begins to drag a disk around the desktop the icon of the trash changes into an eject icon.

      --
      11 was a racehorse
      12 was 12
      1111 Race
      12112
    7. Re:A 20 year old irony by Anonymous Coward · · Score: 0

      and how would i know to drag the icon in the first place? hmm?

      'to eject a disk, start dragging the icon around until you see eject sign appear'

    8. Re:A 20 year old irony by ForemastJack · · Score: 1

      Whoah there, Thunder. You should sit down and use OS X before you pull the trigger.

      In OS X, when I select a bit of removable media (CD, mounted disk, etc.) in the Finder, the Trash icon changes to a standard Eject icon. If it's a CD-R(W) that I've written to, the icon changes to a Apple's standard "burn" icon.

    9. Re:A 20 year old irony by movement · · Score: 1

      Wrong.

      It is (debatably) an improvement, but it is
      most definitely not "really cleared up".

      It is simply not discoverable. Think about it -
      what possible reason would the user have for
      starting to drag the disk somewhere ? There is
      nowhere visible to drag it to !

      Changing the icon when a drag has started is
      exactly when it is too late.

      [My dad, btw, actually made himself an extra
      trashcan with an eject disk icon. That is -
      it was SO confusing, even a user capable of
      doing this preferred to have a separate always-visible widget that provided a clear
      dialogue.]

      --
      -- Remove the trailing '\0' to email me.
    10. Re:A 20 year old irony by Anonymous Coward · · Score: 0
      When you hold a disk and begin to drag it, the trash can on the dock becomes an eject icon.

      An excellent solution!

      Why not take it further and only have one icon in the dock that morphs appropriately to the correct application? That would strike down those dock-hogs-the-desktop flamers.

    11. Re:A 20 year old irony by freaq · · Score: 1

      how is that a problem? "too far away" isn't an issue unless you have your mouse set for the slowest speed. with windows, you have to aim the mouse vertically at a narrow band under the title of a window that might be placed anywhere on the screen, . with macos, you only have to aim horizontally. the vertical part requires _only_ moving the mouse up. no vertical aim required.

      --
      united states nuclear device terrorist bioweapon encryption cocaine korea syria iran iraq columbia cuba
    12. Re:A 20 year old irony by Anonymous Coward · · Score: 0

      Moderated "Flamebait"?

      Mac fanatics really are insecure.

    13. Re:A 20 year old irony by Anonymous Coward · · Score: 0
      There are keyboard shortcuts for ejecting a disk.

      This one bugged me with OSX. For years I used the command-Y keyboard shortcut ("Put Away" on the menu) which would umount discs and eject them. When I would go over macs with my cow-orkers I'd explain to them they had to use "Put Away" (command-Y) and not the more obviously sounding "Eject" (command-E) because Eject leaves the image mounted on the desktop (meant for those days when macs had a single floppy drive: you could 'eject' a disc, still open it up, and copy files to a newly-inserted floppy. The mac would then just ask you to switch discs back and forth as required). The problem with Eject is that people have all these images left on their desktop that they don't "know" how to get rid of, and occasionally they try to open one, or do something with it and sure enough... the OS asks for it back and they get all pissed off.

      Anyway, with OSX they did away with "Put Away" AND command-Y, and now it's all "Eject" and command-E to get the old "Put Away" functionality! All these people I've spent YEARS trying to get to do something right now tell ME I was wrong! I'm glad it does more what people expect, but damn I wish they'd kept Command-Y around as the keyboard shortcut since I'm always typing it and getting no response.

    14. Re:A 20 year old irony by WWWWolf · · Score: 1

      In MacOS the menu bar is at the same place all the time, but it is far away - the "aiming" thing isn't an issue for me.

      The bad thing is that it's not same. The contents of that menu bar depend on the active application! Activate the application first, then open the menu. Grr.

      This also probably means that I can't get SloppyFocus, the God's Chosen Window Focusing Method, for MacOS, and if there is, it makes the menubar use pure hell? (SloppyFocus = focus the window when mouse enters it, but don't blur on exit from window).

    15. Re:A 20 year old irony by Anonymous Coward · · Score: 0
      The old drag-to-trash method still works (backword-compatibility) but the Trash icon changes to an eject symbol if you start dragging a disk icon towards it.

      I thought Apple detested such interface changes...

    16. Re:A 20 year old irony by freaq · · Score: 1

      ! !
      i had not thought of that. thanks.

      --
      united states nuclear device terrorist bioweapon encryption cocaine korea syria iran iraq columbia cuba
  51. Right Click by bwags · · Score: 0, Troll

    My biggest gripe about the mack is the lack of right click context menus. I like them, I use them, and I miss them when I am on a Mac.

    1. Re:Right Click by Anonymous Coward · · Score: 0

      ???? OSX has right click context menus... I use them all the time.

    2. Re:Right Click by Tim+Browse · · Score: 3, Informative

      MacOS has had context menus since MacOS 9 (or possibly MacOS 8 - I'm only a part-time Mac user).

      You control-click (e.g. on a file in the finder) to get them - or if you have an MS mouse, the driver converts* a right-click to a control-click, so it works pretty much like Windows/X.

      Tim

      * Although MacOS may actually just support the right-click natively now - I don't know.

    3. Re:Right Click by Anonymous Coward · · Score: 0

      My biggest gripe about the mack is the lack of...

      "The Mack Dad'll make ya... the Daddy Mack'll make ya..."
    4. Re:Right Click by Elwood+P+Dowd · · Score: 3, Informative

      Yeah. As a million people have said before:

      Any two button USB mouse is automatically supported by MacOS X, and right clicks work like control-clicks (that is, they invoke contextual menus).

      --

      There are no trails. There are no trees out here.
    5. Re:Right Click by Have+Blue · · Score: 2

      OS X does support right-clicking natively. It also supports scroll wheels (in Cocoa).

      For the record, apps were faking contextual menus on the Mac long before they were an OS service.

    6. Re:Right Click by Graff · · Score: 2

      MacOS has had context menus since MacOS 9 (or possibly MacOS 8
      Actually, if I remember correctly, it was around the time of MacOS 7.5. Anyways, it's been a good long time.

      Although MacOS may actually just support the right-click natively now - I don't know.
      Yes, Apple natively supports two button mice with separate left and right click actions. A right click works the same as a control-click (it calls up a contextual menu if available, if not it acts like a left click), plus it still has the control-click. It also supports 3, 4, 5, and more button mice, but those buttons don't have any pre-defined operating system actions associated with them, they need to be defined by the current application or by third-party utilities.
    7. Re:Right Click by djcatnip · · Score: 1

      you can partially thank my brother for contextual menus in system 8.something.

      --
      I make these: http://beatseqr.com
  52. Way to set the strawman by Anonymous Coward · · Score: 0

    There's never been a Windows program that asks that kind of nonsense.

    I find the basic Mac OS (both X and pre-X) fairly intuitive, but applications are horrible, particularly the ones done by small-time developers. There is still not a good NNTP/USENET reader. They're all so bad that you can actually smell them when you start them. The Mac OS 9 is so unstable that WIndows 3.0 laughs at it.

    Please keep in mind that I'm on my powerbook right now writing this, so I'm well aware of the capabilities of the Mac. And let me also say that now that they've added a real OS under the covers, I find the Mac OS really great. I love the idea that I can get to a command shell FINALLY on my Mac.

    I think you can criticize Windows and its well warranted, but the myth of the superior Mac WIMP GUI is just that, a myth.

    1. Re:Way to set the strawman by Anonymous Coward · · Score: 0
      There's never been a Windows program that asks that kind of nonsense.

      Your exposure to programs written for Windows must be very limited, because I've seen hundreds of dialog boxes that are that bad or worse.

  53. Re:They Forgot... + retarted elf. by Anonymous Coward · · Score: 0

    ????
    Are you retarted elf?

    example:
    YOU: "And to turn the machine off, I have to use the power button. Mentally this is like having the on switch turn the PC off! Very bad because I am a whiny bitch who can't really find flaws of substance to point out. So, lets make a seperate button for each task, period, and not lump them together by functionality, since their actions might actually have opposite effects."

    REST OF WORLD:"Shut up!"

    My Take: Do you want a seperate shutdown button visible at all times? What menu would this fall under? Do you really have a legitimate complaint, or did you post this with your troll account?

  54. I wish Apple would follow their own guidelines by Tim+Browse · · Score: 5, Informative

    Well, apart from this document being for developers, and not for the 'layman', I have a couple of issues with it, and they're mainly due to Apple's "Don't do as I do, do as I say" attitude.

    For example: #4 Avoid Custom Controls, and #7 Aqua Is In, Grey Is Out.

    Go try out iTunes, QuickTime, etc to see how much Apple thinks "Grey is out" (the window background is non-standard, and grey). iTunes and Quicktime also have custom title bars, and custom resizing gadgets. All of these things are already implemented perfectly well by the standard GUI, so why doesn't Apple use them? It's like when Bill Gates exhorted developers to use the common dialogs to keep the user experience consistent, while MS Office didn't use them.

    And #5 - Use A Single Menubar is particularly ironic - I doubt very much that anyone porting a Windows app to MacOS would add a menu to their main window (mainly because it's probably quite hard), while Apple should really read and inwardly digest the main points of this article - i.e. when in Rome, do as the Romans do. Anyone remember QuickTime 4? It had a single menu bar on MacOS - and on Windows too! Of course, Windows doesn't have a 'menu bar', so in one of the most impressive displays of pigheadedness and 'not getting it', Apple decided that QuickTime for Windows should create a floating window whose sole purpose was the have a menu on it. Genius - they managed to get all the disadvantages of both systems, and none of the advantages (the menu wasn't attached to the player window).

    And #10 - Reconsider Toolbars still has me puzzled. I never have worked out why Mac users are so insistent that palettes are superior to Toolbars. I always find floating palettes to be a pain in the neck to maintain (as a user) and they're always getting in the way of what I'm trying to do. However, I appreciate that both forms of UI are useful, and wouldn't really be able to honestly state that one is better than the other. Besides, run MS Word, drag a toolbar into the middle of the screen, resize it - looks kinda like a floating palette doesn't it? That said, I can understand why they say not to use toolbars - they're not really a part of the MacOS feel, so they tend to stick out. On the other hand, it is interesting the way half the windows in OSX/Finder use toolbars all over the place. I guess if you make the toolbar icons R-E-A-L-L-Y B-I-G then it's ok for some reason.

    Don't get me wrong - this is a useful document, if a little preachy and arrogant ("well, clearly, our UI is better than the crap you poor Windows developers have had to put up with, you sad losers..."), but I just wish Apple would follow their own edicts a bit more closely.

    However, the best thing to come out of this slashdot article is that I found out that Mr MacKido (the master of reasoned and unbiased argument) doesn't like MacOS X. The thought of him gnashing his teeth about OSX had me chuckling away for ages :)

    Tim

    PS. For the record, and to pre-empt some formulaic replies to this posting, I mostly use Windows, but also use a Mac, and I don't always have good things to say about Windows.

    1. Re:I wish Apple would follow their own guidelines by wadetemp · · Score: 3, Informative

      Go try out iTunes, QuickTime, etc to see how much Apple thinks "Grey is out" (the window background is non-standard, and grey). iTunes and Quicktime also have custom title bars, and custom resizing gadgets.

      The article actually left out the guidelines on the aluminium look. This is actually a look that can be impressed on any Application in 10.2. They're not custom controls, it's just a "skin" for them.

      Apple's guideline to developers is that the aluminum look should be used for applications that attempt to simulate a hardware or "real life" device. iTunes=stereo, QT=TV, etc.

      However, they break even that guideline w/ the new address book app. Go figure. :)

    2. Re:I wish Apple would follow their own guidelines by phillymjs · · Score: 3, Insightful

      I never have worked out why Mac users are so insistent that palettes are superior to Toolbars.

      Because since 1989 when the Mac II was released, we've been able to easily plug a second video card and a cheap (or not so cheap, depending on your budget) second monitor into our Macs and use it exclusively to hold the palettes. Windows multiple-monitor capabilities didn't achieve parity with that of the Mac until Win98, IIRC.

      Personally, I've used dual monitors on every desktop Mac I've owned since 1994, and have no intention of giving them up. Once you get used to that extra screen real estate, working on a single monitor feels very confining.

      ~Philly

    3. Re:I wish Apple would follow their own guidelines by Jordy · · Score: 2

      Wait... you mean address books don't have a physical parallel in real life? Sure it isn't a piece of electronics, but I'm pretty sure leather clad address books do exist.

      --
      The world is neither black nor white nor good nor evil, only many shades of CowboyNeal.
    4. Re:I wish Apple would follow their own guidelines by benad · · Score: 1
      Go try out iTunes, QuickTime, etc to see how much Apple thinks "Grey is out" (the window background is non-standard, and grey). iTunes and Quicktime also have custom title bars, and custom resizing gadgets.

      Funny thing is, the "brushed metal" look is now a standard "theme" that any Cocoa app can use in Mac OS X 10.2 (this is why some .Mac apps are only for 10.2). So, "gray is out", but brushed metal is now officially in...

      Anyone remember QuickTime 4? It had a single menu bar on MacOS - and on Windows too!

      CodeWarrior for Windows does the same thing, but it uses the palette window to "hold" the menu bar, which is still IMHO much better and usable than the original Windows MDI, but still uggly.

      That said, I can understand why they say not to use toolbars - they're not really a part of the MacOS feel, so they tend to stick out.

      That's not what they say. They say that your toolbars, if used, should not be bloated bars with >30 button, half of which you'll never use.

      However, the best thing to come out of this slashdot article is that I found out that Mr MacKido (the master of reasoned and unbiased argument) doesn't like MacOS X. The thought of him gnashing his teeth about OSX had me chuckling away for ages :)

      A lot of the "old" Mac users, while they won't admit it, never wanted to use Windows because they got used to Mac OS before X and they can't adapt themselves to something new.
      I'll say it here, because you won't see it anywhere else: Mac OS X is a step towards simplification. NOT backwards, not worse, simplified. Yet most users got used to the sh*tload of little gadgets that polluted Mac OS 9.

      Yes, Mac OS X is less "usable", but that's because it's new and didn't have 15 years+ of refinements. And by "refinements" I don't mean gadgets sprinkled on top as an excuse for a confusing UI.

      (Sorry for the rant. I hate it when people are nikpicking to hide that they are close-minded, like some "old school" mac fans... Between KDE3 and Blackbox, you can easily guess which window manager I prefer...)

      - Benad

    5. Re:I wish Apple would follow their own guidelines by wadetemp · · Score: 2

      I suppose that's true. Like a good little bot I was just regurgitating what had been fed to me before, but after I posted I got to thinking about it a little bit. Maybe the address book is supposed to be the analog of a paper-based address book, or even a digital address book.

    6. Re:I wish Apple would follow their own guidelines by sg3000 · · Score: 2

      > However, they break even that guideline w/ the
      > new address book app. Go figure. :)

      Uh, yeah, Apple broke their guidelines for the Address Book. All the other iApps that use the brushed metal look have an physical "digital lifestyle" device that goes with it:

      iTunes: MP3 player
      iPhoto: digital camera
      iMovie: digital video
      iDVD: DVD player

      AddressBook: nothing.
      iCal: nothing

      On an entirely unrelated note, what's the point of Inkwell -- the handwriting recognition package? Even if you assume that the digital device for AddressBook and iCal is the iPod (with the 1.2 software), you can't even use handwriting recognition with that! So what's the point?

      Wait... ... maybe they're building a ... nah!

      --
      Insert simplistic political, ideological, or personal proselytization here.
    7. Re:I wish Apple would follow their own guidelines by chippcom · · Score: 1

      Yep, me too. I liked the second video card. So, when I went to PC's it really sucked not having one. Then along came Win98SE which supported them...so for 29 bucks (video card) and a spare monitor, I could have two.

      So, my Dad on his Mac wanted a second monitor too. I figured, find a PCI card (another 30 or so bucks) and he's in business. Except, the absolute cheapest card we could find which would do the trick was over $250!!! Talk about a rip-off. Dad's now using a PC.

      I heard someone here at Slashdot describe OSX as "a great OS with a $2000 hardware dongle."

    8. Re:I wish Apple would follow their own guidelines by JoshWurzel · · Score: 1

      "Remember Quicktime 4" is not a valid argument against this document. You should instead be considering the current version of Quicktime (6) before offering criticisms about how Apple does or does not follow their own GUI guidelines.

      That said, you are absolutely right on the other points.

    9. Re:I wish Apple would follow their own guidelines by wadetemp · · Score: 3, Funny

      AddressBook: nothing.
      iCal: nothing


      Actually, I have repented. Both these apps do have a respective digital lifestyle device: the PDA.

      Wait... ... maybe they're building a ... nah!

      Yeah.... :)

    10. Re:I wish Apple would follow their own guidelines by maxentius · · Score: 1

      I wouldn't go to any great length to defend the brushed-metal look or rationale, but I would suggest that any app that talks to the forthcoming iSync, or otherwise deals with shipping information to or from external user-owned devices (iTunes and iPhoto), fits within Apple's definition of being lifestyle-device related.

      I had no problem syncing the new Address Book from my Palm, then syncing it with my iPod. If I could put my cell phone into the mix, so much the better.

      I'm hoping that when iSync arrives, it will seem as invisible as Rendezvous does already, resolving sync questions in the background depending on which automatically recognized devices are connected.

      The real question is, where is the "i" in Address Book?

      --
      Imagine a Beowulf cluster of neurons.
    11. Re:I wish Apple would follow their own guidelines by Anonymous Coward · · Score: 0

      sucks to be poor

    12. Re:I wish Apple would follow their own guidelines by Tim+Browse · · Score: 2
      You should instead be considering the current version of Quicktime (6) before offering criticisms about how Apple does or does not follow their own GUI guidelines.

      Well, I was referring to Apple's general tendency to ignore platform conventions while exhorting developers to follow MacOS conventions to the letter...

      ...but fair enough, let's do what you suggest.

      Here's a summary of Quicktime 6 running on Windows XP:

      • Custom window background/title bar.
      • Custom resize gadget
      • Custom minimise/maximise/close icons
      • Custom push buttons (that look like little else on Windows)
      • Custom slider control
      • Custom scroll bar control, that neither looks like Windows 2000/9X style, or like the new XP-style.
      • Custom tab control (with, for some reason, a background image of Aqua-style horizontal stripes - the last time Windows had white backgrounds was Windows 3.0, or about 10 years ago, iirc)
      • Custom menu bar rendering
      • Menus are the wrong colour (dark grey)
      • Use of MacOS style custom 'triangle' widget in the movie info window.

      Compare this with:

      • "If you must use custom controls, be sure to use them for unique interface elements; for example, avoid replacing a standard checkbox, for example, with a custom one."

      Or, you might say, a scroll bar. Or a tab control. Or a slider. Or a close button. Or a push button. etc.

      See what I mean?

      Tim

      Before anyone pipes up with "What about Windows Media Player?", I consider that an abomination too :-)

    13. Re:I wish Apple would follow their own guidelines by Anonymous Coward · · Score: 0

      What-dows X-what?

    14. Re:I wish Apple would follow their own guidelines by zapfie · · Score: 2

      From the Aqua HI guidelines:

      Mac OS X version 10.2 provides developers with a new "textured" window appearance (see Figure 5-4). This window style has been designed specifically for use by--and is therefore best suited to--applications that provide an interface for a digital peripheral, such as a camera, or an interface for managing data shared with digital peripherals, such as the Address Book application.

      This appearance may also be appropriate for applications that strive to re-create a familiar physical device--the Calculator application, for example.


      So for the address book, you could either argue a PDA, or the physical counterparts of a real address book and wall calendar.

      --
      slashdot!=valid HTML
    15. Re:I wish Apple would follow their own guidelines by zapfie · · Score: 2

      I doubt very much that anyone porting a Windows app to MacOS would add a menu to their main window (mainly because it's probably quite hard),

      They have. Some companies don't feel like re-doing their interface twice, so they have kind of a weird hybrid interface that will work on both platforms, but isn't really standard to either. I have used more than one app that used a menubar in a main window. It wasn't fun.

      Also, remember that Apple isn't a single entity. There are software engineers, UI designers, UI creators, etc. The people who wrote the document are probably not the people who sat down and designed the iTunes/iWhatever interfaces. It seems hypocritical of them to preach one thing and do another until you realize that. Then it's just bad UI design. :)

      --
      slashdot!=valid HTML
    16. Re:I wish Apple would follow their own guidelines by DCMonkey · · Score: 1

      How does having a global menubar work out on multiple monitors? It seems like it would be a pain. Is it?

      --
      DCMonkey
    17. Re:I wish Apple would follow their own guidelines by phillymjs · · Score: 2

      Nope, it doesn't bother me in the least, because my work is done on the monitor where the menubar lives (17", 1024x768). My cursor only ventures onto the palette monitor (14", 640x480) when I need to select a different tool/function.

      I also usually learn the keyboard shortcuts for the menu selections I use most often.

      ~Philly

    18. Re:I wish Apple would follow their own guidelines by Anonymous Coward · · Score: 0
      Before anyone pipes up with "What about Windows Media Player?", I consider that an abomination too

      But at least it doesn't draw its own menubars...

    19. Re:I wish Apple would follow their own guidelines by rjung2k · · Score: 1

      It lets you store email addresses and AIM buddy names, which are "i"nternet-based.

    20. Re:I wish Apple would follow their own guidelines by rjung2k · · Score: 1

      We're talking about GUIs on Macs, not Windows XP.

    21. Re:I wish Apple would follow their own guidelines by Tim+Browse · · Score: 2
      Well, actually, to quote myself:

      I was referring to Apple's general tendency to ignore platform conventions while exhorting developers to follow MacOS conventions to the letter...

      Tim

  55. Site is fine on every Wintel box I've seen by Anonymous Coward · · Score: 0

    Every last one

  56. Girl power! by VIIseven7 · · Score: 4, Funny

    From the captions:

    In Microsoft Windows ... the user is restricted in her ability to position document windows on the desktop.
    In Mac OS X
    ... the user is free to move her document windows around the desktop.

    MS is just a bunch of chauvinist pigs. Buy Apple, support Women's Lib!

    1. Re:Girl power! by Anonymous Coward · · Score: 0, Offtopic

      Nothing bothers me more than the corruption of the english language at the hands of political correctness.

      English doesn't really have a way to make a gender-neutral reference to an unspecified person. In the absence of this, the established format is to use the male pronoun. It's not a political issue, it's the way in which the language has evolved. That's the key: it has evolved; it wasn't consciously shaped by political interests.

      It's not proper to use "she" in this context. Chairperson, spokesperson, and the like are not correct either. They are awkward and unnatural words that have been created by politics, and have no place in the speech of properly educated people.

      Even worse is when people use "s/he" or some other such construct.

      [I don't feel like burning karma because people disagree with me, so I'm posting anonymously.]

    2. Re:Girl power! by VValdo · · Score: 2

      It's not proper to use "she" in this context. Chairperson, spokesperson, and the like are not correct either. They are awkward and unnatural words that have been created by politics, and have no place in the speech of properly educated people.

      These words have been adopted by business, and as "properly educated" women continue to advance economically, I am confident you'll be seeing such words more in the future ;)

      W

      --
      -------------------
      This is my SIG. There are many like it, but this one is mine.
    3. Re:Girl power! by Lovejoy · · Score: 1

      Well, you're wrong. And I don't give a damn about karma, so mod me down. I don't care.

      Alternating pronouns is correct. Using plurals consistently is also correct. ("Users should be able to move their icons around.") Consult any style guide.

      As one of my college profs said "Including half of the population is not "politically correct." Yes, Yes, I have a degree in English. Yes, I'm a conservative Republican, so I don't suffer PC crap well. This is just common sense.

      (Note: "They" and "their" should NEVER be used as singular neuter pronouns. "Someone left their shoes on the bleachers." ACK!)

      --Now setting prefs to filter out ACs--

    4. Re:Girl power! by Anonymous Coward · · Score: 0

      --Now setting prefs to filter out ACs--

      Yeah, god forbid someone might have something accurate, informative, and unpopular to say.

    5. Re:Girl power! by Anonymous Coward · · Score: 0

      Improper use of the plural in the case you described is not as bad, perhaps because it's done so often that we fail to notice much of the time.

      It's this lack of specificity in the grammatical rules of the language that causes so many people to do it.

      I remembered that I have one of those style manuals around, from god-knows-what english course. It's relatively recent; it has a section on avoiding sexist language, and their suggestion is to use "Someone left his or her shoes on the bleachers." I suppose that it's gramtically correct, but it's inefficient. People tend to sound awkward when saying it. It would be much better if we could just standardize on "he," as people did before they gave this issue any thought from a political perspective.

      This same style manual also suggests that using "spokesperson" is valid. Perhaps I'm not qualified to refute what's printed in this thing, as it does intend to be a definitive guide to english grammar, but I can say with reasonable certainty that 30 years ago, uttering "spokesperson" would have resulted in some very strange looks.

      Of course language is dynamic; any child going through the school system today will feel completely natural saying spokesperson. Regardless, every time I hear it I'll think of it as politics shaping language, and that's just as sleazy as teaching an entire generation to greet each other as comrades.

    6. Re:Girl power! by wilson_c · · Score: 1

      "They" and "their" as singular pronouns have been in popular use for over 200 years. Given that language is a set of arbitrary rules which shifts along with culture and usage, why do you have a problem with this?

      As long as intention can be clearly conveyed and interpreted, there is no right or wrong in language, especially English.

    7. Re:Girl power! by foo12 · · Score: 1

      And since did English become a dead, static language? Oh that's right: It hasn't. Language is mutable, constantly adding words and outright changing form every few generations.

  57. Re:Right Click (right click works) by mrnick · · Score: 2, Informative

    I have MAC OS 10.2 and instead of using Apple's useless 1 bouton mouse thingy I opted for a Logitech cordless optical 3 button wheelmouse.

    Guess what? It all works, the buttons, the wheelmouse, etc.. The right mouse button works just like a PC user would expect.. context menus.

    People should look into an issue before just spewing crack out of their mouths.

    Nick Powers

    --

    Encryption: I may not agree with what you say, but I will defend your right to encrypt it...
  58. keybinding suckiness by Anonymous Coward · · Score: 0

    The backspace, insert, and delete keys are usually wrong in Linux. Windows always gets it right.

    With one exception, Mozilla 1.1. Click on the URL for focus, and hit the backspace. It doesn't erase letters going leftward, noooooooooooooo, it cycles through the listed URLs. What genius did that?

    And Mozilla doesn't logically group functions. The cookie, image, Java, an Javascript settings are in a single dialog in NS4x. Mozilla has 4 different boxes in three different submenus.

  59. Great Marketing by Anonymous Coward · · Score: 0

    I like Macs, but....
    nothing says your product sucks like an advertising campaign that only points out the bad points of your competitor's product.

    Tell me what you have to offer and I'll make a decision. If you just tell me how bad Windows is, I'll assume you have nothing to offer except a grudge.

    -Mx

  60. Good read, and some more Switch ads! by Winterblink · · Score: 1
    This interface guideline stuff was a great read, even as someone who's a Windows developer (please, no stone throwing :D ).

    Anyway, it seems that Apple's got a swath of new Switch ads available and they've conveniently left the old Ellen Feiss one there (probably because it's so damn popular. Enjoy. :)

    --
    "I'm a leaf on the wind. Watch how I soar."
    -Hoban Washburn
    1. Re:Good read, and some more Switch ads! by Anonymous Coward · · Score: 0

      Yeah man, Janie rocks. *and* she saved Christmas. Take that, Ellen!

    2. Re:Good read, and some more Switch ads! by Winterblink · · Score: 1
      Yeah man, Janie rocks. *and* she saved Christmas. Take that, Ellen!

      I'll take Janie over Ellen anyday. At least she seems like she's got half a brain. :)

      --
      "I'm a leaf on the wind. Watch how I soar."
      -Hoban Washburn
  61. agree.html by Golias · · Score: 4, Interesting
    I was one of those people who was really dreading OS X's use of file extensions. I liked the old MacOS way of handling file types so much better.

    However, OS X manages extensions with so much more inteligence than Windows (or any *nix windowing system I've used), that I've complety changed my tune now. I now like the way OS X uses file extensions, and don't want to go back.

    --

    Information wants to be anthropomorphized.

    1. Re:agree.html by Anonymous Coward · · Score: 0

      *nix doesn't care about file extensions, it's all part of the filename, which is the right way in my opinion.

  62. Notice how this was a "Switch" article by Anonymous Coward · · Score: 0

    And its a damn good Switch article

    As for the interface comparison, that power settings panel looks and works EXACTLY the same on Win XP as it does in 98, ME, 2K, etc. XP just made everything gaudy, in addition to its ineffectiveness.

    I've been using Mac OS since V .97 (thats right, prior to version 1.0), and I've NEVER had a complaint. About any aspect of the Mac OS.

    1. Re:Notice how this was a "Switch" article by iPaqMan · · Score: 1

      OMG your so full of #$%#. Never any complaints come on.

      I USED to own a Mac (OS 7.39l2.394.3 - 9.374.37 - Note sarcasm) and I could never understand why a supposedly great OS could not dial a modem without letting you do something else. I guess the time wasted waiting for the modem to dial out was intentionally put in so you could sit back and appreciate Steve, Waz and that pretty fruit colored case.

      I guess I am bitter because I bought a $4000 lemon.

      BTW, Did Steve Jobs himself program you???

    2. Re:Notice how this was a "Switch" article by cscx · · Score: 2

      As for the interface comparison, that power settings panel looks and works EXACTLY the same on Win XP as it does in 98, ME, 2K, etc. XP just made everything gaudy, in addition to its ineffectiveness.

      Strangely enough, the Mac dialog box seems to be verbatim from the Windows 2000 one! Except for the fact that Apple Photoshopped out the system standby and system hibernates combo boxes.

    3. Re:Notice how this was a "Switch" article by MoneyT · · Score: 2

      these aren't exact screen shots. They are examples used to convey a point. In the same way a survey is not an exact representation of the US opinion, it's used to get a point across.

      --
      T Money
      World Domination with a plastic spoon since 1984
    4. Re:Notice how this was a "Switch" article by MoneyT · · Score: 2

      I was always able to do other stuff while my modem dialed (though I often just used the time to catch a snack). Did you ever try clicking into another application? Or did you just look at the watch cursor and go "Aw damn"

      --
      T Money
      World Domination with a plastic spoon since 1984
    5. Re:Notice how this was a "Switch" article by cscx · · Score: 2

      So what you're saying is that Microsoft can take a screen shot of the Mac Desktop, Photoshop out the hard drive/mounted disks and the trash icons, along with the toolbar and control strip and then claim "How difficult the Mac is to use!"

      I think it's all a bunch of malarkey.

    6. Re:Notice how this was a "Switch" article by MoneyT · · Score: 2

      The difference of course being, the screen shot apple used was to demonstrate the errors present in many dialouges into one picture, where as your example is just blatent lying.

      --
      T Money
      World Domination with a plastic spoon since 1984
  63. Re:You guys really eat Apples PR up. Mindless shee by Jeremy+Erwin · · Score: 2

    If you are talking about the Launcher, that was a shareware App that Apple liked and offered as an optional tool in System 7, as a way to let your young kid run apps on your Mac without being able to delete your system files. Since many schools who used Macs used the Launcher to lock down their desktops and prevent studens from hacking their boxen, a lot of teens in the 90's assumed that the Launcher is what MacOS was, and wrote long screeds on message boards about how "restrictive" the OS is.


    The restrictive interface was "At Ease." (I remember using the built in file deletion features of Microsoft Word to delete the "At Ease" preference file , thus exorcising the broken interface from the computer. Ah memories...) Launcher was an attempt to bring the "single click to launch" feature of "At Ease" to users of the Finder. It was kind of clumsy compared to third party application launchers.

    (Why an application launcher? The standard mac technique of storing apps within folders made some sense organizationally, but searching through folders to launch a program is a bit of pain. So after "System 7" most mac users had an aliases folder containing references to frequently used applications. The various application launcher organized such "aliases folders".)

    By the way, Apple doesn't produce shareware. Some Apple things are "free as in beer", though. I think "At Ease" was actually sold as a commercial product.

  64. Uniform user interfaces by teetam · · Score: 2
    The uniform UI assumption has been around for some time - I remember Bill Gate$ talking about it about 6 years ago.

    The emergence of the Web proved them both wrong. Each website (atleast initially) had its own color schema and navigation mechanism. Users never complained. I rather like the fact that each application has its own look-and-feel identity rather than a communist approach to how an app should look.

    Even on the desktop, the popularity of skins is proof of that (to some extent).

    The bottom line is that the application should be intuitively easy to use - having a uniform look and feel does not necessarily guarantee that.

    --
    All your favorite sites in one place!
    1. Re:Uniform user interfaces by Tim+Browse · · Score: 3, Interesting
      The emergence of the Web proved them both wrong. Each website (atleast initially) had its own color schema and navigation mechanism. Users never complained.

      No, they don't complain. They just don't use websites that are too different and/or confusing.

      Tim

    2. Re:Uniform user interfaces by Anonymous Coward · · Score: 1, Interesting

      I force white on black text when browsing, and allow no background images. That usually removes the ugliness from most websites.

      You know what would be sweet though? A Mozilla text filter (optional) that properly capitalizes all-caps or mixed-caps text.

    3. Re:Uniform user interfaces by MoneyT · · Score: 2

      Note however that most webpages have begun to conform.

      1 [optional]) Cover Page, consisting of a clickable graphic or flash animation

      2) Main page, with general new announcements and news in the center.

      3) Across the top of the mainpage lies a basic tool bar for providing options

      4) Along the left side of the page is navigation capabilites

      5) Ads and misc objects on the right.

      --
      T Money
      World Domination with a plastic spoon since 1984
    4. Re:Uniform user interfaces by Anonymous Coward · · Score: 0

      This brings up an interesting point - are the "standard" UI elements really intuitive, or do they just seem that way because people have been trained to deal with them through repeated exposure.

  65. Re:You guys really eat Apples PR up. Mindless shee by Tim+Browse · · Score: 2

    It's not fodder for the Switch campaign - it really isn't. It's to let developers know the headline issues they should be aware of when porting their Windows apps to MacOS.

    As for choosing Windows - well, it's the one I would choose if I were Apple - a document telling Gnome developers how to port their apps to MacOS would have a much smaller target audience.

    However, the fact that the document can't just give you the facts, and has to exude the usual insufferable smugness and arrogance that you usually get from Apple PR doesn't really help, I agree. Most developers know when you're trying to bloke smoke up their proverbials.

    Tim

  66. Darwin or Lamarck might help. by bstadil · · Score: 2
    I think we are doing the GUI development wrongly. MS, Apple. KDE etc all have a tops-down approach with varying degree of provision for tailoring to individual needs.

    The basic GUI is fixed and any innovations originates from the respective companies or developers based on their understanding / thinking about users behavior and preferences.

    Why not try and turn this on its head and use a Darwinian development model. Start with a very simple IU and Meta Configuration files that has to ability to be combined with other Meta Configuration files and thereby create a "derived" or "evolved" IF. Then use the net to exchange the Interface DNA if you like. The "Survival of the fittest" will be measured in "usage time" for the specific phenotype of that GUI.

    There should be a lifespan of any Interface after which time it will die and the user needs to procure a new. The new could be a derivative from the original.

    This might or might not work but I think its worthwhile to try and see if it has merits. We would probably see clusters evolving based on typical usage. The clusters would not be normal tops down thinking like Office / Game station / Development but rather reflect the real world mixed usage.

    Radical new ideas could be introduced as "mutations" and their survivability could be ascertained effectively. Second the radical new ideas need not be perfect initially and they could evolve via usage tweaking. (Kind of a LaMarckian approach in a predominantly Darwinian world).

    I am a bit further along on this and if anyone has an interest drop me a line. (lamarck@s-tadil.com remove -)

    --
    Help fight continental drift.
  67. Other options by Anonymous Coward · · Score: 0

    [Apple]-e for eject
    [Apple]-y for "put away" (same thing)

  68. Re:You guys really eat Apples PR up. Mindless shee by Golias · · Score: 2, Interesting
    This article is just put out as fodder for their "Switch" campaign! Am I the only one who sees this???

    No, you are not the only one who sees that. You would also not be the only one to see the Virgin Mary in that oak tree that was in the news this week. In other words, I think you are seeing what you want to see.

    This article was written for the benifit of developers who are porting Mac apps. It happens to also be of interest to geeks like the crowd here on /. who like reading about GUI design. If their intention was to "bash Windows" to sell people on switching to OS X, there are far more damning things they could have brought up.

    If anything, the article might scare some developers away from doing Mac ports, because they are basically saying "jump through these hoops or Mac users will ignore your app and all the effort you spend on proting will be wasted."

    --

    Information wants to be anthropomorphized.

  69. The Aqua colors are changeable by Anonymous Coward · · Score: 0

    Editable in any and every way. Try the Preferences app.

    1. Re:The Aqua colors are changeable by justsomebody · · Score: 2

      So can I select green and everything is green. Wouldn't bother to edit preferences file

      --
      Signature Pro version 1.13.2-3 release 83.5 beta3try7 after-breakfast edition
  70. Re:You guys really eat Apples PR up. Mindless shee by robertchin · · Score: 2

    The Apple HIG strictly state that a Mac OS X application should never sit behind the dock. If you look at all of Apple's apps, they will automatically resize their windows if you change the vertical size of the dock. Applications that maximize to behind the dock are in violation of Apple's HIG, another reason that a lot of ports of windows applications are considered crappy.

  71. Slashdot: Uninteresting and Uncivil by reallocate · · Score: 2

    Well, I disagree with the Mac comments, but I won't disagree with you about the general decline of interesting pieces here. Add in an increasing uncivility by many posters and you've got an uninteresting and unpleasant place to visit.

    --
    -- Slashdot: When Public Access TV Says "No"
  72. Re:Right Click (right click works) by Juggle · · Score: 0, Flamebait

    So even after paying a premium price for supposedly perfect top of the line hardware....you still have to shell out extra cash for an unencumbered mouse.

    I thought the point of Apple controling the mac hardware was to make sure that you DON'T have to go to third party options.

    If I was paying that much for a system I'd be pissed as heck that the first thing I had to do was throw out the main user interface and buy a new one!

    --
    --- Juggle juggle@hitesman.com
  73. unix & file extensions by Anonymous Coward · · Score: 0

    IMAO, if a unix GUI tries to "handle" file extensions, it's already doing the Wrong Thing(tm). unix GUIs should do the same thing as unix itself - namely, there are no file extensions, it's just that some filenames happen to end with dot-three-letters. naming their files that way is the users' privilege, and unix should do nothing either for or against it.

    as for sorting by file type, the way some GUIs seem to want to do - that's a slow, high-overhead operation involving examining each file to find out just what type it is. you can*not* trust the file's name to indicate this, because the user may have other policies for naming their files, and in any case the reason for the sort-by-type may be that the user wants to _find out_ what type the damn file is, for all the GUI knows.

    1. Re:unix & file extensions by Golias · · Score: 1
      When using most unices, I tend to agree with you, especially when at the command line (which is where I spend most of my time on a Linux box anyway). Unix is all about handling files with a million small apps, rather than running apps for handling files, so having a file that insists on being used by sed when you want to awk would ruin everything.

      However, Macs have traditionally done an outstanding job of dealing with file types. You *can* trust the file type to be correct. It's never been the nightmare experience that the concept presents in Windows. Those who have been long-time Mac users would scream bloody murder if they suddenly could not double-click on a file and have the correct application open it without any further hassle.

      --

      Information wants to be anthropomorphized.

  74. Isn't it rather amusing... by gfhilton · · Score: 0, Troll

    that on a page about interface design that the text in the contents bar of the web page is overflowing out of the bar? This seems like a rather poor interface design standard to me...

    --
    "Do what you wish in your madness, but first let me down off this horse. I wish to see no eyes!"
    1. Re:Isn't it rather amusing... by srelan · · Score: 1

      It looks fine to me on 4 different browsers and Win, Mac, Linux machines I just tested it on...

  75. fa! by Anonymous Coward · · Score: 0

    The MDI is kind of annoying sometimes, but having drop-down menus on every window is far more convenient than the single one on top that Apple uses ...which is always the one for another running application that you're not interested in. Perhaps using Windows has accustomed me to the windows way of doing things, but then again perhaps its a matter of taste and not an exact science as the Apple wierdos maintain. Nice aqua-esque facade change for slashdot. I pity the poor little kiddies who have to read Slashdot over a 28kbps connection, though.

  76. Re:Actually, even MSes own programs have this prob by Anonymous Coward · · Score: 0

    Years ago when I was a newbie, I was in a class that taught the details of MS-Office. The instructor explained to me that there are three different ways of abreviating the word "average", depending on which MS-Office app you are using. Even though it is sold as an integrated suite, the abreviation that works for one app does not work in the others. At that moment, I learned all I really need to know about the consistency of Microsoft's software design. I've been a Mac bigot ever since.

  77. Re:Right Click (right click works) by Etcetera · · Score: 3

    ...you still have to shell out extra cash for an unencumbered mouse.

    The included mouse is perfectly un-encumbered. Unlike on Windows, on the Mac the contextual menu is not required for ANYTHING. By design, there's *nothing* you can do with a contextual menu that you can't do in some other fashion. It's there for those that would like an additional means of accessing functionality.

    Furthermore, the "official means" of accessing contextual menus is "modifier-click", specifically Control-click, not "click in some other way." Most people who decide to purchase multi-button mice map their second buttons to a Control-click, but it's not required.

    Once you get used to it, Keyboard+Mouse control is actually a little faster than Multibutton-Mouse control.

  78. Ninth Point by unsinged+int · · Score: 1, Offtopic
    Numbered lists on web pages should be written using the
      ordered list tag.
  79. Single Philosophy leads to clean Design by ChaoticCoyote · · Score: 4, Insightful

    Because Apple provides focus and direction for developers, Mac applications (generally) behave in expected and "natural" ways. Consistency and simplcity make users happy. Windows sufferes from verbosity, backward compatability, and mixed metaphors. What works in one Windows application may not work in another -- even if the two applications were developed as parts of a single package, like Microsoft Office. There are too many ways to do things: different menu commands, keystrokes, and GUI components lead to confusion. Linux GUIs are, sad to say, even worse than Windows. No one imposed a look-and-ffel guideline on Linux, so apps run an behave differently depending on the whims of individual developers and teams. Even worse, Linux GUIs tend to focus on cloning Windows, instead of boldly trying to be better. What we get are incredibly inconsistent applications that have no consistency or common thread of operation. Put The Gimp, Abiword, and Evolution on the desktop simultaneously, and you can see very divergent philosophies in operation. This isn't a knock against the developers of these fine application -- it is a recognition that the chaotic Linux community lacks the cohesion that Apple can bring to Aqua. Give users a clean, clear, easy operating system, and they'll drop Windows like a rock. So why hasn't Apple conquered the world? Because their product is too damned expensive. Windows could be "defeated" if the Linux community were to produce a high-quality, consistent GUI with a quality set of application -- for free. The question is, are we too individualistic to work together as a community?

    1. Re:Single Philosophy leads to clean Design by MyHair · · Score: 1

      . . .if the Linux community were. . . .
      The question is, are we too individualistic to work together as a community?


      Duh, yeah. That's pretty much what Linux is. What is the "Linux community", anyway? Some want it do dominate the commercial OS market, some have political views, and everyone has their own idea of the ideal UI. KDE, Gnome, Qt, GNUstep. Which one is best? Try to get a consensus answer from the Linux community on that. (You might get a consensus on bash, but then again there are probably csh and ksh lovers around, too; or are they all on SunOS?)

      The Linux community isn't about consensus, but flexibilty, freedom and maybe some elitism. (Okay, Windows, MacOS, *BSD, SunOS, BeOS, Plan 9, OS/2, OpenVMS and AtheOS can be about elitism, too.)

      You make many good points, but "The Linux Community" isn't going to all agree on The Right Way to do things. It will take a distribution to push a consistent look and feel, and then that distribution will get criticized for it by many.

      For me, Linux has been the best learning tool for protocols and hardware that I've ever had. Way better than school and books in most cases. But there are too many problems for me to use it as my main client OS. I held a grudge against Apple Macs for years because they killed Apple II (way back; but it was the right business move), but I've been dabbling with MacOS emulators and reading up on OS X, and I'd really like to use OS X, but I have 5 x86'es and don't plan on spending the dough for an OS X capable Apple Mac real soon.

    2. Re:Single Philosophy leads to clean Design by Anonymous Coward · · Score: 0

      I am amazed and amused by the fact that all the Windows-bashing, die-hard, 'Linux is superior', users can't post a reasonable rebuttal to your views and comments. I applaud you.
      Until the consistency you speak of is attained, Linux will continue to wallow in obscurity from the general public.

    3. Re:Single Philosophy leads to clean Design by Anonymous Coward · · Score: 0

      Now close your eyes.

    4. Re:Single Philosophy leads to clean Design by GlassHeart · · Score: 1
      So why hasn't Apple conquered the world?

      Perhaps because they are no longer trying to conquer the world. There is a comfortable niche in developing a better (subjective opinion of their users) product for a premium price.

      Lots of people pay $40,000 for a car that duplicates the functions of a $10,000 one "But the two cars are not the same," you might protest. Exactly.

  80. Ugh -- corrected post. by ChaoticCoyote · · Score: 2
    There were supposed to be paragraphs in that message! Argghhhh...

    Because Apple provides focus and direction for developers, Mac applications (generally) behave in expected and "natural" ways. Consistency and simplcity make users happy.

    Windows suffers from verbosity, backward compatability, and mixed metaphors. What works in one Windows application may not work in another -- even if the two applications were developed as parts of a single package, like Microsoft Office. There are too many ways to do things: different menu commands, keystrokes, and GUI components lead to confusion.

    Linux GUIs are, sad to say, even worse than Windows. No one imposed a look-and-ffel guideline on Linux, so apps run an behave differently depending on the whims of individual developers and teams. Even worse, Linux GUIs tend to focus on cloning Windows, instead of boldly trying to be better. What we get are incredibly inconsistent applications that have no consistency or common thread of operation.

    Put The Gimp, Abiword, and Evolution on the desktop simultaneously, and you can see very divergent philosophies in operation. This isn't a knock against the developers of these fine application -- it is a recognition that the chaotic Linux community lacks the cohesion that Apple can bring to Aqua.

    Give users a clean, clear, easy operating system, and they'll drop Windows like a rock. So why hasn't Apple conquered the world? Because their product is too damned expensive. Windows could be "defeated" if the Linux community were to produce a high-quality, consistent GUI with a quality set of application -- for free. The question is, are we too individualistic to work together as a community?

  81. Oh Please! by Anonymous Coward · · Score: 0

    As a former exclusive user of Apple products, things like this annoy me to no end.

    Apple berates M$ for using nonstandard scroll bars. But it's OK for them to do the same.

    What Apple is doing is akin to a man with a 3 " penis trying to convince women that big fat penises are no good because of the pain that they can cause. Even though 90% of women may prefer big penises, or 90% of the world may prefer something about the Wintel platform Apple is attempting to tell them that they really don't.

    Apple, your future looks dim for a reason. (most) People don't want to buy what you're selling.

    MacOS may have many technical advantages over Windows, just as the devices that run WinCE have advatages over the machines that run Palm OS. But both of the loses trail for other reasons. #1 Price. I can buy a refurbed Visor Deluxe for under $100. I can get a decent PC for less than the cost of an eMac. #2 Availability of software. I can get so much more software for a Palm OS or Windows machine so, in the great platform Jyhad. I choose the side based upon my computing needs. Not on my need to feel or think "different"ly.

  82. Alignment of Controls in a Dialog Box by Lord_Scrumptious · · Score: 2, Informative

    Under the section 'Use Clean Layout', the Mac OS X guidelines state:

    The Aqua interface of Mac OS X relies on a center-biased, spacious layout of controls and other interface elements. By contrast, Microsoft Windows has a left-biased, more crowded layout.

    In a book called "The Non-Designer's Design Book", author Robin Williams explains some of the principles of visual layout from the field of graphic design. On the topic of alignment, Williams states that items aligned on a page create a strong cohesive unit. An "invisible line" gives order and organization to the elements on the page. She goes on to add that a centred alignment is the most common alignment that beginners use, and often creates a sedate, ordinary, and frankly quite dull appearance.

    The book contains many before-and-after designs where the alignment of elements is modified. Most of the improvements arise from moving elements with a centred alignment to a flush-left or flush-right alignment. Williams doesn't say you should avoid a centred alignment altogether, but does add "...please try very hard to break away from a centered alignment unless you are consciously tring to create a more formal, sedate (often dull?) presentation."

    In fairness to Apple, some of the examples they show in their guidelines demonstrate that their recommendation for a center alignment works by making elements next to each other (such as labels and their controls) flush with the "invisible line" that separates them (as in the sample application preferences dialog). Perhaps the best way of looking at Apple's recommendation is to appreciate that non-centred alignments are not an inferior alternative to centred layouts, and may in fact offer an improvement in dialog design.

    1. Re:Alignment of Controls in a Dialog Box by Maserati · · Score: 1

      Interface Builder has a very strong alignment toolset. While dragging widgets around you see a lot of alignment marks: with other elements, the standard distances from edges, everything the guidelines suggest is in there.

      --
      Veteran, Bermuda Triangle Expeditionary Force, 1992-1951
  83. Gray is Out? by Anonymous Coward · · Score: 0

    If gray is out, how come Apple replaced the happy mac at statup with a monochrome Apple logo?

  84. App vs. platform by alext · · Score: 2

    Presumably because Mozilla, Java and StarOffice are seen as fully-fledged platforms on which all kinds of apps could be developed.

    Hopefully Dotnet will make it clear that only one of these really qualifies, and that doesn't mandate any particular l&f.

  85. WHAT IS WRONG WITH YOU PEOPLE!!! by srelan · · Score: 1, Flamebait

    A simple reference to an Apple developer interface guideline article and it brings out such immature condescension from people who aren't interested in the article to begin with!!! Sure you can find some nit-picking in the article but the venomous anti-Mac rants are completely unwarranted for the actual topic at hand. Some of us are platform agnostic and try to learn best practices wherever we can.
    Are you Windows-only developers really so childish and spitefully smug as to waste your own time trolling uneccessarily? Slashdot is getting very old.... Time to find a site with grown-ups.

    1. Re:WHAT IS WRONG WITH YOU PEOPLE!!! by Anonymous Coward · · Score: 0
      A simple reference to an Apple developer interface guideline article and it brings out such immature condescension from people who aren't interested in the article to begin with!!!

      Did you read the article? The article itself was written in a condescending tone. The whole thing was a Windows slam fest. It even included fake versions of real Windows dialogs that were intentionally doctored so as to illustrate bad design. Of course, the author then went on to point out how bad Windows dialogs are, when the real version of the dialog was just fine. When we're talking about an article that is full of self-righteous arrogance, scorn for Windows, and even deception, how do you expect us to react?

    2. Re:WHAT IS WRONG WITH YOU PEOPLE!!! by Anonymous Coward · · Score: 0

      Yeah whatever man.

      Windows has a standards problem when it comes to GUI HIG.(well actually, they have many problems w/any type of standard theythemselves don't own, but that is a different rant)

      I'm no Mac fanboy, but Slashdot is really getting to be a boring and predictable place to exchange ideas....

      You would think that OSX being BSD and many other STANDARDS would get some credit w/all these supposedly open source geeks. But what you really get 90% time is a bunch of PC-centric, admin types who see the word Apple and launch into a bullshit tirade about things they know nothing about.

      Stick to running windows LANS and let people who know something about programming and UI design discuss these things.

    3. Re:WHAT IS WRONG WITH YOU PEOPLE!!! by srelan · · Score: 1

      You do have a valid point to an extent. What forced me to write my initial post was after reading most of the thread and seeing 40-50% of the articles with the same old anti-Mac childish rhetoric (e.g. "Macs are only for interior decorators", etc) What kind of b.s. comments or those? I've been a Win person as long as anybody, and after a couple years of frustration with enterprise desktop issues in Linux, I've been quite pleased at the direction Apple has moved. I would have assumed that a large contingency of this site would have agreed that a major vendor has moved to *nix. But I guess I'm wrong. I think the fact that Apple has agressively promoted interface style guides has been a plus for the platform and also highlights a long-term issue with Windows programs. (And yes I do realize that Apple doesn't always practice what they preach (iApps), but they are MUCH better about interface consistancy policing with developers than Microsoft is...

  86. Re:Doesn't acknowlege Windows' keyboard superiorit by LoudMusic · · Score: 2

    I've been a Macintosh Administrator for roughly four years now, and this has been my BIGGEST gripe the entire time. But I've come to understand their reasoning. If you watch an everyday Mac user, they never take their hand off the mouse anyway - not even to type, because they so rarely type anyway. There isn't really a need for keyboard shortcuts.

    However, there probably are more keyboard shortcuts than you're aware of. You can navigate Finder by typing the file name in the view you are currently in and it will jump to it. Command+O will open it (why they didn't use ENTER is beyond me), and Command+W closes it. For popup and dialog windows in most Apple applications and many other major producers you can Command+[first letter of the button you want to *click*] and it will activate that button. Though you don't have nav arrows and an enter key like you do in Windows.

    I think there are more keyboard shortcuts with the Mac OSes than people give Apple credit for (due to lack of use/knowledge of the OS), but it's still true that Windows can be completely controlled via the keyboard. I've done everything from the first part of the install to daily use without even a mouse plugged into the computer. Some people would say this was crazy talk and why would anyone want to, but as I'm flying through popup windows and navigating my OS while you're moving your mouse around to click a silly button, you'll understand.

    ~LoudMusic

    --
    No sig for you. YOU GET NO SIG!
  87. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  88. Re:Doesn't acknowlege Windows' keyboard superiorit by gnugnugnu · · Score: 1

    I find that most Yes No type dialogs make me want to say No!
    If these programs had more sensible defaults they would not need to ask me so many stupid questions.

    Thankfully Esc can be consistantly be used to dismiss the current dialog whether the label say No Cancel Done or Whatever, so despite the need to reach a little further on the keyboard i usually use escape (and since it is in the extreme top left i can easily hit it without needing to look).

    I think tools like Glade are invaluable as they not only encourage people to develop lots of Applications they allow people to easily do the right thing and reuse code as well as follow standards.

  89. Re:Doesn't acknowlege Windows' keyboard superiorit by Darren+Winsper · · Score: 2

    Er...have you actually ever used KDE? KDE apps are as controllable from the keyboard as Windows apps. GNOME might be a different story, but I can't say for certain.

  90. Re:You guys really eat Apples PR up. Mindless shee by milovoo · · Score: 1


    OMG, you're right, the only way to really
    free my mind is to use windows,
    then when the whole Palladium initiative
    finally locks the user out of any real interface
    or OS tinkering, I'll be used to it.

    -milo

  91. Mac Newsreader by 0x0d0a · · Score: 2

    There are quite good newsreaders for the Mac. I suspect that you can probably run the terminal-based newsreaders a la BSD. I use pan on Linux, but I never had a problem with YA-NewsWatcher on the Mac (which evidently has become Thoth).

    Take a look here for other newsreaders.

    1. Re:Mac Newsreader by lemkebeth · · Score: 1

      Throth though if based on YA-Newswatcher code violates the NewsWatcher licence by asking for a fee.

      Try MT-NewsWatcher instead. Also, there is an X version of MT-NewsWatcher (freeware app).

  92. Everything new by 2nd+Post! · · Score: 2

    Why? I question every statement you make.

    "People who think POSIX is the best thing since sliced bread agree that Mach sucks"

    Have you no opinion of your own? Just because other people think Mach sucks, you think Mach sucks? Did you know 95% of the population also think that the Mac sucks, even *before* OS X? Okay, so 95% is an exaggeration. But 'experts' also disavowed the Mac. What's new, the difference between you and them?

    "The least Apple could have done would be to use a better microkernel"

    How or why? What would be better about this new microkernel over the XNU-macho microkernel already in place? The macho microkernel has been tested across 16 years and 5 hardware architectures (68k, x86, PPC, Sparc, HP-UX), as well as 4 OSes (NeXT, Open, Darwin, and OS X), so it's fairly good, no?

    Also, I would like to point out that the *Linux* kernel is deficient in regards to latency. Only recently has low latency and pre-emptive patches have made Linux reliably low latency. Not a problem with OS X; in which case, how do you define better?

    "or to design a POSIX-compatible kernel from the ground up that was legacy-free and more similar to how Macs have always worked, no?"

    You're going to have to define legacy free for me. What legacy does OS X have that burdens it. You'll also have to define how or why the classic Mac had an advantage that would make a different kernel an advantage.

    The current kernel has several advantages over the classic Mac OS;

    low latency: As evinced by CoreAudio
    multitasking: No application can take 100% of the CPU to the exclusion of any other application.
    multiprocessing: This is given 'for free' to any multi-threaded application.
    multithreading: The classic Mac OS could not handle multithreading, and as such, could not handle multiple processes, multiple CPUs, and multiple tasks gracefully.
    robustness: The classic Mac OS was not nearly as stable, reliable, or dependable as the current Mac OS, thanks to preemptive multitasking (to ensure no thread or process because CPU starved), protected memory spaces (to ensure that no application or process can intrude and disrupt any other application or process, including the kernel), and a much better virtual memory system to allow more efficient use of available, virtual, and shared memory. Of course, to counter this, one requires more memory than in the classic OS too.

    1. Re:Everything new by psicE · · Score: 2

      Have you no opinion of your own?

      First, I thought Mach was good. Then I read up on comparisons of different microkernels; and found that Mach is actually somewhere in between a microkernel and macrokernel, but closer to the worst of both worlds than the best. I personally think that L4 would be a better choice for most situations, including for OS X.

      How or why? What would be better about this new microkernel over the XNU-macho microkernel already in place?

      The Mach kernel, though claiming to be a microkernel, does a lot that should be done in userspace; in the L4 kernel, absolutely anything and everything that can be done in userspace, is. Using a nanokernel like that would make OS X work much better.

      Also, I would like to point out that the *Linux* kernel is deficient in regards to latency.

      I'm not advocating Linux at all; I much favor the GNU/Hurd and BeOS for their microkernel architectures. I simply think that the OS X kernel could be much more micro than it is.

      You're going to have to define legacy free for me. What legacy does OS X have that burdens it.

      OS X doesn't have legacy. What I meant was, perhaps Apple would have been better off simply updating the Mac OS 9 UI and apps, on top of a clean Cocoa-style API, all on top of a nanokernel, instead of completely rewriting the UI and making it worse than the original one.

      The current kernel has several advantages over the classic Mac OS;

      I know this fully, and I agree. And I think OS X at its core is quite a good operating system compared to most of the alternatives.

      My point is only that Apple felt it necessary to completely redo their operating system. I think if they did that, they should have used a nanokernel instead of a microkernel, and that they also should not have felt the need to completely scrap the OS 9 interface (they should have, in my opinion, just ported it to Cocoa, and made both Platinum and Aqua available as visual options).

  93. Layman's? by CaptainSuperBoy · · Score: 2
    Written on a layman's level

    Huh? It's written for DEVELOPERS. Did you even read the page?

    1. Re:Layman's? by damiam · · Score: 1

      It's written for developers on a laymen's level. Is there a problem with that?

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    2. Re:Layman's? by Anonymous Coward · · Score: 0

      layman = windows developers :P

    3. Re:Layman's? by Anonymous Coward · · Score: 0

      Bullshit. I hope you die of cancer of the eyes.

  94. Fabulous example of why non-standard = awkward by Anonymous+Brave+Guy · · Score: 2

    Visual C++ 6 (the last version before Visual Studio.NET) is the standard development tool where I work. When I started, they gave me a nice, new Windows XP box to play with.

    The great thing about this is that Visual Studio looks like a fish out of water. Microsoft's developers obviously used a whole load of non-standard controls to set up things like the docking windows. Sometimes, they even look the same as the real thing, but aren't; I assume they had some reason for this at the time. Unfortunately, what I now have to look at is some horrible mixture where half the scroll bars on a basic development screen are WinXP style, and the others are "classic Win2K". Same goes for tabs, dialogs, etc.

    This is an object lesson in why, as Apple rightly points out, you should normally try to avoid custom controls, and if you do use them, they should be for something clearly unique, and not just a drop-in replacement for the standard issue.

    --
    If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    1. Re:Fabulous example of why non-standard = awkward by shyster · · Score: 2

      change your theme and performance options to get rid of the XP cartoons and it'll be nice and consistent. Geeks don't care about looks, we care about perfromance....and those few cycles saved will beneifit you in the logn run.

    2. Re:Fabulous example of why non-standard = awkward by jimbolaya · · Score: 2
      Geeks don't care about looks

      Which is precisely why Apple needs to provide human interface guidelines and articles like this. Otherwise, we'll wind up with interfaces that are designed by geeks, for geeks.

      --

      There ain't no rules here; we're trying to accomplish something.

    3. Re:Fabulous example of why non-standard = awkward by DCMonkey · · Score: 1
      Geeks don't care about looks,

      Could have fooled me. It seems sometimes that all they(we?) care about is looks when it comes to GUIs. Some kind of cult of the screenshot. I freely admit to coming under its influence at times.

      we care about perfromance....and those few cycles saved will beneifit you in the logn run.

      Yeah. And if I could save time in a bottle ...

      --
      DCMonkey
  95. Standard widgets are pretty good by 0x0d0a · · Score: 3, Interesting

    if your new custom [widget] is well designed for its specific use, rather than merely cobbled together from generic components then any initial time-wasting will be saved

    I disagree. I generally find that custom widgets charm developers, and annoy users.

    Lets take a look at existing custom widgets. The big annoying ones are bitmap ones (on Windows, often using the standard button as an underly widget). These look different, add nothing to the application, amake the program bigger (esp. to download), slower, look less professional, and seem to frequently be written by interns or something, judging by the quality of them.

    There are custom tab widgets. They usually aren't any better than normal tab widgets, especially the annoying reshuffling multi-row tab widgets.

    There are animated widgets. Animated widgets are just plain annoying to a lot of people.

    There are dials. Every custom widget library seems like it has to come with a dial widget. Dial widgets are about the most difficult interface to work with on a computer, given your input devices (keyboard, mouse).

    A lot of examples of what custom widgets do and how bad they are can be found at the excellent Interface Hall of Shame.

    There are a *very* few custom widgets that I've seen over the past few years that I think are honestly good and deserve being adopted. I haven't seen a single Windows widget that I like, and in all my years of poking around at human-computer-interaction, I've seen exactly three widgets on the Mac that were a good idea (all of which were pretty much uniformly adopted by the Mac developer community).

    A) The slider. The MacOS never had a slider control. When MS copied the Mac's interface elements, this is one of the things they did right -- added a slider. Traditionally, MacOS developers have used scroll bars to fill in the gap, but a fair number of people have introduced a Windows-style slider.

    B) The Mercutio MDEF -- this is a menu widget that supports more complex keybindings. The original Mac menu widget only supported Command-A, not Command-A separate from Command-Shift-A. This has been a fairly useful invention (and the UI was done right -- there was a shift symbol added, not just a capital "A" shown in the menu).

    C) Windoids. These are the little palettes that vanish when you switch to other apps. They don't look like standard windows, they disappear on their own, but they're so useful that everyone uses them now.

    There are also a few, high-level and very custom widgets that don't really appear to the user as widgets, and make reasonable sense. A calendar widget, or something along the lines of GnomeCanvas.

    1. Re:Standard widgets are pretty good by cpt+kangarooski · · Score: 1

      I do agree that there's room for innovation. My only minor nit is with the MDEF.

      On most keyboards -- certainly those Apple ships -- the space, control and option keys don't have any symbols on them. Thus the use of symbols in Mercutio is really perverse as there's no real hint what keys they match.

      Adding symbols along with the text to those keys (and text to the command key), and in the meantime permitting expansion of the menu symbols into text wouldn't have hurt!

      --
      -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
    2. Re:Standard widgets are pretty good by gig · · Score: 2

      All of the "standard key commands" use the Command key, which does have a symbol on it. So to enter any of these commands on a Mac, first hold down Command, then press:

      Open (O)
      Save (S)
      Print (P)
      Select All (A)
      Quit (Q)
      Cut (X)
      Copy (C)
      Paste (V)
      Undo (Z)
      Find (F)
      Find Again (G)
      Help (?)
      Close Window (W)
      Minimize Window (M)
      Hide Application (H)

      That's a lot of productivity and utility for one modifier key, never mind learning the other modifier keys, which is something that's for the truly keyboard-committed.

      Also, Option really works as an option. You can often figure out what Option will do when you press and hold it, because it will just be the opposite of not pressing it. For example, in iPhoto, there is a button that rotates selected images counter-clockwise. When you hold down Option, the button reverses to suggest that pressing it will rotate the image clockwise.

      Nobody ever suggests that the current state of the Mac UI is the ultimate holy grail of interfaces, but it does represent the best thing out there for most people, by a large margin. Most Mac users have also used Windows at some point (at a job, school, library, previous computer, friend's house, whatever) and they still swear by their Macs. Most Windows users, however, typically don't really understand that there are alternatives. They are used to a one-party system and they can't imagine what anything else is like. Time and time again, though, you hear from people who used Windows for years and then switched to a Mac and you see that their eyes were opened. So many problems just drop away. So many housekeeping chores just disappear. So many daily annoyances and especially interruptions just disappear. Flaky hardware and instability just disappear. You can't tell me that Alt+F4 is a better key combination for "close this application" than Command+Q (Quit). You can't tell me that Windows is better because I used it for years and I know it's not.

    3. Re:Standard widgets are pretty good by cpt+kangarooski · · Score: 1

      No, I _do_ generally agree with you. (although I also remember the bad old days when Cmd-P officially meant 'Plain')

      I'm just pointing out this _ONE_ niggling thing.

      --
      -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
  96. Re:Doesn't acknowlege Windows' keyboard superiorit by RickHunter · · Score: 2

    I find that this is especially bad with KDE. Some actions have well-chosen shortcuts, and I use those a lot. Others are totally lacking in keyboard shortcuts, have hard-to-rembmer shortcuts, or have shortcuts that are totally unadvertised.

    The most obvious example of this, IMHO, is kicker. The K menu has, at least in 2.2.x, no keyboard accelerators at all. Bring it up with alt-F1 and scroll around with the arrow keys, fine. But why can't I hit "g" and jump to games, like Windows has allowed me to do in the start menu since 1995?

    There are even bug reports on bugs.kde.org under the kicker package dealing with this. I seem to remember seeing one where the submitter was flamed mercilessly by the operator of the KDE bug tracking system, though that bug seems to have since disappeared. More recent bugs point out that KDE 2.x removed the capability to even define your own menu shortcuts.

    On the other hand, licq is an example of a program that does this well. Most operations have convenient and well-indicated keyboard shortcuts.

    Note to the authors of KDE and GNOME: Just because its a graphical environment doesn't mean you're not allowed to use the keyboard for anything!

  97. The more things change, the more things stay... by 2nd+Post! · · Score: 2

    the same.

    I believe even *with*, and maybe *because* of 21" 1600x1200 resolution screens, Fitts law holds even more than before.

    The 90 pixel tall menu is an even smaller target; your mouse, as precise as it is, has to traverse over hundreds more pixels than in the original 4" screen, making targetting menu bars even harder. Which is the reason why OS X icons scale up to 128x128, taking into account an expected increase in resolution in the future (larger icons are easier to see and hit, than traditional 32x32 icons). In fact, though it may be a hindrance now, that explains why *everything* in OS X is slightly larger.

    1. Re:The more things change, the more things stay... by X_Caffeine · · Score: 1

      re: In fact, though it may be a hindrance now, that explains why *everything* in OS X is slightly larger.

      But I bought a high-resolution monitor to make everything smaller!!!!

      --
      // I will show you fear in a handful of jellybeans.
    2. Re:The more things change, the more things stay... by lemkebeth · · Score: 1

      Actually, the point of high resolution monitors is so you can get more actual pixels per visible pixel.

      The time was long overdue when UI elements should have been made bigger.

      This gives more detail to elements on the screen.

      I mean do you have REALLy good eyesight or something? (Mine is pretty poor)

      Still even with excellent eyesight, making the screen elements smaller and smaller due to increased resolution will eventually make things illegible.

  98. Re:Doesn't acknowlege Windows' keyboard superiorit by BusterB · · Score: 3, Interesting

    > The most obvious example of this, IMHO, is
    > kicker. The K menu has, at least in 2.2.x, no
    > keyboard accelerators at all. Bring it up with
    > alt-F1 and scroll around with the arrow keys,
    > fine. But why can't I hit "g" and jump to
    > games, like Windows has allowed me to do in
    > the start menu since 1995?

    I just checked, and at least KDE 3.1 CVS lets you press a key to jump to the first kicker item beginning with that letter. The letters get underlined when you press a key. The developers are listening.

    - Brent

  99. Re:Doesn't acknowlege Windows' keyboard superiorit by Arandir · · Score: 2

    e've put a ton of work on making nedit keyboard accessible.

    There's the problem: "a ton of work". KDE has a really great infrastructure for keyboards and keyboard shortcuts. But it's a ton of work, and boring besides, to make your app use keyboard shortcuts properly.

    When you're starting out on a new program you delve right into the meat of the cool new stuff you're going to do, arguing that you'll get the keyboard accelerators (and toolstips, what's this, and other GUI stuff) done once you're application stabilizes. But by that time you're stuck. The users are busy submitting wishlists for more cool new features, and you're spending a lot of your time in maintenance mode.

    It would be great if some UI guy came along and started working on the KDE interfaces. This doesn't take a lot of coding expertise, just someone with an eye for consistancy and the fortitude to slog through a really large code base.

    --
    A Government Is a Body of People, Usually Notably Ungoverned
  100. Forward thinking by firippu · · Score: 1

    I think people are missing a more important subject that this discussion calls attention to. I don't see Apple as being perfect in any sense, but its their mode of process and willingness to evolve is generally more progressive and open to the end-users experience. The fact that they even post such articles to help guide potential developers for the OS X platform is something of a curiousity. This article brings up issues that stand alone of any os... I work for a company that does interaction design, and from experiece I can see that Apple realizes that under all the "apps and machinery" of the system, the end UI has an emotional connection with users. There's something about an interface that has cohesion and consistency; it becomes an experience rather than a mechanical operation of clicking mouse buttons and dragging windows. I know for a fact that MS is following Apple's lead at this very moment...

    For god's sake, the last time I was on a windows machine, I started up WinMX and nearly screamed at the interface... I've never had such an experience on a mac... There's a level of comfort in knowing I can expect an intuitive interface on a mac... Windows? Its the best crapshoot I've ever played with!

    1. Re:Forward thinking by Anonymous Coward · · Score: 0

      You blithering idiot, WinMX's bad interface has absolutly nothing to do with Windows. It's all about the developer.

      Were I willing to develop an app for Mac, and I'm not, I would give it the WORST POSSIBLE INTERFACE IMAGINABLE just to spite smart guys like you.

    2. Re:Forward thinking by MoneyT · · Score: 2

      And where as in the windows community your program would most likely be used because in actuality it isn't much worse than some apps out there, in the mac community it would fall flat on it's face.

      --
      T Money
      World Domination with a plastic spoon since 1984
  101. ..." and hardly use any system resources" by Anonymous Coward · · Score: 0

    Actually I did not find this to be true on Win2k Pro. I had Windowblinds set up and was utilizing their virtual desktops tool to enable me to have one window for email/web and one window for active work. The machine was a PIII-800 w/ ~300-400 megs ram (can;t remember exact specs). I found that it significantly slowed startup times on the system/apps as well as compromised the stability of the apps themselves. Even after shutting off the window customization I found this to be true so perhaps it was that particular module but I don't see it as a solution to the staleness of WinXX UI.

    As of this month I now run Gentoo w/ Fluxbox on the machine as the primary OS and I have Win2k Pro running under VMWare Workstation (3.xxx). It is much more responsive this way and it more closely mirrors my home setup.

    I do not have hard proof but I have heard OS "power-users" (ones who frequently use Win/*nix/Mac for different purposes) complain of OS-X's sluggishness with the default Aqua interface with the bells & whistles on. This is presumably addressed is Jaguar but I'm personally tired of eye-candy/performance trade-off in OS/app design the same way I tired of flash interfaces in HTML pages.

    1. Re:..." and hardly use any system resources" by Anonymous Coward · · Score: 0

      One word, STYLEXP

    2. Re:..." and hardly use any system resources" by RzUpAnmsCwrds · · Score: 2

      "on Win2k Pro"

      That's your problem. Win2000 doesn't have a native skin engine. XP does (uxtheme.dll).

  102. Re:Doesn't acknowlege Windows' keyboard superiorit by bedouin · · Score: 1

    I'm a recent switcher and can't speak very well for OS 9 or prior, but in OS X there seems to be a fair amount of keyboard shortcuts, some more useful than anything in Windows. For example, if you want to open up your home directory just hit shift + apple + H; if you want to view your applications folder do the same but hit A. To mount a network drive press apple + K. Most applications have keyboard shortcuts for commonly used operations.

    One thing that was awkward for me at first was Apple + C/V to cut and paste, instead of using Control, like on PC's. It actually makes more sense to me now, since the Apple key is a shorter distance than Control from C and V; it feels more natural. Cutting and pasting in Linux I've always found to be a little bit clumsy; a lot of times I'd end up making mistakes, copying or pasting things I didn't actually want to.

  103. file extensions by Gaccm · · Score: 2

    Unlike Mac OS 9 and earlier, Mac OS X supports and utilizes file name extensions. However, if your application allows users to create documents, such as PDF files, that may find their way onto earlier versions of the Mac OS, be aware that you must write Type and Creator information to those files in order to make them usable on Mac OS 9 and earlier.

    Mac OS X is going from the unix meathod (file types with the data writtin in the file) to the windows meathod (file extensions) While making things slightly simpler for apllication makers, why would they do this? One of the big problems with file extensions is that virus makers use fake icons and .txt or .html endings to their names (i.e. virus.html.exe) to trick the user. Anyone have any ideas on why they would switch to an idea as old as DOS?

    --

    Only dead fish swim with the stream...
    1. Re:file extensions by Etcetera · · Score: 2


      I agree... the Metadata usage in OS X is a step backwards. But it's actually that they're coming from the Mac method (type/creator codes) to the Windows method (with the unix layer using the unix method, obviously). They really should have added "chtype" and "chcreator" utilities ao the BSD layer - and submitted mods to "ls" to optionally display that info from the command line. =(

      Try this article at ArsTechnica for more insight: Metadata, The Mac, and You.

    2. Re:file extensions by Anonymous Coward · · Score: 0

      It's simply about compatibility. With companies sending Word (.doc) files all over the place every day, Apple had to recognize those dot-three extensions as valid document types.

      Accepting "dot-three" as a standard was the simplest way to accomplish more PC compatibility.

    3. Re:file extensions by Etcetera · · Score: 2


      It's simply about compatibility. With companies sending Word (.doc) files all over the place every day, Apple had to recognize those dot-three extensions as valid document types.

      OS 9 was more intelligent about that though. It performed the recognition *at the time the foreign file was introduced into the file system*. When something was downloaded from the internet, decompressed from a non-Mac archive, or copied or opened from a foreign file system (ie, Unix or MS-DOS), *that* was when the File Extension/MIME Type recognition would kick in, assign the right 4-character TYPE code, and assign the default Creator code for that type. Once the file exists in the Mac filesystem, this automatic behavior stops.

      Similar behavior occurs when copying or sending data to a foreign file system (well, it should). The Mac does a lookup on the appropriate .xxx extension and mime-type for a specific TYPE code (and for a specific Creator code, if that entry exists) and renames the file with the appropriate extension. If nothing is found, leave it unchanged if it only has a data fork, flatten it into MacBinary and add ".bin" if it has a resource fork.

      By dealing with meta-data at the point/time of entry, it allows the system to remain compatable with other OS's, but still allows someone working natively on a Mac to not have to deal with idiosynchrasies and restrictions they don't have to.

    4. Re:file extensions by foo12 · · Score: 1

      They did --- install the dev tools. SetFile and GetFileInfo do exactly that.

  104. Well, uh, yeah by tkrotchko · · Score: 2

    I'm typing this on a powerbook using 10.2, but I still think the trashcan should be removed from the whole UI.

    I understand all the points people are making, but I don't find the GUI particularly intuitive (or unintuitive).

    The real reason I prefer 10.x these days is that underneath all the UI stuff is BSD, the GUI is beautiful, but nothing earthshaking.

    But I love my powerbook.

    --
    You were mistaken. Which is odd, since memory shouldn't be a problem for you
  105. Beachball by 0x0d0a · · Score: 2

    The spinning beachball only appears on applications that are busy

    I'd like to see the "busy cursor" die. It's really annoying in a modern windowing system, where you have multiple windows open with different busy states and need to move the mouse around to see all of their states.

    The "busy cursor" was developed for application-modal systems, where only one application was ever in onscreen at one time. The user was usually looking at the cursor, so the cursor was the best place to put a busy indicator -- and if they weren't (possibly using the keyboard, you'd make the cursor visible and then start animating it).

    These days the "busy cursor"provides only a partial view of information on the system and requires the user to switch to the mouse to check busy statuses on various apps. It would be much better to provide a "busy" titlebar indicator on each window (since these days windows, not screens, are the smallest unit across which a "busy" status might differ).

    Of course, minimizing UI modality is also important...

    1. Re:Beachball by stux · · Score: 2

      The busy cursor is because the application is not responding to the OS.

      This is an application issue. If the application was updated to do its heavy lifting in a thread and run the interface in a separate thread, then you wouldn't get the busy cursor.

      --

      ---
      Live Long & Prosper \\//_
      CYA STUX =`B^) 'da Captain,
      Jedi & Last *-fytr
    2. Re:Beachball by 0x0d0a · · Score: 2

      The busy cursor is because the application is not responding to the OS

      Actually, (at least in the classic MacOS API -- I don't know what happens under OS X) the busy cursor *only* appears and is animated if the application *is* responding to the OS. The application does the work of displaying the busy cursor.

      The question is whether the application is currently ready to accept user input.

      If the application was updated to do its heavy lifting in a thread and run the interface in a separate thread, then you wouldn't get the busy cursor

      If you'll notice, I mentioned the fact that that it would be nice to thread or at least queue tasks at the bottom of my original post -- "of course, minimizing UI modality is also important..."

      BTW, having a UI thread was decidedly nontrivial on the classic MacOS because the Toolbox was nonreentrant -- I suspect, but do not know, that this has changed.

    3. Re:Beachball by gig · · Score: 2

      The busy cursor will disappear when applications stop causing it to appear. In a year or two all Mac apps will be multi-threaded (many are now) and there won't ever be a situation where an application stops responding to the system for seconds at a time.

      The MS fix for this would be to remove the busy cursor. The Apple fix is to make it easy to multithread your app and then encourage developers to do that.

    4. Re:Beachball by stux · · Score: 2

      The busy cursor is because the application is not responding to the OS

      Actually, (at least in the classic MacOS API -- I don't know what happens under OS X) the busy cursor *only* appears and is animated if the application *is* responding to the OS. The application does the work of displaying the busy cursor.


      I'm telling you what happens in OSX, the busy cursor (the spinning pizza wheel) appears when the Application is does not respond to the OS for a certain amount of time (it was 1 second in 10.1, I believe its 2 in 10.2). This is related to CarbonEvents, but calling WNE in an old-school mac app at least once every second would be enough to stop the pizza-wheel

      -- reluctant Carbon programmer

      --

      ---
      Live Long & Prosper \\//_
      CYA STUX =`B^) 'da Captain,
      Jedi & Last *-fytr
    5. Re:Beachball by stux · · Score: 2

      IOW make it so that users encourage developers to fix their apps :)

      Which is really the best way to get the problem fixed fastest :)

      --

      ---
      Live Long & Prosper \\//_
      CYA STUX =`B^) 'da Captain,
      Jedi & Last *-fytr
  106. Seems like people are missing the point by JoshWurzel · · Score: 2, Insightful

    The point of this document isn't to say "our interface is right and Windoze blowez". Notice that the url for the page includes the words "developer" and "switch". That means: THIS IS FOR DEVELOPERS WHO ARE STARTING TO DEVELOP FOR MAC.

    Its a set of guidelines to make the porting of a windows application smoother and better received on Mac OS X. Its not an easy thing. The fact is that most ports of Windows software to macs are quite annoying because they flatly refuse to follow the "standard" interface (okay yeah, the iApps don't really follow it either - and I find them annoying too).

    Yes, Apple does somewhat ignore it. But that's not the point at all. Have you seen Matlab 6.5 for OS X? Developers who are thinking about porting their apps to OS X need to realize that Mac users will not be infinitely grateful to them just for doing it. We want our apps to look nice, and feel responsive and familiar when we use them. If you aren't interested in taking the time to put a decent interface on your app, then you should consider letting your competitor "have" the mac platform for your field.

    I'm not saying its easy. But I don't think porting an application is easy at all. And interfaces are SOOOOO easy to build in OS X. Just drag and drop with the available buttons/widgets in Interface Builder. It needs to be done. Mac users have just enough choice in software that they can pick a competitor's product over yours given the same price range and feature set...just because one doesn't look as nice as the other.

    1. Re:Seems like people are missing the point by Anonymous Coward · · Score: 0
      The point of this document isn't to say "our interface is right and Windoze blowez".

      Maybe that wasn't the point of the article, but that's the way it was written. Point by point, the author tried to gloat over Aqua and slam Windows, even going so far as to doctor real Windows dialogs so that they illustrated bad design.

    2. Re:Seems like people are missing the point by MoneyT · · Score: 2

      It was used as an example, as no windows dialouge has all those problems in one shot. It saved space on the document. And to top it off, they couldn't use an exact screen shot, that would violate copyrights. Ad into it that the mac screen shot provided does not exist as a real screen and you see it was all to exemplify a point.

      --
      T Money
      World Domination with a plastic spoon since 1984
  107. Re:Doesn't acknowlege Windows' keyboard superiorit by CaptnMArk · · Score: 2, Interesting

    Proposal 1:

    I suggest every GNOME/KDE/... developer sets one day of the week where he will use X without using the mouse.

    Proposal 2:

    When above is no longer a problem... try using X without running a terminal emulator for anything.
    This will really help improve linux GUI for non-hackers.

  108. some work to do on recently aquired apps by Anonymous Coward · · Score: 0

    Well, it will be a real tough job squeezing Logic Audio's myriad of window-centric menubars into the already cluttered main application menu bar.

    Maybe they will update Logic's ancient midi device icons while they're at it...

  109. Re:Right Click (right click works) by Anonymous Coward · · Score: 0

    Once you get used to it, Keyboard+Mouse control is actually a little faster than Multibutton-Mouse control.

    There is absolutly nothing to substantiate this claim. Once a user gets accustomed to any multi-step task they would of course be quicker at it than using an alternative. It also presumes that the user has one hand on the keyboard and another on the mouse. Too much wrong with the parent to comment without flaming...

  110. yep by Kalewa · · Score: 0, Flamebait

    Sounds like Apple's standard pompus elitist bullshit to me.

  111. iYawn by Anonymous Coward · · Score: 0

    Macs are not interesting computers. Sorry, they're not. They work, they're easy to use, but they're just not interesting. It's like the difference between woodworking and buying at Ikea. Half the fun of having a PC is tweaking it and tuning it to get the most out of it. You end up with something that's personal. You just can't do that with a Mac, at least not at the same level. Macs would make great office / family computers if they weren't so ridiculously expensive.

    How many people who read Slashdot use Macs? Now compare that percentage with the number of articles about Macs vs. the number of articles about PCs. It's just silly. Macs aren't "cool". They're over-priced PCs designed to appeal to women ("that one would go really well with our curtains").

    The only reason some Slashdot editors are pushing Macs is they hate Microsoft, and Macs don't run Windows. But Apple is the closest thing there is to a Microsoft hardware department ("you have to buy our OS and you have to buy our hardware!").

    The problem is, 90% of Slashdot's audience are geeks. And geeks would never buy a Mac (first because Macs are too expensive, second because they're not half as tweakable as PCs and third because there's a serious lack of w4r3z).

    So get over it, Slashdot editors. At home, Windows is here to stay. And even at work, PCs are taking over all segments. Why? Because PCs use something you're so fond of: open standards. So stop posting irrelevant stories that even Mac users yawn at and start posting stuff that really matters (such as stories about the Hammer, Barton, Serial-ATA, Linux, OpenGL2, etc.).

    1. Re:iYawn by MoneyT · · Score: 2

      All that fun fun teaking. Like wastng an entire saturday fixing a sound card because it broke when Win2k updated. Or like following Billy Bob Tech's guide to over-clocking. Or trying to figure out why despite everything you've tried, your monitor still flickers every half hour.

      Macs are computers you can tweak when you want, not because you have to. And it's more challenging therefore more fun. What the hell is so fun about over clocking your computer from the BIOS? Nothing. Now do it on a mac, and you need to get out your soldering iron. That's fun. So tell me what wonderful tweaks I can do to my PC that are any where near as fun as they would be on a mac (I dare you to get a mac classic running a color monitor, or get an LC up and running OS 9)

      As for cost, too fsking bad. Maybe if you stopped buying $500 sound and video cards every 6 months, you would have enough money for a mac.

      --
      T Money
      World Domination with a plastic spoon since 1984
    2. Re:iYawn by Anonymous Coward · · Score: 0

      As for cost, too fsking bad. Maybe if you stopped buying $500 sound and video cards every 6 months, you would have enough money for a mac.

      I won't bother asking you to show me a "$500 sound card", or with detailed sales figures for high-end graphics cards (I'll just point out that 90% of systems use graphics cards under $150).

      I'll just focus on the main point, which you seem to have missed: the reason why I don't buy a Mac is not that I can't afford one. I can. In fact I can afford a truckload of them. The point is I don't want a Mac. Can you grasp the concept? Oh, I use Macs sometimes; I'm not allergic to them or anything. I just can't find any mentally sane reason to buy one.

      Take the top-of-the-line Mac (Dual G4). I've used one and it's a decent machine. But I can buy an equivalent PC for about 60% of the G4's price (in other words, I can almost buy two equivalent PCs for the price of a single Dual G4). And (and this is the important bit), if I'm willing to spend a bit more, I can buy a PC that runs circles around the Dual G4.

      So you see, the PC has both ends of the market. The high-end of performance and the low-end of price. The only reason to buy a Mac (other than ignorance) is to feel superior.

      I can see it worked in your case. Money well spent.

    3. Re:iYawn by MoneyT · · Score: 2

      How about OS X? That seems like a nice reason to buy a mac. Pluse the machines look nice. And I don't have to deal with microsoft, or intel. And I don't have to worry about drivers breaking. And I prefer the system? I use both macs and PCs, and when I have the chance, I rather use a mac.

      --
      T Money
      World Domination with a plastic spoon since 1984
    4. Re:iYawn by ktoz · · Score: 2, Funny
      Half the fun of having a PC is tweaking it and tuning it to get the most out of it.

      Half the fun of owning a toaster oven is modifying the heating coils so you can smelt your own iron.

      Half the fun of owning a ceiling fan is tweaking the motor so it can suck cats off the floor.

      Most people however buy things to use them. Macs are very usable, that's why people buy them.

      If elegant design offends you, just rip the guts out of a Mac and epoxy them to a piece of sheet steel. You'll have all of the functionality without any of the prissiness you seem to associate with good design. And...it'll look right at home in your garage next to that disassembled carburetor : )

  112. But OS X makes all these mistakes, too by het3 · · Score: 1

    OS X is nice, but it has inconsistencies that show poor design. Closing a window might just close a window, or it might close a window and close its application. Many preference dialogues do not have an explicit "Save" option, and no explicit way to revert the settings to what they were: the way to save is to close the window.

    So closing a window might mean "close the window," "quit the application," or "save and close the window." There is no explicit interface to tell you what will happen when you click that little red ball. You have to have a good bit of a priori knowledge to guess what will happen.

  113. it's not all roses by g4dget · · Score: 4, Informative
    Don't get me wrong, OSX is good. In some UI areas, they really are better: dialog boxes are designed better, getting rid of MDI is a good idea, and getting rid of the gray is also good (I never understood why toolkits became so enamored with gray--now if we could only get rid of pseudo-3D...).

    Here are just three observations that come to mind:

    • The single menu bar is a pain on large screens. Worse, it is confusing to many users: when they start an application, they expect an application to appear, not just some subtle change in the appearance of the menubar.
    • Packaging applications in a single directory is good, but drag-and-drop installation is not. When I download the latest version of Mozilla, I don't want to have to hunt down the old version and delete it by hand. Nor do I want to have to hunt down the shortcuts to the old version and replace them with new ones. Upgrading application software should be automatic and centralized. The answer is a real packaging system, not Windows installers, and not drag-and-drop installation.
    • Apple wants consistency among Macintosh applications, so they want developers to use standard shortcuts. That's great for their business--it turns all Mac users into Mac zealots who wouldn't consider using anything else. But as a user who uses different platforms, I want consistency among my different work environments. It makes no difference to me whether my desktop is consistent with yours, what matters to me is that my different desktops are as consistent as possible. That means that platforms need to be configurable.

    There are other problems with the Aqua UI. But the most basic one is perhaps that it is just another toolkit-based GUI--a system in which people produce the same kind of inflexible applications that people produce in the other major toolkits on the other major platforms. The fact that Aqua looks a little prettier and crashes a little less does not get around this basic fact.

    Overall, I think what makes Aqua most useful is a desire to keep applications simple. Unlike Windows, Gnome, or KDE, it comes with useful applications are not overburdened with zillions of options; developers of those desktops should take notice.

    1. Re:it's not all roses by 90XDoubleSide · · Score: 2
      * The single menu bar is a pain on large screens. Worse, it is confusing to many users: when they start an application, they expect an application to appear, not just some subtle change in the appearance of the menubar.

      Mac OS X apps always create a new document (or viewer, main window, etc., as appropriate to the app) when you activate them, so it is no longer possible that the only change you see when switching apps is a new menubar as was possible in Mac OS 9, and of course every app must always create such a window when it launces. You can still switch to an application with no open windows without creting a new window by using command-tab, but in this case it is already extremely apparent which app you have switched to because of the highlight and magnification of that application's dock icon, and this is not the method new users will use at first.

      --
      "Reality is just a convenient measure of complexity" -Alvy Ray Smith
    2. Re:it's not all roses by Anonymous Coward · · Score: 1, Insightful
      The single menu bar is a pain on large screens. Worse, it is confusing to many users: when they start an application, they expect an application to appear, not just some subtle change in the appearance of the menubar.

      I don't know what you mean by it being a pain. I use 1600x1200 displays and have no problems. It is only confusing to people who have been brainwashed by windows to expect that running 10 applications means that the menu bar options are spread around in 10 different places.

      Packaging applications in a single directory is good, but drag-and-drop installation is not. When I download the latest version of Mozilla, I don't want to have to hunt down the old version and delete it by hand. Nor do I want to have to hunt down the shortcuts to the old version and replace them with new ones. Upgrading application software should be automatic and centralized. The answer is a real packaging system, not Windows installers, and not drag-and-drop installation.

      That is why there is an Applications folder. If you put your applications there you won't lose them. If you put them in some other obscure corner of your hard drive, then it's your own fault if you can't find them.
      I don't know what your talking about with shortcuts. If you put the new version in the same place as the old version then your aliases and your links will still work. Plus, you can keep multiple versions around if you need to without conflicts. I'd like to see you do that with IE on Windows.
      Oh, and it would be terrible to be able to install applications with one simple drag and drop action. Much better to have to click Next fifteen times.

    3. Re:it's not all roses by Anonymous Coward · · Score: 0

      [quote]The single menu bar is a pain on large screens. Worse, it is confusing to many users: when they start an application, they expect an application to appear, not just some subtle change in the appearance of the menubar. [/quote]

      There is a reason for this though... the reason is that it is an infinite target.

      What I mean by this, is that if you take your mouse, and you push it right to the top of the screen.... you are on the menu, and you can click an item.

      There was a test awhile go where the took a Mac user, and they said that if they were able to continue going up with the mouse, that they would over shoot them menu by over a factor of 1.5 (that means an extra 1.5 screens).

      Take in contrast windows, the start bar used to be that you had to click exactly on the button... now they copied the infinite target for that, but the way the window system works, they cannot have infinite targets for their menus unless they drastically change their OS (read: copy Mac OS).

    4. Re:it's not all roses by Dr.+Sp0ng · · Score: 3, Insightful
      Packaging applications in a single directory is good, but drag-and-drop installation is not. When I download the latest version of Mozilla, I don't want to have to hunt down the old version and delete it by hand. Nor do I want to have to hunt down the shortcuts to the old version and replace them with new ones. Upgrading application software should be automatic and centralized. The answer is a real packaging system, not Windows installers, and not drag-and-drop installation.
      You don't have to. Just drag the new version to you Applications folder, and you'll get a dialog box asking if you want to replace the old version. Click Yes, and you're done.
    5. Re:it's not all roses by iJed · · Score: 1

      I totally disagree with you on drag-and-drop installation. Not only does this keep consistancy with other file system operations, it is simply better than any other method around. With drag-and-drop you can put your app anywhere you want on disk, and if there is an update you can just replace it and have all aliases continue to work. This, in my opinion, is the greatest feature of the Mac UI.

    6. Re:it's not all roses by Dixie_Flatline · · Score: 2

      The menubar across the top is a far better interface system than the menubar across the top of each window. It's because of Fitts' law. Someone already mentioned that it makes the menu a somewhat 'infinite' target. While not entirely true, it's provably true (ie. I can do the math do back it up, and moreover, I can do usability tests with a random sample of the population to back me up) that it's faster to hit the menu bar in MacOS than in Windows.

      Fitts' law directly relates the size of the target and the distance you have to travel to the target to how long it will take you to hit the target. It's the reason why the start bar in WindowsXP has now changed to extend all the way to the bottom of the screen since Windows 2000. It's much faster to access the start menu now.

    7. Re:it's not all roses by g4dget · · Score: 2
      Mac OS X apps always create a new document (or viewer, main window, etc., as appropriate to the app) when you activate them,

      Maybe that's what they are supposed to do, but they don't. Mozilla is an example of an application that doesn't, and there are others. People click on the dock icon and ... nothing seems to happen.

    8. Re:it's not all roses by g4dget · · Score: 2
      A little knowledge is a dangerous thing. All things being equal, putting targets at the edge of the screen is good. But all things are not equal. When I work in a window on the top, right hand side of my 23" screen, aiming the mouse for a menu at the top left hand side of the screen gives me a tiny target--this is not faster than putting the menu at the top of the window. Putting menus at the top of the screen was a good choice for the original Mac. It's a stupid choice for the huge, high resolution screens we have today.

      In fact, if speed mattered that much, the best thing to use would menus, preferably pie menus that pop up under the mouse. This is the way that GUIs were going before Apple came along. But Apple, in their infinite wisdom, popularized menu bars.

    9. Re:it's not all roses by g4dget · · Score: 2
      Much better to have to click Next fifteen times.

      No, it's much better not to have to worry about upgrading individual software packages manually at all. But Macintosh is almost as primitive as Windows when it comes to software installation: on Windows, you fiddle around with installer dialog boxes, on Macintosh, you muck around in the file system. Come on, move into the 21st century.

    10. Re:it's not all roses by zephc · · Score: 2

      "I never understood why toolkits became so enamored with gray"

      Try looking at a monitor for 8 hours with all your widgets BRIGHT GREEN or NEON PINK. Gray is easiest to look at for long periods of time.

      The subtle white and gray stripe thing that OS X has going on is also very easy to look at for hours on end, not too dull yet not too bright like all-white would be (make sure your monitor's brightness and contrast are adjusted right too... use the Colorsync stuff to get it right).

      (BTW, I have my widgets using the Silver scheme rather than the default Aqua one.)

      --
      "I would say that 99 per cent of what my father has written about his own life is false." - L. Ron Hubbard Jr.
    11. Re:it's not all roses by DCMonkey · · Score: 1

      Yup. iTunes and a couple of other bundled apps don't do this either.

      --
      DCMonkey
    12. Re:it's not all roses by DCMonkey · · Score: 1

      Why doesn't Apple put the apple menu all the way in the right hand corner (it is a few pixels away)? In Classic MacOS the right hand app menu was also a few pixels away from the corner.

      According to Fitts's Law, corners are even better than edges (the current mouse position being best ie: right click).

      Yep. The Start menu is now faster to access, unless you stretch your taskbar to two rows :)

      --
      DCMonkey
    13. Re:it's not all roses by CaptnMArk · · Score: 1

      Yes.

      But on modern systems with large screens it is way too far away from the application windows (I hope you don't run everything maximized like most windows users do when force fed with MDI).

      The correct solution is to use the context menu for most operations and possibly do away with menu bar altogether. The space is better used for taskbar/dock anyway.

    14. Re:it's not all roses by CaptnMArk · · Score: 1

      Seconded.

      Installation simply by copying/unpacking is the best one possible. Much better than the InstallShi?^Held and the like.

      The problem with install programs is that they require interaction and the user doesn't know what they will do.

      RPMs are better in this respect, but could be significantly improved by removing the capability to run post/pre scripts.

      (various registrations need to be done by code already instaled on the system by the detecting the type of package being installed...)

    15. Re:it's not all roses by Dixie_Flatline · · Score: 2

      It would be interesting to do some tests, but I wager that the menu being at the top of the screen is STILL faster than the menu at the top of the window. I have a dual monitor setup on my Linux box here, and both monitors are running at 1280x1024. From the middle of my browser window, which is on monitor 2, it doesn't seem any slower (though subjective measurement is a lousy metric...) to get to the top left of monitor 1 than it is to get to the 'File' menu and click it. However, since Fitts' law is still pretty accurate, even when doing back of the envelope calculations, I'll get back to you with exact (theoretical) times in the next couple of days. :)

      As for pie menus, I think you're right, and I think that the idea of dropping the menubar all together is a good one.

    16. Re:it's not all roses by aafiske · · Score: 1

      "The single menu bar is a pain on large screens. Worse, it is confusing to many users: when they start an application, they expect an application to appear, not just some subtle change in the appearance of the menubar."

      The benefit of a single, at-the-top-of-the screen menubar is that it provides a target for the user of infinite height. In windows, when I want to hit an item on the menu bar, I have to aim for a very small target (depending on my resolution). On any mac, when I aim for a menu bar I only have to aim in one direction, horizontally. It increases speed. See Fitt's Law, http://ei.cs.vt.edu/~cs5724/g1/

      Once you're used to there being one menubar as opposed to many (which is just a matter of what you've been trained on), it's much quicker to use menus.

      Think of it this way, a user opens an application, and then says 'where's the menu bar'... what's the answer? 'the top of the screen'. It's a pretty quick lesson to learn, because the answer is always the same.

    17. Re:it's not all roses by g4dget · · Score: 2
      Well, whether it's faster or not is an experimental question. For me, I'm pretty certain it's not faster because I can't move across the whole screen with a single sweep of the mouse. Keep in mind, too, that if the mouse is to the far right of a menu entry, the target represented by that menu is very small (as viewed from the mouse position).

      Also, one has to be careful interpreting such data. Let's say, for the sake of argument, that hitting the Mac-style menu is still faster even on a large screen, at least for people with their mice adjusted in a certain way. You still have extra eye movements and head movements and a shift of attention when you try to find the menu and when you try to get back to your application. The overall action may still be slower, or it may be more disruptive to one's work, even if just the act of activating the menu is faster.

    18. Re:it's not all roses by Dragonmaster+Lou · · Score: 1

      Actually, I wish Apple or someone else would come up with a hack to allow you to bring the main menu to the mouse pointer, kinda like NextStep (which I believe used a 3 button mouse -- one was the primary, one was the context menu button, and one would pop the main menu up at your mouse pointer),

    19. Re:it's not all roses by jafac · · Score: 2

      You don't have to. Just drag the new version to you Applications folder, and you'll get a dialog box asking if you want to replace the old version. Click Yes, and you're done.

      That's nice until you've got around 30 or so apps installed (including your classic apps, games, all the zillions of little shareware apps) - and then you start wondering about installing programs into a hierarchy under /Applications. Then you're right back to fishing around for the icon.

      What would be nice is if the app folder standard was extended to register the application into a database on it's first run (same way they do licensing, etc). Okay, not a database, maybe a part of Netinfo? Or how about a text file? Whatever - as long as it's a single, central list of all apps installed - and then put a GUI front end on it to install/uninstall/upgrade/repair/reinitialize apps. The best of both worlds.

      The great thing about app folders is that you can simply delete the icon, and you've deleted all the zillions of files the app had on your system. You move it to another folder with a simple drag and drop - no hacking around required. Next time you run it, it checks to see if it's located in it's install folder recorded in it's prefs file, and if not, it updates the app list.

      --

      These are my friends, See how they glisten. See this one shine, how he smiles in the light.
    20. Re:it's not all roses by Anonymous Coward · · Score: 1, Interesting

      It's not just about the menu (or whatever) target. Anyone can whip their pointing device across 3 screens to get to the top left corner. And it'll probably be faster than going to a File menu a few pixels away. However. (And Fitt's Law afficionados always miss this point.) After you're done clicking in your little top left corner menu, you now have to go back to your application, usually right where you left off. I'm willing to bet the (on average) longer distance from top left to the application more than makes up for the initial advantage.

      When working in an application, your mouse will be somewhere near the top of the document, near to where the menu bar and toolbars are. The File menu is a couple pixels away. When you're done in the menu, going back to work is only a couple pixels away again.

    21. Re:it's not all roses by jafac · · Score: 2

      I can't move across the whole screen with a single sweep of the mouse. Then you need to adjust your mouse acceleration settings.

      --

      These are my friends, See how they glisten. See this one shine, how he smiles in the light.
    22. Re:it's not all roses by pi+radians · · Score: 2

      iTunes and a couple of other bundled apps don't do this either.

      really? lemme test that out.

      open iTunes
      Apple-1 (which closes the player but keeps the program running.)
      switch to the finder
      click one the iTunes icon in the dock
      and... TADA! look, a brand new player, all ready to be used.

      Mozilla doen't do it because they don't follow guidelines. every Apple app does.

      --

      sin(6cos(r)+5A)
    23. Re:it's not all roses by scrutty · · Score: 1

      Project Builder doesn't.

      --
      -- Oh Well
    24. Re:it's not all roses by g4dget · · Score: 2

      If I did that, fine positioning would go out the window. You have to face the fact that human hands are only capable of so much range and so much precision--no mouse setting can get around that.

  114. Die MDI Die! by fm6 · · Score: 2
    The MDI tendency directly contradicts Mac OS X, in which windows are document-centric rather than application-centric. No parent application "main window" exists--the menubar and other interface elements, like palettes, are used to constantly indicate which application is active. Document windows are only constrained by the user's desktop size (which might span single screen or multiple monitors).
    That's sort of incorrect. GUI windows are fundamentally document-oriented, and unless you're stuck in a DOS mind set, application-oriented windows don't make a lot of sense. Yeah I know, a lot of you prefer them. I'll bet you use the command line a lot also!

    Anyway, MDI adds a second level of navigation that's a pain to deal with, even if the app has a clean doc-window navigator -- and most MDI apps don't. I've always hated it. I guess I'm not alone, because fewer and fewer apps use MDI. Even MS Word and Excel no longer use it by default.

  115. Re:Some good points (white too white) by Anonymous Coward · · Score: 1, Interesting
    http://www.eink.com/ has some interesting stuff going on.

    Reflective displays are already being used in some handheld computers, so I expect to see full-size reflective monitors on the market in the next few years. I can't wait!

    Things that web designers don't realize about why books are easy on the eyes and web pages aren't:

    1. the book is not beaming light directly at your eyes; it is reflecting and partly diffusing light from another source; our eyes are better adapted to dealing with this kind of stimulation;
    2. a "reading light" is typically an incandescent or halogen lamp that produces more "warm", sun-like colors, which our eyes are better adepted to processing;
    3. the paper in a book is not 100% solid untextured white; it is off-white, often very subtly textured, and partially translucent
    4. the ink on a page is not 100% black; it is almost always a dark grey


    Until reflective displays are common, #1 can't be considered a factor in web design. But #2 you can take into account to some degree by simulating "warmth" in the color choices for your text and backgrounds. I wouldn't worry too much about texture because it's difficult to simulate texture subtly and with fine enough resolution.

    #3 and #4 can be taken into account in your color choices to reduce the contrast just enough to keep the photon beams from burning up people's retinas.

    It should also be noted that most people have their monitor's brightness cranked way up, such that they can't ever see true black, so I don't worry so much about lightening up dark text.
  116. Re:Doesn't acknowlege Windows' keyboard superiorit by RickHunter · · Score: 2

    Oh, excellent. Can't wait for KDE 3.1, then!

    Thanks for the tip, BTW... Do you happen to know if KDE 3.0 lets you do this too, or is it a new 3.1 feature?

  117. Re:Right Click (right click works) by Etcetera · · Score: 2


    I can't back this up or anything, but from working in a university computer lab for a year or two I've noticed that many Mac users -do- routinely have one hand on the keyboard and the other hand on the mouse. Combined with the ease of Command-(key) combinations, I've generally seen those users perform tasks quicker than those using keyboard-only or mouse-only methods.

    Also, anecdotally, ask any first-person shooter gamer what the best interface is and most will say that keyb+mouse is the most efficient.

    YMMV...

  118. Re:Right Click (right click works) by sessamoid · · Score: 2
    Also, anecdotally, ask any first-person shooter gamer what the best interface is and most will say that keyb+mouse is the most efficient.
    Yes, but any fps gamer (and I'm pretty avid an fps gamer) will tell you that the optimal interface is keyboard and MULTIBUTTON mouse. It's also the faster for regular OS navigation.
    --
    "No, no, no. Don't tug on that. You never know what it might be attached to."
  119. Re:Doesn't acknowlege Windows' keyboard superiorit by cpt+kangarooski · · Score: 2

    They didn't use enter or return for, as far as I can tell, two reasons.

    First, within any app other than the Finder, you'd still likely have to use Cmd-O for open. It's pretty nonsensical to imagine hitting the Return key in Word and getting an Open dialog. Thus, consistancy demands that the one app people will ALL use a lot not be dramatically different from ALL other apps.

    Second, when you're renaming an icon in the Finder, you signify that you're done by hitting Return. (there is no rename dialog -- it's all inline) Since modality is not exactly looked upon favorably -- though sometimes tolerated -- on the Mac, it makes sense for Enter in the Finder to mean "toggle the renaming function" rather than "stop the renaming function" with some other key meaning only to start it.

    As for the general worth of keyboard navigation, I suggest you have someone actually time you with a stopwatch using the keyboard, and again while using the mouse. Apple did this and to their surprise, the Mouse was often objectively faster, contrary to the subjective experience of the people being tested. This doesn't ALWAYS hold true, but it is apparently common enough.

    Don't believe it: then give the experiment a try. There's no other way to be sure, when your personal experience is called into doubt.

    --
    -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
  120. Re:Doesn't acknowlege Windows' keyboard superiorit by Have+Blue · · Score: 2

    Damn right you haven't used a Mac in 5 years. Find an OS X box, go into Preferences, Keyboard section, and turn on Full Keyboard Access. You can now manipulate all standard interface elements with the keyboard. Admittedly this feature is not perfect and doesn't work everywhere (try it out in the Preferences app itself if nowhere else), but it's a hell of a lot closer to what you describe than OS 9 ever was.

  121. "Use a single menubar" - look at the example by Animats · · Score: 3, Interesting
    The illustration for "Use a Single Menubar" has Internet Exploder for Mac on the desktop, showing two menubars in its own window, a set of tabs at the left, and displaying an Apple page with two more levels of menu bars. That's funny.

    The example also shows Itunes on the desktop. Although it's not on top, it's not visually obvious that it's currently in background. Itunes clearly follows the convention that "Entertainment Apps Don't Use the Standard GUI but instead Look Like Consumer Electronics Products."

    1. Re:"Use a single menubar" - look at the example by Hal-9001 · · Score: 1

      Technically, the menubar is the the UI element at the top of the screenshot with all the drop-down menus, and the other UI elements you are referring to are toolbars. So there is only a single menubar, but there is a ton of UI cruft as well.

      Admittedly, that screenshot is an example of many bad UI practices...

      --
      "It take 9 months to bear a child, no matter how many women you assign to the job."
    2. Re:"Use a single menubar" - look at the example by banal+avenger · · Score: 1

      "showing two menubars in its own window, a set of tabs at the left, and displaying an Apple page with two more levels of menu bars."

      I only see one menu bar. It's at the top of the screen. And, aside from the fact that the UI of a web page is irrelevant to the UI of an OS, those are center-justified TABS at the top of the Apple page.

    3. Re:"Use a single menubar" - look at the example by Animats · · Score: 2
      Yeah.

      The web page shown is "apple.com", which has a tab bar as its highest level. Below the tab bar is what looks like a menu bar, with no boundaries between the text items. But it doesn't actually have drop-down menus or rollovers; it's just a button bar. Tacky.

      Apple also seems to have crudded up the IE window with yet another built-in button bar, with buttons labelled "Apple", "Apple Support", "Apple Store", etc. Again, tacky.

      Down at the bottom of the screen, we have icons for applications: the Funny Blue Thing, the Funny Green Thing, and the Funny Orange Thing.

      Apple needs Susan Kare, and her minimalism, back.

    4. Re:"Use a single menubar" - look at the example by cygnusx · · Score: 1
      The illustration for "Use a Single Menubar" has Internet Exploder for Mac on the desktop, showing two menubars in its own window, a set of tabs at the left, and displaying an Apple page with two more levels of menu bars.


      The set of tabs on the left are a standard IE feature called "explorer bars", like Moz's sidebar.

      There is no menubar on that IE window, there's a Mosaic-style toolbar and a bar full of links, like Moz's or Opera 6's personal toolbar.
    5. Re:"Use a single menubar" - look at the example by Anonymous Coward · · Score: 0

      The funny Blue/Orange/Green thing seems to spell out "WXP".

    6. Re:"Use a single menubar" - look at the example by Slur · · Score: 2

      The illustration for "Use a Single Menubar" has Internet Exploder for Mac on the desktop, showing two menubars in its own window, a set of tabs at the left, and displaying an Apple page with two more levels of menu bars. That's funny.

      None of the items you describe are "menu bars." They are all horizontally-arrayed buttons. Agreed, it takes awhile for newbies to distinguish images in web pages from UI elements, but they'll never be confused as to where the "real" menu bar is. It's ALWAYS at the top. It's always at the top with NOTHING OVERLAPPING IT. Which app is current? ALWAYS look at the top left corner for the answer.

      Apple has demonstrated a remarkably intelligent consistency in all their OS incarnations. And to be frank, I find nothing inconsistent about the iApps. They are visually funky, but so very simple to understand with a quick glance.

      --
      -- thinkyhead software and media
  122. Supported, not used. by fm6 · · Score: 2
    In Windows you can do everything except specific drawing tasks without having a mouse.
    Well, in theory, that's true. But how well implemented is this in fact? Most apps I use just don't provide keyboard shortcuts for all their actions. Or else, like Frame, they're complicated, obscure, and don't follow Windows GUI guidelines.

    And even when there is adequate hot key support, it can be a pain to use. Ever try to use a web browser without a mouse? In theory, it's quite simple -- a web browser doesn't have that many actions, and all the browsers I've seen provide hot keys for every possible action. But many are context-dependent. You can't, for example use arrow keys to scroll the text unless the doc subwindow has the focus. And be careful not to use Backspace unless you're editing text, or really want to go back to previous page!

    Bottom line: you can have proper keyboard support on any platform provided your app designer (including web page designers) are willing to sit down and think the problem through. Unfortunately, most aren't.

  123. I would like to read that article, but.... by Anonymous Coward · · Score: 0

    I still can't access the article. Does anyone know or setup a mirror... it's been slashdotted to death...

  124. They're grown-ups by Anonymous Coward · · Score: 0

    They're just narrow grown-ups.

  125. settings - mouse - tracking speed by Arker · · Score: 2

    You just need to increase the tracking speed a little. Once the mouse is properly calibrated it's the easiest thing in the world, a quick flick of the wrist takes you to the menu every time, and you never overshoot and have to back down slowly to hit the menu.

    Seriously, give it a try, once you get used to it it's hard to go back.

    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
  126. Ellen Feiss' interface made me switch by Anonymous Coward · · Score: 0

    Damn man, she's hot, and she's a stoner too! How can you go wrong with that? I got me a mac and I love it! 420 DUDES!!

    1. Re:Ellen Feiss' interface made me switch by Anonymous Coward · · Score: 0

      Looks like Goatse likes Apple, too.

      -- The WIPO Troll. No, seriously.

  127. You haven't seen LaunchBar, Have you? by tres · · Score: 1
    LaunchBar takes keyboard support to a whole new level.

    You can't do anything like this in the windows UI. And although windows keyboard shortcuts will give you the ability to arrow your way through the start-menu, just use LaunchBar once, and you'll see that Windows' solution was good in Windows 3.0, but not anymore.

    Granted, Microsoft has done some awesome things with keyboard support (I love context-sensitive help). And you're right, in OS X, some program menu tasks I can't do any other way but a mouse. But when it comes to typing Alt+F and arrowing my way through the menus, it's really not getting me any improvement in speed or functionality. I don't miss it at all.
    If we're talking about OS X, I think its a moot point--I can close dialog boxes from the keyboard. I can rename files in the Finder from the keyboard by simply hitting RETURN (try doing that in Windows Explorer). And I can open any application or document on my system simply by holding down Apple+spacebar and typing in the first couple letters in its name.

    LaunchBar is truly the most innovative program I have had the pleasure to work with for years. It brings the speed of the shell into the GUI. And like tab completion in the shell, once you have it, you never want to go back.

    --
    Notes From Under *nix: blas.phemo.us
  128. Re:Doesn't acknowlege Windows' keyboard superiorit by Durindana · · Score: 1

    It doesn't "acknowledge" this because it's not true. As you say, your Mac OS knowledge is way behind the times. Mac OS X has better keyboard support than Windows, any version - and better than an *nixes, too. OS 9 and previous versions were lacking in this regard, but at this point it's a non-issue.

    Take-away: don't criticize features you've got no familiarity with.

  129. It was like... by Anonymous Coward · · Score: 0

    Beep! Beep! Beep! Beep! Beep! Beep! and then, like, half of my paper was gone!

  130. reminder by skydude_20 · · Score: 3, Informative

    i'm sure they're just reminding everyone that windows copied apple, not the other way around. hopefully they hide that information about the XEROX GUI

    --
    Jesus saves souls and redeems them for valuable cash prizes
    1. Re:reminder by foo12 · · Score: 1

      Apple bought the rights to the XEROX GUI, not stole it. I can't find the link at the moment, but after the TNT Apple/Microsoft made-for-tv movie, Woz posted a FAQ on his site. In it, he commented that the GUI was bought/licensed from XEROX in exchange for a hefty amount of stock.

    2. Re:reminder by rjung2k · · Score: 1

      I believe Xerox eventually sold their shares and received a huge profit, too.

  131. Re:iYawn -- Tweaking Wastes My Time by reallocate · · Score: 2

    Ya know, some of us are using a Mac, regardless of gender, because we've grown tired of all that tweaking you find so bloody interesting. If interesting means it doesn't work out of the box, requires hours of setup, and is still a pain to use, well then, I guess I'm getting boring myself. I did it for years with Linux. What do I have to show for it? Nothing. It was a complete waste of my time.

    For me, OS X is good because I can use the traditional Unix tools I'm comfortable with, without having to put up with the half-baked semi-pro attempts at interface design pawned off by the open source community. I've got better things to do than trying to massage KDE or Gnome or whatever into something that doesn't annoy me. Maybe someday they will be up to par, but I don't want to wait.

    So, obviously, I don't care if Macs aren't as "tweakable" as PC's. That's a good thing. It means I found something I can use without wasting time. If the ever-so-strident open source crowd had managed to market a Linux-based PC with similar attributes, I might have purchased it, instead. But, they won't do that because half of them are off building UI's and "themes" that look like a cross between a teen-ager's wet dream and rejects from Design 101. The other half are off whining, whimpering and worrying about preserving their so-called right to "share" music and movies with the entire planet.

    Nor are Macs "ridiculously expensive". More expensive than a $699 Dell or a $400 no-name white box? Sure. But some of us actually have an income and can make our own decisions. There is no "geek" market to speak of, so why should Apple care about Slashdotters whining about price? Every self-described Slashdot geek could disappear tomorrow with no impact on industry revenues.

    No one has to buy from Apple. If they want to tightly integrate hardware and software, that's their business, not your's. There's no reason why they should do anything different.

    As for why Slashdot is posting Apple stories, perhaps it has something to do with attracting readers who actually have some discretionary income to spend. I'm sure their advertisers would appreciate that.

    --
    -- Slashdot: When Public Access TV Says "No"
  132. Oh for Pete's sake! by mtec · · Score: 1

    Then click the disk and tap command-e

    that stands for 'eject'

    --
    Cake or Death? Cake Please!
    1. Re:Oh for Pete's sake! by Anonymous Coward · · Score: 0

      You're ignoring the most obvious of all...

      The eject button on the CD-ROM itself.

      Oh wait...Mac's don't have that because (a) It allows apple to put in "special" (read "expensive") hardware for no good reason (b) it makes it seem more elegant when actually its mostly a pain in the ass.

      But Mac people will justify any nuttiness by apple. If Steve jobs was killing babies with a pitchfork, mac fanatics would calmly explain this was really the most rational way to do things.

    2. Re:Oh for Pete's sake! by MoneyT · · Score: 2

      You can put whatever fucking drive you want in your mac. Period. The onyl difference is, the eject button will not work to remove a disk. Why? Because unlike windows, Mac OS automaticaly mounts a disk when you put it in. ANd in order to eject a disk, you need to un mount it. It doesn't become un mounted just because you closed the window. So go buy your nice cheap hAcme Drive and put it in your mac. It will work. Have fun.

      --
      T Money
      World Domination with a plastic spoon since 1984
    3. Re:Oh for Pete's sake! by mtec · · Score: 1

      I mentioned that in my post (dickhead)

      --
      Cake or Death? Cake Please!
  133. All your typo are belong to us by drinkypoo · · Score: 2, Offtopic
    From the article:

    Avoid directly transferring your application and document, palette, and toolbar icons to your Mac OS X application. Such icons are inconsistent with the high-quality appearance of icons in Mac OS X; users will consider you application to be unprofessional or unfinished. Design carefully and take pride in your application's icons: In Mac OS X, icons are a critical part of your application's brand.

    Someone should tell apple that when you insert "you" instead of "your" in a document, it appears to be unprofessional or unfinished.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  134. Re:Doesn't acknowlege Windows' keyboard superiorit by speleo · · Score: 1

    Using Autocad I can actually do some drawing tasks without a mouse using keyboard coordinate entry.


    That's an AutoCAD feature--not a Windows feature. You could do the same thing with AutoCAD for the Mac (when it still existed).
  135. so to eject by mtec · · Score: 1

    *command-e *drag to the trash (which morphs to an eject symbol) *hold down f12 for a sec. *open the terminal and use unmount ...and that's not enough? Is there no pleasing people? that said, I wish we could press the little button on the front of the drive...

    --
    Cake or Death? Cake Please!
  136. So to eject (sorry for the line break problem) by mtec · · Score: 1

    *command-e
    *drag to the trash (which morphs to an eject symbol)
    *hold down f12 for a sec.
    *open the terminal and use unmount ...and that's not enough? Is there no pleasing people?

    that said, I wish we could press the little button on the front of the drive...

    --
    Cake or Death? Cake Please!
    1. Re:So to eject (sorry for the line break problem) by Anonymous Coward · · Score: 0

      Well, if you could just press the little button on the front of the drive, that would forcibly unmount the CD, and in any good operating system that has taken a quick thought to that, would note that removing hardware before properly unmounting it, could mean data loss. So, to make sure that users don't unmount a volume in use, you make ejecting a disc a known process. And you avoid all of the old dos junk whereupon you ejected the floppy, or CD and your Micro$oft system gives you a nice big fat bluescreen when it can't find the proper disc.

  137. Re:Doesn't acknowlege Windows' keyboard superiorit by hacker · · Score: 3, Informative
    The single best way to fix this stupid problem is for keyboard shortcuts to be automated but overrideable in GUI toolkits. When I write a menu item, it should scan the entire list of menu items, and generate keyboard mnemonics for everything.

    How old is your Linux box? I've been able to just hit the key I want for whatever menu shortcut I want for several years now, out of the box.

    Humor me, try this:

    1. Launch any gtk+ application, like say...gimp.
    2. Now, open the File menu with your mouse, or Alt-F.
    3. At the top, you'll see 'New'. Highlight it with your mouse, but don't click it.
    4. Hit Backspace.
    5. Now hit Ctrl-N
    6. Now hit Backspace
    7. Now hit Ctrl-Alt-Shift-N.

    See? You can assign and remove any meny accellerator you wish, in any application (that supports it of course, like stock gtk+ applications, XUL code (i.e. Mozilla, Galeon), and so on.

    Your FUD doesn't help the cause.

  138. Re:Doesn't acknowlege Windows' keyboard superiorit by Sits · · Score: 1

    Funny you should mention this. One of the critcisms that was levelled at Windows (it must have been ealier versions such as 3.0) by some user interface experts was that it essentially a keyboard driven interface with mouse support bolted on. However I've seen one of my friends using just the keyboard under Windows and he is far faster than me using both the keyboard and the mouse.

    It is good to see open source desktops such as GNOME 2 starting to get improved (and consistent) keyboard navigation.

  139. Re:Point 9... by MoneyT · · Score: 2

    It's all about being user friendly. If you've never used a computer before, or are just starting out, a single button mouse is worlds easier. Apple relies on the idea that if you are accustomed to having a 2 or more button mouse, you already own one and therefore it is not nessesary to include one.

    --
    T Money
    World Domination with a plastic spoon since 1984
  140. They need to come up with better reasons than that by Anonymous Coward · · Score: 0

    They need to come up with better reasons than that. I've never had any trouble with MDI and I really don't have any use for artsy icons. As for keyboard shortcuts there are plenty of them in Windows.

  141. All UIs Are Stupid by gilgongo · · Score: 1

    >No one has a problem with the dock unless they
    >are already thoroughly entrenched in some other
    >mechanism.

    Bingo. You've inadvertently hit the nail on the had when it comes to the UI wars.

    Consider the following:

    All human-computer interfaces are awful. NONE OF THEM ARE ANY GOOD. You have to learn how to use them, you have to remember what things do, what order to do them in and be able to predict how they will function under different circumstances.

    So what do humans do? They learn them, and become familiar with them to the point that they convince themselves that they are not only the best way of interacting with computers, they're the only way. Typical. Humans are very stupid.

    I personally think that the QUERTY keyboard layout is the "best" one because I'm stupid. I think that a CLUI it the "best" way of interacting with a server OS because I'm stupid.

    But I don't force this down people's throats because I know that both systems are fundamentally stupid, and I'm tooo stupid to think up anything better.

    However, they work fine for me and I can use them to get things done.

    Mac? Windows? Gnome? OS/2? Next?

    Here's the punchline:

    IT DOESN'T MATTER! USE WHAT YOU LIKE! YOU'RE STILL GOING TO GET THE JOB DONE STUPID!

    --
    "And the meaning of words; when they cease to function; when will it start worrying you?"
    1. Re:All UIs Are Stupid by willis · · Score: 1
      I personally think that the QUERTY keyboard layout is the "best" one because I'm stupid. I think that a CLUI it the "best" way of interacting with a server OS because I'm stupid.

      QUERTY? Damn, that's a new one. I use QWERTY. Funny how you can have a spelling error on something that should be as simple as looking at the keys. Out of curiousity, did you type this on a QWERTY keyboard?

      --

      there is no thing
      what else could you want?
    2. Re:All UIs Are Stupid by gilgongo · · Score: 1

      QUERTY is the phonetic spelling of QWERTY. The latter is the keyboard layout itself, the former is how you spell it. In English, you can't pronounce QWERTY (kiew-wuh-erty?) so we have to spell it phonetically.

      I don't make up the rules, I'm stupid, remember?

      JJ

      --
      "And the meaning of words; when they cease to function; when will it start worrying you?"
  142. Other than Excel - what apps use MDI now though? by gilgongo · · Score: 1

    It says "Microsoft Windows-based applications often implement a Multiple Document Interface (MDI),... " As far as I can tell, very few Windows apps use MDI - at least under Win2K/XP. Only Excel does as far as I know. Word doesn't, MSIE doesn't, dunno how you'd class Outlook or Explorer (not document oriented at all probably).

    --
    "And the meaning of words; when they cease to function; when will it start worrying you?"
  143. Re:Doesn't acknowlege Windows' keyboard superiorit by Teancom · · Score: 1

    (since I'm running 3.0.3 and don't have that) it seems to be 3.1 only.

  144. Re:Doesn't acknowlege Windows' keyboard superiorit by usr122122121 · · Score: 3, Informative
    Have you checked out the Universal Access section of System Preferences in 10.2?

    With those options turned on you can do everything you want without needing a mouse.

    --

    -braxton
  145. the Dock by tgibbs · · Score: 2

    I still can't stand the default position of the dock at the bottom of the screen. It doesn't go well with windws that resize from the bottom-right corner, or with horizontal scroll bars.

    But I understand why Apple put it there. Windows has a lot of people conditioned to look to the bottom of the screen for an application menu/launcher. Similarly, the great big icons make it hard to miss for the new user.

    Fortunately, they also included a lot of customization. I am much more comfortable with the dock since I stuck it to the right side of my screen, reduced its size way down, and turned the magnification down. And to my suprise, I find that those high-res icons still look good, and remain recognizable when reduced to the same size as the old small icons.

  146. Re:You guys really eat Apples PR up. Mindless shee by Golias · · Score: 2
    Unfortunately, a LOT of very common programs failed to conform to this guideline. Even Microsofts IE 5.2, which Apple still includes as a default browser, maximizes behind the dock... and Microsoft has a $10 Million Apple-software-only development house set up less than an hour's drive from One Infinite Loop. If they can't even remember to get it right, how often can we expect other companies to do so.

    Perhaps the Apple GUI tools should be set up with defualts to force this behavior, unless the developer deliberately breaks it.

    --

    Information wants to be anthropomorphized.

  147. Re:You guys really eat Apples PR up. Mindless shee by MoneyT · · Score: 2

    I remember using the built in file deletion features of Microsoft Word to delete the "At Ease" preference file , thus exorcising the broken interface from the computer. Ah memories...

    Now why did you bother doing that? You should have done what I did, and built up trust with the teachers. After helping fix a dead file, convert PC to Mac and back again and remove a broken floppy 4 or 5 times, the librarians just gave me the administation passwords to do as I pleased, so that I could work with my programs and with others without calling them over to remove a lock.

    --
    T Money
    World Domination with a plastic spoon since 1984
  148. Re:Right Click (right click works) by Bobartig · · Score: 1

    How many PC's come with a 5-button optical mouse? I always have to buy a new mouse anyways..

    What it really comes down to is choice and preference. At least Apple designed an OS that is fully operational using a single button interface -or- a 9-button Tri optical, force feedback, Microsoft H@x02 Explorer.

    There are plenty of computer users out there who are virtually computer illiterate (my parents included), and it's taken them YEARS of hand holding to get them to use multibutton mice correctly. Strangely enough, both my parents are multiplatform*, but they both have shiny macs at their respective work places.

    * They both use a PC for stock/investor related stuff. Mac support is horrific in that venue. Apple's own employee stock purchase plan is run by E-TRADE, which have no mac support *boggle*

    --
    This is where I get my recommended daily allowance of "Foot in Mouth."
  149. That's where the swing rocks under Java ;-) by Anonymous Coward · · Score: 0

    By having a clean fast and lookalike Look And feel the OSX Java2 version of swing make people think they are running native applications ;-)

    After all, who cares as long as it runs like a charm :o)

    People having the OSX should also enjoy having a webstart complient OS and launch cool webstart application within a single click.

    For examples, go and see http://www.up2go.net

    Anyway, the Aqua look rocks!

    -R4D4-R

  150. An autosizing dialog box is what you want by Dragonfly · · Score: 1

    It will always be as small as is possibly can, which sounds like what you want.

  151. Re:Doesn't acknowlege Windows' keyboard superiorit by Anonymous Coward · · Score: 0

    Quit smoking crack. Yeah, Alt-F4 is so much better than Apple-W because you should have to move your hands around more. Seriously, I can do just about everything with the keyboard on both a Mac (9 and X) and a Windows machine. I think you have never used a Mac long enough to learn the shortcuts. The shortcuts in both Windows and Mac OS are sufficent for 99% of tasks. If anything, Mac OS is slightly easier. Just because you are too lazy to learn shortcuts on a Mac doesn't mean the rest of us are. Bah.

  152. So, does it go well with your curtains? by Anonymous Coward · · Score: 0

    So you would say that someone who likes to make their own furniture (or their own fishtank, or design and build their own home) are "wasting their time"...? You probably never played with Lego.

    I have a dual Athlon MP (assembled by me, with parts that I picked) with Windows 2000 (also installed by me, as well as all the rest of the software I use). And guess what, it works. It worked right out of the box(en). The "tweaking" part is about getting the most out of it (or picking the parts that you feel are best suited to you), not making it work. PCs have worked "out of the box" for years now. In fact, when you compare Windows 2000 (or XP) with OSX, it's pretty clear which one has more compatibility problems (need I say "printing"...?).

    Of course, not everyone enjoys fiddling around with memory timing and comparing features on motherboards. I do. On the other hand, I don't understand how some people spend days tuning their cars or breeding pigeons. But I don't feel superior to them.

    As I said, I think Macs would be great home / office computers (places where you don't need a terribly fast CPU or a terribly fast graphics card) for people who don't know how computers work and who don't really care. But for most people in the world even the cheapest Windows PC is a very expensive thing. Macs aren't even an option.

    The problem is Apple isn't selling computers; they're selling an image. Do you think people would buy as many Levi's if they cost exactly the same as the other brands? Then they'd see that all jeans are basically the same. No... when you buy a Mac you pay more so you can say you have a more expensive computer. Apple is selling the illusion of something better, when in fact they're selling you something that isn't even all that different (is Word on the Mac any different from Word on Windows? is Photoshop on the Mac any different from Photoshop on Windows?).

    You like your Mac, great. But do you, as a Mac user, find these Slashdot articles the least bit interesting? I don't think so.

    1. Re:So, does it go well with your curtains? by reallocate · · Score: 2

      Not saying it's a waste of your time at all. Some people enjoy "tweaking" their car, other people just want to drive.

      I don't use Office or Photoshop, games bore me, and I could care less about downloading music and movies to my machine. (Boring junk stays boring junk after you download it.)

      For several years, I ran machines with Linux and its brethern as well as Windows. Linux was/is fascinating, but one day I realized that most of my time on the machine was devoted to constant adjustments and readjustments of something. Optimize this; download that; futz with libraries; compile this, then fix what broke.

      My frustration grew, and one day I just had enough. This was all input and no output. I wanted to stop playing with my car and just drive someplace.

      So I bought a Mac, something I wouldn't have considered prior to OSX and Aqua. First, I want access to Unix (that's why I used Linux in the first place; I've used MKS Toolkit on DOS and Windows for years), and second, because the quality of the image displayed on the screen is very important to me. (Perhaps more important than to most people; no Linux desktop -- even an antialiased KDE /Liquid setup -- ever pleased me.) Did I pay a premium for that? I suppose so, but that's OK. It's my choice.

      Like I said, if I get could what I want on a cheaper Intel box running Linux, I'd still be there.

      Is Apple selling a brand, an image? Sure. So is MS, IBM, Dell, Gateway, and all the rest. Even you local no-name beige box vendor can't avoid having an image.

      And, yes, I read Slashot daily, and have for a long time. What I don't understand is why Mac stories provoke reams of vitrolic posts by people who seem to think Apple is a direct threat to their personal wellbeing. Some people need to walk away from the keyboard and get a life.

      --
      -- Slashdot: When Public Access TV Says "No"
    2. Re:So, does it go well with your curtains? by Anonymous Coward · · Score: 0

      What I don't understand is why Mac stories provoke reams of vitrolic posts by people who seem to think Apple is a direct threat to their personal wellbeing.

      My point (as I think I have stated enough times already) is a) this is not "stuff that matters" (even to Mac users) and b) this is not "news for nerds" (because Macs aren't very popular with nerds, they're computers for normal people).

      They're just posting this because it's anti-Microsoft. In fact, some of the "anti-Microsoft community" is so obssessed with Microsoft they end up copying Windows instead of coming up with something that's actually better.

      There hasn't been any real innovation since Xerox PARC died. Apple used to copy their ideas and then Microsoft would copy Apple. Now MS and Apple (and Linux) are just copying eachother ad nauseum...

  153. One Reason To Rule Them All. by FIT_Entry1 · · Score: 1

    >> 7. Aqua Is In, Grey Is Out

    What other reason do you need?

  154. Re:Right Click (right click works) by Juggle · · Score: 1

    "Once you get used to it, Keyboard+Mouse control is actually a little faster than Multibutton-Mouse control."

    Tell that to my friend who has little to no control over his left hand.

    The whole idea of mixing inputs is revolting - mouse inputs should come from the mouse keyboard from the keyboard. It's HIGHLY unintuitive to have to mix the two.

    When I was taking a course in Director I'd occasionally let friends come use my decked out PC to work on their projects - once I showed them how to right click to bring up context menus most of them were hooked and started complaining about how the mac did it.

    And these were people who just about had to be bribed to touch a PC.

    --
    --- Juggle juggle@hitesman.com
  155. I'm flamebait? by MoneyT · · Score: 2

    But the parent post was informative? Right...

    --
    T Money
    World Domination with a plastic spoon since 1984
  156. The single menubar is more usable by Fitts' Law. by Ilan+Volow · · Score: 2


    The single menubar at the top of the screen is faster to access because of an ergonomic principle known as Fitts' Law, which states that the time to access a target is a function of the target's distance and size. A at the top menubar is infinitely large because there is no possible way to overshoot it vertically (i.e. you can slam the mouse up to the top of the screen really fast and don't have to correct for any vertical error because you're running into the top of the screen). On the Windows/GNOME/KDE interfaces it's possible to vertically overshoot the menubar, which makes that layout far less usable than the layout on a mac. For a more in-depth explanation of this phenomena, check out this article by UI guru Bruce Tognazinni.

    --
    Ergonomica Auctorita Illico!
  157. Re:Doesn't acknowlege Windows' keyboard superiorit by drsmithy · · Score: 1

    Well, I do have a lot of familiarity with OS X and it's keyboard support *sucks* compared to Windows .
    Apple do not believe in keyboardability, plain and simple. Support for using the keyboard in OS X is a crutch, not an integral and well thought out feature.

  158. Re:Doesn't acknowlege Windows' keyboard superiorit by Dixie_Flatline · · Score: 2

    My main problem with Windows keyboard acceleration is that it's often HARD to find out what you need to know. For instance, why isn't there a little thing beside the 'maximize' option in the Window menu? I don't know how to maximize my Window, and I really wish I did. :)

    So far, EMACS is the only thing that I find gets it right. Yes, yes...things are cryptic and a bit hard to learn, however, if you know the command, you can ask what key it's bound to. If you redefine a key, it shows up differently in the dropdown menus, and if you run a command with a keyboard shortcut without using the shortcut, the system will pop up a little message (in a non-modal fashion!) to tell you what the shortcut is so you know for next time.

    For most apps under Linux, though, I agree. There's really no good reason for it.

  159. Why is a second mouse button so wrong? by el_benito · · Score: 1

    Or even the mousewheel at that?

    I really can't understand why so many Mac users object to multi-button mice and the mousewheel, outside of dogmatism. I will concur that there is a limit past which increasing the # of buttons on a mouse generates convenience, but on the other hand, there are several perfectly valid logical flow for adding at least one extra button to the mouse.

    1. The minimum size of a mouse is decided by how much space you need to house the internal mechanisms. Yeah, lasers and balls need different amounts of space, and then there's a clicker on top of that.
    2. As an object of prelonged usage, a mouse must be ergonomically sensible. This means that the mouse must be able to support the weight that a person needs to exert on it in order to maintain comfortable position.
    3. This size device is going to fill up space under the fingers other than the index
    4. As proven by stimulation by SUV drivers, the middle finger is easily capable of comfortable independant movement.
    5. Putting another mouse button there would effectively double the number of commands possibly generated by that hand.

    So enough blowing smoke... just grow up and package a 2 button mouse with the Mac if you're interested in increasing effective usability... and throw in a mouse wheel, I'm addicted to mine

    --
    http://liquidben.com - Aspiring to an 'under construction' gif
    1. Re:Why is a second mouse button so wrong? by wilson_c · · Score: 1

      Both MacOS 9 and MacOS 10 have native support for multi-button mice and scroll wheels built-in. For better or worse, the designers at Apple have decided that the entire OS should be fully operable with only a single mouse button. This promotes a relative simplicity of design from a user's point of view.

      Having struggled time and again to explain to my father and grandfather what will appear in a context-sensitive menu (they understand the words, but it just doesn't click) I think Apple might be on to something.

      On the other hand, given that the OS and many of the applications are as fully aware of context sensitive menus as Windows, I find it surprising that Apple doesn't offer a multi-button mouse - or at least promote one - where appropriate. Editors are always stunned by how much easier their lives are after I've showed them Final Cut Pro with a right mouse button.

    2. Re:Why is a second mouse button so wrong? by gig · · Score: 2

      > I really can't understand why so many Mac users object to multi-button mice
      > and the mousewheel, outside of dogmatism.

      Remember that most Mac users have used Windows for real work, while most Windows users have not used a Mac at all. When you talk about dogma, we Mac users have seen more than our share of Windows users going through life the hard way ... come on.

      Apple's Pro Mouse doesn't have any buttons. It sits in your hand and you point and press either your whole hand or one finger, two fingers, whatever, and get a click. It becomes second nature.

      I don't have any research to support this, just my own experience, but it seems like the hand has enough brains to take on the simple function of pointing and clicking and that means your brain doesn't have to do that. If you overload the hand, though, with multiple controls, then the brain has to get more involved in mousing. So on a Mac you just think "point, click" and your hand does it very naturally, develops a habit of flicking the cursor up to the menus and such. With a two-button mouse, now you are working individual fingers, e.g. pointer finger on left button, index on right ... the mouse is not a part of your hand anymore like with a one-button mouse.

      Another point about the one-button mouse ... the fact that it is standard means that the computer itself and all Mac apps can be navigated with just one button. If you are on a desktop PC you say "so what?", but if you are using a stylus on a graphics tablet then you are happy to only have to press one button, if you are controlling the computer by voice or gesture (both built-into Mac OS X) then you are also going to gain from only NEEDING point and click. Touch screens, etc. So multiple buttons on a mouse is like a hack that won't scale, and MS Windows requires that second button for some stuff (amazing). On any other pointing device, the other buttons are even less useful and even more in the way. Most trackballs are nightmares of ergonomics just so they can fit a lot of buttons on there and convince somebody who spend $50 last year on a two-button trackball to spend $60 this year on a three-button trackball.

    3. Re:Why is a second mouse button so wrong? by gig · · Score: 2

      One additional point: I can teach almost anyone to play a hand drum musically in almost no time at all because we are used to moving our hands around to hit things. The hands already have the skill and you just have to teach the music. To learn to play the piano musically, though, the person will probably have to build up their finger dexterity quite a bit ... in other words, their hands need to be taught new skills as well as learning the music. The one-button mouse doesn't ask more from the user's dexterity than what most people have from their regular life skills.

      Think about other things you do with your hands and compare to a one-button slam and point mouse with no finger aiming or dexterity required at all, and to a three-button scroller mouse. Pick up a rock and throw it, write with a pencil, point and press with an Apple mouse. EVERYONE can do these things. What are the analogies for the three-button scroller mouse?

      Another point is that point-click-response is easy to see on a Mac. Go up to any Windows system and press the "wrong" mouse button for a task and see how confusing that could be to someone who doesn't have experience with it.

      Finally, Mac OS X has support for up to 32 mouse buttons, so go nuts at Fry's and use whatever you want. Context menus are pluggable, so if the one you want isn't there, make it yourself or get it from somebody else.

  160. Apple make great UI by ducker · · Score: 0, Flamebait

    NOT this is a pathetic artical and has no proof.. its laughable.

    Apple u are manipulative lieing bastards who screw over your own customers and they like it.

    If u invest in apple your dumb.
    If u buy an apple your stupid.
    If u think an Apple is better designed than windows your wrong.

    These werent points in that artical they were just as convincing as a 5 year old. Hope somebody believes it cause i dont.

    Cya Apple losers

  161. Re:The single menubar is more usable by Fitts' Law by amccall · · Score: 2
    I'm sorry.

    I've heard this argument so many times and it has merit, but at the same time its just not true. There is more to life than the amount of time it takes to click on an item that the MacOS single menu bar approach breaks:

    1. Graphical Organization. As was touched on by the parent post, the single menu bar design causes confusion when more than 1 application is running. Having 1 windows focused, when you are attempting to perform an action on another will result in that action being performed ON THE WRONG WINDOW. There is no way around this.

    2. Switching between application. If I'm working with an IE window, and then decide to save a file in another I first must focus the window I want to perform the action in, and then use the menu. I'm doing 2 things here, where as before I could just do one.

    I think it would be interesting though, to create a menu bar approach like the one in Windows, and then make life better according to the sacred Fitt's law by making the mouse accelerate slower over the menu (or even give force feedback) than the rest of the window. This might be disorienting at first, but after someone got used to it, I imagine it could speed things up even more than either the MacOS or Windows style alone.

    The fact that so many people find the single menu bar so annoying should tell you something. UI interface designers have become so high up in their towers they forget to listen to the people that will use it.

    --
    ------ 24.5% slashdot pure
  162. Rather be stuck with MS Windows than Mac hardware by stuartkahler · · Score: 1, Offtopic

    Why doesn't apple seem to understand what it will take to be a real player? They have the best OS, but their hardware is limited and grossly overpriced. After 20 years, they should realize that a great OS will only sell if it can be installed on the hardware of the user's choice. They would crush Microsoft within 5 years if they would port Mac OSX to Intel/AMD based hardware, sell copies of the OS at $50/ea, and help get software designers to include binaries for both OSes in every box they sell.
    Apple is killing themselves by getting entrenched in the hardware side of the market when they should be focused on putting high markup CDroms onto store shelves. Steve Jobs' goal should be to see every x86 based PC sold 'naked', and for people to purchase the OS of their choice to install on it. Apple can go on selling upscale PCs with built in flat screens and dual-processors to yuppies and professionals with 'special needs', but most people just need a cheap PC that is easy to get online with and type papers.
    Apple needs a clue.

  163. Apple guidelines by m00nun1t · · Score: 0, Troll

    Isn't the idea of Apple having guidelines kinda ironic. Why don't they just throw out the whole guidelines manual and replace it with a single line.

    THINK DIFFERENT

  164. It's what you do with it by Anonymous Coward · · Score: 0

    Unless you spend most of your time just browsing your folders and moving files around, the operating system is more or less irrelevant, as long as it's stable and fast (and currently Windows 2000/XP beats OSX in both departments - as does Linux, but Linux isn't as user-friendly or as polished as Windows and OSX). What really counts is the applications.

    And Word looks and does basically the same on Windows and MacOS. And so does Photoshop. And so do pretty much all major programs. Plus there's the fact that virtually all (non-Apple) MacOS software also exists for Windows, while the opposite is not true. And when you take games (which are a major factor for a lot of people) into the equation, it's even more one-sided. Which is why Apple are now buying companies and killing the Windows / Linux versions of their software; because they know the only way professionals will buy Macs is if they have absolutely no choice.

    It would be nice to have the option to run OSX on x86 hardware (sorry but I'm not paying more for hardware that runs slower). But Apple knows that if they released an x86 (or x86-64) port of OSX (which would be pretty easy to do, since it's based on BSD) they'd stop selling Macs altogether. Besides, I don't think Superior Steve would like the idea of regular people using his operating system.

    What's wrong about dealing with Intel or Microsoft or any other company? If they make good products and if I think they're worth the money they're asking, I'll buy them. Just as you "deal with" Apple.

    I wasn't forced to pay for anything I didn't want. I picked every hardware and software component very carefully, from the CPUs to the mouse, from the operating system to the video-editing software. Can you say the same about your Mac(s)?

    And what do you mean by "drivers breaking"? Naturally, a Windows 3.1 driver won't work properly on Windows NT, and a Windows 95 driver won't work properly on Windows 2000. They're completely different operating systems. But a Windows NT driver that works on version 4.0 will keep working after you apply all the (six?) service packs and update all the OS components. In fact, Windows NT drivers will also work fine in Windows 2000 and Windows XP. That's drivers from 1992 working on an OS released in 2002. And don't get me started on Mac drivers (need I say "printing" again?).

    BTW, there are plenty of great-looking PC cases, too (including some Mac clones). Personally I don't like the standard Mac cases, and I wish I could pick my own.

    1. Re:It's what you do with it by MoneyT · · Score: 2

      And so you're welcome to you're opinion. I just think personaly a mac feels better than a PC. Maybe it's because I grew up on them. But I use both, and I always feel more at ease with a mac. It's a feeling of personality and understanding. It sounds lame I know, but I see it all the time, and you see it even with PC users and their computers. The computer just doesn't perform the same for anyone else except the owner. I don't know how to describe it or why, but I feel it more with a mac than with a PC. And in honesty, I've never felt deprived by a lack of games on the mac.

      --
      T Money
      World Domination with a plastic spoon since 1984
  165. debian + windowmaker/fluxbox by Anonymous Coward · · Score: 0

    = happy...

    that's all you need to know...

  166. iApps standardized in Jagwire by Anonymous Coward · · Score: 0

    A number of people have mentioned how Apple violated its own design rules in multiple ways with the iApps. That's correct, and as a die-hard Apple fan Apple's violations of their own rules offends me.

    No one seems to have pointed out in the replies I've read that Apple has at least standardized the iApp interface in OS 10.2 (Jagwire), so that the brushed metal interface is now available for all developers. The brushed metal interface still offends me, but at least they've had the decency to standardize it.

    For those who don't appreciate the importance of getting the interface right, I should describe my struggles to choose a web browser in OS X.

    • Internet Explorer still has OS 9 style buttons in some of its dialogs, which are jarring every time I encounter them.
    • Mozilla and Netscape have completely reinvented the user interface. Not only is that wrong by itself, but they've broken the behavior of text boxes, so selecting text along the left edge of the box frequently gives unexpected results. This can be avoided through much more care than should be necessary given to the positioning of the mouse.
    • Opera and iCab both use the standard OS X widgets, but have a long way to go before they'll feel native to OS X. Buttons with slightly truncated text are common in Opera.
    • So my preferred web browser is OmniWeb, solely because it nails the interface. It feels like an OS X app in a way that no other web browser I've tried comes close to matching. The problem there is that OmniWeb is behind on JavaScript and CSS support, meaning that although it gets the OS interface correct, it gets the Web interface wrong. As a result, I end up switching off between OmniWeb and Netscape and resenting them both.

    I think it's a great thing that Apple makes the effort it does to make its user interface guidelines known, and I appreciate the results every time I use my computer.

    Matthew Morse
    Friends don't let friends Slashdot.

  167. Every OS X window breaks a cardinal rule by Anonymous Coward · · Score: 0

    Never, EVER use color as the sole indicator of purpose. GNOME v1 breaks this rule constantly, with their green and red spheres in their Yes/No buttons. OS X breaks it with their title bar buttons. Red? Yellow? Green? To the typical red-green color-blind male, they all look the same.

    Score: -1 for inaccessibility

    1. Re:Every OS X window breaks a cardinal rule by Dragonmaster+Lou · · Score: 1

      You don't have it quite right. There is also position to indicate what they do, and little "X" "+" and "-" symbols do appear when you hover the mouse over the buttons.

      That said, it would be preferable if the symbols were on all the time for the color blind (having to hover the mouse over the buttons to figure out what they did is annoying), but it's not as totally hopeless as you implied.

  168. Re:Right Click (right click works) by goodmanj · · Score: 1
    ...the contextual menu is not required for ANYTHING. By design, there's *nothing* you can do with a contextual menu that you can't do in some other fashion.

    What about "Show Package Contents" for an application bundle? It's in the context menu in the Finder, but if there's a menu-bar item for it, I haven't found it.

  169. Re:Rather be stuck with MS Windows than Mac hardwa by Anonymous Coward · · Score: 0

    The essence of your post is: "Apple can beat Microsoft by being like Microsoft."

    I think it is you, my friend, who need the clue.

  170. Developers switch to Apple by Anonymous Coward · · Score: 0

    I dont think so I have been developing software for a long time. I have programmed for both platforms and if You think that Programming for Apple UI is easy or worth anyones time you are crazy, Why should I or anyone program for a substandard OS to run on slow substandard hardware Its not going to happen,Apple created Mac OS X to bring it out of death throes, Rhapsody was the best version of OS X ever, these new versions are too bloated with so much crap and Apple rips of the developers Ideas can you say Watson is used in the new sherlock, and iChat is a rip off of a AOL client that a third party wrote that its not worth it, Apple complains about Microsoft when it employs many of the same tactics, Sure Mac OS X is exciting but its days are done, No way to make money off of Mac I will stay with XP, thank you very much...

  171. Another useful Slashdot post... by Anonymous Coward · · Score: 0

    And, judging from your post, half the fun of posting on Slashdot consists of taking one sentence out of context and making senseless comments about it.

    Try reading the whole message, or at least the full paragraph.

    Why can't people simply stand behind their choices without having to justify them and try to convince other people that they are somehow "superior"? It's perfectly okay to prefer Macs. Because you like the case, because you like the desktop, because you like the way the keyboard feels or for any other reason. For some people that may be worth what I (and many like me) consider an excessively high price. But why do you feel the need to say "they're very usable and that's why people buy them". Like PCs aren't usable, or people don't buy them? Duh...! Why are Macs "more elegant"? Because they all look the same?

    I'll take versatility and freedom of choice over (someone else's concept of) elegance anytime.

    You like your Mac? Great, have fun. But must you really spend your life telling everyone about it? Hey, maybe you'll get hired as a Slashdot editor...

    1. Re:Another useful Slashdot post... by reallocate · · Score: 2

      A rare rational statement, for the most part. I doubt that I'm a typical Mac owner, per the reasons I've given elsewhere in this thread. Apple's closed and tightly controlled hardware-software integration brings advantages and disadvantages. Right now, the advantages tip the scales for me. And, for those who don't remember the 1980's, hardware-software integration was a common approach -- in particular, see Amiga and Atari. IBM's open PC architecture changed all that (and also open the door for Microsoft's closed software platform.) There was more variety and competition in the PC market before IBM released their first PC than after. All Apple has done is carefully nurture their brand in order to carve out a tiny sliver of the overall market.

      By the way, I'll trade you the Apple stories for all the "Game Developer Fires Staff", "Video Card Cracks Terabyte Barrier", and "Linux Powers Server in My Boot Heel" pieces.

      --
      -- Slashdot: When Public Access TV Says "No"
  172. Re:Point 9... by N1KO · · Score: 1

    Nonsense, that's like saying its harder to add on a scientific calculator compared to a plain one.

    You can easily ignore the second (or third, fourth, etc) button just as you can ignore all the special functions of a scientific calculator when you're only adding.

  173. I want a choice by Anonymous Coward · · Score: 0

    I just think personaly a mac feels better than a PC. Maybe it's because I grew up on them.

    That's one of the main reasons why so many people run from anything that doesn't look like Windows: because it's what they're used to. I've been using computers since the ZX-81 and I give pretty much everything a try (both in terms of hardware and software). What I like about PCs is the way they let me pick each component individually. What is Microsoft's "monopoly" of PC software compared to Apple's monopoly of Mac software and hardware?

    I can understand feeling more "at home" on the Mac's desktop, but once you're inside a specific program (ex., Photoshop), what's the difference between a Mac and a PC? The only difference I see is the Mac is always reasonable and the PC can be either brilliant or a piece of crap. If it's a PC I use regularly, chances are I've made sure it's closer to the former.

    And in honesty, I've never felt deprived by a lack of games on the mac.

    Still, if you ask 1000 people what are the top 5 things they use their computer for, I'm sure "playing games" will be on 900 people's list. And gaming is, effectively, what drives the high-end PC market (CPUs / graphics cards). No-one needs a 2GHz CPU (or even a 1GHz CPU) to send e-mails.

    But the fact is, virtually all PCs nowadays have CPUs above 1GHz, and they're dirt cheap. Why? Because you have Intel and AMD fighting for the market. You have a choice. Something you don't have on the Mac side of the fence.

    1. Re:I want a choice by Anonymous Coward · · Score: 0

      Playing games?? Maybe if you asked 1000 Slashdot readers.

      If you asked 1000 office workers, or 1000 graphic designers, or 1000 DB admins... many have never even bought a computer game. If they have, it's for their (kids') Playstation 2. They don't care about CPUs and graphics cards. NVidia? What's that? Athlon? Sounds like a jock strap.

    2. Re:I want a choice by Anonymous Coward · · Score: 0

      Actually I wasn't just throwing a number at random. The result of a general census (ages 13-65) turned up "gaming" as one of the top 5 computer applications for about 92% of the participants. The only things that topped it were browsing the internet, e-mail and word processing.

  174. Windows File Extensions Usages are Awesome by Nazmun · · Score: 1

    I know this place is filled with anti-microsoft people, but please notice that this isn't a flamebait.

    I like being able to change the file extension of a file and have it open in different programs or behave a little differently. I constantly due it for many different reasons. When I used a mac os for the first time, this was a really large pain for me.

    Also if for some reason you are changing file extension of a file with the file extensions set to hidden well that really does kinda say something negative about ones intelligence.

    All in all, I'm glad that OSX allows people to more active use file extensions. I am also happy that Windows has always allowed one to do it. I personally choose flexibility on a computer system more then a little convenience. Isn't that why many geeks also use os's like linux?

    --
    Hmmm... Pie...
    1. Re:Windows File Extensions Usages are Awesome by billbaggins · · Score: 4, Interesting
      Ok, normally I wouldn't bother with a reply to this, but you attacked my intelligence, so I'm gonna have at you. The situation that I described took place when I was using SOMEONE ELSE'S COMPUTER. I was not at liberty to set 'show file extensions' to True.

      For another example... say Grandma has created her first web page, and because I was the one talking her through it, she did it in Notepad. Now, she can't see the file extension, but Notepad, being its usual *cough* helpful self, saved it as index.txt or something like that. So she goes and changes the filename (all of which she sees is 'index') to 'index.html'. Mac OS X does the Right Thing here: changes 'index.txt' to 'index.html'. Windows does the simpler, but Wrong thing: changes the filename to 'index.html.txt'. Double-clicking on it will still bring it up in Notepad.

      There's one simple, slightly contrived, example. I'm sure others could be provided. Pray cease to comment on my intelligence, unless you actually know what I'm talking about.

      --
      "The best argument against democracy is a five minute chat with the average voter."
      --Winston Churchill
    2. Re:Windows File Extensions Usages are Awesome by Anonymous Coward · · Score: 0

      Actually, if I want to open, say, index.html as a text file in Linux, I can type "vi index.html". I Windows, I could right-click on index.html and choose "Open with...".

  175. How did they make iTunes small? by GlenRaphael · · Score: 2
    The example also shows Itunes on the desktop. Although it's not on top, it's not visually obvious that it's currently in background.

    I also noticed in the screenshot the iTunes window is tiny and shows just the bare essentials rather than displaying the library. My biggest UI complaint with iTunes has always been that the window is too big and can't be reduced to a small enough size that it doesn't dominate the display. So can anybody tell me how to get the view of iTunes that appears in this screenshot? Is there some really-well-hidden UI element to do that, or is it a third-party hack?

    And I miss windowshading.

    --
    I play Nerd-Folk!
    1. Re:How did they make iTunes small? by Anonymous Coward · · Score: 0

      So can anybody tell me how to get the view of iTunes that appears in this screenshot?

      Click the zoom button in the iTunes window, (the green button on OS X).

      Hardly obscure. It does what the zoom button is meant to do...

    2. Re:How did they make iTunes small? by Anonymous Coward · · Score: 0

      no, that a function of apples itunes gui (and quicktime) you can drag and scale the itunes window even smaller than that so its a square. or you can click the minimze button and it will scale down to the your prefered size and screen placemnt which is sotred it is prefs file.

      your really should use the product before you bash it

    3. Re:How did they make iTunes small? by foo12 · · Score: 1

      The most counter-intuitive, stupid UI decision: Click the maximize button. Bleh --- There's a standard widget to toggle window mode. Use it Apple

  176. Do you stick to your own "standard"? by anomalousman · · Score: 1

    Hey Coward,

    So you call a random user, programmer, astronaut, doctor, lawyer, governor, or president "he" or "him"...

    Do you do the same for a random nurse, or secretary?

    By the way, the "established format" is to have unworthy scum like you (and me) working for the aristocracy. Don't stop turning the clock back just because you're on top of the heap.

  177. Re:Rather be stuck with MS Windows than Mac hardwa by TheInternet · · Score: 2

    They would crush Microsoft within 5 years if they would port Mac OSX to Intel/AMD based hardware sell copies of the OS at $50/ea, and help get software designers to include binaries for both OSes in every box they sell

    So you base this assumption on what, exactly?

    Perhaps you would like to be able to buy a dirt-cheap PC that Mac OS X to boot on. But I don't think the end result for both you and Apple would be nearly as picturesque as you describe.

    Windows is Microsoft's core business. It's hard to imagine Apple crushing Apple on standard wintel hardware, especially in five years. Apple has a considerable product development advantage when working with their own hardware. A lot of the ease-of-use and simple management aspects of Mac OS X come from intergrated hardware.

    - Scott

    --
    Scott Stevenson
    Tree House Ideas
  178. Re:Other than Excel - what apps use MDI now though by jimbolaya · · Score: 2
    I haven't used Office XP (or Windows XP), but in previous versions of Office, Word, Excel, and PowerPoint all use MDI. If Microsoft has changed this, it probably means that they have finally realized that MDI is a Bad Thing. That just adds credence to Apple's argument.

    Keep in mind that Apple's article was not to bash Windows, but to help developers switching to Mac OS X develop consistent and user friendly applications. So, if they say MDI is a bad interface design, it's not entirely relevant whether Microsoft continues to use it or not; they are simply saying, "Don't use MDI on the Mac."

    --

    There ain't no rules here; we're trying to accomplish something.

  179. Give programmers less control. by Decimal · · Score: 2

    I disagree. I generally find that custom widgets charm developers, and annoy users.

    Personally, I don't think that programmers should be given that much control over their apps. I mean for a full screen game sure, but a standard window enviornment? One app I use regularly has an "about" box that fades in and then out. What crap. I know that the programmer could very well choose not to create the app if they weren't given the option, but come on. An analogy: If I donate to a charity, I don't expect to be able to demand what direction their cupbard doors open. Giving programmers more control often means the user has less control. The user should have choices over how their apps look and work. They should be the ones who decide where the "preferences" option goes, whether it be File -> Options or Edit -> Preferences. What if I wanted to designate that a program will have no write access anywhere but the directory it was installed in? How many programs tolerate this? What if they were written for an operating system that won't have it any other way?

    I'd like to see web pages take this route, too. Not user design, but raw data. The user decides where the email is to be shown on the screen if there is one. If there is an [email] tag, put it here. Otherwise it would read "none". Repeat for [last updated], [external links], [internal links], etc.

    I'm sure many here would recoil at the idea of not being able to choose every aspect of how their baby runs, but I certainly don't. It would be nice to use an operating system that rips control from the anus of a programmer and lets the advanced user choose to make it simple. This doesn't mean letting the user compile their own, it means leaving it up to the user in the first place.

    --

    Remember "Bring 'em on"? *sigh
    1. Re:Give programmers less control. by 0x0d0a · · Score: 4, Insightful

      HTML was originally designed to work this way. Unfortunately, it's hard to convince peopel that this is a better system -- legions of hard-copy print era designers swarmed the Web design scene and pretty much decimated any hope of client-side UI control.

      Now, HTML is pretty much an inefficient, hard to parse Postscript variant.

    2. Re:Give programmers less control. by Chazmyrr · · Score: 1

      No, what decimated any hope of client side UI control is that users can't/won't take the time to set up every aspect of a user interface for a given web application. That is the designers job.

  180. Re: Browser by foonie · · Score: 1

    I used to be a big OmniWeb user, but the lack of full JavaScript and CSS support finally got to me. After a short stint with Mozilla, I'm finally going to give Chimera a more serious look. Chimera is officially at 0.4.0, with nightly builds showing 0.5.0. It's basically the same Gecko rendering engine of Mozilla/Netscape, but it's a Cocoa app. When this finally hits 1.0, I predict that it's going to be an amazing application. Definitely worth a try at this point.

  181. Re:Doesn't acknowlege Windows' keyboard superiorit by Anonymous Coward · · Score: 0

    Having to make your own accelerators doesn't sound very "out of the box" to me.

  182. Re:I'm a troll by Anonymous Coward · · Score: 0

    I'm a troll

  183. Oh dear, a usability wannabe! by wackybrit · · Score: 2

    You mean Fitt's Law, of course.

    And it doesn't 'break' Fitt's Law at all. Fitt's Law is related to the distance to, and size of, targets, not their absolute position.

    Positioning the tabs in the middle of a dialog or to the left makes no real difference. You are mistaking the fact that Fitt's Law says that putting things at far edges of the screen improves the user's ability to target them. But.. since these tabs are not at the edge of the screen, the target area is the same whether they're in the middle or not.

    Forgetting Fitt's Law, the Apple dialog is actually better in this example, since the drop down box in the Windows dialog encompasses a range of different options (hours, minutes, don't switch monitor off), whereas the Apple dialog splits the actions into logical parts.

  184. challenge by Anonymous Coward · · Score: 0

    I should have put "challenge" above, not proposal.

    Time to put

    chmod -rwx /dev/mouse /usr/X11R6/bin/xterm

    into cron.weekly. And then measure time before it needs to be changed.

  185. Re:Point 9... by Phroggy · · Score: 2

    Nonsense, that's like saying its harder to add on a scientific calculator compared to a plain one.

    When I was in school I had people ask to borrow my calculator, and when I handed them my TI-82 they looked at it for a bit, then handed it back and asked somebody else for a "normal" calculator. Naturally, anyone who knows how to use it can use it for simple addition with no trouble at all.

    Let me tell you, the one-button mouse is a godsend to anyone in tech support. You'd be amazed how many Windows users have trouble figuring out the difference between a left-double-click and a right-single-click.

    --
    $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
    $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
  186. Video cassettes by wackybrit · · Score: 1

    You have a VCR and you can afford to rent one movie every week for the rest of your life. Let's say you have 60 years left to live.

    This means you can watch a total of 3,120 videos. But does that mean that a video store that keeps 3,120 would keep you satisfied? Of course not. You'd want a wider choice than that, even though you wouldn't want to watch every film.

  187. Re:Point 9... by MoneyT · · Score: 2

    Next time someone asks you for a calculator, hand them a TI-83 and see what they do. It does the same things the same way any other calculator with the same button presses, but people look at it and go google eyed and don't seem to know what to do. Why do you think most calculator programs (like the ones on palm pilots and on your computer) come default in basic mode? So as not to confuse people.

    --
    T Money
    World Domination with a plastic spoon since 1984
  188. Re:Doesn't acknowlege Windows' keyboard superiorit by Phroggy · · Score: 2
    Keyboard shortcuts is one of the things Windows sucks at, compared to Mac OS. Of course Linux sucks much worse, but still, if you're not familiar with the Mac way of doing things, you really have no idea how truly awesome keyboard shortcuts can be. The same shortcuts work in EVERY application, from a text editor to a browser to an SSH client to a game.

    What's the shortcut to paste?

    • In most Windows applications, either Ctrl-V or Shift-Insert works.
    • In some places, such as the Advanced Find dialog box in Microsoft Outlook, Shift-Insert doesn't work and you must use Ctrl-V.
    • In SecureCRT, since Ctrl-V has to be sent to the server, you must use Shift-Insert.
    • In QVTTerm, press Alt-V.
    • In PuTTY, right-click in the window to paste. Anything you select is automatically copied, like X.
    • In a DOS prompt, right-click in the window to paste, but to copy you have to press Enter.
    • In Telnet on Win95/98/ME, press Alt-E-V to select it from the menu, which also works in most other apps, but of course is slower and less convenient than the other ways of doing it.


    Yeah, Windows users will whine about how of course it has to be this way. On the Mac, though, Command-V always works. Always. Everywhere. In all applications.
    --
    $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
    $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
  189. UI...Blah...just use shell! by ducomputergeek · · Score: 1

    All this UI crap...I knew there was a reason I still used shell access.

    --
    "The problem with socialism is eventually you run out of other people's money" - Thatcher.
    1. Re:UI...Blah...just use shell! by Anonymous Coward · · Score: 0

      I guess you do all your surfing in Lynx, and code your JPEGs by hand? Not to mention that you use ed to write your source code, rather than a full-screen editor like vi or emacs?

  190. Re:Doesn't acknowlege Windows' keyboard superiorit by Anonymous Coward · · Score: 0

    Way back in Windows 3.0 it used to be Shift-Insert everywhere (except the DOS window), just like in all applications after the SAA standard. (like DOS Edit or the Borland TurboVision IDEs).
    No idea why MS went with Ctrl-V later on.

  191. button order in dialogs by CaptnMArk · · Score: 1

    One thing I dislike in Mac GUI is the order of buttons in dialogs.

    Unfortunately GNOME 2.0 inherits this problem. I am totally unable to use it until I find the option to reverse the order.

    1. Re:button order in dialogs by Anonymous Coward · · Score: 0

      Your life must really suck, if the order of buttons in a dialog prevents you from using it.

  192. Actually... by Anonymous Coward · · Score: 0

    To click on "OK" in a Mac dialog box with your keyboard, press Return. To click on "Cancel", press command-.

    OSX 10.2 has nearly-complete keyboard control, i.E. press F10 (if I remember correctly) to access the menubar.

    While Windows is really good in this respect, I'd say that Apple is quickly catching up.

  193. Re:The single menubar is more usable by Fitts' Law by Anonymous Coward · · Score: 0

    this should be modded up. he hits it on the head

  194. Predicatable by Anonymous Coward · · Score: 0

    The most obvious button *is* the button in the front of the drive.

    But you have this idea that when disks are closed on a PC they become unmounted.

    Here's how it works:

    1) Button is pushed on front of CD-ROM
    2) Signal is sent to OS (this happens on PC right now).
    3) Unless this will do something dumb (i.e. in the middle of a burn), OS flushes buffers and tells drive to open up.

    So tell me again Mac-boy, how the mac is more elegent.

    You're busy dragging your CD to the trash can, Mac-boy.

    1. Re:Predicatable by MoneyT · · Score: 2

      There's this wonderful little button on our keyboard that ejects CDs. Hell of a lot quicker than reaching up to hit the eject button on the case (or reaching under the desk in the case of most PCs)

      --
      T Money
      World Domination with a plastic spoon since 1984
  195. There is little difference between platforms... by Anonymous Coward · · Score: 0

    Arguing over the tiny differences between platforms is misguided. The real usability issues do not come from Apple or Microsoft, but from poorly developed software on all platforms. People tend to try and reinvent the wheel everytime they design a UI, because most of us tend to think of UI design as "making it perty", instead of the rational analysis and design task it is...

  196. Re:Doesn't acknowlege Windows' keyboard superiorit by Anonymous Coward · · Score: 0

    Nobody wants "out of the box" for Linux. How will people feel all clever and superior if anyone can have a computer just like theirs?

  197. Re:Actually, even MSes own programs have this prob by sfe_software · · Score: 2

    MS quite often breaks their own rules. There are guidelines that a developer must follow in order to get the silly Windows logo on your product, and most of MS's own software break these rules.

    They encourage developers to use the common dialog boxes (Open, Save As, etc), yet most of Office 2000 (and probably other versions) do not. It looks to me like they wanted to add some of the stupid features from Win2k to Office 2k, before Win2k shipped (IIRC, the buttons on the left of the dialog for Desktop, Network etc).

    As a result, one annoyance I have with Office and Visual Studio is this: I keep my "MenuDelay" to zero, eg, I can't stand the 400 millisecond delay between the time you hover over a popup menu and the time the menu shows. It's a simple registry hack (or use TweakUI) to change this. But Office and Visual Studio apparently use their own menus, and ignore this setting.

    There are probably a million other examples (many things in Media Player come to mind).

    I agree, sometimes you do need custom widgets for specific tasks, but one should never replace the OS-provided ones if it can be avoided. This is about my only real gripe with Mozilla honestly... I don't care if it looks the same across platforms, and browsers do not need to be skinned IMO... Not to mention this god-awful buggy text box they created (though better than it used to be, it seems like an unnecessary waste of dev time).

    --
    NGWave - Fast Sound Editor for Windows
  198. MacOS X File Extensions by Oculus+Habent · · Score: 3

    Apple went even farther with MacOS X. While a file may be associated with a primary program, it can also have a list of programs that register the file type. This way, you can open that .JPG in Internet Explorer, Preview, Photoshop, or anything else that told the OS it handles JPEGs.

    --
    That what was all this school was for... to teach us how to solve our own problems. -- janeowit
    1. Re:MacOS X File Extensions by lamz · · Score: 4, Informative

      Actually, to be precise, (and we slashdotters like precise, no?) all previous versions of the Mac OS have recognized both a Creator code and a Filetype code for every single data file. Thus, a file can identify itself as a jpeg, and additionally identifies which application was used to create the file.

      This allows for a fascinating and brilliant user interface device, which is so intuitive that most people will never even realize it exists. When you drag a data file icon to an application icon, the application icon only highlights if that particular application believes it can open that particular file type. (If you're lucky enough to be sitting in front of a Mac right now, give it a try by dragging a data file icon to the wrong application.)

      --

      Mike van Lammeren
      It will challenge your head, your brain, and your mind.

    2. Re:MacOS X File Extensions by schvenk · · Score: 2, Insightful

      ...Which works great until you need to open a file with an application that doesn't think it can open the file. Then you're stuck messing around with altering the type and creator codes. Or you receive a file over email, it's lost its type and creator codes, and you're stuck trying to figure out what it is and recreate them.

      At least for me, while the original Mac OS scheme worked well when it worked, the addition of file extensions is a welcome one because it's easy to tweak when it doesn't work. (I agree with the earlier poster who pointed out that the extension-handling is more elegant than that in Windows.) Beyond that, it makes sense in a world where files are routinely exchanged among platforms.

  199. Re:Doesn't acknowlege Windows' keyboard superiorit by lscoughlin · · Score: 1

    yes, but command-v is a stupid combination.

    --
    Old truckers never die, they just get a new peterbilt
  200. Re:Layman's! by Anonymous Coward · · Score: 0

    I think the point is that almost all Windows programmers are, in fact, total laymen when it comes to usable interface design...

    -spheric*

  201. The whole windows install problem by Sabalon · · Score: 2

    While I am convinced that the default option on InstallShield is to prompt the user to reboot, cause it seems almost every win install does just that - needing it or not, the windows install process is still a major pain that doesn't need to be.

    I am trying to think why you would need to do anything other than move the files in place. On the Mac you just drag and drop. While install scripts may complicate things on Unix systems somewhat, they basically boil down to "move these files from the CD or this location to the final location." If it wasn't for the whole make process, most software installed boil down to "cp -R . /opt/whatever"

    Simplicity.

    So why are windows installs so horrendus? I can see driver installs needing to do something special, but registry settings can be setup the first time the program is run, registrations/proof-of-purchase/warez-serials can be done at the first run of the app.

    In fact, if decompression from a file is the only reason to run an install program, I'd prefer it if they just left the files on the CD as they need to be. That way, if I was to hose photoshop.dll, I could just recopy it from the CD and not have to reinstall.

    If you need to dumb it down a bit, make the autorun say "you just put in this CD - wanna install it?" and if they choose to do so, then make a directory and copy the files there...nothing arcane needed.

  202. Apple software on Windows by zero_offset · · Score: 2
    I find it amusing that the highly-UI-aware Apple manages to produce some of the most bizarre non-standard Windows applications I've ever seen. Talk about "custom controls"...

    "Not a flame, just an observation." :)

    --

    Slashdot quality declines as the number of hot grits posts decreases. - Provolt's Law, Apr-09-2005

  203. 9. Design Clear Dialogs by LordNimon · · Score: 3, Insightful
    In my opinion, #9 clearly demonstrates the difference between professional UI designers and programmers who think they are designers. And the reason I say that is because I'm a programmers who thinks he's a designer, and I would never have figured out #9 on my own.

    The Windows dialog box in #9 looks perfectly normal to me. It asks a question and lets you enter a response. But in the back of my mind, something always bugged me about it, and not just because it gives you three ways to answer a Yes/No question. Now that I see the comparison with the Mac version, I realize what's wrong with it. The Mac version makes more sense and is guininely easier to use. It's not a coincidence that these are also two phrases that describe a Mac (compared to a PC).

    One of the things the Mac dialog box does that the Windows box doesn't is converge everything about the action into the dialog box itself. In other words, it gives you enough information so that you can focus on the immediate issue (saving the file) without having to think how you got there.

    As the text says, dialog boxes interrupt the user. When the user is interrupted, his train of thought is interrupted, and that usually forces him to think unnecessarily harder about what he's doing.

    --
    And the men who hold high places must be the ones who start
    To mold a new reality... closer to the heart
    1. Re:9. Design Clear Dialogs by Anonymous Coward · · Score: 0

      i once saw one of my COMPUTER SCIENCE proffessors click on close [X] and then "Cancel" about 14 times before he realized he wanted to click on "No" in the dialog box.
      Sure it was funny for us watching on the overhead, but it illustrates Apple's point in number 9 beautifully.

  204. Re:The single menubar is more usable by Fitts' Law by Anonymous Coward · · Score: 0

    I'm sorry also, as I do not agree with either of your conclusions.

    Maybe I'm ignorant, but how can you perform an operation on a window you are not currently using? For instance, how can you perform an operation in Word when you are in an Excel window? That would negate argument #2. If you mean you can perform an operation on a non-highlighted window by simply clicking on a command in that window then I would argue that you would want to have that window hightlighted regardless to make sure it is the window/file on which you wish to perform the operation.

    As for your first point, I recommend knowing where your cursor is. It's like driving, keep you car on the correct side of the road or expect an accident... I'd much rather hit the top of the screen, something I cannot overshoot, than focus on the top of a menu bar and overshoot, resulting in highlighting another window instead. That's one way to avoid doing two things again.

    Additionally, who are the so many people who find the single menu bar so annoying? I'll bet that if true, it is split quite cleanly between Mac and Windows users, and is simply a function of familiarity, that is, resistance to change.

  205. ...And Windows' *mouse* superiority by GCP · · Score: 2

    The two button mouse, where the second button is restricted to doing just one thing: bringing up a context menu -- is a huge improvement in usability over a single mouse button.

    The scroll wheel on the mouse, eliminating the need to ever hunt down and manipulate a scroll bar in well-written apps, is the greatest thing since the mouse itself.

    The Mac has neither. The Mac UI seems to be ruled by religious precepts that were finalized in the 1980's and no longer open for discussion.

    Yes, you can buy a 3rd-party mouse with the extra button and wheel, or use both hands and type/click (ctrl-click) and it may work with 3rd-party Windows apps ported to the Mac, but not (or very little) with Apple's own software. Try finding context menus in the Finder or iTunes, etc. On Windows, every visual item would expose the useful operations that could be performed on it via a context menu. You want to know "how do I do...?" for some item? Try right-clicking it. But that's a Windows idea that Apple didn't invent, so they don't believe in it.

    The standard Mac has a single-button mouse, so Mac developers have a lot less incentive than Windows developers to create context menus. Apple doesn't tell developers not to do it, but they never recommend a good, thorough set of context menus as part of their UI guidelines.

    Apple's early studies of mouse buttons compared single mouse buttons with complex functionality vs. multiple mouse buttons, each with complex functionality, and tested them on an audience that had never used a mouse or a GUI before.

    They looked at lots of different placements of scroll bars, never considering the idea of a scroll wheel that could make scrollbars unnecessary.

    How many ways does a study have to be out of date before Apple will reconsider their "I can operate the mouse wearing an oven mit" religion? Almost all computer buyers today (in major markets) are buying a replacement computer, and 95% have experience using a 2-button Windows mouse. Many of them don't use the second button, but the Windows UI doesn't require them to. It's merely a convenience, albeit a huge one. The Apple studies were looking at 2nd mouse functions that were both complex and required, and decided that they weren't a good idea, and now there's no changing their minds.

    Until Apple catches up and starts using a "normal" mouse (or something better), I'll find the process of hunting down scroll bars and selecting followed by menu spelunking too annoying to consider a Mac.

    --
    "Those who have never entered upon scientific pursuits know not a tithe of the poetry by which they are surrounded."
    1. Re:...And Windows' *mouse* superiority by rjung2k · · Score: 1

      Wow, someone who's going to let his multi-thousand-dollar computer purchasing decision be decided by a $25 mouse.

      And you may be interested to know that, while Apple may ship a one-button mouse as standard, MacOS X has support for multiplue buttons and scroll wheels all over the place. Heck, 10.2's Mouse preferences even has a control for scroll wheel acceleration...

    2. Re:...And Windows' *mouse* superiority by GCP · · Score: 2

      Wow, someone who completely missed the point.

      It's not the mouse, it's the apps. It's the UI. Because the dumbed down mouse is the standard, the apps tend to be designed for it, instead of being designed for a 2-button mouse, as all Windows apps are. That design approach is the problem.

      I could easily afford to upgrade the mouse for my "multi-thousand-dollar" computer, but that wouldn't help if the apps aren't built for it. Apps like the Finder, iTunes, etc. don't have context menus for most things, because Apple thinks using only one button is better, and buying a 2-button mouse for my own machine won't change the way Apple designs their apps.

      If only we could convince Apple to Think Different....

      --
      "Those who have never entered upon scientific pursuits know not a tithe of the poetry by which they are surrounded."
  206. Re:Doesn't acknowlege Windows' keyboard superiorit by Sax+Maniac · · Score: 2
    What if the item I want to access with the keyboard isn't on a menu, oh, like the Yes/No dialog in Mozilla? What if it's a toggle button inside a dialog? Did you even read my message?

    You are confusing accelerators with keyboard navigation:

    Keyboard navigation (things like Alt-F to post a "File" menu) are completely different beasts than accelerators. Mnemonics are visible, modal keyboard navgiation items, are not customizable, are complete, so that you don't have to go out of your way to create them. Accelerators (like Ctrl-S to "Save") are hidden modeless shortcuts into common features of the application, are almost always incomplete, and must be user-definable.

    A completely nonobvious and invisible way of assigning your own keyboard accelerators is not the same as having a visible and complete set of keyboard navigation.

    You are also taking the classic open-source argument that Makes UIs Suck: well, just go fix it yourself if you don't like it! Just press Ctrl Alt Meta Shift CokeBottle, then edit >~/.foobarrc, add "MakeMyAppLessStupid=True" restart X, and you're good to go!

    Consider an older, disabled person (or even myself with a hangover) with shaky hands, who doesn't have the fine motor control to do pixel-perfect placement with a mouse. Accessability is another reason for good keyboard navigation. Are you saying that they have to assign every interface element to a shortcut? (How many hours would that take? Dunno about you, but I'd run out of keys and wouldn't be able to remember them all.)

    --
    I can explanate how to administrate your network. You must configurate and segmentate it, so it can computate.
  207. The most important reason to use standard controls by alispguru · · Score: 2

    ... is accessibility. I have a friend who is blind, who is a perfectly competent user of Windows 98, as long as applications use controls understood by his screen reader of choice (Jaws). The moment an app writer gets creative and uses a non-standard control, he's flying blind (literally).

    The most annoying thing about use of non-standard controls is that 99% of the time it's completely gratuitous eye-candy, and usually bad eye-candy at that - the new controls do exactly the same stuff as the standards, and typically badly. It's particularly galling when Microsoft themselves does this, in (say) a password-change dialog for MSN. which loads some funky ActiveX control that hoses the screen reader and forces my friend to make his changes by phoning customer support.

    --

    To a Lisp hacker, XML is S-expressions in drag.
  208. they / their by Lovejoy · · Score: 1

    "They" and "their" as singular pronouns have been in popular use for over 200 years.

    I am too lazy to verify the length of the time "they/their" have been in popular use as neuter pronouns, but I am surprised. I have not run into it. What am I missing?

    Come on - if you can write a sentence like this: "Given that language is a set of arbitrary rules which shifts along with culture and usage, why do you have a problem with this?" surely you have a few holdover prescriptivist tendencies yourself! ;-)

    As long as intention can be clearly conveyed and interpreted, there is no right or wrong in language, especially English.

    That is the descriptivist view, to which I adhere, for the most part. However, society imposes a standard upon the language. This dialect, as I'm sure you know, is called "Standard American English (SAE)" or as I like to call it "Tom Brokaw English."

    There are lots of reasons society imposes these standards. Some of them are good reasons. Many of them aren't. In any case, everyone who wants to be taken seriously in any formal context needs to know them.

    When I get an e-mail from a vendor (usually it's a vendor) with an apostrophe-s for a plural, or a "their" instead of "there" I lose a lot of respect for that person. Is that fair? Probably not. Is it going to happen? Yes. And we can't stop it, so we should teach our kids SAE in addition to whatever non-standard dialect they speak at home.

    Still I contend "DEATH TO 'THEY/THEIR' AS SINGULARS"

    1. Re:they / their by Anonymous Coward · · Score: 0

      In any case, everyone who wants to be taken seriously in any formal context needs to know them.

      I agree with this. If someone won't invest the time to learn their language properly, why should we believe they've taken any more time considering their point of view? To all appearances, they are just an amateur mouthing off or repeating something they heard from someone else.

  209. Re:Actually, even MSes own programs have this prob by pod · · Score: 1

    I would REALLY love to know how many hours of developer time was sunk into the monstrosity that is the text box in Mozilla. Even in the latest daily builds is still does not work right: random highliting of text, weird reformatting and reflowing, broken JavaScript interaction (inserting text at cursor position always appends to the end), and I'm sure many more anyone willing to torture text this wonder of programming would find.

    --
    "Hot lesbian witches! It's fucking genius!"
  210. Re:Doesn't acknowlege Windows' keyboard superiorit by Zane+Edwards · · Score: 1

    You have good points, but what lacks is the consistency for really common keystroke tasks (closing a window, or quitting a program). Still nothing like the horror of loosing your mouse in x-windows!

  211. Re:Doesn't acknowlege Windows' keyboard superiorit by Anonymous Coward · · Score: 0

    So how do Mac telnet clients send Ctrl-V to the server?

  212. Re:Doesn't acknowlege Windows' keyboard superiorit by Geoff · · Score: 2
    So how do Mac telnet clients send Ctrl-V to the server?

    Control and command are different keys.

    --

    Computers are useless. They can only give you answers. -- Pablo Picasso

  213. Mod: -10, idiot luddite. by Anonymous Coward · · Score: 0

    OS 9 is dead. Get over it.

  214. Oh, come ON, that wasn't 1 (Troll)... by Anonymous Coward · · Score: 0

    That was at least 3 (Funny). :-)

  215. Re:Actually, even MSes own programs have this prob by gig · · Score: 2

    A counterpart to that is that I'm typing messages to Slashdot in a little window in a Web page, and my spelling mistakes are being underlined red by Mac OS X (the system), not by OmniWeb (the application). It's important, because I told Mac OS X some extra words to watch for (like "Slashdot") and I don't want to have to tell the computer about those words again.

    Time and again geeks excuse bad computer behavior by saying "well, that's a different application" or "that's a different codebase", or "it was originally written for Windows 95, not XP", or WHATEVER. There are a bajillion geek excuses left over from when computers were slow and stupid and rare and expensive. Microsoft speculates on a market for technological stupidity and they come up winners because so many people are so ignorant about the state of the art. Guys puff their chests out in their blogs about the fact that their Windows system only crashes once a month now and I'm truly saddened by that. Yeah, I know it's better than the daily crashes they used to have, but still. Windows 2000 was supposed to be XP but wasn't because they were going to send the coders in to install security and stability instead of features, and years later look what we have.

  216. Re:The single menubar is more usable by Fitts' Law by Anonymous Coward · · Score: 0

    >1. Graphical Organization. As was touched on by the parent post, the single menu bar
    >design causes confusion when more than 1 application is running. Having 1 windows
    >focused, when you are attempting to perform an action on another will result in that action
    >being performed ON THE WRONG WINDOW. There is no way around this.

    I agree that this is a problem. However, the active status of a window is very, very easy to determine, *and* it has been shown repeatedly that people who aren't sophisticated enough to do this without even thinking about it rarely have more than one window open (excluding finder windows) at a time in MacOS 9. (I am not aware of any usability studies that have recorded stats like this in X yet.)

    >2. Switching between application. If I'm working with an IE window, and then decide to
    >save a file in another I first must focus the window I want to perform the action in, and
    >then use the menu. I'm doing 2 things here, where as before I could just do one.

    True on Windows also, if you think about it for a second. On Windows, it is rare that more than one window is visible, with the default configuration. So you have to go down to the task bar, look at it, come up with which window you want, click it, then look for the menu bar, which you're not sure where is.

    A more advanced user might tile or layer his windows, but a beginner won't. And in any case, when I watch people using windows, I almost invariably see them turn this 'one-step process' into two steps, by clicking on the window in the background, thus bringing it to the foreground, and then clicking on the menu. In fact, I'm not sure it's possible to open a menu on a window that is in the background.

    >I think it would be interesting though, to create a menu bar approach like the one in
    >Windows, and then make life better according to the sacred Fitt's law by making
    >the mouse accelerate slower over the menu (or even give force feedback) than the rest of
    >the window. This might be disorienting at first, but after someone got used to it, I
    >imagine it could speed things up even more than either the MacOS or Windows style alone.

    I cannot conceive of something I would find more loathesome than a mouse pointer that doesn't have some sort of linear mapping for its movement. Having the mouse cursor zip to the middle of one button on Windows is still done occasionally, and it never fails to make me move my mouse cursor off the button, look for it, find it, move it back to the button, and then quit the program and never use it again. This would have the exact same effect.

    >The fact that so many people find the single menu bar so annoying should tell you
    >something. UI interface designers have become so high up in their towers they forget
    >to listen to the people that will use it.

    The fact that so many people find the concept of a GUI annoying should tell you something. Sound familiar? Twenty years ago (almost) that was the credo.

    You're used to two menu bars. You can't stand to change your ways. Therefore, one menu bar is bad. For you. But don't mistake that for universality.

    -Fred Fnord

  217. Re:Point 9... by gig · · Score: 2

    I've tried them all, and I love my Apple Pro Mouse and its one button simplicity. My left hand stays on the keyboard, where it does modifier keys all day, so Shift+U and Control+click are the same thing, while my right hand just points and clicks at things. Point, click, point, click. Gets ingrained in you like a musical instrument.

  218. Mod this falsehood down... by Slur · · Score: 2

    Why total bunk gets modded up as "informative" is beyond me.

    --
    -- thinkyhead software and media
    1. Re:Mod this falsehood down... by skydude_20 · · Score: 2

      +1 Informative is the last mod point i would have wanted on this, maybe +1 funny

      --
      Jesus saves souls and redeems them for valuable cash prizes
  219. *yawwwn* Same old mantra by Anonymous Coward · · Score: 0

    Oh, yes, please tell us again how html was intended as this wonderful, pure system for sharing information over the web, which would allow it to seamlessly flow into all manner of devices and programs, and tra-la-la. That is, until those dumb, lazy, selfish, shortsighted, old-fashioned, dumb, illiterate, dumb designers screwed everything up! How dare they use tables as a layout element! That's not what they were intended for! Shame, shame!

    After all, the "hard-copy print era" should be so over, right? Yet all of those obsolete dinosaurs "swarmed the Web design scene" and ruined the Dream of html!

    Never mind the fact that software companies created browsers that were incompatible with each other and html standards. Never mind the fact that standards-compliant, non-static html layouts are mostly boring and forgettable. Never mind that web sites' primary audience is, in all honesty, usually made up of a lot more AOL subscribers than holier-than-thou armchair web design critics.

    No, no; forget all of that. The W3C approved standards for proper html usage were handed down from the Almighty on clay tablets, and any old-fashioned, unhip "hard-copy print era designer" who questions them is a heretic.

    Sincerely,
    A Hard-copy Print Era Designer

    P.S. Yes that was sarcasm. -sigh-

  220. Photoshopped: Not! by Slur · · Score: 2

    No, the image was not doctored. This is exactly what appears for Windows users on systems lacking power management.

    Apple suggests that such a dialog should be made smaller. For this particular example I believe it would be more appropriate (by Apple HIG) to display the power management options - but in a disabled state. The dialog should then (Windows-style) have a yellow warning icon with some explanatory text saying "No power management features are available on this computer." (Of course this would make the dialog larger, but Windows users just love lots of explanatory text.)

    --
    -- thinkyhead software and media
  221. Re:Doesn't acknowlege Windows' keyboard superiorit by Anonymous Coward · · Score: 0

    Access to the "System" menu in Windows: ALT + SPACE

    Maximise the Window: ALT + SPACE, X
    Minimise the Window: ALT + SPACE, N
    Close the Window: ALT + SPACE, C or ALT + F4

  222. Re:Doesn't acknowlege Windows' keyboard superiorit by hacker · · Score: 2
    What if the item I want to access with the keyboard isn't on a menu, oh, like the Yes/No dialog in Mozilla? What if it's a toggle button inside a dialog?

    Then you use the keyboard, tab and the spacebar, like every other person has been using on Windows, Macintosh, Linux, and Unix for decades. Did you manage to decouple that ability somewhere? I still have it in every OS I've ever used.

    You are confusing accelerators with keyboard navigation:

    No at all. Input is input, and I certainly do NOT want any application overriding or inheriting the binding preferences, input modifiers, accelerators or navigation elements that are set by my window manager, desktop, or OS itself.

    Unlike you, I see this as adding flexibility, not taking it away. I don't want 'Y' and 'N' to be a default choice in a dialog box for Mozilla (when you can easily get to either of those through XUL, or with the normal keyboard without changing a single binding anywhere in your OS). What if I have 'Y' set as a watched binding in my window manager? What if my 'N' key is broken and I've mapped it to a different keystroke through xmodmap?

    You are also taking the classic open-source argument that Makes UIs Suck: well, just go fix it yourself if you don't like it! Just press Ctrl Alt Meta Shift CokeBottle, then edit >~/.foobarrc, add "MakeMyAppLessStupid=True" restart X, and you're good to go!

    Again flexibility. You want a GUI wrapped around those human-readable files? Go ahead and write one up in the favorite toolkit of your choice. Qt, Tk, wxWindows, Xlib, Motif, whatever.

    I take that stance because Open Source works, and has been proven to work well for over a decade. As Linus has said before, If you don't like it, you're entitled to double the purchase price back.

    Why does everyone expect the Open Source community to just cater to them? Why do they think we do this for THEM? We do not work for you. You aren't paying my salary. You have the code. Here's how this works:

    1. If you don't like what it does, fix it.
    2. If you don't want to fix it, help someone else to fix it.
    3. If you don't want to do that, pay someone to fix it.
    4. If you don't want to do that, find something else to use.
    5. If you don't want to do that, then you have absolutely no grounds to complain.

    I should write a HOWTO or whitepaper on this, the attitudes of everyone treating the Open Source and Free Software developers as a big pool of "free" development talent is really getting tiresome.

    "Hey, I like your code, but could you move the button bar to the bottom?"

    "You have the code, go ahead and change it and send me a patch. Right now, moving the button bar is lower on my priority list. Look at button_bar.c around lines 200-240 for the code to change."

    "You suck, Open Source sucks, you all suck!"

    This vomit has to stop, and it will only take force or persistance to bend the newbies back into shape. This is not our problem to deal with.

  223. Re:Doesn't acknowlege Windows' keyboard superiorit by hacker · · Score: 2
    If you want out of the box, you're probably using the wrong Linux distribution. There are roughly 157 recognized Linux distributions. I'm sure there is one which suits your needs. If not, maybe Linux isn't the solution for you.

    Just because a screwdriver could be used as a chisel, doesn't mean it's the best tool for the job. Use the right tool for the right job.

  224. Re:Doesn't acknowlege Windows' keyboard superiorit by Sax+Maniac · · Score: 1
    I think you misunderstand me. I am not saying open source sucks. I'm saying very many OSS developers give little heed to usability, and that damages the way "ordinary" people see us. Yes, I said "us".

    In my original reply, I said I am an open source developer. However, I also believe in usability for non-experts, which means that keyboard navigation has the be there by default. That means keyboard navigation has to work for people who don't know how to recode and recompile applications, learn XUL, or manually edit config files to make things do what they want.

    My point is that if it's done inside the toolkit, then things will Just Work even if the developer doesn't forget.

    User-hostile attitudes like yours ("bend the newbies back in shape") will do nothing to get open-source more widely accepted by a larger, nontechnical audience.

    Further, a proper set of default keyboard mnemonics will not override any shortcuts you have setup in your window manager. Window managers rule the roost in X programming, and if it binds a key, then it simply doesn't deliver the key to the underlying application.

    It would save developer time manually doing it, not effect power users who manually need to override things (quite easily done via X resources, wm configuration, etc) and help people who are used to Windows where you have better keyboard navigation.

    --
    I can explanate how to administrate your network. You must configurate and segmentate it, so it can computate.
  225. Aqua is useless toy by axxackall · · Score: 1
    Today is Sep 10 2002, a decade after GUI came to first Apples, OS/2s, Windows and X11 terminals. Years of usability and style wars. Have we decided yet about color, fonts, shapes and layouts? Not yet? Then we certainly very lazy, stupid, disorganized.

    But actually I don't think so. I think we, users, have already decided that don't care too much about what styles will be delivered by default in our OS, especially, when we can change them. We care more about available applications, stable work and interoperable integration.

    Mac OS before X has real problems with with available applications, compare to Win32. Mac OS X is even worse. Go to te nearest shop and check out yourself. Then double check on the web. Mac OS before X was terribly unstable and very crashing - it was the most unstable GUI on the market. OS X is not perfect either, compare to *n*x. With death of OpenDoc (thanks, Steve) nothing close to COM or CORBA.

    So, what's left to Apple in attempt to save Mac OS? As usually - appealing to style and to snobish users. Mac OS was, is and will be pretty useless expensive (because of hardware) toy until Apple will done or both of the following:

    • either will fire Steve Jobs, the man who failed to bring any market succes to Next, and think more about applications, stability and interoperability (back to OpenDoc?),
    • or will give up Aqua source code, letting OSS to migrate it into X11, and keep as a hardware vendor.
    Meanwhile I advise to use Linux/PPC (YDL, RH or others) as much better OS than Mac OS (including OS X).
    --

    Less is more !
  226. nope, afraid not... by zhobson · · Score: 1
    Both iTunes and the Finder in Mac OS X have context menus for songs and files, respectively. You can ctrl-click or right-click to see them. In fact, despite your unimformed (possibly out of date?) opinion, *most* applications for OS X have context menus where they're appropriate, including the apple ones. Just plug in a damn two-button mouse if you don't like using hte control key, but don't claim there are nocontext menus. You would be wrong.

    However, windows often takes the right-click stuff too far. Some things in the Windows interface (some tray icons, network status comes to mind) can *only* be operated with a right-click. A "normal" click does nothing. Stupid stupid stupid.

    As for keyboard navigation, Windows has been ahead on that front for far too long. It wasn't until the most recent release of OSX that keyboard navigation can be made to work the way it ought to.

    -zack

  227. Re:Doesn't acknowlege Windows' keyboard superiorit by Loligo · · Score: 1

    >Launch any gtk+ application, like say...gimp.

    [ snip ]

    >Now hit Ctrl-N
    >Now hit Backspace
    >Now hit Ctrl-Alt-Shift-N.

    Wow. How INTUITIVE!

    That's much easier than having logical consistent shortcuts in the first damn place.

    -l

  228. Re:Point 9... by ChristTrekker · · Score: 1

    Ditto with what the other replies said.

    Also, it's not obvious what the two buttons do. Which one is the "plain" button and which one is the "scientific" button that I can ignore for now?

    A possible solution would be for both buttons to default to the same function (normal click) unless the user goes into an option panel and enables contextual menus (or whatever) with the 2nd button.