manicwave.com

About

My name is Craig Hockenberry and furbo.org is my place to write for the web.
You can learn more about me or view my résumé. I also have some production notes available. Don't forget to follow me on Twitter.
For fun, click on my picture at the Iconfactory website.

Archives

July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
March 2008
February 2008
December 2007
September 2007
August 2007
July 2007
June 2007

Recent

Waving a red flag
Year two
Brain farts
A phone by any other name would smell as sweet…
Of toolbars and actions
Matt Gallagher deserves a medal…
A thought experiment
Slow ride, make it easy
Front Row To Go
Open sesame
The final test
During the early days of iPhone software development, there were no mechanisms for doing beta tests. Those of us on the bleeding edge were developing apps with very little peer review and beta testing.

Luckily, I have fr

ParseKit Home
Tokenization
Grammars
iPhone
Source Code
Header Docs
ParseKit Documentation
ParseKit

ParseKit is a Mac OS X Framework written by Todd Ditchendorf in Objective-C 2.0 and released under the MIT Open Source License. ParseKit is suitable for use on Mac OS X Leopard or iPhone OS. The framework is an Objective-C implementation of the tools described in "Building Parsers with Java" by Steven John Metsker. ParseKit includes additional features beyond the designs from the book and also some changes to match common Cocoa/Objective-C conventions. These changes are relatively superficial, however, and Metsker's book is the best documentation available for ParseKit.

The ParseKit Framework offers 3 basic services of general interest to Cocoa developers:

String Tokenization via the Objective-C PKTokenizer and PKToken classes.
High-Level Language Parsing via Objective-C – An Objective-C parser-building API (the PKParser class and sublcasses).
Objective-C Parser Generation via Grammars

Core FruitionIn a world where most good blog names are taken…

Home
About Me
« The Best Interface Builder Layout EveriPhone Development: Updating Project Hint »
Quick and Easy Drawing Performance Debugging with NSShowAllDrawing
While watching one of the WWDC09 session videos I was informed of a great tip that I had been previously unknown to me: Pass -NSShowAllDrawing YES as an argument to your application in Xcode to see a visual representation of the drawing that your application performs as it runs.
To illustrate how NSShowAllDrawing works and the issues it can help you correct I’ve put together two videos.  The first shows my app, Bezipped, in its current 1.0 state and its current drawing behavior.

This second video shows how I improved the drawing in Bezipped simply by setting the top-level container to be backed by a Core Animation layer:

I highly recommend giving your app a spin with NSShowAllDrawing if you haven’t already, it was certainly a real eye-opener for me.  There are

Inspired by the amazing but elderly MGTwitterEngine, I wrote my own social networking classes for Cocoa, collectively named SDSocialNetworking. You can find them at their github repo.

Search
MainArticlesForumsTutorialsReviewsAboutLoginRegisterSubmit Story
Tuning Cocoa Applications Using DTrace: Custom Static Probes and Instruments
By dgohara at Mon, Aug 10 2009 1:54pm |Tutorials
Author: Brad Larson
Web Sites: sunsetlakesoftware.com, sonoplot.com
In the first part of this article, I introduced the syntax and structure of DTrace scripts through a series of real-world Cocoa performance problems that DTrace can solve. Within this section, I'll show you how to answer even more specific questions about your application via the use of custom static probes, and I'll demonstrate how easy it is to use DTrace within Instruments to extend its already powerful data capture capabilities.
Custom DTrace probes
So far, we've only used probes that already exist within the system. DTrace also gives you the ability to insert custom static probes within your own code. These probes can be used to provide even more information to your running DTrace scripts. For example, Core Data uses

Programming with C Blocks
  On Apple Devices
  by Joachim Bengtsson
What are Blocks?
What are Blocks Good For?
Getting Started
On and for Mac OS X 10.6 Snow Leopard
On Mac OS X 10.5 Leopard or for iPhone
Blocks in C
Syntax and Usage
Memory Management
Blocks in Objective-C
Blocks in C++
Block Goodies
References and Additional Sources
Version History
0 Comments
1What are Blocks?

Blocks are like functions, but written inline with the rest of your code, inside other functions. They are also called closures, because they close around variables in your scope. (They can also be called lambdas). Let me demonstrate what this means:

counter.zip
#include <stdio.h>
#include <Block.h>
typedef int (^IntBlock)();

IntBlock counter(int start, int increment) {
__block int i = start;

return Block_copy( ^ {
int ret = i;
i += increment;
return ret;
});

}

int main() {
IntBlock mycounter = counter(5, 2);
printf("First call: %d\n", mycounter());
printf("Second call: %d\n", mycounter());
p