Christopher,<br>
<br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">
This is not a reason to fork a project!<br></blockquote><br>
Okay, you've convinced myself :)<br><br>Since OL is a front-end application, isn't appropriate to<br>maintaing server code in it.<br>
<br>
I'll create an account in OL's track to get involved with the <br>
KaMapCache layer.<br>
<br>
Meanwhile, I'll communicate with the ka-Map list, and start<br>
writing a basic how-to ka-Map+OL. If there's anyone else<br>
interested in help, it will me much appreciated.<br><br>
regards,<br>
<br>
Pedro Simonetti.<br><br><div class="gmail_quote">2008/4/28 Christopher Schmidt <<a href="mailto:crschmidt@metacarta.com">crschmidt@metacarta.com</a>>:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Sun, Apr 27, 2008 at 10:42:16PM -0500, Stephen Woodbridge wrote:<br>
> Chris,<br>
><br>
> I sympathize with your sentiment that tile.php and precache.php not<br>
> being part of OpenLayers, but I think it is very useful to have them<br>
> with the examples, for a couple of reasons.<br>
><br>
> 1) it keeps a version that we know works because it has been tested,<br>
> with the code<br>
> 2) it makes it easy for people to find these as they may not have come<br>
> from the ka-map project but might still want to use the,<br>
<br>
</div>So, let's look at other code that this might apply to:<br>
<br>
* TileCache<br>
* MapServer<br>
* GeoServer<br>
* Worldwind tile server<br>
* GDAL2tiles<br>
<br>
All of these have changing versions, some of which will work interact<br>
differently with the outside world between different versions, all of<br>
which might not be the first place that people will look.<br>
<br>
However, I don't think it's a sane expectation that OpenLayers is going<br>
to host the code for any of these.<br>
<br>
In fact, the primary reason, in my opinion, that this is special for<br>
ka-Map is two-fold:<br>
<br>
* The ka-Map project has experienced a long-term dearth of development,<br>
in part due to the success of OpenLayers as a web-mapping frontend.<br>
This means that for the past year or more, there has been limited<br>
support for ka-Map from the people who know it best, and that affects<br>
many things, like documentation, releases, etc. This happens in Open<br>
Source, and I'll admit that OpenLayers is at least partially<br>
responsible, as developer attention has been focused elsewhere.<br>
* ka-Map was never designed for external use as a separable client and<br>
server side components. As such, the documentation for the<br>
server-side components on their own was never particularly seperable,<br>
and the end result was that the server side was only described as<br>
part of the whole process.<br>
<br>
These two things combine to make ka-Map a less than palatable solution<br>
for users concentrating on OpenLayers, because the server-side<br>
components of ka-Map are not easy to set up using the documentation<br>
available from the ka-Map project at this time. However...<br>
<br>
This is not a reason to fork a project!<br>
<br>
Make no mistake: maintaining seperate copies of the ka-Map source code<br>
in OpenLayers is a fork. We should not fork any project for convenience:<br>
all the difficulties that exist in using ka-Map in OpenLayers are easily<br>
solvable. Most are solvable without code: documentation is the only<br>
thing that most of these problems need, and documentation can be easily<br>
written in the OpenLayers wiki, the ka-Map wiki, etc.<br>
<br>
Helping the ka-Map project out by working to document a seperable<br>
server-side component, one designed for use in other applications like<br>
OpenLayers, would be useful to many people, and probably not just<br>
OpenLayers. That's the appropriate place to solve the problem of ka-Map<br>
source code not being effectively documented or clearly available:<br>
forking the project is a mistake, and my first step towards doing so<br>
with the tile.php in examples/ was a faux paus that I should have<br>
corrected long ago. If there are people who are interested in solving<br>
problems within the ka-Map code, we should not continue to solve them in<br>
OpenLayers, where only OpenLayers users benefit.<br>
<br>
Get involved. Help bring life to the ka-Map server side project, kick<br>
out a release, get SVN access, and help out the people who spent so much<br>
time writing the code in the first place.<br>
<br>
Regards,<br>
<font color="#888888">--<br>
Christopher Schmidt<br>
MetaCarta<br>
</font></blockquote></div><br>