阅读说明：本技术 应用程序界面切换方法、装置 (Application program interface switching method and device ) 是由 王谱 龙振海 李帅 于 2019-11-26 设计创作，主要内容包括：本申请的实施例提供了一种应用程序界面切换方法、装置。该方法包括：将第一界面显示在第一界面容器中；响应于用户在第一界面上的第一操作指令,获取第二界面元素；生成第二界面容器,所述第二界面容器的堆栈位置在第一界面容器的堆栈位置之上；将所述第二界面元素显示在所述第二界面容器中,以将第一界面切换至第二界面。本申请实施例的技术方案可以增强应用程序界面在切换过程中的稳定性。(The embodiment of the application provides an application program interface switching method and device. The method comprises the following steps: displaying a first interface in a first interface container; responding to a first operation instruction of a user on the first interface, and acquiring a second interface element; generating a second interface container having a stacked position above the stacked position of the first interface container; displaying the second interface element in the second interface container to switch the first interface to the second interface. The technical scheme of the embodiment of the application can enhance the stability of the application program interface in the switching process.)

1. An application program interface switching method is characterized by comprising the following steps:

displaying a first interface in a first interface container;

responding to a first operation instruction of a user on the first interface, and acquiring a second interface element;

generating a second interface container having a stacked position above the stacked position of the first interface container;

displaying the second interface element in the second interface container to switch the first interface to the second interface.

2. The method of claim 1, wherein the first interface container includes a first container correlation engine therein, and wherein prior to displaying the second interface element in the second interface container, the method further comprises:

transferring the first container correlation engine from a first interface container to the second interface container;

associating the second interface container with a local interface container based on the first container association engine.

3. The method of claim 2, wherein the displaying the second interface element in the second interface container comprises:

generating a second interface element carrier in the second interface container;

loading the second interface element into the second interface element carrier to display the second interface element in the second interface container.

4. The method of claim 2, wherein after switching the first interface to the second interface, the method further comprises:

and in response to a second operation instruction of the user on the second interface, removing the second interface container to display the first interface in the first interface container so as to switch the second interface to the first interface.

5. The method of claim 4, wherein prior to removing the second interface container, the method further comprises:

transferring the first container correlation engine from a second interface container to the first interface container;

associating the first interface container with a local interface container based on the first container association engine.

6. The method of claim 1, wherein the first interface container includes a first interface element carrier therein, and wherein prior to displaying the second interface element in the second interface container, the method further comprises:

transferring the first interface element carrier from a first interface container to the second interface container;

loading the second interface element into the first interface element carrier to display the second interface element in the second interface container.

7. The method of claim 6, wherein displaying the second interface element in the second interface container comprises:

generating a second container correlation engine in the second interface container;

associating the second interface container with a local interface container based on the second container association engine.

8. The method of claim 1, wherein the first interface container comprises a first container correlation engine and a first interface element carrier,

prior to displaying the second interface element in the second interface container, the method further comprises:

transferring the first container correlation engine from a first interface container to the second interface container to correlate the second interface container with a local interface container;

transferring the first interface element carrier from a first interface container to the second interface container to load the second interface element into the first interface element carrier to display the second interface element in the second interface container.

9. The method of claim 1, wherein displaying the second interface element in the second interface container comprises:

generating a second container association engine in the second interface container to associate the second interface container with a local interface container;

generating a second interface element carrier in the second interface container to load the second interface element into the second interface element carrier to display the second interface element in the second interface container.

10. An application interface switching apparatus, comprising:

a first display unit for displaying a first interface in a first interface container;

the acquisition unit is used for responding to a first operation instruction of a user on the first interface and acquiring a second interface element;

a generating unit configured to generate a second interface container having a stack position above a stack position of the first interface container;

a second display unit configured to display the second interface element in the second interface container to switch the first interface to the second interface.

Technical Field

The application relates to the technical field of computers, in particular to an application program interface switching method and device.

Background

In an application interface switching scenario, for example, in a cross-platform development mode, an interface stack is generally customized to manage all generated interfaces, or the interface stack is hosted to a system for interface management. However, how to enhance the stability of the application program interface in the switching process is a technical problem to be solved urgently.

Disclosure of Invention

Embodiments of the present application provide a method and an apparatus for switching an application program interface, a computer-readable medium, and an electronic device, so that the stability of switching the application program interface can be enhanced at least to a certain extent.

