Re: [E-devel] [PATCH] The big cache patch.

[Jose G. <jos...@ju...>]

>>       Thanks. :)  Actually, I do have several things I was thinking
>>  about on this, but let me just mention a kind of 'peripheral' thing
>>  you brought up - namely, that of "background loading of an image
>>  surface".
>>       I'm not sure I see what you mean by this - in evas. For local
>>  files, the images are loaded only when rendering is called and it's
>>  not clear to me what one could gain by having the loading done by
>>  a separate process (if that's what you meant)?
>>       If the files are not local, then I'd say those cases should be
>>  handled by other libs.. have the loading done to tmp local files and
>>  update those files with more data as need be (or something like that).
>>     
>
> In fact on slow computer decoding file can take some time and during
> this time nothing will move.
>
> So I am thinking about the idea of adding something like
> evas_object_image_preload, that will just send the request to a
> background thread. This thread will do the decompression and send an
> event to the object when it is ready. If during this time you need to
> access the data of the image, it will lock. This feature is needed in
> my opinion if you want to do anything with many image like an image
> viewer.
>   

      I see. Yeah, that could be useful.. though if an image viewer
program is going to load lots of large images via such an evas api
func then it could end up using a lot of resources, and if it just
wants to create thumbs of such then that might be best done via
another process to generate thumbnail files. But anyway, the idea
could indeed be useful to have.