|
POST
|
Hi folks, the 2D measurement widget is looking good for 4.9 actually (Sept release)! I will post an update when we get closer to the release date to let you know where we are.
... View more
08-10-2018
03:58 PM
|
3
|
4
|
3116
|
|
BLOG
|
This post provides insight into how we manage version 3.x of the ArcGIS API for JavaScript (JSAPI) release plan and technical support strategy. The JavaScript development team has made great progress bringing version 4.x of the JSAPI closer to parity with 3.x, meanwhile introducing new tech for building very dynamic, expressive 2D and 3D apps. Over the next year, each release will be a balance between capabilities for reaching full parity with 3.x and brand-new innovation. Many customers’ app requirements are fully met by the current release of the 4.x API (4.7) while others are still dependent on 3.x (either with existing apps that they are maintaining or new apps that have requirements such as full editing support). We also have many Esri apps built on 3.x, such as the 2D version of Web AppBuilder for ArcGIS. Technical Support Plan Because we have a large customer base that still depends on 3.x, we are very careful about how we manage the Product Life Cycle (PLC). Our strategy is to make all PLC dates relative to our estimation of the last 3.x release. When is the last release? It depends on when we reach full parity in 4.x, enabling us to move critical apps such as ArcGIS Online’s map viewer to 4.x. When we reassess our estimation of the final release date, PLC phase dates are updated accordingly. Relative dates for each PLC phase are determined in the following manner: - 3.x remains in "General Availability" until the last release of 3.x. - 3.x moves into "Mature Support" after the last release, and lasts for 1 year. - 3.x is retired 3 years after General Availability ends. For more information about the above software support phases and what they entail, refer to the PLC. Recent Update to the PLC Version 3.x was scheduled to move into mature phase next month; July 2018. Based on the current status of the API, this was moved to July 2019, with the mature phase starting August 2019 and retirement in August 2022. As mentioned above, these dates will be revisited depending on progress made towards 3.x parity. If you need further clarification on the above, please reach out to Technical Support through the normal channels. ArcGIS API for JavaScript Kwasi Asante
... View more
06-01-2018
01:36 PM
|
6
|
4
|
12689
|
|
POST
|
Hi David, sorry I don't have an update on the analysis widgets yet. At this time, all I know is that they won't be in 4.5 (~end Sept).
... View more
08-04-2017
11:34 AM
|
0
|
0
|
2443
|
|
BLOG
|
This is the draw sample I was referring to: Draw polygon for spatial query | ArcGIS API for JavaScript 4.4
... View more
07-17-2017
10:30 AM
|
0
|
0
|
6324
|
|
BLOG
|
Here is the simple measure sample that I was referring to: Measure while drawing | ArcGIS API for JavaScript 4.4
... View more
07-17-2017
10:29 AM
|
0
|
0
|
6324
|
|
BLOG
|
We are currently targeting the December release (4.6) for the measurement widget. However, 4.4 will have a sample demonstrating how you can implement simple measurement on your own using map events and the geometry engine.
... View more
07-05-2017
10:02 AM
|
0
|
0
|
6324
|
|
BLOG
|
The team is currently working hard on the sketching implementation for 4.x. We had hoped that we'd have an initial release of 2D draw tools in the 4.4 release, and while the team made good progress on the overall design and beginning implementation, it isn't ready for release. 4.5 is due out in the fall and we are working towards getting 2D drawing into that release. I can share any updates to this thread as the release approaches. 3D drawing will likely be next year. The full *editing* experience will take more time and will be a multi-release implementation (that includes editing widgets). That being said, we will likely have a sample released with 4.4 that shows how you can simply use map events to draw a polygon (that is then used for a spatial query). For those of you that have projects that can't wait for OOB drawing in the API, you can use this code as an example for writing (simple) custom drawing tools. I hope that helps!
... View more
06-21-2017
02:01 PM
|
3
|
0
|
6324
|
|
BLOG
|
New ArcGIS API for JavaScript releases are just around the corner! Here is a preview of some of the new capabilities coming in early July. (Note: These are some of the highlights; a full list of new capabilities and enhancements will be provided in the release notes.) ArcGIS API 4.4 for JavaScript New styles for points in city landscapes: Styling the point data in city scenes can now be done more effectively. Point graphics can be configured to display above buildings with the new relative-to-scene elevation mode. Callout lines can be used to better understand point locations (a callout is essentially extended from the top of the scene). Highlight in 3D: The ability to highlight features in a 3D scene, with options to configure the color and opacity of the highlight effect. Styling building data: We added the option to remove building textures to better emphasize thematic mapping of buildings, and also the option to make textures grayscale (one example of when you might want to do this is if you want to draw attention away from the buildings, and highlight a particular set of interest). Smart Mapping You can now automatically generate renderers for SceneLayers using SmartMapping. Generating type renderers with smart mapping is new to both 2D and 3D views. Note: When we reference smart mapping/generating renderers, we mean that the API creates smart defaults for your map/scene styles on the fly. This capability is typically used in data exploration type apps (as opposed to defining the styling explicitly in code). PointCloudLayer enhancements Added the ability to add natural lighting conditions to a point cloud layer in order to better distinguish objects. Better web map support Added support for Map Notes, WMS, and WMTS layers. OGC support Added support for WMS and WMTS layers. VectorTileLayer printing This release of the JavaScript API includes a support for vector tile layer printing through client-side image. Arcade support in popups Arcade expressions can now be applied in the popup’s content. This is useful for situations when you want to display data that isn't present as an attribute value in your FeatureLayer instance. Web maps that have been created in Portal or Online that contain popups with Arcade expressions will be honored in apps built with the JS API, and developers can also write Arcade expressions directly in their code. Widget standardization In this release, the following widgets have been updated to the widget framework, initially introduced at 4.2: Legend, Popup and Search widgets. Custom Layers The SDK will include documentation and samples for creating your own custom layers. ArcGIS API 3.21 for JavaScript Arcade support in popups As described above. VectorTileLayer printing As described above. (...plus minor enhancements and bug fixes)
... View more
06-20-2017
08:15 AM
|
13
|
17
|
16125
|
|
POST
|
Correct, esri/dijit/analysis/* refers to the analysis widgets. We don't yet have these widgets scheduled yet; I will provide an update to this post once I have more information.
... View more
03-31-2017
01:17 PM
|
1
|
2
|
2443
|
|
POST
|
Hi Adam, the print widget will be included in this release as well (and has been redesigned for 4.x; it's pretty nice!). The draw widget will be part of the summer release at the earliest.
... View more
12-16-2016
12:05 PM
|
0
|
0
|
1297
|
|
POST
|
The SDK is now updated with IdentityTask and FindTask. We also just published the TypeScript definition files with both of these added back in: https://github.com/Esri/jsapi-resources/commit/2978250
... View more
10-21-2016
01:36 PM
|
0
|
0
|
2195
|
|
POST
|
We already spoke on the phone, but just in case others are following this thread - We are working towards having WMS support in 4.3. I will post an update closer to the release to confirm whether it will likely make it.
... View more
10-17-2016
02:15 PM
|
0
|
0
|
2195
|
|
POST
|
Your questions are valid and you've helped us with an oversight. Please keep the feedback and questions coming!
... View more
10-12-2016
03:27 PM
|
0
|
0
|
2195
|
|
POST
|
Yes, we will recreate the TypeScript definitions along with the SDK update. I should have more info on timing by mid-next week.
... View more
10-12-2016
11:53 AM
|
2
|
2
|
2195
|
|
POST
|
Hi Jan, I support the JS API from a product management perspective. I understand your frustration and the difficulty you are experiencing right now. It may not make your job easier, but I'd like to be transparent about our release strategy to at least provide insight into why we released the API into production, and also some info about upcoming releases. As you know, 4.x was a complete rewrite of the API. While 4.0 didn’t have functional equivalence with 3.x, it did lay the foundation with a brand new architecture, programming patterns, and integrated new capabilities like 3D and map rotation. Developers wanting to build web apps with 3D visualization could start using this API and put them into production with the confidence of a fully-released API. In fact, there are already hundreds of great apps already out there that are built on 4.x. Developers that wanted to build 2D web apps could use the online SDK to figure out whether the current version of the API had the capabilities needed for their application requirements. In many cases, developers had to (and continue to) use 3.x because they needed something such as edit which is not yet available in 4. However, by releasing 4.0 to production, we are not holding back those developers who are building apps with requirements that are met by the current API. Because of the value we see in both APIs, we have committed to releasing both APIs concurrently – 4 releases of both 3.x and 4.x are planned for 2017. That being said, we received feedback from the developer community that they needed more help determining whether the current version of the 4.x API had the capabilities needed for their app. For that reason, we put together the Choosing a version guide and detailed matrix help developers quickly determine whether a particular functionality had been built, and also "map" 3.x classes/properties/methods to 4.x (especially useful for cases where the implementation has been redesigned for 4.x). To your point, we haven't provided extensive information about when each of the remaining capabilities will be implemented in 4.x. I understand that this could make it difficult for you when planning your development work. To share information on our release strategy, and a potential way in which we might be able to improve a bit: We have a very dynamic development and release process, with requirements that are driven by the ArcGIS platform (such as enhancements in ArcGIS Online, deeper support for 3D across the platform, vector tile layer support, etc), requirements specific to the API that we've collected from customers over time such as map rotation, and then all of the capabilities that will bring 4.x at parity with 3.x. At any given time, the team works on shorter-term advancements that make it into the subsequent release, and also longer design work that can span multiple releases. Because of all of this complexity and the dynamic nature of our work, we are careful about not committing to time frames unless we are very confident about the timing (so that developers don't plan their development schedule around something that they depend on and later find that it has been delayed). With this in mind, I think we can do better at communicating at least what we are working on, without a firm commitment to a particular release. I think this will give developers an idea about what capabilities are *in progress*, and those that will take longer to implement. One idea we had was to post a blog approximately one month before each release that describes this information. Do you think that would help? I think it is also worth mentioning that 3.x is still a great option - it is a fully featured 2D API that will be supported through 2020. All versions of the API will also be hosted on our CDN indefinitely, so apps won't break, even after the API version reaches the retirement phase. More info here. As you suggested, the 4.x API is in fact a moving target; I promise that we will do our best to support you as you plan your development and build your apps. If you have any specific questions about the status of an API feature, please post them on geonet or contact me directly and we can have a transparent conversation about it. Thanks, Julie
... View more
10-12-2016
11:51 AM
|
1
|
2
|
3069
|
| Title | Kudos | Posted |
|---|---|---|
| 9 | 10-09-2025 03:54 PM | |
| 2 | 10-08-2025 12:38 PM | |
| 1 | 07-28-2025 12:46 PM | |
| 4 | 07-28-2025 08:58 PM | |
| 2 | 02-26-2025 11:02 AM |
| Online Status |
Offline
|
| Date Last Visited |
03-03-2026
07:57 AM
|