Cool.
Sure hope this makes it in; allowing users of Fusion apps to toggle
between the various Google/Virtual Earth/WMS/TMS base layers and
in-house base layers would be a killer feature. In my case it would
also allow me to offload ortho serving to Google or (hopefully with the
next round of orthos) to OAM or another caching tile server.
Another semi-related question... I know that Zac has had some success
using the OpenLayers MapGuide provider with an array of map services
(multiple DNS hosts pointing to the same service) to allow for multiple
connections. Is there any way of configuring Fusion to take advantage
of this? Currently I think that you can only configure a single
MapAgent?. It would be cool if the mapagent could be defined as a list
in the config file, with the first entry being used for session
management and general mapagent calls, and the additional entries being
used for tile requests. Is this something that it is worth putting in
an enhancement request for?
Jason
-----Original Message-----
From: Paul Spencer
Subject: Re: [mapguide-internals] Fusion - Base layers questions...
this is not supported yet, Mike has been working on and off on this.
It is still my intention to get this done for Fusion 2.0 which would
hopefully also be included in MapGuide 2.1.
Mike is wrapping up the 1.1 release (there will still be some
outstanding bugs) in the next day or so, and then moving on to getting
ready for a 2.0 beta in time for inclusion in the MapGuide 2.1 beta.
At this point, there are two remaining features I would like to get
in, arbitrary OpenLayers layers and changing from the existing client
side vector code to OpenLayers vector code.
_______________________________________________
fusion-dev mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fusion-dev
