<html>
<head>
<style type="text/css">
<!--
body { margin-left: 4px; margin-top: 4px; margin-bottom: 1px; margin-right: 4px; font-variant: normal; line-height: normal }
p { margin-top: 0; margin-bottom: 0 }
-->
</style>
</head>
<body style="margin-left: 4px; margin-top: 4px; margin-bottom: 1px; margin-right: 4px">
<p style="margin-top: 0; margin-bottom: 0">
<font face="Comic Sans MS" size="3">All,</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font face="Comic Sans MS" size="3">So what would be the expected additional capabilities of using mode=openlayers over using mode=map? (Especially with regard to only viewing a single layer, TBW, I see this MODE= option as primarily a way to compare more than one layer to others) The many layers is what I'm interested in seeing as a test tool. mode=map already builds a composite map.</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font face="Comic Sans MS" size="3">bobb</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<br>
<br>
>>> Daniel Morissette <dmorissette@mapgears.com> wrote:<br> </p>
<div style="margin-left: 15px; padding-left: 7px; margin-top: 0; margin-bottom: 0; margin-right: 0; border-left: solid 1px #050505; background-color: #f3f3f3">
<p style="margin-top: 0; margin-bottom: 0">
Paul Ramsey wrote:<br>> The beauty part of mode=openlayers is that mapserver doesn't even need<br>> to ship code with it, it can just emit an HTML page that references<br>> openlayers.org.<br><br>Exactly.<br><br>> Any framework that requires server-side components and<br>> isn't cloud-hosted already is kind of out-of-luck.<br><br>A framework that already comes with some server-side dependencies could<br>presumably ship with a generic MapServer template that could already be<br>used today as a generic viewer with mode=browse... no special mode<br>required in this case I don't think.<br><br><br>> There could also be<br>> a mode=googlemaps in combination with the tile mode or a mode=bingmaps<br>> ...<br>><br><br>My comment about keeping this __simple__ was exactly to prevent a<br>proliferation of mode=this, mode=that, etc...<br><br>The initial need is to offer the users a __simple__ mechanism top\<br>preview a mapfile contents, not to link or promote any client framework<br>in particular. The choice of OpenLayers as the default is obvious in my<br>mind for a number of reasons, the main ones being outlined by Paul<br>above) but I respect the fact that others may have differing opinions.<br><br>Daniel<br>--<br>Daniel Morissette<br><a href="http://www.mapgears.com/">http://www.mapgears.com/</a><br>_______________________________________________<br>mapserver-dev mailing list<br>mapserver-dev@lists.osgeo.org<br><a href="http://lists.osgeo.org/mailman/listinfo/mapserver">http://lists.osgeo.org/mailman/listinfo/mapserver</a>-dev<br>
</p>
</div>
</body>
</html>