<\/HEAD>
On 21.03.2017, Lars Schmitz<\/A> kicked off our four-part webinar series for developers about the new ArcGIS Developer Program in a one-hour webcast<\/A>. On Tuesday (28.03.), Lars Schmitz<\/A> and Alexander Erbe<\/A> held the second webcast<\/A> about creating native apps with ArcGIS Runtime<\/A> focusing on the new version 100 (Quartz) and information about the new ArcGIS Runtime Deployment Model<\/A>. This time it was about creating web applications with the new ArcGIS API for JavaScript<\/A> as well as the innovations in the Web AppBuilder for ArcGIS<\/A>.<\/SPAN><\/P><\/P>
<\/SPAN><\/P><\/P>After a brief introduction,
Lars Schmitz<\/A> and I first gave an overview of the currently available versions of the API and the functional differences. The migration to the current version was also briefly addressed. Afterwards, we looked at some demos, especially the functional innovations in the new 4.x versions. A brief look at the innovations in the Web AppBuilder rounded off the webinar.<\/P><\/P>
Important links from the webinar:<\/P>
- ArcGIS API for JavaScript:
Release Notes<\/A> and Migration<\/A><\/LI>WebAppBuilder for ArcGIS: What9;s new<\/?\>?<\/?\>
The video of the webcast:<\/?\>
\
<\/?\>
Many thanks again for your lively participation, we also had great fun. If you have any further questions, suggestions or criticism, you can also use the comments for this. The slide set for the webinar is attached as a PDF to this blog.<\/?\>
<\/?\>
The next webcast on the new ArcGIS API for Python<\/?a> will take place next Tuesday, 11.04., at 4 pm. If you have not yet registered for the webinar series: registration is available here<\/?a>.<\/?p>
Your GeoDev Germany Team<\/?p>
P.S.: We continuously provide you with information on developer and startup topics in our German GeoNet group<\/?a>. As a member, you have the opportunity to actively participate in the community and, for example, write your own blogs. We would be happy 😉<\/?span>
Q&A:
Q: In 3.20 some functions are marked with a cross instead of "Coming soon." Will these functionalities still be identical to 4.x in the future, such as 3D data?
A: 4.x is the "New kid on the block." The goal for this year is to catch up functionally with 3.x. You should definitely rely on 4.x if 3D is also to be used.
Q: But 3.x will never contain 3D data, right?
A: Correct, currently 3D functionality is exclusively planned for 4.x.
Q: How long will 3.x still be supported? I would like to switch to 4.x but have no possibility to do so in the foreseeable future.
A: 3.x will continue to be developed. For example, version 3.21 is planned for Q3. According to current planning, General Availability runs until the end of the year. Afterwards there will be 2 years Mature Support (until December 2020).
Q: What does "exclusively AMD" mean for 3D view on laptops with Intel Graphics?
A: AMD stands for Asynchronous Module Definition and has nothing to do with processors from manufacturer AMD. With AMD, modules and their dependencies are loaded asynchronously in the JavaScript environment.
Q: What restrictions/prerequisites are there for extending Operations Dashboard? Can version 4.x also be used?
A: Currently, 3.x is supported; we are waiting for support of 4.x.
Q: Will Arcade be available only for FeatureLayer or all layer types in future?
A: Currently FeatureLayer is supported. Also check out this DevSummit video: https://www.youtube.com/watch?v=ctNNsthBo8E<\\/a>.
Q: Does that mean the entire API is available for TypeScript?
A: Yes, there are TypeScript Definition Files for 4.x. These are located at https://github.com/Esri/jsapi-resources/tree/master/4.x/typescript and are continuously developed.
Q: Does touch operation of map functions (on smartphone) offer the same functionality as mouse & keyboard?
A: At https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html#navigation, you will find all supported commands or functions.
Q: Will custom widget development in future rely only on TypeScript, or will there also be an option for pure Dijit widgets? Or alternatives?
A: Yes, exclusively via TypeScript and the new Widget Framework.
Q: Since a lot is shown about Portal and I once heard "who develops without Portal develops against a wall," how does support of 4.x API look regarding Server? Or is everything moving towards Portal?
A: The API can still be used directly with services of an ArcGIS Server. The advantage of Portal is that WebMaps or WebScenes can be created there and addressed directly from the JavaScript API via their ID. The data, services, visualizations (including Arcade expressions!) and functions stored in the WebMap are considered one-to-one, loaded and displayed.
Q: Is it possible to temporarily display/integrate client resources (shape files, MDBs, etc.) as features? Without going through server (ArcGIS Server)
A: It is still possible to convert shape files via ArcGIS Online or ArcGSI Enterprise into feature collections and display them. Local data such as MDBs are not directly supported.
