[mapserver-dev] MS-RFC-55: Improving control of output resolution

[thomas bonfort]

It will be up to the rendering code to decide what is scaled or not.
The RFC should probably go into more detail for exactly which
parameters will be affected by the scaling. Other candidates that come
to mind are:
* offsets (line, point, polygon)
* pattern (line)
* outlinewidth (labels)
* shadowsize, background-shadow-size (labels)
* buffer around labels (colision) ?
* minfeaturesize, mindistance (labels)

thomas

On Mon, Mar 9, 2009 at 17:58, Paul Spencer <pspencer at dmsolutions.ca> wrote:
> Daniel,
>
> will this be applied to the gap in symbols?
>
> Paul
>
> On 9-Mar-09, at 3:48 PM, Daniel Morissette wrote:
>
>> Following a discussion at the code sprint this morning, I have prepared MS
>> RFC 55 that documents the solution that we came up with for improving
>> control of output resolution when printing. We realize that there were
>> interesting ideas proposed on the -dev list in the thread on this topic a
>> couple of weeks ago (like the use of point units for instance), but we chose
>> this approach because it is the most straightforward for users and requires
>> very little change to the source and to existing apps/mapfiles.
>>
>> The RFC is going to be online within the next hour at:
>> http://www.mapserver.org/development/rfc/ms-rfc-55.html
>>
>> Daniel
>> --
>> Daniel Morissette
>> http://www.mapgears.com/
>> _______________________________________________
>> mapserver-dev mailing list
>> mapserver-dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/mapserver-dev
>
>
> __________________________________________
>
>   Paul Spencer
>   Chief Technology Officer
>   DM Solutions Group Inc
>   http://research.dmsolutions.ca/
>
> _______________________________________________
> mapserver-dev mailing list
> mapserver-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-dev
>