Other features and advantages of the present application will be apparent from the following detailed description, or may be learned by practice of the application.

According to an aspect of an embodiment of the present application, there is provided an application program interface switching method, including: displaying a first interface in a first interface container; responding to a first operation instruction of a user on the first interface, and acquiring a second interface element; generating a second interface container having a stacked position above the stacked position of the first interface container; displaying the second interface element in the second interface container to switch the first interface to the second interface.

According to an aspect of the embodiments of the present application, there is provided an application interface switching apparatus, including: a first display unit for displaying a first interface in a first interface container; the acquisition unit is used for responding to a first operation instruction of a user on the first interface and acquiring a second interface element; a generating unit configured to generate a second interface container having a stack position above a stack position of the first interface container; a second display unit configured to display the second interface element in the second interface container to switch the first interface to the second interface.

In some embodiments of the present application, based on the foregoing solution, the first interface container includes a first container association engine therein, and the application program interface switching apparatus further includes a first transfer unit, configured to transfer the first container association engine from the first interface container to the second interface container before the second interface element is displayed in the second interface container; and the association unit is used for associating the second interface container with the local interface container based on the first container association engine.

In some embodiments of the present application, based on the foregoing, the second display unit is configured to: generating a second interface element carrier in the second interface container; loading the second interface element into the second interface element carrier to display the second interface element in the second interface container.

In some embodiments of the present application, based on the foregoing solution, the first display unit is configured to: after the first interface is switched to the second interface, in response to a second operation instruction of the user on the second interface, the second interface container is removed to display the first interface in the first interface container, so that the second interface is switched to the first interface.

In some embodiments of the present application, based on the foregoing solution, the first transfer unit is configured to: transferring the first container correlation engine from the second interface container to the first interface container prior to removing the second interface container; the association unit is configured to: associating the first interface container with a local interface container based on the first container association engine.

In some embodiments of the present application, based on the foregoing solution, the first interface container includes a first interface element carrier therein, and the application program interface switching apparatus further includes a second transfer unit, configured to transfer the first interface element carrier from the first interface container to the second interface container before the second interface element is displayed in the second interface container; a loading unit configured to load the second interface element into the first interface element carrier to display the second interface element in the second interface container.

In some embodiments of the present application, based on the foregoing, the second display unit is configured to: generating a second container correlation engine in the second interface container; associating the second interface container with a local interface container based on the second container association engine.

In some embodiments of the present application, based on the foregoing solution, the first interface container includes a first container association engine and a first interface element carrier, and the application interface switching apparatus further includes a third transferring unit, configured to transfer the first container association engine from the first interface container to the second interface container to associate the second interface container with the local interface container before displaying the second interface element in the second interface container; transferring the first interface element carrier from a first interface container to the second interface container to load the second interface element into the first interface element carrier to display the second interface element in the second interface container.

In some embodiments of the present application, based on the foregoing, the second display unit is configured to: generating a second container correlation engine in the second interface container to correlate the second interface container and a local interface container. Generating a second interface element carrier in the second interface container to load the second interface element into the second interface element carrier to display the second interface element in the second interface container.

According to an aspect of the embodiments of the present application, there is provided a computer readable medium, on which a computer program is stored, the computer program, when executed by a processor, implementing the application program interface switching method as described in the above embodiments.

According to an aspect of an embodiment of the present application, there is provided an electronic device including: one or more processors; a storage device for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement the application program interface switching method as described in the above embodiments.

In the technical solutions provided in some embodiments of the present application, a second interface element is obtained through a first operation instruction on a first interface, a second interface container is generated on a stack position of the first interface container where the first interface is located, and then the obtained second interface element is displayed in the second interface container, so as to switch the first interface to the second interface. In the scheme, the first interface is managed by the first interface container, and the second interface is managed by the generated second interface container, so that the possibility of confusion of the first interface and the second interface in the switching process is reduced, for example, in the process of returning and quitting the interfaces, the interfaces can be ensured to return one by one without returning all the interfaces at one time, and the stability of the application program interface in the switching process can be enhanced.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application. It is obvious that the drawings in the following description are only some embodiments of the application, and that for a person skilled in the art, other drawings can be derived from them without inventive effort. In the drawings:

FIG. 1 illustrates an implementation environment diagram of a solution according to an embodiment of the present application;

