User interface processing method and device

Abstract

The embodiment of the invention provides a user interface processing method which comprises the steps that in response to an application starting instruction, a plurality of components are created through a component management module, and each component is an independent function module; adding the plurality of components to a content view through the component management module; and activating the plurality of components through the component management module, the plurality of components being used for displaying data on a user interface. According to the technical scheme, the multiple components can be created through the component management module, the multiple components are added into the content view through the component management module, the multiple components are activated, the independent components can be assembled into the customized user interface, and therefore efficient, flexible and convenient customized user interface development is achieved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of Internet technology, and in particular, to a user interface processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Art

[0002] As the demand for user interfaces continues to increase, interface functions become increasingly complex. Traditional development models usually develop all interface logic and functional codes together. This approach leads to high code coupling, which makes interface components closely related. Modifying or adding a function may affect the stability of the entire system, which increases the difficulty of development and maintenance. The iteration speed of interface development slows down, and comprehensive testing is required for any changes, which seriously affects the improvement of development efficiency and user experience.

[0003] It should be noted that the above content is not necessarily prior art, nor is it intended to limit the scope of patent protection of this application. Summary of the invention

[0004] Embodiments of the present application provide a user interface processing method, apparatus, computer device, computer-readable storage medium, and computer program product to solve or alleviate one or more of the technical problems raised above.

[0005] An aspect of an embodiment of the present application provides a user interface processing method, the method comprising: In response to the application startup instruction, multiple components are created through the component management module, each component being an independent functional module; By means of the component management module, the plurality of components are added to the content view; The plurality of components are activated through the component management module, and the plurality of components are used to display data on a user interface.

[0006] Optionally, the data center is used to maintain a common data mapping table and an observable data mapping table; Correspondingly, the acquiring data from the data center includes: Obtaining a unique identifier for said data; The data is searched from the common data mapping table or the observable data mapping table by the unique identifier.

[0007] Optionally, the plurality of components are further used to obtain external data through a bridge module; The bridge module is configured with a bridge providing interface instance, and the bridge providing interface instance is used for a third party to register and obtain a bridge interface of a corresponding component, and the bridge interface is used to provide the function of the corresponding component to the third party.

[0008] Optionally, external data is obtained through a bridge module, including: Passing the external data to the corresponding target component through the bridge module; and The target component that receives the external data is recorded, and the record is provided to other components so that the data of the other components can be updated.

[0009] Optionally, the multiple components interact with each other through a service module.

[0010] Optionally, the service module is configured with a logical interface; The logic interface is used to connect various components.

[0011] Optionally, the method further comprises: Through the hook processing method, the life cycles of the multiple components and the component management module are bound to each other.

[0012] Another aspect of an embodiment of the present application provides a user interface processing device, the device comprising: A creation module, used to create multiple components through a component management module in response to an application startup instruction, each component being an independent functional module; An adding module, used for adding the plurality of components to the content view through the component management module; The activation module is used to activate the multiple components through the component management module, and the multiple components are used to display data on the user interface.

[0013] Another aspect of an embodiment of the present application provides a computer device, including: at least one processor; and a memory communicatively coupled to the at least one processor; Wherein: the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the method as described above.

[0014] Another aspect of an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and when the computer instructions are executed by a processor, the method described above is implemented.

[0015] Another aspect of an embodiment of the present application provides a computer program product, including a computer program, which implements the method described above when executed by a processor.

[0016] Another aspect of an embodiment of the present application provides a user interface processing device, the system comprising: The component management module is used to create multiple components, each of which is an independent functional module; A content view, built in or coupled to the component management module, and loading the multiple components through the component management module; a data center for providing internal data to one or more of the plurality of components; A bridge module, configured with a bridge-provided interface instance, for transferring external data to any one of the plurality of components; and The service module is configured with a logical interface, and the logical interface is used to connect various components for interaction between the various components.

[0017] The above technical solution adopted in the embodiment of the present application may have the following advantages: Split the overall project or business code into independent components. Create multiple components through the component management module, add multiple components to the content view and activate multiple components through the component management module, so that independent components can be assembled into a customized user interface, thus achieving efficient, flexible and convenient customized user interface development. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The accompanying drawings exemplarily illustrate the embodiments and constitute a part of the specification, and together with the text description of the specification, are used to explain the exemplary implementation of the embodiments. The embodiments shown are for illustrative purposes only and do not limit the scope of the claims. In all drawings, the same reference numerals refer to similar but not necessarily identical elements.

