Running the new iPhone 2.0 software? Want to grab a screenshot of something? Turns out it’s amazingly easy. Hold the Home button down, then tap the power button on the top of the phone. The screen will flash white, and that’s it — the screenshot has been taken.

Sweet feature

(Via MacOSXHints.com.)

I am celebrating the arrival of Mac OS X 10.5 by making the source code to PagePacker available. Here is the compiled application.

Don’t know what PagePacker is? Check this posting.

This is cool app to use to make paper GTD and calendars and stuff, but the nice thing is the source is a great little learning tool for Cocoa

(Via Big Nerd Ranch Weblog.)

This reminds me of the old “hosting a party” metaphor for web apps. Just because you’ve invited someone over to your house/app, doesn’t mean your hosting duties are over. You still need to welcome your guests, show them around, offer some introductions, and make sure they get into the flow.

That’s why the blank slate, the first screen people see, is so key. If it’s unwelcoming, people may not stick around.

This is a big deal for services/sites that have self sign, or have anykind of unguided experience. It is said that a ui should be self teaching, but have you ever seen one. The on the web we are so free to make unique user experiences that are not tied to interface guidelines or even native control widgets. In this is a great danger there are advantages to things like the Apple Human Interface Guidelines as limiting and restrictive as they may seem. To be able to leverage the vast experiences that your user has had (remember that a user is a human not a thing) has immense value. It speaks to using native widgets (or at least try to give the same sense of purpose as the native widget)

But let it be said that what you do for your user on their first experience in your app will reap great rewards (I mean $$) if you leave your user hanging they will not ‘hang’ out and find all your cool stuff. Assume that your mental model of how the app will be experienced is wrong, show them they way.

(Via Signal vs. Noise.)

Shows how to use a CGDataProvider to save a very large image with Image IO

Some sample code to have a good look at, since I seem to be dealing with ever LARGER images every day….

(Via Apple Developer Connection Headlines.)

It’s so regular you could set your watch by it. The decay of a community is just as predictable as the decay of certain stable nuclear isotopes. As soon as an open source project, language, or what-have-you achieves a certain notoriety%u2014its half-life, if you will%u2014they swarm in, seemingly draining the very life out of the community itself. They are the Help Vampires. And I’m here to stop them.

SO RIGHT ON IT HURTS

There are a lot of ways you can create a preferences window for your Cocoa application. Of course you can just start with an empty window and start coding a toolbar. Or, if you don%u2019t want to start from scratch, you can use Matt Gemmell%u2019s SS_PrefsController class. Or you can grab some code from John Devor%u2019s Simple Preferences example project and modify it for your needs.

This is a great way to get a nice pref panel up and running fast

(Via .)

One thing that Sandvox does is to make resized copies of image files. There are often a lot of useful metadata in a JPEG file, so I decided that it would be a good idea to preserve these as much as possible if scaling down a JPEG file to another size. Many but not all of these are supported by NSImage, so it’s not hard to extract from the original image and put in the other.

Good things to keep track of for later

(Via Dan Wood: The Eponymous Weblog.)

Slick, but too geeking for some

(Via Del.icio.us Tag: cocoa.)

Posted by Amit Singh, Mac Engineering Manager

Google is a fantastic company to work for. I could cite numerous reasons why. Take the concept of “20 percent time.” Google engineers are encouraged to spend 20 percent of their time pursuing projects they’re passionate about. I started one such exciting project some time back, and I’m pleased to announce that Google is releasing the fruits of this project as an open source contribution to the Macintosh community. That project is MacFUSE, a Mac OS X version of the popular FUSE (File System in User Space) mechanism, which was created for Linux and subsequently ported to FreeBSD.

This is so very cool, I wish I had the time to play with this (and knew enough to make it worth it…….

(Via Official Google Mac Blog.)

It’s easy to beat up on Interface Builder, which until 10.5 ships, still feels a little crufty. It’s lagged behind Xcode in the major overhaul department. But sometimes I discover features that suprise me, like this tidbit from Apple’s Technical Q&A:

Q&A 1323: Interface element identification in Interface Builder

(Link compliments of Justin Anderson)

What the Q&A describes is a way to quickly identify the UI corresponding with any UI instance in IB’s hierarchical instance view. Just hold down control-shift and click an item:

Scott Stevenson’s recent bindings visualization discoveries, there seem to be a heap of features that I simply haven’t noticed. I guess I better keep my mouth shut before lambasting it too hard… nah!

Can’t wait for the next iteration of xCode as well, bring it on and call me an early (as possible) adopter

(Via Red Sweater Blog.)