On Wed, Apr 8, 2009 at 2:17 PM, Jens Frank <
jens.l.frank@googlemail.com> wrote:
>> As for where to have the OpenLayers code, I would like to have our own
>> copy which we can keep up-to-date as possible. It would not be good to
>> reference the OpenLayers.js directly from OpenLayers or OSM, since those
>> will get changed as others see fit. It could be that some change will break
>> our extension. When we do update our copy of OpenLayers.js, we can test it
>> with our extension and make sure everything is okay.
>
> The SlippyMap extension requires a small change to the original OpenLayers
> code. At the very end of the file, it sets a variable to "true", so that the
> JavaScript can be loaded asynchronously. The part of the JavaScript that
> creates the map polls for these variables. If they are not yet set, the
> function calls itself using alarm() and a ~0.5s delay. Without this hack,
> the loading of the page would stall at the map in many browsers when using
> slow links or slow CPUs