commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Damjan Jovanovic <dam...@apache.org>
Subject Re: [IMAGING] Why don't we just release it?
Date Thu, 18 May 2017 12:16:16 GMT
Imaging is in quite a sad state compared to javax.imageio, with very
limited JPEG support that is hard to improve without major research, and
doesn't add that much value. People seem to mostly use it for extracting
image metadata.

I would like to see most of the following in 1.0:
* Proper support for multi-image formats, where you can see individual
properties for each image
* Thumbnail support for image formats that support it
* Support for incremental loading of image formats like progressive JPEG
* Non-blocking I/O
* Random access file I/O
* Support for enormous images, too big to fit in memory, by processing them
line-by-line or tile-by-tile
* Independence from java.awt, and Android support
* Imaging as a javax.imageio extension that provides the JVM with support
for new image formats

Damjan


On Wed, May 17, 2017 at 11:22 PM, Benedikt Ritter <britter@apache.org>
wrote:

> Hi,
>
> Imaging's inception year is 2007. It has left the incubator around 2009.
> There hasn’t been a release under the Apache Commons umbrella, for various
> reason. I think we gave the initial contributors a hard time because we
> focused to much on code instead of community.
> Imaging is out there. People are using it. I’ve seen project simply
> depending on a SNAPSHOT version. This code is useful to a large group of
> people.
> So I propose that we just release it.
>
> WDYT?
>
> Benedikt
>
> P.S.: Please no „we need to fix this and that“ comments, if you’re not
> intending to fix this stuff.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message