Changes between Version 23 and Version 24 of MapGuideRfc67

Timestamp:

06/19/09 13:20:48 (16 years ago)

Author:

gregboone

Comment:

--

MapGuideRfc67

@@ -204 +204 @@
 This use case is part of use cases involving creation of specific types of print layout elements. The sequence diagram below shows the various steps involved. The sequence assumes the client doesn’t have a data store for storing layout element data.
 
+[[BR]]
+    [[Image(AddRequiredDataUseCase.PNG)]]
+[[BR]]
+
+''PRECONDITIONS''
+
+    • None
+
+''STEPS''
+
+    • Platform client gets the product-specific implementation of resource service.[[BR]]
+    • Client creates a new data store and builds a feature source definition referencing the created data store.[[BR]]
+    • Client adds the feature source definition to resource service by calling !SetResource(fsId, fsXml). This data store will contain the print layout data that will be used to draw the geometry and stylize various aspects of the particular type of print layout element.[[BR]]
+    • If the client chooses to use an existing feature source connection, then the above step can be skipped.[[BR]]
+    • 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]]
+
+
 == Implications ==