[0019] Figure 1 A flowchart of a user interface processing method according to Embodiment 1 of the present application is schematically shown; Figure 2 A newly added flow chart of the user interface processing method according to the first embodiment of the present application is schematically shown; Figure 3 A newly added flow chart of the user interface processing method according to the first embodiment of the present application is schematically shown; Figure 4 The following schematically shows an application example diagram according to the first embodiment of the present application; Figure 5 A block diagram of a user interface processing device according to a second embodiment of the present application is schematically shown; Figure 6 A block diagram of a user interface processing system according to Embodiment 3 of the present application is schematically shown; Figure 7 The hardware architecture diagram of the computer device according to the fourth embodiment of the present application is schematically shown. DETAILED DESCRIPTION

[0020] In order to make the purpose, technical solutions and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present application.

[0021] It should be noted that the descriptions involving "first", "second", etc. in the embodiments of the present application are only for descriptive purposes and cannot be understood as indicating or implying their relative importance or implicitly indicating the number of technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In addition, the technical solutions between the various embodiments can be combined with each other, but they must be based on the ability of ordinary technicians in the field to implement them. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such combination of technical solutions does not exist and is not within the scope of protection required by this application.

[0022] In the description of the present application, it should be understood that the numerical labels before the steps do not indicate the order in which the steps are executed, but are only used to facilitate the description of the present application and to distinguish each step, and therefore should not be understood as a limitation on the present application.

[0023] First, the following terms are explained: UI: User Interface (UI for short, also known as user interface) is the medium for interaction and information exchange between the system and the user. It realizes the conversion between the internal form of information and the form acceptable to humans.

[0024] Secondly, to facilitate those skilled in the art to understand the technical solutions provided by the embodiments of the present application, the relevant technologies are described below. The applicant understands that as the business continues to develop, the types of business become diverse, and traditional business development is achieved by centralizing and coupling the codes of various projects together. This leads to slow development efficiency, difficult maintenance, and a single move affects the entire system.

[0025] To this end, the embodiment of the present application provides a user interface processing technical solution. In this technical solution: by splitting the project or business code into independent components, and then assembling the independent components into a customized UI interface, this method can achieve fast, convenient and flexible customized UI interface development.

[0026] The technical solutions of the present application are described below through multiple embodiments. It should be noted that these embodiments can be implemented in a variety of different forms and should not be construed as being limited to the embodiments described here.

[0027] Embodiment 1 Figure 1 The flowchart of the user interface processing method according to the first embodiment of the present application is schematically shown.

[0028] like Figure 1 As shown, the user interface processing method may include steps S100 to S104, wherein: Step S100, in response to an application startup instruction, a plurality of components are created through a component management module, each component being an independent functional module.

[0029] Step S102: adding the plurality of components to the content view through the component management module.

[0030] Step S104: activating the plurality of components through the component management module, wherein the plurality of components are used to display data on a user interface.

[0031] The user interface processing method provided in this embodiment splits the overall project or business code into independent components. Multiple components are created through the component management module, and multiple components are added to the content view and activated through the component management module, so that the independent components can be assembled into a customized user interface, thereby realizing efficient, flexible and convenient customized user interface development.

[0032] The following combination Figure 1 , each step in steps S100~S104 and other optional steps are explained in detail.

[0033] Step S100 In response to the application startup instruction, multiple components are created through the component management module, and each component is an independent functional module.

[0034] Exemplarily, the component management module can be a Fragment, which is a reusable interface component. Multiple components have been pre-written and implemented, and can also support customization or expansion according to needs. Multiple components can be multiple virtual Views, which are responsible for displaying the UI and are located in the interface layer where users interact with applications. Multiple components can be user information components and user status components, etc. The user information component is used to display the user's basic information, such as user name and avatar. The user status component is used to display the user's current status.

[0035] Step S102 , through the component management module, the multiple components are added to the content view.

[0036] Exemplarily, according to different business needs, the component management module loads different components into its own content view. The content view is equivalent to the display area of ​​the component, which can be a container for carrying UI elements. Multiple components can be bound to the content view through the create view method. The create view method is used to create and return the user interface view of the UI component. For example, through the create view method, the user information component interface can be bound to the content view, and the layout related to the user information (such as UI elements that display the user name and avatar) can be loaded.

[0037] Step S104 , through the component management module, activating the multiple components, and the multiple components are used to display data on the user interface.

