Hi Jody,

you were right. I also cannot access any help pages. I had been looking at the 
TOC only and had not ventured further when I did the first test. Stupid me.


Jody wrote:
> So the "solution" for this is to either ...
> 1. spend days testing and making another JRE or ...
> 2. leave all the options in and let people figure out what works ...
> 
> It seems a strange design to me; there is not really enough information 
> made available through the API for us to make a good decision as a 
> programmer. Like I could try and turn off formats that involve native 
> DLLs; but some of the things like jpeg2000 should only be there if Jesse 
> packaged up the JRE that included gdal; rather than the plain JRE that 
> is on the website....

My approach in this case would be to disable automatic file format discovery 
and hard code the list of available formats to those that were positively 
tested on all platforms with exactly the JRE that's supposed to be used for 
release.
Yes, this means some testing work, but it is imho better than have people 
complaining because the stable release contains obvious bugs.


> I am going to install on this machine; and check what JRE was packaged up.

What do you mean with "what JRE". What are the choices?

The SC1 release contains 1.6.0_06, JAI 1.1.3 is included. Sounds sensible to 
me. I cannot see any traces of gdal but I am not exactly sure for what files I 
should be looking.
I tried it with my system JRE (1.6.0_07 b06 + JAI 1.1.3). No change.

BTW: jpeg2000 works for me. PhotoImpact complains that it is an CMYK image, but 
if it combines the channels the image looks fine. Why is uDig exporting CMY 
images instead of RGB anyway ...

But looking at the source right now I see that you don't give any arguments to 
ImageIO at all:
    ImageIO.write(image, getFormatName(), destination);
This is likely the source of some problems. I guess in the future uDig will 
need an image options dialog anyway, to set compression ratio and the like.

In my apps I use the JAI filestore operation to write the image like this:

                JPEGEncodeParam params= new JPEGEncodeParam();
                params.setQuality(quality);
                params.setRestartInterval(64);

                ParameterBlock pb = new ParameterBlock();
                pb.addSource(img);
                pb.add(fileName);
                pb.add(format);
                pb.add(params);
                JAI.create("filestore", pb);

This works fine for me.

> Thanks for the dedicated testing; I will do what I can but I would 
> rather see us focus on things like the translation problems (that have 
> value for us going forward) than issues with the legend map graphic or 
> even image export.

Not following here: Translation problems are cosmetical, they usually don't 
prevent the user from working. The other problems will create confusion for end 
users, which spoils the image people will get of uDig.

Anyway, happy bug killing.
-- 
Matthias Basler
[EMAIL PROTECTED]

_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel

Reply via email to