[OpenLayers-Users] Delaying Layer Initialization

[Stephen Woodbridge]

Christopher,

How about adding something to the build script like:

svn info | grep "Revision:"
Revision: 3188

to grab the trunk Revision and adding that string somehow to the 
packaged OpenLayers.js then you would have an unambiguous svn Revision.

OK, this won't if you don't have svn installed but it could be 
conditional on having it.

Or if the .svn directory is available then that info is in the 
.svn/entries xml file and this might be a better place to fetch it from 
programmatically. I'm not sure if Windows and Macs also have this structure.

Anyway, I'm just think out loud here in case it might help. Sorry, I 
don't have a patch to offer.

OL 2.4RC5 is looking might fine. Many thanks to you and all the 
contributors for many hours of hard work to make this fine product release.

-Steve W

Christopher Schmidt wrote:
> On Sat, May 26, 2007 at 10:28:39AM +0200, Arnd Wippermann wrote:
>> Hello Christopher,
>>
>> I have the same problem (therefor I'm still using Openlayers 1.0).
> 
> Okay, thanks. I'd heard reports, but they were always vague in the
> problems they were reporting.  
>> OpenLayers should only load tiles for the baselayer from gis.ibbeck.de and
>> wms.jpl.nasa.gov for the world image. If you use firebug, you could see,
>> that the tiles for the other servers are also loaded.
> 
> Agreed. I'll file this as a bug against 2.5. Since it's been around since
> the start of the 2.0 branch, it's not enough to delay 2.4. 
> 
>> After the first load of the map, pan and zoom loads only the tiles for the
>> visible servers.
>>
>> http://gis.ibbeck.de/ginfo/ibbOLClient/OLC2.3%20RC1.html?MAPNR=10000&LAYERS=
>> 11200,12700,11500,11500,10600,10700,10900,11000,10000&ZOOM=3&CENTER=10.1745,
>> 50.819 
>>
>> (If I load the newest version from
>> http://svn.openlayers.org/branches/openlayers/2.4/, Revision 3188 says the
>> html-page and my svn-program, the OpenLayers.VERSION_NUMBER is still
>> "$Revision: 2942 $". Miss I something or is this a bug).
> 
> This is expected -- the VERSION_NUMBER is relevant to the last time that
> file was updated. Part of the release process is to edit the
> OpenLayers.js file (to change the license), so releases get a new
> VERSION_NUMBER -- it's only useful on releases. Unfortunately, I don't
> know of a better way to automate this. 
> 
>> Is it possible with the number of the revision also deliver a variable with
>> the plain text for the OpenLayers Version(example: 2.4 RC4).
> 
> There is no automatic way of doing this, and it's a step that I fear
> would be missed if we made it a human intervention step, which is why
> it's not done. If you're actually using RC4 -- that is, from the /tags/
> instead of the branch -- the VERSION_NUMBER represents that.
> 
> Regards,