People using the Next_Generation_API?

[Cord Thomas]

Sean,

Thank you.

Would you then recommend i pull the beta mapserver, rather than latest
stabl e (4.2.x)?  Most of the docs are for 4.2.x (and some these are
outdated) - i am really quite impressed with progress that has been made
on mapserver (used it 3-4 years ago to make simple maps) - but a little
unclear on the development road map.

As mapserver continues to grow, it would be great to see the unm home page
present some of this information.  Having worked on a number of OS
projects, I know this is a hastle, but sure would be nice.

Cord

> On Nov 28, 2004, at 10:18 AM, Cord Thomas wrote:
>
>> Hello,
>>
>> I see mixed results when querying google about issues like getShapes()
>> where it appears some people are using the next generation API?  I am
>> unclear - is this meant to be used now, or as place holder for future
>> interfaces?
>>
>> I am working on a Perl mapserver application and would like to use the
>> getShape(shapeindex) function, but it does not appear to be available
>> in
>> perl/mapscript_wrap.c - would this be available if i compiled mapserver
>> with the NEXT_GENERATION_API directive?  and how do i do that?
>>
>> Thank you
>>
>> Cord
>>
>>
>
> Cord,
>
> The next generation API experiment is over.  The useful parts are
> now incorporated into the 4.4 mapscript API.  layerObj::getFeature
> is the method that returns instances of shapeObj.  See the API
> reference at mapserver/mapscript/doc/mapscript.txt for details.
>
> Sean
>
> --
> Sean Gillies
> sgillies at frii dot com
> http://users.frii.com/sgillies
>
>