+1 agree.
On Thu, Aug 31, 2023, 9:29 AM Gary Gregory wrote:
> Hi All,
>
> I propose we drop implementating Serializable and avoid any and all
> possible security issues in this area.
>
> Gary
>
I have time in the next coming weeks I will start some experiments with
> Imaging 1.0-alpha3 using it in the Cantaloupe IIIF server and report the
> results here in the dev mailing list.
>
> Bruno
>
> On Thu, 19 May 2022 at 23:03, Gary Lucas wrote:
>
> > Obrigado, Bruno!
Obrigado, Bruno! I appreciate all of the careful work you put into this
release.
Gary
On Thu, May 19, 2022 at 3:56 AM Bruno Kinoshita wrote:
> The Apache Commons Team is pleased to announce the availability of
> Apache Commons Imaging 1.0-alpha3.
>
> Apache Commons Imaging, previously known a
[x] +1 Release these artifacts
Bruno,
Thank you for all your hard work, your mad skills on github, and the
excellent insights on the PR's that you reviewed.
Gary (the other Gary)
My primary interest for Commons Imaging is using it to access
geo-referenced TIFF file (GeoTIFF) . So far, it's worked out pretty well.
The TIFF file format provides a flexible definition for attaching metadata
to images. Back in the 1990's, the Geographic Information System (GIS)
community starte
ita wrote:
> Hi all,
>
> Family will be away in May/June for ~15 days, and I'm planning to use the
> spare time these weeks to release Apache Commons Imaging 1.0-alpha3, and
> Apache Commons Text 1.10.
> I'm working with Gary Lucas on fixing the Hashmap parameters and repl
I just posted a proposal on Jira for a newTIFF-file-writing class that will
help Commons Imaging support the production of very large TIFF files.
I am looking for comments about the design and requirements for the
proposed feature. If you are interested, you may read more at
https://issues.apache
I successfully built the latest version of code using the following:
Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555;
2019-04-04T15:00:29-04:00)
Maven home: C:\Users\gwluc\Documents\Applications\apache-maven-3.6.1\bin\..
Java version: 1.8.0_211, vendor: Oracle Corporation, runtime:
Damjan,
I just submitted a new Tracker Item, #93, and a patch. Unfortunately, I don't
seem to be able to find a control for granting a license. I'm going to Google
a bit to see if I can figure it out. But I wanted to let you know in case you
saw it before I was able to figure it out.
Gary
Damjan,
I just saw that you were soliciting votes for release. I think you've done an
outstanding job and I'm all for it. I would vote twice if I could :-)
I saw that some of the folks on the Apache page were complaining about some of
the code-checking issues. I've never looked at these my
I am making this post to the developers mailing list to see if anyone has ideas
about areas in the Apache Commons Imaging project that would benefit from
performance enhancements. Last year, I had a requirement through my job to
support TIFF images in Java. I selected the Apache Imaging packag
ubject: Re: [sanselan] EXIF_TAG_MODIFY_DATE removed from new imaging package?
On Thu, Apr 26, 2012 at 2:16 PM, Gary Lucas wrote:
>
> Since we're on the subject, another question. In encoding data, I was
> constructing field types and coding the information. But it looks
>
Since we're on the subject, another question. In encoding data, I was
constructing field types and coding the information. But it looks like you've
got some static declarations for doing the same thing. Could you verify that
the following is your intended approach
public TiffOutputField
imaging package?
On Wed, Apr 25, 2012 at 10:30 PM, Gary Lucas wrote:
> I'm taking a stab at transitioning from Sanselan to the new Apache Imaging.
> One thing I've noticed is that one of the EXIF tags my existing software uses
> seems to have been removed from imaging:
>
I'm taking a stab at transitioning from Sanselan to the new Apache Imaging.
One thing I've noticed is that one of the EXIF tags my existing software uses
seems to have been removed from imaging:
public static final TagInfo EXIF_TAG_MODIFY_DATE = new TagInfo(
"Modify Date", 0x013
I see there's some discussion about the next release of Sanselan between Damjan
Jovanovic, Gary Gregory (I'm the other Gary) and some of the Apache community
leaders. My name was even mentioned... so I thought I'd chime in.
First off, Damjan posted a note to the issue tracker that my submitted
Could someone give me some direction on how to handle an Sanselan Issue Tracker
issue?
I've found a change to the DataReaderStrips.java class that reduces the loading
time of most uncompressed TIFF images to 1/5th of the load time required for
the current implementation. I've run the suite
I have just submitted two patches to the Sanselan code tree. These address
issues a byte-order bug (Sanselan issue #54) and a speed enhancement (Sanselan
issue #56).I uploaded the patches as attachments to their associated issues.
Since I am new to using Subversion and the JIRA issue track
is for.
Cheers,
Gary
On Fri, Sep 30, 2011 at 1:32 PM, Gary Lucas wrote:
> I am working on a couple of patches for sanselan. These involve about
> a couple of dozen files. I had two questions about coding style:
>
> First question: Is it okay to use generics for collections? Thes
I am working on a couple of patches for sanselan. These involve about a couple
of dozen files. I had two questions about coding style:
First question: Is it okay to use generics for collections? These are a Java
1.5 element and I've noticed a couple of comments on the project page
mentioning
I've been trying to implement code to write GeoTIFF tags to TIFF files. I was
unable to find any code examples or documentation for this operation, but after
digging through the code, it looks like the TiffImageWriterLossy and
TiffImageWriterLossless classes may be the place to do this.
Tiff
21 matches
Mail list logo
