Changes between Version 16 and Version 17 of MapGuideRfc67


Ignore:
Timestamp:
06/19/09 12:23:59 (15 years ago)
Author:
gregboone
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MapGuideRfc67

    v16 v17  
    139139The 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.
    140140
     141==== !MgPrintLayoutElementBase class ====
     142
     143This class represents the base class for all print layout elements. This is what is returned when a platform client realizes a print layout element using a product-specific print layout service object.
     144
     145This class has properties that are separated out of the actual print layout element schema. For example, Visibility property is externalized from the print layout element itself so that it is controlled at runtime as opposed to hard-coding it. This class and its resource are very analogous to !MgLayerBase and its associated layer definition resource. The !MapDefinition resource actually defines the visibility of each layer and as such !LayerDefinition itself does not contain a Visiblity property. Name is another such property.
     146
     147The !GetResourceId() method returns the resource identifier of the print layout element itself.  Typically, this will be supplied at the construction time of !MgPrintLayoutElementBase.  This again is very similar to !MgLayerBase.
     148
     149The !ForceRefresh() method exists to allow for products that can’t automatically respond to associated resource changes.  Such a product is !MapGuide where there can be no event support (this is not possible even internally since the site server and web server could be separated).  In such products, a client that modifies a resource must invoke a method on the object that is affected by the resource change directly.  In Layer API of Geospatial Platform, the !ForceRefresh on !MgLayerBase helps refresh the layer after its layer definition was modified.
     150
     151
    141152
    142153== Implications ==