Visual business assembly component and real-time interface rendering engine interaction method and system

The interaction of visual business assembly components with a real-time interface rendering engine addresses inefficiencies in traditional software development by enabling rapid, synchronized updates and scalable, maintainable systems accessible to non-technical users.

CN118796178BActive Publication Date: 2024-12-03ZHEJIANG RURAL COMMERCIAL DIGITAL TECH CO LTD
View PDF 11 Cites 0 Cited by

Patent Information

Application Number
CN202411274123.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-09-12
Publication Date
2024-12-03
Estimated Expiration
2044-09-12

AI Technical Summary

Technical Problem

Traditional software development processes are inefficient, require deep programming skills, lead to asynchronous updates between front-end and back-end, and struggle with maintainability and scalability, failing to adapt quickly to market changes and user needs.

Method used

A method and system for interacting visual business assembly components with a real-time interface rendering engine, involving classified storage of components and logic modules, real-time feedback, drag-and-drop interaction, and optimization devices to enhance smoothness and collaboration.

Benefits of technology

This approach lowers the technical threshold, enables rapid prototyping and iterative updates, reduces resource waste, and enhances maintainability and scalability, allowing non-technical users to participate in software development and ensuring synchronized updates between interface and logic.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118796178B_ABST
    Figure CN118796178B_ABST
Patent Text Reader

Abstract

The present invention proposes a method and system for visual business assembly components and real-time interface rendering engine interaction, wherein the visual assembly components and real-time interface rendering engine interaction system includes a component import device, a component design device, a logic module design device, and an integration device. The present invention is to deal with the low efficiency and high technical threshold in the software development process. It makes the construction of business logic and interface design simple and easy to understand through an intuitive visual interface, thereby greatly reducing the technical threshold and allowing operators with non-technical backgrounds to easily participate in software development.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of software development, and in particular to the field of interaction between a visual assembly component and a real-time interface rendering engine. Background Art

[0002] In the traditional model of software development, project development follows a strict linear process from requirements analysis, design, coding, testing to deployment. Although this lifecycle management ensures the systematicness and rigor of the development process, it also leads to the extension of the development cycle and the increase of costs. At the same time, it needs to rely on the participation of a large number of professional and technical personnel, requiring developers to have deep programming skills, which limits the participation of business parties and designers because they lack sufficient programming background to directly realize their ideas. In addition, the existing technology has deficiencies in achieving synchronous updates of the front-end interface and the back-end business logic, resulting in the update of the user interface often lagging behind the change of the back-end logic, which not only affects the user experience, but also increases the complexity of communication and collaboration between front-end and back-end developers. With the rapid changes in the market environment, user needs are becoming increasingly diversified and personalized, and products need to be iterated quickly to adapt to the market, but the slow pace of the traditional development process often cannot keep up with the pace of the market, resulting in the product missing promotion opportunities. In terms of resource utilization, there is a significant waste of resources in the traditional development model, and a lot of time and manpower are invested in repetitive coding and debugging work, which could have been reduced through more efficient tools and methods. Finally, with the rapid development of technology, existing systems are facing problems of maintainability and scalability. Many systems do not consider the possibility of future demand changes in the early design process, which makes it difficult to adapt to new requirements during product iteration. In summary, although existing technologies have made certain achievements in the field of software development, they still face many challenges and limitations. An innovative method is urgently needed to break bottlenecks, improve efficiency, lower barriers, and meet rapidly changing market needs. Summary of the invention

[0003] The present invention proposes a method and system for interaction between a visual business assembly component and a real-time interface rendering engine, which is used to solve the problems of high threshold for use of traditional technologies, long development cycle, cumbersome operation process and waste of resources. The technical solutions adopted are as follows:

[0004] A method for interacting a visual business assembly component with a real-time interface rendering engine, the method comprising:

[0005] S1: According to the different types of components and logic modules, corresponding component libraries and logic module libraries are established to realize classified storage of components and logic modules;

[0006] S2: Set up property editors for component libraries and logic module libraries, bind them to data models, and provide real-time feedback to users through preview windows;

[0007] S3: Through the interactive model, components and logic modules are moved to the design area by dragging, so that the edited components and edited logic modules can interact in real time;

[0008] S4: Add optimization devices to optimize the smoothness of the interaction between components and logic modules, so as to achieve smooth interaction between components and design areas, logic modules and design areas, and components and logic modules.

[0009] Preferably, the S1 includes:

[0010] S11: According to different types of components, the component library is divided into a graphic component library, an interactive component library and an animation effect component library;

[0011] S12: According to different types of logic modules, the logic modules are divided into a rendering control module, an interactive logic module, and a real-time data update module.

[0012] The S2 includes:

[0013] S21: setting a corresponding property editor according to each component library and logic module library, and collecting user input through a form;

[0014] S22: Bind the form of the property editor to the data model of the component and logic module, and establish a real-time connection between the data model of the component and logic module and the preview window, so that while the property is being edited, the display of the corresponding component in the design area is updated in real time and displayed to the user through the preview window.

[0015] Preferably, the interaction between the components and logic modules and the design area includes:

[0016] A: Introduce a drag library, and apply the drag source wrapper provided by the drag library to the component or logic module to make the component or logic module draggable;

[0017] B: Set the placement area wrapper in the design area and define the entire design area as the placement area;

[0018] C: Drag a component or logic module with the mouse. After the component or logic module is dragged to the design area as the mouse is moved horizontally, the mouse is released, and the component or logic module completes the interaction with the design area.

[0019] Preferably, S3 includes:

