UI (User Interface) modular deployment system and establishment method thereof

Through the module configuration system module configurator and rendering engine and other components, the problem of low user interface development efficiency is solved, and flexible interface construction and efficient project development are realized.

CN119002888APending Publication Date: 2024-11-22SHANGHAI MIDU INFORMATION TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410953021.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-16
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

In the prior art, user interface development efficiency is low and interface construction is not flexible enough, resulting in a decrease in project development speed and delivery quality.

Method used

Provides a UI modular provisioning system, including a module configurator, module rendering engine, data binding and event processing unit, state management unit, performance optimization and monitoring unit, and automatically layout and responsive by selecting and configuring predefined modules. Design and render the UI interface corresponding to the actual application scenario.

Benefits of technology

It improves development efficiency, enables developers to efficiently and flexibly build user interfaces, accelerates the development speed and delivery quality of projects, and effectively improves the development efficiency of UI modular provisioning systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119002888A_ABST
    Figure CN119002888A_ABST
Patent Text Reader

Abstract

According to the UI modular deployment system and the building method and device thereof, automatic layout and responsive design are carried out by selecting and configuring predefined modules, so that an actual UI corresponding to an actual application scene is rendered, the development efficiency can be improved, and the development cost is reduced. And developers can construct the user interface more efficiently and flexibly, and the development speed and delivery quality of the project are accelerated, so that the development efficiency of the UI modular deployment system is effectively improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a UI modular deployment system and a construction method thereof. Background Art

[0002] In the prior art, the system user interface (UI) refers to the overall design of the human-computer interaction, operation logic, and interface aesthetics of the software. The user interface is the medium for interaction and information exchange between the system and the user, which realizes the conversion between the internal form of information and the form acceptable to humans; the user interface is the relevant software designed between the user and the hardware for mutual communication, and the purpose is to enable the user to conveniently and efficiently operate the hardware to achieve two-way interaction and complete the work that the hardware is expected to complete. The user interface is widely defined, including human-computer interaction and graphical user interface. There are user interfaces in all fields that participate in information exchange between humans and machines. A good UI design not only makes the software personalized and tasteful, but also makes the operation of the software comfortable, simple, free, and fully reflects the positioning and characteristics of the software. At present, the development efficiency of the user interface is poor, and the construction of the user interface is not flexible enough, which makes the development speed and delivery quality of the project low. Summary of the invention

[0003] One purpose of the present application is to provide a UI modular deployment system and a construction method thereof, which performs automatic layout and responsive design by selecting and configuring pre-defined modules, thereby rendering an actual UI interface corresponding to the actual application scenario. This not only improves development efficiency, but also enables developers to build user interfaces more efficiently and flexibly, speeds up project development speed and delivery quality, and effectively improves the development efficiency of the UI modular deployment system.

[0004] According to one aspect of the present application, a UI modular deployment system is provided, wherein the system includes: a module configurator, a module rendering engine, a data binding and event processing unit, a state management unit, a performance optimization and monitoring unit, wherein:

[0005] The module configurator is used to allow developers to select and configure modules and perform automatic layout and responsive design;

[0006] The module rendering engine is used to render the configured modules into an actual UI interface;

[0007] The data binding and event processing unit is used to bind the attributes of the configured module to the data source of the actual application scenario, and is also responsible for processing the interaction events generated by the user on the actual UI interface, and passing the interaction events to the corresponding module or component for processing;

[0008] The state management unit is used to manage the global state of the system and the interaction of states between configured modules, and is responsible for data interaction and communication between different modules;

[0009] The performance optimization and monitoring unit is used for code splitting, lazy loading and caching of the system, and is responsible for collecting and analyzing the operation data of the system.

[0010] Furthermore, in the above system, the module configurator is used to:

[0011] Through the provided visual interface, developers are allowed to select, adjust the size and position of modules and modify the properties of configured modules, and perform automatic layout and responsive design for configured modules on different designs and screen sizes.

[0012] Furthermore, in the above system, the module rendering engine is used to:

[0013] Analyze the configuration information of the configured module, convert the configuration information into actual HTML, CSS and JavaScript codes, load and render the actual HTML, CSS and JavaScript codes to form an actual UI interface.

