Hi, I'm Jeremy Foo.

Code-fu mantra

andthirdly — Tue, 22 May 2012 15:25:00 +0800

Lately, I’ve been living by some mantras when it comes to dealing with code and large code bases. Not sure if its for everyone, but it works for me.

This mantras of course pertain to Objective-C and the Mac in general.

Subclass as little as possible, composition is better.
Keep implementation files around 500 lines of actual real code, beyond that, you might want to think of refactoring into logical components.
Group logical components by systems.
Readability trumps “generalization”.
Curly brackets are okay if code blocks are greater than 1 single line of code.
Return as early as possible (Wil Shipley).
Companion to returning as early as possible, try not to nest code blocks 3 levels deep.
Async is not always the best solution (refer to mantra #7).
Design for self containment, but more importantly, in areas of responsibility.
Designing public APIs (things that will not change) will probably give you decoupled objects.
Retain/Release is better than autorelease (until ARC of course).
Protocols are awesome.
Composition of data structures at the expense of space might save you time.
Less objects more primitive types.

Thoughts comments? Eager to hear about yours.

libspatialite for iOS

andthirdly — Sat, 19 May 2012 17:28:02 +0800

libspatialite for iOS:

Made a static library project over the weekend to build libspatialite for iOS. Includes GEOS and PROJ though they have to be actually linked into and set not to be omitted to get those into the libspatialite target.

10.8: Objective-C Enhancements

andthirdly — Fri, 17 Feb 2012 12:34:56 +0800

cocoaheads:

Objective-C Enhancements

OS X v10.8 includes the following enhancements to Objective-C:

Default synthesis of accessor methods for declared properties

Type-safe enums

New Core Foundation attributes that allow you to specify custom retain semantics

Object literals for NSArray, NSDictionary, and NSNumber

Streamlined object subscripting

Important Beginning in OS X v10.8, garbage collection is deprecated.

Can’t help be reblog this. Bloody marvelous.

MNCoder

andthirdly — Mon, 23 Jan 2012 20:11:00 +0800

Its been about 3 weeks, but I’m finally done with a piece of work that will be used (hopefully) in the iCloud capable version of Mindnode.

MNCoder is what I’d call a clever hack using NSKeyedArchiver and NSKeyedUnarchiver to help with portability of certain Apple classes between iOS and the Mac. If you worked on both platforms, you’d know that iOS has its own implementation for colors and fonts. With iOS 4 this has been extended to NSAttributedStrings that take Core Text attributes instead of the nicer AppKit additions to NSAttributedStrings.

While I’d admit this is a somewhat complicated way of going about things, 2KSLOC to be exact, I figured this was the most straightforward and intuitive way to help people understand and possibly contribute additional code in the future.

What MNCoder does is that it uses a neutral platform independent NSCoding compliant object to store the base attributes that is needed to reconstruct an equivalent on either platform. Using #ifs, the object will give you the appropriate object. Adding to the system is NSCoder which helps with the finding and replacement of objects at runtime when doing serialization.

Its pretty much like old school language translation. Translate your source language into a intermediate version and then translate that to the target language. Nothing too fancy and easily understood.

The work is released under a BSD license which Markus has nicely given his approval of so here’s hoping it’ll have more contributors as it goes along.

Nice side effect of this is that I’ve had extensive time with Core Text and I’d say its pretty fun.

Befriending Core Text

andthirdly — Mon, 16 Jan 2012 00:52:57 +0800

Befriending Core Text

The Word of Notch: Coding skill and the decline of stagnation

andthirdly — Sat, 14 Jan 2012 16:41:38 +0800

The Word of Notch: Coding skill and the decline of stagnation:

notch:

I am a decent programmer. I know a decent amount of computer science theory, I can type correct code fairly easy. I don’t let my classes expand too much. But I still struggle some with math, and I have a tendency to have too many cross-dependencies in my code.

I used to think I was an awesome…

Avoiding duplicate symbol errors during linking by removing classes from static libraries

andthirdly — Fri, 13 Jan 2012 01:22:21 +0800

Avoiding duplicate symbol errors during linking by removing classes from static libraries:

Oh this is a gem!

A little advice to companies

andthirdly — Mon, 09 Jan 2012 11:34:23 +0800

Before you engage a developer to build a mobile app for you, consider the following points,

Are you shoving your web page into an app?
Are you providing a catalogue of products/services/etc. with no useful way to purchase them beyond being just a showcase?
Are you adding a “game” so that people will actually use your app?
Are you using the app as nothing more than a marketing effort?

If you have answered yes to the above, here’s some cost saving advice.

Don’t do it.

The iPhone Tab Bar

andthirdly — Sun, 08 Jan 2012 13:16:38 +0800

The iPhone Tab Bar:

When designers get bored. Or a more sane way to do tab bars.

Mobile Progressive playback: An atom story.

andthirdly — Fri, 06 Jan 2012 11:30:34 +0800

Mobile Progressive playback: An atom story.:

For the people working with code that has to do with video.

Don't be STUPID: GRASP SOLID!

andthirdly — Fri, 06 Jan 2012 03:13:22 +0800

Don't be STUPID: GRASP SOLID!

iOS and Mac Development Link Roundup: December 2011 – Ole Begemann

andthirdly — Mon, 02 Jan 2012 02:31:49 +0800

iOS and Mac Development Link Roundup: December 2011 – Ole Begemann:

Such a gem.

A Core Data Primer

andthirdly — Tue, 29 Nov 2011 13:57:00 +0800

Everyone’s first encounter with Core Data would be through books and the occasional glance at the documentation. No one tells you what are the base tips in bullet points that you need to know. Having worked on Core Data for the past 9 months, I thought it’ll be a service to the community to at least commit something to Google’s memory.

Everything except NSManagedObjectContext is thread safe.
Create NSManagedObjectContext in new threads prior to using them. Pass them the NSPersistentStoreCoordinator of any NSManagedObjects across threads is fine.
NSManagedObjectID is your friend. Always use it if you are doing threading.
NSManagedObjectID is sometimes temporary. Use obtainPermanentObjectIDs to ensure that they are permanent.
Getting a permanent ID might cost disk access so use wisely.
Process cross context saving on the thread that the NSManagedObjectContext was created.
Instrument’s time profiler is your friend to find where Core Data calls are taking a long time.
Additionally, you can also get SQL statements that are generated as debug messages in console by turning on a flag.
Use as little relationships as possible when fetching objects. Easier to fetch criteria based on the actual operating object and have the fetch also fetch all relationships.
Sometimes it is easier to spin off a thread to fetch results and process them before calling the completion block with results.
Have a manager to handle all Core Data fetching of objects instead of being smart and trying to have individual managed object subclasses handle everything.
NSFetchedResultsController is sometimes a bitch when sending notifications of changed content. Don’t use UITableView’s reloadSectionsWithAnimation and its siblings when crashy happens.
Don’t look into [NSManagedObjectContext registeredObjects] to get objects back. They might already have been deleted but still cached. Stupid stupid me.
Always test Core Data performance on device.
Always do fetches on entities that you are filtering criteria for then use inverse relationships that are prefetched to get the data you really want (Basically think topsy turvy; less database joins the better because this is an object graph).

Check registeredObjects before excuteFetchRequest:Error:

andthirdly — Thu, 07 Apr 2011 18:07:00 +0800

Not too sure if this is the right way of doing this, or if anyone has even tried, but be sure to check the registeredObjects NSArray of the NSManagedContext prior to fetching stuff. This of course only applies to SQLite backed stores, and this is done to reduce SQLite queries and inevitably disk I/O.

You can effectively query the registeredObjects using almost the same predicate as your subclassed NSManagedObjects in order to ensure that the NSManagedObject you want is the same.

Here’s some code to describe what I’m talking about.

+(ManagedLocation *)locationWithCoord:(CLLocationCoordinate2D)coord 
                       managedContext:(NSManagedObjectContext *)moc {

    // loop through registered objects for the type 
    // you want and if they match your criteria

    // blocks rock!

    NSSet *result = [[moc registeredObjects] objectsPassingTest:^BOOL(id obj, BOOL *stop) {
        if ([obj isKindOfClass:[ManagedLocation class]]) {
            if ((((ManagedLocation *)obj).latValue == coord.latitude) && 
                (((ManagedLocation *)obj).lngValue == coord.longitude)) {
                return YES;
            }
        }
        return NO;
    }];

    // so if it doesn't exist. i guess we will have
    // to fetch off the sqlite store

    if ([result count] == 0) {
        result = [moc fetchObjectsForEntityName:[ManagedLocation entityName] 
                                  withPredicate:@"(lat == %lf) && (lng == %lf)", coord.latitude, coord.longitude];
    }

    // final check for existence.
    //
    // if it doesn't exist, create a new ManagedObject
    //  and return it for population of values.

    if ([result count] == 1) {
        return [result anyObject];
    } else {
        NSEntityDescription *locEntity = [NSEntityDescription entityForName:[ManagedLocation entityName] 
                                                     inManagedObjectContext:moc];

        ManagedLocation *loc = [[[ManagedLocation alloc] initWithEntity:locEntity
                                         insertIntoManagedObjectContext:moc] autorelease];

        loc.latValue = coord.latitude;
        loc.lngValue = coord.longitude;

        return loc;
    }

}

So yeah. I was able to reduce by an order of magnitude, the time spent creating stuff.

fork();

andthirdly — Mon, 04 Apr 2011 23:37:34 +0800

Some exciting things are happening and I’m at the brunt of it. Will reveal more when I can. All signs point to yes at this present moment and I’m really excited for the days to come.

Event-ed NSURLRequest

andthirdly — Sun, 03 Apr 2011 13:38:58 +0800

Have been very much inspired by the work on nodejs. For those of you who don’t know, nodejs is a basically a system to do Evented I/O using Google’s V8 Javascript engine.

One such application of nodejs is the development of servers both HTTP or socket based that doesn’t require the spinning up of threads to handle connections and/or network events. Callbacks are assigned to events and when those events happen, the callbacks are ran. No threads, easy peasey, low overheads, etc.

Currently there are 2 ways to do NSURLRequests. You can either wrap it around a thread and execute the operation synchronously or implement its delegate methods and have it run within the runloop.

JOURLRequest is an encapsulation of the NSURLRequest and its delegate methods to provide for a way to easily implement run loop based event-ed NSURLRequests. In addition to handling the delegate methods and providing its own, it also implements a blocks based system on top of the delegate methods to make development easier for developers who already know blocks.

The class also takes into account authentication via blocks or delegate methods to provide the right response to such situations. So its kinda event-ed in its own right.

If deployed on an iOS project, it also handles situations where network reachability is dropped as well as handle when apps go into background or return from foreground and return statuses accordingly.

It also provides static methods to create NSURLRequests based upon a dictionary of POST values. By default, if it detects a NSData within the dictionary, it’ll assume its a file upload and prepare the URLRequests accordingly. If not, it will use the less network intensive x-www-form-urlencoded method.

I’ve started using it for projects and the experience thus far is one of more responsive applications with lesser pains when it comes to dealing with events. (Blocks for the win!)

Its still very much a work in progress, but the bulk of it is there and working. Using it is simply including the files in your project and including the headers where you want to use this class.

Todo:

Further parallel between delegate methods and blocks
NSStream for data downloaded for large files
Suggestions?

Not that available

andthirdly — Wed, 19 Jan 2011 00:37:36 +0800

By a stroke of luck or fate, I’m doing lots of work for a startup on their iOS app. Pretty ambitious goals they have for what they want to accomplish and I’m pretty much on the same page with them to see this well executed.

As such, I won’t be that available for additional work. Still, contact me if you think I can help.

"Typical developer. Listened to what the customer wants and did what they want anyway."

andthirdly — Tue, 14 Dec 2010 01:51:53 +0800

“Typical developer. Listened to what the customer wants and did what they want anyway.”

- Scott Stevenson (NSConf 2009)

Advanced iPhone Development Course on iTunes University

andthirdly — Sat, 20 Nov 2010 01:26:51 +0800

Advanced iPhone Development Course on iTunes University:

Should be a good follow up after finishing CS193P

How to be a Successful Software Engineer

andthirdly — Wed, 17 Nov 2010 12:56:02 +0800

How to be a Successful Software Engineer:

Pretty much everything I see as essential