CN114296845A - Interface processing method, device, electronic device and storage medium - Google Patents

Interface processing method, device, electronic device and storage medium Download PDF

Info

Publication number
CN114296845A
CN114296845A CN202111458533.0A CN202111458533A CN114296845A CN 114296845 A CN114296845 A CN 114296845A CN 202111458533 A CN202111458533 A CN 202111458533A CN 114296845 A CN114296845 A CN 114296845A
Authority
CN
China
Prior art keywords
interface
navigation button
virtual navigation
sub
class object
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.)
Granted
Application number
CN202111458533.0A
Other languages
Chinese (zh)
Other versions
CN114296845B (en
Inventor
徐培培
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Netease Hangzhou Network Co Ltd
Original Assignee
Netease Hangzhou Network Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Netease Hangzhou Network Co Ltd filed Critical Netease Hangzhou Network Co Ltd
Priority to CN202111458533.0A priority Critical patent/CN114296845B/en
Publication of CN114296845A publication Critical patent/CN114296845A/en
Application granted granted Critical
Publication of CN114296845B publication Critical patent/CN114296845B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Landscapes

  • Stored Programmes (AREA)

Abstract

The disclosure specifically discloses an interface processing method, an interface processing device, an electronic device and a storage medium. Wherein, the method comprises the following steps: creating a plug-in manager class object and a main interface class object; analyzing the interface configuration file by using the plug-in manager class object to obtain an analysis result; creating a first interface control and a second interface control in the main interface through the main interface class object; based on the analysis result, a plurality of virtual navigation button objects are created in the first interface control by using the plug-in manager class object and the main interface class object, and a sub-interface corresponding to each virtual navigation button object in the plurality of virtual navigation button objects is determined; and responding to the trigger operation executed on the target virtual navigation button object, and loading a target sub-interface corresponding to the target virtual navigation button object in the second interface control, wherein the target virtual navigation button object is any virtual navigation button object in the plurality of virtual navigation button objects.

Description

Interface processing method, device, electronic device and storage medium
Technical Field
The present disclosure relates to the field of interface processing technologies, and in particular, to an interface processing method and apparatus, an electronic apparatus, and a storage medium.
Background
Currently, a desktop client software interface generally adopts a hierarchical display method, a homepage is provided with a navigation or navigation-like button list, and a sub-interface is accessed by clicking any button. When a cross-platform desktop client is developed, most technical schemes adopt Qt development. In the prior art, a document interface processing scheme based on Qt development is mainly as follows: a main frame page class mainwindow is built in a project, left and right or up and down layout is added to the main frame page class mainwindow, and a navigation interface control class navigation is created and is responsible for creating a plurality of button items. For the secondary modules on the right, different interface classes need to be built in the project. After each button is clicked, a signal is sent to the mainwindow, and then different interface class objects are created and displayed.
The technical scheme has the defects that the code amount of the project becomes large when page switching operation is carried out each time, and the codes of all the sub-interfaces and the main page are integrated in one project, so that the modular management and the parallel development are not facilitated; in addition, once a certain sub-interface module has a problem or needs to be optimized and replaced, the whole project needs to be compiled, the whole application program is updated on the shelf, hot update and upgrade cannot be achieved, and the stability is poor.
In view of the above problems, no effective solution has been proposed.
Disclosure of Invention
The embodiment of the disclosure provides an interface processing method, an interface processing device, an electronic device and a storage medium, which at least solve the technical problems of high engineering development efficiency, large memory space occupation and poor stability caused by the fact that codes of all sub-interfaces and a main page are concentrated in the same engineering and the whole main page needs to be loaded and updated when a user enters or updates the sub-interfaces in the prior art.
According to an aspect of the embodiments of the present disclosure, there is provided an interface processing method, including: creating a plug-in manager class object and a main interface class object; analyzing the interface configuration file by using the plug-in manager class object to obtain an analysis result; creating a first interface control and a second interface control in a main interface through the main interface class object, wherein the first interface control is a navigation interface control, and the second interface control is a sub-interface control; based on the analysis result, creating a plurality of virtual navigation button objects in the first interface control by using the plug-in manager class object and the main interface class object, and determining a sub-interface corresponding to each virtual navigation button object in the plurality of virtual navigation button objects; and responding to a trigger operation executed on a target virtual navigation button object, and loading a target sub-interface corresponding to the target virtual navigation button object in the second interface control, wherein the target virtual navigation button object is any virtual navigation button object in the plurality of virtual navigation button objects.
According to another aspect of the embodiments of the present disclosure, there is also provided an interface processing apparatus, including: the first creating module is used for creating a plug-in manager class object and a main interface class object; the analysis module is used for analyzing the interface configuration file by using the plug-in manager class object to obtain an analysis result; a second creating module, configured to create a first interface control and a second interface control in a main interface through the main interface class object, where the first interface control is a navigation interface control, and the second interface control is a sub-interface control; a first processing module, configured to create, based on the parsing result, a plurality of virtual navigation button objects in the first interface control by using the plug-in manager class object and the main interface class object, and determine a sub-interface corresponding to each of the plurality of virtual navigation button objects; and the second processing module is used for responding to a trigger operation executed on a target virtual navigation button object and loading a target sub-interface corresponding to the target virtual navigation button object in the second interface control, wherein the target virtual navigation button object is any virtual navigation button object in the plurality of virtual navigation button objects.
According to another aspect of the embodiments of the present disclosure, there is also provided a non-volatile storage medium, in which a computer program is stored, where the computer program is configured to execute the interface processing method in any one of the above items when the computer program runs.
According to another aspect of the embodiments of the present disclosure, there is also provided an electronic apparatus, including a memory and a processor, where the memory stores a computer program, and the processor is configured to execute the computer program to perform the interface processing method in any one of the above.
In the embodiment of the disclosure, the method comprises the steps of creating a plug-in manager class object and a main interface class object; analyzing the interface configuration file by using the plug-in manager class object to obtain an analysis result; creating a first interface control and a second interface control in a main interface through the main interface class object, wherein the first interface control is a navigation interface control, and the second interface control is a sub-interface control; based on the analysis result, creating a plurality of virtual navigation button objects in the first interface control by using the plug-in manager class object and the main interface class object, and determining a sub-interface corresponding to each virtual navigation button object in the plurality of virtual navigation button objects; and loading a target sub-interface corresponding to the target virtual navigation button object in the second interface control in response to a trigger operation executed on the target virtual navigation button object, wherein the target virtual navigation button object is any virtual navigation button object in the plurality of virtual navigation button objects, and the purpose of making different sub-interfaces into independent plug-ins and further isolating different sub-interfaces, sub-interfaces and main pages is achieved, so that the technical effects of improving the engineering development efficiency and stability are achieved, and the technical problems of large engineering development efficiency, large memory space occupation and poor stability caused by the fact that codes of all the sub-interfaces and the main pages are concentrated in the same engineering and the whole main page needs to be loaded and updated when a user enters or updates the sub-interfaces in the prior art are solved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the disclosure and together with the description serve to explain the disclosure and not to limit the disclosure. In the drawings:
FIG. 1 is a flow chart of a method of interface processing according to an embodiment of the present disclosure;
FIG. 2 is a schematic diagram of an alternative interface processing method according to an embodiment of the present disclosure;
FIG. 3 is a flow chart of an alternative interface processing method according to an embodiment of the present disclosure;
FIG. 4 is a flow diagram of another alternative interface processing method according to an embodiment of the present disclosure;
FIG. 5 is a flow diagram of another alternative interface processing method according to an embodiment of the present disclosure;
FIG. 6 is a flow diagram of another alternative interface processing method according to an embodiment of the present disclosure;
fig. 7 is a schematic structural diagram of an interface processing apparatus according to an embodiment of the present disclosure.
Detailed Description
In order to make the technical solutions of the present disclosure better understood by those skilled in the art, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are only some embodiments of the present disclosure, not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the disclosure described herein are capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
First, in order to facilitate understanding of the embodiments of the present disclosure, some terms or nouns referred to in the present disclosure will be explained below:
dynamic link library dll: dll is the name of the specified Moh dynamic library. For example, defining a classA { Q _ INTERFACES(ITESTPlugin) } in the project may specify A as a particular class that conforms to the ITESTPlugin interface specification. Wherein ITESTPlugin is a custom interface class.
For example: QPluginLoader, plugloader ("x.dll"); instance () the method can get a qoobject (qt base object), which can be converted into an interface class, and specify it as the implementation of a certain interface, and then convert the object, so as to call the interface provided by itestplug, and the itestplug derived class objects obtained from different dynamic libraries are different, and the implementation of a certain method is also different, so as to create different sub-interfaces.
In accordance with an embodiment of the present disclosure, an interface processing method embodiment is provided, it should be noted that the steps illustrated in the flowchart of the figure may be performed in a computer system such as a set of computer executable instructions, and that while a logical order is illustrated in the flowchart, in some cases the steps illustrated or described may be performed in an order different than here.
The technical scheme of the method embodiment can be executed in a mobile terminal, a computer terminal or a similar arithmetic device. Taking the example of the Mobile terminal running on the Mobile terminal, the Mobile terminal may be a terminal device such as a smart phone (e.g., an Android phone, an iOS phone, etc.), a tablet computer, a palm computer, a Mobile Internet device (MID for short), a PAD, and the like. The mobile terminal may include one or more processors (which may include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a Digital Signal Processing (DSP) chip, a Microprocessor (MCU), a programmable logic device (FPGA), a neural Network Processor (NPU), a Tensor Processor (TPU), an Artificial Intelligence (AI) type processor, etc.) and a memory for storing data. Optionally, the mobile terminal may further include a transmission device, an input/output device, and a display device for a communication function. It will be understood by those skilled in the art that the foregoing structural description is only illustrative and not restrictive of the structure of the mobile terminal. For example, the mobile terminal may also include more or fewer components than described above, or have a different configuration than described above.
The memory may be used to store a computer program, for example, a software program and a module of application software, such as a computer program corresponding to the interface processing method in the embodiments of the present disclosure, and the processor executes various functional applications and data processing by running the computer program stored in the memory, so as to implement the above-mentioned interface processing method. The memory may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory may further include memory located remotely from the processor, and these remote memories may be connected to the mobile terminal through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The display device may be, for example, a touch screen type Liquid Crystal Display (LCD) and a touch display (also referred to as a "touch screen" or "touch display screen"). The liquid crystal display may enable a user to interact with a user interface of the mobile terminal. In some embodiments, the mobile terminal has a Graphical User Interface (GUI) with which a user can interact by touching finger contacts and/or gestures on a touch-sensitive surface, where the human-machine interaction function optionally includes the following interactions: executable instructions for creating web pages, drawing, word processing, making electronic documents, games, video conferencing, instant messaging, emailing, call interfacing, playing digital video, playing digital music, and/or web browsing, etc., for performing the above-described human-computer interaction functions, are configured/stored in one or more processor-executable computer program products or readable non-volatile storage media.
In accordance with an embodiment of the present disclosure, there is provided a method embodiment of interface processing, it being noted that the steps illustrated in the flowchart of the figure may be performed in a computer system such as a set of computer-executable instructions and that, although a logical order is illustrated in the flowchart, in some cases, the steps illustrated or described may be performed in an order different than here.
Fig. 1 is a flowchart of an interface processing method according to an embodiment of the present disclosure, as shown in fig. 1, the method includes the following steps:
step S102, a plug-in manager class object and a main interface class object are created;
step S104, analyzing the interface configuration file by using the plug-in manager class object to obtain an analysis result;
step S106, a first interface control and a second interface control are created in a main interface through the main interface class object, wherein the first interface control is a navigation interface control, and the second interface control is a sub-interface control;
step S108, based on the analysis result, creating a plurality of virtual navigation button objects in the first interface control by using the plug-in manager class object and the main interface class object, and determining a sub-interface corresponding to each virtual navigation button object in the plurality of virtual navigation button objects;
step S110, responding to a trigger operation executed on a target virtual navigation button object, and loading a target sub-interface corresponding to the target virtual navigation button object in the second interface control, where the target virtual navigation button object is any virtual navigation button object in the multiple virtual navigation button objects.
In the embodiment of the disclosure, the method comprises the steps of creating a plug-in manager class object and a main interface class object; analyzing the interface configuration file by using the plug-in manager class object to obtain an analysis result; creating a first interface control and a second interface control in a main interface through the main interface class object, wherein the first interface control is a navigation interface control, and the second interface control is a sub-interface control; based on the analysis result, creating a plurality of virtual navigation button objects in the first interface control by using the plug-in manager class object and the main interface class object, and determining a sub-interface corresponding to each virtual navigation button object in the plurality of virtual navigation button objects; and loading a target sub-interface corresponding to the target virtual navigation button object in the second interface control in response to a trigger operation executed on the target virtual navigation button object, wherein the target virtual navigation button object is any virtual navigation button object in the plurality of virtual navigation button objects, and the purpose of making different sub-interfaces into independent plug-ins and further isolating different sub-interfaces, sub-interfaces and main pages is achieved, so that the technical effects of improving the engineering development efficiency and stability are achieved, and the technical problems of large engineering development efficiency, large memory space occupation and poor stability caused by the fact that codes of all the sub-interfaces and the main pages are concentrated in the same engineering and the whole main page needs to be loaded and updated when a user enters or updates the sub-interfaces in the prior art are solved.
Optionally, the interface configuration file is analyzed; the main interface class object is a main window object and is used for creating a first interface control and a second interface control in a main interface, and is matched with the plug-in manager class object to create a plurality of virtual navigation button objects and determine a sub-interface corresponding to each virtual navigation button object in the plurality of virtual navigation button objects.
Optionally, the first interface control is a navigation interface control, and is configured to display a plurality of virtual navigation button objects, and execute a switching operation of the virtual navigation button objects on the navigation bar; the second interface control is a sub-interface control and is used for triggering and displaying a sub-interface; the virtual navigation button objects and the sub-interfaces have a one-to-one correspondence relationship, that is, each navigation button corresponds to one sub-interface.
Optionally, the target virtual navigation button object is any one of a plurality of virtual navigation button objects in the first interface control, and a target sub-interface corresponding to any one of the target virtual navigation button objects is loaded in the second interface control in response to a trigger operation on any one of the virtual navigation button objects (i.e., the target virtual navigation button object) in the first interface control.
In an optional embodiment, a plugin management class uiPluginmanager is added in the main interface project, and the uiPluginmanager can be used for analyzing an interface configuration file and creating all virtual navigation button objects; in addition, the uiPluginmanager is also used for independently setting different sub-interfaces into respective qt plug-in projects, adding interface configuration files, and the like; creating a navigation bar based on the icons and the plug-in names in the interface configuration file, and loading the plug-in objects through a plug-in manager class object QPluginLoader according to the information of the dynamic link library dll; the QPluginLoader can convert a dynamic link library dll into a plug-in object, and if a Q _ decode _ INTERFACE name is defined and Q _ INTERFACES is used to specify an INTERFACE instance in engineering, after loading the library with QPluginLoader ("x.dll"), it can be converted into a previously registered INTERFACE class object using type conversion, and then the INTERFACE method can be called.
By the method, at least the following technical effects can be realized: when the sub-interfaces are added or deleted, only the interface configuration file needs to be modified, and each sub-interface and the main interface are completely independent, so that the stability of the main interface framework is ensured, and the maintenance is easy; when interface customization is needed, a special sub-interface can be customized quickly; when the updating of the partial sub-interface program is needed, only a certain dynamic library needs to be replaced; and in the aspect of development efficiency, the development is convenient for multiple people to develop in parallel.
In an optional embodiment, the interface processing method further includes:
step S202, defining a target interface set, wherein the target interface set is used for providing interfaces for creating and destroying sub-interfaces corresponding to each virtual navigation button object;
and step S204, deriving the plug-in classes of the sub-interfaces based on the target interface set, wherein different sub-interfaces are respectively created by adopting different sub-projects, and each sub-project corresponds to different plug-in classes.
Optionally, the plug-in class may be written based on but not limited to a Qt plug-in application program interface API standard, and different sub-interfaces correspond to different plug-in classes, for example, in the structural diagram of the interface processing method shown in fig. 2, the structural diagram includes three sub-interfaces, which are a sub-interface a, a sub-interface B, and a sub-interface C, respectively, where the three sub-interfaces correspond to respective plug-in classes, that is, the sub-interface plug-in a, the sub-interface plug-in B, and the sub-interface plug-in C shown in fig. 2.
Optionally, a target interface set is defined, for example, an imainn tabplug, which provides an interface for creating and destroying a sub-interface for interacting with the main interface class object, wherein the creation sub-component interface provided by the imainn tabplug can return a sub-component object by transferring plug-in information.
Optionally, different plug-in classes of the sub-interfaces can be derived based on the above imainn tabplug, each sub-project has one plug-in class, and all plug-in classes can be written but not limited to follow the Qt plug-in API standard; therefore, the requirement of modular development can be met, all the plug-in objects of the sub-interfaces can be assembled on the page based on the flow and the calling mode, and then a plurality of sub-projects are split.
In an optional embodiment, the information recorded in the interface configuration file includes: the identification information of each virtual navigation button object in the plurality of virtual navigation button objects and the dynamic link library information of the sub-interface corresponding to each virtual navigation button object respectively, wherein the identification information includes: icon information and name information.
Optionally, the format of the interface configuration file may be, but is not limited to, an xml format or an ini format.
It should be noted that, by performing page assembly based on the interface configuration file, the purpose of automatically creating the most suitable navigation bar content according to the actual requirement and automatically associating each virtual navigation button object on the navigation bar with the creation and switching of the sub-interface can be achieved.
As an alternative embodiment, fig. 3 is a flowchart of an alternative interface processing method according to an embodiment of the present disclosure, and as shown in fig. 3, parsing the interface configuration file by using the plug-in manager class object to obtain the parsing result includes:
step S402, analyzing the interface configuration file by using the plug-in manager class object, and determining a first mapping relation;
step S404, loading the dynamic link library information of each sub-interface through the first mapping relation by using the plug-in manager class object, and converting the dynamic link library information of each sub-interface into an interface class object corresponding to each interface to obtain a conversion result;
step S406, determining a second mapping relationship based on the first mapping relationship and the conversion result by using the plug-in manager class object, where the second mapping relationship is used to store the corresponding relationship between the identification information of different virtual navigation button objects and different interface class objects.
Optionally, the interface configuration file is analyzed by using the plug-in manager class object, and the plug-in manager class object (i.e. the plug-in manager class) is initialized.
Optionally, the first mapping relationship is used to store a corresponding relationship between identification information of different virtual navigation button objects and dynamic link library information of different sub-interfaces.
Optionally, the interface configuration file is analyzed by using the plug-in manager class object, and a map table is generated, where the map table is used to store the corresponding relationship (i.e., the first mapping relationship) between the identification information of different virtual navigation button objects and the dynamic link library information of different sub-interfaces; and loading the dynamic link library information of each sub-interface in the map table by using the plug-in manager class object, converting the dynamic link library information of each sub-interface into an interface class object corresponding to each interface, and storing the interface class object into a new map table, wherein the new map table is used for storing the corresponding relationship (namely the second mapping relationship) between the identification information of different virtual navigation button objects and different interface class objects.
It should be noted that different sub-interfaces are respectively created by using different sub-projects, and each sub-project corresponds to a different plug-in class, so that the first mapping relationship may be understood as a plug-in object information map table mapped by plug-in information. After initializing a plug-in manager, reading the content in the interface configuration file, storing the content as a map table mapped by plug-in information, loading the dynamic link library information of each sub-interface in the map table by using the plug-in manager, converting the dynamic link library information into an interface class corresponding to each sub-interface, and storing the interface class as a new map table.
As an alternative embodiment, fig. 4 is a flowchart of another alternative interface processing method according to an embodiment of the present disclosure, and as shown in fig. 4, creating a plurality of virtual navigation button objects in the first interface control by using the plug-in manager class object and the host interface class object includes:
step S502, using the plug-in manager class object to create the plurality of virtual navigation button objects through the second mapping relation;
step S504, inserting the plurality of virtual navigation button objects into the first interface control according to a preset sequence by using the main interface class object;
step S506, binding a trigger response event for each of the plurality of virtual navigation button objects by using the main interface class object.
Optionally, each virtual navigation button object includes at least one of: text and icons.
Optionally, the binding a trigger response event for each virtual navigation button object in the plurality of virtual navigation button objects includes: a slot function (a callback function) of a click event is added to each of the plurality of virtual navigation button objects.
Optionally, initializing a plurality of virtual navigation button objects on the main page includes: calling a button initialization interface of a plug-in manager class object for the plurality of virtual navigation button objects through a navigation bar interface control (i.e. the first interface control), wherein the plug-in manager class object traverses all nodes according to the new map table, creates a plurality of virtual navigation button objects matched with node information, returns to a virtual navigation button object list, and saves the plurality of virtual navigation button objects and node identification information (e.g. id information) corresponding to each virtual navigation button object into the map table of the virtual navigation button objects, wherein the virtual navigation button objects correspond to the plurality of virtual navigation button objects matched with the node information; inserting the plurality of virtual navigation button objects into the navigation bar interface control according to a preset sequence by using the main interface class object to form a group of virtual navigation button objects; the main interface class object binds click events for each virtual navigation button object.
In an optional embodiment, the determining the sub-interface corresponding to each of the plurality of virtual navigation button objects includes:
step S602, traversing all sub-interfaces based on the second mapping relationship by using the plug-in manager class object, and determining a third mapping relationship, where the third mapping relationship is used to store corresponding relationships between different virtual navigation button objects and identification information of different sub-interfaces.
Optionally, each virtual navigation button object corresponds to different node identification information, the third mapping relationship is used to store a corresponding relationship between different virtual navigation button objects and identification information of different sub-interfaces, and may be understood as a map table of the virtual navigation button objects, where the map table of the virtual navigation button objects includes the plurality of virtual navigation button objects and the node identification information corresponding to each virtual navigation button object.
As an alternative embodiment, fig. 5 is a flowchart of another alternative interface processing method according to the embodiment of the present disclosure, and as shown in fig. 5, loading the target sub-interface corresponding to the target virtual navigation button object in the second interface control includes:
step S702, calling the plug-in manager class object by using a navigation interface control object to create a target interface, and transmitting a virtual navigation button object through the target interface;
step S704, using the virtual navigation button object to search the identification information of the target sub-interface from the third mapping relationship, using the identification information of the target sub-interface to search the interface class object corresponding to the target sub-interface from the second mapping relationship, and creating a window class object through the interface class object;
step S706, sending a first target signal to a sub-interface control class object by using the navigation interface control object, wherein a signal parameter carried in the first target signal is used for creating the window class object;
step S708, inserting the window class object into the second interface control by using the sub-interface control class object.
Optionally, the target interface may be, but is not limited to, an interface for creating a page component; the signal parameters carried in the first target signal are used for creating the window class object; the fourth mapping relationship is used to store the corresponding relationship between different window class objects and different virtual navigation button objects, and the fourth mapping relationship may be stored in a mapping association table including the corresponding relationship between the window class objects and different virtual navigation button objects.
Optionally, clicking the target virtual navigation button object opens the sub-interface, including: the navigation interface control object calls an interface of a plug-in manager class object creation page component and transmits a virtual navigation button object; the plug-in manager class object finds the identification information (e.g. id address) of the target sub-interface in the map table of the virtual navigation button object, finds the interface class object corresponding to the target sub-interface from the plug-in object information table based on the identification information, creates a window class object QWidget (the window class object is a window component QWidget object, namely a window component object from Qt, a basic unit of the user interface, receives mouse, keyboard and other events from the window system, and draws itself on the screen) through the creation component of the interface class object as a parameter return; the navigation interface control object sends a signal 'insert active page' to a sub-interface control object, the window class object is used as a signal parameter, and the window class object is stored in a 'button-sub-interface association table' in an association manner, wherein the button-sub-interface association table is an association table used for associating the virtual navigation button object with the QWIDGET object, the pointer value of the virtual button object is used as a key value, and the pointer value of the QWIDGET object is used as an association value.
The map table of the virtual navigation button object is a map table of the virtual navigation button objects and node identification information (for example, id information) corresponding to each virtual navigation button object, the map table takes a pointer value of the virtual navigation button object as a key value, takes an id value of a sub-page where a code of the virtual navigation button object is located as an associated value, can find the id value of the associated sub-page according to the virtual navigation button object of a click event sent by a navigation page, facilitates a plug-in manager object to find a plug-in interface object in the second mapping relation by using the id value, and further adopts the plug-in manager to create a specific QWIdget object.
As an alternative embodiment, fig. 6 is a flowchart of another alternative interface processing method according to an embodiment of the present disclosure, and as shown in fig. 6, the interface processing method further includes:
step S802, responding to a trigger operation executed on a virtual navigation button object to be switched in the virtual navigation button object, and searching a window class object to be updated corresponding to the virtual navigation button object to be switched from a fourth mapping relation by using the navigation interface control object, wherein the fourth mapping relation is used for storing the corresponding relation between different window class objects and different virtual navigation button objects;
step S804, sending a second target signal to the sub-interface control class object by using the navigation interface control object, wherein a signal parameter carried in the second target signal is used for creating the window class object to be updated;
step S806, insert the window class object to be updated into the second interface control by using the sub-interface control class object.
Optionally, the signal parameter carried in the second target signal is used to create the window class object to be updated; and the window class object to be updated is a window class object corresponding to the virtual navigation button object to be switched.
Optionally, the window class object to be updated is inserted into the second interface control by using the sub-interface control class object, the current sub-interface is switched, and a new sub-interface is displayed on the current display interface.
Optionally, clicking the virtual navigation button object switches the sub-interface, including: the navigation interface control object inquires a window class object corresponding to a virtual navigation button object to be switched in the button-sub interface association table, and sends a switching activity page signal to the sub interface control class object, wherein the switching activity page signal carries the window class object corresponding to the virtual navigation button object to be switched; and after receiving the active page switching signal, the sub-interface control sets the window class object corresponding to the virtual navigation button switching object as a current active page.
According to an embodiment of the present disclosure, an embodiment of an apparatus for implementing the interface processing method is further provided, fig. 7 is a schematic structural diagram of an interface processing apparatus according to an embodiment of the present disclosure, and as shown in fig. 7, the interface processing apparatus includes: a first creation module 40, a parsing module 42, a second creation module 44, a first processing module 46, a second processing module 48, wherein:
the first creating module 40 is configured to create a plug-in manager class object and a main interface class object; the parsing module 42 is configured to parse the interface configuration file by using the plug-in manager class object to obtain a parsing result; the second creating module 44 is configured to create a first interface control and a second interface control in the main interface through the main interface class object, where the first interface control is a navigation interface control, and the second interface control is a sub-interface control; the first processing module 46 is configured to create a plurality of virtual navigation button objects in the first interface control by using the plug-in manager class object and the main interface class object based on the parsing result, and determine a sub-interface corresponding to each of the plurality of virtual navigation button objects; the second processing module 48 is configured to respond to a trigger operation executed on a target virtual navigation button object, and load a target sub-interface corresponding to the target virtual navigation button object in the second interface control, where the target virtual navigation button object is any virtual navigation button object in the multiple virtual navigation button objects.
In the embodiment of the present disclosure, the first creating module 40 is configured to create a plug-in manager class object and a main interface class object; the parsing module 42 is configured to parse the interface configuration file by using the plug-in manager class object to obtain a parsing result; the second creating module 44 is configured to create a first interface control and a second interface control in the main interface through the main interface class object, where the first interface control is a navigation interface control, and the second interface control is a sub-interface control; the first processing module 46 is configured to create a plurality of virtual navigation button objects in the first interface control by using the plug-in manager class object and the main interface class object based on the parsing result, and determine a sub-interface corresponding to each of the plurality of virtual navigation button objects; the second processing module 48 is used for responding to the triggering operation executed on the target virtual navigation button object, loading a target sub-interface corresponding to the target virtual navigation button object in the second interface control, wherein the target virtual navigation button object is any one of the plurality of virtual navigation button objects, so that different sub-interfaces are made into independent plug-ins, thereby isolating different sub-interfaces, sub-interfaces and main pages, realizing the technical effect of improving the engineering development efficiency and stability, further solves the problems that in the prior art, because the codes of all the sub-interfaces and the main page are concentrated in the same project, when a user enters or updates the sub-interface, the whole main page needs to be loaded and updated, which causes the technical problems of large engineering development efficiency, large memory space occupation and poor stability.
It should be noted that the above modules may be implemented by software or hardware, for example, for the latter, the following may be implemented: the modules can be located in the same processor; alternatively, the modules may be located in different processors in any combination.
It should be noted here that the first creating module 40, the parsing module 42, the second creating module 44, the first processing module 46, and the second processing module 48 correspond to steps S102 to S110 in embodiment 1, and the modules are the same as the corresponding steps in implementation examples and application scenarios, but are not limited to the disclosure in embodiment 1. It should be noted that the modules described above may be implemented in a computer terminal as part of an apparatus.
It should be noted that, for alternative or preferred embodiments of the present embodiment, reference may be made to the description in the foregoing method embodiments, and details are not described herein again.
The interface processing device may further include a processor and a memory, where the first creating module 40, the parsing module 42, the second creating module 44, the first processing module 46, the second processing module 48, and the like are stored in the memory as program units, and the processor executes the program units stored in the memory to implement corresponding functions.
The processor comprises a kernel, and the kernel calls a corresponding program unit from the memory, wherein one or more than one kernel can be arranged. The memory may include volatile memory in a computer readable medium, Random Access Memory (RAM) and/or nonvolatile memory such as Read Only Memory (ROM) or flash memory (flash RAM), and the memory includes at least one memory chip.
According to an embodiment of the present application, there is also provided an embodiment of a non-volatile storage medium. Optionally, in this embodiment, the nonvolatile storage medium includes a stored program, and the apparatus in which the nonvolatile storage medium is located is controlled to execute any one of the interface processing methods when the program runs.
Optionally, in this embodiment, the nonvolatile storage medium may be located in any one of a group of computer terminals in a computer network, or in any one of a group of mobile terminals, and the nonvolatile storage medium includes a stored program.
Optionally, the apparatus in which the non-volatile storage medium is controlled to perform the following functions when the program is executed: creating a plug-in manager class object and a main interface class object; analyzing the interface configuration file by using the plug-in manager class object to obtain an analysis result; creating a first interface control and a second interface control in a main interface through the main interface class object, wherein the first interface control is a navigation interface control, and the second interface control is a sub-interface control; based on the analysis result, creating a plurality of virtual navigation button objects in the first interface control by using the plug-in manager class object and the main interface class object, and determining a sub-interface corresponding to each virtual navigation button object in the plurality of virtual navigation button objects; and responding to a trigger operation executed on a target virtual navigation button object, and loading a target sub-interface corresponding to the target virtual navigation button object in the second interface control, wherein the target virtual navigation button object is any virtual navigation button object in the plurality of virtual navigation button objects.
According to an embodiment of the present application, there is also provided an embodiment of a processor. Optionally, in this embodiment, the processor is configured to execute a program, where the program executes any one of the interface processing methods.
There is further provided, according to an embodiment of the present application, an embodiment of a computer program product, which is adapted to execute a program that initializes the steps of the interface processing method of any one of the above.
Optionally, the computer program product described above, when being executed on a data processing device, is adapted to perform a procedure for initializing the following method steps: creating a plug-in manager class object and a main interface class object; analyzing the interface configuration file by using the plug-in manager class object to obtain an analysis result; creating a first interface control and a second interface control in a main interface through the main interface class object, wherein the first interface control is a navigation interface control, and the second interface control is a sub-interface control; based on the analysis result, creating a plurality of virtual navigation button objects in the first interface control by using the plug-in manager class object and the main interface class object, and determining a sub-interface corresponding to each virtual navigation button object in the plurality of virtual navigation button objects; and responding to a trigger operation executed on a target virtual navigation button object, and loading a target sub-interface corresponding to the target virtual navigation button object in the second interface control, wherein the target virtual navigation button object is any virtual navigation button object in the plurality of virtual navigation button objects.
Optionally, the computer program product described above, when being executed on a data processing device, is adapted to perform a procedure for initializing the following method steps: defining a target interface set, wherein the target interface set is used for providing interfaces for creating and destroying sub-interfaces corresponding to each virtual navigation button object; deriving the plug-in classes of the sub-interfaces based on the target interface set, wherein different sub-interfaces are created by adopting different sub-projects, and each sub-project corresponds to different plug-in classes.
Optionally, the computer program product described above, when being executed on a data processing device, is adapted to perform a procedure for initializing the following method steps: analyzing the interface configuration file by using the plug-in manager class object, and determining a first mapping relation, wherein the first mapping relation is used for storing the corresponding relation between the identification information of different virtual navigation button objects and the dynamic link library information of different sub-interfaces; loading the dynamic link library information of each sub-interface through the first mapping relation by using the plug-in manager class object, and converting the dynamic link library information of each sub-interface into an interface class object corresponding to each interface to obtain a conversion result; and determining a second mapping relation by using the plug-in manager class object based on the first mapping relation and the conversion result, wherein the second mapping relation is used for storing the corresponding relation between the identification information of different virtual navigation button objects and different interface class objects.
Optionally, the computer program product described above, when being executed on a data processing device, is adapted to perform a procedure for initializing the following method steps: creating the plurality of virtual navigation button objects through the second mapping relationship by using the plug-in manager class object; inserting the plurality of virtual navigation button objects into the first interface control according to a preset sequence by using the main interface class object; and binding a trigger response event for each virtual navigation button object in the plurality of virtual navigation button objects by using the main interface class object.
Optionally, the computer program product described above, when being executed on a data processing device, is adapted to perform a procedure for initializing the following method steps: and traversing all the sub-interfaces based on the second mapping relation by using the plug-in manager class object, and determining a third mapping relation, wherein the third mapping relation is used for storing corresponding relations between different virtual navigation button objects and identification information of different sub-interfaces.
Optionally, the computer program product described above, when being executed on a data processing device, is adapted to perform a procedure for initializing the following method steps: calling the plug-in manager class object by using a navigation interface control object to create a target interface, and transmitting a virtual navigation button object through the target interface; searching the identification information of the target sub-interface from the third mapping relation by using the virtual navigation button object, searching the interface class object corresponding to the target sub-interface from the second mapping relation by using the identification information of the target sub-interface, and creating a window class object through the interface class object; sending a first target signal to a sub-interface control class object by using the navigation interface control object, wherein a signal parameter carried in the first target signal is used for creating the window class object; and inserting the window class object into the second interface control by using the child interface control class object.
Optionally, the computer program product described above, when being executed on a data processing device, is adapted to perform a procedure for initializing the following method steps: responding to a trigger operation executed on a virtual navigation button object to be switched in the virtual navigation button object, and searching a window class object to be updated corresponding to the virtual navigation button object to be switched from a fourth mapping relation by using the navigation interface control object, wherein the fourth mapping relation is used for storing the corresponding relation between different window class objects and different virtual navigation button objects; sending a second target signal to the sub-interface control class object by using the navigation interface control object, wherein a signal parameter carried in the second target signal is used for creating the window class object to be updated; and inserting the window class object to be updated into the second interface control by using the child interface control class object.
According to an embodiment of the present application, there is further provided an embodiment of an electronic apparatus, including a memory and a processor, where the memory stores a computer program, and the processor is configured to execute the computer program to perform any one of the interface processing methods.
The above-mentioned serial numbers of the embodiments of the present disclosure are merely for description and do not represent the merits of the embodiments.
In the above embodiments of the present disclosure, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
In the embodiments provided in the present application, it should be understood that the disclosed technology can be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units may be a logical division, and in actual implementation, there may be another division, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present disclosure may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present disclosure. And the aforementioned storage medium includes: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.
The foregoing is merely a preferred embodiment of the present disclosure, and it should be noted that modifications and embellishments could be made by those skilled in the art without departing from the principle of the present disclosure, and these should also be considered as the protection scope of the present disclosure.

Claims (11)

1. An interface processing method, comprising:
creating a plug-in manager class object and a main interface class object;
analyzing the interface configuration file by using the plug-in manager class object to obtain an analysis result;
creating a first interface control and a second interface control in a main interface through the main interface class object, wherein the first interface control is a navigation interface control, and the second interface control is a sub-interface control;
based on the analysis result, creating a plurality of virtual navigation button objects in the first interface control by using the plug-in manager class object and the main interface class object, and determining a sub-interface corresponding to each virtual navigation button object in the plurality of virtual navigation button objects;
and responding to a trigger operation executed on a target virtual navigation button object, and loading a target sub-interface corresponding to the target virtual navigation button object in the second interface control, wherein the target virtual navigation button object is any virtual navigation button object in the plurality of virtual navigation button objects.
2. The interface processing method according to claim 1, further comprising:
defining a target interface set, wherein the target interface set is used for providing interfaces for creating and destroying sub-interfaces corresponding to each virtual navigation button object;
deriving the plug-in classes of the sub-interfaces based on the target interface set, wherein different sub-interfaces are respectively created by adopting different sub-projects, and each sub-project corresponds to different plug-in classes.
3. The interface processing method according to claim 1, wherein the information recorded in the interface configuration file includes:
identification information of each virtual navigation button object in the plurality of virtual navigation button objects and dynamic link library information of a sub-interface corresponding to each virtual navigation button object respectively, wherein the identification information comprises: icon information and name information.
4. The interface processing method according to claim 3, wherein parsing the interface configuration file using the plug-in manager class object to obtain the parsing result comprises:
analyzing the interface configuration file by using the plug-in manager class object, and determining a first mapping relation, wherein the first mapping relation is used for storing the corresponding relation between the identification information of different virtual navigation button objects and the dynamic link library information of different sub-interfaces;
loading the dynamic link library information of each sub-interface through the first mapping relation by using the plug-in manager class object, and converting the dynamic link library information of each sub-interface into an interface class object corresponding to each interface to obtain a conversion result;
and determining a second mapping relation based on the first mapping relation and the conversion result by using the plug-in manager class object, wherein the second mapping relation is used for storing the corresponding relation between the identification information of different virtual navigation button objects and different interface class objects.
5. The interface processing method of claim 4, wherein creating a plurality of virtual navigation button objects within the first interface control using the plug-in manager class object and the host interface class object comprises:
traversing the identification information of different virtual navigation buttons stored in the second mapping relation by using the plug-in manager class object to create a plurality of virtual navigation button objects;
inserting the plurality of virtual navigation button objects into the first interface control according to a preset sequence by using the main interface class object;
and binding a trigger response event for each virtual navigation button object in the plurality of virtual navigation button objects by using the main interface class object.
6. The interface processing method according to claim 4 or 5, wherein the determining the sub-interface corresponding to each of the plurality of virtual navigation button objects comprises:
and traversing all the sub-interfaces based on the second mapping relation by utilizing the plug-in manager class object, and determining a third mapping relation, wherein the third mapping relation is used for storing the corresponding relation between different virtual navigation button objects and the identification information of different sub-interfaces.
7. The interface processing method of claim 6, wherein loading the target sub-interface corresponding to the target virtual navigation button object within the second interface control comprises:
calling the plug-in manager class object by using a navigation interface control object to create a target interface, and transmitting a virtual navigation button object through the target interface;
searching the identification information of the target sub-interface from the third mapping relation by using the virtual navigation button object, searching the interface class object corresponding to the target sub-interface from the second mapping relation by using the identification information of the target sub-interface, and creating a window class object through the interface class object;
sending a first target signal to a sub-interface control class object by using the navigation interface control object, wherein a signal parameter carried in the first target signal is used for creating the window class object;
and inserting the window class object into the second interface control by using the child interface control class object.
8. The interface processing method according to claim 7, wherein after loading the target sub-interface corresponding to the target virtual navigation button object within the second interface control, the method further comprises:
responding to a triggering operation executed on a virtual navigation button object to be switched in the virtual navigation button object, and searching a window class object to be updated corresponding to the virtual navigation button object to be switched from a fourth mapping relation by using the navigation interface control object, wherein the fourth mapping relation is used for storing the corresponding relation between different window class objects and different virtual navigation button objects;
sending a second target signal to the sub-interface control class object by using the navigation interface control object, wherein a signal parameter carried in the second target signal is used for creating the window class object to be updated;
and inserting the window class object to be updated into the second interface control by using the sub-interface control class object.
9. An interface processing apparatus, comprising:
the first creating module is used for creating a plug-in manager class object and a main interface class object;
the analysis module is used for analyzing the interface configuration file by using the plug-in manager class object to obtain an analysis result;
a second creating module, configured to create a first interface control and a second interface control in a main interface through the main interface class object, where the first interface control is a navigation interface control, and the second interface control is a sub-interface control;
a first processing module, configured to create, based on the parsing result, a plurality of virtual navigation button objects in the first interface control by using the plug-in manager class object and the main interface class object, and determine a sub-interface corresponding to each of the plurality of virtual navigation button objects;
and the second processing module is used for responding to a trigger operation executed on a target virtual navigation button object and loading a target sub-interface corresponding to the target virtual navigation button object in the second interface control, wherein the target virtual navigation button object is any virtual navigation button object in the plurality of virtual navigation button objects.
10. A non-volatile storage medium, wherein a computer program is stored in the storage medium, wherein the computer program is configured to execute the interface processing method according to any one of claims 1 to 8 when the computer program runs.
11. An electronic device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to perform the interface processing method according to any one of claims 1 to 8.
CN202111458533.0A 2021-12-01 2021-12-01 Interface processing method, device, electronic device and storage medium Active CN114296845B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111458533.0A CN114296845B (en) 2021-12-01 2021-12-01 Interface processing method, device, electronic device and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111458533.0A CN114296845B (en) 2021-12-01 2021-12-01 Interface processing method, device, electronic device and storage medium

Publications (2)

Publication Number Publication Date
CN114296845A true CN114296845A (en) 2022-04-08
CN114296845B CN114296845B (en) 2024-03-22

Family

ID=80964910

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111458533.0A Active CN114296845B (en) 2021-12-01 2021-12-01 Interface processing method, device, electronic device and storage medium

Country Status (1)

Country Link
CN (1) CN114296845B (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116860247A (en) * 2023-08-31 2023-10-10 江西省信息中心(江西省电子政务网络管理中心 江西省信用中心 江西省大数据中心) User interface generation method and device, storage medium and electronic equipment

Citations (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103488479A (en) * 2013-09-04 2014-01-01 用友软件股份有限公司 Dynamic generating device for client end interface and dynamic generating method for client end interface
CN105224353A (en) * 2014-06-26 2016-01-06 北京北方微电子基地设备工艺研究中心有限责任公司 The method and system of dynamic load interface navigation
CN105511977A (en) * 2015-12-04 2016-04-20 北京远特科技股份有限公司 Vehicle-mounted navigation system testing method and device
KR20170078007A (en) * 2015-12-29 2017-07-07 에스케이플래닛 주식회사 User equipment, control method thereof and computer readable medium having computer program recorded thereon
JP2018005945A (en) * 2017-10-03 2018-01-11 アマノ株式会社 Task management device, task management system, and program thereof
CN107665137A (en) * 2016-07-29 2018-02-06 北京北方华创微电子装备有限公司 Method and apparatus for interface configurations
CN107870711A (en) * 2016-09-27 2018-04-03 阿里巴巴集团控股有限公司 Page navigation method, the method and client that user interface is provided
CN108334371A (en) * 2017-09-07 2018-07-27 北京小米移动软件有限公司 The method and apparatus of edit object
CN108710630A (en) * 2018-04-02 2018-10-26 阿里巴巴集团控股有限公司 A kind of page navigation method, device and equipment
CN109491586A (en) * 2018-11-14 2019-03-19 网易(杭州)网络有限公司 Virtual object control method and device, electronic equipment, storage medium
CN110175301A (en) * 2019-04-08 2019-08-27 平安科技(深圳)有限公司 A kind of navigation bar configuration method and device, computer equipment and storage medium
CN110968226A (en) * 2018-09-30 2020-04-07 北京奇虎科技有限公司 Navigation bar control method and device, mobile terminal and storage medium
CN113031951A (en) * 2021-04-30 2021-06-25 爱捷软件开发(深圳)有限公司 Menu generation method and device, computer equipment and storage medium

Patent Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103488479A (en) * 2013-09-04 2014-01-01 用友软件股份有限公司 Dynamic generating device for client end interface and dynamic generating method for client end interface
CN105224353A (en) * 2014-06-26 2016-01-06 北京北方微电子基地设备工艺研究中心有限责任公司 The method and system of dynamic load interface navigation
CN105511977A (en) * 2015-12-04 2016-04-20 北京远特科技股份有限公司 Vehicle-mounted navigation system testing method and device
KR20170078007A (en) * 2015-12-29 2017-07-07 에스케이플래닛 주식회사 User equipment, control method thereof and computer readable medium having computer program recorded thereon
CN107665137A (en) * 2016-07-29 2018-02-06 北京北方华创微电子装备有限公司 Method and apparatus for interface configurations
CN107870711A (en) * 2016-09-27 2018-04-03 阿里巴巴集团控股有限公司 Page navigation method, the method and client that user interface is provided
CN108334371A (en) * 2017-09-07 2018-07-27 北京小米移动软件有限公司 The method and apparatus of edit object
US20190073095A1 (en) * 2017-09-07 2019-03-07 Beijing Xiaomi Mobile Software Co., Ltd. Method and apparatus for editing object
JP2018005945A (en) * 2017-10-03 2018-01-11 アマノ株式会社 Task management device, task management system, and program thereof
CN108710630A (en) * 2018-04-02 2018-10-26 阿里巴巴集团控股有限公司 A kind of page navigation method, device and equipment
CN110968226A (en) * 2018-09-30 2020-04-07 北京奇虎科技有限公司 Navigation bar control method and device, mobile terminal and storage medium
CN109491586A (en) * 2018-11-14 2019-03-19 网易(杭州)网络有限公司 Virtual object control method and device, electronic equipment, storage medium
CN110175301A (en) * 2019-04-08 2019-08-27 平安科技(深圳)有限公司 A kind of navigation bar configuration method and device, computer equipment and storage medium
CN113031951A (en) * 2021-04-30 2021-06-25 爱捷软件开发(深圳)有限公司 Menu generation method and device, computer equipment and storage medium

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116860247A (en) * 2023-08-31 2023-10-10 江西省信息中心(江西省电子政务网络管理中心 江西省信用中心 江西省大数据中心) User interface generation method and device, storage medium and electronic equipment
CN116860247B (en) * 2023-08-31 2023-11-21 江西省信息中心(江西省电子政务网络管理中心 江西省信用中心 江西省大数据中心) User interface generation method and device, storage medium and electronic equipment

Also Published As

Publication number Publication date
CN114296845B (en) 2024-03-22

Similar Documents

Publication Publication Date Title
CN111104635B (en) Method and device for generating form webpage
CN102129364B (en) Method for embedding widget toolbar in application program and rapid widget accessing method
US8942679B2 (en) Method and system for providing pattern based enterprise applications for organizing, automating, and synchronizing processes for mobile communication devices
US20120079009A1 (en) Method and apparatus for choosing resources based on context and inheritance
CN110992112A (en) Method and device for processing advertisement information
CN102118650A (en) Method and device for displaying television menu, and television
CN108810132B (en) Animation display method, device, terminal, server and storage medium
CN111610972B (en) Page generation method, device, equipment and storage medium
CN106062693A (en) Desktop sharing method and mobile terminal
CN114296845B (en) Interface processing method, device, electronic device and storage medium
CN111324398B (en) Method, device, terminal and storage medium for processing latest content
CN113434063B (en) Information display method, device and equipment
US9741060B2 (en) Recursive navigation in mobile CRM
CN105808313B (en) Intelligent terminal data interactive system and method
CN102446252A (en) Method and device for showing off-limit files
CN115729549A (en) Method and device for generating user interaction interface, storage medium and electronic device
CN106383705B (en) Method and device for setting mouse display state in application thin client
CN115373564A (en) Function shortcut key self-defining method and device, software function control method and terminal
CN111767111A (en) Page data processing method and device, electronic equipment and storage medium
CN111198830A (en) Identification method and device of mobile storage equipment, electronic equipment and storage medium
CN117215543B (en) Component development method suitable for different service scene types and corresponding system thereof
CN111090824B (en) Content processing method and device
CN115129198B (en) Data acquisition method and device, electronic equipment and storage medium
CN114327464B (en) Component construction method and device and storage medium
CN114217877A (en) Operation processing method, device, equipment and medium based on page interaction component

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