> I am discussing the code in 1). It seems to me that an image decoder itself
> should come from an external library, rather than be compiled directly from
> WebKit sources.
Exactly.
> Assuming that we are linking with external decoding libraries, I do not have
> any strong opinion as to which
We’ll have times when we need to decide what goes into this library, and what
goes into WTF. So I like the ones that fit the sentence “Is this really WTF or
is it just __?”
LOL, ROFL and ROFLCOPTER work well for this. I would also suggest:
Web Abstraction Toolbox (it’s hard to tell the dif
I think we have a winner!
> If I suggest one.. how about WAFL? WebCore Abstraction Framework Layer
> It should sound sweet like waffle =)
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev
Sorry, I think we are misunderstanding each other. Let me try to be more
explicit:
There are two conceptual pieces that are required to support image formats:
1) the image decoder itself
2) scaffolding around the API of a decoder to correctly hook it up to the rest
of WebKit.
First of all, the
4 matches
Mail list logo
