Latest Contributions by JuliePowell

Ahh, ok. Sorry about that. yes no This one is a bit more complicated, see below The Widget class is going away with widgets. With regards to view models, it is a bit more complicated. First off, we know how important it is that developers can continue to create tailored experiences with the SDK. Going forward, you will be able to build the same custom experiences using the underlying business logic, but the implementation will change. As we move to the component-based architecture, view models are being considered for 3 possible buckets: 1) The View Model will be kept in the core API, but reworked/moved: The functionality will simply move to another location (since they are currently located in the widgets/ folder). 2) The View Model will be dissolved into the core API: The functionality will be available in core, but through other APIs. For example, AreaMeasurement2DViewModel logic could move to an analysis API similar to what 3D has for AreaMeasurementAnalysis.  3) The View Model's logic belongs to the component: The logic will be exclusively used by the component and the view model will be deprecated and later removed. View models fall into this category when we believe that they don't provide additional value to developers. For example, in the case of the WeatherViewModel, different APIs already exist to set Weather directly on SceneView so the view model isn't really necessary. Categorization of view models into the three buckets above depend on the explanation above, but also based on what we are learning from customers. We really want to understand which view models are being used, and for what purpose so that we can make sure we account for the wide variety of scenarios and customer requirements. We are encouraging customers to fill out this survey to help inform this roadmap: https://arcg.is/005zS9 One other aspect that I would like to share is that sometimes view models are used to make a slight adjustment to the UI (like hide part of it, or add a button to do something). Part of our roadmap is to implement slots which are placeholders within the component UI for you to embed your own functionality/workflows. Components also have configuration and styling options through css properties. So in some cases, developers can write and maintain less custom code because they are able to use the out of box components (as opposed to creating their own UI on top of the view models), and still tailor the experience to meet their requirements. So, the more specific information you can share in the survey, the better we can design the component options for your needs.  I am working on a blog that covers this topic. I will post a link here when it is published.  ... View more

@AndreV that is a great question. While the presentation of UI elements are being transitioned from widgets to components, the underlying business logic that is available (today via view models) will continue to be available. That means that you will be able to build custom experiences and workflows using the SDK’s business logic going forward. However, as we work to modernize and continuously improve the SDK, it is important for us to know how you are using the business logic to help inform our longer-term roadmap. When you have the chance, please fill out this survey so that we can use your input to inform the SDK’s roadmap. We want to continue to offer an SDK that provides maximum productivity when building your apps and at the same time offers the flexibility you need to build your organization’s specific requirements. I just published a blog that covers our transition to components, as well as the roadmap for widgets that I think will be very helpful in understanding our strategy: https://www.esri.com/arcgis-blog/products/js-api-arcgis/developers/javascript-maps-sdk-a-full-transition-to-components/   ... View more

Hello @baohuachu2 ! Calcite is Esri's design system that ArcGIS web-based experiences use (except for Experience Builder). We continue to invest heavily in it as build new components, enhance existing ones, add guide topics, and do overall improvements across the design system (for example, we recently worked on better responsive design and design tokens, etc). The jimu application framework is specific to Experience Builder. It is not based on Calcite because of the development timeframes (Calcite components weren't available when ExB was being built/released). Many customers have requested that Esri creates a Calcite-based theme within ExB, which would blend well with components coming from the JavaScript Maps SDK (also based on Calcite) and any custom ExB widgets that are built with calcite components. This is planned, but we don't have a release date at this time (to my knowledge - perhaps @Jianxia has a more up to date answer on that). That said, even though we don't have a Calcite theme in ExB yet, you can use Calcite to build custom widgets today. You can find doc on that here --> https://developers.arcgis.com/experience-builder/sample-code/widgets/use-calcite-components/ I hope that helps!    ... View more