[webkit-dev] Modern image formats for WebKit

[ChangSeok Oh]

> 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 image decoding libraries that we build scaffolding in order to link with.
O.K Thanks for making clear. =)

ChangSeok

> On Mar 22, 2015, at 12:46 AM, Myles C. Maxfield <mmaxfield at apple.com> wrote:
> 
> 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 code in 2) is required no matter what.
> 
> 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.
> 
> Assuming that we are linking with external decoding libraries, I do not have any strong opinion as to which image decoding libraries that we build scaffolding in order to link with.
> 
> -Myles
> 
> On Mar 20, 2015, at 6:16 PM, ChangSeok Oh <changseok.oh at collabora.com <mailto:changseok.oh at collabora.com>> wrote:
> 
>>> So this is a really a question for people working on other active ports like the EFL and GTK ones. Are there other libraries that you could use for image decoding, or do you still want to keep and maintain a WebKit copy of these image decoders?
>> 
>> Maybe the latter one. I’m not sure what you meant other libraries here if they are not libwebp nor libjxr. 
>> I found webp has been supported by gtk & elf ports already. At least WebPImageDecoder.cpp is a build target for those ports. JXR support would be a same shape with webp support, i. e adding a glue layer JPEGXRImageDecoder.cpp/h and linking libjxr.so.  
>> 
>> ChangSeok
>> 
>>> On Mar 21, 2015, at 6:39 AM, Darin Adler <darin at apple.com <mailto:darin at apple.com>> wrote:
>>> 
>>> We should consider whether to keep the image format decoders in the WebKit tree or not.
>>> 
>>> Dave Hyatt originally created this when we first were planning the Apple Windows port of WebKit, but in the end we chose to not use them for the Windows port. They aren’t used in the Windows port nor in the Mac or iOS ports; for all of those we use a separate image decoding library.
>>> 
>>> So this is a really a question for people working on other active ports like the EFL and GTK ones. Are there other libraries that you could use for image decoding, or do you still want to keep and maintain a WebKit copy of these image decoders?
>>> 
>>> — Darin
>>> _______________________________________________
>>> webkit-dev mailing list
>>> webkit-dev at lists.webkit.org <mailto:webkit-dev at lists.webkit.org>
>>> https://lists.webkit.org/mailman/listinfo/webkit-dev <https://lists.webkit.org/mailman/listinfo/webkit-dev>
>> 
>> _______________________________________________
>> webkit-dev mailing list
>> webkit-dev at lists.webkit.org <mailto:webkit-dev at lists.webkit.org>
>> https://lists.webkit.org/mailman/listinfo/webkit-dev <https://lists.webkit.org/mailman/listinfo/webkit-dev>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-dev/attachments/20150322/9570d968/attachment.html>