3.17 API Update

[cmccullough2]

Will you be migrating this application to the 3.17 API in the near future?

[tmcgee]

@cmccullough2 I am using the 3.17 api without issue. This is in multiple apps for a couple of my clients.

[cmccullough2]

Thank you. I am going to start my migration to 3.17.

[cmccullough2]

For some reason when I moved to the 3.17 api, this image appeared in my viewer. I.E's Dom explorer is not giving me any clues. Have you seen this before?

[tmcgee]

I have not seen that before. The Chrome Dev Tools might be a better tool to inspect the DOM for additional clues.

[cmccullough2]

Thanks. I am looking.

[tmcgee]

@cmccullough2 The repo has been updated to version 3.17 of the Esri JavaScript API. The latest update also provides support for version 2.1 of WebApp Builder.

[cmccullough2]

Double thumbs up. Thanks

[cmccullough2]

@tmcgee When you store the esri.css locally it breaks a bunch of images. I went into the css file and changed the location of images from ../dijit/images/{image} to ..images/{image} to repair the paths. I am a bit nervous about what this will do for future widget installs, etc. (the unknown). Just a thought.

[tmcgee]

Yes if you do not download the images, it would break due to the image paths in the css file. The most common practice for hosting locally is to download the entire JS API which includes everything. Is that not what you are doing?

[cmccullough2]

Yes, I am using the entire JS API. When I need to have the API off my work network I am hosting the API at this location, http://gissweetspot.com/arcgis_js_api/library/3.17/3.17/init.js. The location for the esri.css is here, ''. While I am at work, I have it at another location.

[tmcgee]

The path to your esri.css does not appear in your message above but I see in in the notification I receive.

I am not following why you have the esri css file under the cmv folder - a different location from the rest of the API. Are you making some customizations within it? If so, typically, you use the one in the API location and include your own custom css overrides in a separate css file like this

[cmccullough2]

I have the esri.css in the cmv/css folder within the project. the JS API is outside. I am assuming I have to put the css someplace else??

[tmcgee]

I guess I don't understand why you have the esri.css separate from the JS API. If possible, you should try to keep the css file together with the API and then put any css customizations in a separate file within the project.

[cmccullough2]

Ok, good advice. Under what folder in the api should the css reside.

[cmccullough2]

Nevermind. That was a dumb question. I figured it out. I was making this harder than I needed to.

[tmcgee]

The file should already be included with the api however I see that it is not there on the gissweetspot.com server. That suggests that gissweetspot does not have a complete copy of the API (or I am missing something).

Obviously, I cannot see what you are using inside your network. When you are outside your network, can you use //js.arcgis.com/3.17/esri/css/esri.css and //js.arcgis.com/3.17/ instead of the gissweetspot.com?