IMHO having a worker process is definitely worth the effort. It is a
little daunting at first but once you get your head around it it's
great fun to work on.
If you write your image loader worker process in a well structured way
then you will be able to reuse it from project to project. One day
I did some profiling and it turned out significant time is spent on
loading images. Each listview item has a distinctive image. i have
thousands of items in my listview so I cannot cache them. I tried to
create an image on card folder cache of either PNG or JPEG image files
of exactly the same
This is an API demo for dealing with data that is slow to load:
http://developer.android.com/resources/samples/ApiDemos/src/com/example/android/apis/view/List13.html
You'll of course want to do this a little differently, filling in as much of
each item as you can when binding, and having a
How do I profile the code? I do recycle bitmaps since each list item
displays its own bitmap image and without recycling I quickly run out
of memory.
On Aug 26, 10:50 pm, Dianne Hackborn hack...@android.com wrote:
Run your code in a profiler.
Make sure you aren't thrashing through temporary
http://developer.android.com/guide/developing/tools/traceview.html
http://developer.android.com/guide/developing/tools/traceview.htmlThis may
not be documented, but in newer versions you can use the am command to
start and stop profiling. Use adb shell am to get help for the command.
On Thu,
5 matches
Mail list logo
