Question

I’m reading a custom table cell in tableView:cellForRowAtIndexPath: from a nib file. This works great for my purposes, except it’s quite slow.

Now, I know the right thing to do in the long term is to create the cell entirely in code, and to use a single view, and so on. But this is a prototype, and I don’t want to put that much effort into it.

For now, I’d be happy if I was reading the nib only once in the UIViewController subclass, then tableView:cellForRowAtIndexPath: made copies of it. My assumption here is that copying would be faster than reading the nib.

Here’s what I use to load the nib, which I call from viewDidLoad: (and retain after)

-(id)loadFromNamed:(NSString*)name {     NSArray *objectsInNib = [[NSBundle mainBundle] loadNibNamed:name                                                           owner:self                                                         options:nil];     assert( objectsInNib.count == 1 );     return [objectsInNib objectAtIndex:0]; } 

All is good so far. But the question is: How do I copy this over and over? Is it even possible?

I tried [_cachedObject copy] and [_cachedObject mutableCopy] but UITableViewCell doesn’t support either copy protocol.

If I have to, I can just tell them to ignore the speed until I’m prepared to remove the nib entirely, but I’d rather get it going a little faster if there’s a low-hanging fruit here.

Any ideas?

Answer 1

Use the cell cloning built into the table view. Apple knew generating a lot of table cells was slow. Check out the docs for this method:

- (UITableViewCell *)dequeueReusableCellWithIdentifier:(NSString *)identifier 

You create the cell once, then as new cells are requested, use that method to clone the existing cells. Then you just change what needs to be changed about the new cell and return the cell object.

Also check out the table view realted sample code provided by Apple that uses this method and show you the right way. The fact your cell was loaded from a nib shouldn’t matter at all.

---

Minor clarification: I dont think the above method clone cells for you. Instead it takes cell object that have scrolled off the screen and simply moves them to a new spot. So it’s literally reusing a cell. So be sure your custom table view can be set to all the new values it needs outside of the intialization.