A follow-up to my last message. I do see where the jxTreeIcon item is using data URI for the image but there is still a ton of chatter with the server. With every scale change, the GETLEGENDIMAGE operation is issued for each legend icon and it appears that there is no caching occurring.
Perhaps most of the slowness is in JxTree itself and the client-side assembly of the tree. The AJAX viewer legend is asynchronous and only requests legend images for what are visible whereas the Fusion legend requests ALL of them regardless of their visibility on scale change. -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Fusion-legend-performance-fixes-in-the-future-tp5087026p5087092.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
