Hello,<br><br>I agree with Daniel and Worth :) I am working with mapscript to help to generate mapfile to use it as map file configuration for WMs service. I really need to get method to manage my mapfile.<br><br>[a little bit off topic]<br>
I have the same issue with outputformat object: I can't get a list of outputformat from the mapfile. outputformatlist() method doesn't exist in python mapscript.<br>[/a little bit off topic]<br><br>Thanks,<br><br>
Y.<br><div class="gmail_extra"><br><br><div class="gmail_quote">2012/12/14 Daniel Morissette <span dir="ltr"><<a href="mailto:dmorissette@mapgears.com" target="_blank">dmorissette@mapgears.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I object. :)<br>
<br>
I agree with Worth that this should be supported in MapScript otherwise skipping features like this would mean that over time MapScript will become a second class citizen.<br>
<br>
Even if it is possible in theory to do the same thing in MapScript with custom code, RFC-86 proposes a nice way to handle a common need directly in the mapfile without custom coding, and my opinion is that a given mapfile should work the same way when rendered through the mapserv CGI as when it is rendered through MapScript. A generic MapScript app should be able to open any mapfile built for the CGI and render it without requiring custom code.<br>
<br>
Are the scaletokens processed at rendering time in your implementation? If yes then it should not be that hard to support it in MapScript, or is there some blocker that we are not aware of?<br>
<br>
My 0.02$<br>
<br>
Daniel<div><div class="h5"><br>
<br>
On 12-12-14 3:41 AM, thomas bonfort wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
Devs,<br>
<br>
There's a point that I overlooked when submitting RFC86, which concerns<br>
exposing the scale dependent token mechanism to mapscript.<br>
<br>
I'd argue that the whole point of the RFC is to simplify mapfile<br>
management thus avoiding the use of mapscript in a number of cases, and<br>
that there is no real usecase in exposing this API to mapscript (as a<br>
mapscript script can do these replacements directly on the layer's<br>
data/filter).<br>
If there is no objection, I will amend the mapscript part of the RFC to<br>
state: "Given the more straightforward methods to obtain the same<br>
results as this RFC in mapscript, access to a layer's SCALETOKENs will<br>
not be exposed to mapscript for the time being".<br>
<br>
So, are there any objections? :)<br>
<br>
cheers,<br>
thomas<br>
<br>
<br></div></div>
______________________________<u></u>_________________<br>
mapserver-dev mailing list<br>
<a href="mailto:mapserver-dev@lists.osgeo.org" target="_blank">mapserver-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/mapserver-dev" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/mapserver-dev</a><br>
<br><span class="HOEnZb"><font color="#888888">
</font></span></blockquote><span class="HOEnZb"><font color="#888888">
<br>
<br>
-- <br>
Daniel Morissette<br>
<a href="http://www.mapgears.com/" target="_blank">http://www.mapgears.com/</a><br>
Provider of Professional MapServer Support since 2000<br>
<br>
______________________________<u></u>_________________<br>
mapserver-dev mailing list<br>
<a href="mailto:mapserver-dev@lists.osgeo.org" target="_blank">mapserver-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/mapserver-dev" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/mapserver-dev</a><br>
</font></span></blockquote></div><br><br clear="all"><br>-- <br>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">Responsable Formation et Support</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">Camptocamp France SAS</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">Savoie Technolac, BP 352</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">73377 Le Bourget du Lac, Cedex</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">Tel (France) : +33 4 79 26 57 98</p><p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">
Tel (Suisse) : 02 16 190 10 43 (new)<br></p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">Mob. : +33 6 18 75 42 21</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">Fax : 04 79 70 15 81</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">Mail : <a href="mailto:yves.jacolin@camptocamp.com" target="_blank">yves.jacolin@camptocamp.com</a></p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"><a href="http://www.camptocamp.com" target="_blank">http://www.camptocamp.com</a></p><a href="mailto:yves.jacolin@camptocamp.com" target="_blank"></a><br>
</div>