Changes between Version 24 and Version 25 of MapGuideRfc67

Timestamp:

Jun 19, 2009, 1:35:45 PM (15 years ago)

Author:

gregboone

Comment:

--

MapGuideRfc67

@@ -220 +220 @@
     • Client builds a layer definition, if applicable (for !MapViewport resources, this step is not necessary) that references the feature source definition and adds it to Resource Service by calling !SetResource.[[BR]]
 
+==== Adding a print layout element ====
+
+This use case is part of use cases that realize a particular type of print layout element.
+
+[[BR]]
+    [[Image(AddPrintLayoutElementUseCase2.PNG, 1400)]]
+[[BR]]
+
+''PRECONDITIONS''
+
+    • Adding required data for map viewport creation use case
+
+''STEPS''
+
+    • Client builds an Xml for a particular type of print layout element.  In this Xml, he specifies the Data.!ResourceId property to point to the feature source definition and the Stylization.ResourceId property to point to the layer definition created in the previous steps.  He also sets the fully qualified feature class name of the print layout element data in Data.FeatureClass property.[[BR]]
+    • Client adds this Xml to Resource Service by calling !SetResource(printLayoutElementResId, printLayoutElementXml)[[BR]]
+    • The Resource Service implementation creates an instance of !PrintLayoutResourcesOwner if not already created and adds it to a named dictionary.[[BR]]
+    • The Resource Service calls !AddResource on !MapPrintLayoutResourcesOwner object.[[BR]]
+    • !PrintLayoutResourcesOwner determines the type of the print layout element that is being added and creates an runtime representation object for the resource. In case of !MapViewport resources, this would be !MapViewportResource, inherited from !MapResource class.[[BR]]
+    • !PrintLayoutResourcesOwner then adds this runtime object to Resource Manager and also subscribes to Resource Manager events, if not already done.[[BR]]
+
 
 == Implications ==