Dennis, I'm always interested in having new functionality included in p.mapper if it is possible to keep them reasonably generic and not too tight to a special dataset or application environment.
Search possibilities: Because pmapper 1 and 2 are now using the same approach and a simplified (at least I hope so) definition, it would be possible to add an alternative search functionality as separate . Do you think this can be kept generic and not very much designed for particular datasets? All what the functions would have to do is to create the correct search strings at the end - what is not always so straightforward for shapefiles and the strange regex filter definition. That's the reason why I still keep the PostGIS attribute search separately, it's much easier to work on that. It seams that especially for intranet solutions pmapper users might want to have more flexibility for searches. I'm always a bit reluctant because I like to have search functions as simple as possible => type in a click ok. But if someone wants to contribute an alternative way it can be integrated, as best if kept as replacement functions/scripts one would use instead of the original/basic ones. Redlining: I don't understand exactly where you would like to store the information once a user ends his current session. I think you mean that every user will just see his own added information, not that everybody can add something to a common datapool.(?) Printing options: More printing options could be introduced in an alternative print dialog. And of course they had to be included as optional parameters in the standard printing functions. Like default settings (eg. A4, with legend, etc.) if no other definitions are made and if the application designer wants just to use the existing simple printing parameters. I would really like especially some improvements of the PDF creation where an A3/A2 would mean maybe something like 3 columns instead of 2 and so on. All the PDF creation with the possible combinations of groups and layers is a bit painful to do correctly. It took me some nerves until it worked correctly and I never touched it again. If you plan to re-work a bit on the PDF stuff I would be really glad. Something like defining different font sizes, etc. Currently all line/space separators are hard-coded and in absolute values. I was already making some tests creating LaTeX files and using PDFLaTeX to convert everything to PDF because it handles these things much easier than when you have to define every line break and offset in PDF units and so forth by hand. The areas you mentioned are not the ones that I planned to work on in the next time so there should not be a problem when working both on not always synchronized versions. I'm still reluctant to use CVS but I could set the WebDAV directory writeable with password protection so we could keep the sources more or less synchronized. When you talk about modules, how do you mean that concretely? How should they be integrated? I tried to separate some logical units in sections like query, print, etc. Armin DJ Broerse wrote: > Dear Armin, > > A customer of us, Waterschap Zeeuws Vlaanderen http://www.wszv.nl, > <http://www.wszv.nl/> has successfully introduced web-mapping on their > intranet by means of Mapserver/Pmapper, earlier this year. In a few > years all local authorities in the Netherlands are legally forced to > publish their environmental plans on the web. Most of them will use > commercial products, but in our opinion they don't fit very well. > Therefore we are very glad with the benefits of your Pmapper. We > especially like the easy way it can be modified and maintained, while > commercial products are "/closed"/ and can't handle the subject of > environmental plans very well. So we like to promote your product to > other local authorities. > > We, Ibuildings.nl http://www.ibuildings.nl <http://www.ibuildings.nl/>, > are willing to customize Pmapper for Waterschap Zeeuws Vlaanderen. We > are very glad if we can contribute the modifications to you. So we can > always update the installation and the community gets new functionalities. > > We also like to know how you feel about to make Pmapper extendible with > modules and what does it take to make that possible. > > Can you tell us which modifications you like to have, I will give you a > short list with the modifications. > > Modifications > > * > > Search possibilities > We like to make it possible that the user can dynamically create > their own search questions. It is also possible to search between > 2 or more layers in one search request. > > * > > Redlining > Redlining is very cool. With redlining you can click on the map > and there will appear a form where the user can put their > information about that object. The input and output will be XML/GML. > > * > > Print options > We like to extend the print options so you can choose if you like > to have the legend printed or not, extended legend or the simple > legend printed on map, printsize A4,A3,A2 etc. > > We can give you more information if you like to. > > Could you please make clear to us how you feel about this. Maybe you can > advise us what is best. If you agree on our plans it would be necessary > that you take these issues with you in the product-source. Please tell > us how we can cooperate with you. > > Maybe other Pmapper users like some functionallity too, they can also > reply and maybe participate. > > Thanks in advance for your reply, > > Kind regards, > > Dennis-Jan > > -- > DJ Broerse [EMAIL PROTECTED] > Mobiel: 06 48 01 03 08 > Skype: callto://dennisjan-ibuildings > Ibuildings.nl BV - Information technology > http://www.ibuildings.nl - 0118 42 95 50 > > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Pmapper-users mailing list > [EMAIL PROTECTED] > http://faunalia.it/cgi-bin/mailman/listinfo/pmapper-users