FIG. 2 illustrates an application diagram of an application program interface switching method according to one embodiment of the present application;

FIG. 3 illustrates a flow diagram of an application interface switching method according to one embodiment of the present application;

FIG. 4 illustrates a method flow diagram prior to displaying the second interface element in the second interface container according to one embodiment of the present application;

FIG. 5 illustrates a detailed flow diagram for displaying the second interface element in the second interface container according to one embodiment of the present application;

FIG. 6 illustrates a flow diagram of a method prior to removing the second interface container, in accordance with an embodiment of the present application;

FIG. 7 illustrates a stack structure diagram for application interface switching according to one embodiment of the present application;

FIG. 8 illustrates a method flow diagram prior to displaying the second interface element in the second interface container according to one embodiment of the present application;

FIG. 9 illustrates a detail flow diagram for displaying the second interface element in the second interface container according to one embodiment of the present application;

FIG. 10 illustrates a stack structure diagram of application interface switching according to one embodiment of the present application;

FIG. 11 illustrates a method flow diagram prior to displaying the second interface element in the second interface container according to one embodiment of the present application;

FIG. 12 illustrates a stack structure diagram for application interface switching according to one embodiment of the present application;

FIG. 13 illustrates a detail flow diagram for displaying the second interface element in the second interface container according to one embodiment of the present application;

FIG. 14 illustrates a stack structure diagram of application interface switching according to one embodiment of the present application;

FIG. 15 shows a block diagram of an application interface switching device according to an embodiment of the present application;

FIG. 16 illustrates a schematic structural diagram of a computer system suitable for use in implementing the electronic device of an embodiment of the present application.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art.

Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the application. One skilled in the relevant art will recognize, however, that the subject matter of the present application can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and so forth. In other instances, well-known methods, devices, implementations, or operations have not been shown or described in detail to avoid obscuring aspects of the application.

The block diagrams shown in the figures are functional entities only and do not necessarily correspond to physically separate entities. I.e. these functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor means and/or microcontroller means.

The flow charts shown in the drawings are merely illustrative and do not necessarily include all of the contents and operations/steps, nor do they necessarily have to be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the actual execution sequence may be changed according to the actual situation.

Fig. 1 shows an implementation environment diagram of a technical solution according to an embodiment of the present application.

As shown in fig. 1, an implementation environment of the technical solution of the embodiment of the present application may include a terminal device. For example, any one of the smart phone 101, the tablet computer 102, the touch display 103 and the portable computer 104 shown in fig. 1 is included, but other electronic devices with touch display function and the like are also possible.

In an embodiment of the present application, a user may implement the technical solution of the embodiment of the present application by using a smartphone with a touch display function, such as the smartphone 101 shown in fig. 1. Specifically, the screen of the smart phone may display an interface, and the interface displayed in the screen may be switched.

To make the present application more intuitive for those skilled in the art, a specific example will be described herein.

In a specific implementation of an embodiment, the technical solution of the present application may be implemented with reference to the application shown in fig. 2, for example, fig. 2 shows an application schematic diagram of an application program interface switching method according to an embodiment of the present application.

As shown in fig. 2, a switching effect of an interface of a display device under different operation instructions is shown, wherein in a cell phone screen in a state 201, an APP (application) icon in a local interface is touched to enter an application program, and at this time, a first interface shown as a state 202 is displayed in the cell phone screen. Further, after touching the "second interface" button in the first interface, the interface in the cell phone screen enters the second interface as shown in screen state 203, and in further operation, the interface in the cell phone screen returns to the first interface as shown in state 204 by touching the "back" button in the second interface.

It should be understood to those skilled in the art that the operation on the screen is not limited to the touch manner as shown above, and may be a manner of inputting with a keyboard. It may be a mouse click method or a voice recognition method based on an Artificial Intelligence Engine (AIE).

The implementation details of the technical solution of the embodiment of the present application are set forth in detail below:

according to a first aspect of the present disclosure, an application program interface switching method is provided.

Referring to fig. 3, a flowchart of an application interface switching method according to an embodiment of the present application is shown, which may be performed by a device having a computing processing function, such as the smartphone 101 shown in fig. 1, or the tablet 102 shown in fig. 1. As shown in fig. 3, the method for switching the application program interface at least includes steps 310 to 370:

step 310, displaying the first interface in the first interface container.

