Another lazy loading approach:
HJCache is an iOS library that makes it very easy to asynchronously load images from URLs, display them in smooth scrolling tables, and cache the images in file storage.
via HJCache: iPhone cache library for asynchronous image loading and caching..
Here is a nice set of stencils which can be used in Omni Groups Omnigraffle if you want to layout your iPhone application: iPhone Sketch
Just found this nice Stackoverflow answer by Marcus Zarra.
The rule for storing image data in Core Data is as follows:
- < 100 kb store in the related entity (person, address, whatever).
- < 1 mb store in a separate entity on the other end of a relationship to avoid performance issues.
- > 1 mb store on disk and reference the path in your Core Data store.
You can use the transformable data type to store the NSImage directly into Core Data. In fact you can use the transformable data type to store anything that implements the NSCoder protocol.
via design – Core Data – Storing Images (iPhone) – Stack Overflow.
If you set the NSZombieEnabled environment variable, the Objective C runtime will leave a dummy object behind for every deallocated object. When the zombie object is called, execution stops and you can see the message that was sent to the object and the call stack that tells you where the message came from it doesn’t tell you where you over released the object, but knowing where the object is called from should get you pretty close to the problem.
I was just looking to change the value of the ${PRODUCT_NAME} variable and found this:
1. Go to “Targets” and then do a “Get Info” on the application name.
2. In the window that pops up, go to the “Build” tab.
3. In the “Setting” column, go to the “Packaging” section and expand it if it isn’t already expanded.
4. In that section, change the “Product Name” entry to the desired name.
Found here: http://discussions.apple.com/thread.jspa?threadID=1643724
Google is targeting the iPhone’s lack of real keyboards; inability to run simultaneous apps; inability to allow open development; and lack of interchangeable batteries.
via Google Android challenges Apple iPhone | 26 Oct 2009 | ComputerWeekly.com.
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=1c7c9ab0-87e8-469c-9564-332b11d3a239)
