[mapserver-dev] Versioned MapServer Docs?

[Brent Fraser]

Good idea, but too much coding for me since it's a lot of work to cover all (most?) of the possibilities.    Seth's mappyfile json files are interesting though; might make it easier.

----------------------------------------

From: "Basques, Bob (CI-StPaul)" <bob.basques at ci.stpaul.mn.us>
Sent: 3/19/21 11:27 AM
To: "bfraser at geoanalytic.com" <bfraser at geoanalytic.com>, "mapserver-dev at lists.osgeo.org" <mapserver-dev at lists.osgeo.org>, "Jeff McKenna" <jmckenna at gatewaygeomatics.com>
Subject: Re: [mapserver-dev] Versioned MapServer Docs?

Another thought to consider,  With the HTML option I got to thinking about setting it up as a visual form, where certain elements could be changed in the HTML by the user as FORM elements, and used to create a new Map output tile when submitted.  A way of showing how different parameters/ settings change the output, etc.  sort of a dynamic doc linking thing.

Thanks on the DATA statement, goes to that thought on being able to pass things onto the next curator of the system, probably overkill, but easily readable, etc . . .  I have a real good one for formatting of TEXT inside of the SQL that I should have used.

Bobb

From: Brent Fraser <bfraser at geoanalytic.com>
Reply-To: Brent Fraser <bfraser at geoanalytic.com>
Date: Friday, March 19, 2021 at 12:09 PM
To: Bob Basques <bob.basques at ci.stpaul.mn.us>, "mapserver-dev at lists.osgeo.org" <mapserver-dev at lists.osgeo.org>, Jeff McKenna <jmckenna at gatewaygeomatics.com>
Subject: Re: [mapserver-dev] Versioned MapServer Docs?

Think Before You Click: This email originated outside our organization.	

I too use a editor with [imperfect] syntax highlighting (Notepad++).  But i wanted to go beyond that (your Vim -> html is a nice option).  

My goals for the "mapfile cheatsheet" are:

1.  Make it easy to create a workable mapfile 

 - can simply cut-and paste

 - content should be almost complete

 - have comments showing options, acceptable values, etc for tweaking

2.  Make it available for others to use (e.g. a web page)

3.  Provide links on the keywords pointing to the official doc for details (.rst? .md?) 

 - show syntax highlighting for ease of reading

4.  Make it easy to maintain/update as the mapfile syntax changes

Loved your DATA statement by the way!

Brent

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20210319/8dc68e8b/attachment.html>