If you check the official documentation , you will see nothing standard will fit your needs, or you add an image and center it on the view, but you cn't really manipulate the rest, but to be easy, and just, neat coding, create a custom cell 🙂
If you check the official documentation , you will see nothing standard will fit your needs, or you add an image and center it on the view, but you cn't really manipulate the rest, but to be easy, and just, neat coding, create a custom cell 🙂
Depends on the complication of the Cell.. But mostly I just go for the code, I just use the same code for iPad/iPhone, can do that with nibs too, but code is still faster as NIBs, even though you won't see it with the naked eye, but i like how everything just counts to speed the app up.
I did some testing back in the days with massive rerendering of cells, and i had a slight faster rate with the custom made ones.
Not sure if it was just strange luck, i'm glad to listen to anything that could go against that. People are asking me all the time what is faster, NIB's vs hand coded views.
The amount of developing ofcourse is alot higher with Handcoded, but is processing XML (which NIB's are like you will know Dejo) + compiling the code faster then just coding it all the way?
I'm glad to hear about this (since it's something i'm constantly looking for too).