Step 330, in response to a first operation instruction of the user on the first interface, acquiring a second interface element.

Step 350, a second interface container is generated, the second interface container having a stack position above the stack position of the first interface container.

Step 370, displaying the second interface element in the second interface container to switch the first interface to the second interface.

The steps carried out as above will be explained in detail below:

in steps 310 to 330, displaying a first interface in a first interface container; and responding to a first operation instruction of the user on the first interface, and acquiring the second interface element.

In the present application, by displaying a first interface in a first interface container, the first interface may be caused to be presented in a display screen.

It should be noted that, in the present application, the second interface element may specifically include one or more of pictures, words, symbols, link entries, interface components, and the like.

In steps 350 through 370, generating a second interface container having a stacked position above the stacked position of the first interface container; displaying the second interface element in the second interface container to switch the first interface to the second interface.

In this application, the first interface container may include a first container association engine, where the container association engine is mainly used to associate the interface container in the application program with the interface container in the local system, so that the interface of the application program can be normally displayed on the display interface supported by the local system.

In this application, the first interface container may further include a first interface element carrier, where the interface element carrier is mainly used for carrying and managing interface elements.

In the present application, the steps shown as the above steps 350 to 370 can be implemented by the following embodiments:

the first embodiment,

In this embodiment, before the second interface element is displayed in the second interface container, the steps shown in fig. 4 may be implemented.

Referring to fig. 4, which shows a flowchart of a method before displaying the second interface element in the second interface container according to an embodiment of the present application, specifically, steps 361 to 362 may be included:

step 361, transferring the first container correlation engine from the first interface container to the second interface container.

Step 362, associating the second interface container with a local interface container based on the first container association engine.

Further, after associating the second interface container with a local interface container based on the first container association engine, the displaying the second interface element in the second interface container may be implemented by the steps shown in fig. 5.

Referring to fig. 5, a detailed flowchart for displaying the second interface element in the second interface container according to an embodiment of the present application is shown, which may specifically include steps 371 to 372:

step 371, generate a second interface element carrier in the second interface container.

And 372, loading the second interface element into the second interface element carrier to display the second interface element in the second interface container.

In this embodiment, by transferring the first container correlation engine in the first interface container to the generated second interface container and simultaneously generating the second interface element carrier in the generated second interface container, the second interface container can be correlated with the local interface container without regenerating and initializing a new container correlation engine. The method has the advantages that the technical problem of memory occupation caused by the excessive number of the container correlation engines can be solved on the first aspect, and the time required for regenerating and initializing the new container correlation engines can be saved on the second aspect, so that the interface switching efficiency is improved. In the third aspect, the fluency of the interface in the switching process can be improved, for example, the condition that the interface has a black screen in the switching process can be prevented.

With continued reference to this embodiment, after the first interface is switched to the second interface, the second interface may also be switched to the first interface, which may specifically be implemented as follows:

and in response to a second operation instruction of the user on the second interface, removing the second interface container to display the first interface in the first interface container so as to switch the second interface to the first interface.

Specifically, before removing the second interface container, the steps shown in fig. 6 may be further performed.

Referring to fig. 6, a flowchart of a method before removing the second interface container according to an embodiment of the present application is shown, which may specifically include steps 381 to 382:

step 381, transfer the first container correlation engine from the second interface container to the first interface container.

Step 382, associating the first interface container with a local interface container based on the first container association engine.

In order to make the technical solution of the present embodiment more intuitive and understandable for those skilled in the art, a specific demonstration will be described below with reference to fig. 7.

FIG. 7 shows a stack structure diagram of application interface switching according to one embodiment of the present application.

As can be seen from the figure, state 1 shown in 701 and 705 is a stack structure state when the first interface is displayed, and state 2 shown in 703 is a stack structure state when the second interface is displayed, and it can be seen from process 1 shown in 702 that, in the process of switching the first interface to the second interface, a second interface container is generated above the stack position of the first interface container, and a second interface element carrier is generated in the second interface container, and at the same time, the first container correlation engine in the first interface container is transferred to the second interface container. As can be seen from process 2 shown in 704, in the process of switching the second interface to the first interface, the first container association engine in the second interface container is transferred to the first interface container, and then the second interface container is removed.

Example II,

In this embodiment, before the second interface element is displayed in the second interface container, the steps shown in fig. 8 may be implemented.

