4 ms·
The most insightful bit in my opinion is where he explains how to create fast TableViews. Basically you use CG / Quartz to draw cells instead of adding Labels,
by zyb09 17y ago
The most insightful bit in my opinion is where he explains how to create fast TableViews. Basically you use CG / Quartz to draw cells instead of adding Labels, ImageViews etc. Very good thing to keep in mind!
- anotherperson 17y agoDoesn’t that stop a user from using copy and paste?
- tommusic 17y agoMost table cells don't have selectable/copyable text, as they're not able to get for-free the built-in text editing menu. Clicking on a table cell could advance the user to a "detail" view that does allow cut/copy/paste, though.
- aaronbrethorst 17y agoI haven't watched Loren's talk yet, so hopefully the following points aren't redundant. I've written a number of iPhone apps, and have spent a good deal of time learning how to make UITableViews scroll smoothly. Here are a few more tips: 1. Minimize the number of controls you use. Draw directly into the cell. You may have to suck it up and use a single label or something in order to achieve smooth control resizing during a swipe operation (like in the iPhone Mail app when you swipe the cell to delete a message). 2. Suspend all network requests while scrolling your table (i.e. loading remote images) 3. For the love of god, REUSE YOUR CELLS! There's a reason -dequeueReusableCellWithIdentifier: exists, and you should always use it. 4. Don't use variable height rows unless you absolutely need to. 5. Cache your row heights if you do use variable height rows. 6. Use opaque views. 7. Learn to love Instruments and the other iPhone/OS X profiling tools. You'll be amazed to learn where all of your memory and cycles are going. I normally budget a few days to a week near the end of my iPhone projects just for perf work.