A window display method and apparatus

Abstract

The application discloses a window display method and device, and relates to the field of electronic devices. A terminal displays an application window of a first application on a display screen of the terminal, and the application window comprises multiple elements. After receiving a first operation, the terminal displays an animation of the movement of the application window. When it is determined that the application window moves to a specified area of the display screen of the terminal, a dynamic small window is displayed on the display screen of the terminal, and the dynamic small window comprises part of the elements in the application window. The dynamic small window supports the presentation of a page level, an application level and a system level. The content presented in the dynamic small window is a key element in the display interface. Not only can the dynamic small window not display too much content to affect the user experience, but also can meet the processing requirements of the user.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of electronic devices, and in particular to a window display method and device. BACKGROUND

[0002] At present, terminals such as mobile phones have become electronic devices with high frequency of use in daily life and work. For example, users can use mobile phones to browse news information, watch videos, and make online purchases. If key information such as videos and navigation information in the current interface is moved out of the mobile phone screen during use of the mobile phone, the user cannot continue to view the information. SUMMARY

[0003] Embodiments of the present application provide a window display method and device, which can be referred to as a dynamic small window. After a triggering condition of the dynamic small window is met, the terminal can extract key elements in the display interface of the terminal and display them in the form of a dynamic small window on the terminal screen. The dynamic small window supports presentation at the page level, application level, and system level. In addition, the content presented in the dynamic small window is key elements recommended by the system or customized by a third-party application. Not only will it not display too much content to affect the user experience, but it can also meet the user's processing needs.

[0004] To achieve the above-mentioned purpose, the present application adopts the following technical solutions:

[0005] In a first aspect of the present application, a window display method is provided, which can be applied to a terminal. The method can include: displaying, by the terminal, an application window of a first application on a display screen of the terminal, the application window of the first application including a plurality of elements; and displaying, by the terminal, a first window on the display screen of the terminal after receiving a first operation, the first window including part of the elements in the application window of the first application. The first window can be referred to as a dynamic small window, which can be displayed floating on the terminal screen.

[0006] With the above technical solutions, the terminal can extract key elements in the display interface of the terminal and display them in the form of a window, such as a dynamic small window, on the terminal screen. With limited small window display resources, the display of key content in the application window is achieved, and not only will it not display too much content to affect the user experience, but it can also meet the user's processing needs, such as using the window to help the user to obtain and quickly process multiple tasks.

[0007] In a possible implementation, the first operation can include a drag operation on the application window of the first application in the multitasking interface; and the displaying of the application window of the first application on the display screen of the terminal can include: after receiving the second operation, the terminal displays the multitasking interface, and the multitasking interface includes the application window of the first application; and the displaying of the first window on the display screen of the terminal can include: the terminal displays an animation of the movement of the application window of the first application, and when it is determined that the application window of the first application moves to the specified area of the display screen of the terminal, the terminal displays the first window on the display screen of the terminal. The system-level interaction gesture of sliding the application window upwards in the multitasking interface is used to trigger the display of the window, so that the display of the window is more flexible and the operation is simpler.

[0008] In another possible implementation, the application window of the first application can be a free window; the first operation can be a drag operation on the application window of the first application, i.e., the free window of the first application; and the displaying of the first window on the display screen of the terminal can include: the terminal displays an animation of the movement of the application window of the first application, i.e., the free window; and when it is determined that the application window of the first application, i.e., the free window, moves to the specified area of the display screen of the terminal, the terminal displays the first window on the display screen of the terminal.

[0009] In another possible implementation, the first operation can be an operation of triggering the first application to switch to the background.

[0010] In another possible implementation, after the terminal displays the application window of the first application on the display screen, the method can further include: the terminal displays a notification message on the display screen of the terminal; and the first operation is a selection operation on the notification message.

[0011] According to the above implementation, it can be understood that in the embodiment, the first window (or referred to as a dynamic window) can be triggered to be displayed in various manners, so that the user can call up the first window in any interface, and the processing requirement of the window in multitasking processing is met.

[0012] In another possible implementation, before the displaying of the first window on the display screen of the terminal, the method can further include: the terminal extracts part of elements from the application window of the first application. After the dynamic window is triggered to be displayed, the terminal can extract key elements in the currently displayed application window, and present the key elements to the user in the form of the dynamic window.

[0013] In another possible implementation, the part of elements can be predetermined. For example, the part of elements can be video elements.

[0014] In another possible implementation, the terminal extracting the partial elements from the plurality of elements of the application window of the first application can include: the terminal obtaining the first identifier, obtaining the configuration file corresponding to the first identifier from the stored configuration files corresponding to different identifiers, the configuration file corresponding to the first identifier including the identifier of the partial elements; and the terminal extracting the partial elements from the plurality of elements of the application window of the first application according to the configuration file corresponding to the first identifier. The application developer can define which elements in the corresponding application or interface of the application are key elements to be displayed in the dynamic window.

[0015] In another possible implementation, the terminal extracting the partial elements from the plurality of elements of the application window of the first application can include: the terminal obtaining the type of the first application, obtaining the recommendation model corresponding to the type of the first application from the stored recommendation models corresponding to different types of applications, the recommendation model having the function of extracting the elements to be displayed in the first window according to the type of the application; and the terminal extracting the partial elements from the plurality of elements of the application window of the first application according to the recommendation model corresponding to the type of the first application. The key elements displayed in the dynamic window can be recommended by the system.

[0016] In another possible implementation, the layout of the partial elements in the first window is different from the layout of the elements corresponding to the partial elements in the application window. This embodiment also supports the relayout of the elements in the dynamic window.

[0017] It can be obtained that the content and layout effect presented in the first window, i.e., the dynamic window, support automatic recommendation by the system according to different application types or customization by the third-party application developer, so that the user can more flexibly complete multitasking, and the flexible display and layout requirements of the dynamic window can also be met.

[0018] In another possible implementation, the layout of the partial elements in the first window is predetermined.

[0019] In another possible implementation, before the first window is displayed on the display screen of the terminal, the method can further include: the terminal obtaining the layout file corresponding to the first identifier from the stored layout files according to the first identifier, and the terminal performing layout on the extracted partial elements according to the obtained layout file. The first identifier can include the identifier of the first application, or the first identifier can include the identifier of the first application and the identifier of the interface in the application window.

[0020] In another possible implementation, before displaying the first window on the display screen of the terminal, the method can further include: the terminal obtaining, according to the type of the first application, a layout file corresponding to the type of the first application from the stored layout files, and the terminal performing layout on the extracted partial elements according to the obtained layout file.

[0021] In another possible implementation, after displaying the first window on the display screen of the terminal, the method can further include: the terminal changing the first window to a second window and displaying the second window on the display screen of the terminal after receiving a third operation on the first window; wherein the second window includes partial elements in the application window of the first application, and the second window includes more elements than the first window. The window can be changed from a small window form to a medium window form. The medium window form includes more elements than the first window. For example, the first window includes only partial display class elements in the application window of the first application, and the second window can include the display class elements and partial control class elements in the application window of the first application.

[0022] In another possible implementation, the second window includes a video element, after the terminal displays the second window, the terminal lowers the volume of the terminal after receiving a first sliding operation (such as a sliding operation from top to bottom) on the second window, and the terminal raises the volume of the terminal after receiving a second sliding operation (such as a sliding operation from bottom to top) on the second window. The terminal performs a fast-rewinding operation on the video in the video element after receiving a third sliding operation (such as a sliding operation from right to left) on the second window, and the terminal performs a fast-forward operation on the video in the video element after receiving a fourth sliding operation (such as a sliding operation from left to right) on the second window.

[0023] The elements in the second window, i.e., the medium window form, can be extracted from the plurality of elements in the application window of the first application.

[0024] For example, the elements to be displayed in the medium window form can be predetermined.

[0025] For another example, the terminal can obtain, according to the first identifier, a configuration file corresponding to the first identifier from the stored configuration files corresponding to different identifiers (the configuration file is a configuration file for the medium window form), and then extract the elements to be displayed in the medium window form from the plurality of elements in the application window of the first application according to the obtained configuration file.

[0026] For example, the terminal can acquire, according to the type of the first application, a recommended model corresponding to the type of the first application from the recommended models corresponding to different types of applications stored in the terminal (the recommended model is a recommended model for a window in a medium window form), and then extract, according to the acquired recommended model, the element to be displayed in the window in the medium window form from the plurality of elements of the application window of the first application.

[0027] The layout of the extracted element to be displayed in the window in the medium window form in the window in the medium window form can be different from the layout of the corresponding element in the application window of the first application. For example, the terminal can re-layout the extracted element to be displayed in the window in the medium window form according to the corresponding layout file.

[0028] In another possible implementation, the second window further includes a close button and a zoom-in button; and the method can further include: displaying, by the terminal, the application window of the first application and not displaying the second window after receiving the operation on the zoom-in button.

[0029] In another possible implementation, after the terminal changes the first window to the second window and displays the second window on the display screen of the terminal, the method can further include: changing, by the terminal, the second window to the first window and displaying the first window on the display screen of the terminal after determining that no user operation is received within a preset time or after receiving a fourth operation on the second window. The dynamic small window can also support changing from the medium window form to the small window form, thereby meeting various processing requirements of the user and improving the use experience of the user.

[0030] In another possible implementation, displaying the first window on the display screen of the terminal can include: displaying, by the terminal, a desktop on the display screen of the terminal, and displaying the first window on the desktop, the desktop can include an icon of the second application; and the method can further include: displaying, by the terminal, an animation of moving the first window after receiving the operation of dragging the first window; and displaying, by the terminal, the application window of the second application on the display screen of the terminal when the first window is dragged to the position of the icon of the second application. When the user drags the first window to hover over the icon of the application, the terminal can display the application window of the application.

[0031] In another possible implementation, after the terminal displays the first window, the method can further include: displaying, by the terminal, a multitasking interface including the application window of the second application after receiving a second operation; displaying, by the terminal, an animation of moving the first window after receiving the operation of dragging the first window; and displaying, by the terminal, the application window of the second application on the display screen of the terminal when the first window is dragged to the position of the application window of the second application.

[0032] In another possible implementation, after receiving the drag release operation, the terminal converts the first window into a resource file and inserts the application window of the second application. In addition, after the user stops dragging the window, the window can be converted into a resource file and inserted into the application window. For example, the content of the first window is converted into a resource file and stored locally or sent to another device, and the insertion result is displayed in the application window of the second application.

[0033] In another possible implementation, the terminal is connected with a second terminal; after displaying the first window on the display screen of the terminal, the method can further include: after receiving an operation of dragging the first window, the terminal displays an animation of the movement of the first window; after determining that the user's drag intention is cross-device dragging, the terminal sends data of the first window to the second terminal, the data of the first window being used by the second terminal to display the first window on the display screen of the second terminal. The dynamic small window supports cross-device dragging, and improves the use efficiency of multi-terminal collaborative use.

[0034] The above is an example of a window in the form of a small window, i.e., the first window. A window in the form of a medium window, i.e., the second window, also supports dragging.

[0035] In a second aspect, the present application provides a display device, which can be applied to a terminal. The device can include: a display unit configured to display an application window of a first application on a display screen of the terminal, the application window of the first application including a plurality of elements; and an input unit configured to receive a first operation. The display unit is further configured to display a first window on the display screen of the terminal after receiving the first operation, the first window including part of the elements in the application window of the first application.

[0036] In a possible implementation, the first operation can include a drag operation on the application window of the first application in a multi-task interface. The display unit is specifically configured to display the multi-task interface including the application window of the first application after receiving a second operation. The display unit is specifically configured to display an animation of the movement of the application window of the first application. When it is determined that the application window of the first application moves to a specified area of the display screen of the terminal, the display unit displays the first window on the display screen of the terminal.

[0037] In another possible implementation, the application window of the first application can be a free small window. The first operation can be a drag operation on the application window of the first application, i.e., the free small window of the first application. The display unit is specifically configured to display an animation of the movement of the application window of the first application, i.e., the free small window. When it is determined that the application window of the first application, i.e., the free small window, moves to a specified area of the display screen of the terminal, the display unit displays the first window on the display screen of the terminal.

[0038] In a possible implementation, the first operation can be an operation of triggering the first application to switch to the background.

[0039] In a possible implementation, the display unit is further configured to display a notification message on a display screen of the terminal, and the first operation is a selection operation on the notification message.

[0040] In a possible implementation, the apparatus can further include an obtaining unit configured to extract the partial elements from the plurality of elements of the application window of the first application.

[0041] In a possible implementation, the partial elements can be predetermined. For example, the partial elements can be video elements.

[0042] In a possible implementation, the obtaining unit is specifically configured to: obtain the first identifier, obtain a configuration file corresponding to the first identifier from the stored configuration files corresponding to different identifiers, the configuration file corresponding to the first identifier including identifiers of the partial elements; extract the partial elements from the plurality of elements of the application window of the first application according to the configuration file corresponding to the first identifier; and wherein the first identifier can include an identifier of the first application, or the first identifier can include an identifier of the first application and an identifier of an interface in the application window.

[0043] In a possible implementation, the obtaining unit is specifically configured to: obtain a type of the first application, obtain a recommendation model corresponding to the type of the first application from the stored recommendation models corresponding to different types of applications, the recommendation model having a function of extracting elements to be displayed in the first window according to a type of an application; and extract the partial elements from the plurality of elements of the application window of the first application according to the recommendation model corresponding to the type of the first application.

[0044] In a possible implementation, a layout of the partial elements in the first window is different from a layout of elements corresponding to the partial elements in the application window.

[0045] In a possible implementation, the layout of the partial elements in the first window is predetermined.

[0046] In a possible implementation, the obtaining unit is further configured to obtain a layout file corresponding to the first identifier from the stored layout files according to the first identifier, and to arrange the extracted partial elements according to the obtained layout file. Wherein the first identifier can include an identifier of the first application, or the first identifier can include an identifier of the first application and an identifier of an interface in the application window.

[0047] In another possible implementation, the obtaining unit is further configured to obtain, according to the type of the first application, a layout file corresponding to the type of the first application from the stored layout files, and to perform layout on the extracted partial elements according to the obtained layout file.

[0048] In another possible implementation, the input unit is further configured to receive a third operation on the first window, and the display unit is further configured to change the first window to the second window and display the second window on the display screen of the terminal after receiving the third operation on the first window, wherein the second window includes partial elements in the application window of the first application, and the second window includes more elements than the first window.

[0049] The elements in the second window, i.e., the window in the form of the middle window, can be extracted from the plurality of elements in the application window of the first application by the terminal. That is, the obtaining unit is further configured to extract the elements to be displayed in the second window from the plurality of elements in the application window of the first application.

[0050] For example, the elements to be displayed in the second window can be predetermined.

[0051] For another example, the obtaining unit is specifically configured to obtain, according to the first identifier, a configuration file corresponding to the first identifier from the stored configuration files corresponding to different identifiers (the configuration file is a configuration file for the second window), and then extract the elements to be displayed in the second window from the plurality of elements in the application window of the first application according to the obtained configuration file.

[0052] For another example, the obtaining unit is specifically configured to obtain, according to the type of the first application, a recommendation model corresponding to the type of the first application from the stored recommendation models corresponding to different types of applications (the recommendation model is a recommendation model for the second window), and then extract the elements to be displayed in the second window from the plurality of elements in the application window of the first application according to the obtained recommendation model.

[0053] The layout of the extracted elements to be displayed in the window in the form of the middle window in the window in the form of the middle window can be different from the layout of the corresponding elements in the application window of the first application.

[0054] In another possible implementation, the second window further includes a close button and an enlarge button, the input unit is further configured to receive an operation on the close button, and the display unit is further configured to not display the second window after receiving the operation on the close button, the input unit is further configured to receive an operation on the enlarge button, and the display unit is further configured to display the application window of the first application and not display the second window after receiving the operation on the enlarge button.

[0055] In a possible implementation, the display unit is further configured to, after determining that the user operation is not received within the preset time, or after receiving the fourth operation on the second window, change the second window to the first window and display the first window on the display screen of the terminal.

[0056] In a possible implementation, the display unit displays the first window, which can include displaying a desktop on the display screen of the terminal, displaying the first window on the desktop, and the desktop can include an icon of the second application; the input unit is further configured to receive an operation of dragging the first window; the display unit is further configured to, after receiving the operation of dragging the first window, display an animation of movement of the first window; and when the first window is dragged to a position of the icon of the second application, display an application window of the second application on the display screen of the terminal.

[0057] In a possible implementation, the display unit is further configured to, after receiving the second operation, display a multitasking interface, and the multitasking interface includes the application window of the second application; the display unit is further configured to, after receiving the operation of dragging the first window, display an animation of movement of the first window; and when the first window is dragged to a position of the application window of the second application, display the application window of the second application on the display screen of the terminal.

[0058] In a possible implementation, the input unit is further configured to receive a drag-release operation; and the apparatus can further include a storage unit configured to, after receiving the drag-release operation, store the first window as a resource file; or the apparatus further includes a sending unit configured to, after receiving the drag-release operation, send the first window as a resource file to another device through the second application.

[0059] In a possible implementation, the terminal is connected with a second terminal; the input unit is further configured to receive the operation of dragging the first window; and the display unit is further configured to, after receiving the operation of dragging the first window, display an animation of movement of the first window; and the apparatus can further include a sending unit configured to, after determining that the user's dragging intention is cross-device dragging, send data of the first window to the second terminal, and the data of the first window is used by the second terminal to display the first window on a display screen of the second terminal.

[0060] In a third aspect, a display apparatus is provided, which can include a processor, a memory for storing processor-executable instructions, and wherein the processor is configured to execute the instructions to cause the display apparatus to implement the method according to the first aspect or any one of the possible implementation manners of the first aspect.

[0061] In a fourth aspect, a computer-readable storage medium is provided, which stores computer program instructions, and the computer program instructions, when executed by an electronic device, cause the electronic device to implement the method according to the first aspect or any one of the possible implementation manners of the first aspect.

[0062] In a fifth aspect, the present application provides an electronic device (e.g., the terminal described above), comprising a display screen, one or more processors and a memory; the display screen, the processor and the memory are coupled; the memory is configured to store computer program codes, the computer program codes comprising computer instructions, when the computer instructions are executed by the electronic device, causing the electronic device to perform the method according to the first aspect or any possible implementation of the first aspect.

[0063] In a sixth aspect, the present application provides a computer program product, comprising computer readable codes or a non-volatile computer readable storage medium carrying the computer readable codes, when the computer readable codes are run in an electronic device (e.g., the terminal described above), a processor in the electronic device performs the method according to the first aspect or any possible implementation of the first aspect.

[0064] It can be understood that the display device according to the second aspect and any possible implementation of the second aspect, the display device according to the third aspect, the computer readable storage medium according to the fourth aspect, the electronic device according to the fifth aspect, and the computer program product according to the sixth aspect can achieve the beneficial effects as described in the first aspect and any possible implementation of the first aspect, which will not be described here. BRIEF DESCRIPTION OF DRAWINGS

[0065] FIG. 1 A schematic diagram of a display interface in a related technology provided by an embodiment of the present application;

[0066] FIG. 2 Another schematic diagram of a display interface in a related technology provided by an embodiment of the present application;

