[udig-devel] dpi issues

[Jody Garnett]

Vince Darley wrote:
> At 21:20 26/03/2008, Jody Garnett wrote:
>> I have been thinking a bit more about this; and I agree with you that 
>> ApplicationGIS.drawMap() should "do the right thing" taking scale and 
>> so forth into account as needed.
> Great!
Aside - my decision is not abitrary - udig guideline "Code for 
Convenience" = principle of "least surprise" applies to developers as 
well as users
>> It sounds like the issue of printing (from BIRT or iText) may need 
>> some additional control;
> Of course it would eventually be desirable to allow udig to make use 
> of BIRT's full 'device' capability which would enable 
> device-independent & resolution-independent output to svg, pdf, etc, 
> as well as image output.  This would mean providing a udig renderer 
> which renders to the birt device api.  (see 
> org.eclipse.birt.chart.device.(svg|swt|pdf|...))
>
> I don't know anything about udig rendering chain so have no idea how 
> practical that is.  The results would be very impressive, however.  My 
> little searching suggested that it would involve building a Graphics2D 
> bridge on top of birt's device API (kind of the opposite of what 
> org.eclipse.birt.chart.device.swing.SwingRenderImpl does).
>
> But this goes quite far beyond what I'm looking for at the moment, 
> which is simply getting decent high-resolution output.
Right; well the question becomes - is scaling a raster onto your advice 
a good enough approximation?
>> my gut feeling is we should make some of the MapBoxPrinter / 
>> ExportMapToImageWizard functionality available for others to reuse as 
>> a separate issue. I have confirmed that the Rescale code has only 
>> been applied to trunk.
> ok.  I keep thinking we should move to trunk, but I guess it's still 
> not ready for much?
Hard to know how to respond to that; I can only get paid to work on 
trunk so that is where the action is for new development.
Jody