[Webkit-unassigned] [Bug 90375] Parallel image decoders

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Aug 1 18:37:36 PDT 2012


--- Comment #56 from Huang Dongsung <luxtella at company100.net>  2012-08-01 18:37:32 PST ---
(In reply to comment #53)
> Now that I tried to remove currentFrameHasAlpha, I found the results not satisfactory. The reason is I need to disable some optimizations to achieve this, which might upset users that rely on this API.

Your patch said there are two clients: Texmap and box shadow painting.

I know Texmap well and I think we can overcome about Texmap. I can remove currentFrameHasAlpha() completely in the code related to Texmap.
However, I have lack of knowledge about box shadow painting. My gut feeling still tells me by removing currentFrameHasAlpha() completely.
Otherwise, clients could be confused whether they use currentFrameHasAlpha() or a platform specific function.

> Instead it is enough for currentFrameHasAlpha to return the best guess. By calling directly into each image decoder we can answer this call good enough, until the image is fully decoded.
> So I suggest the first step is to remove decoding caused by currentFrameHasAlpha, this way nativeImageForCurrentFrame being the only public method that triggers image decoding.
> frameIsCompleteAtIndex and frameDurationAtIndex are for GIF animation, I would consider them a separate problem.

I want to try to remove meta data query functions based on your patch, and then refactory parallel image decoders on the preparation.
parallel image decoders changes almost only ImageSource. I think parallel image decoders will get along with your async image decoder.

If you don't mind, I will post a patch in several hours later.

I am curious about the progress of your async image decoder, how we collaborate the preparation and how we commit our async and parallel image decoders.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list