topic Re: ArcGIS API for JavaScript Version 3.11 Released in ArcGIS JavaScript Maps SDK Questions

ArcGIS API for JavaScript Version 3.11 Released

BjornSvensson — Mon, 06 Oct 2014 19:25:43 GMT

Today we released version 3.11 of the ArcGIS API for JavaScript. The optimizer has been updated to support the latest version, and the API & SDK is also available for download. Note that the downloads have moved to a new place.

Read the blog at http://blogs.esri.com/esri/arcgis/2014/10/06/arcgis-api-for-javascript-version-3-11-released/ .

Or for the complete details, read the Whats New at https://developers.arcgis.com/javascript/jshelp/whats_new.html.

For those of you not usually reading any of the above, please read at least the first item, that says:

"This is important if you’re upgrading from earlier versions!

To update your code for version 3.11 references, replace the following URLs:

change /3.10/js/dojo/ to /3.11/ (note the dropped “/js/dojo”) and change /3.10/js/esri/ to /3.11/esri/ (note the dropped “/js”).

An example of this is shown below

Re: ArcGIS API for JavaScript Version 3.11 Released

TimWitt2 — Mon, 06 Oct 2014 19:32:22 GMT

Good stuff!

Re: ArcGIS API for JavaScript Version 3.11 Released

KenBuja — Mon, 06 Oct 2014 20:44:26 GMT

What's going on with the Explore Heat Map sample as you pan east?

This is the result when panning east across the dateline

Which is different from panning west

Re: ArcGIS API for JavaScript Version 3.11 Released

BjornSvensson — Mon, 06 Oct 2014 21:03:54 GMT

Hi Ken Buja‌, the heatmaprenderer is currently in beta and has issues with wraparound if the map starts centered in the eastern hemisphere (which is what you already spotted).

Re: ArcGIS API for JavaScript Version 3.11 Released

DavidColey — Mon, 06 Oct 2014 21:36:23 GMT

Hi Bjorn-

Can you tell us where we might go for the ExpandoPane css? At 3.10 the url is:

http://js.arcgis.com/3.10/js/dojo/dojox/layout/resources/ExpandoPane.css"

Thanks

Re: ArcGIS API for JavaScript Version 3.11 Released

BjornSvensson — Mon, 06 Oct 2014 21:42:56 GMT

Change the number to 3.11 and remove the "js/dojo":
http://js.arcgis.com/3.11/dojox/layout/resources/ExpandoPane.css

Re: ArcGIS API for JavaScript Version 3.11 Released

Manuel_FernandoBenitez — Tue, 07 Oct 2014 13:28:12 GMT

Great!

Re: ArcGIS API for JavaScript Version 3.11 Released

Anonymous User — Tue, 07 Oct 2014 19:25:58 GMT

There is an issue with my measure widget in 3.11. Has this css for the buttons changed?

Re: ArcGIS API for JavaScript Version 3.11 Released

BjornSvensson — Tue, 07 Oct 2014 19:29:55 GMT

Yes. As mentioned in What's new in Version 3.11 | Guide | ArcGIS API for JavaScript we did a number of changes to the Measurement widget (even though we didn't specifically mention CSS on that page).

Could you maybe create a new thread with an example of your code, and/or link to your app?

Re: ArcGIS API for JavaScript Version 3.11 Released

RobertScheitlin__GISP — Tue, 07 Oct 2014 19:33:06 GMT

Jeremy,

Did you update your apps paths to the css and requires?

This is important if you’re upgrading from earlier versions!

To update your code for version 3.11 references, replace the following URLs:

change /3.10/js/dojo/ to /3.11/ (note the dropped “/js/dojo”) and change /3.10/js/esri/ to /3.11/esri/ (note the dropped “/js”).

Re: ArcGIS API for JavaScript Version 3.11 Released

Anonymous User — Tue, 07 Oct 2014 19:37:24 GMT

Hi Robert

I did update the CSS and requires. All other widgets whether ESRI created or custom are working. Only the Measure widget is having issues.

Re: ArcGIS API for JavaScript Version 3.11 Released

Anonymous User — Tue, 07 Oct 2014 19:37:58 GMT

Unfortunately its an internal app, I created a new post a little while ago here Measure Widget Issue - ArcGIS Javascript API 3.11 - Geographic Information Systems Stack Exchange

Re: ArcGIS API for JavaScript Version 3.11 Released

Anonymous User — Tue, 07 Oct 2014 19:38:48 GMT

When I look into the source the button portion of the Measure Widget is not being parsed.

Re: ArcGIS API for JavaScript Version 3.11 Released

Anonymous User — Tue, 07 Oct 2014 19:43:11 GMT

I also created a new ESRI thread https://community.esri.com/thread/114632?sr=inbox

Re: ArcGIS API for JavaScript Version 3.11 Released

JohnGrayson — Tue, 07 Oct 2014 19:48:52 GMT

I ran into some general css issues when moving up to 3.11 and they were all related to differences in the 'claro' theme in dojo 1.10.0

Re: ArcGIS API for JavaScript Version 3.11 Released

Anonymous User — Tue, 07 Oct 2014 20:03:20 GMT

Anything specific you wouldn't mind sharing?

Re: ArcGIS API for JavaScript Version 3.11 Released

DavidColey — Tue, 07 Oct 2014 21:34:20 GMT

Thank you that was it

Re: ArcGIS API for JavaScript Version 3.11 Released

JohnGrayson — Tue, 07 Oct 2014 21:50:13 GMT

For one of my apps which is based on the application boilerplate template, I had to make these two adjustments:

.claro .dijitSplitContainer-child, .claro .dijitBorderContainer-child {

border : none;

}

.claro .dijitSplitContainer-dijitContentPane, .claro .dijitBorderContainer-dijitContentPane {

background-color : transparent;

}

Re: ArcGIS API for JavaScript Version 3.11 Released

RaimondsVerpejs — Mon, 24 Oct 2016 13:23:31 GMT

After upgrading API to 3.11 (or newest) i cant load my application using proxy:

"{error: {code: Forbidden,message:"Application is being used for an unsupported service... URL"

status:403

require([
"esri/geometry/Extent", "esri/map", "esri/layers/ArcGISTiledMapServiceLayer"
], function(
Extent, Map, ArcGISTiledMapServiceLayer
) {
esri.config.defaults.io.proxyUrl = "proxy.ashx";
esriConfig.defaults.io.alwaysUseProxy = true;

var initExtent = new esri.geometry.Extent(xxx, xxx, xxx, xxx, new esri.SpatialReference({wkid: xxx}));
map = new esri.Map("map",{extent:initExtent});
var basemap = new esri.layers.ArcGISTiledMapServiceLayer("URL");
map.addLayer(basemap);

});

How to work around?

Re: ArcGIS API for JavaScript Version 3.11 Released

RobertScheitlin__GISP — Mon, 24 Oct 2016 13:57:05 GMT

Raimonds,

That error message does not seem like it would have anything to do the API version you are using unless you are switching protocols (i.e. http to https or vice versa in your urls).