CN111026366B - User interface implementation method and device, storage medium and electronic equipment - Google Patents
User interface implementation method and device, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN111026366B CN111026366B CN201911101252.2A CN201911101252A CN111026366B CN 111026366 B CN111026366 B CN 111026366B CN 201911101252 A CN201911101252 A CN 201911101252A CN 111026366 B CN111026366 B CN 111026366B
- Authority
- CN
- China
- Prior art keywords
- interface
- component
- event
- user interface
- management component
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
- G06F8/24—Object-oriented
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
The application discloses a user interface realization method, a device, a storage medium and electronic equipment, and relates to the user interface design technology. The specific scheme comprises the following steps: the interface management component acquires an interface update event; the interface updating event carries an event type and interface parameters; the interface management component sends the event type and the interface parameters to an event processing component, and the event processing component acquires a pre-realized interface element template from a database according to the event type; and the event processing component realizes interface elements based on the interface parameters and the interface element templates, and the display component updates the user interface in real time according to the interface elements. The application decouples the display function and the interface element definition function, increases the reusability of the user interface design and is more beneficial to debugging faults.
Description
Technical Field
The present application relates to a user interface design technology, and in particular, to a method and apparatus for implementing a user interface, a storage medium, and an electronic device.
Background
The display component is implemented by a wide variety of interface elements and, upon acquisition of an operation on an interface element, the display component also needs to be updated in response to the operation.
In existing user interface design techniques, in order to pursue design efficiency, presentation functions and interface element definition functions are typically implemented in a display component. In this way, the display function and the interface element definition function are coupled, so that the reusability of the user interface design is reduced, and the debugging of faults is not facilitated.
Disclosure of Invention
Therefore, a main object of the present application is to provide a method for implementing a user interface, which can decouple a display function and an interface element definition function, increase the reusability of a user interface design, and facilitate debugging of faults.
In order to achieve the above purpose, the technical scheme provided by the application is as follows:
in a first aspect, an embodiment of the present application provides a method for implementing a user interface, including the following steps:
the interface management component acquires an interface update event; the interface updating event carries an event type and interface parameters;
the interface management component sends the event type and the interface parameters to an event processing component, and the event processing component acquires a pre-realized interface element template from a database according to the event type;
and the event processing component realizes interface elements based on the interface parameters and the interface element templates, and the display component updates the user interface in real time according to the interface elements.
In a possible implementation manner, the step of updating the user interface in real time by the display component according to the interface element includes:
the display component monitors the execution state attribute of the event processing component through the interface management component;
when the execution state attribute is that the execution is successful, the display component acquires the interface element realized by the event processing component through the interface management component;
the display component updates the user interface according to the interface element.
In a possible implementation manner, before the interface management component obtains the interface update event, the method further includes:
implementing an element model in the interface management component;
binding the element model of the interface management component with the interface element of the display component.
In a possible implementation manner, the step of binding the element model of the interface management component and the interface element of the display component includes:
and setting element attributes of the interface elements bound with the element model through the element model.
In a second aspect, an embodiment of the present application further provides a user interface implementation apparatus, including:
the interface management component is used for acquiring an interface update event; the interface updating event carries an event type and interface parameters; and further configured to send the event type and the interface parameter to an event processing component;
the event processing component is used for acquiring a pre-realized interface element template from a database according to the event type; the interface element template is used for realizing interface elements based on the interface parameters and the interface element templates;
and the display component is used for updating the user interface in real time according to the interface elements.
In one possible embodiment, the display assembly includes:
the monitoring module is used for monitoring the execution state attribute of the event processing component through the interface management component;
the acquisition module is used for acquiring interface elements realized by the event processing component through the interface management component when the execution state attribute is that the execution is successful;
and the updating module is used for updating the user interface according to the interface element.
In a possible implementation manner, the interface management component implements an element model therein;
the interface management component further comprises:
and the binding module is used for binding the element model and the interface element of the display component.
In a possible implementation manner, the interface management component further comprises:
and the attribute setting module is used for setting the element attribute of the interface element bound with the element model through the element model.
In a third aspect, embodiments of the present application also provide a computer-readable storage medium. The specific scheme is as follows:
a computer readable storage medium storing computer instructions which when executed by a processor perform the steps of any one of the possible implementations of the first aspect and the first aspect.
In a fourth aspect, the embodiment of the application further provides electronic equipment. The specific scheme is as follows:
an electronic device, the electronic device comprising:
a processor;
a memory for storing the processor-executable instructions;
the processor is configured to read the executable instructions from the memory and execute the instructions to implement the steps of any one of the foregoing first aspect and any possible implementation manner of the first aspect.
In summary, the application provides a user interface implementation method, a device, a storage medium and an electronic apparatus. The application adds an interface management component and an event processing component, uses the interface management component to acquire an interface update event, uses the event processing component to realize an interface element, and finally uses the display component to update a user interface. The presentation function and the interface element definition function are decoupled by adding an interface management component and an event processing component. Further, the interface elements are implemented using event handling components, increasing the reusability of the user interface design. By adding the interface management component and the event processing component, the realization of the display function and the interface element definition function is separated, and the fault debugging is also facilitated.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort to a person skilled in the art.
FIG. 1 is a flow chart of a method for implementing a user interface according to an embodiment of the present application;
FIG. 2 is a flow chart of steps for updating a user interface while in a user interface implementation method;
fig. 3 is a schematic structural diagram of a user interface implementation device according to an embodiment of the present application;
FIG. 4 is a schematic diagram of a display assembly in a user interface implementation device;
FIG. 5 is a schematic diagram of the structure of an interface management component in a user interface implementation device;
FIG. 6a is a schematic diagram of interface elements in a user interface;
FIG. 6b is a schematic diagram of an element model in an interface management component;
FIG. 7 is a schematic structural diagram of another user interface implementation device according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
The terms "first," "second," "third," "fourth" and the like in the description and in the claims and in the above drawings, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the application described herein may be implemented, for example, in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprise" and "have," as well as any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those elements but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
The core application points of the application are as follows: an interface management component and an event processing component are added, an interface update event is acquired by using the interface management component, interface elements are realized by using the event processing component, and finally a user interface is updated by using a display component. The presentation function and the interface element definition function are decoupled by adding an interface management component and an event handling component. Further, the interface elements are implemented using event handling components, increasing the reusability of the user interface design. By adding the interface management component and the event processing component, the realization of the display function and the interface element definition function is separated, and the fault debugging is also facilitated.
The user interface implementation method provided by the embodiment of the application can be implemented at the client side or the server side. Whether the user interface is implemented at the client or the server, the interface updating event sent by the user interface on the client is acquired, and the user interface on the client is updated through the display component.
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail with specific examples. The following embodiments may be combined with each other, and some embodiments may not be repeated for the same or similar concepts or processes.
Example 1
Fig. 1 is a flow chart of a method for implementing a user interface according to an embodiment of the present application, as shown in fig. 1, where the embodiment mainly includes:
s101: the interface management component acquires an interface update event; the interface update event carries an event type and interface parameters.
The interface management component is a pre-realized component, is abstracted on the basis of the display component and is used for realizing an element model of each interface element in the user interface, and the interface management component is bound with the display component.
The interface management component acquires an interface update event sent by the client, when a user operates a user interface of the client, the interface update event is triggered and sent, and the user interface is updated according to the operation, so that the interface update event is the event triggered when the user interface is operated, and after the interface update event is received, the user interface implementation method provided by the embodiment of the application starts to be executed, and the update operation on the user interface is carried out. By way of example, the operation types of updating the user interface operation may include: refresh user interface, refresh interface element, add interface element, delete interface element, etc.
In order to perform an update operation of the user interface in response to an interface update event, it is necessary to know an operation type of the update user interface operation, and thus, the event type characterizes the operation type of the update user interface operation. In order to complete the updating operation of the user interface, a specific updated interface element and a specific updating parameter need to be obtained, so that the interface parameter characterizes the specific updated interface element and the specific updating parameter. For example, when the interface element is a row in the table and the operation type of the update user interface operation is to delete the interface element, the row number of the row to be deleted in the table needs to be known, and at this time, the interface parameter is the row number of the row to be deleted in the table.
S102: the interface management component sends the event type and the interface parameters to an event processing component, and the event processing component acquires a pre-implemented interface element template from a database according to the event type.
In order to decouple the presentation function and the interface element definition function, the embodiment of the application provides a special event processing component which is specially used for realizing the interface element according to the interface update event.
Thus, the interface management component sends the event type and interface parameters carried by the interface update time to the event processing component. And the event management component acquires a pre-implemented interface element template according to the event type.
The interface element templates are typically stored in a database, and in particular may be stored in a memory of the client, a memory of the server, or in a dedicated cloud memory.
S103: and the event processing component realizes interface elements based on the interface parameters and the interface element templates, and the display component updates the user interface in real time according to the interface elements.
The event processing component sets the interface element template based on the interface element to realize the interface element. The display component updates the user interface in accordance with the interface element implemented by the event processing component. Thus, decoupling of the presentation function and the interface element definition function is achieved. Implementing interface elements using event handling components increases the reusability of user interface designs. By adding the interface management component and the event processing component, the realization of the display function and the interface element definition function is separated, and the fault debugging is also facilitated.
By binding the event processing component and the display component, the display component can update the user interface in real time according to the interface element when the event processing component realizes the interface element. The event processing component and the display component can be directly bound, or the event processing component and the display component can be bound through the interface management component.
Illustratively, when the event processing component and the display component are bound by the interface management component, the display component updates the user interface in real time according to the interface element as shown in fig. 2, including:
s201: the display component monitors the execution state attribute of the event processing component through the interface management component.
Specifically, the event processing component is provided with an execution state attribute, and the execution state attribute is used for representing the running state of the event processing component. The execution state attribute may include states of in-execution, execution success, execution failure, or execution cancellation: when the event processing component is implementing the interface element, the execution state attribute returns to the execution state; when the event processing component finishes realizing the interface element, the execution state attribute returns to the execution success state; when the event processing component realizes that the interface element is abnormal, the execution state attribute returns to the execution failure state; when the execution interface update event is canceled, the execution state attribute returns to the execution canceled state. The interface management component acquires the execution state attribute of the event processing component, and acquires the running state of the event processing component through the execution state attribute. The display component monitors the execution state attribute of the event processing component through the interface management component, and when the interface management component acquires the execution state attribute of the event processing component, the display component monitors the change of the execution state attribute of the event processing component and acquires the execution state attribute of the event processing component.
For example, key-Value observation (KVO) techniques may be employed to effect the monitoring of the execution state attributes of the event processing components. The KVO technology is a lightweight interface technology and can provide a simple and easy-to-use monitoring interface.
S202: and when the execution state attribute is that the execution is successful, the display component acquires the interface element realized by the event processing component through the interface management component.
And when the interface management component acquires the execution state attribute of the event processing component, acquiring the execution parameter returned by the event processing component. Specifically, the event processing component returns different execution parameters for different execution results. When the execution state attribute is that the execution is successful, the event processing component takes the realized interface element as return data; when the execution result is that the execution fails, the event processing component takes the fault information as return data; when the execution status attribute is execution cancel or in execution, no data is returned or the returned data is null.
When the display component monitors that the execution state attribute of the event processing component is successful execution through the interface management component, the display component acquires the return data of the event processing component through the interface management component, and the return data is an interface element for realizing. In order to facilitate the acquisition of the return data, the event processing component may be provided with a return data attribute, and the interface management component acquires the return data of the event processing component according to the return data attribute, and the display component acquires the return data of the event processing component through the interface management component.
The method provided by the embodiment of the application can independently complete functions and independent tests of each component, so that the reusability of each component is improved, and the development efficiency is improved.
S203: the display component updates the user interface according to the interface element.
And after the display component acquires the interface element, updating the user interface in real time according to the interface element.
In order to further separate the display function of the user interface and the implementation function of the interface element, the user interface implementation method provided by the embodiment of the application implements the element model in the interface management component, where the element model is abstracted according to the interface element of the user interface, the interface element is displayed through the display component, the user interface is displayed, and the element model is implementation logic of the interface element.
The element model of the interface management component corresponds to the interface elements displayed in the display component one by one, and the element model of the interface management component and the interface elements of the display component are bound. And when the element model is realized in the interface management component, the element model in the interface management component is updated by the interface element generated by the event processing component, and the interface element in the display component is updated by binding of the interface management component and the display component, so that the display effect of the user interface is updated.
The display effect of the interface element is set through the element attribute, and when the user interface is designed and realized, the display effect of the interface element needs to be set through setting the element attribute. When the interface element abstraction is obtained as an element model, the element attribute of the interface element bound to the element model can be set by setting the element model. And an attribute protocol can be implemented in the interface management component, and the setting mode of the element attribute of the interface element is specified through the attribute protocol. By way of example, setting the element attribute may set the display effect such as the size, color, shape, text, etc. of the interface element, and may also set the interface update event triggered when the interface element is operated.
In a possible implementation manner, a simple and easy-to-use update interface can be further provided in the interface management component, and the client sends an interface update event by calling the update interface. When the developer realizes the generation of the client interface updating event, the interface updating event can be generated by calling the updating interface and sent to the interface management module by the client. When the interface update event is generated by the application update interface, a developer does not need to pay attention to the generation details of the interface update event and only needs to pay attention to the data flow of the interface update event, so that the development process is greatly simplified.
Example two
As shown in fig. 3, a user interface implementation apparatus 300 provided in an embodiment of the present application includes:
an interface management component 301, configured to obtain an interface update event; the interface updating event carries an event type and interface parameters; and further configured to send the event type and the interface parameter to an event processing component;
an event processing component 302, configured to obtain a pre-implemented interface element template from a database according to the event type; the interface element template is used for realizing interface elements based on the interface parameters and the interface element templates;
and the display component 303 is used for updating the user interface in real time according to the interface elements.
The interface management component 301 is respectively connected with the event processing component 302 and the display component 303, and the interface management component 301 obtains an interface update event sent by the client and sends an event type and an interface parameter carried in the interface update event to the event processing component 302. Event processing component 302 implements interface elements based on event type and interface parameters. The display component 303 updates the user interface in real time according to the interface elements.
In one possible implementation, as shown in fig. 4, the display component 303 includes:
a monitoring module 401, configured to monitor, by using the interface management component 301, an execution state attribute of the event processing component 302;
an obtaining module 402, configured to obtain, by using the interface management component 301, an interface element implemented by the event processing component 302 when the execution status attribute is that execution is successful;
an updating module 403, configured to update the user interface according to the interface element.
In the display component 303, the monitor module 401 is connected to the interface management component 301, and monitors the execution state attribute of the event processing component 302 through the interface management component 301. The monitoring module 401 is further connected to the obtaining module 402, and when the execution status attribute is that the execution is successful, the obtaining module 402 is triggered to execute the operation of obtaining the interface element. The acquisition module 402 is further connected to the interface management component 301, and acquires interface elements implemented by the event processing component 302 through the interface management component 301. The acquisition module 402 is further connected to the update module 403, and the acquisition module 402 sends the interface element to the update module 403, and the update module 403 updates the user interface according to the interface element.
In a possible implementation, the interface management component 301 has an element model implemented therein;
as shown in fig. 5, the interface management component 301 further includes:
a binding module 501, configured to bind the element model and an interface element of the display component.
Illustratively, assume that an interface element in a display component comprises: component 1, component 2, header foot, unit 1 and unit 2. The user interface rendered by the display component including the interface element is shown in fig. 6a, the interface element is abstracted to obtain an element model, the component element is abstracted to obtain a component model, the header element is abstracted to obtain a header model, and the unit element is abstracted to obtain a unit model. For the concrete user interface shown in fig. 6b, the element model abstracted from the interface management component includes: component model 1, component model 2, head model, foot model, unit model 1, and unit model 2.
In a possible implementation manner, the interface management component 301 further includes:
and the attribute setting module 502 is configured to set, through the element model, an element attribute of the interface element bound to the element model.
In one possible implementation, as shown in fig. 7, the event processing component 302 is further connected to an interface of the cloud storage 701, and obtains an interface element template from the cloud storage 701.
According to the user interface realization device provided by the embodiment of the application, the display function and the interface element definition function are decoupled by adding the interface management component and the event processing component, the interface element is realized by using the event processing component, the reusability of the user interface design is increased, the realization of the display function and the interface element definition function is separated, and the fault debugging is also facilitated.
Example III
A computer readable storage medium storing instructions that when executed by a processor cause the processor to perform the steps of any of the user interface implementation methods provided by embodiments of the present application. In practice, the computer readable medium may be contained in the apparatus/device/system described in the above embodiments or may exist alone without being assembled into the apparatus/device/system. The computer-readable storage medium carries one or more programs that, when executed, implement steps of any one of the user interface implementation methods provided by the embodiments of the present application according to any one of the user interface implementation devices provided by referring to the embodiments of the present application.
According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example, but is not limited to: portable computer diskette, hard disk, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the foregoing, but are not intended to limit the scope of the application. In the disclosed embodiments, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The method steps of the present application may be implemented by hardware, such as logic gates, switches, application Specific Integrated Circuits (ASIC), programmable logic controllers, embedded microcontrollers, etc., in addition to data processing programs. Such hardware capable of carrying out the methods of the application may therefore also constitute the application.
Example five
The embodiment of the application also provides electronic equipment which can be a computer or a server, wherein any user interface implementation device provided by the embodiment of the application can be integrated. As shown in fig. 8, an electronic device 800 provided by an embodiment of the present application is shown.
The electronic device may comprise one or more processors 801 of a processing core, one or more memories 802 for storing instructions executable by the processors 801. The electronic device may further comprise a power supply 803, an input output unit 804. Those skilled in the art will appreciate that fig. 8 is not intended to be limiting of the electronic device and may include more or fewer components than shown, or may combine certain components, or may be arranged in different components.
Wherein:
the processor 801 is a control part of the electronic device, and uses various interfaces and lines to connect the various parts, read the executable instructions from the memory 802, and execute or execute the instructions stored in the memory 802 to implement the steps of any of the user interface implementation methods provided by the embodiments of the present application.
The memory 802 may be used to store software programs, i.e., programs involved in any of the user interface implementation methods provided by embodiments of the present application.
The processor 801 executes various functional applications and data processing by executing software programs stored in the memory 802. The memory 802 may include a storage program area that may store an operating system, application programs required for at least one function, and the like, and a storage data area; the storage data area may store data or the like that is used according to the needs of the electronic device. In addition, memory 802 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory 802 may also include a memory controller to provide the processor 801 with access to the memory 802.
The electronic device further comprises a power supply 803 for powering the various components, preferably the power supply 803 can be logically coupled to the processor 801 via a power management system such that functions such as managing charging, discharging, and power consumption are performed by the power management system. The power supply 803 may also include one or more of any components, such as a direct current or alternating current power supply, a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator, and the like.
The server may also include an input output unit 804 such as may be used to receive input numeric or character information and to generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control; such as various graphical user interfaces that may be used to display information entered by or provided to a user and a server, which may be composed of graphics, text, icons, video, and any combination thereof.
Any of the user interface implementation methods, devices, storage media and electronic equipment provided by the embodiments of the present application are based on the same design concept, and the technical means in any of the embodiments of the present application may be freely combined, and the combined technical means are still within the protection scope of the present application.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Those skilled in the art will appreciate that the features recited in the various embodiments of the application and/or in the claims may be combined in various combinations and/or combinations even if such combinations or combinations are not explicitly recited in the application. In particular, the features recited in the various embodiments of the application and/or in the claims may be combined in various combinations and/or combinations without departing from the spirit and teachings of the application, all of which are within the scope of the disclosure.
The principles and embodiments of the present application have been described in detail in the present application, the above examples are provided to facilitate understanding of the method of the present application and the core ideas thereof, and are not intended to limit the present application. It will be apparent to those skilled in the art that variations can be made in the present embodiments and applications within the spirit and principles of the application, and any modifications, equivalents, improvements, etc. are intended to be included within the scope of the present application.
Claims (10)
1. A method for implementing a user interface, comprising:
the interface management component acquires an interface update event; the interface updating event carries an event type and interface parameters;
the interface management component sends the event type and the interface parameters to an event processing component, and the event processing component acquires a pre-realized interface element template from a database according to the event type;
the event processing component realizes interface elements based on the interface parameters and the interface element templates, and the display component updates the user interface in real time according to the interface elements so as to realize decoupling of the display function and the interface element definition function of the user interface.
2. The method of claim 1, wherein the step of the display component updating the user interface in real time in accordance with the interface element comprises:
the display component monitors the execution state attribute of the event processing component through the interface management component;
when the execution state attribute is that the execution is successful, the display component acquires the interface element realized by the event processing component through the interface management component;
the display component updates the user interface according to the interface element.
3. The method of claim 1, wherein prior to the interface management component obtaining an interface update event, the method further comprises:
implementing an element model in the interface management component;
binding the element model of the interface management component with the interface element of the display component.
4. The method of claim 3, wherein the step of binding the element model of the interface management component and the interface element of the display component comprises:
and setting element attributes of the interface elements bound with the element model through the element model.
5. A user interface implementation apparatus, comprising:
the interface management component is used for acquiring an interface update event; the interface updating event carries an event type and interface parameters; and further configured to send the event type and the interface parameter to an event processing component;
the event processing component is used for acquiring a pre-realized interface element template from a database according to the event type; the interface element template is used for realizing interface elements based on the interface parameters and the interface element templates;
the display component is used for updating the user interface in real time according to the interface element;
the device implements decoupling of presentation functions and interface element definition functions of a user interface.
6. The apparatus of claim 5, wherein the display assembly comprises:
the monitoring module is used for monitoring the execution state attribute of the event processing component through the interface management component;
the acquisition module is used for acquiring interface elements realized by the event processing component through the interface management component when the execution state attribute is that the execution is successful;
and the updating module is used for updating the user interface according to the interface element.
7. The apparatus of claim 5, wherein the interface management component has an element model implemented therein;
the interface management component further comprises:
and the binding module is used for binding the element model and the interface element of the display component.
8. The apparatus of claim 7, wherein the interface management component further comprises:
and the attribute setting module is used for setting the element attribute of the interface element bound with the element model through the element model.
9. A computer readable storage medium storing computer instructions which, when executed by a processor, implement the steps of the method of any one of claims 1 to 4.
10. An electronic device, comprising:
a processor;
a memory for storing the processor-executable instructions;
the processor is configured to read the executable instructions from the memory and execute the instructions to implement the method of any of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911101252.2A CN111026366B (en) | 2019-11-12 | 2019-11-12 | User interface implementation method and device, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911101252.2A CN111026366B (en) | 2019-11-12 | 2019-11-12 | User interface implementation method and device, storage medium and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111026366A CN111026366A (en) | 2020-04-17 |
| CN111026366B true CN111026366B (en) | 2023-09-22 |
Family
ID=70201420
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911101252.2A Active CN111026366B (en) | 2019-11-12 | 2019-11-12 | User interface implementation method and device, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111026366B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101477461A (en) * | 2009-02-10 | 2009-07-08 | 腾讯科技（深圳）有限公司 | Dynamic generation apparatus and method for application program interface |
| CN102541548A (en) * | 2010-12-23 | 2012-07-04 | 微软公司 | Techniques to customize a user interface for different displays |
| WO2013019497A1 (en) * | 2011-07-29 | 2013-02-07 | Google Inc. | Systems and methods for rendering user interface elements in accordance with a device type |
| CN103425747A (en) * | 2013-07-19 | 2013-12-04 | 百度在线网络技术（北京）有限公司 | Method, device and system for editing webpages in real time |
| CN104111828A (en) * | 2013-04-22 | 2014-10-22 | 易保网络技术(上海)有限公司 | Automatic generation method and system of human-computer interaction interface |
| EP2963543A1 (en) * | 2014-06-30 | 2016-01-06 | Sap Se | User interface generation using a model layer |
| CN107562459A (en) * | 2017-08-29 | 2018-01-09 | 上海雪鲤鱼计算机科技有限公司 | Management system, interface generation/display/operation/display methods, end-of-medium |
| CN109189539A (en) * | 2018-09-03 | 2019-01-11 | 深圳市东微智能科技股份有限公司 | Update method, terminal and the computer readable storage medium at interface |
| CN109614101A (en) * | 2018-11-12 | 2019-04-12 | 深圳和而泰数据资源与云技术有限公司 | Page generation method, system, device, computer equipment and storage medium |
| CN109766158A (en) * | 2018-12-27 | 2019-05-17 | 益萃网络科技（中国）有限公司 | Methods of exhibiting, device, computer equipment and the storage medium of user interface |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7831918B2 (en) * | 2005-09-12 | 2010-11-09 | Microsoft Corporation | Content based user interface design |
| US20120317504A1 (en) * | 2011-06-13 | 2012-12-13 | Microsoft Corporation | Automated user interface object transformation and code generation |
| DE102012221513A1 (en) * | 2011-12-09 | 2013-06-13 | International Business Machines Corp. | Method and system for providing additional data to a graphical interface element |
-
2019
- 2019-11-12 CN CN201911101252.2A patent/CN111026366B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101477461A (en) * | 2009-02-10 | 2009-07-08 | 腾讯科技（深圳）有限公司 | Dynamic generation apparatus and method for application program interface |
| CN102541548A (en) * | 2010-12-23 | 2012-07-04 | 微软公司 | Techniques to customize a user interface for different displays |
| WO2013019497A1 (en) * | 2011-07-29 | 2013-02-07 | Google Inc. | Systems and methods for rendering user interface elements in accordance with a device type |
| CN104111828A (en) * | 2013-04-22 | 2014-10-22 | 易保网络技术(上海)有限公司 | Automatic generation method and system of human-computer interaction interface |
| CN103425747A (en) * | 2013-07-19 | 2013-12-04 | 百度在线网络技术（北京）有限公司 | Method, device and system for editing webpages in real time |
| EP2963543A1 (en) * | 2014-06-30 | 2016-01-06 | Sap Se | User interface generation using a model layer |
| CN107562459A (en) * | 2017-08-29 | 2018-01-09 | 上海雪鲤鱼计算机科技有限公司 | Management system, interface generation/display/operation/display methods, end-of-medium |
| CN109189539A (en) * | 2018-09-03 | 2019-01-11 | 深圳市东微智能科技股份有限公司 | Update method, terminal and the computer readable storage medium at interface |
| CN109614101A (en) * | 2018-11-12 | 2019-04-12 | 深圳和而泰数据资源与云技术有限公司 | Page generation method, system, device, computer equipment and storage medium |
| CN109766158A (en) * | 2018-12-27 | 2019-05-17 | 益萃网络科技（中国）有限公司 | Methods of exhibiting, device, computer equipment and the storage medium of user interface |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111026366A (en) | 2020-04-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109634728B (en) | Job scheduling method and device, terminal equipment and readable storage medium | |
| US8584079B2 (en) | Quality on submit process | |
| CN104737133A (en) | Distributed application optimization using service groups | |
| CN110708362B (en) | Call relation determining method and device, storage medium and electronic equipment | |
| CN111124379B (en) | Page generation method and device, electronic equipment and storage medium | |
| US8918762B2 (en) | Generating test plans and test cases from service-oriented architecture and process models | |
| US8561032B2 (en) | Visualizing thread life time in eclipse | |
| CN111625741A (en) | Page data interaction method and device, storage medium and electronic equipment | |
| CN110661665A (en) | Alarm method based on Internet of things cloud platform, computer storage medium and equipment | |
| CN113364515A (en) | Satellite remote control method, device, equipment and storage medium based on Xstate | |
| RU2554851C2 (en) | Capturing and loading operating system states | |
| CN114625448A (en) | Flow generation method and device combining RPA and AI, electronic equipment and storage medium | |
| CN107577527A (en) | Task generation and scheduling method and device | |
| CN112418447B (en) | System, method, medium, and apparatus for providing machine learning service | |
| CN110134585A (en) | System Test Plan generation method and terminal device | |
| CN111026366B (en) | User interface implementation method and device, storage medium and electronic equipment | |
| CN107203471B (en) | Joint debugging method, service platform and computer storage medium | |
| CN115984022B (en) | Unified account checking method and device for distributed payment system | |
| CN110990177A (en) | Fault repairing method, device, system, storage medium and electronic equipment | |
| CN112181695A (en) | Abnormal application processing method, device, server and storage medium | |
| CN114996955A (en) | Target range environment construction method and device for cloud-originated chaotic engineering experiment | |
| CN108960433B (en) | Method and system for running machine learning modeling process | |
| US9201762B1 (en) | Processor implemented systems and methods for reversible debugging using a replicate process system call | |
| CN111026376B (en) | Function configuration method and device, storage medium and electronic equipment | |
| CN116360800B (en) | Deployment method and device of code branching environment and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |