Hello, yes, great +1
Uli Christoph Baudson schrieb: > Currently, this is a string containing four comma-separated coordinates. > This is hard to use, whenever you want to perform an operation on the > extent, you have to split the string and use parseFloat. There is also > no way to register an event with the setting of the extent, because it's > not a function. > > At the development sprint in Hannover Peter and I discussed the > implementation of a restricted extent. For this, we concluded, using the > Extent object as attribute (and no longer the string) would be > necessary. I am changing this in trunk, if this motion passes. The > changes would include > > (1) The extent attribute is currently *set* by > > map.extent = "a,b,c,d"; > > The new version would use this syntax > > map.extent = new Extent(a,b,c,d); > > > (2) The extent attribute is currently *read* by > > map.extent > > which is a string "a,b,c,d". The new version would use this syntax > > map.extent.toString(); > > and return the same string "a,b,c,d". > > > All custom modules would have to use these changes as well, which will > be important when updating. I'll only change the modules in Mapbender > trunk. > > Please second this motion and vote. > > Christoph > -- --------------------------------------- Ulrich Rothstein WhereGroup GmbH & Co. KG Siemensstraße 8 53121 Bonn Germany Fon: +49 (0)228 / 90 90 38 - 17 Fax: +49 (0)228 / 90 90 38 - 11 mailto:[email protected] www.wheregroup.com Amtsgericht Bonn, HRA 6788 ------------------------------- Komplementärin: WhereGroup Verwaltungs GmbH vertreten durch: Olaf Knopp, Peter Stamm --------------------------------------- _______________________________________________ Mapbender_dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapbender_dev
