atom feed29 messages in net.java.dev.jai-imageio.interestRe: [JAI-IMAGEIO] Mac OS X native ver...
FromSent OnAttachments
Marco Sambin - NeoLogicaSep 6, 2007 8:16 am 
jai-...@javadesktop.orgNov 2, 2007 3:19 pm 
robert engelsNov 2, 2007 3:19 pm 
jai-...@javadesktop.orgNov 2, 2007 3:34 pm 
robert engelsNov 2, 2007 3:34 pm 
robert engelsNov 2, 2007 3:39 pm 
Bob DeenNov 2, 2007 4:01 pm 
robert engelsNov 2, 2007 4:19 pm 
Bob DeenNov 2, 2007 6:16 pm 
robert engelsNov 3, 2007 12:28 am 
Marco Sambin - NeoLogicaNov 5, 2007 12:39 am 
jai-...@javadesktop.orgNov 5, 2007 5:12 pm 
Bob DeenNov 5, 2007 6:07 pm 
jai-...@javadesktop.orgNov 6, 2007 5:00 pm 
Marco Sambin - NeoLogicaNov 20, 2007 10:04 am 
jai-...@javadesktop.orgFeb 4, 2008 11:47 pm 
Marco Sambin - NeoLogicaFeb 5, 2008 12:47 am 
Fabrizio GiudiciFeb 6, 2008 12:04 am 
Marco Sambin - NeoLogicaFeb 6, 2008 1:01 am 
fabr...@tidalwave.itFeb 6, 2008 3:35 am 
Bob DeenFeb 6, 2008 9:59 am 
Brian BurkhalterFeb 6, 2008 10:07 am 
robert engelsFeb 6, 2008 10:10 am 
Brian BurkhalterFeb 6, 2008 10:16 am 
robert engelsFeb 6, 2008 10:24 am 
Brian BurkhalterFeb 6, 2008 10:28 am 
robert engelsFeb 6, 2008 10:33 am 
Brian BurkhalterFeb 6, 2008 10:50 am 
jai-...@javadesktop.orgMar 10, 2008 6:50 am 
Subject:Re: [JAI-IMAGEIO] Mac OS X native version of JIIO
From:Bob Deen (Bob.@jpl.nasa.gov)
Date:Nov 2, 2007 4:01:54 pm
List:net.java.dev.jai-imageio.interest

robert engels wrote:

I also think this would be a perfect time to drop the stupid XML based metadata with ImageIO. This is by far the hardest/time consuming things about writing plugins.

Let's start by defining our own interface for the standard metadata (with a default impl that can read the standard xml/metadata), and then custom interfaces for the formats.

Like:

interface StandardMetadata { int getWidth(); int getHeight(); int getHDPI(); int getVDPI(); ... }

The problem of course is that the plugins are written to be as format- neutral as possible. That's why the XML-based metadata exists... it allows one to accommodate a nearly arbitrary metadata content without any API change. Changing that fundamental philosophy would I think be a bad idea.

However, there is definite value in having a convenience layer... something that takes common calls like you have in your example and translates to/from the underlying XML. Hide all that nastiness from the casual user, although the nastiness is still there for those who need it.

-Bob