I was debating using a custom interface that routes appropriately, however, that might mean I would need a separate image caching handler (this all stems from possible memory issues of our app when handling images, Picasso deals with images really well, which is why I want all my images loaded into memory through Picasso).
>From what I've read, ideally Picasso is a singleton, and now I'm just determining if you can change 'downloaders' on the fly. If so, then this whole thread might become moot! (I really hope) On Tuesday, September 9, 2014 3:35:50 PM UTC-4, Jens Alfke wrote: > > > On Sep 9, 2014, at 12:25 PM, Suresh Joshi <[email protected] <javascript:>> > wrote: > > Picasso is an image loading/smart caching library (something like > FastImageCache for iOS). OkHttp is a HTTP protocol library, that Picasso > uses internally. I'm trying to override OkHttp to point at the filesystem > instead of a web URL (there aren't too many other ways to customize how > Picasso works) > > > Hm. But the images are already downloaded. Are you trying to get them into > Picasso just because the rest of your app is hardwired to go through > Picasso to access resources? If so, could you abstract that to a custom > interface, and have the implementation call either Picasso or CBL? > > —Jens > > -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/8a116e76-55f9-48fe-985f-28bd0aa43644%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