[0067] FIG. 3 Still another schematic diagram of a display interface in a related technology provided by an embodiment of the present application;

[0068] FIG. 4 Still another schematic diagram of a display interface in a related technology provided by an embodiment of the present application;

[0069] FIG. 5 A structural schematic diagram of a mobile phone provided by an embodiment of the present application;

[0070] FIG. 6 A component schematic diagram of a software architecture of a terminal provided by an embodiment of the present application;

[0071] FIG. 7 A flow schematic diagram of a window display method provided by an embodiment of the present application;

[0072] FIG. 8AA schematic diagram of a display coordinate system provided for an embodiment of the present application;

[0073] FIG. 8B Another schematic diagram of a display coordinate system provided for an embodiment of the present application;

[0074] FIG. 9 A schematic diagram of a display interface provided for an embodiment of the present application;

[0075] FIG. 10A Another schematic diagram of a display interface provided for an embodiment of the present application;

[0076] FIG. 10B Still another schematic diagram of a display interface provided for an embodiment of the present application;

[0077] FIG. 11 Still another schematic diagram of a display interface provided for an embodiment of the present application;

[0078] FIG. 12 Still another schematic diagram of a display interface provided for an embodiment of the present application;

[0079] FIG. 13 A schematic diagram of a dynamic small window provided for an embodiment of the present application;

[0080] FIG. 14 A display schematic diagram of a dynamic small window provided for an embodiment of the present application;

[0081] FIG. 15 Another display schematic diagram of a dynamic small window provided for an embodiment of the present application;

[0082] FIG. 16 Still another display schematic diagram of a dynamic small window provided for an embodiment of the present application;

[0083] FIG. 17 Still another display schematic diagram of a dynamic small window provided for an embodiment of the present application;

[0084] FIG. 18 A flow schematic diagram of another window display method provided for an embodiment of the present application;

[0085] FIG. 19 Still another schematic diagram of a display interface provided for an embodiment of the present application;

[0086] FIG. 20A Still another schematic diagram of a display interface provided for an embodiment of the present application;

[0087] FIG. 20B Still another schematic diagram of a display interface provided for an embodiment of the present application;

[0088] FIG. 21AA schematic diagram illustrating yet another display interface provided in an embodiment of this application;

[0089] FIG. 21B A schematic diagram illustrating yet another display interface provided in an embodiment of this application;

[0090] FIG. 22 A schematic diagram illustrating yet another display interface provided in an embodiment of this application;

[0091] FIG. 23 A schematic diagram of another dynamic small window provided in an embodiment of this application;

[0092] FIG. 24A A schematic diagram of yet another dynamic small window provided in an embodiment of this application;

[0093] FIG. 24B A schematic diagram illustrating yet another display interface provided in an embodiment of this application;

[0094] FIG. 24C A schematic diagram illustrating yet another display interface provided in an embodiment of this application;

[0095] FIG. 25 A schematic diagram illustrating yet another display interface provided in an embodiment of this application;

[0096] FIG. 26 A schematic diagram illustrating yet another display interface provided in an embodiment of this application;

[0097] FIG. 27 A schematic diagram illustrating yet another display interface provided in an embodiment of this application;

[0098] FIG. 28 A schematic diagram illustrating yet another display interface provided in an embodiment of this application;

[0099] FIG. 29 This is a schematic diagram illustrating the composition of a display device provided in an embodiment of this application;

[0100] FIG. 30 This is a schematic diagram of the composition of a chip system provided in an embodiment of this application. Detailed Implementation

[0101] Currently, users can use their mobile phones to browse news, watch videos, and shop online. However, if key information on the current screen is moved off-screen while using the phone, the user will be unable to continue viewing it.

[0102] For example, combining FIG. 1 Users browse using mobile phones today or Information found on WeChat official accounts. For example, such as... FIG. 1As shown in (a), the user is currently browsing interface 101, which includes a video element 102. After the user opens interface 101 or clicks the play button on the video element 102, the phone can start playing the corresponding video. Once the video element 102 is removed from the phone screen, viewing can no longer continue. For example, FIG. 1 As shown in (a), the user performs an upward swipe on the phone screen. FIG. 1 As shown in (b), the video element 102 can be moved off the phone screen as the user moves their finger. After the video element 102 is moved off the phone screen, the video in the video element 102 stops playing and is no longer displayed.

[0103] Current technology provides a floating window feature to solve the above problems.

[0104] In one of the related technologies, the floating window function can be customized by third-party application developers. Related technology one includes the following technologies 1-3.

[0105] Technology 1: Third-party application developers can customize page-level or application-level floating window functionality for their applications.

[0106] For example, combining FIG. 2 , A customized page-level floating window feature has been implemented. For example... FIG. 2 As shown in (a), the user is currently viewing a product details page 201, which includes a video element 202. When the user clicks the play button on the video element 202, the phone can begin playing an introductory video for the product. FIG. 2 As shown in (a), the user swipes their finger upwards on the phone screen. As the user's finger moves, the video element 202 can be moved off the phone screen. After the video element 202 is moved off the phone screen, as... FIG. 2 As shown in (b), the mobile phone can display a floating window 203, in which the product introduction video continues to play. However, when the user switches pages, such as returning to the previous page or jumping to another product details page, the floating window no longer appears, and the video stops playing.

[0107] For example, A customized application-level floating window feature has been implemented. This feature is available to users. When watching a video, if the user is When switching pages, the video will be moved to a floating window to continue playing. However, in After exiting, the floating window will no longer be displayed, and the video will stop playing.

[0108] Technology 2: Third-party application developers can customize system-level floating window functionality for their applications.

[0109] For example, such as Some video applications have customized picture-in-picture (PiP) functionality. When users play videos using these applications, they can trigger the video to move from the video component on the page to PiP (PiP can also be considered a floating window) by inputting corresponding actions. Afterwards, even if the user switches pages or exits the video application, the video can still continue playing in PiP for viewing. However, the applications and application types (mainly video applications) supported by PiP, or this system-level floating window, are limited.

[0110] Technology 3 Developers for A floating window function has been defined. This floating window serves as a temporary entry point for a mini-program or article link. For example, combined with... FIG. 3 ,like FIG. 3 As shown in (a) above, the user browses The information page 301 of a certain WeChat official account. Users can swipe from left to right on their phone screen to return to the previous page of information page 301. FIG. 3 As shown in (b), as the user slides their finger, the phone can display a portion of the information page 301 and a portion of the parent page 302 of the information page 301. In response to this slide, the phone can also display a floating indicator area 303 in the lower right corner of the screen. After the user slides their finger into this floating indicator area 303, as shown in (b), the phone can display a floating indicator area 303 in the lower right corner of the screen. FIG. 3 As shown in (c), the mobile phone can display a floating window 304, which is a link to the information page 301. Afterwards, the user... When switching pages, the floating window continuously displays a 304 error. After exiting, the floating window 304 will no longer be displayed. As described above, the floating window 304 is a temporary entry point for links. For example, the information page 301 requires the user to click on the floating window 304 before it will be displayed on the phone.

[0111] In related technology two, Huawei customized a freeform window feature. A freeform window can be considered a system-level floating window. Using this feature allows the entire application window to be displayed as a freeform window. Regardless of whether the user switches pages, opens other applications, or accesses the desktop, this freeform window remains on top. For example, combined with... FIG. 4 ,like FIG. 4As shown in (a) of FIG. 4, the mobile phone displays a chat interface 401. The user can perform a leftward sliding operation on the mobile phone screen starting from the right edge of the screen. In response to the sliding operation, the mobile phone can display a dock bar 402 including one or more application icons, such as a smart life icon 403. After the user performs an operation, such as a tapping operation, on the smart life icon 403 in the dock bar 402, the mobile phone displays the smart life interface in a freeform window 404, as shown in (b) of FIG. 4. Thereafter, the user switches pages in the chat application or opens other applications, and the smart life interface can be displayed in the freeform window on the mobile phone screen. However, the freeform window contains all the content in the application window, which has a lot of redundant information, affecting the acquisition and use experience of key information. FIG. 4 As shown in (a) of FIG. 4, the mobile phone displays a chat interface 401. The user can perform a leftward sliding operation on the mobile phone screen starting from the right edge of the screen. In response to the sliding operation, the mobile phone can display a dock bar 402 including one or more application icons, such as a smart life icon 403. After the user performs an operation, such as a tapping operation, on the smart life icon 403 in the dock bar 402, the mobile phone displays the smart life interface in a freeform window 404, as shown in (b) of FIG. 4. Thereafter, the user switches pages in the chat application or opens other applications, and the smart life interface can be displayed in the freeform window on the mobile phone screen. However, the freeform window contains all the content in the application window, which has a lot of redundant information, affecting the acquisition and use experience of key information.

[0112] It can be seen that the floating window function in the related art is mainly concentrated in a single application or page, or limited to a few applications and application types. Although the freeform window is a system-level global window, it contains the content of the full window of the application, which is too crowded and affects the final user experience.

[0113] The embodiments of the present application provide a display method of a dynamic window. The method can be applied to a terminal. After the triggering condition of the dynamic window is met, the terminal extracts key elements in the display interface of the terminal and displays the key elements in the form of a dynamic window on the screen of the terminal. The dynamic window supports page-level, application-level and system-level presentation, that is, the dynamic window can continue to be displayed on the screen of the terminal regardless of the page switching or application exit of the user. In addition, the content presented in the dynamic window is the key elements recommended by the system or customized by the third-party application, so that the user experience is not affected by too much content, and the processing needs of the user can be met.

[0114] It should be noted that the dynamic window in the embodiments can also be referred to as a floating window or a local window, which is not limited in the embodiments.

[0115] Exemplarily, the terminal in the embodiments of the present application can be a mobile phone, a tablet computer, a handheld computer, a PC, a cellular phone, a personal digital assistant (PDA), a wearable device (such as a smart watch), a vehicle-mounted computer, a game console, and an augmented reality (AR) \ virtual reality (VR) device, and the like. The specific form of the terminal is not specially limited in the embodiments of the present application. In addition, the technical solutions provided by the embodiments of the present application can be applied to other electronic devices, such as smart home devices (such as a television), and the like, in addition to the above-mentioned terminal (or mobile terminal).

[0116] The implementation of the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0117] In the embodiments of the present application, a mobile phone is taken as an example. Please refer to FIG. 5 , which is a structural schematic diagram of a mobile phone provided by the embodiments of the present application. The method in the following embodiments can be implemented in a mobile phone having the above hardware structure.

[0118] As shown in FIG. 5 , the mobile phone can include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a wireless communication module 160, an audio module 170, a loudspeaker 170A, a receiver 170B, a microphone 170C, a headset interface 170D, a sensor module 180, a key 190, a motor 191, an indicator 192, a camera 193, and a display screen 194, and the like. Optionally, the mobile phone can further include a mobile communication module 150, a subscriber identification module (SIM) card interface 195, and the like.

[0119] The sensor module 180 can include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

[0120] It is understood that the structure illustrated in the embodiments does not constitute a specific limitation on the mobile phone. In other embodiments, the mobile phone can include more or fewer components than illustrated, or combine certain components, or split certain components, or different arrangement of components. The illustrated components can be implemented in hardware, software, or a combination of software and hardware.

[0121] The processor 110 can include one or more processing units, for example: the processor 110 can include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Among them, different processing units can be independent devices, or can be integrated in one or more processors.

[0122] The controller can be the nerve center and command center of the mobile phone. The controller can generate operation control signals according to instruction operation codes and timing signals, complete the control of fetching instructions and executing instructions.

[0123] The memory can also be provided in the processor 110, used to store instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory can save instructions or data that the processor 110 has just used or repeatedly uses. If the processor 110 needs to use the instructions or data again, it can be directly called from the memory. Avoiding repeated access, reducing the waiting time of the processor 110, thus improving the efficiency of the system.

[0124] In some embodiments, the processor 110 can include one or more interfaces. The interfaces can include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a SIM interface, and / or a USB interface, etc.

[0125] The charging management module 140 is configured to receive charging input from a charger. The charging management module 140 can also supply power to the mobile phone through the power management module 141 while charging the battery 142. The power management module 141 is configured to connect the battery 142, the charging management module 140, and the processor 110. The power management module 141 can also receive input from the battery 142 to supply power to the mobile phone.

[0126] The wireless communication function of the mobile phone can be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem processor, and a baseband processor, etc.

[0127] The antenna 1 and the antenna 2 are configured to transmit and receive electromagnetic wave signals. Each antenna in the mobile phone can be used to cover a single or multiple communication frequency bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example, the antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in combination with a tuning switch.

[0128] When the mobile phone includes the mobile communication module 150, the mobile communication module 150 can provide a solution for wireless communication including 2G / 3G / 4G / 5G, etc. applied to the mobile phone. The mobile communication module 150 can include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves by the antenna 1, and perform filtering, amplification, etc. on the received electromagnetic waves, and transmit the processed signals to the modem processor for demodulation. The mobile communication module 150 can also amplify the signals modulated by the modem processor, and radiate the signals as electromagnetic waves through the antenna 1. In some embodiments, at least part of the functional modules of the mobile communication module 150 can be disposed in the processor 110. In some embodiments, at least part of the functional modules of the mobile communication module 150 can be disposed in the same device as at least part of the modules of the processor 110.

[0129] The modem processor can include a modulator and a demodulator. The modulator is configured to modulate a low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is configured to demodulate a received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. The low-frequency baseband signal processed by the baseband processor is transmitted to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the microphone 170B, etc.), or displays an image or a video through the display screen 194. In some embodiments, the modem processor can be a separate device. In other embodiments, the modem processor can be independent of the processor 110, and disposed in the same device as the mobile communication module 150 or other functional modules.

[0130] The wireless communication module 160 can provide a solution for wireless communication including wireless local area networks (WLAN) (such as Wi-Fi network), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), NFC, infrared technology (IR), etc. applied to the mobile phone. The wireless communication module 160 can be one or more devices integrated with at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering processing on the electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 can also receive signals to be transmitted from the processor 110, perform frequency modulation and amplification, and radiate the signals as electromagnetic waves through the antenna 2.

[0131] In some embodiments, the antennas 1 and the mobile communication module 150 are coupled, and the antennas 2 and the wireless communication module 160 are coupled, so that the mobile phone can communicate with a network and other devices through wireless communication technologies. The wireless communication technologies can include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies, etc. The GNSS can include global positioning system (GPS), global navigation satellite system (GLONASS), beidou navigation satellite system (BDS), quasi-zenith satellite system (QZSS), and / or satellite based augmentation systems (SBAS).

[0132] The mobile phone implements display functions through a GPU, the display screen 194, and an application processor, etc. The GPU is a microprocessor for image processing, connected with the display screen 194 and the application processor. The processor 110 can include one or more GPUs, which execute program instructions to generate or change display information.

[0133] The display screen 194 is configured to display images, videos, and the like. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flex light-emitting diode (FLED), a Miniled, a MicroLed, a Micro-oLed, a quantum dot light emitting diodes (QLED), or the like. In some embodiments, the mobile phone can include one or N display screens 194, where N is a positive integer greater than 1.

[0134] The mobile phone can implement the photographing function through the ISP, the camera 193, the video codec, the GPU, the display screen 194, and the application processor, and the like. In some embodiments, the mobile phone can include one or N cameras 193, where N is a positive integer greater than 1.

[0135] The external memory interface 120 can be configured to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the mobile phone. The external memory card communicates with the processor 110 through the external memory interface 120 to implement the data storage function. For example, the music, video, and the like are saved in the external memory card.

[0136] The internal memory 121 can be configured to store computer executable program codes including instructions. The processor 110 executes various function applications and data processing of the mobile phone by running the instructions stored in the internal memory 121. The internal memory 121 can include a program storage area and a data storage area. The program storage area can store an operating system, at least one application program required by a function (such as a sound playing function, an image playing function, and the like), and the like. The data storage area can store data created during the use of the mobile phone (such as audio data, a phone book, and the like), and the like. In addition, the internal memory 121 can include a high-speed random access memory, and can further include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, a universal flash storage (UFS), and the like.

[0137] The mobile phone can implement the audio function through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the earphone interface 170D, and the application processor, and the like. For example, music playing, recording, and the like.

[0138] The pressure sensor 180A is configured to sense a pressure signal and convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A can be disposed on the display screen 194. The pressure sensor 180A can be of various types, such as a resistive pressure sensor, an inductive pressure sensor, a capacitive pressure sensor, etc. When a touch operation is performed on the display screen 194, the phone can determine the intensity of the touch operation based on the pressure sensor 180A. The phone can also determine the location of the touch based on the detection signal of the pressure sensor 180A.

[0139] The gyroscope sensor 180B can be configured to determine the motion posture of the phone. The barometric pressure sensor 180C can be configured to measure the barometric pressure. The magnetic sensor 180D can include a Hall sensor. The phone can use the magnetic sensor 180D to detect the opening and closing of a flip cover. The acceleration sensor 180E can be configured to detect the acceleration of the phone in various directions (typically three axes). The distance sensor 180F can be configured to measure the distance. The phone can use the proximity light sensor 180G to detect that the user is holding the phone close to the ear for a call, so as to automatically turn off the screen to save power. The proximity light sensor 180G can also be used for automatic unlocking and locking of the phone in a cover mode or a pocket mode. The ambient light sensor 180L can be configured to sense the ambient light intensity. The fingerprint sensor 180H can be configured to collect a fingerprint. The phone can use the collected fingerprint characteristics to realize fingerprint unlocking, access application locking, fingerprint photographing, fingerprint answering a call, etc. The temperature sensor 180J can be configured to detect the temperature.

[0140] The touch sensor 180K, also referred to as a "touch panel". The touch sensor 180K can be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 can form a touch screen, also referred to as a "touch panel". The touch sensor 180K can be configured to detect a touch operation performed thereon or in the vicinity thereof. The touch sensor 180K can transmit the detected touch operation to the application processor to determine the type of touch event. The display screen 194 can be used to provide visual output related to the touch operation. In other embodiments, the touch sensor 180K can also be disposed on the surface of the phone, which is different from the location of the display screen 194.

[0141] The bone conduction sensor 180M can be configured to obtain a vibration signal. The keys 190 can include a power key, a volume key, etc. The keys 190 can be mechanical keys. Alternatively, the keys 190 can be touch keys. The motor 191 can be configured to generate a vibration prompt. The motor 191 can be used for incoming call vibration prompt, and can also be used for touch vibration feedback. The indicator 192 can be an indicator light, which can be used to indicate the charging status, the power change, and can also be used to indicate messages, missed calls, notifications, etc.

[0142] When the mobile phone includes the SIM card interface 195, the SIM card interface 195 is used to connect the SIM card. The SIM card can be connected and disconnected with the mobile phone by being inserted into or pulled out of the SIM card interface 195. The mobile phone can support one or N SIM card interfaces, and N is a positive integer greater than 1. The mobile phone interacts with the network through the SIM card to realize functions such as call and data communication. In some embodiments, the mobile phone uses an eSIM, that is, an embedded SIM card. The eSIM card can be embedded in the mobile phone and cannot be separated from the mobile phone.

[0143] The software structure of the terminal is exemplarily illustrated by taking the software system of the terminal as an Android system in the embodiments of the present application. It is referred to FIG. 6 for a composition schematic diagram of the software architecture of the terminal provided in the embodiments of the present application.

