Changes between Version 20 and Version 21 of MapGuideRfc67


Ignore:
Timestamp:
Jun 19, 2009, 12:58:50 PM (15 years ago)
Author:
gregboone
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MapGuideRfc67

    v20 v21  
    170170The !GetElements() method returns a collection of actual runtime print layout element instances that are created for the Elements resource id collection.  This is all very similar to !MgMapBase having !GetLayers() returning !MgLayerCollection. Whenever a print layout element is added to or removed from the elements collection, a notification is sent out for listeners interested in the change. Those notifications are obviously on the !XxxMapPrintLayout class since the Common Platform API does not handle events.
    171171
     172[[BR]]
     173    [[Image(PrintLayoutElementCollection.PNG)]]
     174[[BR]]
     175
     176==== Print Layout Templates (Future Direction) ====
     177
     178The idea of using templates to expedite and ease the process of creation of print layouts has been around and is used in such products as AutoCAD, Topobase and ESRI (!ArcGis).  However, the templates used are not inter-operable yet because of a lack of common definition of what that template will be. Typically, you’d create a print layout using an existing template that defines what type of print layout elements should appear, where and how. The ideas of reusing a print layout resource definition for print layout template has been slightly explored with the assumption that when the print layout elements within the template are realized during the creation of an actual print layout, the ambient information is automatically used without further indulgence from the user. For example, if a map viewport is included in the template, we won’t obviously have enough information about what map it will display, what the view of the map is, etc., but we would associate all map viewports with the current map and default view (entire map), for example, upon realization of a print layout using the template.
     179
     180We need more research and elaboration to come up with details on how this would work uniformly across products.
     181
    172182== Implications ==
    173183