Google
 


Subscribe to The Tech Night Owl Newsletter

*Required



 

Archive for March, 2007


It’s the Little Things that Irritate!

Wednesday, March 28th, 2007

For a long, long time now, you’ve been told that Apple designs the best user interfaces. They “just work,” and the learning curve — such as it is — is relatively short. Of course, that doesn’t explain the consistent sales of “Dummies” books about various and sundry Apple products through the years, but compared to other personal computing platforms, Apple is far and away the best.

But it’s not perfect, and every so often, I want to change the things that come out of left field to irritate me and others. I realize that you may not find what I have to say inspires such feelings, but that’s why we offer a Comments panel here, so you can chime in with your own annoyances.

It’s also possible that some of these problems can be resolved, and I’ll start with one, since the matter managed to upset one of my clients until I revealed the solution. You see the client in question, Jack, is a long-time Mac user and a senior citizen who demonstrates that the age of 82 is the new 60. He’s bright, active, and there’s very little in his demeanor to show his age, except for an occasional slight shaking of his hands.

After I configured his new 24-inch iMac, he asked about the Front Row remote, which I proceeded to demonstrate for him. Since my 17-inch MacBook Pro was just a few feet away, it also received the signal, and he wondered aloud how he can sort that out if he got a new Apple notebook.

Well, there’s an easy solution to this, which involves locking a remote to a single Mac. In case you haven’t heard of this little trick, it’s done this way:

  1. Place the remote to within three or four inches of your Mac.
  2. Take the remote and point it at the Apple logo.
  3. Now press and hold both the Menu and Next/Fast-forward buttons for five seconds.

That’s all it takes, so one irritant was quickly resolved, but there’s always more where that came from. Jack wanted to set up his new Logitech MX-400 mouse to zoom an application window to fill the screen, only the various options in the device’s preference panel wouldn’t perform that function. You see, its “zooming” was limited to controlling an application’s built-in Zoom function for the contents of a document. He sighed and went on with his work.

Earlier that day, when I turned the iMac on for the first time, I asked Jack to sit in his office chair, while I showed him how the built-in iSight camera worked as it took his picture during the setup process. Now Jack isn’t enamored of cameras, but that’s not the issue. Consider the office or educational environment where cameras and remotes aren’t welcome. Yes, you can lock up the remotes, but the cameras? Well, you can set up Tiger’s Parental Controls feature to block access to applications, such as iChat and Skype, where the iSight would operate.

But the larger issue is that, except for a very basic educational iMac, you’re stuck with the camera. Ditto for the MacBook and MacBook Pro, and the remote comes with every model save for the Mac Pro, since content creators aren’t supposed to have such toys.

Indeed, these issues aren’t the only ones that can provoke concerns. Take the location of the power switches on the Mac mini and the iMac, which are found at the rear of these units. Now matter how often I use these models, I find myself groping to find them. I suppose if I had them in my office for any length of time, things would be different.

Of course, the iMac used to have the power control up front, on the original pear-shaped version, but Apple has decreed that its consumer desktops should look sleek, and buttons aren’t sleek if you can see them. Then again, you really aren’t supposed to turn off your Mac unless you’re installing a firmware update or you’re leaving your home or office for a few days and don’t want any devices left on to draw even a trickle of current. Otherwise, it’s Sleep all the way.

But what am I saying? After all, I can’t remember the last time my MacBook Pro was shut down, other than to replace a defective battery.

Speaking of the 17-inch version of the MacBook Pro, some folks have complained about the fact that the keyboard strikes you as a little lost and lonesome at the rear of the notebook, with all that empty space to fill. So what should Apple do about this design shortcoming? With those large outboard speakers, would there be room for a numeric keypad? Talk about busy.

Personally, it never bothered me. It took me quite a few years to become accustomed to a notebook keyboard and trackpad and your irritant in this case is of no consequence to me.

But I hope I’ve opened a larger discussion. What bothers you about your Mac and about Mac OS X? And, please, no more demands to restore the Classic Mac Finder. I do not think there is any hope for that. The need for a fixed Finder, however, is something I think we can all agree on, even if it doesn’t otherwise differ all that much from the present version.

Related Articles:


Update! The Leopard Report: Spring Forward, Fall Back!

Tuesday, March 27th, 2007

You can’t imagine the consternation on the part of some Mac users after reading published reports that Mac OS X Leopard was being postponed until October because Apple wanted to improve compatibility with Windows Vista.

Without much thought, some folks ignored the illogical nature of the basic premise and the story simply took off. It’s not that Apple has helped much, since they’ve said very little about Leopard in recent months. Everything about Leopard’s progress is unofficial, with reports from folks who ought to know better about the state of 10.5’s development process, which was said not to be going so well.

So where are all the “top secret” features touted by Steve Jobs at last year’s WWDC? His excuse was that he didn’t want to give Microsoft a chance to copy those features for Windows Vista. As a practical matter, this doesn’t make a whole lot of sense. Even if Microsoft wanted to steal some of those features, it might take a year or two to alter an operating system that was already in the final Q&A process.

In other words, it was all just marketing hype, or perhaps a clever excuse to avoid saying those extra features weren’t quite ready to display publicly last year.

Of course, when Apple barely uttered a word about Leopard’s progress in January at Macworld Expo, you can bet that the rumor mills were fueled to overflowing. Every single month, we heard that final release was just weeks away and Apple would reveal all of Leopard’s secrets to an eager audience of Mac users.

To be sure, I felt reasonably certain in January that Leopard would arrive in late March, to coincide with the sixth anniversary of Mac OS X. As February turned into March, I realized my expectations wouldn’t be fulfilled. At this point, though, it really didn’t matter. It could be May or June and it would make no difference. I have other things to spend my money on, and Tiger works just fine for me. As much as I enjoy putting a new Mac OS through its paces, I’m content to wait.

Update: Anyway, the theory that Leopard would be postponed until fall made no sense either. What would Apple need to do to Leopard when it came to Vista compatibility that would delay it so long? It couldn’t be Boot Camp, since third parties have already managed to induce it to run Vista, and this wouldn’t seem a valid reason to put Leopard on the back burner. What’s more, version 1.2 of the Boot Camp beta has since added official support for Vista, eliminating one more silly argument about the alleged delay.

To make things all the more interesting, Apple was finally quoted as saying that it wasn’t changing its promise to deliver Leopard during the first half of this year.

Now that doesn’t mean that you should always believe Apple, because it may well be that a final delivery date is still in flux. Besides, as most of you realize, Apple has been known to say one thing and do another. For example, as some have mentioned already, the Mac mini first appeared only a few months after Apple’s finance executives said they didn’t intend to enter the low-cost PC arena.

Of course, that could have been a little sleight of hand to misdirect potential competitors. Or perhaps the final decision about whether to go ahead with the mini wasn’t made until after the analyst meeting in question.

So where does that leave us? Well, nowhere I should imagine. After all, the original story about a Leopard delay had no verification and was without logic. It probably should not have been published in the first place.

Of course, so long as Apple continues to say nothing about Leopard, I suppose there’s plenty of room for rampant speculation to fill in the gaps. At the same time, I would hope that a few of those so-called journalists who are ripe and ready to run with any story about Apple, whether verified or not, will learn a few of the basics of their profession.

However, that’s something I’m not betting on.

In any case, for the sake of any of you who really care at this point, I think Apple’s decision to schedule the WWDC in June says it all. They fully expect to have Leopard shipping or close to shipping at that time.

Meantime, I would hope the official announcement will be coming soon, so all the speculation can end for good. Or until there’s something else to speculate about.

Related Articles: