Changes between Version 5 and Version 6 of MapGuideRfc108


Ignore:
Timestamp:
07/30/10 00:51:45 (14 years ago)
Author:
hubu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MapGuideRfc108

    v5 v6  
    3232== Proposed Solution ==
    3333
    34 1.      Create a new resource type that contains information about watermark. This resource is used to define the what element to use(image or text) and where/how to place the watermark.
     341.      Create a new resource type that contains information about watermark. This resource is used to define the what element to use(image or text) and where/how to place the watermark. Add a new XSD file to define the watermark, and the MdfModel and MdfParser are needed to updated about this change. We’ll use the symbol library in MapGuide server to store the images for watermark.
    3535
    36 2.      User can use watermark by defining reference from map. The Map definition will be extented to reference the optional watermark resource. And a Map definition can reference multiple watermark resources.
     362.      User can use watermark by defining reference from map. The Map definition will be extented to reference the optional watermark resource. And a Map definition can reference multiple watermark resources. In the MgMap class, we add a "WatermarkList" field.
    3737
    38 3.      The watermark of WMS will automatically be the same as the published map.
     383.      Change the render logic for map. When all the layers have been rendered and the renderer hasn’t output the result, render the watermark into the result.
    3939
    40 4.      Change the render logic for map. When all the layers have been rendered and the renderer hasn’t output the result, render the watermark into the result.
     404.      For WMS publish, when a map definition is published, the watermark will be added to each layer definition’s header. When the temporary map is created for WMS, it will read to see if any layer has watermark in its definition’s header. If it finds one, it will add the watermark into its "WatermarkList" field.
    4141
    4242== Implications ==
    4343
    44 MapGuide Mastro should update to support watermark.
     44MapGuide Mastro should update to add some UI to define watermark resource and add watermark into a Map.
    4545
    4646== Test Plan ==
    4747
    48 How the proposed change will be tested, if applicable.  New unit tests should be detailed here???
     48Build/Run on Windows/Linux
    4949
    5050== Funding / Resources ==
    5151
    52 This section will confirm that the proposed feature has enough support to proceed.  This would typically mean that the entity making the changes would put forward the RFC, but a non-developer could act as an RFC author if they are sure they have the funding to cover the change.
     52Supplied by Autodesk