[0144] The software system of the terminal can adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. Taking the software system of the terminal as a layered architecture as an example, the layered architecture divides the software into a plurality of layers, and each layer has a clear role and division of labor. The layers communicate with each other through a software interface.

[0145] In some embodiments, as shown in FIG. 6 , the terminal can include an application layer and a framework layer (FWK). The application layer can include a series of application packages. For example, the application packages can include settings, calculator, camera, navigation, shopping, short message, video player, music player, and the like. The applications included in the application layer can be system applications of the terminal or third-party applications, and the embodiments of the present application do not make specific limitations here. The application layer can also include a drag service module and a live window controller. The application layer can also include a launcher. The live window controller can also be referred to as a live window manager, and the embodiments of the present application do not make specific limitations here.

[0146] The framework layer is mainly responsible for providing application programming interfaces (APIs) and programming frameworks for the applications of the application layer. The framework layer can include a window manager (WM) and the like. The window manager can also be referred to as a window management module, and the embodiments of the present application do not make specific limitations here.

[0147] Of course, the terminal can also include other layers, such as a kernel layer (not shown in FIG. 6 ) and the like. The kernel layer is a layer between hardware and software. The kernel layer can at least include display drivers, camera drivers, audio drivers, sensor drivers, and the like.

[0148] In the embodiments of the present application, based on the software architecture described above, when the terminal currently displays an interface of an application, referred to as interface 1, after meeting the triggering condition of the dynamic small window, such as receiving a user operation for triggering the display of the dynamic small window, or the page content changes, or jumping to another application, the terminal can extract the key elements in the interface 1 displayed by the terminal, and add these key elements to the dynamic small window for display on the terminal screen, for the user to continue browsing.

[0149] The embodiments of the present application will be described in detail below with reference to the drawings. FIG. 6 For example, taking a terminal as a mobile phone, the window display method provided by the embodiments of the present application will be described in detail with reference to the drawings. FIG. 7 A flowchart of a window display method provided by the embodiments of the present application is shown in FIG. 1. FIG. 7 As shown in FIG. 1, the method can include:

[0150] S701, the mobile phone displays an application window and receives a user operation for triggering the display of a dynamic small window.

[0151] The window is the most important part of the user interface (user interface, UI), which is a rectangular area on the display screen corresponding to the application, and is the visual interface between the user and the application that generates the window. Generally, after the mobile phone receives a user operation for starting an application, the application can create and display a window in the form of a full-screen large window, which can be referred to as an application window. When the user operates the controls of the interface in the application window, the application can respond accordingly.

[0152] The dynamic small window in the embodiments can refer to a window for presenting key elements of an application on the display screen, which is displayed in the form of a small window floating on the large window on the display screen. When the content on the display screen changes, such as switching the application window or switching the interface in the same application window, the dynamic small window can continue to be displayed. The dynamic small window in the embodiments can also be referred to as a floating small window, a local small window, etc. The application described above can be any one of the applications installed on the mobile phone. The application can be a system application or a third-party application, which is not specifically limited in the embodiments.

[0153] In the embodiments, when the mobile phone displays an application window of an application (which can be the application window of the first application in the embodiments of the present application), the user can perform a corresponding user operation to trigger the mobile phone to display the key elements included in the interface of the application window in the form of a dynamic small window on the display screen of the mobile phone. The user operation can include one or more operations.

[0154] In a possible implementation, the user operation can include an operation of triggering display of the multitasking interface (which can be the second operation in the embodiments of the present application) and an operation of dragging the application window to the specified area in the multitasking interface (which can be the first operation in the embodiments of the present application, or the dragging operation).

[0155] The operation of triggering display of the multitasking interface can be a touch gesture operation or a gesture operation in the air. For example, the touch gesture operation can be a sliding operation on the display screen of the mobile phone, such as a sliding operation from the lower edge of the display screen of the mobile phone to the upper edge of the display screen of the mobile phone, and the finger or stylus is not lifted temporarily after the sliding. The gesture operation in the air can be a static gesture operation in the air or a dynamic gesture operation in the air. The static gesture operation in the air refers to the posture of the hand at a moment, such as finger bending, folding, etc. For example, the OK gesture, the V gesture, the gesture of stretching five fingers, etc. The dynamic gesture operation in the air refers to the motion of the hand in a period of time, including the motion direction, speed, change of the posture of the hand, etc. For example, the waving gesture, the panning gesture, the fist gesture, the pressing gesture, etc. The gesture operation in the air for triggering display of the multitasking interface can be any one of the above static gesture operation in the air or the dynamic gesture operation in the air.

[0156] The operation of dragging the application window to the specified area in the multitasking interface can be a touch gesture operation. For example, the touch gesture operation can be an operation of pressing and moving the application window in the multitasking interface. The operation of dragging the application window to the specified area in the multitasking interface can also be a gesture operation in the air. For example, the gesture operation in the air can be a pressing gesture and a panning gesture for the application window in the multitasking interface. For another example, the gesture operation in the air can be a fist gesture and a panning gesture for the application window in the multitasking interface. For another example, the gesture operation in the air can be a static gesture operation in the air and a panning gesture for the application window in the multitasking interface.

[0157] In another possible implementation, the user operation can include an operation of triggering the application window to be dragged up and an operation of dragging the dragged application window to the specified area.

[0158] The operation triggering the application window to be dragged up can be a touch screen gesture operation. For example, the touch screen gesture operation triggering the application window to be dragged up can be any one of the following predetermined gesture operations: a sliding operation on the display screen (e.g., a sliding operation from the lower edge of the mobile phone to the upper edge of the mobile phone) when the mobile phone displays the application window, a gesture operation on the title bar of the application window (e.g., a long press operation, a double-click operation, etc.), a gesture operation on the application window (e.g., a single-finger long press operation, a single-finger double-click operation, a multi-finger long press operation, etc.), a 3D touch operation on the application window, a palm operation on the application window (e.g., a palm long press operation, a palm single-click operation, etc.), etc. The operation triggering the application window to be dragged up can also be the above-mentioned mid-air gesture operation.

[0159] The operation of dragging the dragged application window to the specified area can be a touch screen gesture operation or a mid-air gesture operation. The operation of dragging the dragged application window to the specified area is similar to the above-mentioned operation of dragging the application window to the specified area in the multi-task interface, and will not be described in detail here.

[0160] In the above implementation, the specified area can be an area on the display screen of the mobile phone at a predetermined distance from an edge of the display screen. The predetermined distance can be predefined or can be provided with a setting interface for the user to set, and the present embodiment does not limit this. For example, the specified area can be an area on the display screen of the mobile phone at a distance of 1 / 3 or 1 / 2 from the upper edge of the display screen.

[0161] For example, in combination with the above-mentioned implementation, FIG. 6 In the above-mentioned implementation, in the case that the application window is dragged up in the multi-task interface or the application window is dragged up, the user can drag (or drag and drop) the application window by performing a corresponding operation. During the dragging of the application window, the mobile phone, such as the launcher of the application layer of the mobile phone, can perform drag monitoring to determine whether the application window is dragged to the specified area. In the present embodiment, the specified area can also be referred to as a docking area.

[0162] In some embodiments, a transparent view control can be provided in the above-mentioned specified area. When the application window is dragged into the specified area, the view control provided in the specified area can monitor the dragging of the application window. That is, when the view control monitors the dragging of the application window, the mobile phone (such as the launcher of the application layer of the mobile phone) can determine that the application window is dragged to the specified area.

[0163] In some other embodiments, the mobile phone (such as the launcher of the mobile application layer) can determine whether the application window has been dragged to a designated area by judging the distance between the application window and the edge of the display screen. For example, taking the designated area as one-third of the distance from the top edge of the display screen as an example, the launcher of the mobile application layer can determine that the application window has been dragged to the designated area when the distance between the top left or top right corner of the application window and the top edge of the display screen is less than a predetermined distance, such as 1 / 3*L (where L is the length of the mobile phone display screen). For example, please refer to... FIG. 8A This is a schematic diagram of a display coordinate system provided in this embodiment. FIG. 8A As shown, the origin of this display coordinate system is the top left corner of the phone screen. The x-axis points from the origin to the right edge of the screen, and the y-axis points from the origin to the bottom edge. The top edge of the screen is 0 on the y-axis in this coordinate system. In the application window, as shown... FIG. 8A As the application window 801 shown is dragged by the user on the mobile phone screen, the mobile phone can monitor the upper left and upper right corners of the application window 801 in real time, such as... FIG. 8A The coordinates of A1 and A2 in the display coordinate system are shown. For example, the coordinates of the top-left corner A1 in the display coordinate system are (x1, y1), and the coordinates of the top-right corner A2 in the display coordinate system are (x2, y1). Based on the coordinates of these two corners of the application window 801 and the coordinates of the top edge of the mobile phone display screen, the mobile phone can determine that the application window 801 has been dragged to the specified area when it determines that the distance between one of these two corners and the top edge of the display screen is less than 1 / 3*L. For example, if the mobile phone determines that the distance (e.g., y1) between the top-left corner A1 or the top-right corner A2 and the top edge of the display screen is less than 1 / 3*L based on the y-coordinate y1 of the top-left corner A1 or the top-right corner A2 on the y-axis, then it can determine that the application window 801 has been dragged to the specified area.

[0164] In some other embodiments, the mobile phone (such as the launcher of the mobile application layer) can determine whether the application window has been dragged to a designated area by judging the distance between the user's finger's pressing point and the edge of the display screen during the user's dragging process. For example, taking the designated area as the area 1 / 2 of the distance from the top edge of the display screen as an example, the launcher of the mobile application layer can determine that the application window has been dragged to the designated area when it is determined that the distance between the user's finger's pressing point and the top edge of the display screen is less than a predetermined distance, such as 1 / 2*L (where L is the length of the mobile phone display screen), and the user continues to slide their finger in the same direction. For example, please refer to... FIG. 8B This is a schematic diagram of a display coordinate system provided in this embodiment. FIG. 8B As shown, the origin of this coordinate system is the top left corner of the phone screen, the x-axis points from the origin to the right edge of the phone screen, and the y-axis points from the origin to the bottom edge of the phone screen. In the application window, as shown... FIG. 8BDuring the process that the application window 801' shown in the middle is dragged by the user on the display screen of the mobile phone, the mobile phone can monitor the pressing point of the user's finger in real time, such as the coordinate of point A in the display coordinate system. According to the pressing point of the user's finger, i.e. the coordinate of point A in the display coordinate system, when the mobile phone determines that the distance between the user's finger and the edge of the display screen is less than 1 / 2*L and the user continues to slide the finger in the same direction, it is determined that the application window 801' is dragged to the specified area.

[0165] After the mobile phone determines that the application window is dragged to the specified area, it indicates that the user wants to use the dynamic small window function of the mobile phone, and the following S702 can be executed.

[0166] In another possible implementation, the user operation can be an operation of switching to another page in the application window. The operation can be a touch gesture operation or a midair gesture operation. For example, the touch gesture operation can be a sliding operation on the display screen of the mobile phone, such as a sliding operation starting from the left edge of the display screen of the mobile phone to the right edge of the display screen. The touch gesture operation can also be a clicking operation on a back button in the current page of the application window. The midair gesture operation can be any one of the static midair gesture operation or the dynamic midair gesture operation in the above implementation.

[0167] Alternatively, the user operation can be a sliding operation on the current page of the application window. The sliding operation can be a touch gesture operation, such as a sliding operation from bottom to top or from top to bottom on the display screen of the mobile phone. The sliding operation can trigger the current page of the application window to slide down or up. Alternatively, the user operation can be a sliding operation starting from the right edge of the display screen of the mobile phone to the left edge of the display screen.

[0168] In another possible implementation, the user operation can be an operation of switching the currently opened application of the mobile phone to the background. The operation can be a touch gesture operation or a midair gesture operation. For example, the touch gesture operation can be a sliding operation on the display screen of the mobile phone, such as a sliding operation starting from the bottom edge of the display screen of the mobile phone to the top edge of the display screen. The midair gesture operation can be any one of the static midair gesture operation or the dynamic midair gesture operation in the above implementation.

[0169] In another possible implementation, when the mobile phone displays the application window, if the mobile phone receives a notification message of another application, the user operation can be a selection operation on the notification message. The selection operation can be a touch gesture operation, such as a clicking operation on the notification message.

[0170] In yet another possible implementation, the application window can be displayed on the display screen of the mobile phone in the form of a full-screen floating window (such as a freeform window). In the case where the mobile phone displays a full-screen floating window (such as a freeform window), the user can perform a corresponding user operation to trigger the mobile phone to display the key element included in the application window in the freeform window in the form of a dynamic window on the display screen of the mobile phone. The user operation can include one or more operations. For example, the user operation (which can be the first operation in the present application) can include an operation of dragging the freeform window to a specified area. The operation can be a touch gesture operation or a hovering gesture operation. It should be noted that the operation of dragging the freeform window to the specified area is similar to the operation of dragging the application window to the specified area in the multitasking interface, and will not be described in detail herein. In addition, the explanation of the specified area and the implementation of determining whether the freeform window is dragged to the specified area are similar to the description of the explanation of the specified area and the determination of whether the application window is dragged to the specified area in the foregoing embodiments, and will not be described in detail herein. Alternatively, the user operation can also be an operation (such as a click operation) on a window button in the freeform window. The window button is used to trigger the mobile phone to display the key element included in the application window in the freeform window in the form of a dynamic window on the display screen of the mobile phone. For specific implementation of triggering the mobile phone to display the application window in the form of a freeform window, reference can be made to the implementation of the example shown in FIG. 4 .

[0171] It should be noted that the touch gesture operation described above can be performed by the user using a hand or using a stylus, and the present embodiment does not limit this. In the present embodiment, pressing down can also be described as holding down, which refers to an operation of pressing down a finger (or holding down the screen using a stylus) without lifting up.

[0172] For example, in combination with FIG. 9 , it is assumed that the application window is the window of application 1, and the user operation in S701 includes an operation of triggering display of a multitasking interface and an operation of dragging the application window to a specified area in the multitasking interface. As shown in (a) of FIG. 9 , the display screen of the mobile phone displays the application window 901 of application 1. The application window 901 includes a news detail page, and the news detail page includes a video element 902. When the user wants to display the key element in the application window 901 in the form of a dynamic window, the user can perform an operation of triggering display of a multitasking interface, such as a sliding operation starting from the lower edge of the display screen of the mobile phone to the upper edge of the display screen of the mobile phone, and the finger is not lifted up after the sliding operation. As shown in (b) of FIG. 9As shown in (b), in response to this operation, the phone displays a multitasking interface 903. This multitasking interface 903 includes application windows (or application window thumbnails) of all applications running in the background on the phone, such as the application window thumbnail 904 of application 1 mentioned above. Then, by pressing the application window thumbnail 904 and moving their finger, the user can drag the application window thumbnail 904 to a designated area on the phone screen, such as moving the finger's pressing point to an area halfway up the top edge of the screen and continuing to swipe upwards. For example, as shown... FIG. 9 As shown in (c), the user can press the application window thumbnail 904 with their finger and move their finger upwards. As the user's finger moves, the phone can animate the application window thumbnail 904 following the user's finger movement and display it on the phone's screen. After the phone determines that the application window thumbnail 904 has been dragged to the designated area 905, indicating that the user wants to use the phone's dynamic thumbnail function, it can execute the following steps S702-S703. Alternatively, as... FIG. 9 As shown in (b), the phone displays a multitasking interface 903. If the application window supports dynamic pop-up functionality, the multitasking interface 903 may also include a pop-up button corresponding to the application window. For example, if the application window 901 of application 1 supports dynamic pop-up functionality, such as... FIG. 9 As shown in (b), the multitasking interface 903 also includes a button 906 corresponding to the application window thumbnail 904 of application 1. If the mobile phone receives an operation from the user on the button 906, such as a click, indicating that the user wants to use the mobile phone's dynamic mini-window function, then the following steps S702-S703 can be executed.

[0173] For example, combining FIG. 10A Taking the application window as the navigation application window, and the user operation in S701 as a selection operation of notification messages as an example. FIG. 10A As shown in (a), the mobile phone's display screen shows an application window 1001 for a navigation application. This application window 1001 includes a navigation details page. While the user is navigating using this navigation application, the mobile phone receives notification messages, such as... FIG. 10A As shown in (b), the phone displays a notification message prompt 1002. When the user wants to view the notification message, they can click on prompt 1002. It is understood that after the user clicks on prompt 1002, the phone will display the details screen corresponding to prompt 1002. Therefore, after receiving this click, the phone can also execute S702-S703, triggering the phone to display key elements of the navigation details page in application window 1001 as dynamic small windows on the phone screen for the user to continue viewing. Combined with... FIG. 10BFor example, the application window is a video application window, and the user operation in S701 is a selection operation on the notification message. As shown in FIG. 10B In (a) of FIG. 7, the display screen of the mobile phone displays a video application window 1001'. The video application window 1001' includes a video detail page. The mobile phone receives a notification message, as shown in FIG. 10B In (b) of FIG. 7, the mobile phone displays prompt information 1002' of the notification message. When the user wants to view the notification message, the user can perform a click operation on the prompt information 1002'. It can be understood that after the user performs the click operation on the prompt information 1002', the mobile phone will display a detail interface corresponding to the prompt information 1002'. Therefore, after receiving the click operation, the mobile phone can further perform S702-S703, that is, the mobile phone can trigger the display of a key element of the video detail page in the video application window 1001' in the form of a dynamic small window on the display screen of the mobile phone, for the user to continue viewing.

[0174] For example, in combination with FIG. 11 The application window is an instant messaging application window, and the user operation in S701 is an operation of switching the instant messaging application to the background. As shown in FIG. 11 In (a) of FIG. 8, the display screen of the mobile phone displays an instant messaging application window 1101. The instant messaging application window 1101 includes a chat detail page. When the user wants to display a key element in the instant messaging application window 1101 in the form of a dynamic small window, the user can perform an operation of switching the instant messaging application to the background, such as a sliding operation starting from the lower edge of the display screen of the mobile phone to the upper edge of the display screen of the mobile phone. After receiving the operation, the mobile phone can perform S702-S703.

[0175] S702. In response to the user operation in S701, the mobile phone obtains small window data.

[0176] After receiving the user operation in S701, the mobile phone indicates that the user wants to display a key element of a currently displayed interface in an application window in the form of a dynamic small window. The mobile phone can obtain small window data.

[0177] The small window data can include an identifier of the application. The small window data can further include an identifier of the interface in the application window, and / or an interface of the application in the application window, such as a screenshot of the application window (or an interface screenshot of the application in the application window). The identifier of the application can be a package name of the application. The identifier of the interface can be an Activity name of the interface.

[0178] For example, in combination with FIG. 6application window, the phone, such as the launcher of the phone application layer, can initiate the dragging of the application window. During the dragging of the application window, the launcher of the phone application layer can perform the dragging monitoring, and after determining that the application window is dragged to the specified area, the launcher of the phone application layer can obtain the package name of the application and the identifier of the interface in the application window from the stack of the activities of the phone, and according to the package name of the application, the interface of the application in the application window can be found, such as a screenshot of the application window, to obtain the above-mentioned small window data. Then, the launcher of the phone application layer can send the obtained small window data to the dragging service module of the phone application layer. The dragging service module of the phone application layer can obtain the small window data.

