Layer.js change breaks commercial layers

FixedZoomLevels clobbers initResolutions in the Layer.js. We used to set the properties in setMap, which isn't clobbered, until r1662, but we moved it into initResolutions. That's a fine choice, but we need to make sure that FixedZoomLevels layers still get most of their properties set by the map.

Erik, please review and commit.

so the reason commercial layers weren't working is actually due to a problem introduced with the fix for Scale dependent layer visibility ticket.

See #99 for new patch to fix this.

so actually there was one of those variables that we did want to bring over from the map to the layer: maxExtent.

In the case of a traditional layer maxExtent is sometimes used in the initialization of the resolutions array (when maxResolution is set to "auto"). FixedZoomLevel layers, however, have no need for maxExtent in order to initialize their resolutions.

Regardless of this fact, maxExtent *is* used for determining whether or not to draw tiles outside of the maxExtent, so not setting this poses a problem. Currently, you don't see this in the google layer because a maxExtent is set by default in its initialization(). VE, however, does not have such a default and we see a script error.

So: We'll bring it over!

See patch.

Please review

no need to copy max/minExtent, projection, or units -- none of these is modified by initResolutions. Instead, copy them over in setMap

cr5 -- please review

Patch looks good. Go ahead to commit.

ok. now i think we have a finally solution. pulled out unnecessary copies from general layer.js initResolutions() and redid the fixedzoomlevels initResolutions() to correctly calculate min/num,max zoomlevels stuff. changed goog/yahoo/ve layer from having present min/max to having *constant* min/max. these constant values get taken into account in the calculations. added tests.

Closed with r1723.