[Mapserver-users] Perl/Python/Ruby mapscript development documentation

[Sean Gillies]

Lowell,

Mapscript.txt is the only file committed to CVS.  The HTML is generated
from it.  Sorta like the relationship of mapscript.i to 
mapscript_wrap.c.
And I'd like to get it produced nightly just like the C wrapper file.

What I'd like to find out from you and others is whether or not the
internal hyperlink targets muck up or reduce the readibility of 
mapscript.txt.
These are the bits of structured text that look like (for example)

.. _shapeObj.project:

Sean

On Feb 26, 2004, at 8:36 AM, Lowell Filak wrote:

> Yes & no - I checked mapscript.html.
> What am I missing - are they not intended to be one in the same? If not
> I'll just automate grabbing it.
> Logging into cvs is not something I look forward to doing manually 
> daily.
> Yes - allowing for the fact that it is not finished.
>
> Lowell
>
> The following message was sent by Sean Gillies <sgillies at frii.com> on
> Wed, 25 Feb 2004 10:54:44 -0700.
>
>> Is that a statement of complete approval?  Did you check the 
>> underlying
>> mapscript.txt file?  Does it look like something you'd use instead of
>> referring to the PHP readme?
>>
>> Sean
>>
>> On Feb 25, 2004, at 6:38 AM, Lowell Filak wrote:
>>
>>> Thank you to all the developers.
>>>
>>> Lowell
>>>
>>> The following message was sent by Sean Gillies <sgillies at frii.com> on
>>> Tue, 24 Feb 2004 10:19:40 -0700.
>>>
>>>> Hi,
>>>>
>>>> Following the example of the PHP-mapscript developers, we are now
>>>> maintaining
>>>> documentation for the development mapscript in a text file.  In CVS 
>>>> in
>>>> can be
>>>> found at mapscript/doc/mapscript.txt.  Language-specific appendices
>>>> will be
>>>> at mapscript/doc/python.txt etc.  This new documentation fills the
>>>> same
>>>> role as
>>>> the README file under mapscript/php3.  Is a work in progress, but 
>>>> I'm
>>>> chipping
>>>> away at it every day and we'll be caught up with the current state 
>>>> of
>>>> the
>>>> development code soon.
>>>>
>>>> We are trying out restructured text as a file format.  It provides
>>>> just
>>>> enough
>>>> structure that it can be parsed and rendered into XML or HTML.  
>>>> During
>>>> the
>>>> evaluation of mapscript.txt I will be regularly generating HTML from
>>>> the text source
>>>> and putting it up at
>>>>
>>>> http://users.frii.com/sgillies/examples/mapscript.html
>>>>
>>>> Links to the original text source and documentation about reST and
>>>> links to
>>>> download of reST tools are at the bottom of the page.  If users
>>>> appreciate this
>>>> development documentation, I'll work the generation of HTML docs 
>>>> into
>>>> the mapserver
>>>> nightly build.
>>>>
>>>> If you have considerations that you'd like to add to Bugzilla
>>>> regarding
>>>> the
>>>> development docs, join the discussion here
>>>>
>>>> http://mapserver.gis.umn.edu/bugs/show_bug.cgi?id=576
>>>>
>>>> or discuss here on the list and I'll try to summarize on Bugzilla.
>>>>
>>>> cheers,
>>>> Sean
>>>>
>>>>
>>>> --
>>>> Sean Gillies
>>>> sgillies at frii dot com
>>>> http://users.frii.com/sgillies
>>>>
>>>> _______________________________________________
>>>> Mapserver-users mailing list
>>>> Mapserver-users at lists.gis.umn.edu
>>>> http://lists.gis.umn.edu/mailman/listinfo/mapserver-users
>>>
>>> _______________________________________________
>>> Mapserver-users mailing list
>>> Mapserver-users at lists.gis.umn.edu
>>> http://lists.gis.umn.edu/mailman/listinfo/mapserver-users
>>>
>>
>> _______________________________________________
>> Mapserver-users mailing list
>> Mapserver-users at lists.gis.umn.edu
>> http://lists.gis.umn.edu/mailman/listinfo/mapserver-users
>