On Thu, Apr 10, 2008 at 10:47:44AM +0200, Cedric BAIL wrote: > On Thu, Apr 10, 2008 at 1:06 AM, Jose Gonzalez <[EMAIL PROTECTED]> wrote: > > Cedric wrote: > > >> That's a pretty hefty patch. :) Do you think you could write > > >> down some of the design/structure/etc, and what you're aiming for > > >> here.. for the sake of posterity and mere mortals with little time > > >> to look it all over. :) > > > > > > Yes of course. So it's basically an improvement of the current cache > > system. > > > > > As the code base of the cache is cleaner, it should be easier to add > > > new functionality. For example, I think adding the background loading > > > of an image surface should be really easy with this code base. > > > > > > I know that this code change is huge, and it's difficult for me to > > > split it as I started to do the work the old way (without git). If you > > > have more questions or if I am not really clear on some change, don't > > > hesitate to ask more question ! > > > > 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.
Or like raster proposed a while back: evas_object_image_load_policy_set(obj, EVAS_LOAD_POLICY_ASYNC); http://www.mail-archive.com/[email protected]/msg14217.html -- Lars Munch ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