[0038] Exemplarily, activating multiple components can make the multiple components enter an active state. When the multiple components enter an active state, data updating or display operations can be performed. In some embodiments, after activating the user information component, the user information component can obtain user information and display it. After activating the user status component, the user status change can be subscribed to display the user's current status.

[0039] In this embodiment, multiple components are created through the component management module, and the multiple components are added to the content view and activated through the component management module, so that independent components can be assembled into a customized user interface, thereby realizing efficient, flexible and convenient customized user interface development.

[0040] In an optional embodiment, the method further includes: obtaining the data from the data center through the multiple components and displaying the data on the user interface. The data center can be used to process the data obtained from the data model and convert it into a form that can be directly used by the view. In some embodiments, data that may be used by multiple components is stored. This part of the data needs to be read and updated by multiple components, and the relevant components can perceive changes in the data they want to obtain. This part of the data can be stored in the data center. In some embodiments, the component management module can have a reference or instance for accessing the data center. When the component management module creates a component, the component management module will pass the reference or instance to the component, so that the component can obtain access to the data center when it is created, and can read and update the data in the data center.

[0041] In this embodiment, the data center can be used as a data carrier, and can also store the data structure of the data carrier, and provide methods such as writing and reading. The data center can centrally manage data and realize data sharing among multiple components.

[0042] In an optional embodiment, the data center is used to maintain a common data mapping table and an observable data mapping table. Correspondingly, obtaining data from the data center includes: Step S200, obtaining a unique identifier of the data.

[0043] Step S202: searching the data from the common data mapping table or the observable data mapping table by using the unique identifier.

[0044] Exemplarily, a normal data mapping table can store normal data, such as static data and data that does not require dynamic monitoring. An observable data mapping table can store observable variables that can notify other components (observers) when data changes. Normal data mapping tables and observable data mapping tables can be key-value data storage structures. The unique identifier can be a key used to uniquely identify each data item. The value is the data associated with the key, and the key is used to index the value. Each key has a corresponding value, and the value can be any type of data such as a number, a string, an object, etc.

[0045] In this embodiment, data is searched from a common data mapping table or an observable data mapping table through a unique identifier, so that there is no need to pay attention to the actual type of data when passing and obtaining data, and the amount of template code can be reduced, thereby improving development efficiency.

[0046] In an optional embodiment, the multiple components are also used to obtain external data through a bridge module. The bridge module is used for communication between external and internal services. The bridge module is configured with a bridge providing interface instance, and the bridge providing interface instance is used for a third party to register and obtain the bridge interface of the corresponding component, and the bridge interface is used to provide the functions of the corresponding component to the third party. The bridge interface instance can be equivalent to a general toolbox, and a third party can register the functions it needs through the general toolbox, and then the bridge module provides the corresponding bridge interface. The bridge module can also have an observer capability, which allows an object to monitor the state changes of another object by subscription. When the observed object changes, all observers will receive a notification and respond accordingly. In some embodiments, a third party (such as a live broadcast room) registers the bridge interface of the gift component through an interface instance, obtains the bridge interface of the gift component through the bridge module, and calls the function of the gift component. The function of calling the gift component can be calling the gift sending function of the gift component.

[0047] In this embodiment, communication between external and internal businesses is achieved through the bridge module, and the functions of the corresponding components are provided to third parties through the corresponding bridge interface. Third parties that need to use the component functions can easily call related functions through the bridge interface, reducing the complexity of direct dependency.

[0048] In an optional embodiment, obtaining external data through the bridge module may include: Step S300: passing the external data to the corresponding target component through the bridge module.

[0049] Step S302, recording the target component that receives the external data, and providing the record to other components so that the data of the other components can be updated.

[0050] Exemplarily, external data may be updated user information, user status changes, gift sending events, etc. In some embodiments, the bridge module may pass the updated user information to the user information component to update the user information. The bridge module may also observe user status changes and notify the user status component to update the current user status. The bridge module may also pass the current interface or activity environment and the gift ID. The gift ID is used to uniquely identify the gift to be sent, and the gift sending success event may be monitored and recorded, so that the gift component can make corresponding processing when the gift is sent, such as updating the UI or displaying a prompt.

[0051] In this embodiment, external data is transmitted through the bridge module, so that the target component can receive the latest data in time and process it, and at the same time, it realizes monitoring and response to related events, so that other related components can make corresponding processing.

