[mapguide-internals] RFC 113 - Support Path Scaling In Symbol Definition is ready for review

[Zac Spitzer]

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-In-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