OS/X Microtip: gfxCardStatus can prevent video out from working

July 24th 2010 · Mac Computer

Here’s another microtip for you. If you have a recent Mac that supports automatic GPU switching, you might have decided that OS/X isn’t smart enough about when it decides to switch. Maybe you run 1Password or The Hit List and can’t fathom why they need the high-powered GPU. So, when you head out on the road, you use gfxCardStatus to “pin” the operating system on the low-powered Intel GPU and give your battery a break.

The problem comes when you go to project a presentation. Suddenly, reliable OS/X won’t do it. Try as hard as you can, click Detect Displays as often as you like – no projection, no secondary display.

Why? Because OS/X requires the high-powered GPU to connect a secondary display like a projector. But there’s no visible error messages or feedback. The connection simply won’t work. To solve the problem just switch gfxCardStatus back to automatic mode.


Don't upgrade to IDEA IntelliJ 9.0.3

July 23rd 2010 · Java

If you’re running IntelliJ on Mac or Linux and use Subversion, don’t upgrade to the new 9.0.3 release. There’s a huge defect that JetBrains doesn’t seem to care about. With the new 9.0.3 release IntelliJ no longer uses the Mac or Linux password keychains. That means all of your passwords will stop working and you will have to manually edit configuration files to get everything working again.

You can find more information in the IDEA-56464 defect. The end result is that you will be required to store all of your passwords in plain text. For those of you on corporate networks that use ActiveDirectory to provide single sign-on to your Subversion instances that means you’ll have to store that password in plain text.

This is completely unacceptable and will keep me on 9.0.2 until this defect is fixed.


Infoworld review of Windows Phone 7 - It's not good

July 17th 2010 · iPhone , Dev Trends

http://www.infoworld.com/d/mobilize/windows-phone-7-dont-bother-disaster-211?page=0,0

I won’t leave you in suspense, the review is bad. Really, really bad. The reviewer works for Infoworld and took part in an in-depth demo of the platform. The reviewer, Galen Gruman, doesn’t pull any punches. Some choice quotes:

“Windows Phone 7 is a waste of time and money. It’s a platform that no carrier, device maker, developer, or user should bother with. Microsoft should kill it before it ships and admit that it’s out of the mobile game for good. It is supposed to ship around Christmas 2010, but anyone who gets one will prefer a lump of coal. I really mean that.”

“…awkward and unsophisticated…[it’s like a great movie trailer], only to discover that all the good stuff was in the trailer and the rest of the movie was a mess. A pig, in fact.”

“Under the hood, Windows Phone 7 rests on creakingly old technology that the main competitors have all moved past.”

“Windows Phone 7 is a pale imitation of the 2007-era iPhone.”

“Microsoft is stuck in 2007, with a smartphone OS whose feature checklist might match that era’s iPhone but whose fit and finish would look like a Pinto next to a Maserati.”

“The developers at Mobile Beat quickly recognized the labor-intensity of this UI method and one asked the Microsoft rep if anyone had bothered to test it with users. The answer was essentially "no” — a scary thought indeed."

“If the Windows Phone 7’s flaws were confined to a poor UI, that wouldn’t be a deal-killer for many users. … But under the hood, Windows Phone 7 gets worse. The core problem is its backward set of technologies, which will fundamentally limit IT, developers, and users alike.”

“Its browser is Internet Explorer 7, with some IE8 capabilities added — that means it does not support HTML5, as the iPhone, Android, WebOS, and Nokia Symbian all do.”

“Microsoft has a long history of producing bad software and plugging away on it for a few versions — usually version 3 — until it is serviceable. But that "get it right in version 3” strategy won’t work this time. … Microsoft has no establishment advantage in mobile today, so delivering an outdated, hamstrung mobile OS and hoping to fix it later just won’t fly."

“… Windows Phone 7 was Redmond’s equivalent of the bungled Hurricane Katrina response effort.”

“If the iPhone is the platinum standard, Android is the gold standard, WebOS is the bronze standard, and Symbian and BlackBerry tie for tin. Windows Phone 7 is clay — a clay pigeon, in fact.”

“Microsoft needs to kill Windows Phone 7 and avoid further embarrassing itself by shipping this throwback. It’s not a question of whether Windows Phone 7 will fail — it will— but how long it will take Microsoft to admit the failure. For the company’s sake, the earlier it fesses up, the better.”