[0179] It should be noted that when the user operation in S701 is the operation of triggering the application window to be dragged and the operation of dragging the dragged application window to the specified area, or the user operation is the operation of switching the currently opened application of the phone to the background, or the user operation is the selection operation on the notification message, the specific implementation of the phone to obtain the small window data is similar to the specific implementation of the phone to obtain the small window data when the user operation is the operation of triggering the display of the multi-task interface and the operation of dragging the application window to the specified area in the multi-task interface, and will not be described in detail here. When the user operation is the operation of switching to other pages in the application window, or the sliding operation on the current page of the application window, the specific implementation of the phone to obtain the small window data can be that after receiving the user operation, the application of the application window can obtain the small window data, and then send the obtained small window data to the dragging service module of the phone application layer.

[0180] In addition, in some embodiments, when the user operation in S701 includes a drag operation on an application window, the user's intention of dragging the application window can be to trigger generation of a dynamic mini-window or to trigger cross-device dragging. As described above, the mini-window data is reported by the launcher of the mobile application layer to the drag service module of the application layer and is processed by the drag service module. In order to enable the drag service module to distinguish whether the user operation is used to trigger display of a dynamic mini-window or to trigger cross-device dragging, the object type can also be included in the above-described mini-window data. The object type is different from the object type in the data obtained by the drag service module when cross-device dragging is performed, and the object type can be used to indicate triggering of display of a dynamic mini-window. For example, the object type can be a live window. As an example, in order to unify the structure of the mini-window data, in this embodiment, for the user operations in various implementation manners in S701, the object type can be included in the mini-window data obtained by the drag service module of the mobile application layer after the user wants to trigger display of a dynamic mini-window and performs the corresponding user operation.

[0181] Continue to combine FIG. 6 After the drag service module of the mobile application layer obtains the mini-window data, it can be determined whether the object type in the mini-window data is a live window to determine whether to trigger display of a dynamic mini-window. After it is determined that the object type in the mini-window data is a live window, the drag service module of the mobile application layer can transmit the mini-window data to the dynamic mini-window controller of the mobile application layer. In some other embodiments, FIG. 6 In the software architecture shown, the drag service module can also not be included. In this embodiment, after receiving the user operation in S701, the launcher or the application of the mobile application layer can obtain the mini-window data and directly transmit the mini-window data to the dynamic mini-window controller of the mobile application layer.

[0182] The above embodiments are described by taking the mobile phone receiving the user operation in S701 and then obtaining the mini-window data as an example. In some other embodiments, after receiving the user operation in S701, the mobile phone can first determine whether the currently displayed application window supports display of a dynamic mini-window. If the application window supports display of a dynamic mini-window, S702 is performed. If the application window does not support display of a dynamic mini-window, the mobile phone can not perform S702, and the mobile phone can display a prompt information to prompt the user that the application window does not support display of a dynamic mini-window.

[0183] In some implementations, the specific implementation of determining whether the application window supports the display of the dynamic widget can be that the mobile phone can store a white list in which the identities of the applications that support the display of the dynamic widget are included. After receiving the user operation in S701, the mobile phone can determine whether the identity of the application corresponding to the application window is included in the white list. When the identity of the application is included in the white list, the mobile phone can determine that the application window supports the display of the dynamic widget. If the identity of the application is not included in the white list, the mobile phone can determine that the application window does not support the display of the dynamic widget. In other implementations, the specific implementation of determining whether the application window supports the display of the dynamic widget can be that, after receiving the user operation in S701, the mobile phone can determine whether the interface of the application in the application window includes a video component. If the interface of the application in the application window includes a video component, it can be determined that the application window supports the display of the dynamic widget. If the interface of the application in the application window does not include a video component, it can be determined that the application window does not support the display of the dynamic widget. In still other implementations, the specific implementation of determining whether the application window supports the display of the dynamic widget can be that the mobile phone can pre-store application types that support the display of the dynamic widget. After receiving the user operation in S701, the mobile phone can determine whether the type of the application corresponding to the application window is an application type that supports the display of the dynamic widget. When the type of the application is an application type that supports the display of the dynamic widget, the mobile phone can determine that the application window supports the display of the dynamic widget. If the type of the application is not an application type that supports the display of the dynamic widget, the mobile phone can determine that the application window does not support the display of the dynamic widget.

[0184] S703, the mobile phone displays the dynamic widget according to the widget data.

[0185] After the mobile phone obtains the widget data, the mobile phone can display the dynamic widget on the display screen according to the widget data. The dynamic widget can include one or more types of elements, such as a display element and a control element. The display element can include one or more of a picture, a video, a text, an icon, and a banner. The control element can include one or more of a button, a progress slider, and a toolbar. That is, the dynamic widget can include one or more of a picture, a video, a text, an icon, a banner, a button, a progress slider, and a toolbar.

[0186] For example, the elements included in the dynamic widget can be part of the elements of the interface of the application window displayed by the mobile phone before receiving the user operation in S701. For ease of description, the elements included in the dynamic widget can be referred to as widget elements.

[0187] As an example, the mobile phone can extract the widget element from the widget window corresponding to the application window according to the identification of the application included in the widget data. Alternatively, the mobile phone can extract the widget element from the interface of the corresponding application window according to the identification of the application and the identification of the interface included in the widget data. In the embodiments of the present application, the first identification can be the identification of the application, or the first identification can include the identification of the application and the identification of the interface.

[0188] In a possible implementation, the widget element can be predefined. That is, which elements are the widget elements can be predefined. The widget elements corresponding to different applications can be the same or different. The widget elements corresponding to different interfaces of the same application can be the same or different.

[0189] For example, the application developer can define which elements in the application are the widget elements in advance, and store the corresponding configuration file in the mobile phone. Taking the case that the widget elements corresponding to different applications are different as an example, the identification of the application and the configuration file can be stored in the mobile phone. The identification of the application can be the package name of the application. As shown in Table 1, the configuration file 1 is stored corresponding to the package name 1 of the application 1, the configuration file 2 is stored corresponding to the package name 2 of the application 2, and so on.

[0190] Table 1

[0191] Application identifier Configuration file Package name 1 Configuration file 1 Package name 2 Configuration file 2 … …

[0192] For example, the application developer can define which elements in the application are the widget elements in advance, and store the corresponding configuration file in the mobile phone. Taking the case that the widget elements corresponding to different applications are different as an example, the identification of the application and the configuration file can be stored in the mobile phone. The identification of the application can be the package name of the application. As shown in Table 1, the configuration file 1 is stored corresponding to the package name 1 of the application 1, the configuration file 2 is stored corresponding to the package name 2 of the application 2, and so on.

[0193] Table 2

[0194]

[0195] The aforementioned configuration file may include identifiers of elements to be displayed in the dynamic pop-up window. These identifiers may include one or more of the following: element ID (e.g., view ID), element class name (e.g., view class), and sorting sequence number (e.g., view index). Furthermore, as described in S702, the pop-up window data includes application identifiers, which correspond to the application window displayed on the phone before the user performs the user operation in S701. Thus, based on Table 1 (or Table 2), the phone can first locate the corresponding configuration file based on the application identifiers (or, the application identifier and the identifier of the interface in the application window) included in the pop-up window data. Then, based on the identifiers of the elements included in the found configuration file, the phone can extract the pop-up window elements from the interface of the application window.

[0196] For example, consider storing configuration files and application identifiers on the phone. Combined with... FIG. 6 As described in S702, the mobile phone searches for the corresponding configuration file based on the application identifier included in the small window data. The specific implementation of extracting small window elements from the application window interface based on the element identifiers in the configuration file can be as follows: After receiving small window data from the drag-and-drop service module of the mobile phone application layer, the dynamic small window controller of the mobile phone application layer can find the corresponding configuration file based on the application identifier included in the small window data. The dynamic small window controller of the mobile phone can also start a virtual display (or virtual screen). For example, the dynamic small window controller of the mobile phone sends a request to the mobile phone display manager to create a Virtual Display. After the display manager completes the creation of the Virtual Display, it can return the identifier (identify, ID) of the created Virtual Display to the dynamic small window controller of the mobile phone. Then, the dynamic small window controller of the mobile phone can transmit the Virtual Display ID and the application package name from the small window data to the window manager of the mobile phone frame layer. Based on the Virtual Display ID and the application package name, the window manager of the mobile phone can move the application window of the application indicated by the package name onto the Virtual Display for drawing. For example, the phone's window manager can find the stack identifier (stackId) of the application indicated by the package name, and then move the corresponding stack to the virtual display for drawing based on the stackId and the VirtualDisplay ID. Afterwards, the phone's dynamic pop-up controller can extract the pop-up element from the application window drawn on the VirtualDisplay based on the identifiers of the elements included in the found configuration file.

[0197] For example, combining FIG. 12For example, before the user performs the user operation in S701, the application window 1201 displayed by the mobile phone, the application developer predefines elements 3, 4 and 5 in the application window 1201 as small-window elements, and the corresponding configuration file is stored in the mobile phone. The small-window data includes the package name of the application corresponding to the application window 1201. After the dynamic small-window controller of the mobile phone receives the small-window data, the dynamic small-window controller can find the corresponding configuration file according to the package name of the application included in the small-window data, where the configuration file includes the identifier of the element 3, the identifier of the element 4 and the identifier of the element 5. The dynamic small-window controller of the mobile phone can also start the VirtualDisplay, and transmit the ID of the VirtualDisplay and the package name of the application in the small-window data to the window manager of the mobile phone. According to the ID of the VirtualDisplay and the package name of the application, the window manager of the mobile phone can draw the application window 1201 on the VirtualDisplay. Wherein, the application window 1201 drawn on the VirtualDisplay includes elements 1, 2, … and 10. According to the identifier of the element 3, the identifier of the element 4 and the identifier of the element 5 included in the configuration file found, the dynamic small-window controller of the mobile phone can extract the element 3, the element 4 and the element 5 from the application window 1201 drawn on the VirtualDisplay. The extracted element 3, element 4 and element 5 will be displayed in the form of a dynamic small window on the display screen of the mobile phone.

[0198] In another possible implementation, the small-window elements can be recommended by the system. That is, the system can recommend which elements as small-window elements. Wherein, the small-window elements corresponding to different types of applications can be the same or different. For example, taking different types of applications corresponding to different small-window elements as an example. The mobile phone can pre-store recommended models corresponding to different types of applications. The application type can include one or more of the following types: music, video, navigation, e-commerce, instant messaging (IM), etc. As shown in Table 3, the recommended model 1 corresponds to the music type, the recommended model 2 corresponds to the video type, the recommended model 3 corresponds to the navigation type, the recommended model 4 corresponds to the e-commerce type, and the recommended model 5 corresponds to the instant messaging type, etc.

[0199] Table 3

[0200] Application type Recommendation model Music Recommendation model 1 Video Recommendation model 2 Navigation Recommendation model 3 E-commerce Recommendation model 4 Instant messaging Recommendation model 5 … …

[0201] Based on Table 3, the mobile phone can first determine the type of the application according to the identifier of the application included in the small-window data. Then, find the recommended model corresponding to the type of the application. After that, the mobile phone can extract the small-window elements from the interface of the application window according to the found recommended model.

[0202] It can be understood that the mobile phone extracts one or more widget elements from the interface of the application window according to the configuration file or the recommended model. Then, the mobile phone displays the extracted one or more widget elements in the form of a dynamic widget on the display screen of the mobile phone.

[0203] For example, the mobile phone displays the widget elements in the dynamic widget according to a pre-configured layout file. The layout file includes the configuration of the drawing area of each widget element (such as the configuration including the identification, position, and style of the element), and the drawing areas of the widget elements do not overlap or partially overlap. In addition, the drawing areas of the widget elements in the layout file can not correspond to the areas of the corresponding widget elements in the original interface, that is, the layout of the widget elements can be reconfigured through the layout file.

[0204] In the above description of extracting the widget elements, when the widget elements corresponding to different applications are the same, the layout files corresponding to different applications can be the same or different. When the widget elements corresponding to different applications are different, the layout files corresponding to different applications are different. In the case that the layout files corresponding to different applications are different, the identification of the application (such as the package name) and the layout file can be stored in the mobile phone in correspondence. When different interfaces of the same application correspond to different widget elements, different interfaces can also correspond to different layout files. In the case that different interfaces of the same application correspond to different component files, the identification of the application, the identification of the interface, and the layout file can be stored in the mobile phone in correspondence.

[0205] The layout file can also be defined by the system developer without the definition of the application developer, that is, the layout of the widget elements is recommended by the system. In the above description of extracting the widget elements, when the widget elements corresponding to different types of applications are the same, the layout files corresponding to different application types can be the same or different. When the widget elements corresponding to different types of applications are different, the layout files corresponding to different application types are different. In the case that the layout files corresponding to different types of applications are different, the application type and the layout file can be stored in the mobile phone in correspondence.

[0206] Based on the above description, the mobile phone can obtain the corresponding layout file according to the identification of the application corresponding to the application window (or the identification of the application and the identification of the interface, or the type of the application), for realizing the layout of the extracted widget elements in the dynamic widget. For example, in the case that the layout file is stored in the mobile phone in correspondence with the identification of the application, the mobile phone can obtain the layout file corresponding to the application according to the identification of the application. FIG. 6 In combination with the above description of extracting the widget elements, the dynamic widget controller of the application layer of the mobile phone can find the corresponding layout file according to the identification of the application in the widget data, and layout the extracted widget elements according to the found layout file. For example, in combination with FIG. 12As shown in the example, the mobile phone's dynamic pop-up controller, based on the found layout file, rearranges the extracted elements 3, 4, and 5 as follows: FIG. 13 As shown in (a) in the figure.

[0207] It should be noted that in this embodiment, there can be one or more layout files corresponding to the same application (or the same interface of an application, or an application of the same type). This embodiment does not impose specific limitations on this. Taking different applications corresponding to different layout files as an example, it can be understood that for the same small window element, the display effect after the phone rearranges the layout based on different layout files will be different. For example, combined with FIG. 12 and FIG. 13 Taking an application with three layout files as an example, after the phone extracts elements 3, 4, and 5, the results of rearranging them using these three different layout files are as follows: FIG. 13 (a) FIG. 13 (b) and FIG. 13application (or the same interface of the application, or the same type of application) has multiple corresponding layout files, the phone can select any one of the multiple layout files to re-layout the extracted widget elements; or the system developer can provide multiple layout files, and the application developer can select one of the multiple layout files, so that the phone can select the corresponding layout file according to the designation of the application developer to re-layout the extracted widget elements. In addition, in the embodiment, the phone can re-layout the extracted widget elements according to the layout file can be achieved by calling the layout capability provided by the system. For example, the system can provide one or more layout capabilities such as secondary layout capability (also referred to as RIO capability), DUP capability, and recommended layout capability. After the widget elements are extracted, the phone can re-layout the widget elements according to the corresponding layout file and by calling the layout capability provided by the system. The DUP capability can also be used to extract the widget elements. For example, the phone can call the DUP capability of the system to extract the widget elements according to the corresponding configuration file (referred to as DUP configuration file). Similarly, the same application (or the same interface of the application, or the same type of application) can have one or more corresponding configuration files (or recommended models). For the same application (or the same interface of the application, or the same type of application), the phone extracts different widget elements according to different configuration files (or recommended models). When the same application (or the same interface of the application, or the same type of application) has multiple corresponding configuration files (or recommended models), the phone can select any one of the multiple configuration files (or recommended models) to extract the widget elements; or the system developer can provide multiple configuration files (or recommended models), and the application developer can select one of the multiple configuration files (or recommended models) to extract the widget elements.

[0208] It should be noted that in the case of any application, the widget elements in the dynamic widget only include one or more predetermined elements, such as only including video elements, the above configuration file / recommended model can not be stored (or not needed) in the embodiment, and the above layout file can also not be stored. In this case, after the phone obtains the widget data, it can directly identify the predetermined elements in the application window, such as video elements, and then re-layout according to the default layout mode. That is, the widget elements are predetermined, and the layout is also predetermined.

[0209] After the extracted widget elements are re-laid out, the phone can display the re-laid out widget elements in the form of a dynamic widget on the display screen of the phone.

[0210] As described in the preceding embodiments, the dynamic window is a small window that floats on the display screen. It is understood that the mobile phone display screen can be divided into multiple grids horizontally or vertically, for example, 4 grids, 8 grids, 12 grids, etc. In this embodiment, the size of the small window, or dynamic window, can be set based on the grid division of the mobile phone display screen. For example, the system developer or application developer can set the size of the dynamic window based on the grid according to requirements.

[0211] For example, combining FIG. 14-FIG. 16 Taking the aspect ratio of the horizontal dynamic window as 16:10 and the aspect ratio of the vertical dynamic window as 10:16 as examples, the display effects of the horizontal and vertical dynamic windows are shown when the mobile phone screen is vertically divided into 4 grids, 8 grids and 12 grids respectively.

[0212] Among them, combined FIG. 14 ,like FIG. 14 As shown in (a), for a landscape-style dynamic window, system developers or application developers can set the width of the dynamic window to 2 grids. Based on the aspect ratio of 16:10 for the landscape dynamic window, the phone can use the 4 grids that divide the phone screen as a reference to display a dynamic window 1401 with a width of 2 grids on the phone screen. For a portrait-style dynamic window, system developers or application developers can set the height of the dynamic window to 2 grids. Based on the aspect ratio of 10:16 for the portrait dynamic window, the phone can use the 4 grids that divide the phone screen as a reference to display a dynamic window 1402 with a height of 2 grids on the phone screen.

[0213] Similarly, combined FIG. 15 ,like FIG. 15 As shown in (a), for a landscape-style dynamic window, system developers or application developers can set the width of the dynamic window to 3 grids. Based on the aspect ratio of 16:10 for the landscape dynamic window, the phone can use the 8 grids that divide the phone screen as a reference to display a dynamic window 1501 with a width of 3 grids. For a portrait-style dynamic window, system developers or application developers can set the height of the dynamic window to 3 grids. Based on the aspect ratio of 10:16 for the portrait dynamic window, the phone can use the 8 grids that divide the phone screen as a reference to display a dynamic window 1502 with a height of 3 grids.

[0214] Combination FIG. 16 ,like FIG. 16As shown in (a) in FIG. 16, for a horizontal version of the dynamic widget, the system developer or the application developer can set the width of the dynamic widget to be 3 grids, and according to the width-to-height ratio of 16:10 of the horizontal version of the dynamic widget, the mobile phone can display the dynamic widget 1601 with a width of 3 grids on the mobile phone display screen, which is divided into 12 grids.

[0215] In addition, in the present embodiment, the display position of the dynamic widget on the display screen can be any position on the display screen. As an example, the display position of the dynamic widget can be predefined (or set by the system). For example, as shown in FIG. 17, the display position of the dynamic widget can be predefined to be a position that is a predetermined distance 1 from the right edge of the display screen and a predetermined distance 2 from the top edge of the display screen. The predetermined distance 1 and the predetermined distance 2 can also be predefined, such as the predetermined distance 1 being Nth of the width of the mobile phone display screen and the predetermined distance 2 being Mth of the length of the mobile phone display screen. In this way, according to the predefined display position and size, the mobile phone can display the dynamic widget 1701 on the mobile phone display screen. As shown in the display effect of FIG. 17, that is, the dynamic widget 1701 can automatically adhere to the edge of the mobile phone display screen. FIG. 17 FIG. 17

