Changes between Version 28 and Version 29 of MapGuideRfc14


Ignore:
Timestamp:
02/07/07 10:43:39 (18 years ago)
Author:
traianstanev
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MapGuideRfc14

    v28 v29  
    283283== Implications ==
    284284
    285 The new symbol definitions and cartographic engine will obviously have an impact on the !LayerDefinition XML schema. Those changes will be proposed in a subsequent RFC. That RFC will discuss any potential compatibility issues, however non are anticipated at this time.
     285The new symbol definitions will have an imapct on the Layer Definition XML schema. To preserve backwards compatibility,
     286we propose to add a new element, a !CompositeTypeStyle that will be the only LDF element that references new symbol definitions.
     287The !CompositeTypeStyle inherits !FeatureTypeStyle alongside Area, Line and !PointTypeStyle. Layers that have a !CompositeTypeStyle
     288will use a new code path for stylization based on the new !SymbolDefinitions. Stylization of layers that have one of the old
     289!TypeStyles will not change. Thus one will be able to mix the two kinds of layers within the same map.
     290
     291Just like the other !FeatureTypeStyles, the !CompositeTypeStyle will hold on to a symbolization object (!CompositeSymbolization),
     292which defines the way features draw. The !CompositeSymbolization will reference a !SymbolDefinition and also optionally define
     293theming expressions for properties of the !SymbolDefinition which are marked as parametrized. Those allow for the symbol definition
     294to take up styles based on attributes of the specific feature class that the !CompositeSymbolization is associated with.
     295
     296See Appendix A for a link to the schema for the proposed Layer Definition additions.
    286297
    287298== Test Plan ==