Hi Stephen,<br><br>Good to see that I'm not alone with that!<br><br>Christopher & Stephen,<br><br>I would like to add one thing. I'm convinced that Python is the "server side language of the future", but a lot of people still uses PHP, or feel more confortable writing/reading PHP code. Of course, I've chosen using OL+ka-Map because I was using ka-Map before, but I've decided that also because I'm not familiar with Python code as with PHP code. So I think that keeping the php code in examples would be good also to php-like developers.<br>
<br>But as Stephen stated, whatever you choose will work.<br><br>my best regards,<br><br>Pedro Simonetti.<br><br><div class="gmail_quote">2008/4/28 Stephen Woodbridge <<a href="mailto:woodbri@swoodbridge.com">woodbri@swoodbridge.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;">Chris,<br>
<br>
I sympathize with your sentiment that tile.php and precache.php not being part of OpenLayers, but I think it is very useful to have them with the examples, for a couple of reasons.<br>
<br>
1) it keeps a version that we know works because it has been tested, with the code<br>
2) it makes it easy for people to find these as they may not have come from the ka-map project but might still want to use the,<br>
<br>
May we should have a contrib directory that these could go into.<br>
<br>
Just a thought, whatever you decide will work.<br>
<br>
-Steve W<div><div></div><div class="Wj3C7c"><br>
<br>
Christopher Schmidt wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
On Sun, Apr 27, 2008 at 10:48:39AM -0300, Pedro Simonetti Garcia wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi Christopher,<br>
<br>
I'm new to OL community, so I don't know all the internal<br>
proceedings / rules to report bugs, write tickets, and so on.<br>
So, forgive me if I skip some steps.<br>
<br>
I wrote the tickets #327 e #1519 of this list.<br>
<br>
<a href="http://trac.openlayers.org/ticket/327" target="_blank">http://trac.openlayers.org/ticket/327</a><br>
</blockquote>
<br>
Right, I need to respond to this one, as the de facto maintainer of the<br>
ka-Map integration with OpenLayers. What it comes down to, breifly, is<br>
that I believe the fixes you have described should be happening<br>
upstream, with the ka-Map project, and that instead of having tile.php<br>
in the OpenLayers examples, we should simply remove it totally.<br>
Similarly, 1518 below: the precache.php.txt file does not belong in<br>
OpenLayers, but I don't see anything particularly wrong with the<br>
KaMapCache layer, if you're interested in it.<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<a href="http://trac.openlayers.org/ticket/1519" target="_blank">http://trac.openlayers.org/ticket/1519</a><br>
</blockquote>
<br>
This is simple, and I just haven't learned enough about translations to<br>
test them yet, so I haven't done anything with it. It looksfine in<br>
general.<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I also wrote a comment on issue #1108, which is related to<br>
the #864 that is flagged to 2.7 milestone.<br>
<br>
<a href="http://trac.openlayers.org/ticket/1108" target="_blank">http://trac.openlayers.org/ticket/1108</a><br>
<a href="http://trac.openlayers.org/ticket/864" target="_blank">http://trac.openlayers.org/ticket/864</a><br>
<br>
I'm also the author of the #1518, which is related to the #1519:<br>
<br>
And I wish to help with this issues, but I'm not sure<br>
exactly how to proceed. I reported those tickets using a<br>
anonymous username/pass. Should I create a account<br>
and post a comment in those tickets to make easier future<br>
discussions about them?<br>
</blockquote>
<br>
That would be good, yeah.<br>
<br>
Your patches, in general, look fine, and I'm glad to know you're still<br>
aware of them and looking to push them forward. So long as that's the<br>
case, there's no problem leaving them in the current milestone. I'm<br>
mosty looking to push a lot of things that people have opened and<br>
forgotten about forward, if there is no active work on them.<br>
<br>
Any further comments on your tickets, I'll do through trac/seperate<br>
maisl to the list: thanks for the summary, and the hard work!<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
If you are interested in my help, please let me know.<br>
<br>
my best regards,<br>
<br>
Pedro Simonetti.<br>
<br>
2008/4/27 Christopher Schmidt <<a href="mailto:crschmidt@metacarta.com" target="_blank">crschmidt@metacarta.com</a>>:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
The 2.7 ticket list is a mess. I'd like to put some effort into cleaning<br>
it up, but to be honest, it's a bit of a big job for me alone.<br>
<br>
<br>
<a href="http://trac.openlayers.org/query?status=new&status=assigned&status=reopened&group=type&milestone=2.7+Release" target="_blank">http://trac.openlayers.org/query?status=new&status=assigned&status=reopened&group=type&milestone=2.7+Release</a><br>
<br>
We have 105 tickets in this release.<br>
<br>
Although some metadata is wrong:<br>
* 38 are bugs<br>
* 57 are features<br>
* 10 are tasks<br>
<br>
Some of these have active work being done on them. Some of them just<br>
need a thorough review. Some of them are probably not being actively<br>
worked on, or are just an idea.<br>
<br>
I think that if there is a ticket here that you consider yourself<br>
'owner' of -- for example, if you reported it -- and you are no longer<br>
actively working on this ticket, that you move it to a different<br>
milestone than the 2.7 milestone. There is one for 2.8 -- if you're not<br>
currently working on it, but you still intend to at some near-future<br>
point, that might be a good place to put it. If you don't intend to get<br>
back to it, but you're still interested in the functionality, please<br>
feel free to toss it to the "Future" milestone. Note that this is all<br>
just my opinion, since we don't have any strong rules on this... would<br>
love to hear others opinions.<br>
<br>
I don't think we have any specific plans for 2.7 at this point, but I'd<br>
personally like to keep our releases a bit more release-early<br>
release-often than 2.6 ended up being, and the current 100+ tickets that<br>
are open is just a bit overwhelming for me...<br>
<br>
Looking forward to hearing/seeing more discussion.<br>
<br>
Regards,<br>
--<br>
Christopher Schmidt<br>
MetaCarta<br>
_______________________________________________<br>
Dev mailing list<br>
<a href="mailto:Dev@openlayers.org" target="_blank">Dev@openlayers.org</a><br>
<a href="http://openlayers.org/mailman/listinfo/dev" target="_blank">http://openlayers.org/mailman/listinfo/dev</a><br>
<br>
</blockquote></blockquote>
<br>
</blockquote>
<br>
</div></div></blockquote></div><br>