[0216] ​​In the above description, for the dynamic small window of horizontal version and the dynamic small window of vertical version, the mobile phone can automatically recommend whether to display the dynamic small window of horizontal version or the dynamic small window of vertical version according to the size of the region formed by all the small window elements after the layout is completed. For example, if the size (such as the width-height ratio) of the region formed by all the small window elements after the layout is completed is greater than or equal to 1:1, the mobile phone can recommend the dynamic small window of horizontal version to display the small window elements after the layout is completed. If the size (such as the width-height ratio) of the region formed by all the small window elements after the layout is completed is less than 1:1, the mobile phone can recommend the dynamic small window of vertical version to display the small window elements after the layout is completed. Taking the case that the small window elements only include video elements as an example, if the size (such as the width-height ratio) of the video element is greater than or equal to 1:1, the mobile phone can recommend the dynamic small window of horizontal version to display the video element. If the size (such as the width-height ratio) of the video element is less than 1:1, the mobile phone can recommend the dynamic small window of vertical version to display the video element. In addition, for the case that the small window elements are video elements, considering that the size of the video in the video element is mostly 16:9 or 16:10, but there are also some videos of other sizes, in order to keep the size of the dynamic small window uniform, the video can be partially cropped to ensure that the video played in the dynamic small window has no black border. For example, if the size (such as the width-height ratio) of the video is greater than or equal to 1:1 and less than or equal to 16:10, the width of the video can be made consistent with the width of the dynamic small window, and the video can be cropped up and down. If the size (such as the width-height ratio) of the video is greater than 16:10, the height of the video can be made consistent with the height of the dynamic small window, and the video can be cropped left and right. If the size (such as the width-height ratio) of the video is greater than or equal to 10:16 and less than 1:1, the height of the video can be made consistent with the height of the dynamic small window, and the video can be cropped left and right. If the size (such as the width-height ratio) of the video is less than 10:16, the width of the video can be made consistent with the width of the dynamic small window, and the video can be cropped up and down.

[0217] It should be noted that the dynamic small window of horizontal version in the above example can refer to the dynamic small window with a large width-height ratio, and the dynamic small window of vertical version can refer to the dynamic small window with a small width-height ratio. In addition, in this embodiment, the width-height ratio of the dynamic small window of horizontal version is taken as 16:10 as an example for description, and the width-height ratio of the dynamic small window of horizontal version can also be other ratios, such as 16:9, 4:3, etc. Similarly, the width-height ratio of the dynamic small window of vertical version can also be other ratios, such as 9:16, 3:4, etc. In this embodiment, the width-height ratio of the dynamic small window of horizontal version and the dynamic small window of vertical version is not specifically limited.

[0218] The above S702-S703 are exemplarily described below in combination with the examples shown in FIG. 6 , and FIG. 9-FIG. 11 .

[0219] For example, in combination with FIG. 6 and FIG. 9In the illustrated example, the video element in the application 1 is predefined as a live window element by the developer of the application 1, the corresponding configuration file corresponding to the package name of the application 1 is stored in the mobile phone, and the configuration of the drawing area of the video element is predefined. The corresponding layout file is also stored in the mobile phone corresponding to the package name of the application 1. For example, as shown in FIG. 8A, the application 1 is opened by the user, and the mobile phone starts the application 1 and displays the application window of the application 1 on the display screen. FIG. 18 As shown in FIG. 8B, the user drags the application window of the application 1, and the mobile phone application layer launcher performs drag listening to determine whether the application window is dragged to a specified area. When it is determined that the application window is dragged to the specified area, the dynamic live window function of the mobile phone is triggered, that is, the following process is performed. FIG. 9 As shown in FIG. 8C, the user presses the application window thumbnail 904 of the application 1 in the multitasking interface and moves the finger to trigger the live window drag service. During the dragging of the application window, the launcher of the mobile phone application layer performs drag listening to determine whether the application window is dragged to a specified area. When it is determined that the application window is dragged to the specified area, the dynamic live window function of the mobile phone is triggered, that is, the following process is performed.

[0220] The launcher of the mobile phone obtains the live window data and sends the live window data to the drag service module of the mobile phone application layer. For example, the launcher sends the live window data to the drag service module in a drag event (DragEvent). The live window data includes the identifier (such as the package name) of the application 1, the object type (specifically, livewindow), and the interface of the application in the application window (such as the application window thumbnail 904 in FIG. 8B). FIG. 9

[0221] The drag service module of the mobile phone determines, according to the object type (livewindow) in the live window data, that the user operation of dragging the application window is used to trigger the display of the dynamic live window. Then, the drag service module of the mobile phone sends the live window data to the dynamic live window controller of the mobile phone application layer to make it perform the processing logic of the dynamic live window service.

[0222] For example, the dynamic live window controller of the mobile phone can find the configuration file corresponding to the application 1 according to the package name of the application 1 included in the live window data. The configuration file includes the identifier of the element in the application 1 that needs to be displayed in the dynamic live window, such as the identifier of the video element. The dynamic live window controller of the mobile phone can also find the layout file corresponding to the application 1 according to the package name of the application 1 included in the live window data. The layout file includes the identifier and position of the video element.

[0223] ​The dynamic widget controller of the mobile phone can also start a virtual screen and pass the ID of the virtual screen and the package name of the application 1 in the widget data to the window manager of the framework layer of the mobile phone. According to the ID of the virtual screen and the package name of the application 1, the window manager of the mobile phone can move the application window of the application 1 indicated by the package name 1 to draw on the virtual screen. The dynamic widget controller of the mobile phone can also generate a shadow and add the shadow to the home screen of the mobile phone. The shadow is generated according to the interface of the application in the widget data, such as the application window thumbnail 904 in FIG. 9 .

[0224] After that, according to the identification of the video element included in the configuration file found, the dynamic widget controller of the mobile phone can extract the widget element, such as the video element 902 in FIG. 9 , from the application window drawn on the virtual screen. For example, according to the identification of the video element, the dynamic widget controller of the mobile phone can determine the layer name and display name of the video element 902 in the application window. According to the layer name and display name, the dynamic widget controller of the mobile phone can extract the video element 902 from the application window drawn on the virtual screen. After the widget element, such as the video element 902, is extracted, the dynamic widget controller of the mobile phone can re-arrange the extracted widget element according to the layout file found.

[0225] After the arrangement is completed, the dynamic widget controller of the mobile phone maps the re-arranged widget element to the shadow of the home screen. In this way, after the user stops dragging the application window, such as releasing the finger in the example shown in FIG. 9 (c), the mobile phone can display the desktop 1901 and display the dynamic widget 1902 on the desktop 1901, as shown in FIG. 19 (a). For example, the dynamic widget 1902 includes a video element. In the video element, the video in the video element 902 shown in FIG. 9 (a) can continue to be played for the user to continue to view. After that, the user switches the sub-screen in the desktop or opens other applications in the mobile phone. The dynamic widget 1902 can continue to be displayed on the display screen of the mobile phone. The sub-screen refers to the page divided by the desktop.

