<html>
<head>
<style type="text/css">
<!--
body { line-height: normal; font-variant: normal; margin-top: 4px; margin-bottom: 1px; margin-right: 4px; margin-left: 4px }
p { margin-top: 0; margin-bottom: 0 }
-->
</style>
</head>
<body style="margin-top: 4px; margin-bottom: 1px; margin-right: 4px; margin-left: 4px">
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">All,</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">OK, probably a weird idea, but. . . . while looking for the brochure mentioned here (only found the old one so far . . .came into the thread in the middle) . . .a thought occurred to me. Why not make this project brochure creation thing a step in the incubation process. Use some sort of basic template and each project has it's own brochure.</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">bobb</font> </p>
<br> <br><br>
<p style="margin-top: 0; margin-bottom: 0">
<br>
<br>
>>> Lars Lingner <ml@lingner.eu> wrote:<br> </p>
<div style="padding-left: 7px; margin-top: 0; background-color: #f3f3f3; margin-bottom: 0; margin-right: 0; border-left: solid 1px #050505; margin-left: 15px">
<p style="margin-top: 0; margin-bottom: 0">
Steve Lime schrieb:<br>> Hi Lars, thanks for working up an updated brochure, looking at the old one<br>> it could use it. Some comments...<br>><br>>   - I think I'd avoid the MapServer website screen shot in favor of another<br>> app. The website text features the security fix announcements which while<br>> a reality in a project aren't marketing friendly. I can offer a couple of sites<br>> as could others I bet. I like your example, nice and colorful.<br><br>If someone could point me to MapServer powered sites, I'll update the<br>screenshot in the flyer.<br><br>><br>>   - Perhaps the screen shots could be a bit taller, more of a square aspect<br>> ratio?<br><br>Ok, I'll take a further look.<br><br>><br>>   - Under features it might make sense to highlight output options: all sorts<br>> of raster images, PDF, SWF, SVG and templated text<br>><br>>   - Might include input and the new output plugin architectures as features<br>><br>>   - The "Leverages best-of-breed" sentence could be reworked to say we<br>> leverage other OSGeo projects including GDAL, GEOS, PostGIS and Proj.4. I<br>> think we should really emphasize the reliance on other OSGeo projects.<br>><br>>   - In the last feature sentence I think MapBuilder can be removed. There are<br>> some frameworks specific to (or that at least favor) MapServer (e.g. p.mapper<br>> and GeoMoose) that could get some love here...<br><br>Thanks for this info. I'm putting it in.<br><br>><br>> I think the 5.6 features are performance centric (raster rendering improvements,<br>> single pass, etc...). The 6.0 release *should* have a more output-based focus<br>> with full support for the rendering plugin, new object structures including<br>> references, better SLD support, styles within labels and so on. XML mapfiles<br>> will be in 5.6. It's important to note that XML mapfiles allow users to define<br>> a configuration in XML but you must transform it to a .map file for use. I hope<br>> that might really have an impact on wysiwyg editors eventually.<br>><br><br>Sounds like an interesting roadmap, I'll spread the word... ;)<br><br><br>Lars<br>_______________________________________________<br>mapserver-users mailing list<br>mapserver-users@lists.osgeo.org<br><a href="http://lists.osgeo.org/mailman/listinfo/mapserver">http://lists.osgeo.org/mailman/listinfo/mapserver</a>-users<br>
</p>
</div>
</body>
</html>