Referring to fig. 8, a flowchart of a method before displaying the second interface element in the second interface container according to an embodiment of the present application is shown, which may specifically include steps 363 to 364:

at step 363, the first interface element carrier is transferred from the first interface container to the second interface container.

Step 364, loading the second interface element into the first interface element carrier to display the second interface element in the second interface container.

Further, after the second interface element is loaded into the first interface element carrier, the displaying of the second interface element in the second interface container may be implemented by the steps shown in fig. 9.

Referring to fig. 9, a detailed flowchart for displaying the second interface element in the second interface container according to an embodiment of the present application is shown, which may specifically include steps 373 to 374:

step 373, generating a second container correlation engine in the second interface container.

Step 374, associating the second interface container with a local interface container based on the second container association engine.

With continued reference to this embodiment, after the first interface is switched to the second interface, the second interface may also be switched to the first interface, which may specifically be implemented as follows:

and in response to a second operation instruction of the user on the second interface, removing the second interface container to display the first interface in the first interface container so as to switch the second interface to the first interface.

Specifically, before the second interface container is removed, the first interface element carrier may be transferred from the second interface container to the first interface container, so as to load the elements in the first interface into the first interface element carrier.

In order to make the technical solution of the present embodiment more intuitive and understandable for those skilled in the art, a specific demonstration will be described below with reference to fig. 10.

FIG. 10 is a diagram illustrating a stack structure for application interface switching, according to one embodiment of the present application.

As can be seen from the figure, state 1 shown in 1001 and 1005 is a stack structure state when the first interface is displayed, and state 2 shown in 1003 is a stack structure state when the second interface is displayed, and it can be seen from process 1 shown in 1002 that, in the process of switching the first interface to the second interface, a second interface container is generated above the stack position of the first interface container, and a second container correlation engine is generated in the second interface container, and at the same time, the first interface element carrier in the first interface container is transferred to the second interface container. As can be seen from process 2 shown in 1004, during the process of switching the second interface to the first interface, the first interface element carrier in the second interface container is transferred to the first interface container, and then the second interface container is removed.

Example III,

In this embodiment, before the second interface element is displayed in the second interface container, the steps shown in fig. 11 may be implemented.

Referring to fig. 11, a flowchart of a method before displaying the second interface element in the second interface container according to an embodiment of the present application is shown, which may specifically include steps 365 to 366:

step 365, transferring the first container correlation engine from the first interface container to the second interface container to correlate the second interface container with the local interface container.

Step 366, transferring the first interface element carrier from the first interface container to the second interface container to load the second interface element into the first interface element carrier, so as to display the second interface element in the second interface container.

With continued reference to this embodiment, after the second interface element is displayed in the second interface container, the second interface may be switched to the first interface, which may specifically be implemented as follows:

and in response to a second operation instruction of the user on the second interface, removing the second interface container to display the first interface in the first interface container so as to switch the second interface to the first interface.

Specifically, before removing the second interface container, the first interface element carrier and the first container correlation engine may be respectively transferred from the second interface container to the first interface container.

In order to make the technical solution of the present embodiment more intuitive and understandable for those skilled in the art, a specific demonstration will be described below with reference to fig. 12.

FIG. 12 is a diagram illustrating a stack structure for application interface switching, according to one embodiment of the present application.

As can be seen from the figure, state 1 shown in 1201 and 1205 is a stack structure state when the first interface is displayed, and state 2 shown in 1203 is a stack structure state when the second interface is displayed, and it can be seen from process 1 shown in 1202 that, in the process of switching the first interface to the second interface, a second interface container is generated above the stack position of the first interface container, and at the same time, the first interface element carrier and the first container correlation engine in the first interface container are transferred to the second interface container. As can be seen from process 2 shown in 1204, in the process of switching the second interface to the first interface, the first interface element carrier and the first container correlation engine in the second interface container are transferred to the first interface container, and then the second interface container is removed.

Example four,

In this embodiment, the displaying the second interface element in the second interface container may be implemented by the steps shown in fig. 13.

Referring to fig. 13, a detailed flowchart for displaying the second interface element in the second interface container according to an embodiment of the present application is shown, which may specifically include steps 375 to 376:

at step 375, a second container association engine is generated in the second interface container to associate the second interface container with the local interface container.

Step 376, generating a second interface element carrier in the second interface container, so as to load the second interface element into the second interface element carrier, so as to display the second interface element in the second interface container.

