[mapguide-internals] For Review : Mapguide RFC 31
-SymbolDefinition Support for Edit Controls and Rich
traian.stanev at autodesk.com
Tue Sep 18 12:44:07 EDT 2007
I am concerned about the new additions to the DataType element. Most of
them are redunadant. Even in the example given in the RFC, the DataType
is set to Angle and specifies that the LBL_ROTATION parameter represents
an Angle. The LBL_ROTATION itself is already referenced inside an
<Angle> element, so there really is no point to specifying a data type
Apart from the redundancy, my concern is that client apps will be coded
to rely on those data type hints exclusively instead of inferring the
data types from the actual contents of the symbol and thus will be
unable to consume symbols created by third parties without undue burden
on the third party to add all those "optional" DataType elements.
Also, the element name DataType is not even meaningful anymore if it can
be set to things like "FillColor" or "LineColor" since arguably these
are both the same data type (color).
From: mapguide-internals-bounces at lists.osgeo.org
[mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Vishal
Sent: Tuesday, September 18, 2007 12:25 PM
To: mapguide-internals at lists.osgeo.org
Subject: [mapguide-internals] For Review : Mapguide RFC 31
-SymbolDefinition Support for Edit Controls and Rich TextSupport
Mapguide RFC 31 (SymbolDefinition Support for Edit Controls and Rich
Text Support (Markup)) is available for review.
Your participation and feedback will be appreciated.
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
More information about the mapguide-internals