In order to help users quickly get started with the latest features and efficiently build visualization projects, we also specially invited the product manager of the Competence Center, Xue Ge, to the EasyV online live broadcast room to share with you~ July 6th (this Thursday) at 3 pm! The function of the component container will be explained in detail, and a practical demonstration will be given. This live broadcast will answer your questions and allow you to easily grasp the mysteries of component containers. Don't miss this opportunity to interact with the product manager face to face!
If you want to watch the replay of the live broadcast, you can go to the video account "EasyV Digital Twin Visualization" for details!
On June 29th, one of the most anticipated functions of Ezhiwei's internal designers and product managers, "Component Container", has been quietly launched! Many users are curious about what the component container function is? What problems can it help me solve?
1. Two major problems
The reason why it is called "one of the most anticipated functions internally" is because in the process of Yizhiwei project construction, especially the design of large screens for data operations, we will frequently need to use multiple components of the same type to combine Paste, and also need to continue to repeat the data access. Similarly, we found in customer communication that many customers have encountered the same troubles in the process of using EasyV to build delivery. The work troubles associated with this kind of repetitive work can actually be summarized as "two major problems".
Duplicate components The workload of making multiple modules and data access is heavy. When making large screens, it is necessary to frequently create many similar component combinations to meet the temporary data presentation needs of different combinations of dimensions.
Components are often used together, and it is difficult to flexibly adapt to multiple application scenarios in groups. In actual project production, it is often necessary to fully present data effects through component matching, but it is difficult to quickly adapt to layout and data only through "grouping".
Here we give an example, "Medical Operation Monitoring Data Large Screen" contains 15 repeated components, and the data in each component is different, indicating that to complete this large screen, at least 15 repeated configurations of styles and data logic are required.
2. Four highlights
Based on the above "two major problems", the EasyV production and research team responded quickly and brought everyone the function of "building block assembly" - component container.
The so-called component container is the production container of custom splicing components (that is, instances), and the size of the container is the size of the external visible area of each instance.
The instance mentioned in the definition refers to each repeating module unit in the component container, and the preset instance refers to the instance module of custom splicing components in the editing mode of the component container. And we will be data-driven, according to the set automatic layout, and other identical modules generated by rendering are called derivative instances.
The pictures are: default instance and derived instance
In practical applications, we found that when the component container is not used when building a large screen, the builder needs to configure the style and data of the components one by one, and the cost of data access and subsequent maintenance is extremely high.
After using the component container to customize the splicing components, the data source is uniformly connected outside the component container, and the data source is uniformly connected to complete the data distribution. Driven by the data, according to the set automatic layout, the same instance modules can be generated in batches.
Now through the component container function, users are more efficient and flexible when building visualization projects:
Personalized customization: Users can easily complete the splicing of custom components by simply dragging and dropping. It can meet the needs of users with diversified and customized components, and enrich the application scenarios of large screens.
Batch generation: Through the data-driven mode, we have realized the ability to generate the same instance modules according to the set automatic layout and batch rendering, meeting the needs of multi-module repeated components and combination display.
Cost reduction and efficiency increase: Through unified access to data sources, data distribution is completed, and there is no need to perform data source access and style configuration for each component, greatly reducing data access and subsequent maintenance costs.
Flexible configuration: Any instance in the component container has the ability to customize the interaction configuration with the inside and outside. You can freely select specific instance items for interactive operation, thereby enhancing the flexibility of interactive configuration.
Three or four steps
The realization of this function only needs four steps:
Step 1: Click on the component container to make preliminary style adjustments;
Step 2: Custom stitching and style preview;
Step 3: Data distribution logic and data configuration;
Step 4: Customize the interaction configuration.
The overall steps are consistent with the previous component configuration, except that there are three more steps: entering the [edit page] from [component container], [custom splicing in the edit page], and distribution and access of [select data source type]. But in practical application, it can increase the overall construction efficiency by nearly 10 times~
In particular, in the process of [Data Distribution Logic and Data Configuration], you need to pay attention to the following configuration process:
① Raw data: to be distributed to the title and flop components.
②Custom component identification: Customize the input identification for the title and card flipper.
③Data processing: processed by the filter into a standard data format.
④Data distribution: complete data distribution, data-driven multi-instance generation (three data, complete three instances)
To sum up, the component container is in the form of custom "building block assembly", which not only makes the repeated component construction more flexible and data access more convenient, but also enriches more functions such as traffic vehicle monitoring, warehouse equipment management, sales order management, water conservancy Complex visualization scenarios such as engineering construction and e-commerce data kanban.
Still want to know more feature details? Click on the "Component Container" operation guide
: https://easyv.cloud/help/docs/vhbm0z4l5ser9026.html to enter the help document, which contains a variety of materials such as case demos. It only takes 3 minutes to get started quickly.