With continued reference to this embodiment, after the second interface element is displayed in the second interface container, the second interface may be switched to the first interface, which may specifically be implemented as follows:

and in response to a second operation instruction of the user on the second interface, removing the second interface container to display the first interface in the first interface container so as to switch the second interface to the first interface.

In order to make the technical solution of the present embodiment more intuitive and understandable for those skilled in the art, a specific demonstration will be described below with reference to fig. 14.

FIG. 14 is a diagram illustrating a stack structure for application interface switching, according to one embodiment of the present application.

As can be seen from the figure, state 1 shown in 1401 and 1403 is the stack structure state when the first interface is displayed, and state 2 shown in 1402 is the stack structure state when the second interface is displayed, during the process of switching the first interface to the second interface, a second interface container is generated on the stack position of the first interface container, and a second container correlation engine and a second interface element carrier are generated in the second interface container, during the process of switching the second interface to the first interface, the generated second interface container is removed.

In order to make the present application more understandable to those skilled in the art, the present application will be described in a specific application scenario with reference to embodiment one:

the application can be applied to an Android APP end and an iOS APP end, and relates to a hybrid development mode of Flutter and Native. Wherein, Flutter is the mobile UI framework of google, and can quickly construct a high-quality native user interface on iOS and Android.

In application, the interface stack of Flutter can be managed by being hosted to a Native interface stack, for example, the interface stack hosted to Android Native can be managed. Specifically, the interface stack of the Flutter is established on the Native interface stack, wherein the Flutter interface element is loaded in the Flutter interface container through the Flutter View to display the Flutter interface, and in addition, the Flutter interface is associated with the Native interface through a Flutter engine.

In the interface switching process, for example, when entering a new Flutter interface, a Flutter View may be generated in a new Flutter interface container for loading an interface element of the new Flutter interface, and the Flutter engine in the previous Flutter interface is transferred to the new Flutter interface, that is, the application scenario only multiplexes the Flutter engine but not the Flutter View, so that switching of the Flutter interface may be implemented.

In the application scenario, since it takes a long time to generate a new Flutter engine, and the Flutter engine occupies a large memory and the Flutter View occupies a small memory, the advantage of multiplexing the Flutter engine instead of multiplexing the Flutter View is that the interface switching speed can be increased and the interface switching fluency can be enhanced, and the problem of excessive memory occupation can be avoided.

In the technical solutions provided in some embodiments of the present application, a second interface element is obtained through a first operation instruction on a first interface, a second interface container is generated on a stack position of the first interface container where the first interface is located, and then the obtained second interface element is displayed in the second interface container, so as to switch the first interface to the second interface. In the scheme, the first interface is managed by the first interface container, and the second interface is managed by the generated second interface container, so that the possibility of confusion of the first interface and the second interface in the switching process is reduced, for example, in the process of returning and quitting the interfaces, the interfaces can be ensured to return one by one without returning all the interfaces at one time, and the stability of the application program interface in the switching process can be enhanced.

The following describes embodiments of an apparatus of the present application, which may be used to execute the application interface switching method in the foregoing embodiments of the present application. For details that are not disclosed in the embodiments of the apparatus of the present application, please refer to the embodiments of the application interface switching method described above in the present application.

FIG. 15 shows a block diagram of an application interface switching device according to an embodiment of the present application.

Referring to fig. 15, an application interface switching apparatus 1500 according to an embodiment of the present application includes: a first display unit 1501, an acquisition unit 1502, a generation unit 1503, and a second display unit 1504.

The first display unit 1501 is used for displaying a first interface in the first interface container; an obtaining unit 1502, configured to obtain a second interface element in response to a first operation instruction of a user on a first interface; a generating unit 1503, configured to generate a second interface container having a stack position above the stack position of the first interface container; a second display unit 1504 used to display the second interface element in the second interface container to switch the first interface to the second interface.

In some embodiments of the present application, based on the foregoing solution, the first interface container includes a first container association engine therein, and the application program interface switching apparatus further includes a first transfer unit, configured to transfer the first container association engine from the first interface container to the second interface container before the second interface element is displayed in the second interface container; and the association unit is used for associating the second interface container with the local interface container based on the first container association engine.

In some embodiments of the present application, based on the foregoing solution, the second display unit 1504 is configured to: generating a second interface element carrier in the second interface container; loading the second interface element into the second interface element carrier to display the second interface element in the second interface container.