[0014] Furthermore, in the above system, the state management unit is used to:

[0015] Manage the interaction between the global state of the system and the states of the configured modules through the state management library to ensure the consistency and predictability of the states of the system and the configured modules;

[0016] Coordinate data interaction and communication between different modules to ensure collaborative work between modules.

[0017] Furthermore, in the above system, the system also includes:

[0018] Module library, which is used to centrally store and manage all modules. Each module is independent and reusable. Each module includes at least one UI component, which is a preset standard component or a scenario component customized according to the business scenario.

[0019] Code reuse units are used to divide different UI components into independent modules. Each module is responsible for handling corresponding user interface elements or interaction logic, so that developers can reuse the module in different projects, pages or functions.

[0020] A construction unit, configured to deploy one or more modules according to an actual application scenario to construct a user interface corresponding to the actual application scenario;

[0021] The maintenance unit is used to locate the corresponding problem module or the module to be modified for repair when a problem occurs or the function of the module to be modified.

[0022] According to another aspect of the present application, a method for building a UI modular deployment system is also provided, wherein the method includes:

[0023] Split the UI interface corresponding to the actual application scenario into at least one module, each module is used to process a single function corresponding to each module; create at least one reusable atomic component and a composite component formed by any combination thereof according to the actual application scenario to form a component library corresponding to the actual application scenario, wherein each module is composed of one or more components;

[0024] Managing the status of components in the component library, transferring data between components, and processing the interaction and communication between components through events;

[0025] Split the source code corresponding to the actual application scenario into sub-codes corresponding to each module, and use lazy loading to delay loading for non-critical modules or components;

[0026] Call the front-end framework to support the development and construction of various modules and component libraries corresponding to the actual application scenarios;

[0027] Package and optimize each module corresponding to the actual application scenario, and continuously integrate or deploy the sub-code corresponding to each module;

[0028] Unit testing, integration testing and audit testing are performed on each module and each component corresponding to the actual application scenario to form a UI modular deployment system corresponding to the actual application scenario.

[0029] Furthermore, in the above method, managing the status of components in the component library, transferring data between components, and processing the interaction and communication between components through events include:

[0030] Use state management tools such as Redux or Vuex to manage the state of each component in the component library;

[0031] Pass data from the parent component in the component library to the corresponding child component through the component's properties;

[0032] Interaction and communication between components are handled through events.

[0033] Furthermore, in the above method, the front-end framework includes a React front-end framework, a Vue front-end framework and an Angular front-end framework.

[0034] Furthermore, in the above method, the modules and components corresponding to the actual application scenario are subjected to unit testing, integration testing and audit testing respectively to form a UI modular deployment system corresponding to the actual application scenario, including:

[0035] Perform unit tests on each module and each component corresponding to the actual application scenario;

[0036] Conduct integration testing on the entire system of the actual application scenario to ensure the coordination between modules;

[0037] The entire system, modules and components of the actual application scenario are code reviewed to form a UI modular deployment system corresponding to the actual application scenario.

[0038] Furthermore, in the above method, the method further comprises:

[0039] Monitor and log the UI modular deployment system corresponding to the actual application scenario that has been built;

[0040] Continuously optimize and iterate the system based on monitoring results and log records.

[0041] Compared with the prior art, the present application provides a UI modular deployment system, wherein the system includes: a module configurator, a module rendering engine, a data binding and event processing unit, a state management unit, and a performance optimization and monitoring unit, wherein the module configurator is used to allow developers to select and configure modules and perform automatic layout and responsive design; the module rendering engine is used to render the configured modules into an actual UI interface; the data binding and event processing unit is used to bind the properties of the configured modules to the data source of the actual application scenario, and is also responsible for processing the interaction events generated by the user on the actual UI interface, and passing the interaction events to the corresponding modules or components for processing; the state management unit is used to manage the interaction between the global state of the system and the states of the configured modules, and is responsible for data interaction and communication between different modules; the performance optimization and monitoring unit is used for code splitting, lazy loading and caching of the system, and is responsible for collecting and analyzing the operation data of the system. By selecting and configuring pre-defined modules for automatic layout and responsive design, the actual UI interface corresponding to the actual application scenario can be rendered, which not only improves development efficiency, but also enables developers to build user interfaces more efficiently and flexibly, speeding up project development and delivery quality, thereby effectively improving the development efficiency of the UI modular deployment system. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Other features, objects and advantages of the present application will become more apparent by reading the detailed description of non-limiting embodiments made with reference to the following drawings:

