Changes between Version 3 and Version 4 of MapGuideRfc52

Timestamp:

Jul 16, 2008, 1:28:00 PM (16 years ago)

Author:

waltweltonlair

Comment:

--

MapGuideRfc52

@@ -28 +28 @@
 == Motivation ==
 
-The GD renderer was !MapGuide's initial image-based renderer.  While it did 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 - it currently has no open issues.  For this reason AGG is configured as !MapGuide's default image-based renderer.
+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/16/2008) there is only one open issue (#632).
 
 One 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.