Lines Matching full:images
35 complicated if you need to load a larger set of images at once. In many cases (such as with
37 android.support.v4.view.ViewPager }), the total number of images on-screen combined with images that
43 you want to avoid continually processing these images each time they come back on-screen. A memory
44 and disk cache can often help here, allowing components to quickly reload processed images.</p>
71 <li>How many images will be on-screen at once? How many need to be available ready to come
75 larger cache to hold the same number of images in memory compared to a device like <a
79 <li>How frequently will the images be accessed? Will some be accessed more frequently than others?
132 screen {@link android.widget.GridView} filled with images on a device with 800x480 resolution would
133 use around 1.5MB (800*480*4 bytes), so this would cache a minimum of around 2.5 pages of images in
176 rely on images being available in this cache. Components like {@link android.widget.GridView} with
182 times where images are no longer available in a memory cache. Of course, fetching images from disk
187 appropriate place to store cached images if they are accessed more frequently, for example in an
307 You want to avoid having to process all your images again so the user has a smooth and fast
315 existing cache object, allowing images to be quickly fetched and re-populated into the {@link
363 android.app.Fragment}. You should notice little to no lag as the images populate the activity almost
364 instantly from memory when you retain the cache. Any images not found in the memory cache are
