On Tue, Nov 11, 2008 at 02:47:49PM -0700, Tim Schaub wrote: > Seems to me like we need a setter and getter. So the following would work: > > polygon.setProjection(foo); > polygon.components[0].components[0].getProjection(); // foo > > And it makes sense to me to push the work on to the setter (setting the > same on all components), making access less work.
Really? I guess it's reasnably likely that any access n a specific component is going to be tied to a getProjectino() on all the components, so setProjectin() being slow is better than getProjection() being slow. > I think it also makes sense to me that the layer does not set the > geometry projection. We assume that geometry projection is properly set > before a feature is added to a layer. This pushes the setting or > transforming closer to the parsing (where it makes sense that you'd know > the projection). I agree. Regards, -- Christopher Schmidt MetaCarta _______________________________________________ Dev mailing list Dev@openlayers.org http://openlayers.org/mailman/listinfo/dev