Unmentioned in this blisteringly bad review is Microsoft’s one ray of hope – Silverlight and the Development Environment for Windows Phone 7. I have no idea whether apps perform well and use the battery sparingly on Windows Phone 7. Right now, no one but the development team at Microsoft do. But the SDK is available, and while its not garnering huge excitement, it does show an environment that will be very familiar to existing Visual Studio and Silverlight developers. Microsoft has gotten very, very good at IDEs and development toolsets and that might entice a new set of developers to roll into the mobile space. And if the tools are good enough it might make them more productive as well.

Unfortunately, if Windows Phone 7 continues to get reviews like this one, no one will buy the phones and no one will buy the software that’s produced for them. Hopefully for the sake of competition they’ll get their acts together by release time.


OS/X Micro-tip: External display not recognized

June 30th 2010 · Mac Computer

I struggled to get a projector working with OS/X. This was entirely unexpected since I’d never had issues in the past. It always “just worked” in usual Apple fashion. I ran out of time and had to give up.

It continued to nag me, so I started digging further. And then the obvious problem hit me. I’m using Cody Krieger’s excellent gfxCardStatus utility. I had it set to force the use of the Intel GPU in order to conserve battery power. And that was the problem. OS/X requires the NVIDIA chipset in order to drive an external display. OS/X won’t use the Intel GPU to do that.

Setting gfxCardStatus to automatically switch got things working again.


iPhone sales trends, what's next?

June 28th 2010 · iPhone , Dev Trends

AppleInsider posted current and historical sales figures for the iPhone.

Year Amount Sold
2007 74 days to sell 1 million phones
2009 3 days to sell 1 million phones
2010 3 days to sell 1.7 million phones

You can’t really extrapolate, but that makes it likely the next phone will sell over 2 million in three days. That’s assuming, of course, that Apple can generate the same excitement for the next phone. Lack of supply almost certainly hurt those sales figures. Apple is notoriously conservative about demand and the result is choked supply at launch.

Another interesting figure is that 77% of pre-orders went to existing customers. That’s a great recurring revenue stream for Apple and speaks volumes about customer loyalty.

Personally though, I think the next phone is going to be a much harder sell. Every year there’s been some hardware feature I, personally, wanted to see. The iPhone 4 has fulfilled all of my wants. It’s completely replaced a GPS, camera and Flip HD. According to Apple, increasing the screen resolution would be pointless since no one would be able to tell the difference. What’s left for the next phone?

  • 4G / LTE
  • Faster CPU/multiple cores
  • Faster GPU
  • More memory
  • Better battery
  • Better camera
  • RFID

Out of that list, only the 4G and RFID would be completely new. I’m sure there’s more that Apple’s planning but I don’t know if there’s anything else that will really provide a “wow” feature. Haptic feedback built into the screen? Temperature sensor? :–)

Clearly there are still going to be improvements with the OS itself, but the remaining big button issues don’t require additional hardware. Right now it’s feeling like all of the low-hanging fruit have been eaten.


Micro-Tip: Using Subclipse on OS/X with Homebrew

June 21st 2010 · Java

If you install Eclipse on OS/X and then install the Subclipse plug-in, you might be surprised to see an error about missing JavaHL bindings for Subversion.

Subclipse uses the official Java to C bindings provided by the Subversion team. On OS/X these aren’t installed by default. If you use Homebrew to install open source software on OS/X (and I highly recommend it), then just installing Subversion won’t give them to you either.

So, to install Subversion using Homebrew and get the JavaHL bindings necessary for Subclipse, use this line:

brew install --universal --java subversion

This will create the 32 and 64 bit versions (—universal) and the JavaHL bindings (—java). So, regardless of whether you’re running Eclipse in 32-bit or 64-bit you should have the appropriate JavaHL bindings.

When Homebrew finishes building Subversion and the JavaHL bindings it will display this:

You may need to link the Java bindings into the Java Extensions folder:
  sudo ln -s /usr/local/lib/libsvnjavahl-1.dylib /Library/Java/Extensions

There’s no “you may” about it. Go ahead and run the sudo command. That will place the link to the JavaHL bindings in the OS/X Java extension library. Now Subclipse should automatically start working. You don’t even need to restart Eclipse if you had it running.

<< Previous articles
Next articles >>