OpenLayers Blog

All the maps that are fit to blog

OpenLayers 2.4-RC1

April 4th, 2007 by crschmidt · 10 Comments

The OpenLayers Development Team is proud to announce the first release candidate of OpenLayers 2.4. While the public API maintains backwards compatibility with previous 2.x releases, OpenLayers 2.4 introduces a number of internal changes that are important for developers working inside the OpenLayers library, including:

  • Support for rendering vectors on the map, using both SVG and VML (finally!)
  • Vector Geometry classes
  • New UI Handler classes
  • New and improved Control classes, including a generic toolbar class
  • Substantial enhancements to existing Layer classes, particularly WFS
  • A massive effort to track down and eliminate memory leaks of JavaScript objects and DOM nodes
  • Better auto-generated class documentation
  • Tons and tons of bug fixes!

As of 2.4-RC1, the OpenLayers 2.4 release closes 106 outstanding tickets, more than any other OpenLayers release to date! For this we are indebted to the many members of the community, as listed in our new contributor file, who have put their hard work into improving OpenLayers. Please see the release notes for OpenLayers 2.4 and the list of closed tickets for more details.

We invite you to help us test the 2.4 release candidate! To test 2.4 in your applications, include the following tag in your OpenLayers-powered page:

  <script src=""></script>

As always, the source is available at Bug reports can be filed in Trac, under the 2.4 version and milestone.

We look forward to your feedback!


The OpenLayers Team

Tags: Uncategorized

10 responses so far ↓

  • 1 Glen Stampoultzis // Apr 4, 2007 at 8:03 pm

    Does this release work in IE? I seem to be having a few issues.

  • 2 crschmidt // Apr 4, 2007 at 8:40 pm

    It should. Any aspect that doesn’t should be reported as a bug. If you can find an example in our examples which doesn’t work in IE, please please please report it — here, mailing list, trac, wherever.

  • 3 Penyaskito OpenLayers « // Apr 5, 2007 at 5:12 pm

    [...] través del blog de OpenLayers, me entero de que han empezado a publicar un archivo en el svn con una lista de todas las personas [...]

  • 4 Vector mapping comes to the masses, but is it free? « thinkwhere // Apr 5, 2007 at 5:23 pm

    [...] earth, geoRSS, virtualearth, geo, gis, google maps, Mapping | In the space of a couple of days, OpenLayers, Microsoft’s Live Search and Google Maps have enabled vector drawing (that’s points, [...]

  • 5 wangcheng // Jun 6, 2007 at 7:10 am

    Thanks for your Contributions for webgis. But I have to say that , the efficiency openlayers parses gml documents is not so good , you object all the points in a polygon before drawing it with vml or svg ,which directly result to the inefficient .I test your gml using the states’ gml data(less then 400k) , it costs more then 10S.(256M dell).

    I have wirte some code to parse and draw the states’gml data(exclude the wfs call from geoserver),it costs less then 1s.

  • 6 wangcheng // Jun 6, 2007 at 9:46 am

    I’sorry for my poor english.I want to say you have instantiated all the points.

  • 7 wangcheng // Jun 7, 2007 at 4:08 am

    Lots of Coordinates parsing of the points is another important factor of the inefficiency .I think maybe you can parse the coordsize attribute of the group contanier using the resolution (var resolution = this.getResolution()) , It will undoubtedly improve the performance of openlayers.

  • 8 wangcheng // Jun 12, 2007 at 2:04 am

    The really factor which contributes to the inefficient is the behaviour “push” of the Array , but not the behaviour “new “.

  • 9 wangcheng // Jun 12, 2007 at 9:20 pm

    The vector objects cant’t be edited by the web visitors.

  • 10 wangcheng // Jun 14, 2007 at 10:50 am

    I want to afford my thought about the program of parsing gml data called from a wfs server . I think you don’t have to follow the procedure to parse gml data using the classes Polygon , LinearRing,Point and act . You could write some simple functions to extract the coordinates information in the gml file and give them to vml elements‘ path properties .
    Maybe it refers to the edit functions later , i think we could construct the point,line and polygon objects when the mouse passes a vml element . Of course when a vml element contains lots of points ,it’s not that easy.
    I need a reply or some exchange .