try at least the latest development version. It should be sufficient to replace the older 'pmapper.js' with the one from the /dl/pmapper2_2006-03-07.zip. For me it resolved most of the image reload problems, even if I got the feeling that in rare cases the problem still appeared.
armin Walter Lorenzetti wrote: > Alle 10:55, gioved? 16 marzo 2006, Armin Burger ha scritto: > Hi Armin, > > so we here in faunalia have some problems in update map with pmapper2: > i didn't find a rule for this problem, seems indipentent from layers charged > or session time, some times it show to our at start of pmapper or lot of time > after... > When the problem go pmapper don't show the request of user but show old map > pre-requested, i hope you undertand the problem!! > > If you want to look at it, you can try our pmapper2 here: > > http://www.faunalia.it/pmapper/pMapper2_inuso/ > > Please Armin, try it and tell me what do you think about it. > > Bie > Walter > > >> *p.mapper 1* is more tested and will not change any more directory >> structures, etc. Mainly some modifications of query and attribute search >> parts are foreseen so far to allow more flexible search (especially with >> PostGIS layers) and result display. >> >> *p.mapper 2* is regarded as beta. And I'm planning to investigate once also >> some time in a more flexible file/dir structure with basic libraries, >> config and customized parts better separated. >> >> Also there might be still some issues with the Ajax requests. I haven't got >> any more the problems with the failing map image update, but I am not sure >> if that is solved completely. So far I seem to be the only one experiencing >> this because there were no postings mentioning that. >> >> pm 2 has advantages in being more flexible how to include it in other >> applications (no frames) and use additional DHTML functionality. But the >> resizing/(re-)positioning part is not really straightforward currently. I >> don't know when I will investigate some time again in this. And since >> nobody else seems to want to work on this it might still remain a temporary >> solution. >> >> With regard to 'prototype.js' I will check if the current code of pm 2 is >> compatible with it, since as I understand prototype.js is not compatible >> with some type of array handling. pm 1 should not very much affected by >> prototype because it's using only fairly amounts of DHTML/DOM and the >> javascript code is not very 'modern'. >> >> armin >> >>> --- Urspr?ngliche Nachricht --- >>> Von: Alessandro Pasotti <ale.pas at tiscali.it> >>> An: pmapper-users at faunalia.it >>> Betreff: [Pmapper-users] which branch for a new project >>> Datum: Thu, 16 Mar 2006 08:02:38 +0100 >>> >>> Hello, >>> >>> After our first public deployment of pmapper (on www.aptversilia.it, very >>> slow >>> server indeed) we are starting a new project for an intranet application >>> which will need a high degree of functional customisation (probably with >>> sort >>> of AJAX stuff), what branch would you suggest to use as code base? >>> >>> In particular, I cant' remember where I've heard about using protoype js >>> libs, >>> this would be a good starting point if they were alreay used in some >>> pmapper >>> branch. >>> >>> We have been working with 1.0.7 so far. >>> >>> >>> Any hint would be highly appreciated. >>> >>> Regards. >>> -- >>> Alessandro Pasotti >>> ICQ# 245871392 >>> Linux User #167502 >
