Mozilla2:ImageLib: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
mNo edit summary
No edit summary
Line 4: Line 4:
* Minimal memory impact, allowing for small device support
* Minimal memory impact, allowing for small device support
== Encoding ==
== Encoding ==
Need to add APIs for encoding images.  See Image_Encoding.
Need to add APIs for encoding images.  See [[Mozilla2:Image_Encoding]].
== ColorSync ==
== ColorSync ==
We should try to add Apple's ColorSync support to the image decoders on Mac and Windows. Many who work with digital media come across images with embedded color profiles and so the images look incorrect in Mozilla. Safari displays them correctly.
We should try to add Apple's ColorSync support to the image decoders on Mac and Windows. Many who work with digital media come across images with embedded color profiles and so the images look incorrect in Mozilla. Safari displays them correctly.

Revision as of 01:00, 8 March 2005

Generally the image support of Mozilla should be aimed at:

  • Supporting open standards: fully compliant and no proprietary extensions
  • Optimized for image loading, decoding and displaying: one of the core requirements of an internet browser
  • Minimal memory impact, allowing for small device support

Encoding

Need to add APIs for encoding images. See Mozilla2:Image_Encoding.

ColorSync

We should try to add Apple's ColorSync support to the image decoders on Mac and Windows. Many who work with digital media come across images with embedded color profiles and so the images look incorrect in Mozilla. Safari displays them correctly.

JPEG2000

JPEG2000: I have found an extension for mozilla and firefox that lets you view JPEG2000 pictures. I'll post it for those you haven't found it yet, as long as the site's maninter can handle the extra traffic and those folks here are ok with a little adverstisement on this site. It lead me to think that we should add the ability to view this file format in the standard dist, if it isn't much of a hassle.

Isn't that illegal? JPEG2000 is heavily patented IIRC. Unless somebody's going to buy off the rights holders. And I didn't think mozilla.org had THAT sort of money. Anyway nobody uses JPEG2000, for this exact reason.

Why not just read the JPEG2000 FAQ on patents instead of FUD-ing?

GIF

The current GIF handling can be further improved, by fixing current 'bugs':

  • Improve memory usage and performance of the decoder (see bug 274391).
  • Optimize memory usage for 8-bit (and less) images (see bug 143046).
  • Reduce source and object code size: Move GIF2.cpp into nsGIFDecoder2 (see bug 196295)

These have all patches available awaiting reviews, requiring more priority than it currently has. Additionally:

  • Optimize for animated images. Currently all the frames are decoded, stored as 24-bit images, and all kept in the memory cache - this could be improved on by keeping the LZW compressed frames and only decode into 8-bit or 24-bit when required.

Video

The next step in animated images is full video support. Is built in support for video formats a requirement for a browser?