StreamJockey

Useful Mac OS X and iOS Links for Developers

http://developer.apple.com/

http://www.iphonedevforums.com/forum/index.php

http://iphonedevelopment.blogspot.com/2008/06/web-services-core.html

http://www.iphonedevsdk.com/

http://idevkit.com/

http://www.cocoadev.com/index.pl

http://cocoadevcentral.com/d/learn_objectivec/

http://pragmaticstudio.com/screencasts

http://www.mobileorchard.com/find-iphone-memory-leaks-a-leaks-tool-tutorial/

Cocoa Is My Girlfriend » ZDS Code Style Guide

We have come to that point in the company’s life that I can no longer review every single line of code before it is passed either to a customer or put directly into production. However, there is always going to be the situation where I need to dive into a piece of code to get an issue sorted out; even if it is just another set of eyes on the problem.

via www.cimgf.com

Big Nerd Ranch Weblog » How to Time

I was asked three times last week how I find how long an activity takes on the Mac and the iPhone.  Here is the most accurate method that I know of:

#import uint64_t start = mach_absolute_time(); 
// do stuff to be timed 
uint64_t end = mach_absolute_time(); 
uint64_t elapsed = end - start; 
mach_timebase_info_data_t info; 
if (mach_timebase_info (&info) != KERN_SUCCESS) { 
  printf ("mach_timebase_info failed\n"); }
uint64_t nanosecs = elapsed * info.numer / info.denom;
uint64_t millisecs = nanosecs / 1000000;

As you use this, remember that the elapsed time for a given function will vary with the load the system is under.

via weblog.bignerdranch.com

The "timing" couldn't be better - I was just researching this topic last week.

mikeash.com: Friday Q&A 2009-11-13: Dangerous Cocoa Calls

First, let me clarify what I mean by a dangerous call. I don't mean something that is obviously dangerous, like -[NSFileManager removeFileAtPath:handler:]. That call is dangerous because you could use it to wipe the user's entire hard drive, but it's not interesting, because it's obvious that it can do this. Instead, I'm going to cover calls which are subtly dangerous, things which you might easily use in an innocent manner, only to discover later that bad things can occur.

via www.mikeash.com

iPhone Xcode "CodeSign error: a valid provisioning profile is required for product type 'Application' in SDK 'Device - iPhone OS 3.1.3'"

When working with multiple provisioning profiles you may occasionally encounter the CodeSign error. This may occur when opening up old projects that were built with profiles that you no longer have available. In some cases, either the release or debug build will work and the other will result in the error. The steps below fixed the issue for us:

1. In our case, we created a new wild card provisioning profile.
2. Delete old provisioning profiles in the Xcode Organizer.
3. From the Apple Developer Site, we downloaded the new provisioning profile. 
4. Next drag it to the Xcode icon to install. You can verify this profile using the Xcode Organizer by selecting your device and you should see the new profile under Provisioning. (If not you can click the + to add it.)
5. In Xcode, expand Targets and you'll see the application name - in this case Contacts. (See Image 1)
6. Double click on the application name to open the Targets "YourApp" Info dialog. (See Image 2a)
7. In the Code Signing section, Code Signing Identity, Any iPhone OS Device, my original setting, which was causing the error, was Don't Code Sign. (See Image 2a)
8. Next using the right column drop-down list, select the proper certificate. Note, once you select the drop-down the invalid certificate entry is gone (in my case iPhone Developer).  (See Image 2b)
9. Now select Build then Clean All Targets with Also Clean Dependencies and Also Remove Precompiled Headers checked.
10. Select Empty Caches from the Xcode menu. 
11. Now you should have success when clicking Build and Run on your device.

Image 1.

 Image 2a.

Image 2b. 

 

Stephen Colbert has an iPad! (HQ)

via www.youtube.com

I love the line "Jay-Z, did you not get one of these..."

Apple iPhone (iPad) SDK 3.2 Beta Released

Along with the iPad media event today, Apple released the iPhone SDK 3.2 beta which can be used for iPad development immediately. It does not support the iPhone or iPod touch.

With this software you can develop applications that run on iPad using the included iPad Simulator, which runs iPhone OS 3.2. Additionally, you can develop applications for iPhone and iPod touch, which run on iPhone OS 3.1.2. Installing the iPhone SDK 3.2 beta requires an Intel-based Macintosh computer running Mac OS X 10.6.2 (Snow Leopard) or later.

The Xcode development environment includes a new iPad simulator. And there are guidelines for developing universal applications that take full advantage of the technologies on the iPod touch, iPhone, and iPad from a single binary.

We have installed the SDK today and will be reporting on it over the next couple of weeks.