ArcGIS API for JavaScript Version 3.5 Released

Version 3.5 of the ArcGIS API for JavaScript is now available! Please refer to the What’s New in 3.5 for the full list of features and bug fixes. Highlights include:

Support for class.on() style events for the map, layers and tasks

Several classes in the API have been enhanced to support .on() style events, also referred to as evented. Specifically, esri/map as well as all classes in esri/layers and all esri/tasks now support class.on() style events. Classes in esri/dijit will have support for this style of event management at a future release.

Some samples have been updated to demonstrate the new .on() style event listening (as well as re-written to use AMD):

Please refer to the full What’s New in 3.5 for additional details on class.on() style events.

More samples that use Asynchronous Modules Definition(AMD)

Additional samples that have been re-written to use AMD:

The full What’s New in 3.5 also has a list of bug fixes and enhancements that we added at 3.5.

To download the JS API and host on your own server, visit the ArcGIS API for JavaScript download page.

This entry was posted in Developer and tagged , , . Bookmark the permalink.

Leave a Reply


  1. Jim Sibbald says:

    Thank you as always for your excellent work on JavaScript. I have, however, noticed that in versions 3.4 and 3.5 library and SDK that there are numerous .DS_Store files scattered throughout. These are created by Mac OS X, I believe. Can they be deleted for those of us not using Apple products?

  2. thisishap says:

    Hi. I’m trying to use the feature layer and a dgrid sample with some of my own data coming from my arcgis for server. I’ve modified it so that everything works except for the highlighting of the grid row once the map polygon is selected. The only thing I can figure that is different between the two is that your sample used feature class “objectid”s and I’m using a shapefile so my key field is “FID”. I assume the failure is happening somewhere at the reference to “.field-id” or “query.objectIds”, wherever those appear. Any idea how I could fix this to work with shapefiles instead?