[mapguide-internals] Adding comments to styles

Walt Welton-Lair walt.welton-lair at autodesk.com
Mon Jun 20 12:40:48 EDT 2011


Changed subject from "RE: [mapguide-internals] RFC 113 - Support Path Scaling In Symbol Definition is ready for review"...


I just want to point out that you can use the existing ExtendedData1 elements to store description / metadata information.  ExtendedData1 was originally introduced as a means for "allocating space for future, additional, and validatable data", but it also works for storing that kind of data.  Unlike pure XML comments, the MG MdfModel preserves all information in ExtendedData1 elements when you deserialize / serialize a model.

Walt

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Zac Spitzer
Sent: Friday, June 17, 2011 11:01 AM
To: MapGuide Internals Mail List
Subject: Re: [mapguide-internals] RFC 113 - Support Path Scaling In Symbol Definition is ready for review

adding a comments/notes/hint attribute sounds like a good approach

On Fri, Jun 17, 2011 at 12:56 PM, Jason Birch <jason at jasonbirch.com> wrote:
> Defective design? :)
>
> I've only really felt the need to annotate advanced styles. And that 
> extends to general usage comments (e.g. symbol dimensions, behaviour) 
> and annotations of the various components such as what a particular 
> path or reference represents.
>
> I wonder if it would be less labour-intensive to add elements and/or 
> attributes to the style that allow storing this information?
>
> J
>
> On 2011-06-16, Jackie Ng <jumpinjackie at gmail.com> wrote:
>> Well that isn't really a defect per se, it is sort of by design. 
>> Because the .net XmlSerializer is serializing raw XML content into a 
>> strongly-typed object graph, stuff that is not represented in the 
>> object graph (like
>> comments) is lost along the way.
>>
>> Sure we can override the Maestro serialization/deserializtion logic 
>> to preserve comments, but this would have to be done for *every 
>> resource class and their known versions*, which is a lot of work for little gain.
>>
>> - Jackie
>>
>> --
>> View this message in context:
>> http://osgeo-org.1803224.n2.nabble.com/RFC-113-Support-Path-Scaling-I
>> n-Symbol-Definition-is-ready-for-review-tp6460741p6485368.html
>> Sent from the MapGuide Internals mailing list archive at Nabble.com.
>> _______________________________________________
>> mapguide-internals mailing list
>> mapguide-internals at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>>
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>



--
Zac Spitzer
Solution Architect / Director
Ennoble Consultancy Australia
http://www.ennoble.com.au
http://zacster.blogspot.com
+61 405 847 168
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals


More information about the mapguide-internals mailing list