Changes between Version 37 and Version 38 of MapGuideRfc67

Timestamp:

Jun 19, 2009, 4:13:59 PM (15 years ago)

Author:

gregboone

Comment:

--

MapGuideRfc67

@@ -115 +115 @@
 
 
-The Data property includes a resource id that corresponds to the feature source definition defining the feature source for print element layout data. The !FeatureClass property within the Data property describes the fully qualified feature class name of the print element layout data.
+The Data property includes a resource id that corresponds to the feature source definition defining the feature source for print element layout data.  The !FeatureClass property within the Data property describes the fully qualified feature class name of the print element layout data. The Data element also includes a property that identifies the Geometry property within the feature class, a Filter property to specify an FDO filter for the features to retrieve, and a set of property mappings.  These property mappings typically are used for determining which column names in the feature class that is used for print layout element type map to which property in a print layout element type.  For example, imagine a feature class named “!NorthArrowFeatureClass” is used for storing north arrow print layout element data (a point feature class) with a column “GEOM” that corresponds to the geometry column and “ORIENTATION,” and a north arrow print layout element schema contains a Rotation property.  Then, the north arrow resource Xml will contain the “GEOM” as a property in the Data property along with a property mapping collection that contains a source property called “ORIENTATION” whose source units could be “radians” and a target property called “Rotation”.  This helps with north arrow realization updating the correct property value of the point feature whenever it is notified of a twist angle change in the viewport it is associated with.
 
 The Stylization property refers to a resource id that corresponds to the layer definition containing stylization information for the print layout element data (described by Data property).  Typically, this will include the composite type style but in general can include any capability we have today in a !LayerDefinition schema. The composite type style can include composite symbolization comprising simple or compound symbol definitions.
@@ -140 +140 @@
 
 The Print Layout architecture also allows for creation of print layout elements that are used as adornments and decorations on other print layout elements.  The decorators are elements that might alter the stylized geometry of their target print layout element and adorners simply draw their own stylized geometry around their target print layout elements. An example of an adorner is a Border print layout element type that can draw a fancy border with symbols around a map viewport print layout element.  These aspects allow for powerful composition of print layout elements.
+
+The following sections discuss the runtime common components that represent various print layout element types.  
 
 ==== !MgPrintLayoutElementBase class ====