In some embodiments of the present application, based on the foregoing solution, the first display unit 1501 is configured to: after the first interface is switched to the second interface, in response to a second operation instruction of the user on the second interface, the second interface container is removed to display the first interface in the first interface container, so that the second interface is switched to the first interface.

In some embodiments of the present application, based on the foregoing solution, the first transfer unit is configured to: transferring the first container correlation engine from the second interface container to the first interface container prior to removing the second interface container; the association unit is configured to: associating the first interface container with a local interface container based on the first container association engine.

In some embodiments of the present application, based on the foregoing solution, the first interface container includes a first interface element carrier therein, and the application program interface switching apparatus further includes a second transfer unit, configured to transfer the first interface element carrier from the first interface container to the second interface container before the second interface element is displayed in the second interface container; a loading unit configured to load the second interface element into the first interface element carrier to display the second interface element in the second interface container.

In some embodiments of the present application, based on the foregoing solution, the second display unit 1504 is configured to: generating a second container correlation engine in the second interface container; associating the second interface container with a local interface container based on the second container association engine.

In some embodiments of the present application, based on the foregoing solution, the first interface container includes a first container association engine and a first interface element carrier, and the application interface switching apparatus further includes a third transferring unit, configured to transfer the first container association engine from the first interface container to the second interface container to associate the second interface container with the local interface container before displaying the second interface element in the second interface container; transferring the first interface element carrier from a first interface container to the second interface container to load the second interface element into the first interface element carrier to display the second interface element in the second interface container.

In some embodiments of the present application, based on the foregoing solution, the second display unit 1504 is configured to: generating a second container correlation engine in the second interface container to correlate the second interface container and a local interface container. Generating a second interface element carrier in the second interface container to load the second interface element into the second interface element carrier to display the second interface element in the second interface container.

FIG. 16 illustrates a schematic structural diagram of a computer system suitable for use in implementing the electronic device of an embodiment of the present application.

It should be noted that the computer system 1600 of the electronic device shown in fig. 16 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.

As shown in fig. 16, computer system 1600 includes a Central Processing Unit (CPU)1601, which can perform various appropriate actions and processes, such as executing the methods described in the above embodiments, according to a program stored in a Read-Only Memory (ROM) 1602 or a program loaded from a storage portion 1608 into a Random Access Memory (RAM) 1603. In the RAM 1603, various programs and data necessary for system operation are also stored. The CPU 1601, ROM 1602, and RAM 1603 are connected to each other via a bus 1604. An Input/Output (I/O) interface 1605 is also connected to the bus 1604.

The following components are connected to the I/O interface 1605: an input portion 1606 including a keyboard, a mouse, and the like; an output section 1607 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, a speaker, and the like; a storage portion 1608 including a hard disk and the like; and a communication section 1609 including a Network interface card such as a LAN (Local Area Network) card, a modem, or the like. The communication section 1609 performs communication processing via a network such as the internet. The driver 1610 is also connected to the I/O interface 1605 as needed. A removable medium 1611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 1610 as necessary, so that a computer program read out therefrom is mounted in the storage portion 1608 as necessary.

In particular, according to embodiments of the application, the processes described above with reference to the flow diagrams may be implemented as computer software programs. For example, embodiments of the present application include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated by the flow chart. In such embodiments, the computer program may be downloaded and installed from a network via the communication portion 1609, and/or installed from the removable media 1611. When the computer program is executed by a Central Processing Unit (CPU)1601, various functions defined in the system of the present application are executed.

It should be noted that the computer readable medium shown in the embodiments of the present application may be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a Read-Only Memory (ROM), an Erasable Programmable Read-Only Memory (EPROM), a flash Memory, an optical fiber, a portable Compact Disc Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In this application, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. Each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units described in the embodiments of the present application may be implemented by software, or may be implemented by hardware, and the described units may also be disposed in a processor. Wherein the names of the elements do not in some way constitute a limitation on the elements themselves.

As another aspect, the present application also provides a computer-readable medium, which may be contained in the electronic device described in the above embodiments; or may exist separately without being assembled into the electronic device. The computer readable medium carries one or more programs which, when executed by an electronic device, cause the electronic device to implement the method described in the above embodiments.

It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the application. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.

Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the method according to the embodiments of the present application.

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains.

It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.