Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Best approach in my eyes would be to download the image files as normal image files via a HTTP get request. Make sure it is threaded of course, and have a thread pool that you can queue up requests into, and have 2-3 threads go through and download.</p> <p>In terms of saving them, I would personally move away from saving to blob in a database, and opt to save them to the persisted storage in your application's private directory. Saving the image files with their filename as their id in the database you have created will be much quicker for loading them back in. </p> <p>You can also hold a reference to the ImageView, and have it display a place-holder initially, with a successful HTTP request replacing the bitmap of the ImageView with the one you have just downloaded/read in from storage.</p> <p>You can also do some image caching within the HTTP request you make.</p> <pre><code>ImageView myImageView = findViewById(R.id.testImage); URL url = new URL("http://www.website.com/image.jpg"); URLConnection connection = url.openConnection(); connection.setUseCaches(true); Object response = connection.getContent(); if (response instanceof Bitmap) { Bitmap bitmap = (Bitmap)response; myImageView.setBitmap(bitmap); } </code></pre> <p>It also may be helpful to lookup the uses of the LRUCache, which performs a lot of caching functionality for you.</p> <p>Check out <a href="http://developer.android.com/training/displaying-bitmaps/cache-bitmap.html" rel="nofollow">this link at the Android Developer site</a> for a good in depth guide to image caching</p> <p><strong>Edit:</strong> You can use the advice in Robert Rowntree's answer to load bitmaps more efficiently to cut down on your memory use as well. The link provided details loading of bitmaps using less memory, something that would work well if you are creating thumbnails from larger images downloaded over the web and saved off to local storage.</p>
    singulars
    1. This table or related slice is empty.
    1. POAndroid - Efficient way to load multiple images from remote server
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USbiddulph.r
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThank you for your answer. You've mentioned using multiple threads. In my application I used Loaders to get the texts from the remote server. Is doing the same thing for images a bad approach? Also even if am using Loaders or multiple threads, shouldn't I do something more to have each image load separately?
      singulars
      1. PO
      1. USuser1851212
    2. COLoaders were introduced relatively recently, so I don't have much experience with them. I am unaware of their benefits/drawbacks in this siutation. My suggested approach would be 2-3 Threads which read image requests from a Vector or Queue, perform AsyncTask, then go looking for another image in the Queue. If none found, the thread dies. Keep a Thread count, and start a new Thread if the count is below your maximum
      singulars
      1. PO
      1. USbiddulph.r
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload