Application program interface switching method and device
By generating new interface containers and managing interface elements during application interface switching, the problem of insufficient stability during interface switching is solved, and the smoothness and stability of interface switching is achieved, avoiding chaos when interface returns.
Patent Information
- Application Number
- CN201911174457.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2019-11-26
- Publication Date
- 2024-11-01
- Estimated Expiration
- 2039-12-19
AI Technical Summary
In cross-platform development mode, the stability of the application interface is insufficient during switching, resulting in confusion in the interface and the problem of returning and exiting may occur at one time.
By generating a second interface container above the stack position of the first interface container and displaying the second interface elements in the container, the first interface and the second interface are managed, ensuring the stability of interface switching and return. The specific steps include transferring the first interface container association engine to the second interface container during switching, and generating the second interface element carrier in the second interface container, avoiding regenerating and initializing the new container engine, reducing memory usage and improving switching efficiency .
It enhances the stability of the application interface during the switching process, prevents interface chaos, ensures that the interface returns one by one without returning all interfaces at once, and improves the smoothness and efficiency of interface switching.
Smart Images

Figure CN112860139B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to a method and device for switching an application program interface. Background Art
[0002] In the scenario of switching application interfaces, such as the interface switching scenario of applications in cross-platform development mode, it is usually necessary to customize an interface stack to manage all generated interfaces, or to host the interface stack to the system for interface management. However, how to enhance the stability of the application interface during the switching process is a technical problem that needs to be solved urgently. Summary of the invention
[0003] The embodiments of the present application provide an application program interface switching method, device, computer-readable medium, and electronic device, which can enhance the stability of application program interface switching at least to a certain extent.
[0004] Other features and advantages of the present application will become apparent from the following detailed description, or may be learned in part by the practice of the present application.
[0005] According to one aspect of an embodiment of the present application, a method for switching an application interface is provided, comprising: displaying a first interface in a first interface container; obtaining a second interface element in response to a first operation instruction of a user on the first interface; generating a second interface container, the stack position of the second interface container being above the stack position of the first interface container; and displaying the second interface element in the second interface container to switch the first interface to the second interface.
[0006] According to one aspect of an embodiment of the present application, an application interface switching device is provided, including: a first display unit, used to display a first interface in a first interface container; an acquisition unit, used to acquire a second interface element in response to a first operation instruction of a user on the first interface; a generation unit, used to generate a second interface container, the stack position of the second interface container being above the stack position of the first interface container; and a second display unit, used to display the second interface element in the second interface container to switch the first interface to the second interface.
[0007] In some embodiments of the present application, based on the aforementioned scheme, the first interface container includes a first container association engine, and the application interface switching device also includes a first transfer unit, which is used to transfer the first container association engine from the first interface container to the second interface container before displaying the second interface element in the second interface container; an association unit, which is used to associate the second interface container and the local interface container based on the first container association engine.
[0008] In some embodiments of the present application, based on the aforementioned scheme, the second display unit is configured to: generate a second interface element carrier in the second interface container; load the second interface element into the second interface element carrier to display the second interface element in the second interface container.
[0009] In some embodiments of the present application, based on the aforementioned scheme, the first display unit is configured to: after switching the first interface to the second interface, in response to a second operation instruction of the user on the second interface, remove the second interface container to display the first interface in the first interface container to switch the second interface to the first interface.
[0010] In some embodiments of the present application, based on the aforementioned scheme, the first transfer unit is configured to: transfer the first container association engine from the second interface container to the first interface container before removing the second interface container; the association unit is configured to: associate the first interface container and the local interface container based on the first container association engine.
[0011] In some embodiments of the present application, based on the aforementioned scheme, the first interface container includes a first interface element carrier, and the application interface switching device also includes a second transfer unit, which is used to transfer the first interface element carrier from the first interface container to the second interface container before displaying the second interface element in the second interface container; a loading unit, which is used to load the second interface element into the first interface element carrier to display the second interface element in the second interface container.
[0012] In some embodiments of the present application, based on the aforementioned solution, the second display unit is configured to: generate a second container association engine in the second interface container; and associate the second interface container with a local interface container based on the second container association engine.
[0013] In some embodiments of the present application, based on the aforementioned scheme, the first interface container includes a first container association engine and a first interface element carrier, and the application interface switching device also includes a third transfer unit, which is used to transfer the first container association engine from the first interface container to the second interface container before displaying the second interface element in the second interface container to associate the second interface container with the local interface container; transfer 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 to display the second interface element in the second interface container.
[0014] In some embodiments of the present application, based on the above solution, the second display unit is configured to: generate a second container association engine in the second interface container to associate the second interface container with the local interface container. Generate 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.
[0015] According to one aspect of an embodiment of the present application, a computer-readable medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the application program interface switching method described in the above embodiment is implemented.
[0016] According to one aspect of an embodiment of the present application, an electronic device is provided, comprising: one or more processors; a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the application interface switching method as described in the above embodiments.
[0017] In the technical solutions provided by some embodiments of the present application, the second interface element is obtained through the first operation instruction on the first interface, and the second interface container is generated on the 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 to switch the first interface to the second interface. In this solution, since the first interface is managed by the first interface container and the second interface is managed by the generated second interface container, the possibility of confusion between the first interface and the second interface during the switching process is reduced. For example, in the process of returning to and exiting the interface, the interfaces can be returned one by one without returning all interfaces at once, so the stability of the application interface during the switching process can be enhanced.
[0018] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] The drawings herein are incorporated into the specification and constitute a part of the specification, showing embodiments consistent with the present application, and together with the specification, are used to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work. In the drawings:
[0020] Figure 1 A diagram showing an implementation environment of the technical solution according to an embodiment of the present application is shown;
[0021] Figure 2A schematic diagram of an application program interface switching method according to an embodiment of the present application is shown;
[0022] Figure 3 A flowchart of an application program interface switching method according to an embodiment of the present application is shown;
[0023] Figure 4 A method flow chart is shown before displaying the second interface element in the second interface container according to an embodiment of the present application;
[0024] Figure 5 A detailed flow chart of displaying the second interface element in the second interface container according to an embodiment of the present application is shown;
[0025] Figure 6 A method flow chart before removing the second interface container according to an embodiment of the present application is shown;
[0026] Figure 7 A stack structure diagram of application program interface switching according to an embodiment of the present application is shown;
[0027] Figure 8 A method flow chart is shown before displaying the second interface element in the second interface container according to an embodiment of the present application;
[0028] Fig. 9 A detailed flow chart of displaying the second interface element in the second interface container according to an embodiment of the present application is shown;
[0029] Fig.10 A stack structure diagram of application program interface switching according to an embodiment of the present application is shown;
[0030] Fig.11 A method flow chart is shown before displaying the second interface element in the second interface container according to an embodiment of the present application;
[0031] Fig.12 A stack structure diagram of application program interface switching according to an embodiment of the present application is shown;
[0032] Fig.13 A detailed flow chart of displaying the second interface element in the second interface container according to an embodiment of the present application is shown;
[0033] Fig.14 A stack structure diagram of application program interface switching according to an embodiment of the present application is shown;
[0034] Fig.15A block diagram of an application program interface switching device according to an embodiment of the present application is shown;
[0035] Fig.16 A schematic diagram of the structure of a computer system suitable for implementing an electronic device of an embodiment of the present application is shown. DETAILED DESCRIPTION
[0036] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this application will be more comprehensive and complete and fully convey the concept of the example embodiments to those skilled in the art.
[0037] In addition, described feature, structure or characteristic can be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present application. However, those skilled in the art will appreciate that the technical scheme of the present application can be put into practice without one or more of the specific details, or other methods, components, devices, steps, etc. can be adopted. In other cases, known methods, devices, realizations or operations are not shown or described in detail to avoid blurring the various aspects of the application.
[0038] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.
[0039] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.
[0040] Figure 1 The following is a diagram showing an implementation environment of the technical solution according to an embodiment of the present application.
[0041] like Figure 1 As shown, the implementation environment of the technical solution of the embodiment of the present application may include a terminal device. For example, including Figure 1 Any one of the smart phone 101, tablet computer 102, touch display 103 and portable computer 104 shown in the figure may of course be other electronic devices with touch display function, etc.
[0042] In one embodiment of the present application, the user can use a smart phone with a touch display function to implement the technical solution of the embodiment of the present application, for example Figure 1 The smart phone 101 shown in FIG. Specifically, the screen of the smart phone can display an interface, and the interface displayed on the screen can be switched.
[0043] In order to enable those skilled in the art to understand the present application more intuitively, a specific example will be used here to illustrate.
[0044] In a specific implementation of an embodiment, reference may be made to Figure 2 The application shown in the embodiment implements the technical solution of the present application, such as Figure 2 , shows an application schematic diagram of an application interface switching method according to an embodiment of the present application.
[0045] like Figure 2 , showing the switching effect of the interface of the display device under different operation instructions, wherein, in the mobile phone screen in state 201, the application is entered by touching the APP (application) icon in the local interface, and at this time, the first interface shown in state 202 is displayed on the mobile phone screen. Further, after touching the "second interface" button in the first interface, the interface on the mobile phone screen enters the second interface as shown in screen state 203 in the figure, and in further operation, by touching the "return" button in the second interface, the interface on the mobile phone screen returns to the first interface as shown in state 204.
[0046] It should be understood by those skilled in the art that the operation on the screen is not limited to the touch method shown above, and can also be a keyboard input method, a mouse click method, or a voice recognition method based on an artificial intelligence engine (AIE).
[0047] The implementation details of the technical solution of the embodiment of the present application are described in detail below:
[0048] According to a first aspect of the present disclosure, a method for switching an application program interface is provided.
[0049] See also Figure 3 , shows a flow chart of an application interface switching method according to an embodiment of the present application, the application interface switching method can be executed by a device having a computing processing function, such as Figure 1 , or by the smartphone 101 shown in Figure 1 The tablet 102 shown in FIG. Figure 3As shown, the application interface switching method at least includes steps 310 to 370:
[0050] Step 310: display the first interface in the first interface container.
[0051] Step 330: Acquire a second interface element in response to a first operation instruction of the user on the first interface.
[0052] Step 350 : Generate a second interface container, wherein the stack position of the second interface container is above the stack position of the first interface container.
[0053] Step 370: Display the second interface element in the second interface container to switch the first interface to the second interface.
[0054] The following is a detailed description of the above implementation steps:
[0055] In step 310 to step 330, the first interface is displayed in the first interface container; in response to the first operation instruction of the user on the first interface, the second interface element is acquired.
[0056] In the present application, by displaying the first interface in the first interface container, the first interface can be displayed on the display screen.
[0057] It should be noted that, in the present application, the second interface element may specifically include one or more elements such as pictures, texts, symbols, link entrances, and interface components.
[0058] In step 350 to step 370, a second interface container is generated, and the stack position of the second interface container is above the stack position of the first interface container; the second interface element is displayed in the second interface container to switch the first interface to the second interface.
[0059] In the present application, the first interface container may include a first container association engine, wherein the container association engine is mainly used to associate the interface container in the application with the interface container in the local system so that the interface of the application can be normally displayed on the display interface supported by the local system.
[0060] In the present application, the first interface container may further include a first interface element carrier, wherein the interface element carrier is mainly used to carry and manage interface elements.
[0061] In the present application, the steps shown in step 350 to step 370 above can be implemented by the following embodiments:
[0062] Embodiment 1
[0063] In this embodiment, before displaying the second interface element in the second interface container, the following steps may be implemented: Figure 4 Steps shown.
[0064] See also Figure 4 , shows a flow chart of a method before displaying the second interface element in the second interface container according to an embodiment of the present application, which may specifically include steps 361 to 362:
[0065] Step 361: Transfer the first container association engine from the first interface container to the second interface container.
[0066] Step 362: Associating the second interface container with the local interface container based on the first container association engine.
[0067] Further, after associating the second interface container with the local interface container based on the first container association engine, the second interface element may be displayed in the second interface container by: Figure 5 The steps shown are implemented.
[0068] See also Figure 5 , shows a detailed flow chart of displaying the second interface element in the second interface container according to an embodiment of the present application, which may specifically include steps 371 to 372:
[0069] Step 371: Generate a second interface element carrier in the second interface container.
[0070] Step 372: load the second interface element into the second interface element carrier to display the second interface element in the second interface container.
[0071] In this embodiment, by transferring the first container association engine in the first interface container to the generated second interface container, and generating the second interface element carrier in the generated second interface container at the same time, the second interface container can be associated with the local interface container without regenerating and initializing a new container association engine. The advantages are that, on the one hand, it can solve the technical problem of memory occupation caused by too many container association engines, and on the other hand, it can save the time required to regenerate and initialize a new container association engine, thereby improving the interface switching efficiency. On the third hand, it can improve the smoothness of the interface during the switching process, for example, it can prevent the occurrence of a black screen during the interface switching process.
[0072] Continuing to refer to this embodiment, after switching the first interface to the second interface, the second interface can also be switched to the first interface, which can be specifically achieved in the following manner:
[0073] 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 as to switch the second interface to the first interface.
[0074] Specifically, before removing the second interface container, the following steps may be performed: Figure 6 Steps shown.
[0075] See also Figure 6 , shows a flow chart of a method before removing the second interface container according to an embodiment of the present application, which may specifically include steps 381 to 382:
[0076] Step 381: Transfer the first container association engine from the second interface container to the first interface container.
[0077] Step 382: Associating the first interface container with the local interface container based on the first container association engine.
[0078] In order to enable those skilled in the art to more intuitively understand the technical solution of this embodiment, Figure 7 Let's illustrate this with a specific demonstration.
[0079] like Figure 7 , showing a stack structure diagram of application program interface switching according to an embodiment of the present application.
[0080] As can be seen from the figure, the state 1 shown in 701 and 705 is the stack structure state when the first interface is displayed, and the state 2 shown in 703 is the stack structure state when the second interface is displayed. It can be seen from the process 1 shown in 702 that in the process of switching from the first interface to the second interface, a second interface container will be generated on the stack position of the first interface container, and a second interface element carrier will be generated in the second interface container. At the same time, the first container association engine in the first interface container is transferred to the second interface container. It can be seen from the process 2 shown in 704 that in the process of switching from the second interface to the first interface, the first container association engine in the second interface container will be transferred to the first interface container, and then the second interface container will be removed.
[0081] Embodiment 2
[0082] In this embodiment, before displaying the second interface element in the second interface container, the following steps may be implemented: Figure 8 Steps shown.
[0083] See also Figure 8 , shows a flow chart of a method before displaying the second interface element in the second interface container according to an embodiment of the present application, which may specifically include steps 363 to 364:
[0084] Step 363: Transfer the first interface element carrier from the first interface container to the second interface container.
[0085] Step 364: load the second interface element into the first interface element carrier to display the second interface element in the second interface container.
[0086] Furthermore, after the second interface element is loaded into the first interface element carrier, the second interface element may be displayed in the second interface container by: Fig. 9 The steps shown are implemented.
[0087] See also Fig. 9 , shows a detailed flow chart of displaying the second interface element in the second interface container according to an embodiment of the present application, which may specifically include steps 373 to 374:
[0088] Step 373: Generate a second container association engine in the second interface container.
[0089] Step 374: Associating the second interface container with the local interface container based on the second container association engine.
[0090] Continuing to refer to this embodiment, after switching the first interface to the second interface, the second interface can also be switched to the first interface, which can be specifically achieved in the following manner:
[0091] 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 as to switch the second interface to the first interface.
[0092] Specifically, before removing the second interface container, 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.
[0093] In order to enable those skilled in the art to more intuitively understand the technical solution of this embodiment, Fig.10 Let's illustrate this with a specific demonstration.
[0094] like Fig.10 , showing a stack structure diagram of application program interface switching according to an embodiment of the present application.
[0095] As can be seen from the figure, the state 1 shown in 1001 and 1005 is the stack structure state when the first interface is displayed, and the state 2 shown in 1003 is the stack structure state when the second interface is displayed. It can be seen from the process 1 shown in 1002 that in the process of switching from the first interface to the second interface, a second interface container will be generated on the stack position of the first interface container, and a second container association engine will be generated in the second interface container. At the same time, the first interface element carrier in the first interface container is transferred to the second interface container. It can be seen from the process 2 shown in 1004 that in the process of switching from the second interface to the first interface, the first interface element carrier in the second interface container will be transferred to the first interface container, and then the second interface container will be removed.
[0096] Embodiment 3
[0097] In this embodiment, before displaying the second interface element in the second interface container, the following steps may be implemented: Fig.11 Steps shown.
[0098] See also Fig.11 , shows a method flow chart before displaying the second interface element in the second interface container according to an embodiment of the present application, which may specifically include steps 365 to 366:
[0099] Step 365: 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.
[0100] Step 366: Transfer 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 to display the second interface element in the second interface container.
[0101] Continuing to refer to this embodiment, after the second interface element is displayed in the second interface container, the second interface can also be switched to the first interface, which can be specifically achieved in the following manner:
[0102] 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 as to switch the second interface to the first interface.
[0103] Specifically, before removing the second interface container, the first interface element carrier and the first container association engine may be transferred from the second interface container to the first interface container respectively.
[0104] In order to enable those skilled in the art to more intuitively understand the technical solution of this embodiment, Fig.12 Let's illustrate this with a specific demonstration.
[0105] like Fig.12 , showing a stack structure diagram of application program interface switching according to an embodiment of the present application.
[0106] As can be seen from the figure, state 1 shown in 1201 and 1205 is the stack structure state when the first interface is displayed, and state 2 shown in 1203 is the stack structure state when the second interface is displayed. It can be seen from process 1 shown in 1202 that in the process of switching from the first interface to the second interface, a second interface container will be generated on the stack position of the first interface container, and at the same time, the first interface element carrier and the first container association engine in the first interface container will be transferred to the second interface container. It can be seen from process 2 shown in 1204 that in the process of switching from the second interface to the first interface, the first interface element carrier and the first container association engine in the second interface container will be transferred to the first interface container, and then the second interface container will be removed.
[0107] Embodiment 4:
[0108] In this embodiment, the second interface element is displayed in the second interface container by: Fig.13 The steps shown are implemented.
[0109] See also Fig.13 , shows a detailed flow chart of displaying the second interface element in the second interface container according to an embodiment of the present application, which may specifically include steps 375 to 376:
[0110] Step 375: Generate a second container association engine in the second interface container to associate the second interface container with the local interface container.
[0111] Step 376: Generate 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.
[0112] Continuing to refer to this embodiment, after the second interface element is displayed in the second interface container, the second interface can also be switched to the first interface, which can be specifically achieved in the following manner:
[0113] 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 as to switch the second interface to the first interface.
[0114] In order to enable those skilled in the art to more intuitively understand the technical solution of this embodiment, Fig.14 Let's illustrate this with a specific demonstration.
[0115] like Fig.14 , showing a stack structure diagram of application program interface switching according to an embodiment of the present application.
[0116] 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. In the process of switching from the first interface to the second interface, a second interface container will be generated above the stack position of the first interface container, and a second container association engine and a second interface element carrier will be generated in the second interface container. In the process of switching from the second interface to the first interface, the generated second interface container will be removed.
[0117] In order to make those skilled in the art better understand the present application, the present application will be described below with reference to Example 1 using a specific application scenario:
[0118] This application can be applied to both Android APP and iOS APP, involving a hybrid development mode of Flutter and Native. Flutter is Google's mobile UI framework that can quickly build high-quality native user interfaces on iOS and Android.
[0119] In the application, the Flutter interface stack can be hosted to the Native interface stack for management, for example, hosted to the Android Native interface stack for management. Specifically, the Flutter interface stack is built on the Native interface stack, wherein the Flutter interface elements are loaded in the Flutter interface container through the Flutter View to display the Flutter interface. In addition, the Flutter interface is associated with the Native interface through the Flutter engine.
[0120] During the interface switching process, for example, when entering a new Flutter interface, a Flutter View can be generated in the new Flutter interface container to load the interface elements of the new Flutter interface, and the Flutter engine in the previous Flutter interface is transferred to the new Flutter interface. That is, this application scenario only reuses the Flutter engine but not the Flutter View, so that the Flutter interface can be switched.
[0121] In this application scenario, since it takes a long time to generate a new Flutter engine and the Flutter engine occupies a large amount of memory while the Flutter View occupies a small amount of memory, the advantage of reusing only the Flutter engine instead of reusing the Flutter View is that it can speed up the interface switching and enhance the smoothness of the interface switching without causing the problem of excessive memory usage.
[0122] In the technical solutions provided by some embodiments of the present application, the second interface element is obtained through the first operation instruction on the first interface, and the second interface container is generated on the 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 to switch the first interface to the second interface. In this solution, since the first interface is managed by the first interface container and the second interface is managed by the generated second interface container, the possibility of confusion between the first interface and the second interface during the switching process is reduced. For example, in the process of returning to and exiting the interface, the interfaces can be returned one by one without returning all interfaces at once, so the stability of the application interface during the switching process can be enhanced.
[0123] The following describes an apparatus embodiment of the present application, which can be used to execute the application interface switching method in the above-mentioned embodiment of the present application. For details not disclosed in the apparatus embodiment of the present application, please refer to the above-mentioned embodiment of the application interface switching method of the present application.
[0124] Fig.15 A block diagram of an application program interface switching device according to an embodiment of the present application is shown.
[0125] Reference Fig.15 As shown, according to an embodiment of the present application, an application program interface switching device 1500 includes: a first display unit 1501 , an acquisition unit 1502 , a generation unit 1503 and a second display unit 1504 .
[0126] Among them, the first display unit 1501 is used to display the first interface in the first interface container; the acquisition unit 1502 is used to acquire the second interface element in response to the first operation instruction of the user on the first interface; the generation unit 1503 is used to generate a second interface container, and the stack position of the second interface container is above the stack position of the first interface container; the second display unit 1504 is used to display the second interface element in the second interface container to switch the first interface to the second interface.
[0127] In some embodiments of the present application, based on the aforementioned scheme, the first interface container includes a first container association engine, and the application interface switching device also includes a first transfer unit, which is used to transfer the first container association engine from the first interface container to the second interface container before displaying the second interface element in the second interface container; an association unit, which is used to associate the second interface container and the local interface container based on the first container association engine.
[0128] In some embodiments of the present application, based on the aforementioned scheme, the second display unit 1504 is configured to: generate a second interface element carrier in the second interface container; load the second interface element into the second interface element carrier to display the second interface element in the second interface container.
[0129] In some embodiments of the present application, based on the aforementioned scheme, the first display unit 1501 is configured as: after switching the first interface to the second interface, 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 to switch the second interface to the first interface.
[0130] In some embodiments of the present application, based on the aforementioned scheme, the first transfer unit is configured to: transfer the first container association engine from the second interface container to the first interface container before removing the second interface container; the association unit is configured to: associate the first interface container and the local interface container based on the first container association engine.
[0131] In some embodiments of the present application, based on the aforementioned scheme, the first interface container includes a first interface element carrier, and the application interface switching device also includes a second transfer unit, which is used to transfer the first interface element carrier from the first interface container to the second interface container before displaying the second interface element in the second interface container; a loading unit, which is used to load the second interface element into the first interface element carrier to display the second interface element in the second interface container.
[0132] In some embodiments of the present application, based on the aforementioned solution, the second display unit 1504 is configured to: generate a second container association engine in the second interface container; and associate the second interface container with a local interface container based on the second container association engine.
[0133] In some embodiments of the present application, based on the aforementioned scheme, the first interface container includes a first container association engine and a first interface element carrier, and the application interface switching device also includes a third transfer unit, which is used to transfer the first container association engine from the first interface container to the second interface container before displaying the second interface element in the second interface container to associate the second interface container with the local interface container; transfer 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 to display the second interface element in the second interface container.
[0134] In some embodiments of the present application, based on the above solution, the second display unit 1504 is configured to: generate a second container association engine in the second interface container to associate the second interface container with the local interface container. Generate 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.
[0135] Fig.16 A schematic diagram of the structure of a computer system suitable for implementing an electronic device of an embodiment of the present application is shown.
[0136] It should be noted that Fig.16 The computer system 1600 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.
[0137] like Fig.16 As shown, the computer system 1600 includes a central processing unit (CPU) 1601, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 1602 or the program loaded from the storage part 1608 to the random access memory (RAM) 1603, such as executing the method described in the above embodiment. In RAM 1603, various programs and data required for system operation are also stored. CPU 1601, ROM 1602 and RAM 1603 are connected to each other through bus 1604. Input / output (I / O) interface 1605 is also connected to bus 1604.
[0138] The following components are connected to the I / O interface 1605: an input section 1606 including a keyboard, a mouse, etc.; an output section 1607 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1608 including a hard disk, etc.; and a communication section 1609 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 1609 performs communication processing via a network such as the Internet. A drive 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, etc., is installed on the drive 1610 as needed so that a computer program read therefrom is installed into the storage section 1608 as needed.
[0139] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication section 1609, and / or installed from a removable medium 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.
[0140] It should be noted that the computer-readable medium shown in the embodiment of the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, - but not limited to - an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by an instruction execution system, device or device or used in combination with it. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, wherein a computer-readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.
[0141] The flowchart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present application. Wherein, each box in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0142] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. The names of these units do not, in some cases, constitute limitations on the units themselves.
[0143] As another aspect, the present application also provides a computer-readable medium, which may be included in the electronic device described in the above embodiment; or may exist independently without being assembled into the electronic device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by an electronic device, the electronic device implements the method described in the above embodiment.
[0144] It should be noted that, although several modules or units of the equipment for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present application, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into being embodied by multiple modules or units.
[0145] Through the description of the above implementation methods, it is easy for those skilled in the art to understand that the example implementation methods described here can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the implementation methods 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 flash drive, a mobile 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 implementation methods of the present application.
[0146] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the embodiments disclosed herein. The present application is intended to cover any variations, uses or adaptations of the present application, which follow the general principles of the present application and include common knowledge or customary technical means in the art that are not disclosed in the present application.
[0147] It should be understood that the present application is not limited to the precise structures that have been 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 present application is limited only by the appended claims.
Claims
1. A method for switching an application program interface, It is characterized in that The method comprises: The first interface is displayed in a first interface container, wherein the stack position of the first interface container is established on the stack position of the local interface container, and the first interface and the display interface supported by the local system belong to interfaces of a cross-platform development mode; the first interface container includes a first container association engine, and the container association engine is used to associate the interface container in the application with the interface container in the local system, so that the interface in the application is displayed on the display interface supported by the local system; In response to a first operation instruction of a user on a first interface, acquiring a second interface element; generating a second interface container, wherein the stack position of the second interface container is above the stack position of the first interface container; Transferring the first container association engine from the first interface container to the second interface container; associating the second interface container with the local interface container based on the first container association engine, wherein the first interface and the second interface are interfaces of the same platform development mode; The second interface element is displayed in the second interface container to switch the first interface to the second interface.
2. The method according to claim 1, It is characterized in that The step of displaying the second interface element in the second interface container includes: generating a second interface element carrier in the second interface container; The second interface element is loaded into the second interface element carrier to display the second interface element in the second interface container.
3. The method according to claim 1, It is characterized in that After switching the first interface to the second interface, the method further includes: 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 as to switch the second interface to the first interface.
4. The method according to claim 3, It is characterized in that Before removing the second interface container, the method further includes: Transferring the first container association engine from the second interface container to the first interface container; Based on the first container association engine, the first interface container and the local interface container are associated.
5. The method according to claim 1, It is characterized in that The first interface container includes a first interface element carrier. Before displaying the second interface element in the second interface container, the method further includes: Transferring the first interface element carrier from the first interface container to the second interface container; The second interface element is loaded into the first interface element carrier to display the second interface element in the second interface container.
6. The method according to claim 1, It is characterized in that The first interface container includes a first interface element carrier, Before displaying the second interface element in the second interface container, the method further includes: Transferring 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; The first interface element carrier is transferred from the first interface container to the second interface container, so as 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.
7. An application program interface switching device, It is characterized in that include: The first display unit is used to display the first interface in a first interface container, the stack position of the first interface container is established on the stack position of the local interface container, and the first interface and the display interface supported by the local system belong to the interface of the cross-platform development mode; the first interface container includes a first container association engine, and the container association engine is used to associate the interface container in the application with the interface container in the local system, so that the interface in the application is displayed on the display interface supported by the local system; An acquisition unit, used to acquire a second interface element in response to a first operation instruction of a user on the first interface; A generating unit, used to generate a second interface container, wherein the stack position of the second interface container is above the stack position of the first interface container; A first transfer unit, used to transfer the first container association engine from the first interface container to the second interface container; an associating unit, used to associate the second interface container with a local interface container based on the first container associating engine, wherein the first interface and the second interface are interfaces of the same platform development mode; The second display unit is used to display the second interface element in the second interface container to switch the first interface to the second interface.
8. A computer readable medium, It is characterized in that A computer program is stored thereon, and when the computer program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.
9. An electronic device, It is characterized in that include: one or more processors; A storage device, used to store one or more programs, when the one or more programs are executed by the one or more processors, enables the one or more processors to implement the method according to any one of claims 1 to 6.
10. A computer program product, It is characterized in that The method comprises a computer program carried on a computer-readable medium, wherein the computer program comprises a program code for executing the method according to any one of claims 1 to 6.
