CN111258694A - Interface loading method and device, user side and storage medium - Google Patents
Interface loading method and device, user side and storage medium Download PDFInfo
- Publication number
- CN111258694A CN111258694A CN202010041596.5A CN202010041596A CN111258694A CN 111258694 A CN111258694 A CN 111258694A CN 202010041596 A CN202010041596 A CN 202010041596A CN 111258694 A CN111258694 A CN 111258694A
- Authority
- CN
- China
- Prior art keywords
- interface
- loading
- user
- target
- target sub
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
Abstract
The application provides an interface loading method, an interface loading device, a user side and a storage medium, relates to the technical field of the Internet, and aims to load a target sub-interface corresponding to a current parent interface in a user interface by configuring an interface management list recorded with parent-child relations among a plurality of interfaces when the user interface finishes loading the current parent interface.
Description
Technical Field
The application relates to the technical field of internet, in particular to an interface loading method, an interface loading device, a user side and a storage medium.
Background
With the rapid development of the mobile internet, more and more mobile Applications (APPs) are developed to provide services for users to meet the increasing use demands of the users.
In addition, with diversification of mobile application products, users experience more and more functions of various APPs, so that the APPs have more and more application functions and the complexity of an interactive interface is increased, for example, an interface with a dependency relationship between the APPs or an application interface with a parent-child relationship exists.
However, in the current interface loading scheme in APP, for example, the loading speed of the interface is slow, which results in poor experience of the user.
Disclosure of Invention
The application aims to provide an interface loading method, an interface loading device, a user side and a storage medium, which can improve the loading speed of an interface.
In order to achieve the purpose, the technical scheme adopted by the application is as follows:
in a first aspect, the present application provides an interface loading method, including:
when the user interface finishes loading the current parent interface, determining a target sub-interface corresponding to the current parent interface in an interface management list; the interface management list records the parent-child relationship among a plurality of interfaces;
and loading the target sub-interface on the user interface.
In a second aspect, the present application provides an interface loading apparatus, the apparatus comprising:
the processing module is used for determining a target sub-interface corresponding to the current parent interface in an interface management list when the user interface finishes loading the current parent interface; the interface management list records the parent-child relationship among a plurality of interfaces;
and the loading module is used for loading the target sub-interface on the user interface.
In a third aspect, the present application provides a user side, including a memory for storing one or more programs; a processor; when the one or more programs are executed by the processor, the interface loading method is realized.
In a fourth aspect, the present application provides a computer-readable storage medium, on which a computer program is stored, which, when executed by a processor, implements the interface loading method described above.
According to the interface loading method, the interface loading device, the user side and the storage medium, the interface management list recorded with the parent-child relationship among the interfaces is configured, so that when the user interface finishes loading the current parent interface, the target child interface corresponding to the current parent interface can be determined in the interface management list, and the target child interface is loaded on the user interface.
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly explain the technical solutions of the present application, the drawings needed for the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and that those skilled in the art can also derive other related drawings from these drawings without inventive effort.
FIG. 1 shows a schematic diagram of a user interface;
FIG. 2 is a schematic application scenario diagram illustrating an interface loading method provided by the present application;
fig. 3 is a schematic structural block diagram of a user side provided in the present application;
FIG. 4 is a schematic flow chart diagram of an interface loading method provided herein;
FIG. 5 illustrates another schematic flow chart diagram of an interface loading method provided herein;
FIG. 6 is a further schematic flow chart diagram of the interface loading method provided herein;
FIG. 7 shows another schematic view of a user interface;
FIG. 8 illustrates yet another schematic flow chart of an interface loading method provided herein;
FIG. 9 shows yet another schematic of a user interface;
FIG. 10 illustrates yet another schematic flow chart of an interface loading method provided herein;
fig. 11 shows a schematic structural block diagram of an interface loading device provided in the present application.
In the figure: 100-user terminal; 101-a memory; 102-a processor; 103-a memory controller; 104-peripheral interfaces; 105-a radio frequency unit; 106-communication bus/signal line; 107-a display unit; 300-interface loading means; 301-a processing module; 302-load module.
Detailed Description
To make the purpose, technical solutions and advantages of the present application clearer, the technical solutions in the present application will be clearly and completely described below with reference to the accompanying drawings in some embodiments of the present application, and it is obvious that the described embodiments are some, but not all embodiments of the present application. The components of the present application, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the present application, as presented in the figures, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments obtained by a person of ordinary skill in the art based on a part of the embodiments in the present application without any creative effort belong to the protection scope of the present application.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Meanwhile, in the description of the present application, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Some embodiments of the present application will be described in detail below with reference to the accompanying drawings. The embodiments described below and the features of the embodiments can be combined with each other without conflict.
As shown in fig. 1, in a scene such as live webcasting, a user interface of a user side may have a plurality of interactive interfaces, and the interactive interfaces may be in a parallel relationship, for example, the four interactive interfaces in fig. 1, named as "chat", "anchor", "ranking", and "visitors", are in a parallel relationship, and the displays of the interactive interfaces do not affect each other, and there is no association; for example, in fig. 1, two interactive interfaces named "ranking list" and "leaderboard" are referred to as a parent-child relationship, and when the interactive interface named "ranking list" in the user interface is clicked, two interactive interfaces named "ranking list" and "leaderboard" are displayed.
Various interactive interfaces are designed on the user interface of the user side, so that different requirements of users can be met; for example, in the live network scenario shown in fig. 1, a user may interact with other users, such as a main broadcast or a viewer, in an interactive interface of "chat", and may view related information of the main broadcast, etc. in the interactive interface of "main broadcast".
In a user interface such as that shown in fig. 1, the current loading scheme for an interactive interface is generally: when a user selects to enter a certain live broadcast room, the user side loads the contents of all the interactive interfaces of the live broadcast room, such as all the contents of four interactive interfaces of "chat", "anchor", "ranking" and "visitors" in fig. 1, and the contents are loaded in the user side when the user clicks the user interface to enter the corresponding live broadcast room; when one interactive interface, such as the interactive interface named "chat", in the user interface is clicked, the user side displays the corresponding interactive content on the user interface.
However, in the above loading scheme, taking the example that the user clicks the interactive interface named "chat" in the user interface, the user end only needs to load the interactive interface named "chat", for example, the contents of other interactive interfaces such as "anchor", "ranking", "visitors" and the like do not actually generate interactive contents with the user, so that when the user clicks the user interface to enter the corresponding live broadcasting room, the user interface of the user end loads more interface contents irrelevant to the current interactive contents of the user, which results in a slow loading speed of the interface and poor user experience.
Therefore, based on the above drawbacks, the present application provides a possible implementation manner as follows: by configuring an interface management list recorded with the parent-child relationship among a plurality of interfaces, when the user interface finishes loading the current parent interface, a target child interface corresponding to the current parent interface can be determined in the interface management list, so that the target child interface is loaded on the user interface; after the current parent interface is loaded, a user only needs to load the target child interface corresponding to the current parent interface, and does not need to load all interactive interfaces, so that the loading speed of the interface is increased.
Referring to fig. 2, fig. 2 is a schematic application scenario diagram illustrating an interface loading method provided in the present application, in some embodiments of the present application, a server and a client are located in a wireless network or a wired network, and the server and the client perform data interaction through the wireless network or the wired network; for example, the server may send the live video code stream to the user side, and the user side may play and receive the live video code stream sent by the server to generate a live video picture.
In some embodiments of the present application, the user terminal may employ a mobile terminal device, which may include, for example, a smart phone, a Personal Computer (PC), a tablet computer, a wearable mobile terminal, and the like.
The interface loading method provided by the application can be applied to a user side shown in fig. 2, wherein an application program is installed in the user side, corresponds to a server, and is used for providing services for a user, for example, the user side can receive a live video code stream sent by the server and play the live video code stream to generate a live video picture; the interface loading method provided by the application can be realized through the application program installed in the user side.
Referring to fig. 3, fig. 3 is a schematic block diagram illustrating a user terminal 100 provided in the present application, and in an embodiment, the user terminal 100 includes a memory 101, one or more processors (only one of which is shown) 102, a memory controller 103, a peripheral interface 104, an rf unit 105, a display unit 107, and the like. These components may communicate with each other via one or more communication buses/signal lines 106.
The memory 101 may be configured to store software programs and modules, such as program instructions/modules corresponding to the interface loading apparatus provided in the present application, and the processor 102 executes various functional applications, image processing, and the like by running the software programs and modules stored in the memory 101, so as to implement the interface loading method provided in the present application.
The Memory 101 may be, but is not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Read-Only Memory (EPROM), an electrically Erasable Programmable Read-Only Memory (EEPROM), and the like.
The processor 102 may be an integrated circuit chip having signal processing capabilities. The processor 102 may be a general-purpose processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), a voice processor, a video processor, and the like; but may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. The methods, steps, and logic blocks disclosed in some embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor 102 may be any conventional processor or the like.
The peripheral interface 104 couples various input/output devices to the processor 102 as well as to the memory 101. In some embodiments, the peripheral interface 104, the processor 102, and the memory controller 103 may be implemented in a single chip. In other embodiments of the present application, they may be implemented by separate chips.
The rf unit 105 is used for receiving and transmitting electromagnetic waves, and implementing interconversion between the electromagnetic waves and electrical signals, so as to communicate with a communication network or other devices.
The display unit 107 is configured to provide a graphical output interface for a user, display image information, for example, the display unit 107 may serve as a user interface for playing a video live picture, and receive an interactive instruction generated on the display unit 107 by the user.
It is understood that the structure shown in fig. 3 is only an illustration, and the user terminal 100 may also include more or less components than those shown in fig. 3, or have a different configuration than that shown in fig. 3. The components shown in fig. 3 may be implemented in hardware, software, or a combination thereof.
The interface loading method provided by the present application is exemplarily described below with the user terminal 100 shown in fig. 3 as an exemplary execution subject.
Referring to fig. 4, fig. 4 shows a schematic flowchart of an interface loading method provided in the present application, which may include the following steps:
In an embodiment, the user side may store an interface management list, where the interface management list records parent-child relationships among multiple interfaces; such as in the user interface illustrated in fig. 1, for example, the parent-child relationships recorded by the interface management list may include: the parent-child relationship between the ranking and the Zhonggong list and the vermicelli list, the parent-child relationship between the Zhonggong list and the Zhonggong list information interface, the parent-child relationship between the vermicelli list and the vermicelli list information interface, the parent-child relationship between the chat and the chat interface, the parent-child relationship between the anchor and the anchor information interface, and the parent-child relationship between the honored guest and the honored guest list interface.
It should be noted that, parent-child relationships among a plurality of interfaces recorded in the interface management list are relative, and for a specific interface, the interface management list can be used as not only a child interface of some interfaces, but also a parent interface of other interfaces; for example, in the above-described exemplary parent-child relationship, "zhonggong list" may be used as a child interface of "ranking," and "zhonggong list" may also be used as a parent interface of "zhonggong list information interface.
Thus, in an embodiment, when the user interface of the user terminal finishes loading the current parent interface, the user terminal may traverse the interface management list, for example, and determine the target sub-interface corresponding to the current parent interface in the interface management list, so that the target sub-interface is loaded on the user interface without loading other interfaces.
For example, in combination with the above example, when the user end uses the "zhonggong list" as the current parent interface and finishes loading the "zhonggong list" on the user interface, the user end may determine the "zhonggong list information interface" as the target sub-interface according to the interface management list of the above example, and load the "zhonggong list information interface" on the user interface, without loading other interfaces such as the "chat interface", the "fan list information interface", and the "honoured list interface".
Therefore, based on the above design, according to the interface loading method provided by the application, by configuring the interface management list in which the parent-child relationship among the multiple interfaces is recorded, when the user interface finishes loading the current parent interface, the target child interface corresponding to the current parent interface can be determined in the interface management list, so that the target child interface is loaded on the user interface.
It should be noted that, in some possible implementations, in order to decouple the interfaces having the association relationship, each interface may be packaged as a corresponding functional plug-in and stored locally at the user end.
In this way, when step 205 is executed, the user end may initialize the target function plug-in corresponding to the target sub-interface, so as to record the target sub-interface in the user interface.
In the above scheme, in which each interface is encapsulated into a corresponding functional plug-in and stored locally at the user side, a plug-in manager can be configured at the user side to uniformly manage all the functional plug-ins.
In addition, in some possible embodiments, the same functional plug-in may be initialized multiple times to load the corresponding sub-interface on the user interface. For example, in an application scenario of live webcasting, a public screen plug-in is required to be used in both live webcasting rooms related to live webcasting and live webcasting, and when a user side directly jumps from the live webcasting room to the live webcasting room, or when the user side closes the live webcasting room and then enters the live webcasting room, a sub-interface corresponding to the public screen plug-in needs to be loaded on a user interface.
Therefore, in an embodiment, all the function plug-ins locally stored at the user end can be initially stored in the hard disk of the user end; in addition, in order to facilitate multiple times of multiplexing of the same functional plug-in, each time a functional plug-in is initialized for the first time, so that when the user interface loads the sub-interface corresponding to the functional plug-in, the user side can store the functional plug-in the memory of the user side, and thus when the functional plug-in is initialized for the next time, the user side can directly obtain the functional plug-in from the memory.
Thus, in an embodiment, the interface management list stored at the user side may further record a state identifier of each functional plug-in, where the state identifier may be used to indicate that the corresponding functional plug-in is stored in a hard disk or a memory of the user side, and the interface management list may be stored in the plug-in manager.
To this end, referring to fig. 5 on the basis of fig. 4, fig. 5 shows another schematic flowchart of the interface loading method provided in the present application, and as a possible implementation manner, before executing step 205, the interface loading method may further include the following steps:
step 204-1, reading a state identifier corresponding to the target function plug-in from the interface management list; when the target function plug-in corresponds to the first state identifier, executing step 204-2; when the target function plug-in corresponds to the second state identifier, executing step 204-3;
step 204-2, acquiring a target function plug-in from a memory;
and step 204-3, acquiring the target function plug-in from the hard disk, and loading the target function plug-in the memory.
In an embodiment, after the user performs step 203 to determine the target sub-interface, the user may read an interface management list stored by the plug-in manager, so as to read the state identifier corresponding to the target function plug-in from the interface management list.
When the user side reads the interface management list and determines that the target function plug-in corresponds to the first state identifier, the representation target function plug-in is loaded in a memory of the user side, and at the moment, the user side acquires the target function plug-in from the memory; when the user reads the interface management list and determines that the target function plug-in corresponds to the second state identifier, the representation target function plug-in is stored in the hard disk of the user, and at the moment, the user acquires the target function plug-in from the hard disk and loads the target function plug-in the memory, so that when the target function plug-in is used next time, the user can acquire the target function plug-in from the memory, and the reusability of the function plug-in is improved.
It should be noted that, when the user side executes step 204-3, the user side may update the interface management list, for example, update the state identifier corresponding to the target function plug-in the interface management list from the second state identifier to the first state identifier, so as to indicate that the target function plug-in is loaded in the memory.
In addition, when the target function plug-in is loaded in the memory, if the corresponding memory space is released, the user side may also update the state identifier corresponding to the target function plug-in the interface management list from the first state identifier to the second state identifier, so as to indicate that the target function plug-in is not loaded in the memory.
It should be noted that, in the implementation manner of encapsulating each interface as a corresponding functional plug-in, each functional plug-in may register other functional plug-ins that need to communicate with the plug-in manager according to the respective function implementation, so as to implement the purpose of communicating among the functional plug-ins by means of the plug-in manager; or, each functional plug-in can call the interfaces of other functional plug-ins for communication through the plug-in manager; alternatively, the communication may be performed by invoking a communication mechanism in the client native system, such as NSNotification in the iOS system.
In addition, in the implementation manner of encapsulating each interface as a corresponding functional plug-in, after the interfaces with the association relationship are decoupled, the user side can operate the functional plug-ins, so that the corresponding interfaces can be maintained conveniently.
For example, referring to fig. 6 on the basis of fig. 5, fig. 6 shows a further schematic flowchart of the interface loading method provided by the present application, and may further include the following steps:
in step 207-1, when the target function plug-in is uninstalled, the target sub-interface is removed from the user interface.
In an embodiment, the user side may monitor the state of each functional plugin in the plugin manager, including the life cycle, parent interface object, functional component information, and the like of each functional plugin, for example, the state of each functional plugin may be recorded by using the interface management list, so that the user side may monitor the state of each functional plugin by reading the interface management class table; after the target sub-interface is loaded in the user interface, if the user side monitors that the target function plug-in is unloaded, the user side can remove the target sub-interface from the user interface; for example, in the user interface shown in fig. 1, assuming that the "zhonggong leaderboard information interface" is used as the target sub-interface, when the target function plug-in corresponding to the "zhonggong leaderboard information interface" is uninstalled, the user end may remove the "zhonggong leaderboard information interface" from the user interface, and the user interface after removing the "zhonggong leaderboard information interface" may be as shown in fig. 7.
In addition, the user side may perform operations such as the uninstalling and the like on the target function plug-in, and in some other possible embodiments of the present application, the user side may perform operations such as updating and the like on the target function plug-in, for example, updating a list and the like.
Thus, referring to fig. 8 on the basis of fig. 5, fig. 8 shows a further schematic flowchart of the interface loading method provided by the present application, and may further include the following steps:
and step 207-2, when the target function plug-in is updated, updating the target sub-interface in the user interface according to the updated target function plug-in.
In an embodiment, the user side may monitor the state of each functional plug-in the plug-in manager by using the above scheme; after the target sub-interface is loaded in the user interface, if the user side monitors that the target function plug-in is updated, the user side may update the target sub-interface in the user interface according to the updated target function plug-in, for example, the target sub-interface may be loaded on the user interface again according to the updated target function plug-in the manner of loading the target sub-interface; for example, in the user interface shown in fig. 1, assuming that the "zhonggong chart information interface" is used as the target sub-interface, when the target function plug-in corresponding to the "zhonggong chart information interface" is updated, the user side may reload the "zhonggong chart information interface", and the user interface after reloading the "zhonggong chart information interface" may be as shown in fig. 9.
It should be noted that, in the above implementation provided by the present application, only one interface is taken as a target sub-interface as an illustration; in some other possible implementations of the present application, the number of the target sub-interfaces corresponding to the current parent interface may also be multiple, such as in the interface management list illustrated in fig. 1, when "ranking" is used as the current parent interface, the corresponding target sub-interfaces include two interfaces, namely "leader board" and "fan board".
Thus, according to the implementation manner provided by the present application, when the "ranking" is completed as the loading of the current parent interface, the user needs to load two sub-interfaces, namely the "gongtangbang list" and the "fan list", in the user interface.
However, if the two sub-interfaces of the "zhonggong list" and the "fan list" are loaded in the user interface at the same time, the user end needs to load more interfaces in a short time, and the interface loading is slow in terms of perception of the user side.
Therefore, as a possible implementation manner, the interface management list stored by the user side may further record the loading priority of each interface, and the loading priority of each interface represents the loading sequence of the corresponding interface; the higher the loading priority is, the more the corresponding interface is loaded into the user interface; and at the bottom of the loading priority month, the later the corresponding interface is loaded into the user interface.
Thus, when the user determines that there are multiple target sub-interfaces corresponding to the current parent interface in the interface management list, the user may sequentially load each target sub-interface in the user interface according to the respective loading priority of each target sub-interface when performing step 205.
For example, in the scenario shown in fig. 1, assuming that the loading priority of the "gong leaderboard" is higher than the loading priority of the "fan leaderboard", when the user determines the "gong leaderboard" and the "fan leaderboard" as the target sub-interfaces according to the interface management list, the user may load the "gong leaderboard" on the user interface first and then load the "fan leaderboard", so that the user interface may display the content to the user more quickly, thereby increasing the loading speed of the interface.
In addition, in some possible implementation manners, different interfaces may have different loading manners, for example, when a user enters a live broadcast room, a live broadcast picture needs to be loaded in a user interface at the fastest speed; some interfaces need to adopt some delay strategies to be loaded in the user interface, such as interface advertisements and other contents; some interfaces may need to meet certain triggering conditions and be loaded in a user interface, for example, a bullet screen interface needs to select a bullet screen mode to display a bullet screen in a live broadcast picture, and if the bullet screen interface selects to close the bullet screen, the bullet screen does not need to be displayed in the live broadcast picture; still other interfaces need to rely on loading after the loading of other interfaces is completed.
Therefore, as a possible implementation manner, the loading manner of each interface can be recorded in the interface management list stored by the user side; when the user side executes step 205, the interface management list may be read, and a target loading manner corresponding to the target sub-interface is obtained from the interface management list, such as immediate loading, delayed loading, triggered loading, or dependent loading in the above example; therefore, the user side can load the target sub-interface on the user interface according to the target loading mode.
In addition, referring to fig. 10 on the basis of fig. 4, fig. 10 shows a further schematic flowchart of the interface loading method provided in the present application, and as a possible implementation manner, before executing step 203, the interface loading method may further include the following steps:
In an embodiment, before performing step 203, the user end may first obtain the interface management list, for example, so as to perform step 203 according to the obtained interface management list.
The method for the user side to obtain the interface management list may be receiving the transmission of other devices such as a server, or reading the local part of the user side.
For example, in an embodiment, in an implementation manner that encapsulates each interface described above as a corresponding functional plug-in and stores all the functional plug-ins in a plug-in manager, the plug-in manager may store information of each functional plug-in, such as a plug-in interface name, a plug-in implementation class, a plug-in interface protocol, a loading manner, a parent loading interface, and the like, in an interface management file in the form of, for example, a JSON (JS object Notation) file; wherein the JSON file can be stored in, for example, a hard disk space at the user side.
When the user side starts the corresponding APP, the user side can read the interface management file into the memory and initialize the interface management file to obtain the interface management list, so that when the interface loading method provided by the application is executed, the interface management list can be read from the memory and the interface management file does not need to be read repeatedly and initialized, and the acquisition efficiency of the interface management list is improved.
In addition, based on the same inventive concept as the above interface loading method provided in the present application, please refer to fig. 11, fig. 11 shows a schematic structural block diagram of an interface loading apparatus 300 provided in the present application, where the interface loading apparatus 300 includes a processing module 301 and a loading module 302. Wherein:
the processing module 301 is configured to determine, in the interface management list, a target child interface corresponding to the current parent interface when the user interface finishes loading the current parent interface; the interface management list records the parent-child relationship among a plurality of interfaces;
and a loading module 302, configured to load the target sub-interface on the user interface.
Optionally, as a possible implementation manner, each interface is packaged as a corresponding functional plug-in for storage;
when the user interface loads the target sub-interface, the loading module 302 is specifically configured to:
and initializing a target function plug-in corresponding to the target sub-interface so as to load the target sub-interface on the user interface.
Optionally, as a possible implementation manner, the interface management list further records a state identifier of each functional plug-in;
before the loading module 302 initializes the target function plug-in corresponding to the target sub-interface to load the target sub-interface on the user interface, the processing module 301 is further configured to:
when the target function plug-in corresponds to the first state identifier, acquiring the target function plug-in from the memory; the first state identification represents that the corresponding functional plug-in is loaded in the memory;
when the target function plug-in corresponds to the second state identifier, acquiring the target function plug-in from the hard disk, and loading the target function plug-in the memory; and the second state identifier represents the corresponding functional plug-in and stores the functional plug-in the hard disk.
Optionally, as a possible implementation manner, the loading module 302 is further configured to:
when the target function plug-in is uninstalled, the target sub-interface is removed from the user interface.
Optionally, as a possible implementation manner, the loading module 302 is further configured to:
and when the target function plug-in is updated, updating the target sub-interface in the user interface according to the updated target function plug-in.
Optionally, as a possible implementation manner, the interface management list further records a loading priority of each interface;
when there are multiple target sub-interfaces, the loading module 302 is specifically configured to, when the user interface loads the target sub-interface:
and sequentially loading each target sub-interface on the user interface according to the loading priority of each target sub-interface.
Optionally, as a possible implementation manner, the interface management list further records a loading manner of each interface;
when the user interface loads the target sub-interface, the loading module 302 is specifically configured to:
and acquiring a target loading mode corresponding to the target sub-interface from the interface management list, and loading the target sub-interface on the user interface according to the target loading mode.
Optionally, as a possible implementation manner, before the processing module 301 determines the target sub-interface corresponding to the current parent interface in the interface management list, the processing module is further configured to:
and acquiring an interface management list.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to some embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s).
It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, functional modules in some embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
The functions, if implemented in the form of software functional modules 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 application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to perform all or part of the steps of the method according to some embodiments of the present application. And the aforementioned storage medium includes: u disk, removable hard disk, read only memory, random access memory, magnetic or optical disk, etc. for storing program codes.
The above description is only a few examples of the present application and is not intended to limit the present application, and those skilled in the art will appreciate that various modifications and variations can be made in the present application. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.
It will be evident to those skilled in the art that the present application is not limited to the details of the foregoing illustrative embodiments, and that the present application may be embodied in other specific forms without departing from the spirit or essential attributes thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the application being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned.
Claims (11)
1. An interface loading method, characterized in that the method comprises:
when the user interface finishes loading the current parent interface, determining a target sub-interface corresponding to the current parent interface in an interface management list; the interface management list records the parent-child relationship among a plurality of interfaces;
and loading the target sub-interface on the user interface.
2. The method of claim 1, wherein each interface is packaged as a corresponding functional plug-in for storage;
the step of loading the target sub-interface on the user interface comprises the following steps:
initializing a target function plug-in corresponding to the target sub-interface so as to load the target sub-interface on the user interface.
3. The method of claim 2, wherein the interface management list further records a status identifier of each functional plug-in;
before the step of initializing a target function plug-in corresponding to the target sub-interface to load the target sub-interface at the user interface, the method further comprises:
when the target function plug-in corresponds to the first state identifier, acquiring the target function plug-in from a memory; the first state identification represents that the corresponding functional plug-in is loaded in the memory;
when the target function plug-in corresponds to the second state identifier, acquiring the target function plug-in from a hard disk, and loading the target function plug-in the memory; and the second state identifier represents the corresponding functional plug-in and stores the functional plug-in the hard disk.
4. The method of claim 2, wherein the method further comprises:
removing the target sub-interface from the user interface when the target function plug-in is uninstalled.
5. The method of claim 2, wherein the method further comprises:
and when the target function plug-in is updated, updating the target sub-interface in the user interface according to the updated target function plug-in.
6. The method of claim 1, wherein the interface management list further records a loading priority of each interface;
when a plurality of target sub-interfaces exist, the step of loading the target sub-interfaces on the user interface comprises the following steps:
and sequentially loading each target sub-interface on the user interface according to the loading priority of each target sub-interface.
7. The method of claim 1, wherein the interface management list further records a loading mode of each interface;
the step of loading the target sub-interface on the user interface comprises the following steps:
and acquiring a target loading mode corresponding to the target sub-interface from the interface management list, and loading the target sub-interface on the user interface according to the target loading mode.
8. The method of claim 1, wherein prior to the step of determining the target child interface corresponding to the current parent interface in an interface management list, the method further comprises:
and acquiring the interface management list.
9. An interface loading apparatus, comprising:
the processing module is used for determining a target sub-interface corresponding to the current parent interface in an interface management list when the user interface finishes loading the current parent interface; the interface management list records the parent-child relationship among a plurality of interfaces;
and the loading module is used for loading the target sub-interface on the user interface.
10. A user terminal, comprising:
a memory for storing one or more programs;
a processor;
the one or more programs, when executed by the processor, implement the method of any of claims 1-8.
11. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010041596.5A CN111258694A (en) | 2020-01-15 | 2020-01-15 | Interface loading method and device, user side and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010041596.5A CN111258694A (en) | 2020-01-15 | 2020-01-15 | Interface loading method and device, user side and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111258694A true CN111258694A (en) | 2020-06-09 |
Family
ID=70947026
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010041596.5A Pending CN111258694A (en) | 2020-01-15 | 2020-01-15 | Interface loading method and device, user side and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111258694A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112181554A (en) * | 2020-09-08 | 2021-01-05 | 安徽鸿程光电有限公司 | Interactive interface display method and device, electronic device and storage medium |
| CN112657186A (en) * | 2020-12-28 | 2021-04-16 | 网易（杭州）网络有限公司 | Game interaction method and device |
| CN113448582A (en) * | 2021-08-27 | 2021-09-28 | 统信软件技术有限公司 | Window display method, computing device and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101944036A (en) * | 2010-09-27 | 2011-01-12 | 苏州光格设备有限公司 | Memory optimization method on basis of rich internet applications (RIA) of industrial monitoring system |
| CN106792188A (en) * | 2016-12-06 | 2017-05-31 | 腾讯数码（天津）有限公司 | A kind of data processing method of live page, device and system |
| CN109697088A (en) * | 2018-11-23 | 2019-04-30 | 努比亚技术有限公司 | Application interface loading method, mobile terminal and computer readable storage medium |
| CN111309293A (en) * | 2020-02-27 | 2020-06-19 | 北京奇艺世纪科技有限公司 | Interface framework construction method and device, electronic equipment and storage medium |
-
2020
- 2020-01-15 CN CN202010041596.5A patent/CN111258694A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101944036A (en) * | 2010-09-27 | 2011-01-12 | 苏州光格设备有限公司 | Memory optimization method on basis of rich internet applications (RIA) of industrial monitoring system |
| CN106792188A (en) * | 2016-12-06 | 2017-05-31 | 腾讯数码（天津）有限公司 | A kind of data processing method of live page, device and system |
| CN109697088A (en) * | 2018-11-23 | 2019-04-30 | 努比亚技术有限公司 | Application interface loading method, mobile terminal and computer readable storage medium |
| CN111309293A (en) * | 2020-02-27 | 2020-06-19 | 北京奇艺世纪科技有限公司 | Interface framework construction method and device, electronic equipment and storage medium |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112181554A (en) * | 2020-09-08 | 2021-01-05 | 安徽鸿程光电有限公司 | Interactive interface display method and device, electronic device and storage medium |
| CN112181554B (en) * | 2020-09-08 | 2023-06-20 | 安徽鸿程光电有限公司 | Interactive interface display method, device, electronic device and storage medium |
| CN112657186A (en) * | 2020-12-28 | 2021-04-16 | 网易（杭州）网络有限公司 | Game interaction method and device |
| CN112657186B (en) * | 2020-12-28 | 2024-02-02 | 网易（杭州）网络有限公司 | Game interaction method and device |
| CN113448582A (en) * | 2021-08-27 | 2021-09-28 | 统信软件技术有限公司 | Window display method, computing device and storage medium |
| CN113448582B (en) * | 2021-08-27 | 2021-12-07 | 统信软件技术有限公司 | Window display method, computing device and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111258694A (en) | Interface loading method and device, user side and storage medium | |
| KR20220127887A (en) | Method and apparatus for displaying live broadcast data, device and storage medium | |
| CN111814089B (en) | Page rendering method and device, rendering server and storage medium | |
| CN111756917B (en) | Information interaction method, electronic device and computer readable medium | |
| CN110381332A (en) | Direct broadcasting room component processing method, device, electronic equipment and readable storage medium storing program for executing | |
| CN108228293B (en) | Interface skin switching method and device | |
| CN111090423B (en) | Webhook framework system and method for realizing active calling and event triggering | |
| CN111258740A (en) | Method and device for starting application program and electronic equipment | |
| CN112218108B (en) | Live broadcast rendering method and device, electronic equipment and storage medium | |
| CN110007936B (en) | Data processing method and device | |
| CN112766945A (en) | Virtual resource allocation processing method, device, equipment and storage medium | |
| CN109168012B (en) | Information processing method and device for terminal equipment | |
| CN112068850A (en) | Method and device for creating service product instance and electronic equipment | |
| CN113900721A (en) | Operating system starting method and device and electronic equipment | |
| CN108764866B (en) | Method and equipment for allocating resources and drawing resources | |
| CN111209065A (en) | Dynamic wallpaper setting method and device, storage medium and electronic equipment | |
| CN113312237A (en) | Information feedback method and device, electronic equipment and storage medium | |
| CN111124523A (en) | Method and apparatus for initializing applications | |
| CN111382039A (en) | Method, device, electronic equipment and storage medium for reporting user behavior event | |
| CN115225950A (en) | Video playing control method and device | |
| CN112230819B (en) | Information processing method, information processing apparatus, storage medium, and electronic device | |
| CN110262912B (en) | Calling method and device for procedure call gRPC | |
| CN115525834A (en) | Method for screening and displaying messages, computer device and recording medium | |
| CN111143740B (en) | Information processing method and device and electronic equipment | |
| CN110324722B (en) | Method, device, equipment and storage medium for acquiring data in live broadcast room |
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 |