Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 64B9E200C78 for ; Thu, 18 May 2017 15:20:57 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 630E7160BC4; Thu, 18 May 2017 13:20:57 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id A9485160BB0 for ; Thu, 18 May 2017 15:20:56 +0200 (CEST) Received: (qmail 32270 invoked by uid 500); 18 May 2017 13:20:55 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 32254 invoked by uid 99); 18 May 2017 13:20:55 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 May 2017 13:20:55 +0000 Received: from [10.0.127.223] (unknown [12.154.31.190]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 714741A031B for ; Thu, 18 May 2017 13:20:55 +0000 (UTC) From: Benedikt Ritter Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: [IMAGING] Why don't we just release it? Date: Thu, 18 May 2017 09:20:30 -0400 References: To: Commons Developers List In-Reply-To: Message-Id: <6ADAFB2A-9796-4AA6-BCB5-220AAF9F09BD@apache.org> X-Mailer: Apple Mail (2.3273) archived-at: Thu, 18 May 2017 13:20:57 -0000 Hi Damjan, > Am 18.05.2017 um 08:16 schrieb Damjan Jovanovic : >=20 > 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. >=20 > 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 Any reason we can=E2=80=99t add this after 1.0? I=E2=80=99d like to get = the release train going for imaging. Once we have a 1.0 I think it will = be easier to push out incremental releases=E2=80=A6 Benedikt >=20 > Damjan >=20 >=20 > On Wed, May 17, 2017 at 11:22 PM, Benedikt Ritter > wrote: >=20 >> Hi, >>=20 >> Imaging's inception year is 2007. It has left the incubator around = 2009. >> There hasn=E2=80=99t 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=E2=80=99ve 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. >>=20 >> WDYT? >>=20 >> Benedikt >>=20 >> P.S.: Please no =E2=80=9Ewe need to fix this and that=E2=80=9C = comments, if you=E2=80=99re not >> intending to fix this stuff. >>=20 >>=20 >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org >> For additional commands, e-mail: dev-help@commons.apache.org >>=20 >>=20 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org