Latest Contributions by LefterisKoumis

Hello Peter. I developed WAB's custom widgets and also modified ESRI widgets to fit the needs our customers. For the modified ESRI widgets, I kept track of the changes by keeping a log. Github is another option to keep track of your changes. Every time there was a new version of WAB, I just posted the custom widget by updating the app's config.json file. For the ESRI's customized widgets, I had to re-apply the changes. In 2019, ESRI announced that the WAB 2D it will not upgraded to use the newer JS API library, version 4.x WAB 2D is using the older JS API 3.x library. Instead, they introduced the Experience Builder (EB) to replace WAB in the near future.  So, all the new tools and widgets which are based on the JS API 4.x cannot be used in the WAB 2D. That was a major shift because WAB 2B is based on Dojo but the EB is based on the ReactJS.  You can see that since last year there were very few upgrades done on the WAB2D, since ESRI moved to a different direction. So, it is my opinion, that  if you are getting started in the development of web-based apps, to spend time to learn ReactJS and Typescript and utilize the JS API to create custom widgets. I personally will not use EB. Just use HTML5, css3 and JS API 4.x to develop web-based apps. I am also spending time to become familiar with the esri-calcite effort. The templates will assist you creating apps which use the JS API 4.x and websites which will be in compliance with the ADA requirements. That's my two cents. https://esri.github.io/calcite-web/     ... View more

For anyone who has the same concerns, here is a reply I received from one of the original contributors to the Calcite work, Eric Goforth who got a response from ESRI: Got an official statement from Esri (specifically, Julie Powell who is the Product Manager for the ArcGIS API for JavaScript) on the status / future of Calcite. Her response is quoted in blue below: This is a little bit of Github repo spaghetti, but I want to give you a little background… As you know, Calcite has been around for some time and exists in several repos in varying states. The repo that you referenced, calcite-web, was the original Calcite implementation. Over the years Calcite has grown to include a full web component library, and the design has evolved over time. All new work goes into another repo, calcite-components, and our internal version of this is what the UI/UX of the new map viewer is based on. Calcite-components inherited everything that we needed from calcite-web. Now that Calcite is becoming an official offering, we are cleaning up all of the repos and references to Calcite, and will be publishing a new repo with the most up to date content. All other repos will be deprecated. Here's the good news: It is still the recognizable Calcite design that GEO Jobe knows, but has continued to evolve as design systems do. It includes many web components (not just css) that can be used directly in applications, framework-agnostic. It now has dedicated resources, so it will continue to grow. It will be fully integrated into the Developer site, and simply licensed with our Essentials plan (or higher, and available for organizational users) The source code will remain available for those that want to customize We will be introducing our Design System story at the Developer Summit and EPC and the new repos will be available around that time. So be on the lookout for the next iteration getting released around the EPC / Dev Summit 2021. As expected, it won't visually depart from the current Calcite -- which means that any apps written with Calcite Web will still look Esri-authentic, even if they can't leverage all of the new features of the relaunch. ... View more