Thanks for the files. Silke Reimer wrote: > Hallo! > > Some time ago I told you that we made some small enhancements to > p.mapper and wanted to contribute them to the main source. > > Finally I found the time to download the actual p.mapper and try to > apply our patches to it (the patches where made from 1.9.1). Most of > our patches are not working any more and so little important or > so special that I don't think, it is worth to upgrade them to 1.9.5. > > The still remaining patches are coming with this email: > > * pmapper-1.9.5-scale.diff: > - adaption of minscale and maxscale: p.mapper shows everything in > ]maxscale,minscale[ while UMN MapServer works with > [maxscale,minscale]. P.mapper has been adapted to UMN MapServer. > The problem is visible in the legend where a layer can be grayed > even if it is still visible.
ok, now I understood what you meant. It's replacing '>=' with '>', etc.. I added it to the current code. > * pmapper-1.9.5-i18n.diff, de.po > - i18n support. The patch is not working completely mainly because > the p.mapper.mo is somewhat outdated. I had no time to adapt it > fully but thought it could be useful to send it to give an idea > how i18n can be included. de.po can be translated into a .mo > file by: > msgfmt --statistics -o p.mapper.mo de.po > p.mapper.mo should be located at > incphp/locale/de/LC_MESSAGES/p.mapper.mo to be found by p.mapper I don't know if anybody really uses the gettext functions... But I will add the files also to the dl directory. > * pmapper-1.9.5-vertical.diff: > - adding vertical tabular to show results of a layer. This is > useful if you many attributes in a tabular but only few results. > This patch as well is not working fully because the way, info > results are shown has changed a lot (especially by the > possibility to sort the attributes). Again I had not time to do > the full work but thought someone could be inspirated by this > code (otherwise throw it away ;-) > I will put it to the contributions dl directory for people interested to add it to current applications. I started to modify the query results in a way that the results are not any more written out as fixed HTML but as JSON like structure, loaded into the application via XMLHttp (Ajax). So the display can be done quite flexibly with Javascript, and also saved in a PHP session variable or JS object, and re-used if needed. I just need to define a good and stable representation of the various result parameters (including things like links, etc). > Please contact me with any questions, problems etc. > > Greetings, > > Silke best regards, armin
