CN114265652B - UI interface display method and device, cloud server and storage medium - Google Patents
UI interface display method and device, cloud server and storage medium Download PDFInfo
- Publication number
- CN114265652B CN114265652B CN202111531854.9A CN202111531854A CN114265652B CN 114265652 B CN114265652 B CN 114265652B CN 202111531854 A CN202111531854 A CN 202111531854A CN 114265652 B CN114265652 B CN 114265652B
- Authority
- CN
- China
- Prior art keywords
- target
- interface
- service
- file
- service module
- 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
- 238000000034 method Methods 0.000 title claims abstract description 65
- 230000008569 process Effects 0.000 claims abstract description 39
- 230000005540 biological transmission Effects 0.000 claims description 11
- 230000003993 interaction Effects 0.000 claims description 11
- 230000001960 triggered effect Effects 0.000 claims description 5
- 238000011161 development Methods 0.000 abstract description 12
- 230000006870 function Effects 0.000 description 37
- 238000010586 diagram Methods 0.000 description 20
- 230000006399 behavior Effects 0.000 description 11
- 238000004891 communication Methods 0.000 description 6
- 230000000694 effects Effects 0.000 description 3
- 230000002452 interceptive effect Effects 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- FFBHFFJDDLITSX-UHFFFAOYSA-N benzyl N-[2-hydroxy-4-(3-oxomorpholin-4-yl)phenyl]carbamate Chemical compound OC1=C(NC(=O)OCC2=CC=CC=C2)C=CC(=C1)N1CCOCC1=O FFBHFFJDDLITSX-UHFFFAOYSA-N 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Landscapes
- User Interface Of Digital Computer (AREA)
Abstract
The application provides a UI interface display method, a device, a cloud server and a storage medium, wherein the cloud server is provided with a cloud service product comprising a plurality of service modules and a UI service, the UI service provides a plurality of UI interfaces shared by the plurality of service modules, and the running process of the UI service is different from the running process of the plurality of service modules. The target service module is used for sending a call request for calling the target UI interface to the UI service, wherein the call request comprises input configuration parameters corresponding to the target UI interface. And the UI service is used for displaying the target UI interface according to the input configuration parameters and feeding back the output result information of the target UI interface to the target service module. The UI display function required by a plurality of service modules is provided by a single UI service, so that all the service modules multiplex the UI interface provided by the UI service, and the UI development cost is reduced.
Description
Technical Field
The present application relates to the field of cloud computing technologies, and in particular, to a UI interface display method, a device, a cloud server, and a storage medium.
Background
With the continuous development of cloud computing technology, more and more users choose to use resources provided by cloud computing manufacturers to deploy their services or directly purchase services provided by cloud computing manufacturers, such as cloud desktops and some cloud application products.
Current cloud desktops and cloud application products often run in a virtual machine environment, and can involve development inside an operating system in a virtual machine on the cloud. Generally, these cloud desktops and cloud applications mostly run in the background in a system service mode, but some functions or some scenes need to pop up some UI prompts, such as file selection dialog boxes, download progress bars, service abnormality prompts, etc., on interfaces. In practical applications, the display of these UI interfaces is often performed by different processes, and if each process develops its own UI display code, the workload is large. Moreover, the display of the UI interface and the corresponding service are all running in the same process, and if the UI interface displays the code abnormally, the corresponding service is often not normally running.
Disclosure of Invention
The embodiment of the invention provides a UI (user interface) display method, a device, a cloud server and a storage medium, which are used for reducing UI development cost of different service modules in a cloud service product and ensuring operation reliability of the service modules.
In a first aspect, an embodiment of the present invention provides a UI interface display method, which is applied to a UI service of a cloud service product, where the method includes:
receiving a call request for a target service module in the cloud service product to call a target UI (user interface), wherein the call request comprises input configuration parameters corresponding to the target UI; the target service module is any one of a plurality of service modules contained in the cloud service product, a plurality of UI interfaces shared by the plurality of service modules are provided in the UI service, the target UI interface is one of the plurality of UI interfaces, and the process in which the UI service operates is different from the process in which the plurality of service modules operate respectively;
displaying the target UI according to the input configuration parameters;
and feeding back the output result information of the target UI interface to the target service module.
In a second aspect, an embodiment of the present invention provides a UI interface display device, located in a UI service of a cloud service product, where the device includes:
the receiving module is used for receiving a call request of a target UI interface called by a target service module in the cloud service product, wherein the call request comprises input configuration parameters corresponding to the target UI interface; the target service module is any one of a plurality of service modules contained in the cloud service product, a plurality of UI interfaces shared by the plurality of service modules are provided in the UI service, the target UI interface is one of the plurality of UI interfaces, and the process in which the UI service operates is different from the process in which the plurality of service modules operate respectively;
The display module is used for displaying the target UI according to the input configuration parameters;
and the sending module is used for feeding back the output result information of the target UI interface to the target service module.
In a third aspect, an embodiment of the present invention provides a cloud server, including:
the cloud service product comprises a plurality of service modules and UI (user interface) services, wherein the UI services provide a plurality of UI interfaces shared by the plurality of service modules, and the running process of the UI services is different from the running process of the plurality of service modules;
the target service module in the plurality of service modules is used for sending a call request for calling a target UI interface to the UI service, and the call request comprises input configuration parameters corresponding to the target UI interface; receiving output result information of the target UI fed back by the UI service; wherein the target UI interface is one of the plurality of UI interfaces, and the target service module is any one of a plurality of service modules included in the cloud service product;
and the UI service is used for displaying the target UI interface according to the input configuration parameters and feeding back the output result information of the target UI interface to the target service module.
In a fourth aspect, an embodiment of the present invention provides a non-transitory machine-readable storage medium, on which executable code is stored, which when executed by a processor of a cloud server, causes the processor to at least implement the UI interface display method according to the first aspect.
In the embodiment of the invention, a shared UI service is set in the cloud service product, and all the service modules share the UI service, and the process in which the UI service operates is different from the process in which each service module operates. A plurality of UI interfaces for multiplexing all service modules are provided in the UI service. When a certain target service module needs to display a certain UI (called a target UI), a corresponding call request is triggered to the UI service, and the call request carries relevant configuration parameters required to be input for calling the target UI, so that the UI service finishes rendering and displaying the target UI based on the input configuration parameters, and feeds back output result information (such as whether the display is successful or not and the interaction behavior of a user on the interface) of the target UI to the target service module.
By combining the UI display requirements of the service modules, a plurality of UI interfaces with higher use requirements of the service modules are preconfigured in UI service, part of interface elements in the UI interfaces are fixed, and only part of interface elements can be changed along with input configuration parameters of the service modules, so that the difference of the overall visual effect is small when different service modules use the same UI interface, and the consistency of the styles of the UI interfaces is maintained. The UI display requirements of different service modules are independently provided in another independent UI service, all the service modules multiplex the UI interface provided by the UI service in a mode of independent UI service, the UI development cost is reduced, the UI display logic is separated from the service logic of the service modules, and the problem that the service modules cannot normally operate due to abnormal UI display can be avoided.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic diagram of a composition of a cloud service product according to an embodiment of the present invention;
fig. 2 is a schematic functional distribution diagram of a cloud service product according to an embodiment of the present invention;
FIG. 3a is a schematic diagram illustrating a call logic of a file selection dialog type interface according to an embodiment of the present invention;
FIG. 3b is a schematic diagram of a file selection dialog interface according to an embodiment of the present invention;
FIG. 3c is a schematic diagram of another file selection dialog interface according to an embodiment of the present invention;
FIG. 4a is a schematic diagram illustrating a call logic of a file upload and download dialog interface according to an embodiment of the present invention;
FIG. 4b is a schematic diagram of a file upload and download dialog interface according to an embodiment of the present invention;
FIG. 5a is a schematic diagram illustrating a call logic of a message alert dialog type interface according to an embodiment of the present invention;
FIG. 5b is a schematic diagram of a message alert dialog interface according to an embodiment of the present invention;
FIG. 6a is a schematic diagram of a call logic of a custom UI according to an embodiment of the present invention;
FIG. 6b is a schematic diagram of a custom UI according to an embodiment of the present invention;
FIG. 6c is a schematic diagram of interaction behavior corresponding to the UI interface shown in FIG. 6 b;
Fig. 7 is a schematic diagram of a UI interface display process according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of a UI interface display device according to an embodiment of the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments of the present invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
Some embodiments of the present invention are described in detail below with reference to the accompanying drawings. In the case where there is no conflict between the embodiments, the following embodiments and features in the embodiments may be combined with each other. In addition, the sequence of steps in the method embodiments described below is only an example and is not strictly limited.
Cloud computing providers have provided a wide variety of cloud service products for use by users, such as cloud desktops and other cloud applications (applications). Each cloud service product actually includes several service modules, or functional modules, such as an agent (agent) module, a session management module, a Firmware Over-The-Air (Fota) module, and so on. The service modules are responsible for realizing different service logics in corresponding cloud service products, and the UI display requirements are often met in the running process.
At present, one commonly used UI development logic is to put a service module (i.e. its service logic) and its required UI display function into the same process, and this process is responsible for running the service module and executing the corresponding UI display logic. If this process exits abnormally due to the UI display, the corresponding service module is also affected and becomes unavailable. Moreover, if other service modules of a cloud service product also need UI display functions, development and design of the corresponding service modules and their required UI display logic need to be performed in other processes, in fact, if each process individually develops its own UI display code, development workload is large and many works are repeated.
In order to reduce the development cost of the UI and ensure the reliable operation of the service module, the embodiment of the invention provides a new UI construction and use framework. In summary, in the scheme provided by the embodiment of the invention, an independent UI service is constructed in the cloud service product, and the UI display function is decoupled from each service module in the cloud service product, i.e. any problem occurs in the UI service, and normal service modules are not affected. In addition, the UI service can provide UI display functions for all the service modules in the cloud service product, each service module does not need to develop the corresponding UI display function independently, and development cost is reduced.
Fig. 1 is a schematic composition diagram of a cloud service product according to an embodiment of the present invention, where, as shown in fig. 1, the cloud service product includes: a plurality of service modules and UI services. In practical applications, the cloud service product may run in a cloud server in the cloud, for example, in a virtual machine in the cloud server.
In fig. 1, the UI Service is represented as GUI-Service, which is responsible for all UI-related display functions, supporting display requirements of various UI interfaces from multiple clients.
In fig. 1, the plurality of service modules is represented as n service modules as follows: biz-Service-1, biz-Service-2, …, biz-Service-n. The clients are a plurality of service modules. The Service modules are mainly responsible for realizing different Service functions of the whole cloud Service product, and when the UI needs to be displayed, the corresponding UI interface is displayed by calling the GUI-Service.
As shown in fig. 1, different Service modules run in different processes, such as process 1, process 2, …, process n, illustrated in the figure, and GUI-Service runs in another independent process, such as process Z, illustrated in fig. 1.
In an alternative embodiment, as shown in FIG. 1, the Service module may interact with GUI-Service by way of a remote procedure call (Remote Procedure Call, gRPC for short) for example. gRPC communication, which is an efficient communication framework with small data transmission amount and low delay, can reduce the delay of UI display caused by cross-process communication.
Of course, in practical application, other communication modes may be adopted to implement communication between the service module and the UI service according to the requirement, such as pipeline, socket communication, shared memory, and so on.
In addition, in practical applications, a plurality of Service modules included in a cloud Service product may mostly operate in a system Service manner, that is, most of Service modules provide a system (operating system) level Service and operate in a kernel mode with system rights, because the Service modules require the system rights to complete corresponding functions, and for safety reasons, as shown in fig. 2, a UI Service (i.e., GUI-Service in the drawing) may operate in a user mode, so that some operations that jeopardize the safe operation of the system can be avoided from being performed on the UI interface by the system rights by a user.
In the embodiment of the invention, since the UI service independently operates to provide a unified UI display function for each service module in the cloud service product, namely, the UI display function provided by the UI service is multiplexed by each service module, the UI display function commonly used by a plurality of service modules can be abstracted, some UI interfaces with higher abstract use rate can be configured in the UI service for each service module to call.
As shown in fig. 1, a plurality of UI interfaces commonly used can be obtained by abstracting UI functions commonly used by a plurality of service modules, and the UI interfaces mainly comprise the following three types: a file selection dialog box type interface, a file upload and download dialog box interface, and a message prompt dialog box type interface. These three types of UI interfaces can basically satisfy the UI display functions required for more than 90% of cloud product services. In order to cope with the situation that some service modules have special UI display requirements and the three types of UI interfaces cannot meet the display requirements, one special type of UI interface, called a custom UI interface, may be further included in the multiple UI interfaces provided by the UI service.
In practical application, various types of UI interfaces provided by the UI service in the cloud service product are used by each service module in the cloud service product, unified design development is carried out on each UI interface multiplexed by a plurality of service modules at the UI service side, the same type of UI interfaces used by the plurality of service modules can be ensured to have consistent overall style, and meanwhile, style consistency among different types of UI interfaces can be considered, so that the style of the UI interfaces is consistent with the style of the service modules. The style of the UI reflects the overall layout and visual characteristics of the interface.
It will be appreciated that many of the three types of UI interfaces illustrated above may include interface elements such as text, buttons, selection boxes, text boxes, and the like. Interface elements can be divided into two categories from the point of view of their stability or variability: fixed elements and variable elements. These fixed elements reflect the overall layout, style characteristics of the interface, such as the color, length, width of the text box, the background color of the entire interface, the color, length, width of the progress bar, etc. The change elements are basically related to different service modules, that is, when the different service modules call the same type of interface, some interface elements in the interface can be adjusted according to requirements so as to be matched with the call requirements triggered when the user executes a certain service function, for example, some text contents displayed in the interface are changed.
Based on this, after a plurality of UI interfaces are designed in the UI service, in order for each service module to use the UI interfaces, each service module needs to be informed of the existence of the UI interfaces and what types of parameters need to be input when calling. As can be seen from the description of the fixed elements and the variable elements, in practice, when the service module invokes the UI interface, parameters to be input often correspond to the variable elements, and of course, some parameters related to control management and interface selection need to be input. The UI service may abstract the corresponding call interface parameters (i.e. the parameter types to be input) for each UI interface, and inform each service module, so that when the service module calls a UI interface of a certain type, the service module inputs the corresponding configuration parameters according to the corresponding parameter types.
The parameters that need to be entered for different types of interfaces will be exemplified below. Here, it is assumed that the service module already knows the type of parameter to be input when each UI interface is called, and when the target UI interface (one of multiple UI interfaces) needs to be called, a call request including the input configuration parameter corresponding to the target UI interface is triggered to the UI service for the target service module (any one of multiple service modules), where the input configuration parameter is determined according to the known type of parameter to be input when the target UI interface is called. After receiving the call request, the UI service displays a corresponding target UI interface based on the input configuration parameters carried in the call request, and further feeds output result information of the target UI interface back to the target service module. The output result information may include status information for reflecting whether the target UI interface can be successfully displayed. In addition, if the user triggers some interactive actions in the displayed target UI interface, the UI service also responds to the interactive actions and feeds back the interactive action information triggered by the user on the target UI interface to the target service module.
In summary, three dialog interfaces commonly used can be provided in the UI service, and abstractions of calling input parameters and output information can be performed, so that for the UI service, basic function display of the dialog interfaces of corresponding types can be satisfied through the input of some basic and important parameters, and thus the UI service does not need to expose all UI capabilities of the UI interface to each service module, i.e. the service module does not need to care about related information of some fixed interface elements in the UI interface, interaction between the service module and the UI service is simplified, and the transmission data volume between the service module and the UI service is reduced.
The above description is briefly introduced for three dialog interfaces, and for the three dialog interfaces, it is actually equivalent to that the three dialog interfaces have been already constructed in the UI service, and the service module only needs to call as needed and fine tune some interface elements therein. However, when the UI functions required to be used by the service module are beyond the coverage of the three dialog interfaces, the service module may also customize the private UI functions based on the custom UI interface provided by the UI service. In short, when the service module needs to perform UI display, if the service module finds that there are no UI interfaces required by the UI interfaces in the multiple dialog box interfaces that the UI service can provide, the user-defined UI interface is called, and a plurality of UI controls configured locally are sent to the UI service, so that the UI service displays the plurality of UI controls in the user-defined UI interface according to the configuration information corresponding to each UI control, receives interaction behaviors of the user, and feeds back the interaction behaviors to the service module.
The above has briefly described the various UI interfaces that the UI service can provide and the procedure in which the service module invokes the UI interfaces, and the following exemplary description is made of the functions of the various UI interfaces and the types of parameters that need to be input in conjunction with the following embodiments.
Fig. 3a is a schematic diagram of a call logic of a file selection dialog type interface according to an embodiment of the present invention, as shown in fig. 3a, when a target service module wants to call a UI interface of a file selection dialog type, parameters (params) types that need to be input include: request identification (id), file operation type (type), interface title (title). And the output results (return) that the UI service needs to feed back to the service module may include: interface display status (status), file-path (file-path).
When a certain UI interface (called a target UI interface) provided by the UI service is called, the target service module triggers a call request corresponding to the target UI interface to the UI service. It is assumed here that the target service module invokes a file selection dialog type interface, and it will be appreciated that the identity of the interface type may be sent to the UI service in association with the invocation request, which may be the inclusion of the interface type identity in the invocation request. The parameter types required to be input by the file selection dialog box type interface as illustrated in fig. 3a, the call request also needs to include an input configuration parameter determined by the target service module according to the input parameter types, that is, the input configuration parameter includes a request identifier corresponding to the call request, interface title information and a target file operation type selected from known multiple file operation types.
The request identifier is used for identifying which service module triggers the call request and what UI interface is called by the call request. Because the UI service is shared by multiple service modules, and different service modules may all trigger a call request of the UI interface to the UI service, in order to identify each call request sent by each service module, the service module needs to generate the request identifier to be carried in the call request.
The file operation type refers to that in the interfaces such as a file selection dialog box, file selection dialog box interfaces (namely, specific UI interfaces included in one type) corresponding to different file operation types can be provided according to the commonly used file operation types. Common file operation types include file selection and file save, so two file selection dialog interfaces can be set: file selection dialog interface a, file save dialog interface B. The two file operation types are informed to each service module in advance, so that the target service module can select the required file operation type according to the requirement of the currently executed service logic, for example, a certain file is required to be selected currently, and the file selection operation is selected; if a file is currently required to be saved, a file save operation is selected.
The interface title refers to interface title information which can be customized by the target service module based on the operation type of the target file selected by the target service module.
When the UI service receives the call request including the input configuration parameter, it is known that the target service module currently needs to use the target file selection dialog box interface (for example, the file selection dialog box interface a or the file saving dialog box interface B) corresponding to the target file operation type, and then the target file selection dialog box interface is displayed, and the interface title information customized by the target service module is displayed at the title information position of the interface.
Based on the successful display of the target file selection dialog interface, the user may perform a corresponding file selection or file save operation in the target file selection dialog interface. In any operation, a corresponding file operation path (such as a file selection path and a file storage path) is actually displayed in the target file selection dialog box interface, and when the user confirms that the operation is completed, the UI service may learn that output result information needs to be fed back to the target service module based on the request identifier, where the output result information may include the file operation path and may also include a display state (such as successful display) of the target file selection dialog box interface. It will be appreciated that if the target file selection dialog interface is not successfully displayed, then there will be no subsequent user input of the file operation path, and only feedback of the display status information, such as failure of the interface display, will occur.
Fig. 3B and 3c illustrate two specific file selection dialog type interfaces, respectively, referred to as a file selection dialog interface a and a file save dialog interface B.
In fig. 3b, it is assumed that interface title information input by the target service module is: opening. It is assumed that the file selection dialog interface a contains a text box 301 for displaying the file selection path and a text box 302 for displaying the file name that is finally selected. Based on the user's file selection behavior, a corresponding file selection path is displayed in text box 301 and the file name of the final selected file is displayed in text box 302. When the user clicks an "open" button in the drawing, the UI service feeds back output result information including the file selection path and the file name to the target service module.
In fig. 3c, it is assumed that interface title information input by the target service module is: the other is stored. It is assumed that a text box 303 for displaying a file save path, a text box 304 for displaying a file name of a saved file, and a selection box 305 for selecting a file save type are included in the file save dialog interface B. Based on the user's file save behavior, the corresponding file save path will be displayed in text box 303, and the final named file name will be displayed in text box 304, and the selected file save type will be displayed in selection box 305. When the user clicks a "save" button in the drawing, the UI service feeds back output result information including the file save path, file name, and file save type to the target service module.
Fig. 4a is a schematic diagram of a call logic of a file upload and download dialog interface according to an embodiment of the present invention, as shown in fig. 4a, when a target service module wants to call the file upload and download dialog interface, parameters (params) types that need to be input include: request identification (id), interface title (title), file description information (content), transmission progress information (fraction). And the output results (return) that the UI service needs to feed back to the service module may include: interface display status (status). Optionally, a subtitle (subtitle) may be further included in the input parameter type. The file description information is used for describing the file name which is being uploaded or downloaded.
The meaning of the different parameter types described above is illustrated in connection with fig. 4 b.
In fig. 4b, it is assumed that interface title information input by the target service module is: the file description information is (file name): abcdefgtrwh.rar, the transmission progress information is: 60%, the subtitle information is: the 1 st file is being uploaded, 1 in total.
Based on the above assumption, as shown in fig. 4b, in the file upload and download dialog interface, text content for displaying interface title information may become: 60% completed; the text content for displaying the subtitles becomes: 1 st file is uploaded, and 1 file is totally uploaded; the text content for displaying the file description information becomes: abcdefgtrwh. The color area in the progress bar representing the completed progress is rendered as an effect matching the 60% progress. When the user clicks a pause button in the figure in the file downloading or uploading process, the UI service feeds back output result information including a pause downloading or uploading instruction to the target service module, and of course, when the interface is successfully displayed or cannot be displayed, the UI service feeds back corresponding display state information to the target service module.
Fig. 5a is a schematic diagram of a call logic of a message prompt dialog type interface according to an embodiment of the present invention, where, as shown in fig. 5a, when a target service module wants to call the message prompt dialog type interface, parameters (parameters) types that need to be input include: request identification (id), message hint type (type), interface title (title), hint message content (content). And the output results (return) that the UI service needs to feed back to the service module may include: interface display status (status).
The preset message prompt types may include, for example, those illustrated in the drawings: error alert type (error), alert type (warning), general alert type (tip).
Fig. 5b illustrates the interface display effect when the user selects the error type of prompt. In fig. 5b, it is assumed that the target service module is transmitting a certain file, and an abnormal error occurs in the transmission process, and at this time, a corresponding message prompt interface needs to be called to perform error prompt. The input interface title information is assumed to be: file transmission, wherein the content of the input prompt message is as follows: this file exceeds the upper limit of the file size allowed for transmission. Then in the message alert interface corresponding to the error type "file transfer" is displayed at the text position for displaying the interface title and "this file exceeds the upper limit of the file size allowed to be transferred" is displayed at the text position for displaying the alert message content.
Fig. 6a is a schematic diagram of a call logic of a custom UI according to an embodiment of the present invention, as shown in fig. 6a, when a target service module wants to call the custom UI, parameters (parameters) types that need to be input include: request identification (id) and custom UI control List (List < common control >). And the output results (return) that the UI service needs to feed back to the service module may include: list indicating UI control states in the UI control list: (List < common control status >).
In the embodiment of the present invention, two interface functions may be defined, which are respectively called a first interface function (such as common control) and a second interface function (such as common control status), and are supported in each service module and UI service, where the first interface function is used to transmit relevant configuration information of multiple UI controls customized by the service module between the service module and the UI service, and the second interface function is used to transmit display result states of multiple UI controls and modified configuration information between the UI service and the service module, where modification of configuration information of one UI control mainly refers to a change result of user interaction behavior on the UI control, for example, in a text box that is not originally filled with content or is filled with initial default content, and then the configuration information of the text box corresponding to the filled content is modified as follows: new text content entered by the user.
In the first interface function, a plurality of UI controls and configuration functions of the controls are supported, such as configuration functions of a plurality of UI controls including Text (Text), a selection box (CheckBox), a picture (Image), a Text box (TextEdit), a Button (Button), and the like, wherein the configuration functions are simply the configuration of attributes and attribute values of each UI control, and the attributes include Text content, color, width, length, height, background color, display position, and the like.
In practical application, since the number of the same UI control in a UI interface may be multiple and may include multiple different UI controls in the process of customizing one UI interface, in order to distinguish each UI control, when the service module configures the UI control in a customized manner, an index identifier (index) may be allocated to each configured UI control, so as to uniquely identify one UI control in the UI interface. Based on this, for the target service module, each required UI control may be selected according to the actual service requirement, and relevant attribute values may be configured as required, and unique index identifiers may be allocated to each UI control, after the configuration operations are completed, the configuration result may be encapsulated by the first interface function, so as to trigger, for the UI service, a call request corresponding to the custom UI interface through the first interface function, where the call request includes configuration information from the plurality of UI controls corresponding to the first interface function and the index identifier of each UI control.
After receiving the call request, the UI service analyzes the configuration information of each UI control, and renders and displays the configuration information of each UI control in the user-defined UI interface.
The display result of the custom UI interface is illustrated with reference to fig. 6 b. In fig. 6b, it is assumed that the target service module is configured with several UI controls: the text content is "user name: "text 601; a text box 602 for entering a user name, the initially configured text box content being empty; the text content is "password: "text 603; a text box 604 for entering a login password, the initially configured text box having blank contents; and a confirm button 605. And as shown in fig. 6b, assume that the index identifications of the 5 UI controls described above are in order: index1, index2, index3, index4, index5.
After displaying the custom UI interface as shown in fig. 6b, optionally, at this time, the UI service may feed back status information successfully displayed by its custom UI interface to the target service module, and then the user may perform an input operation of a user name and a login password in the interface.
As shown in fig. 6c, assume that the user enters a user name of "plum somewhere" and a login password of "123456". Based on the user's input behavior, some attribute values of the text boxes 602 and 604 are changed, i.e., the text content therein is changed from the original blank content to the content input by the user. Based on this, after the user clicks the confirm button 605, the UI service may feed back the index identification of the UI control whose attribute value has been changed and the changed attribute value to the target service module.
In the above example, the UI service may feed back the result information of the following interaction behavior to the target service module: [ index2, plum; index4,123456]. After receiving the feedback information, the target service module knows that the user name input by the user is 'Lishiqi' and the login password is '123456' based on the two index identifiers, so that subsequent login checking processing can be performed.
The UI service may call the second interface function, encapsulate the index identifier of the UI control and the modified attribute value thereof, so as to feed back a list containing the index identifier of each modified UI control and the modified attribute value thereof to the target service module through the second interface function, and the target service module analyzes the index identifier and the modified attribute value.
In summary, by constructing the UI service independently running in a certain process in the cloud service product, decoupling the UI display from each service module in the cloud service product, and configuring each service module to multiplex various commonly used UI interfaces provided by the UI service, development cost of the UI interfaces can be reduced, and normal running of the service modules is also facilitated.
Fig. 7 is a flowchart of a UI interface display method according to an embodiment of the present invention, which may be performed by a UI service of a cloud service product, as shown in fig. 7, and includes the steps of:
701. And receiving a call request for calling the target UI interface by the target service module in the cloud service product, wherein the call request comprises input configuration parameters corresponding to the target UI interface.
The target service module is any one of a plurality of service modules contained in the cloud service product, a plurality of UI interfaces shared by the plurality of service modules are provided in the UI service, the target UI interface is one of the plurality of UI interfaces, and the running process of the UI service is different from the running process of the plurality of service modules.
702. And displaying a target UI interface according to the input configuration parameters.
703. And feeding back the output result information of the target UI interface to the target service module.
The specific implementation process of the solution provided in this embodiment may refer to the related description in the foregoing embodiment, which is not repeated here.
A UI interface display device of one or more embodiments of the present invention will be described in detail below. Those skilled in the art will appreciate that these means may be configured by the steps taught by the present solution using commercially available hardware components.
Fig. 8 is a schematic structural diagram of a UI interface display device according to an embodiment of the present invention, where the device corresponds to a UI service in a cloud service product, and as shown in fig. 8, the device includes: a receiving module 11, a display module 12, and a transmitting module 13.
The receiving module 11 is configured to receive a call request for a target service module in the cloud service product to call a target UI interface, where the call request includes an input configuration parameter corresponding to the target UI interface; the target service module is any one of a plurality of service modules contained in the cloud service product, a plurality of UI interfaces shared by the plurality of service modules are provided in the UI service, the target UI interface is one of the plurality of UI interfaces, and the process in which the UI service operates is different from the process in which the plurality of service modules operate respectively.
And the display module 12 is used for displaying the target UI interface according to the input configuration parameters.
And the sending module 13 is used for feeding back the output result information of the target UI interface to the target service module.
Optionally, the UI service operates in a user mode.
Optionally, the sending module 13 is further configured to: and notifying the multiple service modules of the parameter types which are required to be input by using the multiple UI interfaces respectively, so that the target service module determines the input configuration parameters according to the parameter types corresponding to the target UI interfaces.
Optionally, the target UI interface is a file selection dialog box type interface, and the input configuration parameters include a request identifier corresponding to the call request, interface title information, and a target file operation type selected from a plurality of known file operation types. At this time, the display module 12 specifically functions to: and displaying the interface title information in a target file selection dialog box interface corresponding to the target file operation type, wherein the target file selection dialog box interface comprises a file path operation box corresponding to the target file operation type. The sending module is further configured to: and receiving a file operation path input by a user in the file path operation box. The sending module is specifically configured to: and feeding back the file operation path to the target service module according to the request identification.
Optionally, the target UI interface is a file upload and download dialog box interface, and the input configuration parameters include a request identifier corresponding to the call request, interface title information, uploaded or downloaded file description information, and transmission progress information. At this time, the display module 12 specifically functions to: and displaying the interface title information, the file description information and the transmission progress information in the file uploading and downloading dialog box interface. The sending module is specifically configured to: and feeding back the display state of the file uploading and downloading dialog box interface to the target service module according to the request identification.
Optionally, the target UI interface is a message prompt dialog box type interface, and the input configuration parameters include a request identifier corresponding to the call request, interface title information, prompt message content, and a target message prompt type selected from a plurality of known message prompt types. At this time, the display module 12 specifically functions to: in the target message prompt interface corresponding to the target message prompt type, displaying the interface title information and the prompt message content, wherein the sending module is specifically configured to: and feeding back the display state of the target message prompt interface to the target service module according to the request identification.
Optionally, the target UI interface is a custom UI interface, and the input configuration parameter includes a request identifier corresponding to the call request, a plurality of UI controls configured by the target service module in a custom manner, and index identifiers corresponding to the plurality of UI controls. At this time, the display module 12 specifically functions to: and displaying the plurality of UI controls in the user-defined UI interface according to index identifiers corresponding to the plurality of UI controls. The receiving module 11 is further configured to: and receiving interaction behavior information of the user on a target UI control in the plurality of UI controls. The sending module 13 is further configured to: and feeding back the display state of the user-defined UI interface, the index identifier corresponding to the target UI control and the interaction behavior information to the target service module according to the request identifier.
The apparatus shown in fig. 8 may perform the steps performed by the UI service in the foregoing embodiments, and detailed performing procedures and technical effects are referred to the descriptions in the foregoing embodiments and are not repeated herein.
In addition, embodiments of the present invention provide a non-transitory machine-readable storage medium having executable code stored thereon, which when executed by a processor of a cloud server, causes the processor to at least implement the steps performed by a UI service as in the previous embodiments.
The above described apparatus embodiments are merely illustrative, wherein the network elements illustrated as separate components may or may not be physically separate. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
From the above description of the embodiments, it will be apparent to those skilled in the art that the embodiments may be implemented by adding necessary general purpose hardware platforms, or may be implemented by a combination of hardware and software. Based on such understanding, the foregoing aspects, in essence and portions contributing to the art, may be embodied in the form of a computer program product, which may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present invention, and are not limiting; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims (13)
1. A UI interface display method, characterized by being applied to a UI service of a cloud service product, comprising:
receiving a call request for a target service module in the cloud service product to call a target UI (user interface), wherein the call request comprises input configuration parameters corresponding to the target UI; the target service module is any one of a plurality of service modules contained in the cloud service product, a plurality of UI interfaces shared by the plurality of service modules are provided in the UI service, the target UI interface is one of the plurality of UI interfaces, and the process in which the UI service operates is different from the process in which the plurality of service modules operate respectively;
displaying the target UI according to the input configuration parameters;
and feeding back the output result information of the target UI interface to the target service module.
2. The method of claim 1, wherein the UI service operates in a user state.
3. The method according to claim 1, wherein the method further comprises:
and notifying the multiple service modules of the parameter types which are required to be input by using the multiple UI interfaces respectively, so that the target service module determines the input configuration parameters according to the parameter types corresponding to the target UI interfaces.
4. The method of claim 1, wherein the receiving a call request from a target service module in the cloud service product to call a target UI interface comprises:
and receiving a call request for calling the target UI interface, which is triggered by the target service module through a remote procedure call mode.
5. The method according to any one of claims 1 to 4, wherein the target UI interface is a file selection dialog box type interface, and the input configuration parameters include a request identifier corresponding to the call request, interface title information, and a target file operation type selected from a plurality of known file operation types;
the displaying the target UI interface according to the input configuration parameter includes:
displaying the interface title information in a target file selection dialog box interface corresponding to the target file operation type, wherein the target file selection dialog box interface comprises a file path operation box corresponding to the target file operation type;
the step of feeding back the output result information of the target UI interface to the target service module comprises the following steps:
receiving a file operation path input by a user in the file path operation box;
And feeding back the file operation path to the target service module according to the request identification.
6. The method according to any one of claims 1 to 4, wherein the target UI interface is a file upload and download dialog interface, and the input configuration parameters include a request identifier corresponding to the call request, interface title information, uploaded or downloaded file description information, and transmission progress information;
the displaying the target UI interface according to the input configuration parameter includes:
displaying the interface title information, the file description information and the transmission progress information in the file uploading and downloading dialog box interface;
the step of feeding back the output result information of the target UI interface to the target service module comprises the following steps:
and feeding back the display state of the file uploading and downloading dialog box interface to the target service module according to the request identification.
7. The method according to any one of claims 1 to 4, wherein the target UI interface is a message prompt dialog box type interface, and the input configuration parameters include a request identifier corresponding to the call request, interface title information, prompt message content, and a target message prompt type selected from a plurality of known message prompt types;
The displaying the target UI interface according to the input configuration parameter includes:
displaying the interface title information and the prompt message content in a target message prompt interface corresponding to the target message prompt type;
the step of feeding back the output result information of the target UI interface to the target service module comprises the following steps:
and feeding back the display state of the target message prompt interface to the target service module according to the request identification.
8. The method according to any one of claims 1 to 4, wherein the target UI interface is a custom UI interface, and the input configuration parameters include a request identifier corresponding to the call request, a plurality of UI controls configured by the target service module in a custom manner, and index identifiers corresponding to the plurality of UI controls;
the displaying the target UI interface according to the input configuration parameter includes:
in the user-defined UI interface, the plurality of UI controls are displayed according to index identifiers corresponding to the plurality of UI controls respectively;
the step of feeding back the output result information of the target UI interface to the target service module comprises the following steps:
receiving interaction behavior information of a user on a target UI control in the plurality of UI controls;
And feeding back the display state of the user-defined UI interface, the index identifier corresponding to the target UI control and the interaction behavior information to the target service module according to the request identifier.
9. A UI interface display device, characterized by being located in a UI service of a cloud service product, the device comprising:
the receiving module is used for receiving a call request of a target UI interface called by a target service module in the cloud service product, wherein the call request comprises input configuration parameters corresponding to the target UI interface; the target service module is any one of a plurality of service modules contained in the cloud service product, a plurality of UI interfaces shared by the plurality of service modules are provided in the UI service, the target UI interface is one of the plurality of UI interfaces, and the process in which the UI service operates is different from the process in which the plurality of service modules operate respectively;
the display module is used for displaying the target UI according to the input configuration parameters;
and the sending module is used for feeding back the output result information of the target UI interface to the target service module.
10. A cloud server, comprising:
The cloud service product comprises a plurality of service modules and UI (user interface) services, wherein the UI services provide a plurality of UI interfaces shared by the plurality of service modules, and the running process of the UI services is different from the running process of the plurality of service modules;
the target service module in the plurality of service modules is used for sending a call request for calling a target UI interface to the UI service, and the call request comprises input configuration parameters corresponding to the target UI interface; receiving output result information of the target UI fed back by the UI service; wherein the target UI interface is one of the plurality of UI interfaces, and the target service module is any one of a plurality of service modules included in the cloud service product;
and the UI service is used for displaying the target UI interface according to the input configuration parameters and feeding back the output result information of the target UI interface to the target service module.
11. The cloud server of claim 10, wherein the UI service operates in a user mode.
12. The cloud server of claim 10, wherein said plurality of UI interfaces comprises at least one of: a file selection dialog box type interface, a file upload and download dialog box interface, a message prompt dialog box type interface, and a custom UI interface.
13. A non-transitory machine-readable storage medium having executable code stored thereon, which when executed by a processor of a cloud server, causes the processor to perform the UI interface display method of any of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111531854.9A CN114265652B (en) | 2021-12-14 | 2021-12-14 | UI interface display method and device, cloud server and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111531854.9A CN114265652B (en) | 2021-12-14 | 2021-12-14 | UI interface display method and device, cloud server and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114265652A CN114265652A (en) | 2022-04-01 |
| CN114265652B true CN114265652B (en) | 2023-10-31 |
Family
ID=80827263
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111531854.9A Active CN114265652B (en) | 2021-12-14 | 2021-12-14 | UI interface display method and device, cloud server and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114265652B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20150049242A (en) * | 2013-10-29 | 2015-05-08 | 엘지전자 주식회사 | Cloud service interworking apparatus and method thereof |
| CN105027155A (en) * | 2013-03-28 | 2015-11-04 | 高通股份有限公司 | Unifying cloud services for online sharing |
| CN107547753A (en) * | 2017-10-13 | 2018-01-05 | 三星电子（中国）研发中心 | The method and system that a kind of interface customizations are shown |
| CN112394972A (en) * | 2019-08-14 | 2021-02-23 | 北京东土科技股份有限公司 | Cloud application publishing method, device, equipment and storage medium |
| CN113296798A (en) * | 2021-05-31 | 2021-08-24 | 腾讯科技（深圳）有限公司 | Service deployment method, device and readable storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8639747B2 (en) * | 2010-07-01 | 2014-01-28 | Red Hat, Inc. | System and method for providing a cloud computing graphical user interface |
-
2021
- 2021-12-14 CN CN202111531854.9A patent/CN114265652B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105027155A (en) * | 2013-03-28 | 2015-11-04 | 高通股份有限公司 | Unifying cloud services for online sharing |
| KR20150049242A (en) * | 2013-10-29 | 2015-05-08 | 엘지전자 주식회사 | Cloud service interworking apparatus and method thereof |
| CN107547753A (en) * | 2017-10-13 | 2018-01-05 | 三星电子（中国）研发中心 | The method and system that a kind of interface customizations are shown |
| CN112394972A (en) * | 2019-08-14 | 2021-02-23 | 北京东土科技股份有限公司 | Cloud application publishing method, device, equipment and storage medium |
| CN113296798A (en) * | 2021-05-31 | 2021-08-24 | 腾讯科技（深圳）有限公司 | Service deployment method, device and readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114265652A (en) | 2022-04-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20140047429A1 (en) | Directing plug-in updates for a software application to a target audience using manifest parameters | |
| EP2538328A1 (en) | A method of provisioning a cloud-based render farm | |
| CN113663325B (en) | Team creation method, joining method, device and storage medium in virtual scene | |
| US11966795B2 (en) | Method and device for loading minus-one screen, terminal, and computer readable storage medium | |
| US11431563B1 (en) | Intelligent management of cloud infrastructures using a cloud management platform | |
| CN112328390B (en) | Method, device and storage medium for automatically implementing cloud management platform | |
| US20150039515A1 (en) | Interactive product improvement through the use of variants and data gathering reports in a system that can be updated on the fly | |
| CN109032661A (en) | System version method for customizing, device and intelligent terminal | |
| US11755301B2 (en) | Deployment of cloud infrastructures using a cloud management platform | |
| CN107526584B (en) | Data access method and device | |
| CN111078348A (en) | Interface management method, device, equipment and storage medium | |
| CN114265652B (en) | UI interface display method and device, cloud server and storage medium | |
| CN113360160A (en) | Method and device for deploying application, electronic equipment and storage medium | |
| CN113791920A (en) | Dual-system communication method, device, electronic equipment and computer readable storage medium | |
| CN110543343A (en) | Financial interaction page generation method and device based on native android application | |
| CN113157270A (en) | Page adaptation method and device | |
| US20130104178A1 (en) | Set top box resource allocation for executing a widget | |
| CN112632917B (en) | Online document processing method and device, electronic equipment and storage medium | |
| CN116954384A (en) | Implementation method and device of custom soft keyboard, electronic equipment and storage medium | |
| CN112099782B (en) | Game development method, device, equipment and storage medium | |
| US20200344305A1 (en) | Commissioning a virtualised network function | |
| CN113434234A (en) | Page jump method, device, computer readable storage medium and processor | |
| CN114327530A (en) | Method and device for updating model file and computing equipment | |
| CN111338617A (en) | Method for centrally controlling linux by using xml and python | |
| CN112187841B (en) | Service hosting method and device based on SaaS platform, electronic equipment and storage medium |
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 |