Posted 4 weeks ago

Using AppleScript to press keys

We can find all keycodes in

/System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/Headers/Events.h

example:

AppleScripts for iTunes

Posted 1 month ago
Posted 1 month ago
Posted 7 months ago
digdog:

「Actually, Sheldon Has Better Design.」
If you’re an iOS developer, and love the sitcom The Big Bang Theory, then you have to watch season 4 episode 12: The Bus Pants Utilization (original air date is January 6, 2011.)
In this episode, Leonard comes up with an idea for his iOS app and derails his friendship with Sheldon.
What’s the App?
It’s a handwriting-recognition based equation solver, or in Sheldon’s way: 「The Surprisingly Helpful Equation-Linked Differential Optimized Numerator.」 The idea behind this is to use iPhone’s camera to take a picture of the equation, and scan it with handwriting recognition, then run it through a symbolic evaluation engine, and bam.
Learning Cocoa
During the episode, they show several actual Objective-C code snippets and interesting design sketches on white boards, here are some of them:
 They have a CRecognition object holds an UIImage instance variable, and sadly they name it _Photo (with underline as prefix), it’s not the naming convention Apple suggested.
 The next morning, Sheldon starts his own design, if you look closer, it’s much more considered than Leonard’s.
 For example, since this is an utility app, Sheldon comes up with a flip view design that similar to built-in Camera/Stocks app. A full screen SPhotoView with a snapshot button in the middle, and on the other side, it’s SEquationView and a UITableView at the bottom with some buttons.
 In here, you can see more details. A UITableView holds the scanned equations, and supports rotation for landscape full screen detail view and portrait detail view. On the right side, Sheldon shows better understanding about UIViewController』s view hierarchy design concept.
 Later, Leonard’s team is doing some reference counting. Instead of accessing instance variable directly in -initWithPhoto: and -dealloc, they decide to use retain property self.photo, with class method to return a autoreleased CRecognition object, and claim there’s no leaks.
What a mess, you should always use instance variable directly in -initWithPhoto: and -dealloc when creating/releasing instance object.
 Here you see Leonard’s app class hierarchy, mostly MFC-ish (thanks, @lukhnos.) style naming convention for the class names, almost everything starts with letter 「C」 (is for 「Class」 I think), CAppDelegate, CMainView, CCameraView, CSymbolicView, etc. They should use prescribed prefix like 「LRH,」 which means Leonard, Rajesh and Howard.
 The beautiful Penny is next to Sheldon, and there’s Facebook API on the white board.
 In the end, Penny’s shoes app project. There’re many of them on the AppStore already, and the UI design for this one looks kinda lame.
 And Sheldon is working on this project… (for customer from hell?)
Conclusion
I love and enjoy this episode a lot, and the TBBT crew does a great job for all these minor details, they look very convincing to me.
But, they should use Mac when doing the coding, I only saw Raj’s MacBook Pro, and rest of them are using PCs. That’s not right, you can’t run Xcode on PC, well, unless they all use Hackintoshes…
Also, If you want to hire someone for your iOS app project, I highly recommend Sheldon Cooper.
References
The Big Bang Theory: 4x12 The Bus Pants Utilization
Apple: Introduction to Coding Guidelines for Cocoa
[digdog dig]; - To nil, or not to nil, that is the question

digdog:

「Actually, Sheldon Has Better Design.」

If you’re an iOS developer, and love the sitcom The Big Bang Theory, then you have to watch season 4 episode 12: The Bus Pants Utilization (original air date is January 6, 2011.)

In this episode, Leonard comes up with an idea for his iOS app and derails his friendship with Sheldon.

What’s the App?

It’s a handwriting-recognition based equation solver, or in Sheldon’s way: 「The Surprisingly Helpful Equation-Linked Differential Optimized Numerator.」 The idea behind this is to use iPhone’s camera to take a picture of the equation, and scan it with handwriting recognition, then run it through a symbolic evaluation engine, and bam.

Learning Cocoa

During the episode, they show several actual Objective-C code snippets and interesting design sketches on white boards, here are some of them:

They have a CRecognition object holds an UIImage instance variable, and sadly they name it _Photo (with underline as prefix), it’s not the naming convention Apple suggested.

The next morning, Sheldon starts his own design, if you look closer, it’s much more considered than Leonard’s.

For example, since this is an utility app, Sheldon comes up with a flip view design that similar to built-in Camera/Stocks app. A full screen SPhotoView with a snapshot button in the middle, and on the other side, it’s SEquationView and a UITableView at the bottom with some buttons.

In here, you can see more details. A UITableView holds the scanned equations, and supports rotation for landscape full screen detail view and portrait detail view. On the right side, Sheldon shows better understanding about UIViewController』s view hierarchy design concept.

Later, Leonard’s team is doing some reference counting. Instead of accessing instance variable directly in -initWithPhoto: and -dealloc, they decide to use retain property self.photo, with class method to return a autoreleased CRecognition object, and claim there’s no leaks.

What a mess, you should always use instance variable directly in -initWithPhoto: and -dealloc when creating/releasing instance object.

Here you see Leonard’s app class hierarchy, mostly MFC-ish (thanks, @lukhnos.) style naming convention for the class names, almost everything starts with letter 「C」 (is for 「Class」 I think), CAppDelegate, CMainView, CCameraView, CSymbolicView, etc. They should use prescribed prefix like 「LRH,」 which means Leonard, Rajesh and Howard.

The beautiful Penny is next to Sheldon, and there’s Facebook API on the white board.

In the end, Penny’s shoes app project. There’re many of them on the AppStore already, and the UI design for this one looks kinda lame.

And Sheldon is working on this project… (for customer from hell?)

Conclusion

I love and enjoy this episode a lot, and the TBBT crew does a great job for all these minor details, they look very convincing to me.

But, they should use Mac when doing the coding, I only saw Raj’s MacBook Pro, and rest of them are using PCs. That’s not right, you can’t run Xcode on PC, well, unless they all use Hackintoshes…

Also, If you want to hire someone for your iOS app project, I highly recommend Sheldon Cooper.

References

  1. The Big Bang Theory: 4x12 The Bus Pants Utilization
  2. Apple: Introduction to Coding Guidelines for Cocoa
  3. [digdog dig]; - To nil, or not to nil, that is the question
Posted 9 months ago
Posted 10 months ago

NSValue and NSData

NSValue and non-object types

Posted 10 months ago

Deep vs. Shallow vs. Lazy copy

Object Copy

Posted 11 months ago

What is Toll-Free Bridging?

Toll-free bridging means that the data structures are interchangeable. It is just as simple as casting — that’s the “toll-free” part. Anyplace you can use the type on one side of the bridge, you can use the other. So, for example, you can create a CFString and then send NSString messages to it, or you can create an NSArray and pass the array to CFArray functions.

Reference: 

  1. http://stackoverflow.com/questions/806115/toll-free-bridges
  2. http://www.mikeash.com/pyblog/friday-qa-2010-01-22-toll-free-bridging-internals.html
Posted 11 months ago

Using NSZombieEnabled

Use Xcode:

  1. Edit Scheme
  2. Select Arguments tab.
  3. Add Environment Variables.
    Name:NSZombieEnabled
    Value:YES


     

Introduce NSZombieEnabled: http://www.cocoadev.com/index.pl?NSZombieEnabled

Posted 11 months ago

Notification and Delegates pattern

Use the Notification pattern when anonymous objects need to passively observe and react to important events. In contrast, use the Delegates pattern when anonymous objects need to actively influence events as they happen.

Use the Delegates pattern when exactly one object is given an opportunity to influence or react to changes as they are happening.