[0043] Figure 1 A schematic diagram showing a system framework of a UI modular deployment system according to one aspect of the present application is shown;

[0044] Figure 2 A schematic diagram showing a process of building a UI modular deployment system according to one aspect of the present application;

[0045] Figure 3 A detailed flow chart of a method for building a UI modular deployment system according to one aspect of the present application is shown.

[0046] The same or similar reference numerals in the drawings represent the same or similar components. DETAILED DESCRIPTION

[0047] The present application is described in further detail below in conjunction with the accompanying drawings.

[0048] In a typical configuration of the present application, the terminal, the device of the service network and the trusted party all include one or more processors (CPU), input / output interfaces, network interfaces and memories.

[0049] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0050] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include non-transitory media such as modulated data signals and carrier waves.

[0051] like Figure 1 As shown, Figure 1A schematic diagram of a system framework of a UI modular deployment system proposed in one aspect of the present application, the system can be implemented using HTML hypertext markup language, JavaScript programming language and CSS content service exchanger, wherein the system includes: a module configurator, a module rendering engine, a data binding and event processing unit, a state management unit, a performance optimization and monitoring unit, wherein:

[0052] The module configurator is used to allow developers to select and configure modules and perform automatic layout and responsive design;

[0053] The module rendering engine is used to render the configured modules into an actual UI interface;

[0054] The data binding and event processing unit is used to bind the properties of the configured modules to the data source of the actual application scenario, and is also responsible for processing the interaction events generated by the user on the actual UI interface, and passing the interaction events to the corresponding modules or components for processing; here, the data binding and event processing unit allows developers to bind the properties of each configured module to the data source corresponding to the actual application scenario. When the data source corresponding to the actual application scenario changes, the properties of the corresponding module will also be automatically updated; the data binding and event processing unit is also responsible for processing the interaction events generated by the user on the actual UI interface, such as click, slide and other events, and passing the interaction events generated by the user to the corresponding modules or components for processing.

[0055] The state management unit is used to manage the global state of the system and the interaction of states between configured modules, and is responsible for data interaction and communication between different modules;

[0056] The performance optimization and monitoring unit is used for code splitting, lazy loading and caching of the system, and is responsible for collecting and analyzing the operation data of the system. Here, the performance optimization strategy in the performance optimization and monitoring unit includes techniques such as code splitting, lazy loading, caching, etc. to improve the loading speed and response performance of the system; the performance optimization and monitoring unit is also responsible for collecting and analyzing the operation data of the system, such as loading time, memory usage, etc., so as to timely discover and solve performance problems.

[0057] In a UI modular deployment system provided in an embodiment of the present application, automatic layout and responsive design are performed by selecting and configuring pre-defined modules, thereby rendering an actual UI interface corresponding to the actual application scenario. This not only improves development efficiency, but also enables developers to build user interfaces more efficiently and flexibly, speeds up project development speed and delivery quality, and effectively improves the development efficiency of the UI modular deployment system.

[0058] Following the above embodiment of the present application, the module configurator is used to:

[0059] Through the provided visual interface, developers are allowed to select, adjust the size and position of modules and modify the properties of configured modules, and perform automatic layout and responsive design for configured modules on different designs and screen sizes.

[0060] Here, the module configurator is a tool that allows developers to select and configure modules. By providing a visual interface, developers can drag and adjust the size and position of the selected modules, as well as modify the properties of the configured modules, thereby realizing the selection and customized design of modules; the module configurator also has the functions of automatic layout and responsive design, which can realize the adjustment and layout of the configured modules on different designs and screen sizes, thereby ensuring that the configured modules can be well displayed on different designs and screen sizes.

[0061] Following the above embodiment of the present application, the module rendering engine is used to:

[0062] Analyze the configuration information of the configured modules, convert the configuration information into actual HTML, CSS and JavaScript codes, load and render the actual HTML, CSS and JavaScript codes to form an actual UI interface. The module rendering engine is responsible for rendering the configured modules into an actual UI interface. It needs to parse the configuration information of each module and convert the parsed configuration information into actual HTML, CSS and JavaScript codes; then, through the efficient rendering capabilities of the module rendering engine, load and render the actual HTML, CSS and JavaScript codes to form an actual UI interface, so as to ensure that the UI interface can be quickly loaded and updated.

[0063] Following the above embodiment of the present application, the state management unit is used to:

[0064] Manage the interaction between the global state of the system and the states of the configured modules through the state management library to ensure the consistency and predictability of the states of the system and the configured modules;

[0065] Coordinate data interaction and communication between different modules to ensure collaborative work between modules.

[0066] Here, the state management unit manages the interaction between the global state in the system and the states of the configured modules, which is usually implemented through a state management library (such as Redux, Vuex, etc.) to ensure the consistency and predictability of the states of the system and the configured modules; the state management unit is also responsible for coordinating data interaction and communication between different modules to ensure that the modules can work together.

[0067] like Figure 1 As shown, a UI modular deployment system proposed in one aspect of the present application also includes: a tool and auxiliary facility unit, which provides a code editor to build development tools such as tool debuggers to improve development efficiency and quality; the auxiliary facilities in the tool and auxiliary facility unit include but are not limited to version control, continuous integration or deployment, etc., to ensure version management and automated deployment of code.

[0068] Furthermore, a UI modular deployment system proposed in one aspect of the present application also includes: documentation and community support to provide detailed module documentation and instructions for use to facilitate developers to understand and use the module, and regularly organize training or sharing sessions to allow developers to understand the latest development techniques and optimization methods.

[0069] like Figure 1 As shown, a UI modular deployment system proposed in one aspect of the present application also includes:

[0070] A module library is a library used to centrally store and manage all modules. Each module is independent and reusable. Each module includes at least one UI component, which is a preset standard component or a scenario component customized according to the business scenario. The module library is a library that centrally stores and manages all modules. Each module is independent and reusable. The module library needs to have a good classification and indexing system to facilitate developers to quickly find the required modules. The modules in the module library can be formed by pre-designed standard components or scenario components customized for specific business scenarios.

[0071] The code reuse unit is used to divide different UI components into independent modules, each module is responsible for processing corresponding user interface elements or interaction logic, so that developers can reuse the module in different projects, pages or functions; the code reuse unit divides the UI modular deployment system into different modules, each module is formed by different UI components, each module is responsible for processing corresponding user interface elements or interaction logic, allowing developers to reuse these modules in different projects, pages or functions, avoiding repeated code writing, thereby improving development efficiency.

[0072] The construction unit is used to deploy one or more modules according to the actual application scenario to build a user interface corresponding to the actual application scenario; since the modules are pre-defined and developed, developers can quickly combine and deploy one or more pre-defined modules to build a user interface corresponding to the actual application scenario. This rapid construction capability can shorten the development cycle and speed up the progress of the project.

[0073] The maintenance unit is used to locate the corresponding problem module or the module to be modified for repair when a problem occurs or the function of the module needs to be modified; since the modular structure makes the code clearer and easier to understand, when a problem occurs or the function of the module needs to be modified, the developer can more easily locate the relevant module, reducing the time to find and fix the problem. In addition, the modular structure also reduces the coupling between codes, making the code easier to modify and maintain.

[0074] like Figure 1 As shown, one aspect of the present application proposes a UI modular deployment system that also has a team collaboration function. The system supports multiple developers to work on different modules at the same time, thereby improving the efficiency of team collaboration. Each developer can focus on the module he is responsible for without worrying about the code of other parts. This division of labor and cooperation can speed up the development of the project. Furthermore, the system also has an extensibility function. Since the system supports the addition of new modules and functions, it has good extensibility. When project requirements change, developers can easily add new modules to meet these requirements without making large-scale modifications to the entire code base.

[0075] In the above-mentioned embodiments of the present application, the development efficiency is improved through code reuse units, rapid construction of construction units, maintenance units that are easy to maintain the system, team collaboration functions and scalability functions, so that developers can build user interfaces more efficiently and flexibly, thereby accelerating the development speed and delivery quality of the project.

