Hi,
Pmapper 5 will be great for many reasons. But I think MapServer 6
compatibility is not the one that should be decisive.
AFAIC pmapper 4 branch is compatible with MapServer 6 (but I'm using dev
version).
If there are few users feedbacks in this way concerning dev version, I
think it could
2012/10/25 Thomas RAFFIN traf...@sirap.fr
Hi,
Pmapper 5 will be great for many reasons. But I think MapServer 6
compatibility is not the one that should be decisive.
AFAIC pmapper 4 branch is compatible with MapServer 6 (but I'm using dev
version).
AFAIC pmapper4 has serious trouble with
Le 25/10/2012 10:59, Raffaele Morelli a écrit :
AFAIC pmapper4 has serious trouble with latest php-mapscript (at least the
one in debian testing/wheezy)
In Mapserver 6.x some mapfile statements are changed and 5.x ones will
broke 6.x, can't say if pmapper is affected too.
No, I think you
On 25/10/2012 10:59, Raffaele Morelli wrote:
AFAIC pmapper4 has serious trouble with latest php-mapscript (at least the
one in debian testing/wheezy)
In Mapserver 6.x some mapfile statements are changed and 5.x ones will
broke 6.x, can't say if pmapper is affected too.
regards
-r
In
On 25/10/2012 19:03, Armin Burger wrote:
And I will soon set up a maintenance release of pmapper 4
forgot to add: Thanks to Thomas who provides all those patches in SVN!
armin
--
Everyone hates slow websites. So do
this a left-over from pmapper 4 that has still not been removed, you can
silently ignore it. Or just remove in lib/init/initmap.php - function
_initConfig() the 3 lines starting with
if ($this-map-resolution != 96) {
On 24/10/2012 09:57, Raffaele Morelli wrote:
hi,
I am working on a
2012/10/24 Armin Burger armin.bur...@gmail.com
this a left-over from pmapper 4 that has still not been removed, you can
silently ignore it. Or just remove in lib/init/initmap.php - function
_initConfig() the 3 lines starting with
if ($this-map-resolution != 96) {
Thank you, silently
