This is actually much easier, and makes more sense, in MapGuide Enterprise.
MGE does not share the MWF / MWX / DAT concept at all. Instead, you have a
repository of datasources, then layers created from those datasources, then
maps which contains one or more of those layers, and then a web layout that
contains a map. At the time a web layout is requested by the viewer, the
entire thing is assembled at the server. For your situation, in MGE, you
wouldn't even necessarily have to have a map defined at all in the server
repository. Or even layers for that matter. Using the API you could
assemble the map from underlying feature sources and dynamically assemble
the layers and maps. You would still have to develop the interface that
lets the user choose from (and optionally style) the available layers and
then return the resultant map, but this can all be done using the
server-side API.
--
Andy Morsell, P.E.
Spatial Integrators, Inc.
http://www.SpatialGIS.com
wrote in message news:5430476@discussion.autodesk.com...
In the 6.5 version of MapGuide we were using the dynamic authoring toolkit
to create and modify MWX files programmatically. One of the main reasons we
wanted to do this is we have a large number of DWG's or SDF's that a user
may select from and they need to be swapped in an out of the viewer, but we
didn't want to have to load them all as MWF's initially, so it made sense
for us to create a MWX and set the drawing files to be used in the XML file.
We loaded the MWX file into memory, and then changed the DWG layer node
("MapLayers/DWGLayer/DWGLayerDataSources/DWGFeatureDataSource/DWG") at
runtime to point to a user specified DWG. Finally we serialized the MWX to
disk as a temporary MWF file and passed it back to the user.
Is there a similar way to perform this task in MapGuide Enterprise?