[0226] It should be noted that the examples shown in FIG. 9 and FIG. 18-FIG. 19 are used to illustrate that the video in the information detail page is displayed in the form of a dynamic widget on the display screen of the mobile phone. It can be understood that the information detail page is a hypertext markup language (HTML) web page. That is, for the HTML web page (such as the information in the public number , today The video in the information (such as news articles) can be displayed in a dynamic window on the phone by the user performing the user operation described in S701. The video source in the dynamic window can be said to originate from an HTML webpage. In this embodiment, the video source in the dynamic window can also be other sources, such as a surface view, for example... SurfaceView in third-party applications (such as FIG. 10B (as shown in the example), or a texture view, such as... This includes third-party applications such as `textureView`. In other words, any interface containing video elements (e.g., `surfaceView`, `textureView`, etc.) can extract the video element from the corresponding interface using the method of this embodiment, as long as the user performs an operation that triggers the display of a dynamic pop-up window, allowing the video within the video element to continue playing in the dynamic pop-up window. Its specific implementation is the same as described above. FIG. 18 The implementation in the example shown is similar, and will not be elaborated upon here. FIG. 18 In the illustrated embodiment, the small window element can be system-recommended, and the layout of the small window element can also be system-recommended. This embodiment does not impose any specific restrictions here.

[0227] In scenarios where a user drags an application window to trigger the display of a dynamic pop-up window, this embodiment provides a dynamic pop-up window display animation. For example, combined with... FIG. 20A ,like FIG. 20A As shown in (a), the user presses application window 2001 and moves their finger. As the user's finger moves, application window 2001 can flip inwards (or outwards) from the phone screen and update its display on the phone screen. The updated application window is as follows: FIG. 20A In (b) of the text, 2002, and FIG. 20A As shown in (c) 2003. And as the user moves their finger, the application window's opacity gradually changes from 0 to 100%, that is, from opaque to transparent. For example, application window 2001 has an opacity of 0, and as the user moves their finger, the opacity gradually increases until the updated application window's opacity reaches 100%. This gives the user the visual effect that application window 2001 is rotating and shrinking until it disappears. Additionally, as described in the above embodiments, the phone maps the shadow to the main screen so that the shadow is displayed on the phone's screen. In this example, the shadow can be the area containing the cropped application window's small window elements (such as...). FIG. 9picture of the region where the video element is located. In combination with the above-mentioned dynamic effect of the application window, as the user's finger moves, the transparency of the shadow displayed on the phone display screen gradually changes from 100 to 0, i.e., from transparent to opaque, to give the user a visual effect of the shadow gradually appearing and becoming clear. In combination with the above two dynamic effects, after the transparency of the application window is 100 and the transparency of the shadow is 0, the display effect can be as shown in FIG. 20A (d) of FIG. 20, the phone displays the shadow 2004. Since the content of the final displayed dynamic small window is the same as that of the shadow 2004, the user can be given an effect of the application window gradually changing to the dynamic small window with the above-mentioned dynamic effect. Finally, after the user releases the finger, as shown in FIG. 20A (e) of FIG. 20, the phone can display the dynamic small window 2005 on the phone display screen. The above example is described by taking the flipping of the application window as an example. The application window can also be cropped as the user's finger moves, such as cropping from the lower edge of the application window to the upper edge, or cropping the region where the small window element is located. In this way, in combination with the change in transparency and the change in transparency of the shadow, the user can also be presented with a dynamic effect of the application window gradually changing to the dynamic small window. In addition, after the effect shown in FIG. 20A (d) of FIG. 20 is presented, if the user does not release the finger but slides the finger towards the lower edge of the display screen, the application window can be displayed full screen again. Of course, the content of the shadow can also be different from that of the dynamic small window.

[0228] For example, in combination with FIG. 20B the application window can be applied to the fading-out effect and the dynamic small window can be applied to the fading-in effect, to gradually switch from the application window to the dynamic small window. As shown in FIG. 20B (a) of FIG. 21, the user presses the application window 2006 and moves the finger. As the user's finger moves, the transparency of the application window 2006 gradually changes from 0 to 100, i.e., from opaque to transparent. As shown in FIG. 20B (a) of FIG. 21, the transparency of the application window 2006 is 0, and as the user's finger moves, the transparency of the application window 2006 increases, such as the application window 2006 changing to FIG. 20B (b) of FIG. 21, until the transparency is 100. In addition, the shadow mapped to the home screen by the phone gradually changes from 100 to 0, i.e., from transparent to opaque, as the user's finger moves. As shown in FIG. 20B (c) of FIG. 21, the shadow 2008 displayed by the phone. As the user's finger continues to move, the transparency of the shadow changes to 0, such as the phone displaying FIG. 20Bthe shadow 2009 shown in (d) in FIG. 20. With the cooperation of the two dynamic effects, the application window fades out and the dynamic small window fades in, which gives the user the effect that the application window gradually changes into the dynamic small window with the above dynamic effect. Finally, after the user releases the finger, the phone displays the dynamic small window 2010 on the display screen, as shown in (e) in FIG. 20. This dynamic effect is visually simple. FIG. 20B

[0229] For example, for a navigation application, the small window element can be recommended by the system, and the layout of the small window element can also be recommended by the system. For example, as shown in the examples in FIGS. 21 and 22, the recommended model of the navigation application is stored in the phone in correspondence with the application type, and the layout file is also stored in the phone in correspondence with the application type. After the user opens the navigation application, the phone starts the navigation application and displays the application window of the navigation application on the display screen. Then, the user can use the navigation application for navigation. During the navigation with the navigation application, if the phone receives a notification message, after the user clicks the notification message, the dynamic small window function of the phone is triggered, that is, the following process is performed: FIG. 6 FIG. 10A The navigation application of the phone obtains the small window data and sends the small window data to the drag service module of the application layer of the phone. The small window data includes the identifier (such as the package name) of the navigation application, the object type (specifically, livewindow), and the interface of the application in the application window (such as the screenshot of the application window 1001 in FIG. 23).

[0230] The drag service module of the phone determines, according to the object type (livewindow) in the small window data, that the user operation of clicking the notification message is used to trigger the display of the dynamic small window. Then, the drag service module of the phone sends the small window data to the dynamic small window controller of the application layer of the phone, so that the dynamic small window controller performs the processing logic of the dynamic small window service. FIG. 10A For example, the dynamic small window controller of the phone can determine, according to the package name of the navigation application included in the small window data, that the application type of the application is navigation, and based on this, the recommended model corresponding to the navigation application can be found. The recommended model is used to identify the elements in the navigation application, such as the navigation direction, distance, and road indication as the small window element. The dynamic small window controller of the phone can also find the layout file corresponding to the navigation application according to the determined application type. The layout file includes the layout configuration of the small window element of the navigation application.

[0231]

[0232]

[0233] ​​​​The phone's dynamic window controller can also launch a virtual screen and pass the virtual screen's ID and the navigation application's package name from the window data to the phone's frame layer's window manager. Based on the virtual screen's ID and the navigation application's package name, the phone's window manager can move the navigation application's window onto the virtual screen for rendering. The phone's dynamic window controller can also generate a window shadow and add it to the phone's home screen. This shadow is based on the application's interface from the window data, such as... FIG. 10A The screenshot was generated from application window 1001.

[0234] Then, based on the recommended model, the phone's dynamic pop-up controller can extract pop-up elements from the application window drawn on the virtual screen. For example, if the pop-up element is... FIG. 10A The navigation direction is 1003, the distance is 1004, and the road indication is 1005. After extracting the navigation direction 1003, the distance 1004, and the road indication 1005, the phone's dynamic window controller can rearrange the extracted window elements according to the found layout file.

[0235] After the layout is complete, the phone's dynamic pop-up controller maps the rearranged navigation direction, distance, and road signs onto the shadow of the main screen. Additionally, it's understandable that when a user clicks on a notification, the phone can also display the notification's details in response to that action. Thus, when a user clicks on a notification, such as in... FIG. 10A In example (b) shown in the text, after releasing the finger, as... FIG. 21A As shown in (a), the phone can display a details screen 2101 corresponding to the notification message, and display a dynamic pop-up 2102 on the details screen 2101. For example, the dynamic pop-up 2102 includes navigation direction, distance, and road instructions, allowing the user to continue viewing navigation information. Afterwards, when the user switches to the desktop and opens other applications on the phone, the dynamic pop-up 2102 can continue to float on the phone's screen. It can be seen that during navigation, if the navigation application window moves from the foreground to the background, key elements of the navigation application window can be displayed on the phone's screen as dynamic pop-ups, allowing the user to continue viewing navigation information.

[0236] It should be noted that for a navigation application, the widget element displayed in the dynamic widget can include the navigation direction, distance and road indication described above. In some other embodiments, the dynamic widget can not include these elements, or include one or more of the navigation direction, distance and road indication, and can also include other elements of the navigation application, such as a "navigation end" button, etc. The present embodiment does not make specific limitations here. In addition, the above embodiments are described taking the case that the widget element of the navigation application is system recommended. In some other embodiments, the widget element of the navigation application can also be defined by the application developer, such as taking the case of calling the extraction of the DUP capability provided by the system to implement the widget element. The mobile phone is pre-configured with a corresponding DUP configuration file (which includes the DUP ID of the widget element), and the dynamic widget controller of the mobile phone can extract the element of the specified DUP ID from the application window drawn by the virtual screen according to the pre-configured DUP configuration file. Then, after the extracted element is re-laid out according to the layout file, it is mapped to the shadow of the main screen to realize the display of the specified widget element in the dynamic widget. Similarly, in combination with FIG. 10B As shown in FIG. 21B , after the mobile phone receives the user's click operation on the notification message, the mobile phone can display the detail interface 2101' corresponding to the notification message, and display the dynamic widget 2102' on the detail interface 2101'. As shown, the dynamic widget 2102' includes a video element. In the video element, the video in the video element 1003' in (a) can continue to be played for the user to continue to view. After that, the user switches to the desktop and opens other applications in the mobile phone, and the dynamic widget 2102' can continue to be displayed on the display screen of the mobile phone. FIG. 10B

[0237] For example, for instant messaging, note, information and other list application interfaces, the widget element can be system recommended. Among them, the widget element can be the last N messages (such as two, three) or information. As an example, the last N messages (or information) can be identified according to the time of the message (or information), such as the N messages closest to the current time as the last N messages. The last N messages (or information) can also be identified according to the display position of the message (or information) in the interface, such as the N messages from the bottom of the interface as the last N messages. The layout of the widget element can also be system recommended. For example, in combination with FIG. 6 and FIG. 11 ​In the shown example, after the user opens the instant messaging application, the phone can start the instant messaging application, and display an application window of the instant messaging application on the display screen, such as the application window including a chat detail page including three messages. The user can perform an operation of switching the instant messaging application to the background, such as performing a sliding operation from the lower edge of the display screen of the phone to the upper edge of the display screen of the phone. After receiving the operation of switching the application to the background, the phone can trigger the dynamic window function of the phone. The implementation can refer to the implementation of displaying the dynamic window corresponding to the navigation application. In this way, in response to the operation of the user, the dynamic window controller of the phone can extract the window elements, such as the last two messages in the chat detail page, and display the window elements in the form of a dynamic window after being rearranged on the display screen of the phone. For example, in the shown example, the user performs a sliding operation from the lower edge of the display screen to the upper edge of the display screen, and after the finger is removed from the display screen of the phone, the phone can display the desktop 2201, and display the dynamic window 2202 on the desktop 2201. For example, the dynamic window 2202 includes the last two messages in the chat detail page, for the user to continue to view. After that, the user switches the sub-screen in the desktop, or opens other applications in the phone, and the dynamic window 2202 can continue to be displayed in a suspended manner on the display screen of the phone. FIG. 11 In the shown example, the user performs a sliding operation from the lower edge of the display screen to the upper edge of the display screen, and after the finger is removed from the display screen of the phone, the phone can display the desktop 2201, and display the dynamic window 2202 on the desktop 2201. For example, the dynamic window 2202 includes the last two messages in the chat detail page, for the user to continue to view. After that, the user switches the sub-screen in the desktop, or opens other applications in the phone, and the dynamic window 2202 can continue to be displayed in a suspended manner on the display screen of the phone. FIG. 22 In the shown example, the user performs a sliding operation from the lower edge of the display screen to the upper edge of the display screen, and after the finger is removed from the display screen of the phone, the phone can display the desktop 2201, and display the dynamic window 2202 on the desktop 2201. For example, the dynamic window 2202 includes the last two messages in the chat detail page, for the user to continue to view. After that, the user switches the sub-screen in the desktop, or opens other applications in the phone, and the dynamic window 2202 can continue to be displayed in a suspended manner on the display screen of the phone.

[0238] After the phone displays the dynamic window on the display screen of the phone, the method can further include the following: S704-S706.

[0239] S704, the phone receives a user operation on the dynamic window.

[0240] S705, the phone displays the dynamic window in the form of a window.

[0241] As described in the foregoing embodiments, after receiving the user operation in S701, the phone can display a dynamic window on the display screen of the phone, and the dynamic window is a window displayed in a suspended manner on the display screen. The dynamic window in the form of a window can be the first window in the embodiments of the present application. In the present embodiment, the dynamic window in the form of a window can be used by the user to continue to browse the key information in the application window that is not displayed on the display screen. For example, in combination with (a) in FIG. 22, the user can continue to browse the video in the information detail page. For another example, in combination with (a) in FIG. 23, the user can continue to browse the navigation information in the navigation application. For another example, in combination with FIG. 24, the user can continue to browse the video in the video detail page. For another example, in combination with (a) in FIG. 25, the user can continue to browse the messages in the instant messaging application. FIG. 19 FIG. 21A FIG. 21B FIG. 22

[0242] ​​​​In this embodiment, the dynamic small window in the form of a small window supports the following user operations. For example, the user operation in S704 can be operation 1 for triggering the dynamic small window to change from the form of a small window to the form of a medium window. The operation 1 can be the third operation in this embodiment. As an example, the operation 1 can be a touch gesture operation such as a single-click operation, a double-click operation, etc. on the dynamic small window in the form of a small window. That is, after the user performs the operation 1 on the dynamic small window in the form of a small window, the dynamic small window changes from the form of a small window to the form of a medium window and is displayed on the display screen. It should be noted that the dynamic small window in the form of a medium window is also displayed in suspension on the display screen and can continue to be displayed on the display screen of the mobile phone after the user switches pages or exits the application or opens another application. The dynamic small window in the form of a medium window can be the second window in this embodiment.

[0243] In some embodiments, the dynamic small window in the form of a medium window can be extracted from the corresponding application window by the mobile phone, and then displayed on the display screen of the mobile phone after being rearranged. In some embodiments, the small window elements and the arrangement manner in the dynamic small window in the form of a medium window can be defined by the system or the developer of the application. The configuration file or the recommended model for extracting the small window elements and the layout file for rearranging the small window elements can also be stored in the mobile phone in advance. The specific implementation is similar to that of the dynamic small window in the form of a small window, and will not be described here.

[0244] For example, in combination with FIG. 19 , the operation 1 is a click operation on the dynamic small window in the form of a small window, the small window elements and the arrangement manner in the dynamic small window in the form of a medium window are defined by the developer of the application, the corresponding configuration file and the layout file are stored in the mobile phone, and the developer of the application defines the video element, the play / pause button and the progress bar in the application as the small window elements in the dynamic small window in the form of a medium window. For example FIG. 19As shown in (a), the phone displays a dynamic small window 1902 on the desktop 1901. The phone receives a click operation from the user on the dynamic small window 1902. In response to this click operation, the phone searches for the configuration file and layout file corresponding to the dynamic small window in the application. The configuration file includes identifiers of the elements that the application needs to display in the dynamic small window, such as the identifiers of video elements, play / pause buttons, and progress bars. The layout file includes the identifiers and positions of video elements, the positions of play / pause buttons, and the positions of progress bars, etc. Based on the found configuration file, the phone extracts the small window elements that need to be displayed in the dynamic small window from the application window drawn on the virtual screen, such as video elements, play / pause buttons, and progress bars. Then, based on the found layout file, the phone re-layouts the video elements, play / pause buttons, and progress bars. After the layout is completed, the phone maps the re-layout small window elements onto the shadow of the main screen. Thus, as shown... FIG. 19 As shown in (b), the mobile phone can display a dynamic window 1903 in the form of a medium window on the desktop 1901. The dynamic window 1903 in the form of a medium window includes a video component 1904, a play / pause button 1905, and a progress bar 1906.

[0245] Similarly, combined FIG. 21A ,like FIG. 21A As shown in (a), the phone displays a dynamic small window 2102 on the details screen 2101 corresponding to the notification message. The phone receives the user's operation 1 on the dynamic small window 2102, such as clicking the operation, and can find the configuration file and layout file corresponding to the dynamic small window in the application. Then, the phone extracts the small window elements to be displayed in the dynamic small window according to the configuration file, rearranges them, and maps them to the shadow of the main screen. Thus, as shown... FIG. 21A As shown in (b), the mobile phone can display a dynamic small window 2103 in the form of a medium window on the details screen 2101 corresponding to the notification message. This dynamic small window 2103 includes navigation direction, distance, road instructions, and an end navigation button. Combined with... FIG. 22 ,like FIG. 22 As shown in (a), the mobile phone displays a dynamic small window 2202 on the desktop 2201. The mobile phone receives the user's operation 1 on the dynamic small window 2202, such as clicking the operation, as shown in (a). FIG. 22 As shown in (b), the mobile phone can display a dynamic window 2203 in the form of a medium window on the desktop 2201. This dynamic window 2203 in the form of a medium window includes the two most recent messages in the chat details page, a voice button, and an input box 2204.

[0246] It should be noted that similar to the description of the layout file in the corresponding description of the dynamic small window in the form of a small window, the same application (or the same interface of the application, or the same type of application) can have one or more layout files corresponding to the dynamic small window in the form of a medium window. Similarly, the dynamic small window in the form of a medium window can also have one or more configuration files (or recommendation models). It can be understood that the mobile phone can extract different small window elements displayed in the dynamic small window in the form of a medium window for different configuration files (or recommendation models). For the same small window element, the mobile phone displays the display effect after rearrangement based on different layout files.

[0247] For example, in combination with FIG. 23 In a certain shopping application, the configuration file corresponding to the dynamic small window in the form of a medium window includes configuration file a1 and configuration file a2, and the corresponding layout files are layout file b1 and layout file b2. Among them, the configuration file a1 includes the identification of the product preview, the identification of the product price and the identification of the product introduction. The configuration file a2 includes the identification of the product preview, the identification of the product price, the identification of the product introduction, the identification of the shopping cart button and the identification of the immediate purchase. As shown in (a) of FIG. 23 According to the configuration file a1 and the layout file b1, the mobile phone can display the dynamic small window 2301 in the form of a medium window. As shown in (b) of FIG. 23 According to the configuration file a2 and the layout file b2, the mobile phone can display the dynamic small window 2302 in the form of a medium window. For example, for the same small window element, such as including product preview, product price, product introduction, shopping cart button and immediate purchase button. If the mobile phone includes two different layout files, such as layout file b2 and layout file b3, then as shown in (c) of FIG. 23 According to the layout file b3, the mobile phone can display the dynamic small window 2303 in the form of a medium window. As can be seen, it is different from the layout of the dynamic small window 2302 shown in (b) of FIG. 23 For example, in combination with FIG. 24A In a certain video application, the configuration file corresponding to the dynamic small window in the form of a medium window has two as an example. As shown in (a) of FIG. 24A According to one configuration file and the corresponding layout file, the mobile phone can display the dynamic small window 2401 in the form of a medium window. As shown in (c) of FIG. 24A According to another configuration file and the corresponding layout file, the mobile phone can display the dynamic small window 2403 in the form of a medium window. For example, for the same small window element, the mobile phone includes two different layout files, then the mobile phone can display the dynamic small window in the form of a medium window as shown in (a) of FIG. 24A 2401, as shown in FIG. 24AAs shown in (b) of the diagram, the layout of the dynamic window 2402 is different from that of the dynamic window 2401.

[0248] It should be noted that when there are multiple layout files for dynamic small windows in the form of medium-sized windows for the same application (or the same interface of an application, or an application of the same type), the mobile phone can select any one of these layout files to rearrange the extracted small window elements. Alternatively, the system developers can provide multiple layout files, and the application developers can select one from these files. In this way, the mobile phone can select the corresponding layout file from the multiple layout files according to the application developer's specification to rearrange the extracted small window elements. Similarly, when there are multiple configuration files (or recommended models) for dynamic small windows in the form of medium-sized windows, the mobile phone can select any one of the multiple configuration files (or recommended models), or select the corresponding configuration file (or recommended model) according to the application developer's specification, for the extraction of small window elements.

[0249] In addition, in some embodiments, the dynamic mini-window in the form of a medium window may include a close button and a zoom button in addition to the mini-window element. The close button is used to close the dynamic mini-window, and the zoom button is used to enlarge the dynamic mini-window, that is, to display the application window in a full-screen format. For example, combined with... FIG. 19 ,like FIG. 19 As shown in (b), the dynamic mini-window 1903 in the form of a window may include a close button 1908 and a zoom button 1907 in addition to the mini-window element. When the phone receives a user's operation on the close button 1908, such as clicking the button, the phone can close the dynamic mini-window 1903 and only display the desktop 1901. When the phone receives a user's operation on the zoom button 1907, such as clicking the button, the phone can display the application window of the corresponding application, such as... FIG. 9 The application window 901 shown in (a) can also include a motion button. A user can drag the dynamic window by pressing and moving their finger at the motion button. For example, combined with... FIG. 19 ,like FIG. 19 As shown in (b), the dynamic window 1903 in the form of a medium window may also include a movement button 1909. After the mobile phone receives the user's operation of pressing the movement button 1909 and moving their finger, the mobile phone moves the dynamic window 1903 on the mobile phone display screen.

[0250] In some embodiments, after a user performs the above operation 1 on a small window dynamic window, causing the phone to display a medium window dynamic window on the screen, if the user does not operate the phone for X seconds (e.g., 3 seconds), the phone can automatically switch the display of the medium window dynamic window to a small window dynamic window. For example, combined withFIG. 19 ,like FIG. 19 As shown in (b), after the mobile phone displays a dynamic small window 1903 in the form of a window, if the user does not operate the mobile phone for 3 seconds, the mobile phone can display as shown in (b). FIG. 19 The dynamic window 1902 in the form of a small window is shown in (a) above. Alternatively, after the mobile phone displays a dynamic window in the form of a medium window on the screen, if it receives an operation from the user on a blank area of ​​the mobile phone screen, i.e., an area where no interface elements are displayed, such as a click operation, the mobile phone can also switch the display of the dynamic window in the form of a medium window to a dynamic window in the form of a small window. Alternatively, after the mobile phone displays a dynamic window in the form of a medium window on the screen, if it receives an operation from the user on the edge area of ​​the dynamic window in the form of a medium window (where there are no operable elements, such as...), the dynamic window 1902 in the form of a small window. FIG. 19 For operations (the area within the dashed box shown in (b)), such as click or double-click, the mobile phone can also switch the dynamic window in the form of a central window to a smaller dynamic window.

[0251] In addition, in conjunction with the above FIG. 14-FIG. 16 As described above, in this embodiment, the size of a dynamic window in the form of a small window can be set based on the grid division of the display screen. Similarly, the size of a dynamic window in the form of a medium window can also be set based on the grid division of the display screen. This can be set by the system developer or application developer. For example, continuing to combine... FIG. 14-FIG. 16 Taking a horizontal dynamic window with a width-to-height ratio of 16:10 and a vertical dynamic window with a width-to-height ratio of 10:16 as an example... FIG. 14-FIG. 16 The images show the display effects of a dynamic small window in landscape and portrait modes when the phone's screen is vertically divided into 4, 8, and 12 grids, respectively.

[0252] As can be seen, combined FIG. 14 ,like FIG. 14 As shown in (b), for a horizontal dynamic window in the form of a medium window, system developers or application developers can set the width of the dynamic window in the form of a medium window to 3.5 grids. Based on the aspect ratio of 16:10 for the horizontal dynamic window, the mobile phone can use the 4 grids that divide the mobile phone display as a reference to display a dynamic window 1403 with a width of 3.5 grids in the form of a medium window on the mobile phone display. For a vertical dynamic window in the form of a medium window, system developers or application developers can set the height of the dynamic window in the form of a medium window to 3.5 grids. Based on the aspect ratio of 10:16 for the vertical dynamic window, the mobile phone can use the 4 grids that divide the mobile phone display as a reference to display a dynamic window 1404 with a height of 3.5 grids in the form of a medium window on the mobile phone display.

[0253] Similarly, combined FIG. 15 ,like FIG. 15As shown in (b), for a landscape-style dynamic window in the form of a medium window, system developers or application developers can set the width of the medium window to 5 grids. Based on the aspect ratio of 16:10 for the landscape dynamic window, the phone can use the 8 grids that divide the phone screen as a reference to display a medium window 1503 with a width of 5 grids. For a portrait-style dynamic window in the form of a medium window, system developers or application developers can set the height of the medium window to 5 grids. Based on the aspect ratio of 10:16 for the portrait dynamic window, the phone can use the 8 grids that divide the phone screen as a reference to display a medium window 1504 with a height of 5 grids.

[0254] Combination FIG. 16 ,like FIG. 16 As shown in (b), for a horizontal dynamic window in the form of a medium window, system developers or application developers can set the width of the dynamic window to 5 grids. Based on the aspect ratio of 16:10 for the horizontal dynamic window, the mobile phone can use the 12 grids divided on the mobile phone screen as a reference to display a dynamic window 1603 with a width of 5 grids. For a vertical dynamic window in the form of a medium window, system developers or application developers can set the height of the dynamic window to 5 grids. Based on the aspect ratio of 10:16 for the vertical dynamic window, the mobile phone can use the 12 grids divided on the mobile phone screen as a reference to display a dynamic window 1604 with a height of 3 grids.

[0255] Furthermore, in this embodiment, the display position of the dynamic window in the form of a medium window on the display screen can be any position on the display screen. As an example, the display position of the dynamic window in the form of a medium window can be predefined. For example, the display position of the dynamic window in the form of a medium window can be predefined as a predetermined distance 3 from the right edge of the display screen and a predetermined distance 4 from the top edge of the display screen. The predetermined distances 3 and 4 can also be predefined. In this way, according to the predefined display position and size, the mobile phone can display the dynamic window in the form of a medium window on the mobile phone display screen. If the dynamic window in the form of a medium window automatically snaps to the edge of the mobile phone display screen according to the predetermined display position, similar to... FIG. 17 The display effect of the dynamic small window 1701 in the form of a small to medium window.

[0256] As described in the above embodiments, a dynamic small window in the form of a medium window may include elements that can be interacted with by the user. For example, FIG. 19 The play / pause button 1905 and the progress bar 1906 are shown in (b) above. For example, FIG. 21A The end navigation button shown in (b) above. For example, FIG. 22the voice button and the input box 2204 shown in (b) of FIG. 22. In the embodiment, the user can operate the operable element in the dynamic widget in the form of the middle window, and the mobile phone can respond accordingly according to the user's operation.

[0257] As an example, the specific implementation that the mobile phone responds accordingly according to the user's operation on the element in the dynamic widget in the form of the middle window can be as follows: after receiving the corresponding user operation, such as the operation 1 described above, the mobile phone extracts the widget element to be displayed in the dynamic widget in the form of the middle window from the application window on the virtual screen and performs the re-layout, and then records the correspondence between the layout position of the widget element in the dynamic widget in the form of the middle window and the position of the corresponding element in the original application window. In this way, after receiving the user's operation on a certain widget element in the dynamic widget in the form of the middle window, the mobile phone can determine the corresponding position of the widget element in the original application window according to the recorded correspondence, and inject the user's operation into the element at the position in the original application window. Then, the mobile phone can respond accordingly. In addition, the mobile phone can also update the state of the corresponding widget element in the dynamic widget in the form of the middle window according to the result of the response.

[0258] For example, continuing to combine FIG. 19 the correspondence between the layout position of the play / pause button 1905 in the dynamic widget and the position of the corresponding play / pause button in the original application window is recorded after the play / pause button 1905 is extracted from the application window on the virtual screen and re-laid out. As shown in (b) of FIG. 19, FIG. 19 As shown in (b) of FIG. 22, the mobile phone receives the user's operation on the input box 2204, such as a click operation. According to the recorded correspondence, the mobile phone determines the corresponding position of the input box 2204 in the original application window, and injects the user's click operation into the element at the position, that is, the input box of the application window. In this way, as shown in (c) of FIG. 22, FIG. 22 For example, continuing to combine FIG. 22 the correspondence between the layout position of the input box 2204 in the dynamic widget and the position of the corresponding input box in the original application window is recorded after the input box 2204 is extracted from the application window on the virtual screen and re-laid out. As shown in (b) of FIG. 22, FIG. 22As shown in (c) of FIG. 22, the mobile phone can display the input method interface 2205 on the display screen of the mobile phone. The mobile phone can also update the state of the input box in the dynamic mini-window in the form of a medium window, such as displaying a cursor in the input box. Then, the user can perform input in the dynamic mini-window in the form of a medium window by performing operations in the input method interface 2205.

[0259] The above examples are described by taking the operation on the operable element in the dynamic mini-window in the form of a medium window as an example to illustrate the corresponding control. In some other embodiments, for the scenario of playing a video in the dynamic mini-window in the form of a medium window, the present embodiment can also support the corresponding gesture operation in the dynamic mini-window to realize the control on the played video. For example, the user slides a finger on the dynamic mini-window from bottom to top, and the mobile phone can increase the volume of the played video in the dynamic mini-window. The user slides a finger on the dynamic mini-window from top to bottom, and the mobile phone can decrease the volume of the played video in the dynamic mini-window. The user slides a finger on the dynamic mini-window from left to right, and the mobile phone can perform a fast-forward operation on the played video in the dynamic mini-window. The user slides a finger on the dynamic mini-window from right to left, and the mobile phone can perform a fast-rewind operation on the played video in the dynamic mini-window. Specifically, after receiving the corresponding gesture operation, the mobile phone can inject the gesture operation into the video element in the original application window, so that the mobile phone can perform a corresponding response according to the injected gesture operation, and update and display the response result in the dynamic mini-window in the form of a medium window.

[0260] In some embodiments, the above examples are described by taking the operation 1 on the dynamic mini-window in the form of a small window, and then the mobile phone changes the display of the dynamic mini-window in the form of a small window to the dynamic mini-window in the form of a medium window as an example. In some other embodiments, after receiving the operation 2 of the user on the dynamic mini-window in the form of a small window, the mobile phone can also display a close button and an enlarge button on the dynamic mini-window in the form of a small window. The close button is used to close the dynamic mini-window, and the enlarge button is used to enlarge the dynamic mini-window, that is, to display the application window in the form of a full-screen large window. It should be noted that the operation 2 is specifically an operation different from the operation 1, such as the operation 1 is a click operation, and the operation 2 can be a double-click operation. For example, the operation 1 is a double-click operation, and the operation 2 is a click operation. The present embodiment does not specifically limit the specific implementation form of the operation 1 and the operation 2.

[0261] It should be noted that the above embodiments are described taking the difference between the small window elements included in the dynamic small window in the middle window form and the dynamic small window in the small window form as an example. In other embodiments, the dynamic small window in the middle window form can also include the same small window elements as the dynamic small window in the small window form, and the difference lies in that the dynamic small window in the middle window form further includes one or more of the close button, the zoom-in button, and the moving button. In addition, in the scenario where the small window elements in the dynamic small window in the middle window form are the same as or different from the small window elements in the dynamic small window in the small window form, one or more of the close button, the zoom-in button, and the moving button can be displayed within a preset time after the user triggers the dynamic small window displayed in the small window form to be switched to the dynamic small window in the middle window form, and after the preset time, the buttons can be hidden, and only the corresponding small window elements are displayed in the dynamic small window in the middle window form.

[0262] For ease of understanding, the following describes the process of changing the dynamic small window in the small window form to the dynamic small window in the middle window form, taking the dynamic small window in the middle window form and the dynamic small window in the small window form as an example, and the small window elements in the dynamic small window in the middle window form being the same as the dynamic small window in the small window form. FIG. 24B and FIG. 24C For ease of understanding, the following describes the process of changing the dynamic small window in the small window form to the dynamic small window in the middle window form, taking the dynamic small window in the middle window form and the dynamic small window in the small window form as an example, and the small window elements in the dynamic small window in the middle window form being the same as the dynamic small window in the small window form.

[0263] Taking the dynamic small window in the middle window form and the dynamic small window in the small window form as an example, and the dynamic small window in the middle window form being the same as the dynamic small window in the small window form, the following describes the process of changing the dynamic small window in the small window form to the dynamic small window in the middle window form. FIG. 24B For example, the phone displays the dynamic small window in the middle window form in response to the click operation on the dynamic small window in the small window form. As shown in (a) of FIG. 7, the phone displays the desktop 01, and the desktop 01 displays the dynamic small window in the small window form 02. The phone receives the click operation of the user on the dynamic small window in the small window form. In response to the click operation, the phone displays the dynamic small window in the middle window form 03. FIG. 24B FIG. 24B ​As shown in (b) of FIG. 1, the mobile phone displays a dynamic widget 03 in the form of a medium window on the desktop 01. The dynamic widget 03 in the form of a medium window includes a close button 06, an enlarge button 04 and a move button 05. The dynamic widget 03 in the form of a medium window also includes an operation prompt 07 for prompting the user to perform upward, downward, leftward and rightward sliding operations on the dynamic widget 03 to operate the dynamic widget 03. For example, the user slides a finger upward on the dynamic widget 03, and the mobile phone can increase the volume of a video played in the dynamic widget 03; the user slides a finger downward on the dynamic widget 03, and the mobile phone can decrease the volume of the video played in the dynamic widget 03; the user slides a finger rightward on the dynamic widget 03, and the mobile phone can fast-forward the video played in the dynamic widget 03; and the user slides a finger leftward on the dynamic widget 03, and the mobile phone can fast-rewind the video played in the dynamic widget 03. The mobile phone can also display a prompt information 08 around the dynamic widget 03 in the form of a medium window, such as a colored (e.g., blue) border around the dynamic widget 03. Then, if the user does not perform any operation for a preset time, such as 3 seconds, the close button 06, the enlarge button 04 and the move button 05 on the dynamic widget 03 in the form of a medium window disappear and are no longer displayed, and the operation prompt 07 and the prompt information 08 are also no longer displayed, as shown in (c) of FIG. 1. FIG. 24B As shown in (c) of FIG. 1, the mobile phone plays only a video in the dynamic widget 03 in the form of a medium window. After the mobile phone plays only the video in the dynamic widget 03 in the form of a medium window, if the user performs a click operation on the dynamic widget 03 in the form of a medium window, the mobile phone can display the close button 06, the enlarge button 04 and the move button 05 on the dynamic widget 03 in the form of a medium window again, as shown in (d) of FIG. 1. FIG. 24B As shown in (d) of FIG. 1, the mobile phone can display the close button 06, the enlarge button 04 and the move button 05 on the dynamic widget 03 in the form of a medium window on the desktop 01 again, and can also display the prompt information 08 around the dynamic widget 03 in the form of a medium window again. After the mobile phone displays the dynamic widget 03 in the form of a medium window as shown in (d) of FIG. 1, if the user performs a click operation on the dynamic widget 03 in the form of a medium window, the mobile phone can play only a video in the dynamic widget 03 in the form of a medium window, as shown in (c) of FIG. 1. FIG. 24B In the case of the dynamic widget 03 in the form of a medium window as shown in (d) of FIG. 1, if no user operation is received within a preset time, such as 3 seconds, the mobile phone can play only a video in the dynamic widget 03 in the form of a medium window, as shown in (c) of FIG. 1. FIG. 24B As shown in (c) of FIG. 1. After the mobile phone displays the dynamic widget 03 in the form of a medium window as shown in (d) of FIG. 1, if the user performs a click operation on the dynamic widget 03 in the form of a medium window, the mobile phone can play only a video in the dynamic widget 03 in the form of a medium window, as shown in (c) of FIG. 1. FIG. 24B As shown in (d) of FIG. 1, if the mobile phone receives a user operation from the lower left corner, the lower right corner or the bottom edge of the dynamic widget 03 in the form of a medium window into the dynamic widget 03 (the operation can be the fourth operation in the embodiments of the present application), the mobile phone can display a dynamic widget 02 in the form of a small window, as shown in (a) of FIG. 1. FIG. 24C As shown in (a) of FIG. 1, the mobile phone can display the dynamic widget 02 in the form of a small window again. It should be noted that the dynamic widget 03 in the form of a medium window includes the operation prompt 07, which can be displayed only when the dynamic widget 03 in the form of a medium window is displayed for the first time, and the operation prompt 07 is not displayed when the dynamic widget 03 in the form of a medium window is displayed for the second time.

[0264] In combination with FIG. 24CTaking a dynamic small window displayed on a mobile phone as an example, which appears as a double-click window. FIG. 24C As shown in (a), the phone displays desktop 09, and on desktop 09, a dynamic small window 10 is displayed. The phone receives a double-click operation from the user on the dynamic small window. In response to this double-click operation, as follows... FIG. 24C As shown in (b), the mobile phone displays a dynamic window 11 in the form of a medium window on the desktop 09. This dynamic window 11 includes a close button 14, a zoom button 12, and a move button 13. The dynamic window 11 also includes an operation prompt 15, which instructs the user to perform up, down, left, and right swipe operations on the dynamic window 11 to control it. Afterwards, if the user does not perform any operation after a preset time, such as 3 seconds, the close button 14, zoom button 12, and move button 13 disappear from the dynamic window 11, and the operation prompt 15 also disappears. FIG. 24C As shown in (c), the mobile phone displays an operation prompt 16 on a dynamic small window 11 in the form of a window. This operation prompt 16 prompts the user to double-click the outer layer of the dynamic small window 11 to trigger the display of the dynamic small window, showing the area where the outer layer is located. The mobile phone displays... FIG. 24C After the dynamic small window 11 in the form of the middle window shown in (c) is executed, if the user does not perform any operation after a preset time, such as 3 seconds, then... FIG. 24C As shown in (d), the mobile phone plays only video in the dynamic window 11 in the middle window format. After the mobile phone plays only video in the dynamic window 11 in the middle window format, if the user clicks on the dynamic window 11 in the middle window format, then as shown in (d), the mobile phone plays only video in the dynamic window 11 in the middle window format. FIG. 24C As shown in (e), the phone can re-display the close button 14, zoom button 12, and move button 13 on a dynamic small window 11 in the form of a central window on desktop 09. (The last sentence appears to be incomplete and possibly refers to a different phone display.) FIG. 24C In the case of the dynamic window 11 shown in (e), if no user operation is received within a preset time, such as 3 seconds, only the video can be played in the dynamic window 11 in the form of a medium window. FIG. 24C As shown in (d) in the image. The phone displays as follows: FIG. 24C (e) or FIG. 24C In the case of the dynamic window 11 shown in (d), if the mobile phone receives a double-click operation from the user on the outer layer of the dynamic window 11 (this operation can be the fourth operation in the embodiments of this application), then... FIG. 17 As shown in (a), the mobile phone can redisplay the dynamic small window 10 in the form of a small window. It should be noted that the dynamic small window in the form of the above-mentioned small window includes operation prompts 15 and 16, which can be displayed only when the dynamic small window in the form of the small window is displayed for the first time, and not displayed when it is not displayed for the first time.

[0265] S706, the mobile phone receives the user operation of dragging the dynamic widget, and moves the dynamic widget.

[0266] After displaying the dynamic widget in the form of a small window or in the form of a medium window, after receiving the user operation of dragging the dynamic widget, the mobile phone can display an animation of moving the dynamic widget on the display screen of the mobile phone. The user operation of dragging the dynamic widget can be a touch gesture operation. For example, the touch gesture operation can be a pressing and moving operation on the dynamic widget. That is, the user presses the dynamic widget and moves the finger to drag the dynamic widget on the display screen of the mobile phone.

[0267] In some embodiments, after the user presses the dynamic widget and moves the finger to move the dynamic widget on the display screen, if the user releases the finger, the mobile phone can automatically adsorb the dynamic widget to the edge of the display screen according to the position of the dynamic widget on the display screen after the user releases the finger. For example, in combination with FIG. 17 Taking the dynamic widget in the form of a small window and the user operation of dragging the dynamic widget as a pressing and moving operation on the dynamic widget as an example, as shown in FIG. 17 After the user performs the user operation in S701, the mobile phone can display the dynamic widget 1701 at the upper right corner of the display screen of the mobile phone. After the mobile phone receives the pressing and moving operation of the user on the dynamic widget 1701, the mobile phone can display the moving animation of the dynamic widget on the display screen of the mobile phone. After the dynamic widget is dragged, if the user releases the finger within the range of the movable position 1 shown in FIG. 17 , the mobile phone can automatically adsorb and display the dynamic widget 1701 at the position shown by the movable position 1. Similarly, if the user releases the finger within the range of the movable position 2 shown in FIG. 17 , the mobile phone can automatically adsorb and display the dynamic widget 1701 at the position shown by the movable position 2. If the user releases the finger within the range of the movable position 3 shown in FIG. 19 , the mobile phone can automatically adsorb and display the dynamic widget 1701 at the position shown by the movable position 3. Similarly, the dynamic widget in the form of a medium window can also move on the display screen of the mobile phone in response to the dragging operation of the user. For example, the user can press and move the finger at the moving button of the dynamic widget in the form of a medium window, such as the moving button 1909 shown in FIG. 25 (b) of

[0268] In some other embodiments, after displaying the dynamic widget (e.g., a dynamic widget in the form of a small window or a dynamic widget in the form of a medium window) on the display screen, the mobile phone can display a multi-task interface or a split-screen interface in response to a corresponding operation performed by the user. When the user presses the dynamic widget and moves the finger, causing the dynamic widget to move on the display screen, if the user stops moving the finger on an application window (which can be an application window of a second application in embodiments of the present application) in the multi-task interface or the split-screen interface, causing the dynamic widget to hover over the application window, the mobile phone can enlarge the application window and display it on the display screen.

[0269] Further, if the application window displayed at this time is a window of an application such as a memo, a document editor, a file manager, an instant messaging application, etc., the mobile phone can further display a prompt for prompting the user whether to insert the dynamic widget into the application window. If an operation of selecting to insert (which can be a drag-and-drop release operation in embodiments of the present application) is received, the dynamic widget can be converted into a resource file (e.g., a picture, a video, or a link, etc.) and inserted into the application window. After the dynamic widget is converted into the resource file and inserted into the application window, the dynamic widget can continue to be displayed on the display screen or can be automatically closed. If an operation of selecting not to insert is received, the dynamic widget can continue to be displayed on the display screen. If the application window displayed is not a window of the above-mentioned applications, after the user releases the finger, the dynamic widget can continue to be displayed on the display screen.

[0270] For example, in combination with FIG. 25 For example, in combination with FIG. 25 As shown in (a) of FIG. 25, a dynamic widget 2501 is displayed on the display screen of the mobile phone. The user performs a corresponding operation, such as a sliding operation starting from the lower edge of the display screen to the upper edge of the display screen, and without releasing the finger or the stylus after the sliding operation, triggers the mobile phone to display a multi-task interface 2502 on the display screen. The mobile phone receives an operation of pressing the dynamic widget 2501 and moving the finger. In response to the operation, the mobile phone can display an animation of the dynamic widget 2501 moving with the finger. After the dynamic widget 2501 moves to the position of an application window thumbnail in the multi-task interface 2502, if the user continues to move the finger to cause the dynamic widget 2501 to continue to move, the mobile phone can switch the application window thumbnail displayed on the display screen in the multi-task interface 2502 as the dynamic widget 2501 moves. As shown in (b) of FIG. 25, when the dynamic widget 2501 moves to the position of the application window thumbnail in the multi-task interface 2502, the user slides the finger to the left. As the user slides the finger, as shown in (c) of FIG. 25, the dynamic widget 2501 moves to the left with the finger. FIG. 25 FIG. 25 ​As shown in (c) of FIG. 25, the phone switches the application window thumbnail of application 1 displayed in multitasking interface 2502 to the application window thumbnail 2503 of application 2. If the user stops moving the finger at this time, so that the dynamic widget 2501 hovers over the application window thumbnail 2503 of the application 2, the phone displays the application window 2504 of the application 2 as shown in (d) of FIG. 25. In this case, FIG. 25 As shown in (d) of FIG. 25, the phone displays the application window 2504 of the application 2. In this case, FIG. 25 As shown in (d) of FIG. 25, the phone displays the application window 2504 of the application 2. In this case,

[0271] For example, taking the application window 2504 of an instant messaging application as an example, as shown in (d) of FIG. 25, the phone displays a prompt area 2505 for prompting the user whether to insert the dynamic widget 2501 into the application window 2504. If the phone receives an operation of the user selecting to insert, such as an operation of dragging the dynamic widget 2501 into the prompt area 2505 and lifting the finger, the phone converts the dynamic widget 2501 into a resource file and inserts the resource file into the application window. FIG. 26 As shown in (d) of FIG. 25, the phone displays the application window 2504 of the application 2. In this case, FIG. 26 As shown in (e) of FIG. 25, after the user lifts the finger, the phone displays the application window 2507 in full screen and sends out the dynamic widget 2501 converted into a resource file, and the phone also displays a sent message prompt 2508. In addition, after the dynamic widget 2501 is converted into a resource file and inserted into the application window, the dynamic widget 2501 is automatically closed and no longer displayed on the display screen of the phone. After the dynamic widget 2501 is dragged into the prompt area 2505, the phone also displays a release prompt, such as a plus sign 2506, on the dynamic widget 2501 (such as the upper left corner), to prompt the user that after the user lifts the finger, the dynamic widget 2501 will be converted into a resource file and inserted into the application window. After the dynamic widget 2501 is dragged out of the prompt area 2505, the release prompt is removed. At this time, if the user lifts the finger, the dynamic widget 2501 is automatically attracted to the edge of the display screen.

[0272] Similarly, in the scenario where the phone displays a dynamic widget (such as a dynamic widget in the form of a small window or a dynamic widget in the form of a medium window) on the desktop, after the user presses the dynamic widget and moves the finger, so that the dynamic widget moves on the display screen, if the user stops moving the finger over an icon of an application on the desktop, so that the dynamic widget hovers over the icon of the application, the phone opens the application and displays a corresponding application window. If the displayed application window is a window of an application such as a memo, a document editor, a file manager, an instant messaging application, etc., the user can also select to insert the dynamic widget converted into a resource file into the application window.

[0273] For example, in combination with FIG. 26For example, consider a dynamic small window, which is a small window in the form of a dynamic small window. FIG. 26 As shown in (a), the mobile phone screen displays a desktop 2601, on which a dynamic small window 2602 is displayed. The mobile phone receives the user's action of pressing the dynamic small window 2602 and moving their finger. FIG. 26 As shown in (b) above, in response to this operation, the phone can display a minimized dynamic window 2603 and show an animation of its movement. (See image below.) FIG. 26 As shown in (c), when the dynamic window 2603 moves to the position of an application icon on the desktop, such as the information icon 2604, if the user stops moving their finger, causing the dynamic window 2603 to hover over the information icon 2604, then as shown in (c), FIG. 26 As shown in (d) above, the mobile phone can display this information in application window 2605. Further, as... FIG. 25 As shown in (d), the phone can also display a prompt area 2606 to prompt the user whether to insert the dynamic window 2603 into the application window 2605. If the phone receives an operation where the user drags the dynamic window 2603 into the prompt area 2606 and lifts their finger, the phone can convert the dynamic window 2603 into a resource file and then insert it into the application window. Additionally, after the dynamic window 2603 is dragged into the prompt area 2606, the phone can also display a release prompt on the dynamic window 2603 (e.g., the upper left corner), such as a plus sign 2607, to indicate that releasing the finger will trigger the conversion of the dynamic window 2603 into a resource file and its insertion into the application window. If the user does not want to insert the dynamic window 2603 into the application window 2605, they can drag the dynamic window 2603 to another area outside the prompt area 2606 and lift their finger. The phone can respond to the user's operation by enlarging the shrunken dynamic window 2603 and re-displaying it on the screen, as shown in (d). FIG. 26 As shown in (a) above. For further details, please refer to [reference needed]. FIG. 27 The descriptions of the corresponding content are not repeated here. The above explanation uses the example of application window 2605, which supports insertion, as an example. In some other embodiments, for applications that do not support insertion, when the user drags the shrunken dynamic window to the application's icon and hovers it over it, the phone can display a message indicating that insertion is not supported. Afterwards, if the user lifts their finger, the phone can enlarge the shrunken dynamic window and re-display it on the screen, as shown below. FIG. 27 As shown in (a) in the figure.

[0274] In some other embodiments, when the phone is connected with other terminals (which can be the second terminal in the embodiments of the present application), the user can also drag the dynamic widget (such as the dynamic widget in the form of a small window or the dynamic widget in the form of a medium window) to other terminals connected with the phone by dragging. For example, after receiving the user's pressing and moving operation on the dynamic widget, the phone can perform drag listening to determine whether to trigger cross-device dragging. For example, after determining that the dynamic widget is dragged into the cross-device dragging awareness area, it is determined that the cross-device dragging is triggered. After determining that the cross-device dragging is triggered, the phone can send the data of the dynamic widget to the target device of the cross-device dragging, so that the target device performs the continuation of the dragging. After receiving the user's release operation, the target device can display the dynamic widget (such as the dynamic widget in the form of a small window or the dynamic widget in the form of a medium window) on the display screen of the target device, so as to achieve the effect of cross-device dragging of the dynamic widget to other devices. Alternatively, after receiving the user's dragging operation, the target device can display the dynamic widget in full screen on the display screen of the target device.

[0275] In addition, after the phone displays the dynamic widget (such as the dynamic widget in the form of a small window or the dynamic widget in the form of a medium window), if the user presses the dynamic widget and quickly slides to the edge of the display screen of the phone, the phone can close the dynamic widget and stop displaying the dynamic widget on the display screen of the phone. It can be understood that the above-mentioned embodiments describe the scheme of closing the dynamic widget, which is triggered by the user. In some other embodiments, the dynamic widget can also be automatically closed, such as the end of video playing in the dynamic widget or the end of navigation.

[0276] In some other embodiments, in the scenario that the phone displays the dynamic widget (such as the dynamic widget in the form of a small window or the dynamic widget in the form of a medium window) on the application window of other applications, the user can trigger the phone to replace the dynamic widget by performing corresponding operations. For example, in combination with FIG. 27 As shown in (a) of FIG. 27, the phone displays the chat detail page 2701 of the instant messaging application, and the dynamic widget 2702 of application 1 is displayed on the chat detail page 2701. For example, the phone receives the user's double-finger pinch operation with one finger on the chat detail page 2701 and the other finger on the dynamic widget 2702. As a response to the operation, as shown in (b) of FIG. 27, the phone displays the chat detail page 2701 of the instant messaging application, and the dynamic widget 2703 of application 2 is displayed on the chat detail page 2701. FIG. 27 FIG. 28 ​As shown in (b), the phone displays application window 2703 of application 1 (which includes information details), and displays a dynamic pop-up 2704 of the instant messaging application on application window 2703. Alternatively, the phone receives an operation from the user to switch the instant messaging application to the background, such as a swipe operation from the bottom edge of the phone screen to the top edge of the phone screen. In response to this operation, the phone closes (or does not display) the dynamic pop-up 2702, and additionally... FIG. 28 As shown in (c), the mobile phone displays desktop 2705, and displays a dynamic window 2706 of the instant messaging application on desktop 2705. The specific implementation of the dynamic window 2704 of the instant messaging application displayed on the mobile phone can be found in the detailed description of the corresponding content in the above embodiments, and will not be elaborated upon here.

[0277] In the above embodiments, the background color of the dynamic window is a light color, such as white. In other embodiments, the background color of the dynamic window can also be a dark background (such as black) or a transparent background; this embodiment does not impose any limitations on this. Furthermore, the dynamic window in the form of a small window can automatically collapse and hide on the phone, and then reappear on the phone screen after receiving a user's operation. As an example, after the dynamic window in the form of a small window is displayed, if the phone receives a drag operation from the user to pull the dynamic window off the edge of the phone screen, the dynamic window will be hidden. For example, combined with... FIG. 28 For example, a dynamic small window, in the form of a small window, is attached to the upper right corner of the phone screen. FIG. 29 As shown in (a), the phone displays a dynamic window 2801 in the upper right corner of the screen. When the phone receives a drag operation from the user on the dynamic window 2801 towards the right edge of the screen (such as pressing the dynamic window 2801 and moving a finger), the phone hides the dynamic window 2801. FIG. 29 As shown in (b), the phone can also display a call-up button 2802 at a corresponding location on the phone screen (e.g., where the dynamic window 2801 is dragged off the screen). If the phone receives a user's operation on the button 2802, such as a click, the phone can redisplay the dynamic window 2801 on the phone screen. Similarly, after a dynamic window in medium window form is displayed, if the phone receives a user's drag operation on the dynamic window to the edge of the phone screen, the medium window dynamic window will be hidden. The phone can also display a call-up button. If a user's operation on the call-up button is received, the dynamic window will be redisplayed. It is understandable that if a small window dynamic window is hidden, a small window dynamic window will also be redisplayed after an operation on the call-up button. If a medium window dynamic window is hidden, a medium window dynamic window will also be redisplayed after an operation on the call-up button.

[0278] By adopting the technical solutions provided in the embodiments, the terminal can extract key elements in the terminal display interface and display the key elements in the form of a dynamic small window on the terminal screen. By using limited small window display resources, the display of key content in the application window is realized, and the user experience is not affected by the display of too much content, and the processing needs of the user can be met, such as the use of a dynamic small window to help the user to acquire and quickly process information in multiple tasks. In addition, after the triggering condition of the dynamic small window is met, such as user-initiated triggering or system automatic triggering, the dynamic small window can be displayed, so that the user can call the dynamic small window in any interface, and the processing needs of the small window in multiple task processing are met. The dynamic small window has the characteristics of supporting application or system triggering, flexible display, and simple operation.

[0279] The dynamic small window supports page-level, application-level, and system-level presentation. In addition, the content and layout effect presented in the dynamic small window support automatic recommendation by the system according to different application types or customization by a third-party application developer, so that the user can more flexibly complete multiple task processing, and the flexible display and layout needs of the dynamic small window can be met. With the system-level small window triggering gesture (such as sliding the application window downward in the multi-task interface), a natural flow sliding gesture animation effect is supported, such as the application window turning into a dynamic small window (i.e., a rotating manner), and the application window and the dynamic small window can also be combined with a gradual appearance and disappearance animation effect, thereby improving the user experience.

[0280] FIG. 5 A composition diagram of a display device provided in the embodiments of the present application is shown in FIG. 29. FIG. 30 As shown in the figure, the device can be applied to a terminal (such as the mobile phone described above), and the device can include a display unit 2901 and an input unit 2902.

[0281] The display unit 2901 is configured to display an application window of a first application on a display screen of the terminal, and the application window of the first application includes a plurality of elements.

[0282] The input unit 2902 is configured to receive a first operation.

[0283] The display unit 2901 is further configured to display a first window on the display screen of the terminal after receiving the first operation, and the first window includes part of the elements in the application window of the first application.

[0284] Further, the first operation can include a drag operation on the application window of the first application in the multi-task interface.

[0285] The display unit 2901 is specifically configured to display a multi-task interface after receiving the second operation, and the multi-task interface includes the application window of the first application.

[0286] The display unit 2901 is specifically configured to display an animation of movement of an application window of the first application, and display the first window on the display screen of the terminal when it is determined that the application window of the first application moves to the specified area of the display screen of the terminal.

[0287] Further, the application window of the first application can be a free window, and the first operation can include a drag operation on the application window of the first application, i.e., the free window of the first application.

[0288] The display unit 2901 is specifically configured to display an animation of movement of an application window of the first application, and display the first window on the display screen of the terminal when it is determined that the application window of the first application moves to the specified area of the display screen of the terminal.

[0289] Further, the first operation can be an operation of triggering the first application to switch to the background.

[0290] Further, the display unit 2901 is further configured to display a notification message on the display screen of the terminal, and the first operation is a selection operation on the notification message.

[0291] Further, the apparatus can further include an acquisition unit 2903 configured to extract part of elements from a plurality of elements of the application window of the first application.

[0292] Further, the part of elements can be predetermined. For example, the part of elements can be video elements.

[0293] Further, the acquisition unit 2903 is specifically configured to: acquire a first identifier, acquire a configuration file corresponding to the first identifier from stored configuration files corresponding to different identifiers, the configuration file corresponding to the first identifier including an identifier of the part of elements; extract the part of elements from the plurality of elements of the application window of the first application according to the configuration file corresponding to the first identifier; and wherein the first identifier can include an identifier of the first application, or the first identifier can include an identifier of the first application and an identifier of an interface in the application window.

[0294] Further, the acquisition unit 2903 is specifically configured to: acquire a type of the first application, acquire a recommendation model corresponding to the type of the first application from stored recommendation models corresponding to different types of applications, the recommendation model having a function of extracting elements to be displayed in the first window according to the type of the application; and extract the part of elements from the plurality of elements of the application window of the first application according to the recommendation model corresponding to the type of the first application.

[0295] Further, the layout of the part of elements in the first window is different from the layout of the elements corresponding to the part of elements in the application window.

[0296] Further, the layout of the part of elements in the first window is predetermined.

[0297] Furthermore, the acquisition unit 2903 is also used to acquire a layout file corresponding to the first identifier from a stored layout file, and to lay out the extracted elements according to the acquired layout file.

[0298] Furthermore, the acquisition unit 2903 is also used to acquire a layout file corresponding to the type of the first application from the stored layout file, and to lay out the extracted elements according to the acquired layout file.

[0299] Furthermore, the input unit 2902 is also used to receive a third operation on the first window.

[0300] The display unit 2901 is further configured to, upon receiving a third operation on the first window, change the first window to a second window and display it on the terminal's display screen; wherein the second window includes some elements from the application window of the first application, and the second window includes more elements than the first window.

[0301] Furthermore, the acquisition unit 2903 is also used to extract the elements to be displayed in the second window from multiple elements of the application window of the first application.

[0302] For example, the elements to be displayed in the second window can be pre-defined.

[0303] For example, the acquisition unit 2903 is specifically used to acquire the configuration file corresponding to the first identifier from the stored configuration files corresponding to different identifiers (the configuration file is a configuration file for the second window) based on the first identifier, and then, based on the acquired configuration file, extract the elements to be displayed in the second window from multiple elements of the application window of the first application.

[0304] For example, the acquisition unit 2903 is specifically used to acquire a recommendation model corresponding to the type of the first application from the stored recommendation models corresponding to different types of applications (the recommendation model is a recommendation model for the second window) based on the type of the first application. Then, based on the acquired recommendation model, it extracts the elements to be displayed in the second window from multiple elements of the application window of the first application.

[0305] For elements extracted that need to be displayed in a medium-sized window, their layout in the medium-sized window can be different from the layout of the corresponding element in the application window of the first application.

[0306] Furthermore, the second window also includes a close button and a zoom button.

[0307] The input unit 2902 is further configured to receive an operation on the closing button; and the display unit 2901 is further configured to, after receiving the operation on the closing button, not display the second window.

[0308] The input unit 2902 is further configured to receive an operation on the zoom-in button; and the display unit 2901 is further configured to, after receiving the operation on the zoom-in button, display the application window of the first application and not display the second window.

[0309] Further, the display unit 2901 is further configured to, after determining that no user operation is received within the preset time or after receiving the fourth operation on the second window, change the second window to the first window and display the first window on the display screen of the terminal.

[0310] Further, the display unit 2901 displays the first window, which can include displaying a desktop on the display screen of the terminal, and displaying the first window on the desktop, and the desktop can include an icon of the second application.

[0311] The input unit 2902 is further configured to receive an operation of dragging the first window.

[0312] The display unit 2901 is further configured to, after receiving the operation of dragging the first window, display an animation of moving the first window, and display the application window of the second application on the display screen of the terminal when the first window is dragged to a position of the icon of the second application.

[0313] Further, the display unit 2901 is further configured to, after receiving the second operation, display a multitasking interface including the application window of the second application, display an animation of moving the first window after receiving the operation of dragging the first window, and display the application window of the second application on the display screen of the terminal when the first window is dragged to a position of the application window of the second application.

[0314] Further, the input unit 2902 is further configured to receive a drag-release operation.

[0315] The apparatus can further include a storage unit 2904 configured to, after receiving the drag-release operation, store the first window after being converted into a resource file, or the apparatus can further include a sending unit 2905 configured to, after receiving the drag-release operation, send the first window after being converted into a resource file to a second terminal through the second application.

[0316] Further, the terminal is connected with the second terminal, and the input unit 2902 is further configured to receive the operation of dragging the first window.

[0317] The display unit 2901 is further configured to, after receiving the operation of dragging the first window, display an animation of moving the first window.

[0318] The sending unit 2905 is further configured to send, to the second terminal, data of the first window after determining that the user's drag intention is cross-device drag, the data of the first window being used by the second terminal to display the first window on a display screen of the second terminal.

[0319] The display device can be applied to an electronic device, such as the terminal (e.g., the mobile phone) in the foregoing embodiments. The display device can include a processor, a memory for storing processor-executable instructions, and a display screen. The processor is configured to execute the instructions to cause the display device to implement the functions or steps performed by the terminal (e.g., the mobile phone) in the foregoing method embodiments.

[0320] The electronic device (which can be a terminal, such as the mobile phone in the foregoing embodiments) can include a display screen, a memory, and one or more processors. The display screen, the memory, and the processor are coupled. The memory is configured to store computer program code including computer instructions. When the processor executes the computer instructions, the electronic device can perform the functions or steps performed by the terminal (e.g., the mobile phone) in the foregoing method embodiments. Of course, the electronic device includes but is not limited to the display screen, the memory, and the one or more processors. For example, the structure of the electronic device can refer to the structure of the mobile phone shown in ​ .

[0321] The chip system can be applied to an electronic device, such as the terminal (e.g., the mobile phone) in the foregoing embodiments. As shown in ​ , the chip system includes at least one processor 3001 and at least one interface circuit 3002. The processor 3001 can be the processor in the foregoing electronic device. The processor 3001 and the interface circuit 3002 can be interconnected through a line. The processor 3001 can receive and execute computer instructions from the memory of the foregoing electronic device through the interface circuit 3002. When the computer instructions are executed by the processor 3001, the electronic device can perform the steps performed by the mobile phone in the foregoing embodiments. Of course, the chip system can also include other discrete devices, which are not limited in the embodiments of the present application.

[0322] The embodiments of the present application further provide a computer-readable storage medium for storing computer instructions for running an electronic device, such as the terminal (e.g., the mobile phone) described above.

[0323] The embodiments of the present application further provide a computer program product including computer instructions for running an electronic device, such as the terminal (e.g., the mobile phone) described above.

[0324] Through the description of the above embodiments, those skilled in the art can clearly understand that, for the convenience and brevity of description, only the division of the above functional modules is exemplified, and in actual application, the above functions can be completed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.

[0325] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative, for example, the division of the modules or units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another device, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the displayed or discussed units can be indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0326] The units described as separate components can or can not be physically separated, and the components shown as units can be one physical unit or multiple physical units, that is, can be located in one place or can be distributed to multiple different places. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment scheme.

[0327] In addition, the functional units in each embodiment of the present application can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0328] The integrated unit, if realized in the form of a software functional unit and sold or used as an independent product, can be stored in a readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application essentially or say the parts that make contributions to the prior art or all or part of the technical solutions can be embodied in the form of a software product, which is stored in a storage medium and includes a plurality of instructions to make a device (which can be a single-chip microcomputer, a chip, etc.) or a processor execute all or part of the steps of the method described in the embodiments of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various storage medium that can store program codes.

