server-side SLD support

[Bart van den Eijnden (OSGIS)]

Steve,

to be honest I personally don't see a use case/necessity for mixing the two.

Best regards,
Bart

--
Bart van den Eijnden
OSGIS, Open Source GIS
http://www.osgis.nl


--------- Oorspronkelijk bericht --------
Van: Steve Lime <Steve.Lime at DNR.STATE.MN.US>
Naar: MAPSERVER-DEV at LISTS.UMN.EDU <MAPSERVER-DEV at LISTS.UMN.EDU>
Onderwerp: Re: [UMN_MAPSERVER-DEV] server-side SLD support
Datum: 01/11/06 21:36

> Why would someone want to mix SLD and MapServer classes? Is there an
> obvious
> use case? I like the idea (for non-OWS use as well), but would prefer
> keeping things
> simple. 
> 
> Steve
> 
> &gt;&gt;&gt; Daniel Morissette &lt;dmorissette at MAPGEARS.COM&gt; 11/1/2006
3:30 PM &gt;&gt;&gt;
> Yewondwossen Assefa wrote:
> &gt; 
> &gt;  I am more leaning to say that we should not save the classes
> generated, 
> &gt; but only the SLD (marking the classes as temporary as you suggested).
> 
> &gt; But when we talk about save, it is done through mapscript, so the
> users 
> &gt; will have the ability to manipulate the classes before saving the map
> 
> &gt; and next reload of the map will givent diffrent result.
> &gt; If it is a documented and acceptable limitation, I do not see any 
> &gt; problem discarding the new classes created.
> &gt; 
> 
> This kind of inconsistent behavior makes me nervous. What you propose 
> reopens the questions that I sent earlier this morning.
> 
> I mean someone could load a mapfile with MapScript, not knowing that it
> 
> contained a SLD ref. Then modify a few classes (including some coming 
> from a SLD) or insert new classes and save the map, expecting the 
> changes to be saved, but then because the MapScript code was not 
> SLD-aware the changes would actually be lost and odd side-effects might
> 
> happen next time the saved map is loaded.
> 
> I'm also not clear on whether the current ApplySLD() method is 
> sufficient for MapScript apps to interact with this feature if you plan
> 
> to maintain both the SLD ref and a set of temporary classes in memory.
> 
> &gt;&gt; Maybe if we don't allow people to mix SLD and CLASSes, it would
make
> 
> &gt;&gt; life easier? But still the generated classes would need to be
> removed 
> &gt;&gt; and the SLD keyword written upon saving.
> &gt;&gt;
> &gt;  I still think we should allow the mixing of SLD and CLASS elements
> and 
> &gt; mark SLD generated classes as &quot;non savable&quot;
> &gt; 
> 
> Mixing SLD and CLASS elements would be nice, but if that becomes the 
> source of odd side-effects for apps that are not SLD-aware then that's
> 
> not good.
> 
> Daniel
> -- 
> Daniel Morissette
> http://www.mapgears.com/
> 
>