<div class="gmail_quote">Hi Paul,<br><br>Sorry for the late response, I wish I had posted this before, but I was working in a rush.<br><br>I just want to add that I think this I great and important step in ka-Map development. As you pointed out, some of its features are very appealing for many developers, specially for those more confortable with PHP than Python.<br>
<br>I'm working in a project with ka-Map + OL, and we'll be working on it until december this year, so yes, I think ka-Map still a good choice for many people, and therefore making it easier to configure, customize, and/or integrate with other tools is something very bennefical to the ka-Map community. JSON support is also another cool feature. <br>
<br>I hear this news with a lot of enthusiasm, since I thought the ka-Map project was inactive, which is a shame. So, I'm very happy to see there will be more new stuff coming from ka-Map community!<br><br>I have a limited spare time, but I will try to stay tuned with you developers, and share insteresting things I found along the development of the project I'm working for.<br>
<br>My best wishes,<br><br>Pedro Simonetti.<br><br><div class="gmail_quote">2008/5/7 Paul Spencer <<a href="mailto:pspencer@dmsolutions.ca" target="_blank">pspencer@dmsolutions.ca</a>>:<div><div></div><div class="Wj3C7c">
<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br>
<br>
just wondering what, if anything, people are planning to do with ka-Map these days. I have a feeling that most developer efforts are, in fact, going into OpenLayers. However, ka-Map has a few features that are appealing to some folks and are not served by OpenLayers:<br>
<br>
1) server-side configuration without changing the client side<br>
2) written in php<br>
3) tile creation/management<br>
<br>
I think it may be useful to pull out portions of ka-Map's server side stuff, clean it up and add some new features, and provide more direct support for OpenLayers. I'm not entirely sure what this would look like but it may be something like:<br>
<br>
* a php-based configuration file similar to the existing config.php for specifying various options and identifying maps and tile caches<br>
* a php-based tile engine similar to the existing tile.php for dynamically serving tiles from a cache and rendering them as necessary<br>
* a php-based tool that returns javascript or json to the client with an appropriately configured layer(s) (all the settings for the layer are taken from the configuration of the cache and other settings)<br>
* a client-side way of using the javascript or json from the server-side - could be as simple as including a script tag after OpenLayers.js or an entirely new Control or add-in for OpenLayers.<br>
<br>
This would focus efforts on improving tile.php rendering, tile management tools such as precache.php, and cleaning up that code while leaving the javascript stuff to OpenLayers.<br>
<br>
Comments?<br>
<br>
__________________________________________<br>
<br>
Paul Spencer<br>
Chief Technology Officer<br>
DM Solutions Group Inc<br>
<a href="http://www.dmsolutions.ca/" target="_blank">http://www.dmsolutions.ca/</a><br>
<br>
_______________________________________________<br>
ka-Map-dev mailing list<br>
<a href="mailto:ka-Map-dev@lists.maptools.org" target="_blank">ka-Map-dev@lists.maptools.org</a><br>
<a href="http://lists.maptools.org/mailman/listinfo/ka-map-dev" target="_blank">http://lists.maptools.org/mailman/listinfo/ka-map-dev</a><br>
</blockquote></div></div></div><br>
</div><br>