[0052] In an optional embodiment, the multiple components interact with each other through a service module. The service module is used to implement communication between multiple internal components and simple business logic processing. For example, in the gift panel, when operating the same gift or other gifts, the contents of the operation are mutually exclusive. One of the operations may involve multiple components, and component A and component B among these multiple components may need to be in the same position in the same display area. The service module can be used to enable component A and component B to communicate with each other, so that component B is hidden when component A is displayed, and component A is hidden when component B is displayed.

[0053] In this embodiment, the service module components do not need to directly depend on or communicate with each other, but use the service module as an intermediary to exchange data and operate, thereby reducing the coupling degree of multiple components and simplifying the communication logic.

[0054] In an optional embodiment, the service module is configured with a logical interface. The logical interface is used to connect various components. The logical interface is an interface for internal data forwarding and monitoring. Multiple components can obtain the logical interface and then forward and monitor internal data through the logical interface.

[0055] In this embodiment, each component can obtain or send data through the same universal logical interface without directly relying on other modules or components, thereby simplifying the interaction process between components.

[0056] In an optional embodiment, the multiple components and the component management module are mutually bound in life cycle through a hook processing method. The hook processing method allows the program to insert custom logic at a specific life cycle stage. Multiple components and management modules have life cycle capabilities, which refer to the different states and stages that a component or object goes through during its existence, as well as the operations and behaviors that can be performed in these states. In some embodiments, when a target component is created by a component management module, the component management module can pass its own life cycle to the target component. When a related component is loaded or unloaded, the hook method can notify other parts that depend on the related component, so that other components can understand the change of state and independently process the state change.

[0057] In order to make this application easier to understand, the following Figure 4 An exemplary application is provided.

[0058] In this exemplary application, the generation of gift panel is taken as an example. Multiple widgets are pre-written, such as gift banner component, fan badge component, batch gift component and upgrade gift component. When the application starts, the widget management module (WidgetManger) creates multiple widgets and loads multiple widgets into its own content view. After the widget management module (WidgetManger) activates multiple widgets, each widget can obtain data from the data center (DataCenter) and display it on the interface. Through the view model (ViewModel), multiple widgets can realize the separation of UI and logic, and drive the UI through data. Multiple widgets can interact with each other through the logical interface created by the service module (Service). Multiple widgets can communicate with the outside through the bridge module (Bridge). This solution can flexibly load and manage different components (Widgets) through the component management module (WidgetManger), realize data sharing of various components (Widgets) through the data center (DataCenter), and realize external and internal communication of multiple components through the bridge module (Bridge) and service module (Service), thereby realizing a customized UI interface and simplifying complex business layout and UI.

[0059] Embodiment 2 Figure 5 The block diagram of the user interface processing device according to the second embodiment of the present application is schematically shown. The device can be divided into one or more program modules, one or more program modules are stored in a storage medium, and are executed by one or more processors to complete the embodiment of the present application. The program module referred to in the embodiment of the present application refers to a series of computer program instruction segments that can complete specific functions. The following description will specifically introduce the functions of each program module in this embodiment. Figure 5 As shown, the apparatus 1600 may include: a creation module 1610, an addition module 1620 and an activation module 1630, wherein: A creation module 1610, for creating multiple components through a component management module in response to an application startup instruction, each component being an independent functional module; An adding module 1620, configured to add the plurality of components to a content view through the component management module; The activation module 1630 is used to activate the multiple components through the component management module, and the multiple components are used to display data on the user interface.

[0060] As an optional embodiment, the data is acquired from a data center through the multiple components and the data is displayed on the user interface.

[0061] As an optional embodiment, the data center is used to maintain a common data mapping table and an observable data mapping table; Correspondingly, the acquiring data from the data center includes: Obtain a unique identifier for said data; The data is searched from the common data mapping table or the observable data mapping table by the unique identifier.

[0062] As an optional embodiment, the plurality of components are further used to obtain external data through a bridge module; The bridge module is configured with a bridge providing interface instance, and the bridge module provides an interface instance for a third party to register and obtain a bridge interface of a corresponding component, and the bridge interface is used to provide the third party with the function of the corresponding component.

[0063] As an optional embodiment, obtaining external data through a bridge module includes: Passing the external data to the corresponding target component through the bridge module; and The target component that receives the external data is recorded, and the record is provided to other components so that the data of the other components can be updated.

[0064] As an optional embodiment, the multiple components interact with each other through a service module.

[0065] As an optional embodiment, the service module is configured with a logical interface; The logic interface is used to connect various components.

[0066] As an optional embodiment, the method further includes: Through the hook processing method, the life cycles of the multiple components and the component management module are bound to each other.

[0067] Embodiment 3 like Figure 6 A block diagram of a user interface processing system according to Embodiment 2 of the present application is schematically shown. The system 1700 may include: The component management module 1710 is used to create multiple components, each of which is an independent functional module; A content view 1720, which is built in or coupled to the component management module, and loads the multiple components through the component management module; A data center 1730 for providing internal data to one or more of the plurality of components; A bridge module 1740, configured with a bridge providing interface instance, for transferring external data to any one of the plurality of components; and The service module 1750 is configured with a logic interface, and the logic interface is used to connect various components for interaction between the various components.

[0068] As an optional embodiment, the data is acquired from a data center through the multiple components and the data is displayed on the user interface.

[0069] As an optional embodiment, the data center is used to maintain a common data mapping table and an observable data mapping table; Correspondingly, the acquiring data from the data center includes: Obtain a unique identifier for said data; The data is searched from the common data mapping table or the observable data mapping table by the unique identifier.

[0070] As an optional embodiment, the plurality of components are further used to obtain external data through a bridge module; The bridge module is configured with a bridge providing interface instance, and the bridge module provides an interface instance for a third party to register and obtain a bridge interface of a corresponding component, and the bridge interface is used to provide the third party with the function of the corresponding component.

[0071] As an optional embodiment, obtaining external data through a bridge module includes: Passing the external data to the corresponding target component through the bridge module; and The target component that receives the external data is recorded, and the record is provided to other components so that the data of the other components can be updated.

[0072] As an optional embodiment, the multiple components interact with each other through a service module.

[0073] As an optional embodiment, the service module is configured with a logical interface; The logic interface is used to connect various components.

[0074] As an optional embodiment, the method further includes: Through the hook processing method, the life cycles of the multiple components and the component management module are bound to each other.

[0075] Embodiment 4 Figure 7The schematic diagram of the hardware architecture of a computer device 10000 suitable for implementing the user interface processing method according to the third embodiment of the present application is schematically shown. In some embodiments, the computer device 10000 may be a terminal device such as a smart phone, a wearable device, a tablet computer, a personal computer, a vehicle terminal, a game console, a virtual device, a workbench, a digital assistant, a set-top box, a robot, etc. In other embodiments, the computer device 10000 may be a rack server, a blade server, a tower server, or a cabinet server (including an independent server, or a server cluster composed of multiple servers), etc. Figure 7 As shown, the computer device 10000 includes but is not limited to: a memory 10010, a processor 10020, and a network interface 10030 that can communicate with each other through a system bus. Among them: The memory 10010 includes at least one type of computer-readable storage medium, and the readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (such as SD or DX memory), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 10010 can be an internal storage module of the computer device 10000, such as a hard disk or memory of the computer device 10000. In other embodiments, the memory 10010 can also be an external storage device of the computer device 10000, such as a plug-in hard disk equipped on the computer device 10000, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. Of course, the memory 10010 can also include both the internal storage module of the computer device 10000 and its external storage device. In this embodiment, the memory 10010 is generally used to store the operating system and various application software installed in the computer device 10000, such as program codes of the user interface processing method, etc. In addition, the memory 10010 can also be used to temporarily store various data that have been output or will be output.

[0076] In some embodiments, the processor 10020 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other chips. The processor 10020 is generally used to control the overall operation of the computer device 10000, such as performing control and processing related to data interaction or communication with the computer device 10000. In this embodiment, the processor 10020 is used to run the program code stored in the memory 10010 or process data.

[0077] The network interface 10030 may include a wireless network interface or a wired network interface, and the network interface 10030 is generally used to establish a communication link between the computer device 10000 and other computer devices. For example, the network interface 10030 is used to connect the computer device 10000 to an external terminal through a network, and to establish a data transmission channel and a communication link between the computer device 10000 and the external terminal. The network may be a wireless or wired network such as an intranet, the Internet, the Global System of Mobile communication (GSM), Wideband Code Division Multiple Access (WCDMA), 4G network, 5G network, Bluetooth, Wi-Fi, etc.

[0078] It should be pointed out that Figure 7 Only a computer device having components 10010 - 10030 is shown, but it should be understood that implementation of all of the components shown is not a requirement, and more or fewer components may alternatively be implemented.

[0079] In this embodiment, the user interface processing method stored in the memory 10010 can also be divided into one or more program modules and executed by one or more processors (such as processor 10020) to complete the embodiment of the present application.

[0080] Embodiment 5 An embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the steps of the user interface processing method in the embodiment are implemented.

[0081] In this embodiment, the computer-readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, disk, optical disk, etc. In some embodiments, the computer-readable storage medium can be an internal storage unit of a computer device, such as a hard disk or memory of the computer device. In other embodiments, the computer-readable storage medium can also be an external storage device of a computer device, such as a plug-in hard disk equipped on the computer device, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. Of course, the computer-readable storage medium can also include both the internal storage unit of the computer device and its external storage device. In this embodiment, the computer-readable storage medium is generally used to store an operating system and various application software installed on the computer device, such as the program code of the user interface processing method in the embodiment. In addition, the computer-readable storage medium can also be used to temporarily store various types of data that have been output or are to be output.

[0082] Embodiment 6 An embodiment of the present application also provides a computer program product, including a computer program, which implements the method in the above embodiment when executed by a processor.

[0083] Obviously, those skilled in the art should understand that the modules or steps of the above-mentioned embodiments of the present application can be implemented by general-purpose computer devices, they can be concentrated on a single computer device, or distributed on a network composed of multiple computer devices, optionally, they can be implemented by executable program codes of computer devices, so that they can be stored in a storage device and executed by the computer device, and in some cases, the steps shown or described can be executed in a different order from that herein, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. In this way, the embodiments of the present application are not limited to any specific combination of hardware and software.

[0084] It should be noted that the above are only preferred embodiments of the present application, and the patent protection scope of the present application is not limited thereto. Any equivalent structure or equivalent process transformation made using the contents of the specification and drawings of the present application, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A user interface processing method, characterized in that: The method comprises: In response to the application startup instruction, multiple components are created through the component management module, each component being an independent functional module; By means of the component management module, the plurality of components are added to the content view; The plurality of components are activated through the component management module, and the plurality of components are used to display data on a user interface.

2. The method according to claim 1, characterized in that The method further comprises: The data is acquired from a data center through the multiple components and displayed on the user interface.

3. The method according to claim 2, characterized in that The data center is used to maintain the common data mapping table and the observable data mapping table; Correspondingly, the acquiring data from the data center includes: Obtain a unique identifier for said data; The data is searched from the common data mapping table or the observable data mapping table by the unique identifier.

4. The method according to claim 1, characterized in that: The multiple components are also used to obtain external data through the bridge module; The bridge module is configured with a bridge providing interface instance, and the bridge module provides an interface instance for a third party to register and obtain a bridge interface of a corresponding component, and the bridge interface is used to provide the third party with the function of the corresponding component.

5. The method according to claim 4, characterized in that Get external data through the bridge module, including: Passing the external data to the corresponding target component through the bridge module; and The target component that receives the external data is recorded, and the record is provided to other components so that the data of the other components can be updated.

6. The method according to claim 5, characterized in that The multiple components interact with each other through the service module.

7. The method according to claim 6, characterized in that The service module is configured with a logical interface; The logic interface is used to connect various components.

8. The method according to claim 1, characterized in that The method further comprises: Through the hook processing method, the life cycles of the multiple components and the component management module are bound to each other.

9. A user interface processing device, characterized in that: The device comprises: A creation module, used to create multiple components through a component management module in response to an application startup instruction, each component being an independent functional module; An adding module, used for adding the plurality of components to the content view through the component management module; The activation module is used to activate the multiple components through the component management module, and the multiple components are used to display data on the user interface.

10. A computer device, characterized in that: include: at least one processor; and a memory communicatively connected to the at least one processor; wherein: The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and when the computer instructions are executed by a processor, the method according to any one of claims 1 to 8 is implemented.

12. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to claims 1 to 8 are implemented.

13. A user interface processing system, characterized in that: The system comprises: The component management module is used to create multiple components, each of which is an independent functional module; A content view, built in or coupled to the component management module, and loading the multiple components through the component management module; a data center for providing internal data to one or more of the plurality of components; A bridge module, configured with a bridge-provided interface instance, for transferring external data to any one of the plurality of components; and The service module is configured with a logical interface, and the logical interface is used to connect various components for interaction between the various components.

Images