Its not a big deal. Don't let uDig hold up fixes. We can track until we
get something stable. I just didn't realize that it was a risk factor. I
will update uDig now that I know that it is not published API. I can look
at using LiteRenderer again but I wish I knew why we stopped using it.
Originally we used LiteRenderer to render coverages then I think Cory
changed it when he was doing some work on it. I don't know what his reason
was. I wouldn't be surprised if it doesnt apply anymore. I am CCing the
uDig list and maybe someone can remind me.
In the mean time I am just patching uDig to work with the new
GridCoverageRenderer.
Jesse
On Mon, Aug 24, 2009 at 11:01 AM, Andrea Aime <[email protected]> wrote:
> Jesse Eichar ha scritto:
>
>> Hi,
>>
>> Did the GridCoverageRenderer constructor just change? I am suddenly
>> getting compile errors in uDig.
>>
>
> It did:
>
> http://jira.codehaus.org/browse/GEOT-2534
>
> Never really considered GridCoverageRenderer as published API,
> people are supposed to go through a GTRenderer to render maps.
> If you want we can add back a backwards compatible version?
>
> Cheers
> Andrea
>
> --
> Andrea Aime
> OpenGeo - http://opengeo.org
> Expert service straight from the developers.
>
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