[0076] like Figure 2 As shown, it is a flow chart of a method for building a UI modular deployment system proposed in another aspect of the present application, wherein the method can be implemented using HTML hypertext markup language, JavaScript programming language and CSS content service exchanger, and the method sequentially includes the following steps: well-designed module architecture, component development, data-driven design, asynchronous loading and performance optimization, use of modern front-end frameworks, modular construction and deployment, test quality assurance, monitoring and logging, and continuous optimization and iteration, wherein, Figure 2 The process diagram in the figure is specifically embodied as follows: Figure 3 The detailed flow diagram shown in the figure specifically includes steps S11, S12, S13, S14, S15 and S16, and the specific steps are as follows:

[0077] Step S11, split the UI interface corresponding to the actual application scenario into at least one module, each module is used to process its corresponding single function; create at least one reusable atomic component and a composite component formed by any combination of the atomic component and any combination thereof according to the actual application scenario to form a component library corresponding to the actual application scenario, wherein each module is composed of one or more components.

[0078] In step S11, it is necessary to clarify the required modules and the responsibilities of each module according to the actual application scenario, that is, each module should have clear responsibilities and definitions, and follow the single responsibility principle; modular decomposition is also required to split the complex UI interface into multiple modules, each module handles a part of the corresponding functions; and use dependency injection or dependency management frameworks to reduce coupling between modules, implement dependency management, and then design a module architecture that fits the actual application scenario well. In order to adapt to the actual application scenario, component development is required, in which reusable atomic components such as buttons, input boxes, cards, etc. can be created; one or more atomic components are combined to form more complex composite components or pages; a component library is established and maintained based on atomic components and composite components to facilitate developers to quickly select and use components.

[0079] Step S12, managing the status of components in the component library, transferring data between components, and processing the interaction and communication between components through events.

[0080] Step S13, split the source code corresponding to the actual application scenario into sub-codes corresponding to each module, and use lazy loading to delay loading for non-critical modules or components; here, it is necessary to implement asynchronous loading and performance optimization, such as using packaging tools such as Webpack to split the source code corresponding to the actual application scenario into multiple modules, which not only realizes code splitting, but also realizes on-demand loading; for non-critical modules or components, lazy loading can be used for delayed loading, thereby realizing lazy loading; performance monitoring tools are also used to analyze and optimize the performance of the system.

[0081] Step S14, calling the front-end framework to support the development and construction of each module and component library corresponding to the actual application scenario. Here, the front-end framework includes but is not limited to the React front-end framework, the Vue front-end framework and the Angular front-end framework, wherein the React front-end framework uses modern front-end frameworks such as React, which provides strong support for component-based development; the Vue front-end framework is a popular front-end framework, which provides an intuitive and easy-to-understand component system; the Angular front-end framework is a better choice for large-scale enterprise-level applications.

[0082] Step S15, packaging and optimizing each module corresponding to the actual application scenario, and continuously integrating or deploying the sub-code corresponding to each module to achieve modular construction and deployment, wherein construction tools such as Webpack and Rollup are used to package and optimize each module, and a continuous integration or deployment process is set to ensure the quality of the code and automated deployment.

[0083] Step S16, performing unit testing, integration testing and audit testing on each module and each component corresponding to the actual application scenario, so as to form a UI modular deployment system corresponding to the actual application scenario.

[0084] Through the above steps S11 to S16, the development efficiency of the UI modular deployment system can be effectively improved through comprehensive optimization in multiple aspects such as module division, component development, performance optimization, asynchronous loading and performance optimization, use of modern front-end frameworks, modular construction and deployment, test quality assurance, monitoring and logging, and continuous optimization and iteration.

[0085] Following the above embodiment of the present application, the step S12 manages the status of the components in the component library, transfers data between components, and processes the interaction and communication between components through events, including:

[0086] Use state management tools such as Redux or Vuex to manage the state of each component in the component library and implement state management of components under data-driven design;

[0087] Through the properties of the component (such as props, etc.), data is passed from the parent component in the component library to the corresponding child component to achieve property transfer under data-driven design;

[0088] Use events (such as events, etc.) to handle interactions and communications between components and implement event responses under data-driven design.

[0089] Following the above embodiment of the present application, the step S16 performs unit testing, integration testing and audit testing on each module and each component corresponding to the actual application scenario to form a UI modular deployment system corresponding to the actual application scenario, including:

