Thanks Armin for these notes. I reply inline:
>> well, there are frameworks like GeoExt that might already have offered > this type of functionality. Did you ever try them? As you know, GeoExt is more a client viewer, decouled by the server side. What I like in Pmapper is the integrated environment, where with few configurations you obtain a full-featured system (client+server). Having an admin API would allow the configuration to be made through a web based UI, or even a desktop app. This would simplify/streamline the process of setting up and deploying maps and services for the end-user. > > > Armin, do you have any plans about it? Will you put it out when things are >> done, or will you share the code while working on it? >> > > So far quite some parts are still a bit under construction with frequent > and possibly still deeper changes. It was not always easy to understand the > sometimes strange logic of OL, and the OL mailing list was of no help for > very specific questions (I practically never got any reply). So I was > sometimes close to abandon the idea of using OL. Now I found most ways for > workarounds, and the map navigation and interaction tools are mainly > working. > > I'm currently in the final stage of rewriting the old and badly structured > query code of p.mapper, this might be even possible to port it back to the > p.mapper 4 (the new one will be version 5). The query stuff is again a bit > of a mess, this time from the side of MapServer. But the new query classes > should allow more easily to write you own functionality for the query > result display if needed since this is now decoupled from actually getting > the query result. > > A missing part is also the printing where I will mainly have to > investigate how to print tiled layers that are not available via Mapserver > (like OSM layers, Google layers will anyway not be allowed to be included > in printings). > > Just to give an idea how the composition of layers from mapserver and OL > works: You can define as now to have all MS layers (or groups) being > rendered on a single map image, with or without tiling. Or you can split > groups of layers into a few blocks, each block is an OL layer (I call the > OL layers 'olThemes' to avoid too much of naming confusion). The > combination which layers are rendered together or separately can be done in > any type of combination. Using tiled layers for the time being will require > to use the Google spherical mercator projection for the map. I cerated 2 > new types of new OL layers, one tiled and the other non-tiled. Both are > based on MapScript and will only work inside a user PHP session. > > It will be very likely that the first release version of p.mapper 5 will > have some very specific functionalities not yet included, and most likely > also only a few plugins will work already then. > > When the code is a bit more stable I will put it on the SVN, depending > also if anyone is interested in contributing some developments. I might put > a preliminary beta version out in the next week or so, so that people can > have a look at it on their own installation. > > Great work. I'm not able to comment your points in this moment, I need to have a look to the code, but it sounds great! I hope to have a ride on it soon ;) > A first draft version (already 2 weeks old) is available at > http://www.pmapper.net/demo/**pmapper-5-dev/<http://www.pmapper.net/demo/pmapper-5-dev/> > http://www.pmapper.net/demo/**pmapper-5-dev/?config=**singletile<http://www.pmapper.net/demo/pmapper-5-dev/?config=singletile> OSM within Pmapper! That's what I was longing for ;) giovanni ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ pmapper-users mailing list pmapper-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pmapper-users
