Slashdot Mirror


The Roadmap to Leopard?

Alexandros Roussos writes with a link to the site MacScoop, which claims to have obtained a roadmap for the months leading up to Leopard's release. It's a straightforward article, stating how much access individuals outside the company will have access to the product prior to October. "Major build on early August - In a little more than a month, Apple's development team targets a feature-full build. The build that was provided to developers during the World Wide Developers Conference earlier this month is actually not totally feature frozen. Some minor features are currently being finished for the system. These features will arrive in the August build along with user-interface improvements, sources told MacScoop. If you expect major 'wow' features or interface changes, you will be disappointed. What we may expect is additional settings and [some] user interface polish[ing]. Among the most criticized parts of the new user interface [are] the new menu bar and Dock."

33 of 152 comments (clear)

  1. WTF? by Penguin+Follower · · Score: 4, Insightful

    Among the most criticized parts of the new user interface [are] the new menu bar and Dock."

    OK, I watched the WWDC07 demos of Leopard and I thought the new Dock and menu bar looked good. What's the beef? I've not read any "reviews" yet. No matter what happens - come October this MacPro will be running Leopard.

  2. Amazing insight! by ZxCv · · Score: 4, Insightful

    Is it just me, or is the "timeline" the article talks about not just something you could reasonably deduce, knowing where Leopard is at right now and when they plan to release it?

    Didn't seem like there was any real new info here, but maybe it's just me.

    --

    Perl - $Just @when->$you ${thought} s/yn/tax/ &couldn\'t %get $worse;
  3. The menu bar... by ZxCv · · Score: 4, Insightful

    ...seems to be the main complaint among the bits I've read. And after having used it now myself, I'd have to agree.

    Personally, I like the new look of the dock. The menu bar, however, is something I really hope they make an option. For the same reason that I (and many others) don't want or use semi-transparent windows, I don't want a semi-transparent menu bar. It's like they threw readability and usability out the window, all in the name of looking "cool".

    --

    Perl - $Just @when->$you ${thought} s/yn/tax/ &couldn\'t %get $worse;
    1. Re:The menu bar... by WhatAmIDoingHere · · Score: 2, Interesting

      I've had leopard installed for about two days now and the semi-transparent menu bar is actually pretty nice. It doesn't jump out at you when you look near the top of documents.. It's just kinda.. there, but in the background.

      The reflections from the dock are also very nice. It actually reflects everything, even video.

      --
      Not a Twitter sockpuppet... but I wish I was.
    2. Re:The menu bar... by node+3 · · Score: 2, Interesting

      I've heard it's optional (an interview with someone important at Apple (Steve?), or maybe even during the keynote). Have you checked in System Preferences? A "defaults write" command? Or maybe that feature is one of the "interface polishes" that are yet to happen.

      Regardless, I think the translucent menu is a good idea, and one that probably doesn't grab you at first, but takes some acclimation. Also, I think having it be configurable via System Preferences (or at least via defaults), is also a good idea.

    3. Re:The menu bar... by LKM · · Score: 2, Informative

      Actually, animations in Mac OS X usually serve a purpose (windows "flowing" in and out of the dock tell you where you can find them) and/or tend to only appear when they aren't annoying (menus don't "fade in" because that is annoying when you want to select a menu item, but fade out after you've made your selection).

  4. please oh please submit feedback to ADC by Gary+W.+Longsine · · Score: 2, Insightful
    --
    If you mod me down, I shall become more powerful than you could possibly imagine.
  5. Re:Uhm by WrongSizeGlass · · Score: 3, Funny

    That's basically ALL that changed in Desktop: the menu and the dock. I believe your forgot about the dewy grass Desktop image.

    Won't somebody think of the dewy grass!
  6. Agreed by pavon · · Score: 4, Interesting

    I think the transparent menu is unnecessary, and perhaps counterproductive, but not a huge deal. I'm curious about what is disliked about the dock though. Stacks seemed a nice feature, and other than that there really wasn't much to right home about. Oh actually I do have a complaint about the stack - smartly, the last item placed on the stack is the one visible in the dock, but when you go to fan them out, it become the farthest one away making it the hardest to click, even though it is the one you are most likely to open.

    I'm also curious about how they are handling mounted volumes. I noticed that they were not on the desktop anymore (yea! I hate using the desktop for anything but wallpaper). It didn't look like they were available in the dock though either. Is the finder sidebar the only place you will be able to find them now? I'd love it if they were accessible via a special stack in the dock, with newly inserted ones showing up on the top. I use DragThing right now to do something similar.

    While I'm drifting off subject, I've wondered how the shared volumes will work for large networks. Jobs mentioned that any computer will automatically be found (via netbios or zeroconf?) and will show up in the finder sidebar. What happens if you are on a company or dorm network - hundreds of computers in the sidebar? I'd hope not. Maybe after a certain number of computers, it is replaced with a "see entire network link" where you can browse and/or pick which computers should be in the sidebar.

    1. Re:Agreed by Penguin+Follower · · Score: 2, Insightful

      I,too, am interested in stacks. And Spaces. I always made use of multiple virtual desktops on my Linux boxes. Oh and since I am bad about doing backups any more regularly than twice a year, I'll probably use Time Machine as well.

      Core Animation is sweet. As is 64 bit from top to bottom.

      Oh and what's the deal with the blazin' speed of Steve's demo machine that was at WWDC07? I've got quad-core 2.66GHz MacPro that just doesn't have the snappiness of the MacPro Steve demo'ed. Is there that much of a difference between mine and a 3.0GHz (quad or 8 core) in running regular apps? I just don't see it....

    2. Re:Agreed by Firehed · · Score: 4, Insightful

      I just pray that Leopard's Finder doesn't flip out if a network share suddenly goes missing, as Tiger's does. It's enough of a pain that I need to fully quit out of Azureus and iTunes which I have configured to do all of their storage on a network drive, and it's entirely my fault. But when my computer flips shit and locks up for fifteen minutes because I unplugged the network cable before unmounting all the shares... you get the idea. An auto-mount option, preferably with location-based configuration (sort of how I use MarcoPolo.app right now, with its scripting tools) would be great, but I'd be content if it simply gracefully disconnected from network shares that have become unavailable.

      --
      How are sites slashdotted when nobody reads TFAs?
  7. Re:Please oh please oh please, DITCH STACKS! by Anonymous Coward · · Score: 5, Informative

    Bullshit. In grid mode, the icons display with file names, and a right-click gets a menu, and one of the items is to open the folder in the Finder. Yeah, there are some rough spots that need fixing up, but because of the NDA I won't go into that. But I figured I'd stretch the NDA a little when I saw blatant misinformation about dock behavior, from someone whom I'm guessing doesn't actually have the beta but is just passing on misunderstood info.

  8. Re:Please oh please oh please, DITCH STACKS! by Anonymous Coward · · Score: 2, Informative

    You're right that by default the Stacks sort by and use the last added item icon, but you can change to different sort criteria and thus a different icon will be reflected in the stack.

    It may be possible to manually change the stack icon but i haven't looked into it very much.

    Another big complaint people had with Leopard is that a previously advertised feature of screen sharing within iChat appeared to have been moved to the new Finder instead. While the Finder does indeed support screen sharing i can state that iChat appears to have the feature there too. At least there is a screen sharing button in iChat and one of the capabilities iChat 4 reports is apple:iq:rd:server and apple:iq:rd:client.

    For any XMPP devs that might read this post here's a list of all the capabilities reported when i did a service discovery on iChat:

    iChat v3 capabilities

    http://jabber.org/protocol/si
    http://jabber.org/protocol/si/profile/file-transfe r
    jabber:iq:version
    http://jabber.org/protocol/bytestreams
    apple:iq:vc:capable
    apple:iq:vc:multivideo
    http://jabber.org/protocol/sipub
    http://jabber.org/protocol/xhtml-im
    vcard-temp:x:update
    apple:iq:vc:video
    apple:iq:vc:available
    apple:iq:vc:audio
    Service Discovery (http://jabber.org/protocol/disco#info)
    apple:profile:bundle-transfer
    apple:iq:vc:multiaudio

    iChat v4 additional capabilities

    apple:iq:rd:client
    apple:iq:vc:recauth
    apple:iq:vc:ice
    apple:iq:rd:server
    apple:profile:efh-transfer
    apple:iq:vc:auxvideo
    http://www.apple.com/xmpp/message-attachments
    apple:profile:transfer-extensions:rsrcfork

    So it looks like iChat will get some new abilities. I think the ICE stuff will solve one of the major problems that Tiger users have complained about, NAT traversal for audio/video. I believe the efh stuff is encrypted file transfers but am not sure. Looks like there's no Jingle or true SIP support coming though. :(

  9. You know... by SvnLyrBrto · · Score: 5, Informative

    > I'm also curious about how they are handling mounted volumes. I noticed
    > that they were not on the desktop anymore (yea! I hate using the desktop
    > for anything but wallpaper).

    You can take HDs, CDs, iPods, servers, and mounted disc images off the desktop right now, if you're so inclined.

    Go to Finder>Preferences, or use command-comma while Finder is the selected app. From there, just uncheck the top three ("Show these items on the Desktop") boxes in the "General" pane. Bamf... nothing on your desktop but what you purposely put there.

    cya,
    john

    --
    Imagine all the people...
  10. Re:Sensible timeline? by node+3 · · Score: 2, Insightful

    How long are you thinking it will take to press a disc, stick it in a box, and ship it to the store?

    Given that FC is in Sept., and FC is the first *intended* final version, a month+ of going through fine-tuning, and a week or two of manufacturing, seems more than adequate.

  11. Re:The Dock & the Menu Bar by node+3 · · Score: 4, Insightful

    most people who use their computer move the dock to the side I highly suspect this isn't true.
  12. Re:Please oh please oh please, DITCH STACKS! by dr.badass · · Score: 2, Insightful

    . Unless I'm mistaken, stacks are HORRIBLE!!!

    You are mistaken. Both views have a "Show In Finder" option, and the grid view most certainly does contain text. The screenshots on Apple's site, as well as the keynote demo both show this, which casts some doubt on everything else you've said.

    --
    Don't become a regular here -- you will become retarded.
  13. Re:Dock 3D is a major improvement by dr.badass · · Score: 2, Insightful

    The new Dock is awesome, though. It is not 3D eye candy, it actually is 3D.

    No, sorry. It's 2D that looks 3D. You don't need 3D to create the reflection effect, or to have objects appear to be behind other objects. Also, Stacks don't work quite how you seem to think. They're just a different view for Dock folders. You can't create a "second row" of apps, for instance.

    --
    Don't become a regular here -- you will become retarded.
  14. Re:Blu-Ray & HDDVD Support? by Anonymous Coward · · Score: 2, Interesting

    Apple has backed Blu-Ray for a very long time now. They even joined Board of Directors of the Blu-ray Disc Association. Thus, Bu-ray support is a certainty. That said, however, rumors have it they will also hedge their bet by supporting HD-DVD.

  15. The problem with the new dock by alms · · Score: 3, Informative

    is that you can't tell which applications are running and which are not. In the Tiger dock, running applications have a very visible black triangle under them. In the Leopard dock, there is a much more subtle shadowing effect that indicates running applications. It needs to be less subtle.

  16. Re:Multitouch: Already there in Mac OS X 10.4 by atrocious+cowpat · · Score: 2, Interesting

    "What about multitouch? -- It's already incorporated into the iPhone interface, "

    Actually you have (limited) Multitouch-capability already in OS X 10.4. The MacBooks' and MacBookPros' Trackpads will interpret actions you do with two fingers differently than actions you do with one finger. Examples:

    click [one finger] = "left click"
    click [two fingers] = "right click" ("control click" for you 1-button-mouse-maccies ;) )

    drag [one finger] = nothing (unless trackpad-button is depressed, then it's "drag selected item")
    drag [two fingers] = scroll horizontally or vertically, depending on direction of drag

    The latter function (two-finger-scroll) is actually one of the nicest input-features i've ever encountered, right on par with the scroll-wheel (slightly better even, because it works horizontally too, without having to press any modifier key). I had heard about it and could not quite imagine how this would be good, but once I tried it I was hooked immediately.(*)

    I, too, hope that Apple will expand the Multitouch-capabilities of their OS/Trackpads, but the basic functionality is already here.

    (*) Yes, I know there were Trackpads before with dedicated strips for scrolling (or software, that would create a "scrolling-area" on your trackpad, but this works without having to think about where you put your fingers (and it works seamlessly in the x/y-directions).

    --
    sig? Oh, that sig...
  17. Patterns are bad by ghutchis · · Score: 3, Informative

    The more small patterns you have in the image (or section of the image near the top), the worse the menu bar looks.

    I have my Mac set to change the desktop once a day. At first, everything was great -- it was picking images with sky at the top -- essentially solid color. Then it brought up a zen rock garden, which is one of my favorite images.

    On Leopard, it makes the menus unreadable. The dark/light pattern in the rocks makes it impossible to find letters in the menu. I've also found many pictures will make it difficult to read or identify menu extras on the right side of the screen.

    They need to fix this ASAP. Oh, and the new Finder icons are horrible too. There's zero color contrast to identify the different folders.

    1. Re:Patterns are bad by WhatAmIDoingHere · · Score: 2, Informative

      I have something like a star field cluster for a background. Pretty much a bunch of black with greenish white dots. There's some of the cluster behind the "Help" menu but it doesn't keep me from being able to read "Help" and it doesn't look bad, either. The regular menus being transparent over my open document/browser/whatever actually is pretty cool.

      --
      Not a Twitter sockpuppet... but I wish I was.
  18. It's like Copeland all over again! by Bones3D_mac · · Score: 2, Insightful

    Personally, I think Apple has finally lost it after several years of producing innovations that have changed much of the world. The fact that they are touting a transparent menubar as a major feature suggests their idea pool for MacOS X development is starting to collapse in the same way Copeland did in the mid 90's. They've become too focused on presentation and eye candy, rather than improving what goes on under the hood.

    Of course, that isn't to say MacOS X hasn't been a mess in terms of the Human Interface Guidelines (on which the Mac OS was based) since the earliest public releases, but making the one visual concept that has remained consistent and immediately recognizeable in all versions of the Mac OS almost completely invisible has to be the single worst offense to date. The menubar was supposed to be a fixed (and always visible) reference point for the user to rely on while the rest of the desktop evironment continually changes during each session of use. It's the one part of the OS that keeps everything else organized and easily understood.

    Aside from Leopard, we'll soon have the iPhone to contend with, which is sure to be a nightmare once the early adopters get past the hype and Steve Jobs' Reality Distortion Field and start to realize just how confining the device really is due to all the red tape that comes with it. It will probably sell as expected, but in the end, it may go down in history as on of the worst products in Apple's history, next to the Lisa, as a result of all the artificial limitations imposed upon it that kept it from being the killer product everyone really wanted it to be.

    By the time this all plays out, Steve Jobs may get ousted for both 10.5 and the iPhone, much like Gil Amelio was due to Copeland and mac cloning.

    --


    8==8 Bones 8==8
    1. Re:It's like Copeland all over again! by mmeister · · Score: 5, Insightful

      Wow.. do you absolute NOT know what you're talking about.

      Copland failed because it was much too ambitious. They wanted 100% backward compatibility + protected memory and other modern OS goodies.

      As for the menu bar reference point -- it is still fixed, as always and is still quite visible. There may be some bugs where certain images make it disappear, but I'd call that a bug at this point. It isn't a major feature (the feature is the improved desktop which focuses on removing clutter so you can see more of your digital images). Stacks is a big deal. Once you actually start using it, you'll realize it vastly improves the dock.

      Why would iPhone be a nightmare? Sure, there's the Steve RDF, but it seems pretty clear that for the first time, an emphasis on usability has been placed on a smart phone. I'm sure that there will be issues, but they'll be solved with software updates and I think calls that this will be a flop are incredibly premature. I'm sure you want it to be a flop, that is clear from your statements.

      Steve Jobs will not get ousted for 10.5 or iPhone.

      I think Mac OS X 10.5 is going to be a very solid release. Perhaps it is not as end-user feature laden as some would like, but it has plenty of useful features that will make it worth the $129 upgrade. More importantly, the features and functionality added for developers means that there will be some very cool apps coming down the pipe.

      The iPhone will do well. The secret is that much of the functionality is in software that can easily be updated via syncing with iTunes. Bugs can easily be addressed. Improvements can be made and sent out much in the same way Apple does for its standard applications. I'm sure there will be glitches (when several hundred thousand people start using something, there are bound to be edge cases that come up). And the 2nd generation will do even better.

      I predict that Apple will have an iPhone battery replacement program (much like for the iPod, possibly better since you'll likely take it to a AT&T store) which, while not resolving the user replaceable battery, will relieve the anxiety of what to do after two years of battery use.

      In the end, I'm sure there will be some limitations, as this is a 1.0 product, but those limitations will be worked out. There will be some very vocal nay sayers out there, but based on what I've seen thus far (and my own experience with previous phones), Apple is changing the game here. It is putting emphasis on the end user experience -- something that's apparently new to the industry -- and I think they will be successful because of it.

  19. Re:What I'd like to know by Anonymous Coward · · Score: 3, Informative

    Can't speak for the final release, but the WWDC beta has the following versions:

    apache - 2.2.4
    bash - 3.2.9(1)-release
    ksh - Version M 1993-12-28 s+
    openssl - 0.9.71
    perl - 5.8.8
    postfix - 2.4.0
    python - 2.5.1
    ruby - 1.8.6
    sqlite - 3.3.17
    svn - 1.4.3
    zsh - 4.3.4
    x11 - Xquartz server based on X.org Release 7.2, built on ?P

  20. OSX is Mac OS X, with extraneous bits removed by Gary+W.+Longsine · · Score: 2, Interesting
    The iPhone operating system is OS X, and it's probably a Leopard variant. Although I haven't seen reliable indications of this, I'm sure such details will emerge after people get their hands on the iPhone. There are a few hints that iPhone's OS X is probably Leopard based, however. Certainly the iPhone could have been developed *without* some of these technologies, and some could have been back-ported to Tiger, but it seems more likely that iPhone is based on Leopard code. Some of the hints include:
    1. iPhone has a 160 dpi screen, and Leopard has been revamped with Resolution Independent Displaywhich makes support of panels with higher pixel densities essentially automatic, compared to tons of extra work required without it
    2. DTrace and XRay would be extremely helpful in deep performance tuning required to get excellent performance on handheld class hardware. These tools were undoubtedly used to optimize many modules of the Leopard codebase. Optimizing Tiger using other tools for the iPhone is certainly possible, but would have been more resource intensive (skilled labor).
    3. Objective C 2.0's garbage collection feature would be handy to help ensure efficient overall use of memory on low-memory devices like handhelds
    4. multi-threaded network stack is probably useful on a device that runs multiple network connections concurrently (WiFi and cell phone voice network)
    5. Applications on the iPhone, notably Safari and Mail, appear to perform in a much zippier fashion than their counterparts on Tiger, particularly on a lower-horsepower device. These applications have undoubtedly been optimized using XRay and DTrace. Heck you can tell this just by watching the iPhone demos in the keynote and the commercials, but also by using the Safari 3 beta, which is much, much zippier than Safari 2 was.

    You are correct that this approach using a common code base for a mainstream OS and the "mobile version" is not true for Windows. Windows CE/PocketPC/Windows Mobil are radically different animals to the Windows 2000/XP/Vista operating systems that were contemporaneous with them. The early versions were actually forks from the Windows 95/98/ME code base.

    This common code base between Macintosh and iPhone will prove to be a tremendous advantage to Apple as the OS X platform evolves. By contrast, Symbian has fractured into at least 3 different systems, Windows Mobile is a forked codebase from an old version of Windows, and there are at least several different Linux forks, each with a manufacturer custom middleware layer on top. It will be harder than people think for other cell phone manufacturers to catch up with, and keep up with, iPhone's OS X.

    It's very likely that OS X has a great deal more in common with Mac OS X than you think. In fact, it's very likely to be built from the same source, managed in the very same respository (well, certain modules may have been forked during the secret R&D phase, but if it isn't already, it will be merged back in soon enough). I know that this is a little hard to believe, because there are too many examples to the contrary, which make it seem as if this must be "hard". However, it's really much more labor intensive to do this "wrong", e.g. to fork a code base then try to constantly back-port all the fixes and enhancements you get from the energy going into the main code branch.

    If you want to better understand how this can work, examine two things. (1) The distinction between Mac OS X and Mac OS X Server is non existent. It's the only commercial operating system in the world where that's true. (One could argue that any version of FreeBSD or Linux can function equally well as a server and a client, but one could also argue that neither really functions all that well as a desktop/notebook client OS). (2) Consider the way that Cocoa applications are built for both PowerPC an

    --
    If you mod me down, I shall become more powerful than you could possibly imagine.
  21. WWDC 2007 Keynote vs. Leopard feature set by Gary+W.+Longsine · · Score: 2, Insightful

    Everybody has their undies in a bunch about the 10 things the Jobs showed in the recent keynote. Those things were carefully chosen by Jobs, likely with a great deal of input from other executives and managers at Apple, probably more such input than any keynote ever before. Why? Because Apple was trying to motivate the 5000 developers at WWDC to be more innovative with their use of some of the Mac OS X technologies. Apple focused that keynote on things like creative use of CoverFlow in several places, and other uses of CoreAnimation, to get developers to think more creatively.

    Leopard has a bunch of interesting OS level features (some described here: Leopard and here: Leopard Server

    Your complaints about the menu bar are valid, but can be easily solved by adding a user preference setting to the Dock for transparency level, and making the default be "very nearly opaque".

    I think you're missing the point about the iPhone.

    --
    If you mod me down, I shall become more powerful than you could possibly imagine.
  22. Finder flipping out when network shares go missing by Gary+W.+Longsine · · Score: 3, Informative

    I think this issue of the Finder flipping out is due partly to the finder and partly due to the automounter (autofs), both of which appear to have received a major overhaul in Leopard. Autofs has apparently been threaded. If the Finder is instrumented with NSOperation (I can find no publicly available documentation to that effect), then the combination of those efforts should be a "Finder" which appears to be much more responsive than on previous versions of Mac OS X.

    --
    If you mod me down, I shall become more powerful than you could possibly imagine.
  23. Mounted Volumes on Desktiop is a Finder option by LKM · · Score: 2, Interesting

    Showing mounted volumes on the Desktop was always a Finder option. Maybe Steve simply had it turned off. I think early versions of OS X did not have this option, and Mac users complained, so Apple put it in.

  24. Re:Finder flipping out when network shares go miss by Guy+Harris · · Score: 2, Informative

    I think this issue of the Finder flipping out is due partly to the finder and partly due to the automounter (autofs), both of which appear to have received a major overhaul in Leopard. Autofs has apparently been threaded.

    If nothing is in the process of being automounted, the automounter has precisely nothing to do with any Finder hangs.

    With the old single-threaded automounter, if a mount was in progress, the automounter would be incapable of responding to any other requests. As the old automounter was a user-mode NFS server, which handled /Network/Server, as well as directories such as /Network/Applications and /Network/Server, those paths referred to symbolic links in the file system implemented by that server, so any references to them turned into requests to the automounter - which, as noted, would hang, if the automounter was in the process of trying to mount a file system from an unresponsive server (which includes servers that aren't on your network because you've disconnected from the network on which they reside).

    If, however, the automounter wasn't in the middle of a mount, it could respond to those requests. However, if the server in question was unresponsive, subsequent NFS requests would hang.

    With autofs:

    • references to already-mounted file systems would be handled entirely by the autofs kernel code, without involving the automount daemon at all;
    • references that trigger a mount, because they're referring to a file system not already mounted, would be handled by a thread in the automount daemon separate from threads handling other mounts, so if the mount hangs because the server doesn't respond, other references that involve the automount daemon can still make progress (although if they also try to mount from an unresponsive or unreachable server, they won't make much progress until they time out).

    So switching to autofs and a multi-threaded automounter will help some hangs - but not all hangs.

  25. Translucency sucks by Steeltoe · · Score: 2, Informative

    Translucency really, really sucks. It is distracting and makes it harder to read. Just look at Word for Mac or iTerm. The translucent effect just makes it harder on the eyes, while providing NO benefit. It should really be optional overall.

    Now, MenuShade is a program that gives your menu a less-brighter shade. THAT is a good idea, because it prevents the menu from burning in your fancy LCD. Im using it all the time, and it is easier on the eyes, AND simple to read.

  26. Re:The Dock & the Menu Bar by boscosmith · · Score: 2, Informative

    I maintain 12 macs for different friends and family. The people using them are not power users, but they know how to configure their machines. Anyway, of the 12, ONE person moved their doc to the side. Something to do with Final Cut Pro and wanting to have the video time slider at the very bottom of the screen. Other than that, everyone leaves it on the bottom.