[0090] Write unit tests for each module and component corresponding to the actual application scenario to ensure the correctness of the functions of each module and component;

[0091] Conduct integration testing on the entire system of the actual application scenario to ensure the coordination between modules;

[0092] Set up a code review and automated testing process to conduct code review and testing on the entire system, modules and components of the actual application scenario to form a UI modular deployment system corresponding to the actual application scenario, thereby ensuring the overall code quality.

[0093] Following the above embodiment of the present application, another aspect of the present application provides a method for building a UI modular deployment system, which further includes:

[0094] Monitor and log the UI modular deployment system corresponding to the actual application scenario that has been built;

[0095] Continuously optimize and iterate the system based on monitoring results and log records.

[0096] Here, log recording and error tracking tools are used to monitor the operating status of the UI modular deployment system corresponding to the actual application scenario formed. User operations, performance data and other information are recorded in the form of logs for analysis and optimization. At the same time, user feedback is collected in the form of logs to understand user usage habits and needs. The system is continuously optimized and iterated based on user feedback and data analysis results (such as monitoring results and log records), so as to improve the UI modular deployment system corresponding to the actual application scenario formed.

[0097] In summary, the present application provides a UI modular deployment system, wherein the system includes: a module configurator, a module rendering engine, a data binding and event processing unit, a state management unit, and a performance optimization and monitoring unit, wherein the module configurator is used to allow developers to select and configure modules and perform automatic layout and responsive design; the module rendering engine is used to render the configured modules into an actual UI interface; the data binding and event processing unit is used to bind the properties of the configured modules to the data source of the actual application scenario, and is also responsible for processing the interaction events generated by the user on the actual UI interface, and passing the interaction events to the corresponding modules or components for processing; the state management unit is used to manage the interaction between the global state of the system and the states of the configured modules, and is responsible for data interaction and communication between different modules; the performance optimization and monitoring unit is used for code splitting, lazy loading and caching of the system, and is responsible for collecting and analyzing the operation data of the system. By selecting and configuring pre-defined modules for automatic layout and responsive design, the actual UI interface corresponding to the actual application scenario can be rendered, which not only improves development efficiency, but also enables developers to build user interfaces more efficiently and flexibly, speeding up project development and delivery quality, thereby effectively improving the development efficiency of the UI modular deployment system.

[0098] It should be noted that the present application can be implemented in software and / or a combination of software and hardware, for example, can be implemented using an application specific integrated circuit (ASIC), a general purpose computer or any other similar hardware device. In one embodiment, the software program of the present application can be executed by a processor to implement the steps or functions described above. Similarly, the software program of the present application (including relevant data structures) can be stored in a computer-readable recording medium, for example, a RAM memory, a magnetic or optical drive or a floppy disk and similar devices. In addition, some steps or functions of the present application can be implemented using hardware, for example, as a circuit that cooperates with a processor to perform each step or function.

[0099] In addition, a part of the present application may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present application through the operation of the computer. The program instruction for calling the method of the present application may be stored in a fixed or removable recording medium, and / or transmitted through a data stream in a broadcast or other signal-bearing medium, and / or stored in a working memory of a computer device that runs according to the program instruction. Here, according to an embodiment of the present application, a device is included, the device including a memory for storing computer program instructions and a processor for executing program instructions, wherein, when the computer program instruction is executed by the processor, the device is triggered to run the method and / or technical solution based on the aforementioned multiple embodiments according to the present application.

[0100] It is obvious to those skilled in the art that the present application is not limited to the details of the above exemplary embodiments, and that the present application can be implemented in other specific forms without departing from the spirit or basic features of the present application. Therefore, from any point of view, the embodiments should be regarded as exemplary and non-restrictive, and the scope of the present application is limited by the attached claims rather than the above description, so it is intended to include all changes that fall within the meaning and scope of the equivalent elements of the claims in the present application. Any figure mark in the claims should not be regarded as limiting the claims involved. In addition, it is obvious that the word "comprising" does not exclude other units or steps, and the singular does not exclude the plural. Multiple units or devices stated in the device claim can also be implemented by one unit or device through software or hardware. The words first, second, etc. are used to indicate names, and do not indicate any particular order.

