getMaxExtent(), getMaxResolution(), and getNumZoomLevels(). They were just
wrapping around the properties. better to just access the property directly.
Needed to update for these removals in many different files.
- Improved initResolutions() functionality. It is now I believe both thorough
and complete. The only exception is that we should maybe allow a way for
the user to set up resolutions[] array using only minResolution and
numZoomLevels instead of only maxResolution and numZoomLevels... but I'm not
really sure anyone would ever really want to use that. And at any rate, I
don't know the math for how to do it. I'm sure schuyler or Dr. 5 would.
Oh. for a summary of how initResolutions works, see:
http://trac.openlayers.org/wiki/SettingZoomLevels
- Move getResolution(), initResolutions() out of HTTPRequest and into Layer. On
thinking this through (and trying to write documentation), I realized that
the real, true, GENERIC case for a layer will be using this awesome
resolutions[] array that allows for setting number of zoom levels, default
max resolutions, special scale arrays, etc.
- Updated code for getZoomForExtent() to work with resolutions[] array, instead
of using the the log 2 equation.
- Move standard getZoomForExtent() and getExtent() out of Grid and into
Layer. Like above, there is no reason for these methods to be found so far
down in the food chain. They are part of the generic calculations for
generic layers, so they belong in Layer.
git-svn-id: http://svn.openlayers.org/trunk/openlayers@1379 dc9f47b5-9b13-0410-9fdd-eb0c1a62fdaf
a list of scales or resolutions in the options to the constructor, from which
resolutions are calculated. Map now has a 'setScale' function which will allow
you to zoom to as close to a given scale as possible.
git-svn-id: http://svn.openlayers.org/trunk/openlayers@1171 dc9f47b5-9b13-0410-9fdd-eb0c1a62fdaf