[0020] S31: Create an application programming interface for the component, define a custom event that the component needs to trigger, and transmit data changes to the logic module through the application programming interface;

[0021] S32: creating an application programming interface of the logic module, receiving data from the component, and transmitting the return results and triggering events of the logic module;

[0022] S33: In the main interface, combine the components and logic modules together to form a complete module.

[0023] Preferably, the S4 includes:

[0024] S41: Establish unit test modules to test components and logic modules and ensure that components and logic modules work as expected;

[0025] S42: Establish an integration test module to test the interaction between components and logic modules, and ensure that the interaction between components and logic modules is smooth;

[0026] S43: Establish an end-to-end testing module, simulate user operations, test the entire system process, and ensure the smoothness of the entire process.

[0027] A visual business assembly component and a real-time interface rendering engine interaction system, the system comprising:

[0028] Component library and logic module library: According to the different types of components and logic modules, corresponding component libraries and logic module libraries are established to realize classified storage of components and logic modules;

[0029] Area design module: Set up property editors for component libraries and logic module libraries, bind them to data models, and provide real-time feedback to users through preview windows;

[0030] Interactive device: through the interactive model, components and logic modules can be moved to the design area by dragging, so that the edited components and edited logic modules can interact in real time;

[0031] Optimization device: Add optimization device to optimize the smoothness of the interaction between components and logic modules, so as to achieve smooth interaction between components and design areas, logic modules and design areas, and components and logic modules.

[0032] Preferably, the area design module includes:

[0033] Property editor: Set up corresponding property editors according to each component library and logic module library, and collect user input through forms;

[0034] Real-time synchronization device: binds the form of the property editor to the data model of the component and logic module, and establishes a real-time connection between the data model of the component and logic module and the preview window, so that while the properties are edited, the display of the corresponding component in the design area is updated in real time and displayed to the user through the preview window.

[0035] Preferably, the interaction device comprises:

[0036] Component API: Create the component API, define the custom events that the component needs to trigger, and transmit data changes to the logic module through the API;

[0037] Application programming interface of logic module: Create the application programming interface of logic module, receive data from components, and transmit the return results and trigger events of logic module;

[0038] Integrated device: In the main interface, combine components and logic modules together to form a complete module.

[0039] Preferably, the optimization device comprises:

[0040] Unit test module: Establish unit test modules to test components and logic modules and ensure that components and logic modules work as expected;

[0041] Integration test module: Establish an integration test module to test the interaction between components and logic modules, and ensure smooth interaction between components and logic modules;

[0042] End-to-end testing module: Establish an end-to-end testing module to simulate user operations, test the entire system process, and ensure the smoothness of the entire process;

[0043] The test optimization device tests the smoothness of the interaction between the visualization component and the logic module and the design area, including:

[0044] Build a test environment similar to the actual situation and record the operation start time and response completion time;

[0045] The response time of each operation is calculated based on the collected operation start time and response completion time. The performance evaluation score is obtained by combining the system throughput and the number of concurrent users. The performance evaluation score formula can be obtained by the following formula:

[0046]

[0047] Where P represents the performance evaluation score, It represents the average throughput actually observed per unit time, M max represents the maximum throughput of the system per unit time, C represents the number of concurrent users actually observed, and C max Indicates the maximum number of concurrent users that the system can stably support. It represents the average value of the response time actually observed per unit time, E min Indicates the minimum acceptable response time per unit time, Emax represents the maximum response time that can be received within a unit time, n represents the total number of unit time periods tested, and the throughput represents the amount of data successfully transmitted by the network within a unit time, and the number of concurrent users represents the number of users who interact with the system at the same time period;

[0048] And the performance evaluation result is obtained according to the performance evaluation strategy combined with the performance evaluation score, wherein the performance evaluation strategy is:

[0049] When 90<P≤100, it means that the system performance is very good, the throughput is close to the maximum value, the number of concurrent users is high, and the response time is very short. The existing system should be maintained to ensure that the system can continue to run efficiently;

[0050] When 50<P≤90, it indicates that there is an abnormal risk in system performance, and an abnormal risk warning is issued to the user;

[0051] When P≤50, it indicates that the system performance is poor, and a poor performance warning is issued to the user.

[0052] Beneficial effects of the present invention: The present invention is to deal with the low efficiency and high technical threshold in the software development process. It makes the construction of business logic and interface design simple and easy to understand through an intuitive visual interface, thereby greatly reducing the technical threshold and allowing operators with non-technical backgrounds to easily participate in software development. In addition, the real-time interface rendering engine of the present invention can ensure that the change of the user interface is synchronized with the update of the business logic, solving the problem of the interface and logic being out of sync. It also responds quickly to changes in market demand through rapid prototyping and iterative updates, thereby improving the flexibility and adaptability of software development. By optimizing the development process, the present invention reduces resource waste, provides a real-time feedback mechanism, and speeds up the design decision-making process. At the same time, it strengthens communication and collaboration among team members through shared visual components and real-time update mechanisms, thereby improving the work efficiency of the team. The modular design and componentized architecture of the present invention enhance the maintainability and scalability of the system, and provide a solid foundation for future product iterations and functional upgrades. Most importantly, the present invention stimulates the innovation potential of the team by lowering the technical threshold and providing a fast iteration environment, thus opening up a new path for innovation and development in the software industry.

[0053] Through this invention, we can achieve breakthroughs in the following aspects:

[0054] 1. Improve development efficiency: Through a visual operation interface, business personnel and designers can directly participate in product construction without writing code, greatly shortening the development cycle.

[0055] 2. Lower the technical threshold: The simplified operation process and intuitive user interface make it easy for people with non-technical backgrounds to get started and participate in software development.

[0056] 3. Realize synchronous update of interface and logic: The real-time interface rendering engine ensures that any changes in business logic can be immediately reflected in the user interface, eliminating the problem of asynchronous front-end and back-end development.

[0057] 4. Rapid response to market demand: The present invention supports rapid iteration, allowing the product to quickly adapt to market changes and user needs.

[0058] 5. Enhanced multi-platform compatibility: The present invention supports instant cross-platform adaptation, simplifying development work on different devices and operating systems.

[0059] 6. Optimize resource allocation: Reduce resource waste in traditional coding and debugging processes, allowing resources to be used more efficiently.

[0060] 7. Enhance the maintainability and scalability of the system: The componentized design makes the system easier to maintain and expand, and adapt to the needs of future product iterations. BRIEF DESCRIPTION OF THE DRAWINGS

[0061] Figure 1 The present invention is a flowchart of the method for interaction between a visual assembly component and a real-time interface rendering engine. DETAILED DESCRIPTION

[0062] The preferred embodiments of the present invention are described below in conjunction with the accompanying drawings. It should be understood that the preferred embodiments described herein are only used to illustrate and explain the present invention, and are not used to limit the present invention.

[0063] One embodiment of the present invention, referring to Figure 1 As shown, a method for interacting a visual business assembly component with a real-time interface rendering engine includes:

[0064] S1: According to the different types of components and logic modules, corresponding component libraries and logic module libraries are established to realize classified storage of components and logic modules;

[0065] S2: Set up property editors for component libraries and logic module libraries, bind them to data models, and provide real-time feedback to users through preview windows;

[0066] S3: Through the interactive model, components and logic modules are moved to the design area by dragging, so that the edited components and edited logic modules can interact in real time;

[0067] S4: Add optimization devices to optimize the smoothness of the interaction between components and logic modules, so as to achieve smooth interaction between components and design areas, logic modules and design areas, and components and logic modules.

[0068] The working principle and effect of the above technical solution are as follows: Visual assembly components allow users to build and arrange through the editor, and users can select and modify component properties through the component panel. These components are usually designed as a low-code development method, that is, the developed components can be dragged and arranged through the editor to complete specific business functions. The assembled components will carry their properties, styles, behaviors and other data. These data will be passed to the real-time interface rendering engine for subsequent rendering and interaction processing. The rendering engine uses the HTML parser to parse the HTML document into a DOM tree, which is the basis for the browser to understand and operate the web page. The CSS parser parses the CSS style and converts it into a CSS object, which is assembled into a CSSOM tree. After the DOM tree and the CSSOM tree are built, the browser will build a rendering tree (RenderTree) based on these two trees, which determines which elements are visible and their style information. After the rendering tree is built, the browser will calculate the size and absolute position of all elements and determine their layout on the page. After the page layout is completed, the browser will convert each node in the rendering tree into pixels and decode all media files to finally generate a visual image result. The real-time interface rendering engine considers the data and properties of components, such as color, size, position, etc., during the rendering process. The rendering engine dynamically adjusts the rendering results according to the properties of the components to achieve real-time visualization. The user's interaction with the component (click, drag, etc.) is also processed by the rendering engine and the rendering results are updated in real time. Visual assembly components allow developers to quickly build pages by dragging, arranging, etc., without having to write a lot of HTML, CSS and JavaScript code, which significantly improves development efficiency. The real-time interface rendering engine can respond immediately to changes in component properties without recompiling or loading the entire page, further speeding up the development iteration. The intuitiveness and ease of use of visual assembly components allow developers to quickly get started even without deep programming knowledge, lowering the threshold for development. The instant feedback of real-time rendering helps developers understand the page effect more intuitively and reduce development troubles caused by code errors or logic problems. The real-time interface rendering engine can convert the properties and behaviors of components into visual interface effects in real time, ensuring that users can immediately see the modified page effect. The real-time interaction support between components and rendering engines makes the page highly interactive. Users can trigger corresponding page changes by operating components, improving the user experience. The flexibility of visual assembly components allows developers to freely combine and modify components as needed to meet different business needs. The scalability of the real-time interface rendering engine allows developers to add new rendering effects and interactive functions as needed to meet the continuous development and changes of the project. The modular design of visual assembly components makes the code structure clear and easy to maintain. When you need to modify or expand the page function, you only need to modify and expand the specific components.The abstraction and encapsulation of the real-time interface rendering engine allow developers to focus more on the implementation of business logic without having to worry too much about the underlying rendering details.

[0069] In one embodiment of the present invention, the S1 includes:

[0070] S11: According to different types of components, the component library is divided into a graphic component library, an interactive component library and an animation effect component library;

[0071] S12: According to different types of logic modules, the logic modules are divided into a rendering control module, an interactive logic module and a real-time data update module.

[0072] The working principle and effect of the above technical solution are as follows: the graphic component library is mainly responsible for displaying information on the interface, and users can adjust its appearance (such as size, color, font, etc.) through the property editor to adapt to different design requirements. The graphic component library provides a set of standard interfaces and property sets, so that developers can easily embed it into any interface. The interactive component library not only displays information, but also receives user input and triggers corresponding events or behaviors according to user operations. The interactive component library provides an event handling mechanism, allowing developers to define various event listeners and callback functions for components to implement complex interactive logic. The animation effect component library provides an animation control interface, allowing developers to define animation parameters such as type, duration, delay, and animation trigger conditions and end conditions. The rendering control module receives data and style information from the component library, and draws the component onto the interface according to preset layout rules and rendering algorithms. At the same time, it is also responsible for handling performance issues in the rendering process, such as reducing the number of redrawing and rearrangement and improving rendering efficiency. The interactive logic module triggers the corresponding event handling function by listening to user operations. In the event handling function, the module updates the status of the component or performs other operations according to business needs. At the same time, it can also feed back the results of user operations to the user. The real-time data update module obtains the latest data from the server or other data sources through polling, WebSocket or other real-time communication technologies. After obtaining the data, the module will map the data to the corresponding components on the interface according to the data format and update rules to realize the real-time display of the data. At the same time, it can also handle abnormal situations in the data update process, such as data loading failure or data format error. By subdividing components and logic modules, each part becomes more independent and modular. This means that developers can easily reuse these components and modules to quickly build interfaces and functions in different projects, reducing duplication of work and improving development efficiency. The classified storage method makes the organizational structure of the component library and the logic module library clearer. Developers can quickly find the required components or modules, lowering the threshold for learning and use. At the same time, this structure also facilitates collaboration and code management between teams. The subdivided components and modules can be expanded or modified as needed without affecting other parts. This flexibility enables the system to easily adapt to changing business needs and technological development. At the same time, when new functions need to be added, only new components or modules need to be developed and integrated into the existing system.

[0073] In one embodiment of the present invention, S2 includes:

[0074] S21: setting a corresponding property editor according to each component library and logic module library, and collecting user input through a form;

[0075] S22: Bind the form of the property editor to the data model of the component and logic module, and establish a real-time connection between the data model of the component and logic module and the preview window, so that while the property is being edited, the display of the corresponding component in the design area is updated in real time and displayed to the user through the preview window.

[0076] The working principle and effect of the above technical solution are as follows: a dedicated property editor is designed for each type of component. These editors provide different configuration items according to the characteristics of the component or module, such as color selector, font selector, numeric input box, drop-down menu, etc. Inside the property editor, form elements (such as input box, selection box, slider, etc.) are used to build a user interface so that users can enter or select configuration values. These form elements are directly associated with the properties of the component or module. When the user enters or selects values ​​in the form of the property editor, these values ​​are collected in real time and stored in temporary variables or data structures, waiting for further processing. Bind the form elements in the property editor to the data model of the component or logic module. This means that any changes in the form elements are automatically updated to the data model, and vice versa. This binding is usually implemented through a data binding framework or two-way data binding technology. Establish a real-time connection between the design area and the preview window. This connection ensures that the status of the components and logic modules in the design area is synchronized with the content displayed in the preview window. When the user modifies the properties of the component or logic module in the property editor, these changes are immediately reflected in the data model. These changes are then passed to the design area and preview window through the real-time connection mechanism. In the design area, the corresponding components are re-rendered according to the new property values; in the preview window, users can see the impact of these changes on the final interface effect. The whole process forms a closed-loop feedback system. Users modify the properties of components or logic modules through the property editor, and these changes are reflected in the design area and preview window in real time through the data model and the real-time connection mechanism. Users can further adjust the properties according to the preview effect until a satisfactory effect is achieved. The real-time preview function allows users to see interface changes instantly during the editing process without waiting for compilation or refresh, which greatly improves design efficiency and user satisfaction. Users can adjust the properties of components and logic modules directly in the design environment and immediately view the effects in the preview window. This instant feedback mechanism helps users quickly iterate and optimize design solutions. Data model binding and real-time update mechanisms reduce the workload of manual coding and debugging, allowing developers to focus more on interface design and function implementation itself. The number of times the page needs to be recompiled or refreshed due to modifying the properties of components or logic modules is reduced, thereby speeding up the development process.

[0077] In one embodiment of the present invention, the interaction between the components and logic modules and the design area includes:

[0078] A: Introduce a drag library, and apply the drag source wrapper provided by the drag library to the component or logic module to make the component or logic module draggable;

[0079] B: Set the placement area wrapper in the design area and define the entire design area as the placement area;

[0080] C: Drag a component or logic module with the mouse. After the component or logic module is dragged to the design area as the mouse is moved horizontally, the mouse is released, and the component or logic module completes the interaction with the design area.

[0081] The working principle and effect of the above technical solution are as follows: First, a drag library needs to be integrated into a project, which provides the API and tools required to implement the drag function. The drag source wrapper provided by the drag library is used to encapsulate the representation elements of the component or logic module. This wrapper will mark the element as draggable and handle the initialization, ongoing and end stages of the drag event. In the drag source wrapper, it is usually necessary to prepare some data related to the component or logic module, which will be passed during the drag process and used to create or update the elements in the design area when placed. The drop target wrapper provided by the drag library is used to wrap the entire design area. This wrapper is responsible for listening to drag events, especially events of the drag element entering, hovering and leaving the drop area. Defining the entire design area as a drop area means that the user can place the dragged component or logic module anywhere in the design area. In the drop area, visual feedback (such as changing the mouse pointer style, displaying a placeholder or a highlighted area) can be used to indicate the location where the user can currently place the drag element. The user drags the component or logic module that has been wrapped as a drag source with the mouse and moves it on the screen. During this process, the drag library handles the mouse move event and updates the position and state of the dragged element. When the dragged element enters the design area, the drop area wrapper captures this event and prepares to receive the dragged element. The user continues to move the mouse to adjust the drop position and releases the mouse button at a satisfactory position. After the mouse is released, the drag library triggers a drop event. In this event, interaction processing is performed based on the data of the dragged element and the drop area, such as creating a new component or logic module instance in the design area and updating its properties and position. Drag and drop operation is an intuitive and natural way of interaction. Users do not need to learn complex commands or interface elements. They can add, move and adjust components or logic modules through simple mouse operations. This intuitiveness reduces the learning cost and improves user efficiency. The drag library provides a wealth of APIs and tools, allowing developers to quickly implement drag and drop functions without having to write related code from scratch. This greatly saves development time and allows developers to focus more on business logic and function implementation. At the same time, drag and drop operations also accelerate the iteration process of interface design. Developers can quickly try out different layouts and component combinations, and optimize the design through instant feedback, thereby improving development efficiency. Drag-and-drop operations allow users to more flexibly control interface elements, such as the location and size of components and logic modules. This flexibility allows users to customize the interface according to their needs and preferences, thereby improving the user experience.

[0082] In one embodiment of the present invention, S3 includes:

[0083] S31: Create an application programming interface for the component, define a custom event that the component needs to trigger, and transmit data changes to the logic module through the application programming interface;

[0084] S32: creating an application programming interface of the logic module, receiving data from the component, and transmitting the return results and triggering events of the logic module;

[0085] S33: In the main interface, combine the components and logic modules together to form a complete module.

[0086] The working principle and effect of the above technical solution are as follows: a set of APIs are designed for each component, which define the operations that the component can perform and the custom events that can be triggered. These operations include data acquisition, setting, and response to user interaction. Inside the component, a series of custom events are defined, which are triggered when the component state changes or when the user interacts. When the state of the component changes or certain operations need to be performed, the relevant data changes or operation requests are transmitted to the logic module through its API. A set of APIs are designed for each logic module, which define the data types that the logic module can receive, the operations that can be performed, and the types of results that can be returned. The logic module receives data from the component through its API. The logic module performs corresponding business logic processing based on the received data. After the processing is completed, the logic module returns the results to the component and triggers related events through the API. In the main interface, according to the needs and design of the application, the components and the logic module are integrated through the API. This involves placing components in the interface layout and connecting the components to the logic module programmatically. After integration, a closed loop of data flow and event processing is formed between the components and the logic module. Users interact with the interface through components, and components transmit user input or state changes to the logic module through APIs; the logic module processes data and returns results or triggers events, which in turn affect the display and behavior of components through APIs. In this way, components and logic modules are tightly combined to form a complete module. This module contains both user interface elements (components) and code (logic modules) that process data and business logic, thereby realizing specific functions of the application. By splitting the application into components and logic modules, each part becomes more independent and reusable. This means that the same component or logic module can be reused in different applications or projects, thereby reducing the workload of repeated development and improving development efficiency. Components are responsible for the display of user interfaces and data, while logic modules are responsible for processing data and business logic. This clear division of responsibilities makes the system structure clearer, easier to understand and maintain. When problems occur, specific components or logic modules can be located more quickly, reducing the time to troubleshoot and fix the problem.

[0087] In one embodiment of the present invention, the S4 includes:

[0088] S41: Establish unit test modules to test components and logic modules and ensure that components and logic modules work as expected;

[0089] S42: Establish an integration test module to test the interaction between components and logic modules, and ensure that the interaction between components and logic modules is smooth;

[0090] S43: Establish an end-to-end testing module, simulate user operations, test the entire system process, and ensure the smoothness of the entire process.

[0091] The working principle and effect of the above technical solution are as follows: for components and logic modules, unit testing will test their internal logic and functions respectively to ensure that they can correctly perform the expected operations. The test device will write test cases for each component and logic module, which will simulate various input conditions and boundary conditions and verify whether the output results meet expectations. Unit testing is usually performed in an isolated environment, that is, only a single module is tested without considering the interaction with other modules. The main goal of integration testing is to test the interaction between software components. At this stage, multiple components and logic modules are combined to test whether the interface and data transfer between them are performed as expected. Integration testing simulates the interaction scenarios between components, including the sending and receiving of data, the triggering and response of events, etc. The test device will write test cases to verify whether these interactions meet the design specifications and business logic. The main goal of end-to-end testing is to simulate user operations and test the entire process of the entire system flow from start to end. This includes user interface interaction, backend service calls, database read and write operations, etc. End-to-end testing simulates user behavior, starting from logging into the system until completing a specific task or operation. The test harness writes test scripts to automate these operations and verify that the system's responses and results are as expected. Unit testing is usually performed in an isolated environment without relying on other modules or external systems. This makes the testing process more stable and reduces test failures due to dependencies. By writing detailed test cases for each module, unit testing can cover multiple paths and boundary conditions of the code to ensure the robustness and reliability of the code. Integration testing can discover inconsistencies and problems in the interfaces between components to ensure that they can interact and collaborate correctly. By testing the integration of multiple components, integration testing can ensure the overall stability and reliability of the system. End-to-end testing simulates the user's actual operation process and can discover problems that may be missed in unit testing and integration testing. By ensuring the smoothness of the entire system process, end-to-end testing can improve the user experience and thus improve user satisfaction.

[0092] One embodiment of the present invention is a system for interacting with a visual business assembly component and a real-time interface rendering engine, the system comprising:

[0093] Component library and logic module library: According to the different types of components and logic modules, corresponding component libraries and logic module libraries are established to realize classified storage of components and logic modules;

[0094] Area design module: Set up property editors for component libraries and logic module libraries, bind them to data models, and provide real-time feedback to users through preview windows;

[0095] Interactive device: through the interactive model, components and logic modules can be moved to the design area by dragging, so that the edited components and edited logic modules can interact in real time;

[0096] Optimization device: Add optimization device to optimize the smoothness of the interaction between components and logic modules, so as to achieve smooth interaction between components and design areas, logic modules and design areas, and components and logic modules.

[0097] The working principle and effect of the above technical solution are as follows: Visual assembly components allow users to build and arrange through the editor, and users can select and modify component properties through the component panel. These components are usually designed as a low-code development method, that is, the developed components can be dragged and arranged through the editor to complete specific business functions. The assembled components will carry their properties, styles, behaviors and other data. These data will be passed to the real-time interface rendering engine for subsequent rendering and interaction processing. The rendering engine uses the HTML parser to parse the HTML document into a DOM tree, which is the basis for the browser to understand and operate the web page. The CSS parser parses the CSS style and converts it into a CSS object, which is assembled into a CSSOM tree. After the DOM tree and the CSSOM tree are built, the browser will build a rendering tree (RenderTree) based on these two trees, which determines which elements are visible and their style information. After the rendering tree is built, the browser will calculate the size and absolute position of all elements and determine their layout on the page. After the page layout is completed, the browser will convert each node in the rendering tree into pixels and decode all media files to finally generate a visual image result. The real-time interface rendering engine considers the data and properties of components, such as color, size, position, etc., during the rendering process. The rendering engine dynamically adjusts the rendering results according to the properties of the components to achieve real-time visualization. The user's interaction with the component (click, drag, etc.) is also processed by the rendering engine and the rendering results are updated in real time. Visual assembly components allow developers to quickly build pages by dragging, arranging, etc., without having to write a lot of HTML, CSS and JavaScript code, which significantly improves development efficiency. The real-time interface rendering engine can respond immediately to changes in component properties without recompiling or loading the entire page, further speeding up the development iteration. The intuitiveness and ease of use of visual assembly components allow developers to quickly get started even without deep programming knowledge, lowering the threshold for development. The instant feedback of real-time rendering helps developers understand the page effect more intuitively and reduce development troubles caused by code errors or logic problems. The real-time interface rendering engine can convert the properties and behaviors of components into visual interface effects in real time, ensuring that users can immediately see the modified page effect. The real-time interaction support between components and rendering engines makes the page highly interactive. Users can trigger corresponding page changes by operating components, improving the user experience. The flexibility of visual assembly components allows developers to freely combine and modify components as needed to meet different business needs. The scalability of the real-time interface rendering engine allows developers to add new rendering effects and interactive functions as needed to meet the continuous development and changes of the project. The modular design of visual assembly components makes the code structure clear and easy to maintain. When you need to modify or expand the page function, you only need to modify and expand the specific components.The abstraction and encapsulation of the real-time interface rendering engine allow developers to focus more on the implementation of business logic without having to worry too much about the underlying rendering details.

[0098] In one embodiment of the present invention, the area design module includes:

[0099] Property editor: Set up corresponding property editors according to each component library and logic module library, and collect user input through forms;

[0100] Real-time synchronization device: binds the form of the property editor to the data model of the component and logic module, and establishes a real-time connection between the data model of the component and logic module and the preview window, so that while the properties are edited, the display of the corresponding component in the design area is updated in real time and displayed to the user through the preview window.

[0101] The working principle and effect of the above technical solution are as follows: a dedicated property editor is designed for each type of component. These editors provide different configuration items according to the characteristics of the component or module, such as color selector, font selector, numeric input box, drop-down menu, etc. Inside the property editor, form elements (such as input box, selection box, slider, etc.) are used to build a user interface so that users can enter or select configuration values. These form elements are directly associated with the properties of the component or module. When the user enters or selects values ​​in the form of the property editor, these values ​​are collected in real time and stored in temporary variables or data structures, waiting for further processing. Bind the form elements in the property editor to the data model of the component or logic module. This means that any changes in the form elements are automatically updated to the data model, and vice versa. This binding is usually implemented through a data binding framework or two-way data binding technology. Establish a real-time connection between the design area and the preview window. This connection ensures that the status of the components and logic modules in the design area is synchronized with the content displayed in the preview window. When the user modifies the properties of the component or logic module in the property editor, these changes are immediately reflected in the data model. These changes are then passed to the design area and preview window through the real-time connection mechanism. In the design area, the corresponding components are re-rendered according to the new property values; in the preview window, users can see the impact of these changes on the final interface effect. The whole process forms a closed-loop feedback system. Users modify the properties of components or logic modules through the property editor, and these changes are reflected in the design area and preview window in real time through the data model and the real-time connection mechanism. Users can further adjust the properties according to the preview effect until a satisfactory effect is achieved. The real-time preview function allows users to see interface changes instantly during the editing process without waiting for compilation or refresh, which greatly improves design efficiency and user satisfaction. Users can adjust the properties of components and logic modules directly in the design environment and immediately view the effects in the preview window. This instant feedback mechanism helps users quickly iterate and optimize design solutions. Data model binding and real-time update mechanisms reduce the workload of manual coding and debugging, allowing developers to focus more on interface design and function implementation itself. The number of times the page needs to be recompiled or refreshed due to modifying the properties of components or logic modules is reduced, thereby speeding up the development process.

[0102] In one embodiment of the present invention, the interaction device comprises:

[0103] Component API: Create the component API, define the custom events that the component needs to trigger, and transmit data changes to the logic module through the API;

[0104] Application programming interface of logic module: Create the application programming interface of logic module, receive data from components, and transmit the return results and trigger events of logic module;

[0105] Integrated device: In the main interface, combine components and logic modules together to form a complete module.

[0106] The working principle and effect of the above technical solution are as follows: a set of APIs are designed for each component, which define the operations that the component can perform and the custom events that can be triggered. These operations include data acquisition, setting, and response to user interaction. Inside the component, a series of custom events are defined, which are triggered when the component state changes or when the user interacts. When the state of the component changes or certain operations need to be performed, the relevant data changes or operation requests are transmitted to the logic module through its API. A set of APIs are designed for each logic module, which define the data types that the logic module can receive, the operations that can be performed, and the types of results that can be returned. The logic module receives data from the component through its API. The logic module performs corresponding business logic processing based on the received data. After the processing is completed, the logic module returns the results to the component and triggers related events through the API. In the main interface, according to the needs and design of the application, the components and the logic module are integrated through the API. This involves placing components in the interface layout and connecting the components to the logic module programmatically. After integration, a closed loop of data flow and event processing is formed between the components and the logic module. Users interact with the interface through components, and components transmit user input or state changes to the logic module through APIs; the logic module processes data and returns results or triggers events, which in turn affect the display and behavior of components through APIs. In this way, components and logic modules are tightly combined to form a complete module. This module contains both user interface elements (components) and code (logic modules) that process data and business logic, thereby realizing specific functions of the application. By splitting the application into components and logic modules, each part becomes more independent and reusable. This means that the same component or logic module can be reused in different applications or projects, thereby reducing the workload of repeated development and improving development efficiency. Components are responsible for the display of user interfaces and data, while logic modules are responsible for processing data and business logic. This clear division of responsibilities makes the system structure clearer, easier to understand and maintain. When problems occur, specific components or logic modules can be located more quickly, reducing the time to troubleshoot and fix the problem.

[0107] In one embodiment of the present invention, the optimization device comprises:

[0108] Unit test module: Establish unit test modules to test components and logic modules and ensure that components and logic modules work as expected;

[0109] Integration test module: Establish an integration test module to test the interaction between components and logic modules, and ensure smooth interaction between components and logic modules;

[0110] End-to-end testing module: Establish an end-to-end testing module to simulate user operations, test the process of the entire system, and ensure the smoothness of the entire process.

[0111] The test optimization device tests the smoothness of the interaction between the visualization component and the logic module and the design area, including:

[0112] Build a test environment similar to the actual situation and record the operation start time and response completion time;

[0113] Based on the collected operation start time and response completion time, the response time of each operation is calculated. At the same time, the performance of the component is evaluated by combining the system throughput and the number of concurrent users. The performance evaluation formula can be obtained through the following formula:

[0114]

[0115] Where P represents the performance evaluation score, M represents the average throughput actually observed per unit time. max represents the maximum throughput of the system per unit time, C represents the number of concurrent users actually observed, and C max Indicates the maximum number of concurrent users that the system can stably support. It represents the average value of the response time actually observed per unit time, E min Indicates the minimum acceptable response time per unit time, E max represents the maximum response time that can be received within a unit time, n represents the total number of unit time periods tested, and the throughput represents the amount of data successfully transmitted by the network within a unit time, and the number of concurrent users represents the number of users who interact with the system at the same time period;

[0116] When 90<P≤100, it means that the system performance is very good, the throughput is close to the maximum value, the number of concurrent users is high, and the response time is very short. The existing system should be maintained to ensure that the system can continue to run efficiently.

[0117] When 50<P≤90, it means that the system performance is acceptable, but there may be some bottlenecks or room for optimization. You should deeply analyze the specific performance of each sub-item (throughput, number of concurrent users, response time) to find out the performance bottleneck. Optimize the bottleneck, including optimizing database queries, increasing cache, adjusting system configuration, etc. At the same time, pay attention to the stability and reliability of the system to ensure that the system can still run stably under high load.

[0118] When P≤50, it means that the system performance is poor and may not meet current needs or future growth needs. Performance tuning and troubleshooting should be performed immediately. First, determine which sub-items caused the low score. If the throughput is low, you need to optimize the data processing process, increase hardware resources, etc.; if the number of concurrent users is low, you need to consider load balancing, increase the number of servers, etc.; if the response time is long, you need to optimize the code, database query, etc.

[0119] The working principle and effect of the above technical solution are as follows: for components and logic modules, unit testing will test their internal logic and functions respectively to ensure that they can correctly perform the expected operations. The test device will write test cases for each component and logic module, which will simulate various input conditions and boundary conditions and verify whether the output results meet expectations. Unit testing is usually performed in an isolated environment, that is, only a single module is tested without considering the interaction with other modules. The main goal of integration testing is to test the interaction between software components. At this stage, multiple components and logic modules are combined to test whether the interface and data transfer between them are performed as expected. Integration testing simulates the interaction scenarios between components, including the sending and receiving of data, the triggering and response of events, etc. The test device will write test cases to verify whether these interactions meet the design specifications and business logic. The main goal of end-to-end testing is to simulate user operations and test the entire process of the entire system flow from start to end. This includes user interface interaction, backend service calls, database read and write operations, etc. End-to-end testing simulates user behavior, starting from logging into the system until completing a specific task or operation. The test harness writes test scripts to automate these operations and verify that the system's responses and results are as expected. Unit testing is usually performed in an isolated environment without relying on other modules or external systems. This makes the testing process more stable and reduces test failures due to dependencies. By writing detailed test cases for each module, unit testing can cover multiple paths and boundary conditions of the code to ensure the robustness and reliability of the code. Integration testing can discover inconsistencies and problems in the interfaces between components to ensure that they can interact and collaborate correctly. By testing the integration of multiple components, the overall stability and reliability of the system can be ensured. End-to-end testing simulates the user's actual operation process and can discover problems that may be missed in unit testing and integration testing. By ensuring the smoothness of the entire system process, end-to-end testing can improve user experience and thus improve user satisfaction.