[0329] The above merely provides the specific implementation of the present application, but the protection scope of the present application is not limited to this. Any change or replacement within the technical scope disclosed by the present application should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A window display method characterized by, The method applied to a terminal comprises: The terminal displays an application window of a first application in a full-screen floating window on a display screen of the terminal, the application window comprising a plurality of elements; the first application is a video application; After receiving a first operation, the terminal displays a first window on the display screen of the terminal, the first window comprising part of the elements in the application window, the part of the elements being extracted from the plurality of elements in the application window; the part of the elements is a video element; After receiving a third operation on the first window, the terminal changes the first window to a second window and displays the second window on the display screen of the terminal; The second window comprises part of the elements in the application window, and the second window comprises more elements than the first window; The first window comprises elements browsable by a user, and the second window comprises elements browsable by a user and elements operable by a user, the elements operable by a user comprising a zoom-in button; After receiving an operation on the zoom-in button, the terminal displays the application window in a full-screen large window and does not display the second window; The display of the first window on the display screen of the terminal comprises: the terminal displays a desktop on the display screen of the terminal, and displays the first window on the desktop, the desktop comprising an icon of a second application; After the display of the first window on the display screen of the terminal, the method further comprises: After receiving an operation of dragging the first window, the terminal displays an animation of the movement of the first window; When the first window is dragged to a position of the icon of the second application, the terminal displays an application window of the second application on the display screen of the terminal; After receiving a drag-release operation, the terminal sends the video element to a second terminal through the application window of the second application.

