Slashdot Mirror


Mac OS X Desktop and GUI Design

Khelder sent us a nifty little bit about the MacOS X Desktop. It talks quite a bit about UI Design (mirror) from a Mac-Centric but also a general perspective. It's quite interesting stuff for anyone into MacOS-X, but also it has lots of practical stuff for anyone who's ever tried to create a usable theme for one of today's modern window managers.

21 of 348 comments (clear)

  1. Tog's the man by cei · · Score: 4

    It's worth noting that Tog, who wrote the article that's linked to, was one of the (if not the only) designers of the original Mac OS GUI. If anyone has a foundation for constructive criticism of a GUI, this man does. If I were Jobs, or anyone else at Apple for that matter, I'd pay attention to what Tog has to say.
    ------
    WWhhaatt ddooeess dduupplleexx mmeeaann??

    --
    This sig intentionally left justified.
  2. Re:Actually, with respect to GNOME/KDE by John+Allsup · · Score: 3
    While my friend and I read the article, we both thought the same thing: GNOME (and to a lesser extent KDE) are both flexible enough to allow you to create a desktop with most of the ideas that the author had about the perfect desktop.
    Consistency? If the two gnome applicatons run on different hosts, what decides the appearance? (and how is it made uniform across the two applications?). GNOME doesn't do this at present, and the CORBA system won't help, since it isn't possible to move binaries across incompatible processors (i.e. you cannot just copy any style files needed from one machine to the other, and the screen-end of the UI (aka X) is powerless to help since all it knows about are the rectangles)
    For instance, you could put any gnome-panel on any of the sides of the screen and have any buttons or taskbars or menus or documents or anything on them you darn well please. You could make them any size, and have them autohide at any speed.
    content -- How, for example, can you have one of the bars correspond to open applications (i.e. GIMP, netscape, etc.) and another to open documents? you must remember that the GUI upon which the panel rests knows virtually nothing about what is on the screen.
    With both QT and GTK, I know that you can "rip" toolbars out of their default position and move them into a vertical position on the right or left, just as the author suggested.
    At present only possible at a per-window level. How do I put the 'main toolbar' for the 'currently focused document' on the left (such that it updates as I focus a different document)?
    How do I put the menu for the current application at the top of the screen? How do I add some global options to the menus?
    As far as the round menus go, I just don't know what he was talking about.
    Also known as 'Pie menus' think of a circle appearing at where the mouse was clicked, subdivided like a pie chart, such that you, say, go left for formatting details, right for copy.
    But, with differnt themes of the respective toolkit, one cold put thick borders on buttons.
    Thats eye-candy, nothing more. You can't change the feel or logical arrangement of a GNOME or KDE application with the theme alone.
    In short, I agree with you as far as UI designers knowing UI and learning about it. That's obvious, it could always help. But I feel that the inherent flexibility that GNOME and KDE provide go a long way to making the UI usable,
    Pardon?? (All I've ended up using is Sawmill, wterm and Xemacs.) There is NO global scriptability for GNOME applications, and similarly for KDE in 1.x. KDE 2.x may be different, I hope so.
    There is little flexibility at the application level (like you get with various Windows applications -- GNOME and KDE applications aren't mature/bloated enough for that, and wouldn't get sufficient development anyhow)
    no matter what you preferences or prejudices or habits or preconcievied notions of what a UI should be.
    If your preferences or prejudices relate to simplicity of design, overall thought of design, plans for future, etc. then I'm afraid that that just isn't the case. what needs to be stressed, and isn't is Flexibility, Reuseability, possiblities for Customisation/Integration at the component level -- currently KDE 1.x and GNOME 1.x have no real concept of a component level.
    While GNOME and KDE can be improved (what can't be improved?), they also deserve a high-five for their work so far.
    True, but it is all too often that the people in charge see the cosmetic factors in their competition, and go all out to emulate those and only those without the thought that has gone in to the rest of the design of what they aspire to copy. The moral of this story is: Think, Think and Think again before you code something that you want to put out (TAI -- Linus didn't think about global users when starting Linux, and didn't distribute it until it was going somewhere, and he's stuck to his aims ever since.)
    John
    --
    John_Chalisque
  3. Re:Agreed. by Darchmare · · Score: 3

    Re: #1, blame Be. LinuxPPC, Yellow Dog Linux, etc. didn't have much trouble. If Apple is so afraid of the competition, they'd have never released Darwin. They probably wouldn't have moved to ROM in RAM either.

    Be has its own reasons for switching to Intel, and shifted the blame elsewhere for their own convenience. If they were expecting free R&D from Apple they should have expected otherwise. Not to mention their investment by Intel - Be's recent (ie. within this month) announcements seem to indicate that they are at the mercy of their shareholders.

    Seriously though, why would Apple care? BeOS running on Apple hardware doesn't lose them any money. You're assuming a murder when there wasn't even a motive.

    Re: #2, current share prices, increasing marketshare, and sales numbers indicate otherwise.

    Re: #3, it's subjective. Nobody in the public has even used it, anyhow.

    Re: #4, hard to say. Refer to #3.

    ...if you want to point out mistakes, try not carefully introducing cloning in '88 or '89 (you can blame Jean-Louis Gasee of Be for that one). How about Copland? How about over-pricing?

    - Jeff A. Campbell
    - VelociNews (http://www.velocinews.com)

    --

    - Jeff
  4. Re:Out of touch? by Darchmare · · Score: 4

    Actually, there are a large number of Mac users (myself included) who have some reservations with the new UI. It's hard to tell until we actually get to sit down with it, though.

    I'm cautiously optimistic, but there are a number of people who have had major issues with what Apple has shown so far. Tog, who worked at Apple for 14 years, is one of them. I personally think Apple threw the screenshots out for public consumption as a sort of trial balloon - they've done this before. Given that there are 5-6 months until release, they've got time to make the kind of minor changes people are advocating.

    Anyhow, please don't stereotype Mac users. We don't all agree with everything Apple does, and aren't nearly as blind/conformist as you think we are (witness the deafening roar of bitching Mac users erupted in when QuickTime 4 was released).

    - Jeff A. Campbell
    - VelociNews (http://www.velocinews.com)

    --

    - Jeff
  5. Re:Out of touch? by oneirine · · Score: 3

    I'm not sure I like the new UI terribly much myself, but there is a hell of a lot of impressive technology behind it. I'd have to actually use it to know for sure, but it looks like too much gaudy eye candy for my taste. I'm hoping there's a Platinum Appearance that one can switch to if one desires.

    There's an article on ars technica that another poster provided a link to, which goes into all of the swank new technology behind the eye candy. It says that PDF is a superset of PostScript, which isn't exactly true. PDF is a subset of PostScript with some new onscreen features added like forms and hyperlinks. Eventually PostScript and PDF are going to be pretty close to merged - Adobe's PostScript Extreme engine is a PDF RIP (PDF to print, with no PostScript in between) and a PostScript to PDF converter.

    There are a couple things about Display PDF that aren't mentioned in the article that are extremely cool. GDI and QuickDraw are the current systems for onscreen display on Windows and the Mac OS, respectively. On Windows or the Mac, if you copy anything other than text from one app to another, you are copying not the original file, but GDI or QuickDraw commands. And most non-desktop publishing apps use GDI or QuickDraw to print, which causes a couple of problems. GDI and QuickDraw are both RGB, which throws color off completely if you copy a CMYK TIFF from Photoshop into Quark or copy an EPS with spot colors from FreeHand into PageMaker. And GDI (and to a lesser extent, QuickDraw) is not at all friendly to PostScript printers.

    PDF (as of version 1.2) understands CMYK and it understands spot color channels. PDF is friendly to non-PostScript and PostScript printers alike. Which means that non-desktop publishing apps will suddenly print much nicer to PostScript printers, and it means that copying and pasting from one desktop publishing app to another just may stop being the Extremely Bad Thing that it is now.

    Oh, and because Mac OS X is based on NeXTStep is based on BSD, for the first time I'll be able to do my desktop publishing on a real OS. No more stopping to allocate more RAM to FreeHand or less to Quark; no more crash and reboot.

    In the same way that I tolerate the bright gaudy blue of the G3 on my desk at work, I'll probably learn to tolerate the jelly bean buttons and the jewel-bright scrollbars of Mac OS X.

  6. Good article, a few problems by crayz · · Score: 3

    I can't believe this guy didn't know to hold option to close windows behind you. That for me is one of the most important time saving features, but it gives the user the flexibility to leave open the windows he wants open also.

    In addition, in the MacOS the command he didn't know is just that, the command key. Hold it and you can move or windowshade(minimize) background windows without switching to them.

    Apple tells users shortcuts very clearly in it's help system, just go in there and search, you'd be surprised how many things you can do just by holding a button.

    But anyway, he definitely raises some valid criticisms of OS X, and I definitely don't want to have a "Finder/Browser" type file navigation system. I also think Apple will be total idiots if they don't include a way to use something that is almost exactly like the current platinum look, or at least have a theme system that would let a third party do that. There are some bitter arguments going on in the MacOS community right now(www.maccentral.com/forum/) about the OS X interface, and no matter what Apple does it is going to piss off a whole ton of people.

    Oh, BTW:

    system folder: 5,138 files
    total on main HD partition: 29,957 files

    Wow.

    1. Re:Good article, a few problems by Foogle · · Score: 3
      I have to say that, for all the focus it gets here in Linux-world, themeable windows management is about the last thing in the world that matters. You might think that Apple - King of the UI - should be more concerned with this sort of thing than other people, but I feel quite otherwise. Let me explain.

      Themes (as they stand on our desktops today) are nothing more than eye-candy. Eye candy is nice (that's why people obsess over wallpaper), but it's hardly the end-all of UI. It's the actual *interface* that is the bell-ringer for a UI. It doesn't really matter what it looks like (provided it isn't visually distracting), so much as how it works.

      Take your average E-theme for example. Most of them just change a few pixmaps here and there. Nothing fundamentally different about your Desktop, changes when you alter a theme. Maybe you click somewhere else to close a window. BFD. Themes don't change how the layout of my application looks. Themes don't control what my filemanager looks like. Themes don't tuck me in a night...

      Okay, forget that last one (I've heard that some of the new Sawmmill themes do just that). What's my point? I'd rather Apple/Englightenment/KDE spent their energy in developing a more usable *interface* than a prettier one. And, actually, I think Apple has done (and will continue doing) just that.

      -----------

      "You can't shake the Devil's hand and say you're only kidding."

  7. Attention GNOME/KDE developers! by ywwg · · Score: 4

    Do _you_ know Fitts's law?

    GUI design has been well researched by Apple and others, and the developers of the new desktops should actually read this stuff. It seems that most of the features included in both desktop environments seem to be added because they are "cool" or they are what a particular developer thinks is best. If everyone makes sure that they are playing by these rules, we can ensure that both environments are superior in speed and ease-of-use to both windows and mac.

    1. Re:Attention GNOME/KDE developers! by John+Whitley · · Score: 5
      Better yet, how about the GNOME/KDE developers get someone on board with real, hard-core HCI design experience who can do a comprehensive analysis of usability issues within these environments? Then follow it up by writing a professional-grade book documenting User Interface programmer's guidelines, ala the similar documents from Apple, (the defunct) Go Corp., and so on.

      Realistically, those involved in designing user interfaces for Open Source projects should take it upon themselves to invest in some good UI books. Ben Shneiderman's Designing the User Interface, 3rd Ed. is a good starting point. Harold Thimbleby's User Interface Design, out of print, is a good book for the quantitative side of HCI, e.g. Fitt's Law and other known metrics relating to user interfaces, if you can find it. Wander through the HCI stacks of your local university library, raid graduate level HCI professors' web sites for other suggested papers and books to read. Shell out for a membership to the ACM SIGCHI -- surf through the CHI conference proceedings for good UI nuggets and broad-based UI design principles.

      I also find it amusing how these great Linux user environment projects got started off -- with noone seemingly having any understanding of UI design at the helm. What sort of user experience are we really building for Linux? The problem is that no one really knows. This business of "built by hackers, for hackers" doesn't wash, as few hackers I've known have any clue whatsoever about user interface design issues. This is a substantial field, with many solved problems, yet instead of Using The Source (i.e. doing the readily available background reading) many Open Source projects continue to reinvent the UI wheel -- badly.

      That said, there have been some successes, but mostly in individual isolated projects. Nothing on the scale of providing a comprehensive, flexible, yet unified user experience..

  8. Re:Is he nuts? by smileyy · · Score: 3

    The Mac OS has always been limited to 31 character filenames. This is, I believe, derived from a limitation in HFS, the Mac OS file system. HFS+, which debuted with Mac OS 8.1 offers support for 255 character file names. However, the OS has not been updated to support 255 characters, due to legacy OS and application issues.

    The collapsible directories *have* been there -- I suspect he's talking more about this method being the default, rather than the freeform/gridded icon layout that is currently the default with the Mac OS.

    Where Tog I believe missed the mark (or perhaps he did mention this, I don't recall) and the Salon article certainly did, is that the old-style Finder is still present in Mac OS. The NeXT-style browser is simply the default, and offers a new option. From what I can tell, the NeXT-style is oriented at newer users.

    --
    pooptruck
  9. A new invention... by Anonymous Coward · · Score: 4

    I have, I think, created the most accurate random dice throw simulator ever known to the computer world. It is held inside a tiny black box, with a serial connection and an Ethernet port.

    Questions please?

    Q: How does it work?

    A: It is sent signals from the programmer that set the method used to determine the result, and to get a new throw.

    Q: What do I have to do to use it in program X?

    A: Sending it a zero over the serial port will get a new random throw. Sending it any other number from 1 to 11 will set the method it uses.

    Q: What methods does it use?

    A: The number sets it, and it increases in randomness with the number; i.e. 1 just does a fairly simple random generator, while 10 takes a minute to mathematically simulate the dice on an atomic scale as it flies through the air!

    Q: Why does it need Ethernet then?

    A: That's for when you send it the signal 11, the most random mode. It posts a comment to Slashdot, enters a wait state for two hours, then comes back, takes the moderation score and adds 1.

  10. Re:no, you are by Darchmare · · Score: 3

    Actually, he's partially right. Within the last few years - around the release of MacOS 8.1 I believe - Apple began transitioning people over to the HFS Extended (HFS+) file system. HFS+ does indeed support long (at least 255 character) file names.

    However, the functionality is not apparent in the current MacOS. I guess Apple figured poorly coded apps might break, and there isn't really a good way to display filenames in the Finder with that long of names (it looks a bit unwieldly).

    My understanding is that long filenames work just fine in OSX.

    - Jeff A. Campbell
    - VelociNews (http://www.velocinews.com)

    --

    - Jeff
  11. Re:Offbase by Darchmare · · Score: 3

    Xerox was paid by Apple in the form of stock options for what Apple gained by visiting their office.

    Here's an account by Jef Raskin, one of the original Mac developers (much of the Mac's concepts came from his research from much earlier).

    - Jeff A. Campbell
    - VelociNews (http://www.velocinews.com)

    --

    - Jeff
  12. Tog's questionable judgment by ~k.lee · · Score: 5

    I used to respect Tognazzini a great deal. However, close reading of his writing, over an extended period of time, has led me to believe that he has questionable judgment about many issues. Just examine his article, How Programmers Stole the Web, where he claims that:

    • BASIC is the paragon of computer programming languages, because it uses a "simple" state-machine paradigm (I can only assume he means programs composed of global variables and GOTOs, like a finite-state automaton).
    • JavaScript is counterintuitive because it (a) resembles C++ instead of BASIC and (b) the code must be enclosed in comments (he thinks an XML-based inline programming language would have been the better choice, apparently ignorant of how bulky and clumsy pure XML-syntax programming languages like ColdFusion Markup Language (CFML) have turned out.)
    • Tognazzini calls it "inexplicable" that VBScript is not cross-browser and cross-platform, and seems to imply that this is due to engineers' habits of "enforced illogic" (which leads engineers to hate BASIC)---not on the Microsoft attempt to turn the Web into their proprietary fiefdom.

    These are only a sample of the glaring Deep Wrongness in the article I link to above.

    In addition, Tog is a relentless Apple partisan, despite his objections to the new Aqua interface. This clouds his perception of all Apple-related issues. For example, among other things, he says in the Aqua/OS X interface article that "Apple could argue, and few would deny it, that Apple was first and Microsoft is the one who made things difficult by failing to accurately copy the Mac interface." Ignoring, of course, the fact that Microsoft would have been perfectly happy to copy the Apple interface exactly, except that Apple is one of the most litigious companies in the IT industry (have you seen Microsoft threaten to sue KDE over their Windows98 theme?).

    IMHO, Tognazzini has suffered from a lesser form of the same brain rot that has affected Jon Katz since becoming published on the web: free to spout off without an editor, never forced to confront dissenting opinions before publication, he has become something of an autodidact. This may seem a bit harsh, but I urge the programmers in the audience to read the "How Programmers Stole the Web" article. It reveals a great deal about the didacticism of Tognazzini's thought habits, and will probably cast a very different light on his supposedly authoritative interface design ideas.

    I once respected Tog. Occasionally, he comes up with some good insights. However, don't let his impressive resume blind you to his often misled assertions.

    ~k.lee
    --
    (remove nospam for email)
  13. Radio interview with Tog by John+Siracusa · · Score: 3

    He talks about the QT4 player, Mac OS X, and GUIs in general. Listen in.

  14. Aqua (sort of) Tested by NII+Link · · Score: 4
    It's quite a coincidence that this article should appear on /. today (and no, I'm not talking about how late it is). Today, I did a little experiment: I downloaded an Aqua-like theme for Kaliedoscope (a theme switcher for Mac OS) and this program called "Greg's Browser," which is a NeXT/Mac OS X - like file browser. For several hours I used the theme and the file browser as I went about my usual business, just to approximate what it would be like to use the OS X GUI.

    My first impression upon activating the theme was the expected "that looks cool," and I also noticed that it was a bit brighter looking than the current "platinum" look of OS 9. Not that it was a bad thing, it wasn't blindingly bright, just a little unfamiliar at first. That soon changed however, as I began to actually use it. The theme isn't the most accurate representation of Aqua, for example it doesn't have the slowly throbbing default buttons, but it did have the same "traffic light" buttons on the windows. Some have expressed concern that the buttons are too close together and that someone could miss and accidently close a window, but that did not happen to me once. I got used to the new setup very quickly (to contrast, I never seem to get used to it when I have to use Windows). In fact, I took a liking to the buttons and that pinstripe background. They aren't noticable while doing work, but when you want them you know exactly where to look.

    The other main thing that the theme altered was the icons. Even without Quartz and 128x128 (scalable) icons, the new icons look great! That's not one of the things anyone has really been arguing over though...

    Unfortunately, the theme cannot simulate translucency, shadows or the "sheet" dialogs - although from the pictures the sheets look really good. The tranclucency might need some playing with, but again I could not try it in person. So on to the browser...

    I found the browser useful for quickly navigating a heirarchy of folders - just move the arrow keys towards where you want to go. On the other hand, it wasn't so great for copying/moving files to other places - in most cases a new browser window must be opened. Of course the limitations of this browser might not be the same as Apple's, and the browser view is just an addition to the traditional icon, list, and button views. I'll probably end up using a combination them all, much like I do now.

    Keeping all this in mind, it's imporant to remember that Aqua is still in development. Mac OS X is scheduled to be released this summer (not next year as Tog said, that's when it will be preinstalled on all shipping Macs), so there's still time to make any criticisms you might have heard - that is probably one of the reasons for showing Aqua so far in advance.

    --
    -Rafi Remove the Spanish to email me.
  15. Re:Out of touch? by Darchmare · · Score: 4

    It's not hard, if the OS is designed with a single button in mind. You just weren't used to it.

    I agree 100% with the round mouse thing. I think Apple was aiming toward little kids (which seem to be able to use it, due to its size), but they should never have shipped it with their higher end systems. Same with the keyboard.

    For the record, I prefer 2 button mice, which work just fine on the Mac (you can simulate a second button on later revs of the OS by holding down control and clicking on the a file - contextual menus). On the other hand, I have been forced to support Windows users confused by the second button, so they may have a point.

    In the end, it doesn't cost much to buy a better mouse. Apple should make it a build to order option, and support both equally.

    - Jeff A. Campbell
    - VelociNews (http://www.velocinews.com)

    --

    - Jeff
  16. Use of text instead of graphical icons by rambone · · Score: 3
    I once attended a lecture by the brilliant Edward Tufte (who was lecturing on his three great visual design books), and the one point that was hammered in again and again was to "inline" information. Instead of using a silly icon or shape that users must "follow" to find the information they want, put the information right there, inlined.

    It appears that is what TOG is discussing here as well. He seems to be pointing out that Aqua places too much emphasis on the usefulness of graphical representations (which look gorgeous but do not relay much information).

    That is why I have always found primitive interfaces such as TWM so useful - more often than not, informative text takes the palce of a pretty (but useless) graphic.

    By the way, anyone who has the chance to see Edward Tufte speak should do so. For $500 you get all his books and a great lecture that was really worth $500, as hard as that might be to swallow. I can actually say that I learned a great deal about interface design.

  17. Ya know, I like it by deeny · · Score: 3

    MacOS X Server (in an earlier incarnation) was the first Unix I used on my desktop. It got me really aware that there were Unixes with good GUIs. Unfortunately, Linux lags WAY behind in the seamless integration that even buggy betas of Rhapsody had.

    I came to Linux from MacOS X and I suspect a lot of other people will too.

    Be patient little penguins. MacOS X is no threat to Linux.

    _Deirdre

  18. 3rd Generation GUI by nutty · · Score: 4


    I must say, i learned a lot from the report the Arsificial Intelligentia over at arstechnica.com put up.

    Check it here.

    Its got a great deal of info on how MacOS X and Quartz are a 3rd generation GUI, relying on vectors, and a great deal of pdf technology to speed things up. This decreases the amount of power needed to run a transformation like the genie effect by great amounts.

    Good stuff.
    /nutt

  19. Re:Boy was I wrong. by Darchmare · · Score: 4

    Actually, it's more like this:

    1. Pay Xerox in the form of Apple stock.
    2. Take a few notes on what Xerox has done. No code.
    3. Mix in a large number of ideas by Jef Raskin and others.
    4. Develop the Lisa/Mac.
    5. Bill Gates takes a look, and...
    6. The rest is history.

    Hope that clears things up a little more.


    - Jeff A. Campbell
    - VelociNews (http://www.velocinews.com)

    --

    - Jeff