Claims

1. A UI modular deployment system, wherein: The system includes: a module configurator, a module rendering engine, a data binding and event processing unit, a state management unit, a performance optimization and monitoring unit, wherein: The module configurator is used to allow developers to select and configure modules and perform automatic layout and responsive design; The module rendering engine is used to render the configured modules into an actual UI interface; The data binding and event processing unit is used to bind the attributes of the configured module to the data source of the actual application scenario, and is also responsible for processing the interaction events generated by the user on the actual UI interface, and passing the interaction events to the corresponding module or component for processing; The state management unit is used to manage the global state of the system and the interaction of states between configured modules, and is responsible for data interaction and communication between different modules; The performance optimization and monitoring unit is used for code splitting, lazy loading and caching of the system, and is responsible for collecting and analyzing the operation data of the system.

2. The system according to claim 1, wherein: The module configurator is used to: Through the provided visual interface, developers are allowed to select, adjust the size and position of modules and modify the properties of configured modules, and perform automatic layout and responsive design for configured modules on different designs and screen sizes.

3. The system according to claim 1, wherein: The module rendering engine is used to: Analyze the configuration information of the configured module, convert the configuration information into actual HTML, CSS and JavaScript codes, load and render the actual HTML, CSS and JavaScript codes to form an actual UI interface.

4. The system according to claim 1, wherein: The state management unit is used for: Manage the interaction between the global state of the system and the states of the configured modules through the state management library to ensure the consistency and predictability of the states of the system and the configured modules; Coordinate data interaction and communication between different modules to ensure collaborative work between modules.

5. The system according to claim 1, wherein: The system also includes: Module library, which is used to centrally store and manage all modules. Each module is independent and reusable. Each module includes at least one UI component, which is a preset standard component or a scenario component customized according to the business scenario. Code reuse units are used to divide different UI components into independent modules. Each module is responsible for handling corresponding user interface elements or interaction logic, so that developers can reuse the module in different projects, pages or functions. A construction unit, configured to deploy one or more modules according to an actual application scenario to construct a user interface corresponding to the actual application scenario; The maintenance unit is used to locate the corresponding problem module or the module to be modified for repair when a problem occurs or the function of the module to be modified.

6. A method for building a UI modular deployment system, wherein: The method includes: Split the UI interface corresponding to the actual application scenario into at least one module, each module is used to process a single function corresponding to each module; create at least one reusable atomic component and a composite component formed by any combination thereof according to the actual application scenario to form a component library corresponding to the actual application scenario, wherein each module is composed of one or more components; Managing the status of components in the component library, transferring data between components, and processing the interaction and communication between components through events; Split the source code corresponding to the actual application scenario into sub-codes corresponding to each module, and use lazy loading to delay loading for non-critical modules or components; Call the front-end framework to support the development and construction of various modules and component libraries corresponding to the actual application scenarios; Package and optimize each module corresponding to the actual application scenario, and continuously integrate or deploy the sub-code corresponding to each module; Unit testing, integration testing and audit testing are performed on each module and each component corresponding to the actual application scenario to form a UI modular deployment system corresponding to the actual application scenario.

7. The method according to claim 6, wherein: The management of the status of components in the component library, the transmission of data between components, and the interaction and communication between components through event processing include: Use state management tools such as Redux or Vuex to manage the state of each component in the component library; Pass data from the parent component in the component library to the corresponding child component through the component's properties; Interaction and communication between components are handled through events.

8. The method according to claim 6, wherein: The front-end frameworks include React front-end framework, Vue front-end framework and Angular front-end framework.

9. The method according to claim 1, wherein: The unit test, integration test and audit test are respectively performed on each module and each component corresponding to the actual application scenario to form a UI modular deployment system corresponding to the actual application scenario, including: Perform unit tests on each module and each component corresponding to the actual application scenario; Conduct integration testing on the entire system of the actual application scenario to ensure the coordination between modules; The entire system, modules and components of the actual application scenario are code reviewed to form a UI modular deployment system corresponding to the actual application scenario.

10. The method according to claim 6, wherein: The method further comprises: Monitor and log the UI modular deployment system corresponding to the actual application scenario that has been built; Continuously optimize and iterate the system based on monitoring results and log records.