[OpenLayers-Users] openlayers single file librarry problem

[Joanne Cook]

Hi Chris,

If only I didn't make school-girl errors and occasionally over-write critical files :-)

I like the idea of having separate ones for each map page too, so I can reduce the amount of included libraries to what is required in each case.

Cheers

Jo
----- Original Message -----
From: "Christopher Schmidt" <crschmidt at metacarta.com>
To: "Joanne Cook" <j.cook at oxfordarch.co.uk>
Cc: "users" <users at openlayers.org>
Sent: Wednesday, 13 May, 2009 13:51:05 GMT +00:00 GMT Britain, Ireland, Portugal
Subject: Re: [OpenLayers-Users] openlayers single file librarry problem

On Wed, May 13, 2009 at 12:37:43PM +0000, Joanne Cook wrote:
> Hi Chris,
> 
> Thanks for that- adding the stylesheet link and the OpenLayers.ImgPath worked a treat (rather than risking over-writing the original OpenLayers.js file).

The intention is that a single file build should never live in the same
place as the OpenLayers.js non-single file build that is inclued in
trunk. Generally:

  /openlayers/
  /openlayers/lib/OpenLayers.js <- non-singlefile
  /openlayers/OpenLayers.js <- single file

The file -- if any -- in /build/ is irrelevant, and the file that
'ships' in /openlayers/OpenLayers.js can be rebuilt with a full build at
any time. 

-- Chris

> Jo
> ----- Original Message -----
> From: "Christopher Schmidt" <crschmidt at metacarta.com>
> To: "Joanne Cook" <j.cook at oxfordarch.co.uk>
> Cc: "users" <users at openlayers.org>
> Sent: Wednesday, 13 May, 2009 12:28:28 GMT +00:00 GMT Britain, Ireland, Portugal
> Subject: Re: [OpenLayers-Users] openlayers single file librarry problem
> 
> On Wed, May 13, 2009 at 11:11:32AM +0000, Joanne Cook wrote:
> > Hi All,
> > 
> > I'm not totally sure if this is an openlayers issue or related to mapfish, but I am having problems building a single file version of the openlayers libraries.
> > 
> > I start in /var/www/mapfish/client/mfbase/openlayers/build. The (mapfish) documentation suggests that I should be able to state the location of the file I am trying to create, so I run:
> > sudo ./build.py full.cfg /var/www/scripts/openlayers_sfl.js
> > 
> > This works to the extent that it creates the file, and most elements work OK in the web page. However, it can't find the image folder or the theme folder, so I don't have the navigation elements, and firebug shows me that it's looking for them in the root folder /var/www, so /var/www/theme and /var/www/img. The same happens if I change the build path to /var/www/mapfish/client/mfbase/openlayers/lib/openlayers_sfl.js.
> > 
> > Clearly I can copy the img and theme folders into my root folder, but is there something I'm missing about building the library?
> 
> OpenLayers can only automatically find images and theme if the
> OpenLayers file is *named* OpenLayers.js. The theme can be included
> manually (via a <link rel="stylesheet"> to theme/default/style.css), and
> the image path can be specified by setting OpenLayers.ImgPath.
> 
> -- Chris
> 
> > 
> > 
> > ------
> > Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information.
> > 
> > _______________________________________________
> > Users mailing list
> > Users at openlayers.org
> > http://openlayers.org/mailman/listinfo/users
> 
> -- 
> Christopher Schmidt
> MetaCarta
> 
> 
> -- 
> -----------------------------------------------------
> Joanne Cook
> Senior IT Support and Development
> Oxford Archaeology (North)
> 01524 880212
> http://thehumanjourney.net
> 
> 
> ------
> Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information.
> 

-- 
Christopher Schmidt
MetaCarta


-- 
-----------------------------------------------------
Joanne Cook
Senior IT Support and Development
Oxford Archaeology (North)
01524 880212
http://thehumanjourney.net


------
Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information.