Changes between Version 9 and Version 10 of MapGuideRfc52


Ignore:
Timestamp:
07/28/08 14:45:58 (16 years ago)
Author:
waltweltonlair
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MapGuideRfc52

    v9 v10  
    2828== Motivation ==
    2929
    30 The GD renderer was !MapGuide's initial image-based renderer.  While it does a good job, the AGG renderer now provides superior image quality, especially when it comes to anti-aliasing.  The AGG renderer is now also mature in terms of stability and performance.  For this reason AGG is configured as !MapGuide's default image-based renderer.  As of today (7/24/2008) there are two reported issues involving AGG (#632 and #634).
     30The GD renderer was !MapGuide's initial image-based renderer.  While it does a good job, the AGG renderer now provides superior image quality, especially when it comes to anti-aliasing.  The AGG renderer is now also mature in terms of stability and performance.  For this reason AGG is configured as !MapGuide's default image-based renderer.  As of today (7/28/2008) there are three reported issues involving AGG (#459, #632, and #634).
    3131
    3232One of GD renderer's biggest issues is that it doesn't provide full support for the new stylization ([wiki:MapGuideRfc32 MapGuide RFC 14]).  In particular it does not support clipped area styles.  While support for this could be added, it seems like a waste of time given that AGG already fully supports the new stylization ''and'' provides better image quality.  A recent RFC around raster reprojection ([wiki:MapGuideRfc32 MapGuide RFC 51]) also raised the issue as to whether GD renderer would need to be updated.