2. The method of claim 1, wherein, The display of the application window of the first application on the display screen of the terminal comprises: After receiving a second operation, the terminal displays a multitasking interface, and the multitasking interface comprises the application window; The first operation is an operation on the application window in the multitasking interface.

3. The method of claim 1, wherein, The application window is a free small window.

4. The method according to any one of claims 1 to 3, characterized in that, Before the display of the first window on the display screen of the terminal, the method further comprises: The terminal extracts the part of the elements from the plurality of elements in the application window.

5. The method according to claim 4, wherein The part of the elements is predetermined; or The extraction of the part of the elements from the plurality of elements in the application window by the terminal comprises: the terminal acquires a first identifier, acquires a configuration file corresponding to the first identifier from stored configuration files corresponding to different identifiers, the configuration file corresponding to the first identifier comprising an identifier of the part of the elements, and the terminal extracts the part of the elements from the plurality of elements in the application window according to the configuration file corresponding to the first identifier; or the first identifier comprises an identifier of the first application, or the first identifier comprises an identifier of the first application and an identifier of an interface in the application window. The terminal extracts the partial elements from the plurality of elements of the application window, comprising: the terminal obtaining a type of the first application, and obtaining a recommendation model corresponding to the type of the first application from stored recommendation models corresponding to different types of applications, the recommendation model having a function of extracting elements to be displayed in the first window according to the type of the application; and the terminal extracting the partial elements from the plurality of elements of the application window according to the recommendation model corresponding to the type of the first application.

6. The method according to any one of claims 1-3, characterized in that, The layout of the partial elements in the first window is different from the layout of the elements corresponding to the partial elements in the application window.

7. The method of claim 6, wherein, The layout of the partial elements in the first window is predetermined; or Before displaying the first window on the display screen of the terminal, the method further comprises: the terminal obtaining a layout file corresponding to the first identifier or the type of the first application from stored layout files according to the first identifier or the type of the first application, and the terminal performing layout on the partial elements according to the obtained layout file; wherein the first identifier comprises an identifier of the first application, or the first identifier comprises an identifier of the first application and an identifier of an interface in the application window.

8. The method of claim 1, wherein, The second window further comprises a close button; The method further comprises: after the terminal receives an operation on the close button, the terminal does not display the second window.

9. The method of claim 1, wherein, After the terminal changes the first window to the second window to be displayed on the display screen of the terminal, the method further comprises: The terminal changes the second window to the first window to be displayed on the display screen of the terminal after determining that no user operation is received within a preset time, or after receiving a fourth operation on the second window.

10. The method of any one of claims 1-3, wherein, After the terminal displays the first window, the method further comprises: The terminal displays the multitasking interface after receiving a second operation, and the multitasking interface comprises an application window of a second application; The terminal displays an animation of the movement of the first window after receiving an operation of dragging the first window; When the first window is dragged to a position of the application window of the second application, the terminal displays the application window of the second application on the display screen of the terminal; The terminal sends the video element to a second terminal through the application window of the second application after receiving a drag release operation.

11. The method of any one of claims 1-3, wherein, The terminal is connected with a second terminal; After displaying the first window on the display screen of the terminal, the method further comprises: The terminal displays an animation of the movement of the first window after receiving an operation of dragging the first window; After determining that the drag intention of the user is cross-device dragging, the terminal sends data of the first window to the second terminal, and the data of the first window is used to display the first window on a display screen of the second terminal.

12. A display device, characterized by comprising: comprise: a processor; a memory for storing instructions executable by the processor; and a display screen. wherein the processor is configured to execute the instructions to cause the display device to implement the method of any of claims 1-11.

13. A computer-readable storage medium having stored thereon computer program instructions, wherein, The computer program instructions, when executed by the electronic device, cause the electronic device to implement the method of any of claims 1-11.

Images