[0120] Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.

Claims

1. A method for interacting a visual business assembly component with a real-time interface rendering engine, characterized in that: The method comprises: S1: According to the different types of components and logic modules, corresponding component libraries and logic module libraries are established to realize classified storage of components and logic modules; S2: Set up property editors for component libraries and logic module libraries, bind them to data models, and provide real-time feedback to users through preview windows; S3: Through the interactive model, components and logic modules are moved to the design area by dragging, so that the edited components and edited logic modules can interact in real time; S4: adding an optimization device to optimize the smoothness of the interaction between the component and the logic module, so as to achieve smooth interaction between the component and the design area, the logic module and the design area, and the component and the logic module, and said S2 includes: S21: setting a corresponding property editor according to each component library and logic module library, and collecting user input through a form; S22: Bind the form of the property editor to the data model of the component and logic module, and establish a real-time connection between the data model of the component and logic module and the preview window, so that while the property is being edited, the display of the corresponding component in the design area is updated in real time and displayed to the user through the preview window.

2. The method for interacting between a visual business assembly component and a real-time interface rendering engine according to claim 1, characterized in that: The S1 includes: S11: According to different types of components, the component library is divided into a graphic component library, an interactive component library and an animation effect component library; S12: According to different types of logic modules, the logic modules are divided into a rendering control module, an interactive logic module, and a real-time data update module.

3. The method for interacting between a visual business assembly component and a real-time interface rendering engine according to claim 1, characterized in that: The components and logic modules interact with the design area in the following ways: A: Introduce a drag library, and apply the drag source wrapper provided by the drag library to the component or logic module to make the component or logic module draggable; B: Set the placement area wrapper in the design area and define the entire design area as the placement area; C: Drag a component or logic module with the mouse. After the component or logic module is dragged to the design area as the mouse is moved horizontally, the mouse is released, and the component or logic module completes the interaction with the design area.

4. The method for interacting with a visual business assembly component and a real-time interface rendering engine according to claim 1, characterized in that: The S3 includes: S31: Create an application programming interface for the component, define a custom event that the component needs to trigger, and transmit data changes to the logic module through the application programming interface; S32: creating an application programming interface of the logic module, receiving data from the component, and transmitting the return results and triggering events of the logic module; S33: In the main interface, combine the components and logic modules together to form a complete module.

5. The method for interacting between a visual business assembly component and a real-time interface rendering engine according to claim 1, characterized in that: The S4 includes: S41: Establish unit test modules to test components and logic modules and ensure that components and logic modules work as expected; S42: Establish an integration test module to test the interaction between components and logic modules, and ensure that the interaction between components and logic modules is smooth; S43: Establish an end-to-end testing module, simulate user operations, test the entire system process, and ensure the smoothness of the entire process.

6. Visual business assembly components and real-time interface rendering engine interaction system, characterized by: The system comprises: Component library and logic module library: According to the different types of components and logic modules, corresponding component libraries and logic module libraries are established to realize classified storage of components and logic modules; Area design module: Set up property editors for component libraries and logic module libraries, bind them to data models, and provide real-time feedback to users through preview windows; Interactive device: through the interactive model, components and logic modules can be moved to the design area by dragging, so that the edited components and edited logic modules can interact in real time; Optimization device: Add optimization device to optimize the smoothness of the interaction between components and logic modules, so as to achieve smooth interaction between components and design areas, logic modules and design areas, and components and logic modules.

7. The interactive system between the visualization business assembly component and the real-time interface rendering engine according to claim 6 is characterized in that: The area design module includes: Property editor: Set up corresponding property editors according to each component library and logic module library, and collect user input through forms; Real-time synchronization device: binds the form of the property editor to the data model of the component and logic module, and establishes a real-time connection between the data model of the component and logic module and the preview window, so that while the properties are edited, the display of the corresponding component in the design area is updated in real time and displayed to the user through the preview window.

8. The interactive system of the visual business assembly component and the real-time interface rendering engine according to claim 6 is characterized in that: The interactive device comprises: Component API: Create the component API, define the custom events that the component needs to trigger, and transmit data changes to the logic module through the API; Application programming interface of logic module: Create the application programming interface of logic module, receive data from components, and transmit the return results and trigger events of logic module; Integrated device: In the main interface, combine components and logic modules together to form a complete module.

9. The interactive system of visual business assembly components and real-time interface rendering engine according to claim 6, characterized in that: The optimization device comprises: Unit test module: Establish unit test modules to test components and logic modules and ensure that components and logic modules work as expected; Integration test module: Establish an integration test module to test the interaction between components and logic modules, and ensure smooth interaction between components and logic modules; End-to-end testing module: Establish an end-to-end testing module to simulate user operations, test the process of the entire system, and ensure the smoothness of the entire process.

Citation Information

Patent Citations

  • Comprehensive portal management system of dragging type layout configuration

    CN105302578A

  • Visualized designer based on ReactJS and data large-size screen manufacturing method

    CN107330053A

  • Real-time updating data visualization large screen method and system based on modularization

    CN111522565A

  • Component generation method and device, computer equipment and computer readable storage medium

    CN111752560A

  • Display system prototype configuration development tool

    CN112068831A