[mapserver-dev] Any reaction to the 5.4 release plan?

[Steve Lime]

I'm ok with either, whichever is easiest. This would be an appropriate addition to 5.4 so feel free to
commit. It's a pretty isolated addition so the impact elsewhere in the code base in minimal so I don't
think there's a need for an RFC...

Steve

>>> On 2/4/2009 at 10:58 AM, in message
<f3b73b7d0902040858j6b8d6fe6q8bcbf326d1f30088 at mail.gmail.com>, Tamas Szekeres
<szekerest at gmail.com> wrote:
> Yes, the first one would be easier to implement by eliminating to realloc
> the items array at each subsequent items.
> I originally didn't want to add that TEXT hack since the mapscript users are
> already able to set the items of the features programmatically.
> 
> Tamas
> 
> 
> 
> 2009/2/4 Daniel Morissette <dmorissette at mapgears.com>
> 
>> Tamas Szekeres wrote:
>>
>>> Steve,
>>>
>>>
>>> I would support to have 
> http://trac.osgeo.org/mapserver/ticket/2870implemented (or something like 
> this) in this release.
>>> It's a small change though, it would establish an option is to have a
>>> certain set of the items retrieved and bypass msLayerWhichItems in some
>>> cases. This would also be essential if we think about caching the features
>>> for later use in the future additions.
>>>
>>>
>> In this ticket, instead of hijacking the TEXT member of the inline features
>> for the attributes, would it not be better to add a new/explicit ITEMS
>> parameter for that?
>>
>> Either
>>
>>    FEATURE
>>        POINTS -0.2 51.5 END
>>        ITEMS "value1;value2;value2"
>>    END
>>
>> or
>>
>>    FEATURE
>>        POINTS -0.2 51.5 END
>>        ITEMS
>>          "value1"
>>          "value2"
>>          "value3"
>>        END
>>    END
>>
>>
>> --
>> Daniel Morissette
>> http://www.mapgears.com/ 
>> _______________________________________________
>> mapserver-dev mailing list
>> mapserver-dev at lists.osgeo.org 
>> http://lists.osgeo.org/mailman/listinfo/mapserver-dev 
>>