Application display method, terminal device, and computer program product
By implementing page loading and independent page stack management between the first and second windows in the terminal device, the problem of cumbersome operations for users to revisit deeply layered pages in the application is solved, thus improving the user experience.
Patent Information
- Application Number
- PCT/CN2025/138818
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-16
- Filing Date
- 2025-11-29
- Publication Date
- 2026-11-19
AI Technical Summary
When users revisit pages that are deeply nested within an application, they need to click multiple times, which is cumbersome and results in a poor user experience.
By loading pages between the first and second windows and utilizing independent page stack management, users can perform target operations in the first window and load the second page into the second window, achieving fast page display and saving, and simplifying the operation process.
It improves the user experience by simplifying the process of revisiting previously viewed pages through multi-window display and page stack management, reducing the number of hierarchical search steps.
Smart Images

Figure CN2025138818_19112026_PF_FP_ABST
Abstract
Description
Application display methods, terminal devices and computer program products
[0001] This application claims priority to Chinese Patent Application No. 202510643464.2, filed on May 16, 2025, entitled “Application Display Method, Terminal Equipment and Computer Program Product”, the entire contents of which are incorporated herein by reference. Technical Field
[0002] This application belongs to the field of terminal technology, and in particular relates to application display methods, terminal devices and computer program products. Background Technology
[0003] With the development of terminal technology, users can install various applications on their devices and browse pages within these applications to access content of interest. Currently, applications generally have numerous functions and deep hierarchies, especially super apps, which often require users to click multiple times to navigate to deeper levels of the application. After browsing a deeply nested page within an application, users need to click repeatedly to revisit it, resulting in cumbersome operations and a poor user experience. Summary of the Invention
[0004] This application provides an application display method, terminal device, and computer program product, which can solve the problem that after a user browses a deeply layered page in an application, if they want to view the page again, the user needs to click multiple times to view it, which is cumbersome and results in a poor user experience.
[0005] In a first aspect, embodiments of this application provide an application display method, which may include:
[0006] The first page of the first application is displayed in the first window;
[0007] In response to an operation performed on the first page, a second page of the first application is displayed in the first window; the second page is a sub-page of the first page.
[0008] In response to a first target operation on the first window, the second page is loaded into the second window, and the first page is displayed in the first window.
[0009] In the application display method described above, a user can browse pages of a first application in a first window, such as the first page of the first application, and perform operations on the first page to browse a second page of the first application. When a user is browsing a page (e.g., the second page) of the first application, if the user wants to view the second page later, the user can perform a first target operation on the first window to load the second page displayed in the first window into another window. This means that pages viewed by the user can be loaded into other windows, allowing the saved pages to be quickly displayed without requiring the user to navigate through different layers to find the desired page. This simplifies the process of viewing previously viewed pages and improves the user experience.
[0010] In some embodiments, the first window and the second window have their own page stacks; wherein, before the first target operation is detected, the page stack of the first window includes the first page and the second page, and the second page is the top element of the page stack of the first window; when the second page is loaded into the second window and the first page is displayed in the first window, the top element of the page stack of the first window is the first page, the page stack of the second window includes the second page, and the second page is the top element of the page stack of the second window.
[0011] In the application display method provided in this embodiment, when displaying the page of the first application in the first window, the terminal device can establish a page stack for the first window to manage the pages in the first window. After detecting a first target operation on the first window, the terminal device can create a second window, load a second page into the second window, and establish a page stack for the second window to manage the pages in the second window. The page stack of the second window and the page stack of the first window can be independent of each other, so that operations performed on the pages in the first window do not affect the pages in the second window. Similarly, operations performed on the pages in the second window do not affect the pages in the first window.
[0012] For example, after establishing the page stack of the second window, the terminal device can push the second page onto the page stack of the second window. Alternatively, the terminal device can first push the homepage of the first application onto the page stack of the second window, and then push the second page onto the page stack of the second window. Or, the terminal device can sequentially push all the pages currently included in the page stack of the first window onto the page stack of the second window. After pushing the second page onto the page stack of the second window, the top element of the page stack of the second window can be the second page.
[0013] For example, when a second page is pushed onto the page stack of the second window, the terminal device can pop the second page from the page stack of the first window. After the second page is popped from the page stack of the first window, the top element of the page stack of the first window can be the parent page of the second page (e.g., the first page). That is, when the second page is moved from the first window to the second window, the first window can display the parent page of the second page (e.g., the first page). Alternatively, when the second page is pushed onto the page stack of the second window, the terminal device can keep the page stack of the first window unchanged. That is, the top element of the page stack of the first window can still be the second page, and when the second page is moved to the second window, the first window can still display the second page.
[0014] In some embodiments, loading the second page into the second window in response to a first target operation on the first window includes:
[0015] In response to a first target operation on the first window, the second page is loaded into the second window and displayed in the second window, wherein the second page is displayed in the second window and the second window does not overlap with the first window.
[0016] In the application display method provided in this embodiment, after loading the second page into the second window in response to the first target operation on the first window, the terminal device can directly display the second window, and the second window does not overlap with the first window, which makes it convenient for users to view the second page through the second window.
[0017] In one embodiment, before loading the second page into the second window in response to a first target operation on the first window, the method may further include:
[0018] Display the first menu bar in the first window;
[0019] In response to an operation on the first menu bar, a first window control menu is displayed; the first window control menu includes a first menu item.
[0020] The step of loading the second page into the second window in response to a first target operation on the first window includes:
[0021] In response to a first target operation on the first menu item, the second page is loaded into the second window and the second window is displayed.
[0022] In the application display method provided in this embodiment, when the terminal device displays the page of the first application in the first window, it can also display a first menu bar. After the first menu bar is clicked, the terminal device can display a first window control menu. The first window control menu can include one or more menu items, such as "Multi-window within application," "Replace application," and "Close window." "Multi-window within application" can be used to display multiple pages of the first application together with one or more other windows. "Replace application" can be used to switch applications launched in the first window. "Close window" can be used to close the first window. The first menu item can be "Multi-window within application." That is, the terminal device can load the second page displayed in the first window into the second window for display based on the user's operation on the first menu bar and the operation on "Multi-window within application" in the first window control menu. The entry point for multi-window display is clear and intuitive, making it convenient for users to display multiple windows and improving the user experience.
[0023] In one embodiment, loading the second page into the second window and displaying the second window in response to a first target operation on the first menu item may include:
[0024] Obtain the declaration information corresponding to the first application;
[0025] When it is determined from the declaration information that the first application supports multi-window display, in response to the first target operation on the first menu item, the second page is loaded into the second window and the second window is displayed.
[0026] In the application display method provided in this embodiment, after the terminal device launches the first application, when displaying the page of the first application, the terminal device can display the first menu bar corresponding to the first window. Additionally, the terminal device can read the declaration information corresponding to the first application and determine whether the first application supports multi-window display based on the declaration information. When it is determined that the first application supports multi-window display, when the terminal device displays the first window control menu based on the user's operation on the first menu bar, the menu item corresponding to multi-window display in the first window control menu is in a triggerable state; that is, when the user browses the page of the first application, they can initiate multi-window display by triggering the corresponding menu item. However, when the first application does not support multi-window display, the menu item corresponding to multi-window display in the first window control menu is in a non-triggerable state; that is, when the user browses the page of the first application, they cannot trigger the corresponding menu item, thus preventing multi-window display from being initiated.
[0027] For example, the application display method can be a system function provided by the terminal device. The terminal device can provide relevant interfaces to the first application, allowing the first application to call the system function through these interfaces. Additionally, when developing the first application, developers can adapt it to determine if it supports multi-window display. If the first application supports multi-window display, developers can determine the specific pages within the first application that support it. For instance, when determining that the first application supports multi-window display, developers can add corresponding declaration information to the first application. This declaration information can be used to indicate whether the first application supports multi-window display and which pages within the first application support it. In other words, when it is determined that the first application needs to support multi-window display, developers only need to perform simple adaptation, resulting in a small adaptation workload and effectively extending applications that support multi-window display.
[0028] In other embodiments, after the second page is loaded into the second window, the second window is stacked with the first window and the second window is located behind the first window.
[0029] In the application display method provided in this embodiment, when the second page is loaded into the second window in response to the first target operation on the first window, the second window can be located behind the first window, that is, the second window can be not displayed, so that when the user does not need to view the page in the second window temporarily, it does not occupy display space, thereby making it convenient for the user to view the page through the first window.
[0030] In one embodiment, before loading the second page into the second window in response to a first target operation on the first window, the method may further include:
[0031] Display the second menu bar in the first window;
[0032] In response to an operation on the second menu bar, a second window control menu is displayed; the second window control menu includes second menu items.
[0033] The step of loading the second page into the second window in response to a first target operation on the first window includes:
[0034] In response to a first target operation on the second menu item, the second page is loaded into the second window.
[0035] In the application display method provided in this embodiment, when the terminal device displays the page of the first application in the first window, it can also display a second menu bar. After the second menu bar is clicked, the terminal device can display a second window control menu. The second window control menu can include one or more menu items, such as "Window Temporary Storage," "Replace Application," and "Close Window." "Window Temporary Storage" can be used to temporarily store the page of the first application through one or more other windows. The second menu item can be "Window Temporary Storage." That is, the terminal device can load the second page displayed in the first window into the second window based on the user's operation on the second menu bar and the operation on "Window Temporary Storage" in the second window control menu. The entry point for page temporary storage is clear and intuitive, making it convenient for users to temporarily store pages and improving the user experience.
[0036] For example, loading the second page into the second window in response to a first target operation on the second menu item may include:
[0037] Obtain the declaration information corresponding to the first application;
[0038] When it is determined from the declaration information that the first application supports multi-window display, the second page is loaded into the second window in response to the first target operation on the second menu item.
[0039] In one embodiment, loading the second page into the second window in response to a first target operation on the second menu item may include:
[0040] In response to a first target operation on the second menu item, the second page is loaded into the second window, and the size of the first window is adjusted; the second window is located behind the adjusted first window, and the adjusted first window partially obscures the second window.
[0041] In the application display method provided in this embodiment, when the first window is a full-screen window, when the second page is loaded into the second window and the second window is located behind the first window, the terminal device can shrink the first window to shrink the full-screen first window into a non-full-screen window, and can partially display the second window, such as displaying the title bar and / or part of the border of the second window, so that the user can understand the temporarily stored second page.
[0042] In another embodiment, after loading the second page into the second window in response to a first target operation on the second menu item, the method may further include:
[0043] In response to an operation on the second menu bar, the second window control menu is displayed; the second window control menu includes a third menu item.
[0044] In response to a second target operation on the third menu item, the second window is displayed.
[0045] In the application display method provided in this embodiment, after the second window is located behind the first window, the terminal device can display the window behind the first window in the display interface based on the user's relevant operations, allowing the user to view the temporarily stored page. Specifically, after temporarily storing a page, the terminal device can adjust the menu items included in the second window control menu; for example, a "Window Tile" menu item can be added to the second window control menu. "Window Tile" can be used to display the window corresponding to the temporarily stored page in the display interface. That is, after loading the second page into the second window, the terminal device can display the second window corresponding to the second page in the terminal device's display interface based on the user's click operation on "Window Tile" in the second window control menu, allowing the user to view the second page through the second window.
[0046] In some embodiments, displaying the second window may include:
[0047] The first window is minimized and displayed in a first display area, and the second window is displayed in a second display area; the first display area and the second display area do not overlap.
[0048] Displaying the second page in the first window may include:
[0049] The second page is displayed in the first display area through a scaled-down version of the first window.
[0050] In the application display method provided in this embodiment, when the first window is a full-screen window, when the second window is displayed based on the user's operation of "multi-window within application" in the first window control menu, or when the first window and the second window are stacked, when the second window is displayed based on the user's operation of "window storage" in the second window control menu, the terminal device can shrink the first window and display the shrunken first window in the first display area, and can also display the second window in the second display area, so that the user can view the first window and the second window at the same time.
[0051] For example, the first display area can be larger than the second display area. The size of the second window can be smaller than the size of the scaled-down first window to facilitate user browsing of the page through the first window.
[0052] In one embodiment, after displaying the scaled-down first window in the first display area and the second window in the second display area, the method may further include:
[0053] In response to a first preset operation on the first window and / or the second window, the second window is displayed in the first display area, and the first window is displayed in the second display area.
[0054] In the application display method provided in this embodiment, when the size of the first window is larger than the size of the second window, the user can perform a first preset operation in the second window or the first window (such as double-clicking the second window, or long-pressing the second window and dragging it to the position of the first window, or long-pressing the first window and dragging it to the position of the second window) to swap the second window with the first window, thereby displaying the page displayed in the second window through the larger window, which makes it convenient for the user to view the temporarily stored page.
[0055] In another embodiment, after the first page is displayed in the first window, the method may further include:
[0056] When the third page is displayed in the first window, in response to a third target operation on the first window, the third page is loaded into the third window, the third window is displayed in the second display area, and the second window is displayed in the second display area, while a fourth page is displayed in the first display area through the first window; the third page is the second page or another page of the first application; the fourth page is the parent page of the third page; the third window and the second window do not overlap.
[0057] For example, when the third page is the homepage of the first application, the fourth page can also be the homepage of the first application.
[0058] For example, the size of the third window can be smaller than the size of the scaled-down first window.
[0059] For example, the size of the second window and the size of the third window can both be smaller than the size of the scaled-down first window.
[0060] In the application display method provided in this embodiment, after the second page is loaded into the second window, the terminal device can display the first page in the first window. While the first page is displayed in the first window, the user can continue to temporarily save the first page to load it into a newly created window (e.g., a third window). Alternatively, the user can view other pages of the first application in the first window through relevant operations. While viewing other pages of the first application in the first window, the user can also continue to temporarily save other pages of the first application to load them into a third window.
[0061] For example, when loading the first page or other pages of the first application into a third window, the terminal device can display the parent page of the first page in the first window. The parent page of a page displayed in the first window can be a page that has been opened in the first window, i.e., a page included in the page stack of the first window. Specifically, when migrating a page displayed in the first window (e.g., the third page or other pages) to another window (e.g., the third window), if that page does not have a parent page in the first window—that is, if no other page in the first application has not been opened in the first window before that page, for example, if that page is the top element of the page stack of the first window—the terminal device can still display that page in the first window. For instance, when displaying the homepage of the first application in the first window, since no other page in the first application has been opened in the first window before the homepage of the first application, i.e., the homepage of the first application can be the top element of the page stack of the first window, therefore, when loading the homepage of the first application into another window, the terminal device can still display the homepage of the first application in the first window.
[0062] In another embodiment, when displaying the second window and the third window in the second display area, the method may further include:
[0063] In response to a second preset operation on the second window and / or the third window, the positions of the second window and the third window in the second display area are swapped.
[0064] In the application display method provided in this embodiment, when multiple windows are displayed in the second display area, such as when the second window and the third window are displayed, the user can perform a second preset operation in the second window or the third window (e.g., long press the second window and drag the second window to the position of the third window, or long press the third window and drag the third window to the position of the second window) to exchange the positions of the second window and the third window, which can facilitate the viewing of the page in the second display area.
[0065] In another embodiment, when displaying the second window and the third window in the second display area, the method may further include:
[0066] In response to a third preset operation on the first window, the size of the first display area and the size of the second display area are adjusted.
[0067] Based on the adjusted size of the first display area, the size of the first window is adjusted, and the adjusted first window is displayed in the first display area.
[0068] Based on the adjusted size of the second display area, adjust the size of the second window and the size of the third window, and display the adjusted second window and the third window in the second display area.
[0069] In the application display method provided in this embodiment, a horizontal bar can be provided on the side (e.g., the right edge) of the first window. This horizontal bar can be dragged to change the ratio between the first and second display areas. That is, the user can adjust the size of the first and second display areas by dragging the horizontal bar. For example, the user can drag the horizontal bar to the left to shrink the size of the first display area and increase the size of the second display area. Similarly, the user can drag the horizontal bar to the right to increase the size of the first display area and shrink the size of the second display area. After adjusting the size of the first and second display areas, the terminal device can adjust the size of the first window, as well as the size of the second and third windows, based on the adjusted sizes, thereby improving the display effect and enhancing the user experience.
[0070] For example, the adjusted size of the first display area is the same as the adjusted size of the second display area.
[0071] For example, when the adjusted second window and the third window are displayed in the second display area, the second window and the third window are displayed stacked.
[0072] In the application display method provided in this example, when dragging the horizontal bar to the left, the adjusted sizes of the first and second display areas can be set to be the same by default. That is, after detecting an operation where the horizontal bar is dragged to any position on the display interface, the terminal device can adjust the sizes of the first and second display areas to be the same, thereby adjusting the display interface to dual-screen mode (i.e., a mode where both display areas are the same size). In dual-screen mode, the terminal device can display the adjusted second and third windows in the adjusted second display area through window stacking, allowing users to easily compare the pages displayed in the first window and the pages displayed in the second (or third) window.
[0073] In one embodiment, when the second window is the focused window, the second window is located above the third window; and / or,
[0074] When the second window is not the focus window, the third window is located on top of the second window.
[0075] In the application display method provided in this embodiment, when the display interface is adjusted to dual-screen mode, the topmost window displayed in the second display area can be the focus window in the second display area, so as to facilitate the user to continue viewing the page of the focus window in the second display area. When there is no focus window in the second display area, the topmost window displayed in the second display area can be the window corresponding to the page with the latest storage time, so as to facilitate the user to view the page with the latest storage time.
[0076] In some embodiments, after displaying the second window, the method may further include:
[0077] In response to a fourth target operation on the second window, the second page is loaded into the fourth window, and the homepage of the first application is displayed in the second window, or the second page is displayed.
[0078] In the application display method provided in this embodiment, after loading the second page into the second window, the user can also load the second page from the second window into other windows (e.g., a newly created fourth window) for display. When loading the second page into the fourth window, the terminal device can still display the second page in the second window. Alternatively, the terminal device can display the parent page of the second page in the second window. When there is no parent page of the second page in the second window, the terminal device can display the homepage of the first application in the second window.
[0079] In other embodiments, after displaying the second window, the method may further include:
[0080] In response to an operation performed on the second page in the second window, the fifth page of the first application is displayed in the second window, while the first page remains displayed in the first window; wherein the fifth page is a sub-page of the second page.
[0081] In the application display method provided in this embodiment, after the second page is loaded into the second window, the user can open a new page in the second window. That is, while the second page is displayed in the second window, the user can perform related operations on the second page to display other pages of the first application in the second window, such as displaying the next level page of the second page. The page stack of the second window is independent of the page stack of the first window; when the second window displays a newly opened page, it does not affect the pages displayed in the first window. For example, the first window can still display the first page.
[0082] It should be understood that before opening the fifth page in the second window, the page stack of the second window can include the second page, and the second page can be the top element of the page stack of the second window. When the fifth page is opened in the second window, the terminal device can push the fifth page onto the page stack of the second window. At this time, the page stack of the second window can still include the fifth page, and the fifth page can be the top element of the page stack of the second window.
[0083] In some embodiments, after the first page is displayed in the first window, the method may further include:
[0084] In response to an operation performed on the first page, a sixth page of the first application is displayed in the first window, the sixth page being a sub-page of the first page;
[0085] In response to a fifth target operation on the first window, the sixth page is loaded into the fifth window, and the first page is displayed in the first window.
[0086] In the application display method provided in this embodiment, after the second page is loaded into the second window, the first window can display the first page. While the first page is displayed in the first window, the user can switch the page displayed in the first window, for example, switching the page displayed in the first window from the first page to another page (e.g., the sixth page). While the sixth page is displayed in the first window, the user can continue to temporarily save the sixth page. That is, while the sixth page is displayed in the first window, the terminal device can create a fifth window based on the user's target operation on the first window, and can load the sixth page into the fifth window.
[0087] Secondly, embodiments of this application provide an application display device, which may include:
[0088] The display module is configured to display a first page of a first application in a first window; and in response to an operation performed on the first page, display a second page of the first application in the first window; the second page is a sub-page of the first page.
[0089] The processing module is configured to load the second page into the second window in response to a first target operation on the first window;
[0090] The display module is also used to display the first page in the first window.
[0091] In some embodiments, the first window and the second window have their own page stacks; wherein, before the first target operation is detected, the page stack of the first window includes the first page and the second page, and the second page is the top element of the page stack of the first window; when the second page is loaded into the second window and the first page is displayed in the first window, the top element of the page stack of the first window is the first page, the page stack of the second window includes the second page, and the second page is the top element of the page stack of the second window.
[0092] In some embodiments, the processing module is specifically configured to, in response to a first target operation on the first window, load the second page into the second window and display the second window, wherein the second page is displayed in the second window and the second window does not overlap with the first window.
[0093] In one embodiment, the display module is further configured to display a first menu bar in the first window; and to display a first window control menu in response to an operation on the first menu bar; the first window control menu includes a first menu item;
[0094] The processing module is specifically used to load the second page into the second window in response to a first target operation on the first menu item;
[0095] The display module is also used to display the second window.
[0096] In one embodiment, the processing module is further configured to obtain declaration information corresponding to the first application; when it is determined from the declaration information that the first application supports multi-window display, in response to the first target operation on the first menu item, the second page is loaded into the second window.
[0097] In other embodiments, after the second page is loaded into the second window, the second window is stacked with the first window and the second window is located behind the first window.
[0098] In one embodiment, the display module is further configured to display a second menu bar in the first window; and to display a second window control menu in response to an operation on the second menu bar; the second window control menu includes second menu items;
[0099] The processing module is further configured to load the second page into the second window in response to a first target operation on the second menu item.
[0100] In one embodiment, the processing module is further configured to, in response to a first target operation on the second menu item, load the second page into the second window and adjust the size of the first window; the second window is located behind the adjusted first window, and the adjusted first window partially obscures the second window.
[0101] In another embodiment, the display module is further configured to display the second window control menu in response to an operation on the second menu bar; the second window control menu includes a third menu item; and to display the second window in response to a second target operation on the third menu item.
[0102] In some embodiments, the display module is further configured to shrink the first window and display the shrunken first window in a first display area, and display the second window in a second display area; the first display area and the second display area do not overlap;
[0103] The display module is further configured to display the second page in the first display area through a scaled-down first window.
[0104] In one embodiment, the display module is further configured to, in response to a first preset operation on the first window and / or the second window, display the second window in the first display area and the first window in the second display area.
[0105] In another embodiment, the processing module is further configured to load the third page into the third window in response to a third target operation on the first window when the third page is displayed in the first window;
[0106] The display module is further configured to display the third window in the second display area, and display the second window in the second display area, and display a fourth page in the first display area through the first window; the third page is the second page or another page of the first application; the fourth page is the parent page of the third page; the third window and the second window do not overlap.
[0107] In another embodiment, when the second window and the third window are displayed in the second display area, the processing module is further configured to, in response to a second preset operation on the second window and / or the third window, swap the positions of the second window and the third window in the second display area.
[0108] For example, the size of the second window and the size of the third window are both smaller than the size of the first window after being reduced in size.
[0109] In another embodiment, when the second window and the third window are displayed in the second display area, the processing module is further configured to, in response to a third preset operation on the first window, adjust the size of the first display area and the size of the second display area; adjust the size of the first window according to the adjusted size of the first display area, and display the adjusted first window in the first display area; and adjust the size of the second window and the size of the third window according to the adjusted size of the second display area.
[0110] The display module is also used to display the adjusted second window and the third window in the second display area.
[0111] For example, when the adjusted second window and the third window are displayed in the second display area, the second window and the third window are displayed stacked.
[0112] In one embodiment, when the second window is the focused window, the second window is located above the third window; and / or,
[0113] When the second window is not the focus window, the third window is located on top of the second window.
[0114] For example, the adjusted size of the first display area is the same as the adjusted size of the second display area.
[0115] In some embodiments, the processing module is further configured to load the second page into the fourth window in response to a fourth target operation on the second window;
[0116] The display module is also used to display the homepage of the first application in the second window, or to display the second page.
[0117] In other embodiments, the display module is further configured to, in response to an operation performed on the second page in the second window, display the fifth page of the first application in the second window, and maintain the first page displayed in the first window; wherein the fifth page is a sub-page of the second page.
[0118] In some embodiments, the display module is further configured to display a sixth page of the first application in the first window in response to an operation performed on the first page, wherein the sixth page is a sub-page of the first page;
[0119] The processing module is further configured to load the sixth page into the fifth window in response to a fifth target operation on the first window;
[0120] The display module is also used to display the first page in the first window.
[0121] Thirdly, embodiments of this application provide a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the terminal device implements the application display method described in any one of the first aspects above.
[0122] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program, which, when executed by a terminal device, causes the terminal device to implement the application display method described in any one of the first aspects above.
[0123] Fifthly, embodiments of this application provide a computer program product, which includes a computer program that, when executed on a terminal device, causes the terminal device to implement the application display method described in any one of the first aspects.
[0124] It is understood that the beneficial effects of the second to fifth aspects mentioned above can be found in the relevant descriptions in the first aspect mentioned above, and will not be repeated here. Attached Figure Description
[0125] Figure 1 is a schematic diagram of the structure of the terminal device to which the application display method provided in the embodiments of this application is applicable;
[0126] Figure 2 is a schematic diagram of the software architecture to which the application display method provided in the embodiments of this application is applicable;
[0127] Figure 3 is an example diagram of the page stack provided in an embodiment of this application;
[0128] Figures 4 to 6 are a set of interface diagrams provided in the embodiments of this application;
[0129] Figure 7 is another set of interface diagrams provided in the embodiments of this application;
[0130] Figure 8 is another set of interface diagrams provided in the embodiments of this application;
[0131] Figure 9 is another set of interface diagrams provided in the embodiments of this application;
[0132] Figure 10 is another set of interface diagrams provided in the embodiments of this application;
[0133] Figures 11 to 13 are another set of interface diagrams provided in the embodiments of this application;
[0134] Figures 14 to 17 are another set of interface diagrams provided in the embodiments of this application;
[0135] Figure 18 is a schematic flowchart of the application display method provided in an embodiment of this application;
[0136] Figures 19 and 20 are another set of interface diagrams provided in the embodiments of this application. Detailed Implementation
[0137] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.
[0138] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.
[0139] In the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.
[0140] References to "one embodiment" or "some embodiments" as described in this application specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in another embodiment," "in yet another embodiment," etc., appearing in different parts of this application specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof all mean "including but not limited to," unless otherwise specifically emphasized.
[0141] Furthermore, the term "multiple" mentioned in the embodiments of this application should be interpreted as two or more.
[0142] The steps involved in the application display method provided in this application embodiment are merely examples. Not all steps are mandatory, nor are all information or message contents required. They can be added or removed as needed during use. The same step or step or message with the same function in this application embodiment can be referenced and learned from each other in different embodiments.
[0143] The business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.
[0144] With the development of terminal technology, users can install various applications on their devices and browse pages within these applications to access content of interest. Applications generally have numerous functions and deep hierarchies, especially super apps, which often require users to click multiple times to navigate through deeper levels of pages. Hierarchy refers to the layered structure between different pages within an application. Generally, the homepage is the highest-level page (e.g., the first level). The homepage can link to one or more subpages (e.g., subpage A), meaning users can access subpage A from the homepage. Subpage A can be a second-level page. A subpage A (e.g., subpage A1) can also link to one or more subpages (e.g., subpage B), meaning subpage B is a subpage of subpage A1, and users can access subpage B from subpage A1. Subpage B can be a third-level page. Subpage B can also have its own subpages, and so on.
[0145] After browsing deeply nested pages within an application, users often need to perform multiple clicks to revisit those pages. For example, after browsing a subpage (e.g., subpage b1 of subpage a1), if a user continues browsing another subpage a (e.g., subpage a2) and wants to revisit subpage b1, they must first click the "back" button on subpage a2 to return to the first-level homepage, then click to access subpage a1 on the homepage, and finally click to access subpage b1 within subpage a1. This cumbersome process results in a poor user experience.
[0146] To address the aforementioned problems, embodiments of this application provide an application display method, a terminal device, and a computer program product. In this method, when the terminal device displays the first page of a first application in a first window, if a user wants to view a next-level page (e.g., a second page), the user can perform an operation (e.g., a click) on the first page. Based on the user's operation on the first page, the terminal device can display the second page of the first application in the first window. When the terminal device displays the second page in the first window, if the user wants to save the second page for later viewing, the user can perform a first target operation in the first window. After detecting the first target operation on the first window, the terminal device can load the second page into the second window and display the first page of the first application in the first window.
[0147] In this embodiment of the application, when a user browses a certain page of the first application, the user can perform a corresponding target operation on the first window to load the page displayed in the first window into other windows. That is, the pages that the user has browsed can be loaded into other windows, so that the pages that the user has browsed can be saved through other windows. Thus, the saved pages can be quickly displayed through other windows, eliminating the need for the user to go through the hierarchy to find the page they want to view. This simplifies the operation of the user to view the pages they have browsed, improves the user experience, and has strong usability and practicality.
[0148] In this application embodiment, the terminal device can be a mobile phone, tablet computer, smart screen, wearable device, in-vehicle device, augmented reality (AR) / virtual reality (VR) device, smart speaker, laptop computer, ultra-mobile personal computer (UMPC), netbook, personal digital assistant (PDA), or desktop computer, etc., and there are no restrictions on the specific type of terminal device in this application embodiment.
[0149] The following first introduces the terminal device involved in the embodiments of this application. Please refer to FIG1, which shows a schematic diagram of a structure of terminal device 100.
[0150] Terminal device 100 may 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, antenna 1, antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor module 180, buttons 190, a camera 191, and a display screen 192, etc. Among them, sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer 180E, a proximity 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, etc.
[0151] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the terminal device 100. In other embodiments of this application, the terminal device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.
[0152] Processor 110 may include one or more processing units, such as application processors (APs), modem processors, graphics processing units (GPUs), image signal processors (ISPs), controllers, video codecs, digital signal processors (DSPs), baseband processors, and / or neural network processing units (NPUs). These different processing units may be independent devices or integrated into one or more processors.
[0153] The controller can generate operation control signals based on the instruction opcode and timing signals to complete the control of instruction fetching and execution.
[0154] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.
[0155] In some embodiments, the processor 110 may include one or more interfaces. Interfaces may 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 subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.
[0156] It is understood that the interface connection relationships between the modules illustrated in the embodiments of this application are merely illustrative and do not constitute a structural limitation on the terminal device 100. In other embodiments of this application, the terminal device 100 may also adopt different interface connection methods or a combination of multiple interface connection methods as described in the above embodiments.
[0157] The charging management module 140 is used to receive charging input from the charger.
[0158] The power management module 141 connects the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, providing power to the processor 110, internal memory 121, display screen 192, camera 191, and wireless communication module 160, etc. The wireless communication function of the terminal device 100 can be implemented through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor, and baseband processor, etc.
[0159] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in terminal device 100 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, 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 conjunction with a tuning switch.
[0160] The mobile communication module 150 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the terminal device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be housed in the same device.
[0161] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the 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. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs sound signals through audio devices (not limited to speaker 170A, receiver 170B, etc.) or displays images or videos through the display screen 192. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 110 and may be housed in the same device as the mobile communication module 150 or other functional modules.
[0162] The wireless communication module 160 can provide solutions for wireless communication applications on the terminal device 100, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.
[0163] In some embodiments, antenna 1 of terminal device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling terminal device 100 to communicate with networks and other devices via wireless communication technology. The wireless communication technology may 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 may include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and / or satellite-based augmentation systems (SBAS).
[0164] Terminal device 100 implements display functions through a GPU, display screen 192, and application processor. The GPU is a microprocessor for image processing, connected to the display screen 192 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.
[0165] The display screen 192 is used to display images, videos, etc. The display screen 192 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 flexible light-emitting diode (FLED), a Miniled LED, a MicroLED, a Micro-OLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the terminal device 100 may include one or N display screens 192, where N is a positive integer greater than 1.
[0166] Terminal device 100 can perform shooting functions through ISP, camera 191, video codec, GPU, display 192 and application processor.
[0167] The ISP is used to process the data fed back by the camera 191.
[0168] Camera 191 is used to capture still images or videos. In some embodiments, terminal device 100 may include one or N cameras 191, where N is a positive integer greater than 1.
[0169] A digital signal processor (DSP) is used to process digital signals. Besides digital image signals, it can also process other digital signals. For example, when terminal device 100 selects a frequency, the DSP can perform Fourier transforms on the frequency energy.
[0170] Video codecs are used to compress or decompress digital video. Terminal device 100 may support one or more video codecs. Thus, terminal device 100 can play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG 2, MPEG 3, MPEG 4, etc.
[0171] NPU stands for Neural Network (NN) Computing Processor. By borrowing the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it can rapidly process input information and continuously learn on its own. NPUs enable intelligent cognitive applications in terminal devices, such as image recognition, facial recognition, speech recognition, and text understanding.
[0172] The external storage interface 120 can be used to connect an external storage card, such as a Micro SD card, to expand the storage capacity of the terminal device 100. The external storage card communicates with the processor 110 through the external storage interface 120 to perform data storage functions. For example, music, video, and other files can be saved on the external storage card.
[0173] Internal memory 121 can be used to store computer executable program code, which includes instructions. Internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of terminal device 100 (such as audio data, phonebook, etc.). Furthermore, internal memory 121 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc. Processor 110 executes various functional applications and data processing of terminal device 100 by running instructions stored in internal memory 121 and / or instructions stored in memory located in the processor.
[0174] Terminal device 100 can implement audio functions, such as music playback and recording, through audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and application processor.
[0175] Audio module 170 is used to convert digital audio information into analog audio signal output, and also to convert analog audio input into digital audio signal. Audio module 170 can also be used for audio signal encoding and decoding. Speaker 170A, also called a "loudspeaker," is used to convert audio electrical signals into sound signals. Receiver 170B, also called a "handset," is used to convert audio electrical signals into sound signals. Microphone 170C, also called a "microphone" or "microphone unit," is used to convert sound signals into electrical signals. Headphone jack 170D is used to connect wired headphones.
[0176] Buttons 190 include a power button, volume buttons, etc. Buttons 190 can be mechanical buttons or touch-sensitive buttons. Terminal device 100 can receive button input and generate key signal inputs related to user settings and function control of terminal device 100.
[0177] The software system of terminal device 100 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. For example, the software system of terminal device 100 can adopt a layered architecture such as Android operating system (OS), Harmony OS, or iOS. This application embodiment uses a layered architecture as an example to illustrate the software structure of terminal device 100.
[0178] Figure 2 is a software structure block diagram of the terminal device 100 according to an embodiment of this application.
[0179] A layered architecture divides software into several layers, each with a clear role and function. Layers communicate with each other through software interfaces. In some embodiments, the operating system is divided into four layers, from top to bottom: the application layer, the application framework layer, the runtime and system libraries, and the kernel layer.
[0180] The application layer can include a series of application packages.
[0181] As shown in Figure 2, the application package may include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, and SMS.
[0182] In some embodiments, the application display provided in this application can be a system function provided by a terminal device. The terminal device can provide relevant interfaces to the application, allowing the application to call the system function through these interfaces. Additionally, developers can adapt the application during development to determine if it supports multi-window display. When the application supports multi-window display, developers can identify the specific pages within the application that support it. For example, when a developer determines that an application supports multi-window display, they can add corresponding declaration information to the application. This declaration information can indicate whether the application supports multi-window display and which pages within the application support it. In other words, when it is determined that an application needs to support multi-window display, developers only need to perform simple adaptation, which is straightforward and requires minimal work, effectively extending the application to support multi-window display.
[0183] After a terminal device launches an application, it can display the application's page and menu bar. Additionally, the terminal device can read the application's declaration information and determine whether the application supports multi-window display. If the application supports multi-window display, the multi-window display menu item in the window control menu will be triggerable when the terminal device displays the menu based on user actions on the menu bar. This means that while browsing the application's page, the user can initiate multi-window display by triggering the corresponding menu item. Conversely, if the application does not support multi-window display, the multi-window display menu item will be untriggerable, meaning that while browsing the application's page, the user cannot trigger the multi-window display menu item, thus preventing multi-window display from being initiated.
[0184] The application framework layer provides application programming interfaces (APIs) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.
[0185] As shown in Figure 2, the application framework layer may include a window manager, content provider, view system, phone manager, resource manager, notification manager, system management module, etc.
[0186] The window manager is used to manage windowed applications. It can retrieve screen size, determine the presence of a status bar, lock the screen, and capture screenshots, among other things.
[0187] Content providers store and retrieve data, making that data accessible to applications. This data may include videos, images, audio, made and received phone calls, browsing history and bookmarks, phone books, etc.
[0188] A view system includes visual controls, such as controls for displaying text and controls for displaying images. View systems can be used to build applications. A display interface can consist of one or more views. For example, a display interface including a text notification icon could include views for displaying text and views for displaying images.
[0189] The phone manager is used to provide communication functions for terminal device 100. For example, it manages call status (including connection, hang-up, etc.).
[0190] The file explorer provides applications with various resources, such as localized strings, icons, images, layout files, video files, and more.
[0191] The notification manager allows applications to display notifications in the status bar. These notifications can be used to deliver informational messages and can disappear automatically after a short pause, requiring no user interaction. For example, the notification manager can be used to notify users of download completion or message alerts. The notification manager can also display notifications as icons or scrolling text in the top status bar, such as notifications from background applications, or as dialog boxes on the screen. Examples include displaying text messages in the status bar, emitting sounds, vibrating the device, and flashing indicator lights.
[0192] The system management module can include the ArKUI development framework, meta-capabilities, and intelligent multi-window functionality. ArKUI can integrate multi-window controls and page stacks to control entry into multi-window display. Meta-capabilities can include ability initiation and indexing mechanisms. Intelligent multi-window functionality can include in-application multi-window (i.e., multi-window display within the application) and spatial windows. When entering multi-window display, i.e., when a specific page of the application needs to be displayed through another window, an ability can be initiated to create a window and establish a corresponding page stack for that ability (i.e., that window). Based on the indexing mechanism and the page stack corresponding to that window, the page is displayed within that window. In other words, during multi-window display, each newly created window can correspond to an independent page stack, resulting in a shallower page stack for each newly created window. This allows for quick display of the page the user wants to view through various windows and enables cross-level page interaction within the application. Furthermore, data across windows within the same application can be shared in real time. This means that when data in a page displayed in one window is updated, the data displayed in other windows will also be updated accordingly, ensuring data consistency and up-to-dateness across multiple windows. In other words, the system management module can implement multi-window functionality within the application based on meta-capabilities (ability and index) and the intelligent multi-window mechanism.
[0193] It should be understood that the processes corresponding to each window can be managed independently.
[0194] The page stack manages the order and state of pages as the user navigates within an application, ensuring that the user can move forward, backward, and return to specific pages as expected. The page stack typically uses a Last-In-First-Out (LIFO) principle to manage pages within the application. When a user navigates to a new page, that page (usually its identifier) is pushed onto (or saved to) the top of the stack; when the user returns to the previous page, the page at the top of the stack (i.e., the page identifier) is popped out to display the previous page. In the embodiments described in this application, the page saved in the page stack can refer to the page identifier.
[0195] For example, please refer to Figure 3, which shows an example diagram of the page stack provided in an embodiment of this application.
[0196] After launching an application, the terminal device can create a main window and display the application's pages through it. Additionally, the terminal device can create a page stack corresponding to the main window. When a user browses the application's pages through the main window, the terminal device can manage the pages displayed in the main window using the corresponding page stack. For example, as shown in Figure 3(a), when the user browses page 1--page 2--page 3 sequentially through the main window, the page stack corresponding to the main window can sequentially include page 1--page 2--page 3 from bottom to top.
[0197] In one embodiment, when a page of the application is displayed in the main window, if the user triggers multi-window display, the terminal device can create a secondary window and establish a page stack corresponding to that secondary window. Furthermore, the terminal device can push the page onto the page stack corresponding to the secondary window to manage the pages within that secondary window through that page stack.
[0198] For example, when page 1 is displayed in the main window, if the user triggers multi-window display, the terminal device can create a secondary window (e.g., secondary window 1) to display page 1. Additionally, the terminal device can establish a page stack corresponding to secondary window 1 to manage the pages within secondary window 1. For example, as shown in Figure 3(a), the page stack corresponding to secondary window 1 can include page 1.
[0199] Similarly, when page 2 is displayed in the main window, if the user triggers multi-window display, the terminal device can create a secondary window (e.g., secondary window 2) to display page 2. Additionally, the terminal device can establish a page stack corresponding to secondary window 2 to manage the pages within secondary window 2. For example, as shown in Figure 3(a), the page stack corresponding to secondary window 2 can include page 2.
[0200] Similarly, when page 3 is displayed in the main window, if the user triggers multi-window display, the terminal device can create a secondary window (e.g., secondary window 3) to display page 3. Additionally, the terminal device can establish a page stack corresponding to secondary window 3 to manage the pages within secondary window 3. For example, as shown in Figure 3(a), the page stack corresponding to secondary window 3 may include page 3.
[0201] In another embodiment, when a page of the application is displayed in the main window, if the user triggers multi-window display, the terminal device can create a secondary window and establish a page stack corresponding to that secondary window. After establishing the page stack corresponding to the secondary window, the terminal device can first push the application's home page onto the page stack corresponding to the secondary window. Subsequently, the terminal device can push that page onto the page stack corresponding to the secondary window.
[0202] For example, when page 1 (e.g., the application's homepage) is displayed in the main window, if the user triggers multi-window display, the terminal device can create a secondary window (e.g., secondary window 1) and establish a page stack corresponding to secondary window 1. After establishing the page stack corresponding to secondary window 1, the terminal device can first push the application's homepage (e.g., page 1) onto the page stack corresponding to secondary window 1. Since page 1 has already been pushed onto the page stack corresponding to secondary window 1, the terminal device can perform the push operation of page 1 onto the stack again without being based on the multi-window display trigger operation, that is, as shown in Figure 3(b), the page stack corresponding to secondary window 1 can include page 1.
[0203] Similarly, when page 2 is displayed in the main window, if the user triggers multi-window display, the terminal device can create a secondary window (e.g., secondary window 2) and establish a page stack corresponding to secondary window 2. After establishing the page stack corresponding to secondary window 2, the terminal device can first push the application's home page (e.g., page 1) onto the page stack corresponding to secondary window 2. Subsequently, based on the multi-window display trigger operation, the terminal device can push page 2 onto the page stack corresponding to secondary window 2, as shown in Figure 3(b). The page stack corresponding to secondary window 2 can sequentially include page 1 to page 2 from the bottom to the top.
[0204] Similarly, when page 3 is displayed in the main window, if the user triggers multi-window display, the terminal device can create a secondary window (e.g., secondary window 3) and establish a page stack corresponding to secondary window 3. After establishing the page stack corresponding to secondary window 3, the terminal device can first push the application's home page (e.g., page 1) onto the page stack corresponding to secondary window 3. Subsequently, based on the multi-window display trigger operation, the terminal device can push page 3 onto the page stack corresponding to secondary window 3, as shown in Figure 3(b). The page stack corresponding to secondary window 3 can sequentially include page 1 to page 3 from the bottom to the top.
[0205] As described above, when the application's pages are displayed in the main window, after triggering multi-window display, the terminal device can display the application's pages through one or more secondary windows. Each secondary window corresponds to an independent page stack, making the page stacks of each secondary window relatively shallow. This allows users to quickly view the pages they want, such as pages that have been previously viewed in deeper layers, without needing to delve into the layers to find the desired page. This simplifies the user experience of viewing previously viewed pages. Furthermore, multi-window display also allows users to simultaneously view pages across different layers of the application. For example, when the main window displays page 1 (the first layer), the terminal device can simultaneously display page 2 (the second layer), page 3 (the third layer), and page 4 (the fourth layer) through secondary windows, etc. This enables interaction between pages across different layers, facilitating collaborative operations between different pages within the same application.
[0206] It should be noted that the above-described method of pushing the page of an application onto the page stack of a secondary window when the user triggers multi-window display, or pushing the application's home page and the page thereon onto the page stack of a secondary window, is merely an illustrative explanation and should not be construed as a limitation on the embodiments of this application. In the embodiments of this application, when the user triggers multi-window display when the user triggers multi-window display while the application's page is displayed in the main window, the terminal device may also push all pages currently included in the page stack of the main window onto the page stack of the secondary window.
[0207] For example, when page 1 (e.g., the application's homepage) is displayed in the main window, if the user triggers multi-window display, the terminal device can create a secondary window (e.g., secondary window 1) and establish a page stack corresponding to secondary window 1. After establishing the page stack corresponding to secondary window 1, the terminal device can sequentially push all the pages currently included in the page stack corresponding to the main window into the page stack corresponding to secondary window 1. Since the page stack corresponding to the main window currently only includes page 1, the terminal device can push page 1 into the page stack corresponding to secondary window 1, as shown in Figure 3(c), the page stack corresponding to secondary window 1 can include page 1.
[0208] Similarly, after displaying page 1 in the main window, if the user triggers multi-window display when displaying page 2, the terminal device can create a secondary window (e.g., secondary window 2) and establish a page stack corresponding to secondary window 2. After establishing the page stack corresponding to secondary window 2, the terminal device can push all the pages currently included in the page stack corresponding to the main window into the page stack corresponding to secondary window 2 in sequence. For example, when the page stack corresponding to the main window includes pages 1 through 2 from bottom to top, the terminal device can first push page 1 into the page stack corresponding to secondary window 2, and then push page 2 into the page stack corresponding to secondary window 2, as shown in Figure 3(c). The page stack corresponding to secondary window 2 can include pages 1 through 2 from bottom to top.
[0209] Similarly, after displaying page 2 in the main window, when displaying page 3, if the user triggers multi-window display, the terminal device can create a secondary window (e.g., secondary window 3) and establish a page stack corresponding to secondary window 3. After establishing the page stack corresponding to secondary window 3, the terminal device can sequentially push all the pages currently included in the page stack corresponding to the main window into the page stack corresponding to secondary window 3. For example, when the page stack corresponding to the main window includes page 1--page 2--page 3 sequentially from bottom to top, the terminal device can first push page 1 into the page stack corresponding to secondary window 3, then push page 2 into the page stack corresponding to secondary window 3, and then push page 3 into the page stack corresponding to secondary window 3, as shown in Figure 3(c). The page stack corresponding to secondary window 3 can sequentially include page 1--page 2--page 3 from bottom to top.
[0210] Runtime consists of core libraries and a virtual machine. Runtime is responsible for the scheduling and management of the operating system.
[0211] The core library consists of two parts: one part is the functionalities that the Java language needs to call, and the other part is the core library of the operating system.
[0212] The application layer and application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.
[0213] System libraries can include multiple functional modules. For example: surface manager, media libraries, 3D graphics processing libraries (e.g., OpenGLES), 2D graphics engines (e.g., SGL), etc.
[0214] The Surface Manager is used to manage the display subsystem and provides the blending of 2D and 3D layers for multiple applications.
[0215] The media library supports playback and recording of various common audio and video formats, as well as still image files. It supports multiple audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG.
[0216] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.
[0217] A 2D graphics engine is a graphics engine for 2D drawing.
[0218] The kernel layer is the layer between hardware and software. The kernel layer contains at least the display driver, camera driver, audio driver, and sensor driver.
[0219] The following example, using application A which supports multi-window display, illustrates the user interface of the application display method provided in this application embodiment.
[0220] Please refer to Figures 4 to 6, which show a set of interface schematic diagrams provided in the embodiments of this application.
[0221] After a user launches application A on a terminal device, the terminal device can display the page of application A. For example, the terminal device can create a main window 400 and display the page of application A in the main window 400. The main window 400 can be a full-screen window. Alternatively, the main window 400 can be a non-full-screen window. The following example illustrates the scenario where the main window 400 is a full-screen window.
[0222] Specifically, when a terminal device displays a page (e.g., page a) of application A in the main window 400, the terminal device can display other pages of application A (e.g., pages one level below page a) in the main window 400 based on user actions on page a (e.g., click actions). It should be understood that when the terminal device creates the main window 400 to display pages of application A, the terminal device can establish a page stack corresponding to the main window 400 to manage the pages displayed in the main window 400.
[0223] When the main window 400 displays a page of application A (e.g., page a), the main window 400 can also display a menu bar 401. After the menu bar 401 is clicked, the terminal device can display the window control menu 402 corresponding to the main window 400. The window control menu 402 can include one or more menu items, such as "Multi-window within application," "Replace application," and "Close window." "Multi-window within application" can be used to display multiple pages of application A together with the main window 400 through one or more secondary windows. "Replace application" can be used to switch applications launched in the main window 400. That is, when a user wants to switch from application A launched in the main window 400 to another application (e.g., application B), the user can click "Replace application," and after clicking "Replace application," select application B to display the page of application B through the main window 400. "Close window" can be used to close the main window 400.
[0224] It should be understood that the menu bar 401 can be located anywhere on the main window 400. For example, as shown in Figure 4(a), the menu bar 401 can be located at the top of the main window 400. Alternatively, the menu bar 401 can also be located at the bottom, left, or right of the main window 400, or other locations. The following will illustrate this by taking the example of the menu bar 401 being located at the top of the main window 400.
[0225] When a user is browsing page a of application A, if the user wants to save page a temporarily, as shown in Figure 4(a), the user can click the menu bar 401 at the top of the main window 400. As shown in Figure 4(b), after the terminal device detects the click operation on the menu bar 401, it can display the window control menu 402, which can display menu items such as "Multi-window within application", "Replace application", and "Close window". After the terminal device displays the window control menu 402, as shown in Figure 4(b), the user can click "Multi-window within application" to save page a temporarily for later viewing.
[0226] Alternatively, when a user is browsing page a of application A, if the terminal device determines that page a can be temporarily saved to a secondary window for display, the terminal device can display a prompt message. This prompt message can be used to suggest that the user can save page a for display in a secondary window. For example, as shown in Figure 4(c), the terminal device can display a pop-up window 500. Pop-up window 500 may include the prompt message "Page a can be displayed in a secondary window. Do you want to save page a?", as well as a confirmation button 510 and a cancel button 520. The confirmation button 510 can be used to confirm saving page a, and the cancel button 520 can be used to refuse saving page a. As shown in Figure 4(c), when the user wants to save page a, the user can click the confirmation button 510. The following description will use the example of saving a page through clicking on an "in-application multi-window" as an example.
[0227] It should be understood that whether page A can be temporarily stored can be determined based on the declaration information corresponding to application A. That is, when developers are developing application A, if they determine that application A supports multi-window display, they can adapt application A, for example, by using declaration information to indicate that application A supports multi-window display and the pages that application A supports for multi-window display. The terminal device can determine whether page A can be temporarily stored based on the declaration information corresponding to application A.
[0228] As shown in Figure 4(d), after the terminal device detects a click on "In-Application Multi-Window" or a click on the confirmation button 510, it can create a secondary window (e.g., the primary window) 410 for displaying page a, load page a into the primary window 410, and shrink the size of the main window 400, reducing the full-screen main window 400 to a non-full-screen window. Subsequently, the terminal device can display the shrunken main window 400 in display area a and the primary window 410 in display area b, thus displaying page a through the primary window 410 in display area b. Display areas a and b do not need to overlap.
[0229] It should be noted that when the terminal device creates the first requested window 410, it can establish a corresponding page stack for the first requested window 410, and the page stack corresponding to the first requested window 410 is independent of the page stack corresponding to the main window 400. That is, operations performed on the page displayed in the main window 400 will not affect the page displayed in the first requested window 410. Similarly, operations performed on the page displayed in the first requested window 410 will not affect the page displayed in the main window 400.
[0230] After establishing the page stack corresponding to the first requesting window 410, the terminal device can push page a onto the page stack corresponding to the first requesting window 410. Alternatively, after establishing the page stack corresponding to the first requesting window 410, the terminal device can first push the home page of application A onto the page stack corresponding to the first requesting window 410, and then push page a onto the page stack corresponding to the first requesting window 410. Alternatively, after establishing the page stack corresponding to the first requesting window 410, the terminal device can sequentially push all the pages included in the page stack corresponding to the main window 400 onto the page stack corresponding to the first requesting window 410. It should be understood that after pushing page a onto the page stack corresponding to the first requesting window 410, the top element in the page stack corresponding to the first requesting window 410 can be page a.
[0231] Additionally, as shown in Figure 4(d), when displaying page a through the initial request window 410, the terminal device can display the parent page of page a, such as page b, in the shrunk main window 400. Page b can be a page included in the page stack corresponding to the main window 400. That is, when page a is pushed onto the page stack corresponding to the initial request window 410, the terminal device can pop page a from the page stack corresponding to the main window 400. After popping page a from the page stack corresponding to the main window 400, the top element in the page stack corresponding to the main window 400 can be the parent page of page a (e.g., page b). At this time, the main window 400 can display page b. Alternatively, the terminal device can continue to display the original page in the shrunk main window 400, that is, it can continue to display page a in the main window 400. In other words, when page a is pushed onto the page stack corresponding to the initial request window 410, the terminal device can keep the page stack corresponding to the main window 400 unchanged. In other words, when a user temporarily saves a page displayed in the main window 400 to a secondary window, the terminal device can load that page into the secondary window and can display the page one level above that page in the main window 400, or it can still display that page.
[0232] The following example illustrates how, when a page displayed in the main window 400 is temporarily saved to a secondary window, the terminal device displays the page one level above that page in the main window 400.
[0233] It should be noted that the parent page of a page displayed in the main window 400 can be a page that has been opened in the main window 400, that is, a page included in the page stack corresponding to the main window 400. Specifically, when loading a page displayed in the main window 400 into a secondary window, if that page has no parent page in the main window 400, meaning no other page in application A has been opened in the main window 400 before that page (e.g., the page is the top element of the page stack corresponding to the main window 400), the terminal device can still display that page in the main window 400. For example, when displaying the homepage of application A in the main window 400, since no other page in application A has been opened in the main window 400 before the homepage of application A (meaning the homepage of application A is the top element of the page stack corresponding to the main window 400), the terminal device can still display the homepage of application A in the main window 400 when loading the homepage of application A into a secondary window.
[0234] It should be understood that after detecting a click on "in-application multi-window" or a click on the confirmation button 510, the terminal device loads a page (e.g., page a) from the main window 400 into a secondary window (e.g., primary secondary window 410). Alternatively, it can be described that after detecting a click on "in-application multi-window" or a click on the confirmation button 510, the terminal device moves page a from the main window 400 to the primary secondary window 410. When moving page a from the main window 400 to the primary secondary window 410, the terminal device can remove page a from the main window 400 and load page a into the primary secondary window 410. Specifically, when moving page a from the main window 400 to the primary secondary window 410, page a can be removed from the page stack of the main window 400 and added to the page stack of the primary secondary window 410.
[0235] The sizes of display area a, display area b, the adjusted main window 400, and the initial window 410 can be determined according to the actual scenario, and this application embodiment does not impose any restrictions on this. For example, when a user browses the page of application A, the main window 400 can be the primary browsing window, and the initial window 410 can be the secondary browsing window. To facilitate the user's browsing of the page of application A and to facilitate the simultaneous display of the page through multiple secondary windows, as shown in Figure 4(d), the size of display area a can be larger than the size of display area b. The size of the main window 400 can be the same as the size of display area a. The size of the initial window 410 can be smaller than the size of display area b. For example, the width of the initial window 410 can be the same as the width of display area b, and the height of the initial window 410 can be less than half the height of display area b.
[0236] Furthermore, the specific position of window 410 within display area b can be determined based on the actual scenario, and this embodiment does not impose any restrictions on this. The position of the window within the display area can refer to the position of the window's center point, the position of the window's top (or bottom) edge, or the positions of multiple vertices of the window. The specific position can be determined based on the actual scenario, and this embodiment does not impose any restrictions on this. The following example illustrates the position of the window within the display area as the position of the window's center point.
[0237] For example, as shown in Figure 4(d), the initial request window 410 can be located in the middle of the display area b, meaning the terminal device can display the initial request window 410 in the middle of the display area b. Alternatively, the initial request window 410 can be located at the top (i.e., near the top of the display area b) or the bottom (i.e., near the bottom of the display area b), and so on. The following will illustrate this by taking the initial request window 410 being located in the middle of the display area b as an example.
[0238] As described above, the page stack corresponding to the first request window 410 is independent of the page stack corresponding to the main window 400. That is, operations performed on the pages displayed in the main window 400 will not affect the pages displayed in the first request window 410. Similarly, operations performed on the pages displayed in the first request window 410 will not affect the pages displayed in the main window 400.
[0239] For example, when the terminal device displays page b through the main window 400 and page a through the first request window 410, the user can open a new page in the first request window 410. The newly opened page can be displayed in the first request window 410, while the main window 400 can still display page b.
[0240] For example, when the terminal device displays page b through the main window 400 and page a through the first request window 410, as shown in Figure 5(a), when the user switches page b displayed in the main window 400 to another page of application A (e.g., page c), the page displayed in the first request window 410 may remain unchanged, that is, the first request window 410 may continue to display page a.
[0241] It should be understood that page c can be any page of application A. For example, page c can be N levels above page b, or page c can be M levels below page b, or page c can be a page at the same level as page b, and so on. Here, both N and M can be greater than or equal to 1. That is, when N=1, page c can be the page one level above page b. When N=2, page c can be the two levels above page b. Similarly, when M=1, page c can be the next level page of page b. When M=2, page c can be the two levels below page b.
[0242] As shown in Figure 5(a), when page c is displayed in the main window 400, if the user wants to continue saving page c, the user can click the menu bar 401 at the top of the main window 400. After the terminal device detects the click operation on the menu bar 401, it can display the window control menu 402.
[0243] After the page is temporarily saved, that is, after the main window 400 is reduced to a non-full-screen display, the terminal device can adjust the menu items included in the window control menu 402. For example, a "Full Screen" menu item can be added to the window control menu 402. "Full Screen" can be used to display the main window 400 in full screen to meet the user's need to view the main window 400 in full screen. For example, as shown in Figure 5(b), after the terminal device detects a click operation on the menu bar 401, it can display menu items such as "Multi-window within application", "Full Screen", "Replace application", and "Close window".
[0244] As shown in Figure 5(b), users can continue to click "In-App Multi-Window" to temporarily save page c for later viewing.
[0245] As shown in Figure 5(c), after the terminal device detects a click operation on "In-Application Multi-Window", it can create a secondary window (e.g., a second secondary window) 420 to display page c. Page c can be loaded into the second secondary window 420, and the second secondary window 420 can be displayed in the display area b, so that page c can be displayed through the second secondary window 420 in the display area b. When displaying page c through the second secondary window 420, the terminal device can display the parent page of page c (e.g., page d) in the main window 400, and can continue to display page a in the first secondary window 410. It should be understood that page d can be a page included in the page stack corresponding to the main window 400, that is, page d can be a page that has been opened in the main window 400. When page c has no parent page, that is, when no other page in application A has been opened in the main window 400 before page c, the terminal device can continue to display page c in the main window 400 when displaying page c through the second secondary window 420.
[0246] The second required window 420 does not overlap with the first required window 410. The size of the second required window 420 can be the same as or different from the size of the first required window 410. That is, the sizes of the secondary windows can be the same or different. The following will illustrate this by assuming that the sizes of the secondary windows are the same.
[0247] It should be understood that the specific position of the second window 420 in the display area b can be determined according to the actual scenario, and this application embodiment does not impose any restrictions on this.
[0248] For example, a terminal device can display multiple secondary windows in display area b from top to bottom, based on the page's temporary storage time from earliest to latest. The page's temporary storage time can refer to the time the user triggers the temporary storage of the page, or it can be the time the corresponding secondary window is created. The early or late temporary storage time can be determined based on the time elapsed since the current moment (e.g., the moment the second secondary window 420 is displayed). A shorter time elapsed since the current moment indicates a later temporary storage time; conversely, a longer time elapsed since the current moment indicates an earlier temporary storage time.
[0249] The earlier a page is stored, the higher its corresponding secondary window can be positioned within display area b; conversely, the later a page is stored, the lower its corresponding secondary window can be positioned within display area b. "Higher" in display area b means closer to the top of the display area b; "lower" means closer to the bottom of the display area b.
[0250] Since page a's temporary storage time is earlier than page c's temporary storage time, the terminal device can determine to display the first required window 410 corresponding to page a and the second required window 420 corresponding to page c from top to bottom in the display area b. That is, the terminal device can determine the position of the second required window 420 corresponding to page c in the display area b, which can be located below the position of the first required window 410 corresponding to page a in the display area b. For example, as shown in Figure 5(c), the terminal device can move the first required window 410 upwards to move the upper edge of the first required window 410, which is located in the middle, to a position at a preset threshold distance (e.g., preset threshold A) from the upper edge of the display area b, and can display the second required window 420 below the first required window 410. The preset threshold A can be determined according to the actual scenario, and this embodiment does not limit it. For example, the preset threshold A can be determined to be 0, or it can be determined to be any value such as 1 cm or 2 cm, depending on the actual scenario.
[0251] Alternatively, as shown in Figure 5(d), to improve the display effect, the primary window 410 and the secondary window 420 can be displayed as a whole in the middle of the display area b. That is, the distance between the upper edge of the primary window 410 and the upper edge of the display area b and the distance between the lower edge of the secondary window 420 and the lower edge of the display area b can be the same. Therefore, the terminal device can determine the preset threshold A based on the height of the display area b, the height of each secondary window, and the interval between the secondary windows. Based on the preset threshold A, the primary window 410 can be moved upwards, and the secondary window 420 can be displayed below the moved primary window 410. For example, when the height of the display area b is H0, the height of each secondary window is H1, and the interval between the secondary windows is H2, the terminal device can determine the preset threshold A = (H0 - 2 * H1 - H2) / 2. The height of each secondary window and the interval between the secondary windows can be determined according to the actual scenario.
[0252] For example, the terminal device can display multiple secondary windows in display area b from bottom to top, based on the page's storage time from earliest to latest. The earlier a page's storage time, the lower its corresponding secondary window can be in display area b; conversely, the later a page's storage time, the higher its corresponding secondary window can be in display area b. Since page a's storage time is earlier than page c's, the terminal device can determine to display the first secondary window 410 and the second secondary window 420 in display area b from bottom to top. That is, the terminal device can determine that the second secondary window 420 can be positioned above the first secondary window 410 in display area b. For example, the terminal device can move the first secondary window 410, currently in the middle of display area b, downwards and display the second secondary window 420 above it. It should be understood that the specific content of the first request window 410 when the terminal device moves down can be referred to the relevant content of the first request window 410 when the terminal device moves up. For the sake of brevity, it will not be repeated here.
[0253] The following example illustrates how the terminal device shown in Figure 5(d) displays multiple secondary windows in the display area b from top to bottom according to the page's temporary storage time, from earliest to latest.
[0254] It should be noted that when the terminal device creates the second request window 420, it can establish a corresponding page stack for the second request window 420. After establishing the page stack for the second request window 420, the terminal device can push page c onto the page stack for the second request window 420. Alternatively, after establishing the page stack for the second request window 420, the terminal device can first push the home page of application A onto the page stack for the second request window 420, and then push page c onto the page stack for the second request window 420. Alternatively, after establishing the page stack for the second request window 420, the terminal device can sequentially push all the pages included in the page stack corresponding to the main window 400 onto the page stack for the second request window 420. It should be understood that after pushing page c onto the page stack for the second request window 420, the top element of the page stack for the second request window 420 can be page c.
[0255] The page stack corresponding to the second request window 420 is independent of the page stack corresponding to the main window 400 and the page stack corresponding to the first request window 410. That is, operations performed on the pages displayed in the main window 400 or the first request window 410 will not affect the pages displayed in the second request window 420. Similarly, operations performed on the pages displayed in the second request window 420 will not affect the pages displayed in the main window 400 or the first request window 410.
[0256] For example, when a terminal device displays page d through the main window 400, page a through the first request window 410, and page c through the second request window 420, the user can open a new page in the first request window 410. The newly opened page can be displayed in the first request window 410, while the main window 400 can still display page d, and the second request window 420 can still display page c. Alternatively, the user can open a new page in the second request window 420. The newly opened page can be displayed in the second request window 420, while the main window 400 can still display page d, and the first request window 410 can still display page a.
[0257] For example, when the terminal device displays page d through the main window 400, page a through the first request window 410, and page c through the second request window 420, as shown in Figure 6(a), when the user switches page d displayed in the main window 400 to another page of application A (e.g., page e), the terminal device determines that the page displayed in the first request window 410 and the page displayed in the second request window 420 can remain unchanged. That is, the terminal device can continue to display page a through the first request window 410 and can continue to display page c through the second request window 420.
[0258] It should be understood that page e can be any page of application A. For example, page e can be a page N levels above page d, or a page M levels below page d, or a page at the same level as page d, and so on. Here, both N and M can be greater than or equal to 1.
[0259] As shown in Figure 6(a), when page e is displayed in the main window 400, if the user wants to continue saving page e, the user can click the menu bar 401 at the top of the main window 400. As shown in Figure 6(b), after the terminal device detects the click operation on the menu bar 401, it can display the window control menu 402. For example, the terminal device can display menu items such as "Multi-window within application", "Fullscreen window", "Replace application", and "Close window".
[0260] As shown in Figure 6(b), users can continue to click "Multi-window within the application" to temporarily save page e for later viewing.
[0261] After the terminal device detects a click operation on "In-Application Multi-Window", it can create a secondary window (e.g., a third secondary window) 430 to display page e. Page e can be loaded into the third secondary window 430, and the third secondary window 430 can be displayed in the display area b, so that page e can be displayed through the third secondary window 430 in the display area b. When displaying page e through the third secondary window 430 in the display area b, the terminal device can display the parent page of page e (e.g., page f) in the main window 400, and can display the continuation page a in the first secondary window 410, and the continuation page c in the second secondary window 420. The third secondary window 430 and the second secondary window 420 do not need to overlap, and the third secondary window 430 and the first secondary window 410 do not need to overlap. Page f can be a page included in the page stack corresponding to the main window 400, that is, page f can be a page that has been opened in the main window 400. When page e has no parent page, that is, when no other page in application A has been opened in the main window 400 before page f, the terminal device can continue to display page e in the main window 400 when page e is displayed in the third main window 430.
[0262] It should be understood that since page e's temporary storage time is later than page c's, when multiple secondary windows are displayed from top to bottom in display area b according to the page's temporary storage time from earliest to latest, the terminal device can determine that the third secondary window 430 can be positioned below the second secondary window 420 in display area b. For example, if there is a blank area above the first secondary window 410 in display area b, and the third secondary window cannot be fully displayed below the second secondary window 420, the terminal device can move the first secondary window 410 and the second secondary window 420 upwards, and can display the third secondary window 430 below the moved second secondary window 420.
[0263] In one embodiment, when the lower portion of the moved second window 420 cannot fully display the third window 430, as shown in FIG6(c), the terminal device may display only a portion of the third window 430 in the display area b. It should be understood that when the lower portion of the second window 420 cannot fully display any content of the third window 430, the terminal device may not display the third window 430 in the display area b.
[0264] When the terminal device displays a portion of the third window 430 or does not display the third window 430 in the display area b, if the user wants to view the third window 430, the user can perform a preset operation (such as an upward swipe operation) in the display area b to move the window in the display area b upward, so that the third window 430 is gradually displayed completely in the display area b.
[0265] For example, as shown in Figure 6(c), when the terminal device only displays a portion of the third request window 430 in display area b, if the user wants to view the complete third request window 430, the user can perform an upward swipe operation in display area b. As shown in Figure 6(d), after the terminal device detects the upward swipe operation in display area b, it can move each window in display area b (i.e., the first request window 410, the second request window 420, and the third request window 430) upward, so that the third request window 430 can be gradually and completely displayed in display area b, making it convenient for the user to view.
[0266] In another embodiment, when the third request window 430 cannot be fully displayed below the second request window 420, the terminal device can move each window in the display area b (i.e., the first request window 410 and the second request window 420) upwards, so that there is enough area in the display area b to fully display the third request window 430, thereby allowing the latest temporary page to be fully displayed in the display area b, making it convenient for the user to view the latest temporary page.
[0267] When the third requested window 430 is fully displayed in display area b, the first requested window 410 may not be fully displayed in display area b, as shown in Figure 6(d). The terminal device may display only a portion of the first requested window 410. Alternatively, the terminal device may not display the first requested window 410 in display area b. When the terminal device displays a portion of the first requested window 410 or does not display the first requested window 410 in display area b, if the user wants to view the first requested window 410, the user can perform a preset operation (such as a downward swipe operation) in display area b. After the terminal device detects the downward swipe operation in display area b, it can move each window in display area b (i.e., the first requested window 410, the second requested window 420, and the third requested window 430) downwards, so that the first requested window 410 can be gradually fully displayed in display area b.
[0268] In other words, multiple secondary windows displayed in display area b can be browsed by swiping through preset operations (such as swiping up or swiping down).
[0269] It should be understood that when the terminal device creates the third request window 430, it can establish a corresponding page stack for the third request window 430. After establishing the page stack corresponding to the third request window 430, the terminal device can push page e onto the page stack corresponding to the third request window 430. Alternatively, after establishing the page stack corresponding to the third request window 430, the terminal device can first push the home page of application A onto the page stack corresponding to the third request window 430, and then push page e onto the page stack corresponding to the third request window 430. Alternatively, after establishing the page stack corresponding to the third request window 430, the terminal device can sequentially push all the pages included in the page stack corresponding to the main window 400 onto the page stack corresponding to the third request window 430. It should be understood that after pushing page e onto the page stack corresponding to the third request window 430, the top element of the page stack corresponding to the third request window 430 can be page e.
[0270] The page stack corresponding to the third request window 430 is independent of the page stacks corresponding to the main window 400, the first request window 410, and the second request window 420. That is, operations performed on the pages displayed in the main window 400, the first request window 410, or the second request window 420 will not affect the pages displayed in the third request window 430. Similarly, operations performed on the pages displayed in the third request window 430 will not affect the pages displayed in the main window 400, the first request window 410, or the second request window 420.
[0271] It should be noted that when displaying a user-stored page through secondary windows such as the primary window 410, secondary window 420, or tertiary window 430, each secondary window may also include a menu bar. After the menu bar of a secondary window is clicked, the terminal device can display the window control menu corresponding to that secondary window. The window control menu corresponding to that secondary window includes one or more menu items, such as "Multi-window within application," "Fullscreen window," "Replace application," and "Close window." "Multi-window within application" can be used to temporarily store the page displayed in this secondary window through other secondary windows. "Fullscreen window" can be used to display the secondary window in fullscreen mode. "Replace application" can be used to switch the application launched in this secondary window, i.e., it can be used to switch the currently launched application A. "Close window" can be used to close this secondary window. Users can click the menu bar corresponding to a secondary window to display the window control menu corresponding to that secondary window and perform related operations on the menu items in the window control menu to operate that secondary window.
[0272] For example, when displaying a user-stored page through secondary windows such as primary window 410, secondary window 420, or tertiary window 430, if the user clicks "Switch Application" in the window control menu 402 corresponding to the main window 400, or clicks "Switch Application" in the window control menu corresponding to a secondary window, to switch to another application (e.g., application B), the terminal device can exit multi-window display and display the page of application B through the main window 400. For example, the page of application B can be displayed through the full-screen main window 400. If application B supports multi-window display, when displaying the page of application B through the main window 400, the terminal device can also display a menu bar 401 in the main window 400, allowing the user to use the menu bar 401 displayed in the main window 400 to perform multi-window display of application B.
[0273] Please refer to Figure 7, which shows another set of interface diagrams provided in the embodiments of this application.
[0274] As shown in Figure 7(a), when the terminal device displays page b through the main window 400 and page a through the first-request window 410, the first-request window 410 may also include a menu bar 411. The menu bar 411 can be located at any position on the first-request window 410. For example, as shown in Figure 7(a), the menu bar 411 can be located at the top of the first-request window 410. Alternatively, the menu bar 411 can also be located at the bottom, left, or right of the first-request window 410, or other positions. The following will illustrate this by taking the example of the menu bar 411 being located at the top of the first-request window 410.
[0275] As shown in Figure 7(a), when page a is displayed through the initial request window 410, the user can also click the menu bar 411 at the top of the initial request window 410. As shown in Figure 7(b), after the terminal device detects the click operation on the menu bar 411, it can display the window control menu 412. For example, the window control menu 412 can be displayed in the initial request window 410. The window control menu 412 may include menu items such as "Multiple windows within an application", "Full screen window", "Replace application", and "Close window".
[0276] As shown in Figure 7(b), the user can click "In-application Multi-window" in the window control menu 412 to temporarily save the page a that is first displayed in window 410.
[0277] After the terminal device detects a click on "In-Application Multi-Window" in the window control menu 412, it can create a secondary window (e.g., a fourth secondary window 440) to display page a. Page a can be loaded into the fourth secondary window 440, and the fourth secondary window 440 can be displayed in the display area b, allowing page a to be displayed through the fourth secondary window 440. While page a is displayed through the fourth secondary window 440, the terminal device can continue to display page b in the main window 400. That is, the "In-Application Multi-Window" operation performed on the primary window 410 will not affect the page displayed in the main window 400.
[0278] As shown in Figure 7(c), when the page stack corresponding to the first request window 410 only includes page a, when page a is displayed through the fourth request window 440, the terminal device can continue to display page a in the first request window 410.
[0279] Alternatively, as shown in Figure 7(d), when the page stack corresponding to the first request window 410 includes the homepage of application A and page a from bottom to top, the terminal device can display the homepage of application A in the first request window 410 when displaying page a through the fourth request window 440. That is, when page a is loaded into the fourth request window 440, the terminal device can pop page a from the page stack corresponding to the first request window 410. At this time, the top element of the page stack corresponding to the first request window 410 can be the homepage of application A. Therefore, the terminal device can display the homepage of application A in the first request window 410.
[0280] Alternatively, as shown in Figure 7(e), when the page stack corresponding to the first request window 410 includes all pages in the page stack corresponding to the main window 400, when displaying page a through the fourth request window 440, the terminal device can display the page one level above page a (e.g., page b) in the first request window 410. That is, when page a is loaded into the fourth request window 440, the terminal device can pop page a from the page stack corresponding to the first request window 410. At this time, the top element of the page stack corresponding to the first request window 410 is page b. Therefore, the terminal device can display page b in the first request window 410. Where, when page a is loaded into the fourth request window 440, if the page stack corresponding to the first request window 410 only contains page a, when displaying page a through the fourth request window 440, the first request window 410 can continue to display page a.
[0281] It should be noted that when the terminal device creates the fourth secondary window 440, it can establish a corresponding page stack for the fourth secondary window 440. After establishing the page stack corresponding to the fourth secondary window 440, the terminal device can push page a onto the page stack corresponding to the fourth secondary window 440. Alternatively, after establishing the page stack corresponding to the fourth secondary window 440, the terminal device can first push the home page of application A onto the page stack corresponding to the fourth secondary window 440, and then push page a onto the page stack corresponding to the fourth secondary window 440. Alternatively, after establishing the page stack corresponding to the fourth secondary window 440, the terminal device can sequentially push all the pages included in the page stack corresponding to the first secondary window 410 onto the page stack corresponding to the fourth secondary window 440. It should be understood that after pushing page a onto the page stack corresponding to the fourth secondary window 440, the top element of the page stack corresponding to the fourth secondary window 440 can be page a.
[0282] The page stack corresponding to the fourth secondary request window 440 is independent of the page stack corresponding to the main window 400 and the page stack corresponding to the first request window 410. That is, operations performed on the pages displayed in the main window 400 or the first request window 410 will not affect the pages displayed in the fourth secondary request window 440. Similarly, operations performed on the pages displayed in the fourth secondary request window 440 will not affect the pages displayed in the main window 400 or the first request window 410.
[0283] It should be understood that the terminal device displays the content of the fourth secondary window 440 in display area b based on the user's click operation on "Multi-window within application" in the window control menu 412. This can be compared to the aforementioned display of the content of the second secondary window 420 in display area b based on the user's click operation on "Multi-window within application" in the window control menu 402. For simplicity, this will not be repeated here. For example, as shown in Figure 7(c), the terminal device can move the first secondary window 410, located in the middle of display area b, upwards, and display the fourth secondary window 440 below the moved first secondary window 410. The first secondary window 410 and the fourth secondary window 440 are displayed as a whole in the middle of display area b.
[0284] After displaying page a through the fourth secondary window 440, the user can continue to temporarily save the page displayed in the main window 400 or any secondary window, and can display the saved page in the display area b through a newly created secondary window (e.g., the fifth secondary window). For example, the terminal device can display the fifth secondary window below the fourth secondary window 440. The specific content of the fifth secondary window displayed by the terminal device in the display area b can be referred to the relevant content of the third secondary window 430 displayed by the terminal device in the display area b, and will not be repeated here.
[0285] In this embodiment of the application, when the terminal device displays multiple pages of application A simultaneously through multiple request windows, for example, as shown in Figure 6(c), when the terminal device displays page f through the main window 400 in display area a, and displays page a through the first request window 410, page c through the second request window 420, and page e through the third request window 430 in display area b, the terminal device can adjust the display state of the windows based on the user's relevant operations.
[0286] Please refer to Figure 8, which shows another set of interface diagrams provided in the embodiments of this application.
[0287] As shown in Figure 8(a), when the terminal device displays page f in display area a via the main window 400, and displays page a via the first secondary window 410, page c via the second secondary window 420, and page e via the third secondary window 430 in display area b, if the user wants to adjust the display order of the secondary windows in display area b, for example, if the user wants to swap the display order between the first secondary window 410 and the second secondary window 420, the user can perform a preset operation in display area b (e.g., long-pressing the first secondary window 410 and dragging it to the position of the second secondary window 420, or long-pressing the second secondary window 420 and dragging it to the position of the first secondary window 410). Long-pressing the first secondary window 410 can be done at any position. Similarly, long-pressing the second secondary window 420 can be done at any position. Figure 8(a) illustrates this by taking the example of long-pressing the menu bar of the second desired window 420 and dragging the second desired window 420 to the position of the first desired window 410.
[0288] As shown in Figure 8(b), after the terminal device detects the operation of long-pressing the second request window 420 and dragging the second request window 420 to the position of the first request window 410, it can adjust the positions of the first request window 410 and the second request window 420 in the display area b. That is, the second request window 420 can be adjusted to the original position of the first request window 410, and the first request window 410 can be adjusted to the original position of the second request window 420, so that the display area b displays the second request window 420--first request window 410--third request window 430 from top to bottom.
[0289] Please refer to Figure 9, which shows another set of interface diagrams provided in the embodiments of this application.
[0290] As shown in Figure 9(a), when the terminal device displays page f in display area a through the main window 400, and displays page a through the first request window 410, page c through the second request window 420, and page e through the third request window 430 in display area b, when the user wants to swap a certain request window in display area b with the main window 400 in display area a, that is, when the user wants to display the page displayed in a certain request window through a larger window to facilitate viewing the temporary page, for example, when the user wants to swap the second request window 420 with the main window 400, the user can perform a preset operation in the second request window 420 or the main window 400 (such as double-clicking the second request window 420, or long-pressing the second request window 420 and dragging the second request window 420 to the position of the main window 400, or long-pressing the main window 400 and dragging the main window 400 to the position of the second request window 420). The double-clicking of the second window 420 can be done at any location. Figure 9(a) illustrates this by taking the location of the menu bar when the second window 420 is double-clicked as an example.
[0291] As shown in Figure 9(b), after the terminal device detects the double-click operation of the second window 420, it can swap the second window 420 with the main window 400 so that the second window 420 is displayed in the original position of the main window 400, i.e., page c, and the main window 400 is displayed in the original position of the second window 420, i.e., page f. When swapping windows, the terminal device can adjust the size of the secondary window 420 and the page c according to the original size of the main window 400. For example, the size of the secondary window 420 and the page c can be adjusted to the original size of the main window 400, and the adjusted secondary window 420 can be displayed in the original position of the main window 400, so that the adjusted page c can be displayed through the adjusted secondary window 420. Similarly, the size of the main window 400 and the page f can be adjusted according to the original size of the secondary window 420. For example, the size of the main window 400 and the page f can be adjusted to the original size of the secondary window 420, and the adjusted secondary window 420 can be displayed in the original position of the secondary window 420, so that the adjusted page f can be displayed through the adjusted main window 400.
[0292] It should be noted that the above-described method of swapping a secondary window with the main window via double-click or drag-and-drop is merely illustrative and should not be construed as a limitation of the embodiments of this application. In the embodiments of this application, the operation of swapping a secondary window with the main window can be determined according to the actual scenario. For example, the window control menu corresponding to each secondary window may include a menu item for swapping with the main window (e.g., "Swap with Main Window"). When a user wants to swap a secondary window with the main window, the user can click "Swap with Main Window" in the window control menu corresponding to that secondary window. After the terminal device detects the click operation of "Swap with Main Window", it can swap the secondary window with the main window.
[0293] Please refer to Figure 10, which shows another set of interface diagrams provided in the embodiments of this application.
[0294] As shown in Figure 10(a), when the terminal device displays page f in display area a through the main window 400 and displays pages in display area b through one or more secondary windows—for example, displaying page a through the first secondary window 410, page c through the second secondary window 420, and page e through the third secondary window 430 in display area b—a horizontal bar 1000 can be set between display area a and display area b. For example, the horizontal bar 1000 can be set at the right edge of the main window 400. The horizontal bar 1000 can be dragged to change the ratio between display area a and display area b. That is, the user can adjust the size of display area a and display area b by dragging the horizontal bar 1000. For example, the user can drag the horizontal bar 1000 to the left to shrink the size of display area a and increase the size of display area b. For example, the user can drag the horizontal bar 1000 to the right to increase the size of display area a and shrink the size of display area b.
[0295] In one embodiment, when dragging the horizontal bar 1000 to the left, the adjusted sizes of display area a and display area b can be set by the terminal device by default. For example, the terminal device can set the adjusted sizes of display area a and display area b to be the same by default. That is, after detecting an operation of dragging the horizontal bar 1000 to any position on the display interface, the terminal device can adjust the sizes of display area a and display area b to be the same size, so as to adjust the display interface to a dual-screen mode (i.e., a mode in which the two display areas are the same size) to display the main window 400 and the secondary window, which can facilitate the user to compare and view the page displayed in the main window 400 and the page displayed in the secondary window.
[0296] In another embodiment, when the horizontal bar 1000 is dragged to the left, the adjusted sizes of display area a and display area b can be determined by the terminal device based on the position of the dragged horizontal bar 1000 on the display interface. For example, the terminal device can use the position of the dragged horizontal bar 1000 on the display interface as the boundary between display area a and display area b. That is, after detecting the operation of dragging the horizontal bar 1000 to the left, the terminal device can adjust the size of display area a and display area b according to the position of the dragged horizontal bar 1000 on the display interface, so as to display the main window 400 and the secondary window according to the adjusted sizes of display area a and display area b.
[0297] In one embodiment, when the horizontal bar 1000 is dragged to the right, the adjusted sizes of display area a and display area b can be determined by the terminal device based on the position of the dragged horizontal bar 1000 on the display interface. For example, the terminal device can use the position of the dragged horizontal bar 1000 on the display interface as the boundary between display area a and display area b. That is, after detecting the operation of dragging the horizontal bar 1000 to the right, the terminal device can adjust the size of display area a and display area b according to the position of the dragged horizontal bar 1000 on the display interface, so as to display the main window 400 and the secondary window according to the adjusted sizes of display area a and display area b.
[0298] In another embodiment, after adjusting the terminal device's display interface to dual-screen mode, the sizes of the adjusted display area a and display area b can be set by default when dragging the horizontal bar 1000 to the right. For example, the terminal device can default to setting the size of the adjusted display area a to be the same as the size of the display area a before adjusting to dual-screen mode, and the size of the adjusted display area b to be the same as the size of the display area b before adjusting to dual-screen mode. That is, after adjusting the terminal device's display interface to dual-screen mode, if an operation of dragging the horizontal bar 1000 to any position on the display interface is detected, the terminal device can restore the display interface from dual-screen mode to the original large-screen mode (e.g., the mode shown in Figure 10(a) where the size of the main window 400 is larger than the size of any secondary window).
[0299] The following example illustrates how dragging the horizontal bar 1000 to the left adjusts the display to dual-screen mode, and dragging the horizontal bar 1000 to the right in dual-screen mode restores the display to large-screen mode.
[0300] In one embodiment, after the terminal device detects an operation of dragging the horizontal bar 1000 to any position on the display interface, it can adjust the size of display area a and display area b. It can adjust the size of the main window 400 according to the adjusted size of display area a, and adjust the size of each secondary window (e.g., first request window 410, second request window 420, and third request window 430) in display area b according to the adjusted size of display area b. Subsequently, the terminal device can continue to display the adjusted main window 400 in the adjusted display area a, and can display the adjusted secondary windows (e.g., first request window 410, second request window 420, and third request window 430) in the adjusted display area b through window stacking.
[0301] Window stacking can refer to multiple windows being stacked on a display interface (e.g., display area b) in a layered manner. The content of the topmost window can be fully displayed, while the content of other windows can overlap (i.e. be obscured). The title bars and / or part of the borders of other windows can be displayed, making it convenient for users to quickly identify and switch windows.
[0302] It should be understood that the embodiments of this application do not limit the size of the adjusted main window 400 and the sizes of the adjusted secondary windows, and can be determined according to the actual scenario. For example, the size of the adjusted main window 400 can be the same as the size of the adjusted display area a. The width of the adjusted secondary windows can be the same as the width of the adjusted display area b. To achieve window stacking, the height of the adjusted secondary windows can be the same and can be less than the height of display area b. Alternatively, the height of the bottommost secondary window can be the same as the height of display area b, and the heights of the other secondary windows can be less than the height of display area b, and the heights of the other secondary windows can be the same or different. The following will illustrate this by taking the example that the adjusted secondary windows are all the same height and all less than the height of display area b.
[0303] For example, to improve display quality, the terminal device can determine the adjusted height of the secondary windows based on the height of display area b, the number of secondary windows in display area b, and the required display height of the lower-level secondary windows (i.e., secondary windows not displayed at the top of display area b) within display area b. For instance, when the height of display area b is H0, display area b includes R secondary windows, and the required display height of the lower-level secondary windows in display area b is H3, the terminal device can determine the number of lower-level secondary windows as (R-1) and the adjusted height of the secondary windows as (H0-H3*(R-1)). The required display height of the lower-level secondary windows in display area b can be determined based on the actual scenario. For example, the required display height of the lower-level secondary windows in display area b can be determined based on the height of the title bar of the lower-level secondary windows.
[0304] When displaying the adjusted secondary windows in the adjusted display area b using a window stacking method, the terminal device can determine the stacking relationship between the secondary windows based on the page's storage time from earliest to latest and the display order from latest to latest (i.e., bottom to top). That is, the earlier a page's storage time is, the lower its corresponding secondary window can be displayed (i.e., in a lower layer); the older a page's storage time is, the higher its corresponding secondary window can be displayed (i.e., in a higher layer). Alternatively, the terminal device can determine the stacking relationship between the secondary windows based on the page's storage time from earliest to latest and the display order from latest to latest (i.e., top to bottom). That is, the earlier a page's storage time is, the higher its corresponding secondary window can be displayed (i.e., in a higher layer); the older a page's storage time is, the lower its corresponding secondary window can be displayed (i.e., in a lower layer). In addition, the terminal device can also determine the topmost secondary window in display area b, and display the adjusted secondary windows in display area b according to the stacking relationship between the secondary windows and the topmost secondary window. The following example illustrates how the terminal device can determine the stacking relationship between the secondary windows based on the page's storage time from earliest to latest and the display order from latest to earliest.
[0305] In some embodiments, after dragging the horizontal bar 1000 to any position on the display interface, the secondary window displayed on the topmost layer of display area b can be the focus window in display area b. When there is no focus window in display area b, the secondary window displayed on the topmost layer of display area b can be the window corresponding to the page with the latest storage time.
[0306] For example, in the scenario shown in Figure 10(a), the temporary storage time of page a is earlier than that of page c, and the temporary storage time of page c is earlier than that of page e. That is, the terminal device can determine the stacking relationship between the various secondary windows as follows: the first secondary window 410 corresponding to page a can be located below the second secondary window 420 corresponding to page c, and the second secondary window 420 corresponding to page c can be located below the third secondary window 430 corresponding to page e.
[0307] As shown in Figure 10(a), when a user wants to compare page f displayed in the main window 400 with page a displayed in the first desired window 410, the user can click any position in the first desired window 410 to set it as the focus window. Subsequently, as shown in Figure 10(b), the user can drag the horizontal bar 1000 to any position on the display interface.
[0308] As shown in Figure 10(c), after the terminal device detects the operation of dragging the horizontal bar 1000 to any position on the display interface, it can adjust the size of display area a and display area b to the same size, that is, it can switch the display interface to dual-screen mode, and can adjust the size of the main window 400, the first requested window 410, the second requested window 420, and the third requested window 430. Subsequently, the terminal device can display the adjusted main window 400 in display area a, and according to the above-mentioned stacking relationship, display the adjusted first requested window 410 on the top layer of display area b, display the adjusted third requested window 430 below the first requested window 410, and display the adjusted second requested window 420 below the third requested window 430.
[0309] As shown in Figure 10(c), when the terminal device displays the adjusted main window 400 in display area a, the adjusted first secondary window 410 at the top of display area b, the adjusted third secondary window 430 below the first secondary window 410, and the adjusted second secondary window 420 below the third secondary window 430, if the user wants to switch the secondary window displayed at the top of display area b, the user can perform a preset operation (e.g., click the secondary window that needs to be displayed at the top (e.g., click the title bar of the secondary window)). For example, as shown in Figure 10(c), when the user wants to view page c, that is, when the user wants to display the second secondary window 420 at the top of display area b, the user can click the title bar of the second secondary window 420.
[0310] As shown in Figure 10(d), after the terminal device detects the click operation on the title bar of the second request window 420, it can adjust the display order between the first request window 410, the second request window 420 and the third request window 430. That is, the second request window 420 can be moved to the top layer of the display area b, the first request window 410 can be moved to the bottom layer of the second request window 420, and the third request window 430 can be moved to the bottom layer of the first request window 410.
[0311] As shown in Figure 10(d), when the terminal device displays the main window 400 in display area a and the second request window 420, the first request window 410 and the third request window 430 in display area b, if the user wants to restore the display interface to the original large screen mode, the user can drag the horizontal bar 1000 to any position on the display interface to the right.
[0312] As shown in Figure 10(e), after the terminal device detects the operation of dragging the horizontal bar 1000 to any position on the display interface, it can restore the size of the display area a to its original size, and it can restore the size of the display area b to its original size. That is, it can restore the display interface to the original large screen mode, and it can adjust and display the size of the main window 400, the second request window 420, the first request window 410, and the third request window 430 according to the original large screen mode.
[0313] For example, the terminal device can display each secondary window from back to front (i.e., from bottom to top) in the display area b from top to bottom (i.e., from top to bottom) according to the display order between the currently displayed secondary windows. As shown in Figure 10(e), the terminal device can determine that the third secondary window 430 is located at the top of the display area b, the first secondary window 410 can be located below the third secondary window 430, and the second secondary window 420 can be located below the first secondary window 410.
[0314] It should be understood that the display positions of the various secondary windows in display area b when the display interface is restored to large screen mode are only illustrative and should not be construed as limiting the embodiments of this application. In the embodiments of this application, the various secondary windows can also be displayed in display area b in other ways.
[0315] It should be noted that after the terminal device detects the operation of dragging the horizontal bar 1000 to any position on the display interface, if it determines that there is no focus window in display area b, the terminal device can display the adjusted main window 400 in display area a, and can display the various secondary windows in display area b from front to back (i.e., from top to bottom) according to the page's storage time from latest to earliest. For example, in the scenario shown in Figure 10(a), after the terminal device detects the operation of dragging the horizontal bar 1000 to any position on the display interface, if it determines that there is no focus window in display area b, the terminal device can display the adjusted third primary window 430 at the top of display area b, and can display the adjusted second primary window 420 below the third primary window 430, and can display the adjusted first primary window 410 below the second primary window 420.
[0316] Please refer to Figures 11 to 13, which show another set of interface schematic diagrams provided in the embodiments of this application.
[0317] When a terminal device displays multiple pages of application A through multiple windows, the terminal device can close one or more windows based on the user's closing action.
[0318] As shown in Figure 11(a), when the terminal device displays page f in the main window 400 in display area a, and displays page a in the first request window 410, page c in the second request window 420, and page e in the third request window 430 in display area b, when the user wants to close a certain request window, for example, when the user wants to close the first request window 410, the user can click the menu bar 411 at the top of the first request window 410.
[0319] As shown in Figure 11(b), after the terminal device detects a click on the menu bar 411, it can display the window control menu 412 corresponding to the first window 410, which can display menu items such as "Multi-window within application", "Full screen window", "Replace application" and "Close window". The user can click "Close window" in the window control menu 412.
[0320] As shown in Figure 11(c), after the terminal device detects a click on the "Close Window" option in the window control menu 412, it can close the first requested window 410. Furthermore, after closing the first requested window 410, the terminal device can adjust the positions of the second requested window 420 and the third requested window 430 within the display area b. For example, to improve the display effect, the terminal device can move the second requested window 420 and the third requested window 430 upwards so that they are displayed as a whole in the center of the display area b.
[0321] As shown in Figure 12(a), when a user wants to close all secondary windows in display area b, the user can click the menu bar 401 at the top of the main window 400.
[0322] As shown in Figure 12(b), after the terminal device detects a click on the menu bar 401, it can display the window control menu 402 corresponding to the main window 400, which can display menu items such as "Multi-window within application", "Full screen window", "Replace application", and "Close window". The user can click "Full screen window" in the window control menu 402.
[0323] As shown in Figure 12(c), after the terminal device detects the click operation of "Full Screen" in the window control menu 402, it can display the main window 400 in full screen to close all secondary windows in the display area b.
[0324] Alternatively, as shown in Figure 13(a), a horizontal bar 1000 can be set between display area a and display area b. When the user wants to close all secondary windows in display area b, the user can drag the horizontal bar 1000 to the right to a preset position. The preset position can be a position relative to the right edge of the display interface at a preset threshold (e.g., preset threshold B). The preset threshold B can be determined according to the specific scenario. The preset threshold B can be set by the terminal device by default or can be customized by the user.
[0325] As shown in Figure 13(b), after the terminal device detects the operation of dragging the horizontal bar 1000 to the right to the preset position, it can close all secondary windows in the display area b and display the main window 400 in full screen.
[0326] It should be understood that the above-described method of displaying the main window 400 in full screen after detecting the operation of dragging the horizontal bar 1000 to the preset position is merely an illustrative explanation and should not be construed as a limitation on the embodiments of this application. In the embodiments of this application, the terminal device may also determine the size of the display area a based on the position of the dragged horizontal bar 1000 in the display interface, and can display the main window 400 according to the size of the display area a. For example, the size of the main window 400 may be the same as the size of the display area a.
[0327] In some embodiments, when the terminal device displays the page of application A through the first window, the user can first temporarily save the page displayed in the first window to another window based on a certain target operation, and can then display the other window in the display interface based on another target operation, so as to facilitate the user to view the temporarily saved page.
[0328] Please refer to Figures 14 to 17, which show another set of interface schematic diagrams provided in the embodiments of this application.
[0329] After a user launches application A on a terminal device, the terminal device can display the page of application A. For example, the terminal device can create a main window 1400 and display the page of application A in the main window 1400. The main window 1400 can be a full-screen window. Alternatively, the main window 1400 can be a non-full-screen window. The following example illustrates the situation with the main window 1400 being a full-screen window.
[0330] Specifically, when a terminal device displays a page (e.g., page a) of application A in the main window 1400, the terminal device can display other pages of application A (e.g., pages one level below page a) in the main window 1400 based on user actions on page a (e.g., click actions). It should be understood that when the terminal device creates the main window 1400 to display pages of application A, the terminal device can establish a page stack corresponding to the main window 1400 to manage the pages displayed in the main window 1400.
[0331] When a page of application A (e.g., page a) is displayed in the main window 1400, the main window 1400 may also include a menu bar 1401. When the menu bar 1401 is clicked, the terminal device can display a window control menu 1402 corresponding to the main window 1400. The window control menu 1402 may include one or more menu items, such as "Window Temporary," "Replace Application," and "Close Window." "Window Temporary" can be used to temporarily store the page displayed in the main window 1400 through one or more windows.
[0332] The menu bar 1401 can be located anywhere on the main window 1400. For example, as shown in Figure 14(a), the menu bar 1401 can be located at the top of the main window 1400. Alternatively, the menu bar 1401 can also be located at the bottom, left, or right of the main window 1400, or other locations. The following will illustrate this by taking the example of the menu bar 1401 being located at the top of the main window 1400.
[0333] When a user is browsing page a of application A, if the user wants to save page a, as shown in Figure 14(a), the user can click the menu bar 1401 at the top of the main window 1400. As shown in Figure 14(b), after the terminal device detects the click operation on the menu bar 1401, it can display the window control menu 1402, which can display menu items such as "Save Window", "Replace Application", and "Close Window". After the terminal device displays the window control menu 1402, as shown in Figure 14(b), the user can click "Save Window" to save page a for later viewing.
[0334] Alternatively, when a user is browsing page a of application A, if the terminal device determines that page a can be temporarily saved to a secondary window for display, the terminal device can display a prompt message. This prompt message can be used to suggest that the user can save page a for display in a secondary window. For example, as shown in Figure 14(c), the terminal device can display a pop-up window 1403. Pop-up window 1403 may include the prompt message "Page a can be displayed in a secondary window. Do you want to save page a?", as well as a confirmation button 1431 and a cancel button 1432. The confirmation button 1431 can be used to confirm saving page a, and the cancel button 1432 can be used to refuse saving page a. As shown in Figure 14(c), when the user wants to save page a, the user can click the confirmation button 1431. The following description will use the example of saving a page by clicking the "Save Window" button for illustration.
[0335] As shown in Figure 14(d), after the terminal device detects a click operation on "Window Temporary Storage" or a click operation on the confirmation button 1431, it can create a secondary window (e.g., the primary request window) 1410 and load page a into the primary request window 1410. The primary request window 1410 can be located behind the main window 1400, that is, the main window 1400 can be located above the primary request window 1410. When the primary request window 1410 is located behind the main window 1400, the terminal device can shrink the main window 1400 to reduce the full-screen main window 1400 to a non-full-screen window, and can display the title bar and / or part of the border of the primary request window 1410, so that the user can easily understand the temporarily stored page a.
[0336] It should be understood that the size of the first requested window 1410 and the sizes of the second requested window 1420 and the third requested window 1430, etc., can be determined according to the actual scenario, and this application embodiment does not impose any restrictions on this.
[0337] It should be noted that when the terminal device creates the first requested window 1410, it can establish a corresponding page stack for the first requested window 1410, and the page stack corresponding to the first requested window 1410 is independent of the page stack corresponding to the main window 1400. That is, operations performed on the pages displayed in the main window 1400 will not affect the pages in the first requested window 1410. Similarly, operations performed on the pages in the first requested window 1410 will not affect the pages displayed in the main window 1400.
[0338] After establishing the page stack corresponding to the first requesting window 1410, the terminal device can push page a onto the page stack corresponding to the first requesting window 1410. Alternatively, after establishing the page stack corresponding to the first requesting window 1410, the terminal device can first push the home page of application A onto the page stack corresponding to the first requesting window 1410, and then push page a onto the page stack corresponding to the first requesting window 1410. Alternatively, after establishing the page stack corresponding to the first requesting window 1410, the terminal device can sequentially push all the pages included in the page stack corresponding to the main window 1400 onto the page stack corresponding to the first requesting window 1410. It should be understood that after pushing page a onto the page stack corresponding to the first requesting window 1410, the top element of the page stack corresponding to the first requesting window 1410 can be page a.
[0339] As shown in Figure 14(d), when page a is loaded into the first-order window 1410, the terminal device can display the parent page of page a, such as page b, in the main window 1400. Page b can be a page included in the page stack corresponding to the main window 1400. That is, when page a is pushed onto the page stack corresponding to the first-order window 1410, the terminal device can pop page a from the page stack corresponding to the main window 1400. After popping page a from the page stack corresponding to the main window 1400, the top element of the page stack corresponding to the main window 1400 can be the parent page of page a (e.g., page b). At this time, the main window 1400 can display page b. Alternatively, when page a is loaded into the first-order window 1410, the terminal device can continue to display the original page in the main window 1400. That is, when page a is pushed onto the page stack corresponding to the first-order window 1410, the terminal device can keep the page stack corresponding to the main window 1400 unchanged. The following example illustrates how, when a page displayed in the main window 1400 is temporarily saved to a secondary window, the terminal device displays the page one level above that page in the main window 1400.
[0340] It should be noted that the parent page of a page displayed in the main window 1400 can be a page that has been opened in the main window 1400, that is, a page included in the page stack corresponding to the main window 1400. Specifically, when loading a page displayed in the main window 1400 into a secondary window, if that page has no parent page in the main window 1400, meaning no other page in application A has been opened in the main window 1400 before that page (e.g., the page is the top element of the page stack corresponding to the main window 1400), the terminal device can still display that page in the main window 1400. For example, when displaying the homepage of application A in the main window 1400, since no other page in application A has been opened in the main window 1400 before the homepage of application A (meaning the homepage of application A is the top element of the page stack corresponding to the main window 1400), the terminal device can still display the homepage of application A in the main window 1400 when loading the homepage of application A into a secondary window.
[0341] It should be understood that after page a is loaded into the primary window 1410, the user can continue browsing the page in the main window 1400 and can also temporarily save the browsed page for later viewing. Alternatively, after page a is loaded into the primary window 1410, the user can also view the saved page, that is, the secondary window located behind the main window 1400 can be displayed in the display interface.
[0342] After a page is temporarily saved, i.e., after the main window 1400 is reduced to a non-full-screen display, the terminal device can adjust the menu items included in the window control menu 1402. For example, it can add a "Full Screen" menu item and a "Tile" menu item to the window control menu 1402. "Full Screen" can be used to display the main window 1400 in full screen. "Tile" can be used to display the window corresponding to the temporarily saved page in the display interface. That is, after page a is temporarily saved, the terminal device can display the first requested window 1410 corresponding to page a in the terminal device's display interface based on the user's click operation of "Tile" in the window control menu 1402, so that the user can view page a through the first requested window 1410.
[0343] The following example illustrates how, after page a is loaded into the first main window 1410, the user continues browsing the page in the main window 1400.
[0344] After page a is loaded into the initial window 1410, the user can continue browsing the page through the main window 1400. For example, as shown in Figure 15(a), the user can switch from page b displayed in the main window 1400 to another page of application A (e.g., page c). If the user wants to save page c while browsing it, as shown in Figure 15(a), the user can continue to click the menu bar 1401 at the top of the main window 1400.
[0345] As shown in Figure 15(b), after the terminal device detects a click on the menu bar 1401, it can display the window control menu 1402, such as "Full Screen", "Tile", "Save Window", "Replace Application", and "Close Window". The user can then click "Save Window" to save page c.
[0346] After the terminal device detects a click operation on "window temporary storage", it can create a secondary window (e.g., a second secondary window) 1420 and load page c into the second secondary window 1420. The second secondary window 1420 can be located behind the main window 1400. The specific position of the second secondary window 1420 behind the main window 1400 can be determined according to the actual scenario, and this embodiment does not impose any restrictions on this.
[0347] For example, the terminal device can temporarily store multiple secondary windows behind the main window 1400 from front to back (i.e., from top to bottom) according to the page's storage time from earliest to latest. Specifically, the earlier a page is stored, the more prominent (i.e., the higher) the corresponding secondary window can be behind the main window 1400; conversely, the later a page is stored, the more prominent (i.e., the lower) the corresponding secondary window can be behind the main window 1400.
[0348] Because page a's temporary storage time is earlier than page c's, the terminal device can determine that the first request window 1410 corresponding to page a is earlier than the second request window 1420 corresponding to page c. The terminal device determines that the first request window 1410 can be located behind the main window 1400, and the second request window 1420 can be located behind the first request window 1410. That is, as shown in Figure 15(c), the main window 1400 can be located above the first request window 1410, and the first request window 1410 can be located above the second request window 1420. In other words, the main window 1400 can obscure part of the content of the first request window 1410, and the first request window 1410 can obscure part of the content of the second request window 1420. Furthermore, when loading page c into the second request window 1420, the terminal device can display the parent page of page c (e.g., page d) in the main window 1400.
[0349] For example, the terminal device can temporarily store multiple secondary pages in order of their storage time, from earliest to latest, behind the main window 1400, from back to front. Specifically, the earlier a page is stored, the further back its corresponding secondary window can be positioned behind the main window 1400; conversely, the later a page is stored, the further forward its corresponding secondary window can be positioned behind the main window 1400.
[0350] Because page a's temporary storage time is earlier than page c's, the terminal device can determine that the second request window 1420 corresponding to page c is earlier than the first request window 1410 corresponding to page a. The terminal device determines that the second request window 1420 can be located behind the main window 1400, and the first request window 1410 can be located behind the second request window 1420. That is, as shown in Figure 15(d), the main window 1400 can be located above the second request window 1420, and the second request window 1420 can be located above the first request window 1410. In other words, the main window 1400 can obscure part of the content of the second request window 1420, and the second request window 1420 can obscure part of the content of the first request window 1410. Furthermore, when loading page c into the second request window 1420, the terminal device can display the page one level above page c (e.g., page d) in the main window 1400.
[0351] The following example illustrates how the terminal device shown in Figure 15(c) temporarily stores multiple secondary windows from front to back behind the main window 1400 according to the page's storage time from earliest to latest.
[0352] It should be understood that when the terminal device creates the second desired window 1420, it can establish a corresponding page stack for the second desired window 1420. After establishing the page stack for the second desired window 1420, the terminal device can push page c onto the page stack for the second desired window 1420. Alternatively, after establishing the page stack for the second desired window 1420, the terminal device can first push the home page of application A onto the page stack for the second desired window 1420, and then push page c onto the page stack for the second desired window 1420. Alternatively, after establishing the page stack for the second desired window 1420, the terminal device can sequentially push all the pages included in the page stack corresponding to the main window 1400 onto the page stack for the second desired window 1420. It should be understood that after pushing page c onto the page stack for the second desired window 1420, the top element of the page stack for the second desired window 1420 can be page c.
[0353] Additionally, when page c is loaded into the second main window 1420, the terminal device can pop page c from the page stack corresponding to the main window 1400. After popping page c from the page stack corresponding to the main window 1400, the top element in the page stack corresponding to the main window 1400 can be the parent page of page c (e.g., page d), therefore, the main window 1400 can display page d.
[0354] The page stack corresponding to the second request window 1420 is independent of the page stack corresponding to the main window 1400 and the page stack corresponding to the first request window 1410. That is, operations performed on pages in the main window 1400 or the first request window 1410 will not affect pages in the second request window 1420. Similarly, operations performed on pages in the second request window 1420 will not affect pages in the main window 1400 or the first request window 1410.
[0355] It should be noted that after page c is loaded into the second request window 1420, the user can continue browsing the page through the main window 1400 and can also save the browsed page for later viewing. Alternatively, the user can also view the saved page, that is, view both the first request window 1410 and the second request window 1420.
[0356] For example, after page c is loaded into the second main window 1420, the user can continue browsing the page through the main window 1400. For instance, as shown in Figure 16(a), the user can switch from page d displayed in the main window 1400 to another page of application A (e.g., page e). When the user is browsing page e, if the user wants to view a temporarily saved page, as shown in Figure 16(a), the user can click the menu bar 1401 at the top of the main window 1400.
[0357] As shown in Figure 16(b), after the terminal device detects a click on the menu bar 1401, it can display the window control menu 1402, which may include menu items such as "Full Screen", "Tile", "Save Window", "Replace Application", and "Close Window". After displaying the window control menu 1402, the user can click "Tile" in the window control menu 1402 to display the saved page. That is, the primary window 1410 and the secondary window 1420 located behind the main window 1400 can be displayed on the terminal device's display interface for the user's convenience.
[0358] As shown in Figure 16(c), after the terminal device detects a click operation on "Tile Window", it can shrink the main window 1400, the first requested window 1410, and the second requested window 1420. The shrunken main window 1400 can be displayed in display area a, and the shrunken first requested window 1410 and second requested window 1420 can be displayed in display area b. The shrunken main window 1400 can display page e, the shrunken first requested window 1410 can display page a, and the shrunken second requested window 1420 can display page c. Display areas a and b do not need to overlap. The first requested window 1410 and the second requested window 1420 do not need to overlap.
[0359] It should be understood that the sizes of display area a, display area b, the reduced main window 1400, the reduced first request window 1410, and the reduced second request window 1420 can be determined according to the actual scenario, and this application embodiment does not impose any restrictions on this. Specifically, the content of the reduced main window 1400 can refer to the content of the reduced main window 400 shown in Figure 5, the content of the reduced first request window 1410 can refer to the content of the first request window 410 shown in Figure 5, the content of the reduced second request window 1420 can refer to the content of the second request window 420 shown in Figure 5, and the positions of the reduced first request window 1410 and the reduced second request window 1420 in display area b can refer to the positions of the first request window 410 and the second request window 420 in display area b shown in Figure 5, which will not be elaborated further here.
[0360] It should be noted that the main window 1400, the first request window 1410, and the second request window 1420 can each have independent page stacks. That is, the page stack corresponding to the main window 1400 can be independent of the page stack corresponding to the first request window 1410, the page stack corresponding to the main window 1400 can be independent of the page stack corresponding to the second request window 1420, and the page stack corresponding to the first request window 1410 can also be independent of the page stack corresponding to the second request window 1420. In other words, operations performed on the pages displayed in the main window 1400 will not affect the pages displayed in the first request window 1410 and the second request window 1420. Similarly, operations performed on the pages displayed in the first request window 1410 and the second request window 1420 will not affect the pages displayed in the main window 1400.
[0361] For example, when a terminal device displays page e in display area a via the main window 1400, and displays page a via the first request window 1410 and page c via the second request window 1420 in display area b, as shown in Figure 17(a), when the user switches page e displayed in the main window 1400 to another page of application A (e.g., page f), the page displayed in the first request window 1410 and the page displayed in the second request window 1420 can remain unchanged. That is, the first request window 1410 can continue to display page a, and the second request window 1420 can continue to display page c. Here, page f can be any page of application A.
[0362] When the terminal device displays page f in display area a through the main window 1400, and displays page a in display area b through the first request window 1410 and page c through the second request window 1420, if the user wants to continue to save page f, as shown in Figure 17(a), the user can click the menu bar 1401 at the top of the main window 1400. As shown in Figure 17(b), after the terminal device detects the click operation on the menu bar 1401, it can display the window control menu 1402, such as "Full Screen", "Tile", "Save Window", "Replace Application", and "Close Window".
[0363] As shown in Figure 17(b), users can click "Window Temporary" in the window control menu 1402 to temporarily save page f.
[0364] After detecting a click operation on "Window Temporary", the terminal device can create a secondary window (e.g., a fourth secondary window) 1440, load page f into the fourth secondary window 1440, and display the fourth secondary window 1440 in the display area b, so as to display page f through the fourth secondary window 1440. While displaying page f through the fourth secondary window 1440, the terminal device can also display the parent page of page f (e.g., page g) in the main window 1400.
[0365] It should be understood that the fourth requested window 1440 and the first requested window 1410 may not overlap, and the fourth requested window 1440 and the second requested window 1420 may not overlap. Furthermore, the size of the fourth requested window 1440 may be the same as the size of the first requested window 1410 displayed in display area b.
[0366] For example, as shown in Figure 17(c), when the terminal device displays secondary windows in display area b from top to bottom according to the page's storage time from earliest to latest, since the storage time of page f is later than that of page c, the terminal device can display the fourth secondary window 1440 corresponding to page f below the second secondary window 1420 corresponding to page c. When the fourth secondary window 1440 cannot be fully displayed below the second secondary window 1420, the terminal device can display a portion of the fourth secondary window 1440 or not display it at all. When the terminal device displays a portion of the fourth secondary window 1440 or does not display it, when the user performs a preset operation (e.g., an upward swipe) in display area b, the terminal device can gradually display the fourth secondary window 1440 in display area b based on the user's upward swipe operation.
[0367] It should be understood that when the terminal device creates the fourth secondary window 1440, it can establish a corresponding page stack for the fourth secondary window 1440. After establishing the page stack for the fourth secondary window 1440, the terminal device can push page f onto the page stack for the fourth secondary window 1440. Alternatively, after establishing the page stack for the fourth secondary window 1440, the terminal device can first push the home page of application A onto the page stack for the fourth secondary window 1440, and then push page f onto the page stack for the fourth secondary window 1440. Alternatively, after establishing the page stack for the fourth secondary window 1440, the terminal device can sequentially push all the pages included in the page stack corresponding to the main window 1400 onto the page stack for the fourth secondary window 1440. After pushing page f onto the page stack for the fourth secondary window 1440, the top element of the page stack for the fourth secondary window 1440 can be page f.
[0368] Additionally, when page f is loaded into the fourth secondary window 1440, the terminal device can pop page f from the page stack corresponding to the main window 1400. After popping page f from the page stack corresponding to the main window 1400, the top element in the page stack corresponding to the main window 1400 can be the parent page of page f (e.g., page g). Therefore, the terminal device can display page g in the main window 1400.
[0369] The page stack corresponding to the fourth secondary request window 1440 is independent of the page stacks corresponding to the main window 1400, the first request window 1410, and the second request window 1420. That is, operations performed on the pages displayed in the main window 1400, the first request window 1410, or the second request window 1420 will not affect the pages displayed in the fourth secondary request window 1440. Similarly, operations performed on the pages displayed in the fourth secondary request window 1440 will not affect the pages displayed in the main window 1400, the first request window 1410, or the second request window 1420.
[0370] For example, when a terminal device displays page g through the main window 1400, page a through the first request window 1410, page c through the second request window 1420, and page f through the fourth request window 1440, the user can open a new interface in the first request window 1410. The newly opened interface can be displayed in the first request window 1410, while the main window 1400 can still display page g, the second request window 1420 can still display page c, and the fourth request window 1440 can still display page f. Alternatively, the user can open a new interface in the second request window 1420. The newly opened interface can be displayed in the second request window 1420, while the main window 1400 can still display page g, the first request window 1410 can still display page a, and the fourth request window 1440 can still display page f.
[0371] It should be noted that after displaying one or more secondary windows in display area b, the terminal device can also, based on user operations, load the page displayed in one secondary window into another newly created secondary window, or switch the position of the secondary window in display area b, or swap the main window and a secondary window, or adjust the display interface to dual-screen mode, or switch the display order of the secondary windows in dual-screen mode, or restore the display interface in dual-screen mode to large-screen mode, or close one or more secondary windows, etc. For details, please refer to the relevant descriptions shown in Figures 7 to 13 above; for the sake of brevity, they will not be repeated here.
[0372] The application display method provided in this application embodiment will be described in detail below with reference to the user interface shown above.
[0373] It should be noted that the application display method provided in this application embodiment can be a system function provided by a terminal device. The terminal device can provide an interface to the application to call the function, thereby realizing multi-window display within the application. When an application needs to call the function, the developer can adapt the application, for example, by configuring declaration information for the application to indicate that the application supports the function and the pages within the application that support the function. Therefore, after a user launches an application, the terminal device can obtain the declaration information corresponding to the application. When it is determined from the declaration information that the application supports the function, the terminal device determines that the application can call the function to realize multi-window display within the application. When it is determined from the declaration information that the application does not support the function, or when the declaration information is not obtained, the terminal device can determine that the application cannot call the function, thus determining that the application cannot realize multi-window display within the application.
[0374] The following example illustrates how a terminal device determines that a first application supports a certain function based on the declaration information corresponding to the first application.
[0375] Please refer to Figure 18, which shows a schematic flowchart of the application display method provided in this embodiment. This method can be applied to the terminal device described above. As shown in Figure 18, the method may include:
[0376] S1801, The terminal device displays the first page of the first application in the first window.
[0377] S1802, In response to the operation applied to the first page, the terminal device displays the second page of the first application in the first window; the second page is a sub-page of the first page.
[0378] S1803, The terminal device responds to the first target operation on the first window, loads the second page into the second window, and displays the first page of the first application in the first window.
[0379] It should be understood that when a terminal device responds to a target operation (e.g., a first target operation) on a first window and loads a page (e.g., a second page) into a window (e.g., a second window), it can also be described as the terminal device responding to a first target operation on a first window and migrating a second page from the first window to the second window. Specifically, when migrating the second page from the first window to the second window, the second page can be removed from the first window and loaded into the second window. Alternatively, the second page can be removed from the page stack of the first window and added to the page stack of the second window.
[0380] The first application can be any application on the terminal device. For example, the first application can be application A as described above. The first page can be any page in the first application. For example, the first page can be page a as described above. The first window can be the main window as described above. The second window can be the secondary window as described above. For example, the second window can be the primary window as described above. When displaying a page of the first application through the first window, the terminal device can establish a page stack corresponding to the first window to manage the pages displayed in the first window through the page stack corresponding to the first window.
[0381] In some embodiments, when a page of the first application is displayed in the first window, the terminal device may also display a menu bar (e.g., menu bar B1) in the first window. When a preset operation (e.g., preset operation A1) is detected on the menu bar B1, the terminal device may display a window control menu (e.g., window control menu M1) corresponding to the first window. The window control menu M1 includes one or more menu items.
[0382] In one embodiment, the window control menu M1 may include a menu item (e.g., menu item R1) for triggering multi-window display. For example, menu item R1 may be the aforementioned "in-application multi-window". When it is determined that the first application supports multi-window display, menu item R1 is in a triggerable state, meaning the user can trigger menu item R1 to display multiple windows. The specific location of the menu bar B1 in the first window and the specific content of the window control menu M1 can be referred to the relevant description shown in Figure 4 above. For example, the terminal device may display the menu bar B1 at the top of the first window.
[0383] For example, the preset operation A1 is clickable. The first target operation may include clicking on a menu item R1 (e.g., "Multi-window within application"). That is, if the first application supports multi-window display, when the user wants to save the second page displayed in the first window, the user can click on the menu bar B1 at the top of the first window. After the terminal device detects the click on the menu bar B1, it can display the window control menu M1. After displaying the window control menu M1, the user can click on the menu item R1 in the window control menu M1. After the terminal device detects the click on the menu item R1, it can create a second window, load the second page into the second window, and display the second window.
[0384] In another embodiment, the window control menu M1 may include a menu item (e.g., menu item R2) for triggering window staking. For example, menu item R2 may be the aforementioned "window staking". The specific content of the window control menu M1 can be referred to the relevant description shown in Figure 14 above, and will not be repeated here. For example, the preset operation A1 can be a click operation. The first target operation may include a click operation on menu item R2 (e.g., "window staking"). That is, when the user wants to save the second page displayed in the first window, the user can click the menu bar B1 at the top of the first window. After the terminal device detects the click operation on menu bar B1, it can display the window control menu M1. After displaying the window control menu M1, the user can click menu item R2 in the window control menu M1. After the terminal device detects the click operation on menu item R2, it can create a second window, load the second page into the second window, and the second window may be located behind the first window.
[0385] For example, when creating a second window, the terminal device can establish a corresponding page stack for the second window, and the page stack corresponding to the second window is independent of the page stack corresponding to the first window. That is, operations performed on the pages in the first window will not affect the pages in the second window. Similarly, operations performed on the pages in the second window will not affect the pages in the first window. It should be understood that the specific content of the page stack corresponding to the second window can refer to the relevant content of the page stack corresponding to any of the previously mentioned primary windows (e.g., the primary primary window), and for the sake of simplicity, it will not be repeated here.
[0386] In some embodiments, when the terminal device loads a second page into a second window, it can display the parent page of the second page, such as the first page, in the first window. Alternatively, the terminal device can continue to display the original page in the first window, that is, it can continue to display the second page in the first window. In other words, when a page displayed in the first window is loaded into another window, the terminal device can display the parent page of that page in the first window, or it can still display that page. The following will illustrate this by taking the example of the terminal device displaying the parent page of a page displayed in the first window when a page displayed in the first window is loaded into another window.
[0387] It should be understood that after loading the second page into the second window in response to the first target operation on the first window, the user can continue browsing the pages of the first application through the first window, for example, by continuing to browse the third page of the first application through the first window. While browsing the third page of the first application, i.e., when the terminal device displays the third page in the first window, if the user wants to save the third page, the user can continue to click the menu bar B1 at the top of the first window. After detecting the click operation on the menu bar B1, the terminal device can display the window control menu M1. The user can perform a target operation (e.g., a click operation) on the menu item R1 (e.g., "Multi-window within application") or the menu item R2 (e.g., "Window Save") in the window control menu M1. After detecting the click operation on the menu item R1 or the menu item R2, the terminal device can create a third window and load the third page into the third window. While loading the third page into the third window, the terminal device can continue to display the second page in the second window and can also display the parent page of the third page (e.g., the fourth page) in the first window. Specifically, when loading the third page into the third window, if the third page has no parent page, meaning the user has not opened any other pages of the first application in the first window before the third page, the terminal device can continue to display the third page in the first window.
[0388] The third page can be a parent page of the second page (e.g., the first page), or it can be any other page. That is, after loading the second page into the second window in response to a first target operation on the first window, the terminal device can display the parent page of the second page (e.g., the first page) in the first window. When the first page is displayed in the first window, the terminal device can load the first page into the third window based on the user's target operation (e.g., a third target operation) on the first window. Alternatively, when the parent page of the second page is displayed in the first window, the terminal device can switch the page displayed in the first window based on the user's relevant operation to display other pages in the first window, and when other pages are displayed in the first window, it can load those other pages into the third window based on the user's third target operation on the first window. It should be understood that the relevant operation for switching the page displayed in the first window can be determined according to the actual scenario, and this embodiment does not limit this. For example, the relevant operation can be a swipe operation, or a click operation on the content of the currently displayed page in the first window, etc.
[0389] Similarly, when creating a third window, the terminal device can establish a corresponding page stack for the third window. This page stack is independent of the page stack of the first window, and also independent of the page stack of the second window. That is, operations performed on pages in the third window will not affect pages in the first or second windows. Likewise, operations performed on pages in the first or second window will not affect pages in the third window. It should be understood that the specific content of the page stack corresponding to the third window can be referenced from the aforementioned content regarding the page stack of any of the primary windows; for the sake of simplicity, it will not be elaborated upon here.
[0390] In some embodiments, after a second page is loaded into a second window in response to a first target operation on a first window, the terminal device may display the second window, and the second window may not overlap with the first window.
[0391] In one embodiment, when the window control menu M1 includes a menu item R1 (e.g., "In-App Multi-Window") for triggering multi-window display, the terminal device can load a second page into the second window and display it in response to a first target operation on the first window. That is, when the terminal device displays the window control menu M1 based on a user's click operation on the menu bar B1 in the first window, and the window control menu M1 includes a menu item R1 (e.g., "In-App Multi-Window"), the terminal device can load a second page into the second window and display it based on a user's click operation on the menu item R1 (e.g., "In-App Multi-Window"). The specific content of the second window displayed by the terminal device based on the click operation on "In-App Multi-Window" can be referred to the relevant description in Figure 4 above, and will not be repeated here.
[0392] In another embodiment, when the window control menu M1 includes a menu item R2 (e.g., "Window Temporary") for triggering window tiling, the window control menu M1 may also include a menu item (e.g., menu item R3) for triggering window tiling. For example, menu item R3 may be the aforementioned "Window Tiling". After a second page is loaded into a second window based on a first target operation on menu item R2, and the second window is located behind the first window, when the user wants to view the temporary page, i.e., wants to view the window behind the first window, the user can click the menu bar B1 at the top of the first window. After the terminal device detects the click operation on the menu bar B1, it can display the window control menu M1, at which time the window control menu M1 may include menu item R3 (e.g., "Window Tiling"). After displaying the window control menu M1, the user can click the menu item R3 (e.g., "Window Tiling"). After the terminal device detects the click operation on the menu item R3, it can display the second window. The specific content of the second window displayed by the terminal device based on the click operation of "window tiling" can be referred to the relevant description in Figure 16 above, and will not be repeated here.
[0393] For example, when displaying the second window, the terminal device can reduce the size of the first window and display the reduced first window in the first display area, and can also display the second window in the second display area. The first and second display areas do not need to overlap. For example, the first display area can be display area a as described above, and the second display area can be display area b as described above. It should be understood that the specific content of the second window displayed by the terminal device, as well as the specific content of display area a and display area b, can be referred to the relevant descriptions shown in Figure 4 or Figure 16 above, and will not be repeated here.
[0394] In some embodiments, when the window control menu M1 includes a menu item R2 (e.g., "window pause") for triggering window pausing, after loading the second page into the second window in response to a first target operation on the first window, the terminal device can stack the second window and the first window, and the second window can be located behind the first window.
[0395] For example, when the second window and the first window are stacked, to allow the user to see the currently stored page, the terminal device can adjust the size of the first window, and the second window can be located behind the adjusted first window. The adjusted first window may partially obscure the second window; for example, the title bar of the second window can be displayed in the interface, allowing the user to see the currently stored page. It should be understood that the specific details of the second window being located behind the first window can be referred to the relevant descriptions shown in Figures 14 and 15 above, and will not be repeated here.
[0396] In some embodiments, after the second window is displayed, the user can swap the first and second windows. That is, when the user wants to view the page in the second window from the original position of the first window, the user can perform a preset operation (e.g., preset operation A2) in the second and / or first window. After the terminal device detects the preset operation A2 on the second and / or first window, it can swap the first and second windows, i.e., swap their positions. When swapping the first and second windows, the terminal device can adjust the size of the second window and the size of the page displayed in the second window based on the original size of the first window, and can also adjust the size of the first window and the size of the page displayed in the first window based on the original size of the second window.
[0397] For example, when the first window displays the third page and the second window displays the second page, if the user wants to view the second page in the second window in a larger window, the user can perform a preset operation A2 in the second window and / or the first window. After the terminal device detects the preset operation A2 in the second window and / or the first window, it can swap the positions of the first window and the second window, adjust the size of the first window and the third page according to the original size of the second window, and adjust the size of the second window and the second page according to the original size of the first window, so that the first window can be displayed in the original position of the second window, and the second window can be displayed in the original position of the first window, making it convenient for the user to view the second page displayed in the second window.
[0398] Similarly, after the third window is displayed, the user can also swap the positions of the first and third windows. That is, the terminal device can swap the positions of the first and third windows based on the user's preset operation A2 on the first and / or third windows.
[0399] It should be noted that the preset operation A2 can be a double-click operation, a drag-and-drop operation, or a click operation on a menu item in the window control menu (such as "Swap with Main Window"). For example, the window control menus corresponding to the windows displayed in the second display area may include menu items for swapping windows (such as "Swap with Main Window"). When a user wants to swap a window in the second display area (such as the second window) with the first window (i.e., the main window), the user can click the "Swap with Main Window" menu item in the window control menu corresponding to the second window to perform the window swap. The specific details of the terminal device swapping the first window with other windows can be referred to the relevant description of the terminal device swapping the main window with a secondary window shown in Figure 9 above, and will not be repeated here.
[0400] In some embodiments, when multiple windows are displayed in the second display area, the terminal device may adjust the position of each window in the second display area based on a user's preset operation (e.g., preset operation A3).
[0401] For example, after displaying a second window and a third window in the second display area, if the user wants to swap the positions of the second and third windows in the second display area, the user can perform a preset operation A3 on the second window. After the terminal device detects the preset operation A3 on the second window, it can swap the positions of the second and third windows in the second display area. And / or, the user can perform a preset operation A3 on the third window. After the terminal device detects the preset operation A3 on the third window, it can swap the positions of the third and second windows in the second display area.
[0402] It should be noted that the preset operation A3 can be a drag-and-drop operation. The specific details of how the terminal device swaps the positions of the second and third windows in the second display area based on the drag-and-drop operation can be found in the description of the terminal device swapping the positions of the first and second windows in display area b shown in Figure 8 above, and will not be repeated here.
[0403] In some embodiments, when a terminal device displays a page in a first display area through a first window and in a second display area through one or more windows, a horizontal bar may be provided between the first and second display areas. The horizontal bar can be dragged to change the ratio between the first and second display areas. That is, the user can adjust the size of the first and second display areas by dragging the horizontal bar.
[0404] In other words, when a user wants to adjust the size of the first display area and the second display area, the user can perform a preset operation on the first window (such as dragging a horizontal bar). After the terminal device detects the dragging operation, it can adjust the size of the first display area and the second display area. Based on the adjusted size of the first display area, it can adjust the size of the first window, and based on the adjusted size of the second display area, it can adjust the size of the second window and the third window. Furthermore, it can display the adjusted first window in the first display area and the adjusted second and third windows in the second display area.
[0405] It should be understood that the specific content of the first display area and the second display area adjusted by the terminal device based on the drag operation of the horizontal bar, as well as the display of the first window, the second window and the third window after the adjustment, can be referred to the relevant description of the terminal device adjusting the size of display area a and display area b according to the drag operation of the horizontal bar, as well as the display of the main window and each secondary window after the adjustment, as shown in Figure 10 above.
[0406] For example, when the terminal device's display interface is adjusted to dual-screen mode, i.e., when the size of the adjusted first display area is the same as the size of the adjusted second display area, the terminal device can display the adjusted second and third windows in the adjusted second display area through window stacking. Specifically, when a focused window exists in the windows displayed in the second display area, the terminal device can display that focused window on top of the second display area to facilitate the user's continued viewing of the page in that focused window. When no focused window exists in the windows displayed in the second display area, the terminal device can display the window corresponding to the page with the latest temporary storage time on top of the second display area to facilitate the user's viewing of the most recently stored page.
[0407] For example, when displaying a second window and a third window in the second display area, if the second window is the focus window, the terminal device can display the second window at the top of the second display area and the third window below it. If neither the second nor the third window is the focus window, the terminal device can display the third window corresponding to the third page with the later storage time at the top of the second display area and the second window below it.
[0408] When the terminal device's display interface is adjusted to dual-screen mode, the terminal device continues to display the adjusted second and third windows in the adjusted second display area by means of window stacking. The specific content of these windows can be referred to the relevant description shown in Figure 10 above, and will not be repeated here.
[0409] In some embodiments, when a terminal device displays multiple pages of a first application through multiple windows, the terminal device can close one or more windows based on a user's closing action. For example, when the terminal device displays a fourth page through a first window, a second page through a second window, and a third page through a third window, if the user wants to close the second window, the user can perform a preset operation on the second window (e.g., clicking the "Close Window" option in the window control menu corresponding to the second window). After detecting this preset operation on the second window, the terminal device can close the second window. Similarly, if the user wants to close the third window, the user can perform a preset operation on the third window (e.g., clicking the "Close Window" option in the window control menu corresponding to the third window). After detecting this preset operation on the third window, the terminal device can close the third window. If the user wants to close the first window, the user can perform a preset operation on the first window (e.g., clicking the "Close Window" option in the window control menu corresponding to the first window). After detecting this preset operation on the first window, the terminal device can close the first window.
[0410] It should be noted that the specific details of closing the first, second, or third window based on the "Close Window" operation in the window control menu can be found in the description of the terminal device closing the first window shown in Figure 11 above, and will not be repeated here.
[0411] For example, when a user wants to close all windows in the second display area, the user can perform a preset operation on the first window (e.g., clicking "Full Screen" in the window control menu corresponding to the first window, or dragging a horizontal bar to a preset position). After the terminal device detects this preset operation on the first window, it can close all windows in the second display area. For instance, if the terminal device displays a fourth page in the first display area through a first window, and a second page in the second display area through a second window and a third page through a third window, and the user wants to close the second and third windows, the user can click "Full Screen" in the window control menu corresponding to the first window, or drag a horizontal bar to a preset position. After the terminal device detects this operation on the first window, it can close the second and third windows.
[0412] Specifically, the terminal device closes the second and third windows by clicking the "Full Screen" option in the window control menu corresponding to the first window. The details of this process can be found in Figure 12, which illustrates the terminal device closing the first, second, and third requested windows. Similarly, the terminal device closes the second and third windows by dragging a horizontal bar to a preset position. The details of this process can be found in Figure 13, which illustrates the terminal device closing the first, second, and third requested windows, and will not be repeated here.
[0413] It should be noted that this application embodiment does not limit the number of pages that users temporarily store, and can be determined according to the actual scenario.
[0414] In some embodiments, when the number of windows displayed in the second display area is greater than two, for example, after the second and third windows are displayed in the second display area, the user can continue browsing the page through the first window. While continuing to browse the page through the first window, if the user wants to save a page displayed in the first window (e.g., page S1), the user can click the menu bar B1 at the top of the first window. After the terminal device detects the click operation on the menu bar B1, it can display the window control menu M1, and based on the user's click operation on menu item R1 (e.g., "In-Application Multi-Window") or menu item R2 (e.g., "Window Temporary") in the window control menu M1, it can create a window (e.g., window W1) for displaying page S1, and load page S1 into window W1. After loading page S1 into window W1, the terminal device can display window W1 in the second display area to display page S1 through window W1. While the terminal device displays window W1 in the second display area, it can continue to display the second and third windows in the second display area.
[0415] It should be noted that window W1 does not need to overlap with any of the first, second, or third windows. Specifically, when creating window W1, the terminal device can establish a corresponding page stack for window W1. The page stack corresponding to window W1 is independent of the page stack corresponding to the first window, the second window, and the third window. That is, operations performed on the pages displayed in window W1 do not affect the pages displayed in the first, second, or third windows. Similarly, operations performed on the pages displayed in the first, second, or third windows do not affect the pages displayed in window W1.
[0416] It should be understood that the specific content of the terminal device displaying window W1 in the second display area can be referred to the relevant description of the terminal device displaying the third window in display area b as shown in Figure 6 or Figure 17 above, and will not be repeated here.
[0417] In some embodiments, when the second page is displayed in the second display area through the second window, the terminal device may also display a menu bar (e.g., menu bar B2) in the second window. When a preset operation (e.g., a click operation) on the menu bar B2 is detected, the terminal device may display the window control menu corresponding to the second window (e.g., window control menu M2). The window control menu M2 includes one or more menu items.
[0418] In one embodiment, the window control menu M2 corresponding to the second window may include a menu item R1 that triggers multi-window display, such as a "Multi-window within application" menu item. After the second page is loaded into the second window, when the user wants to save the second page displayed in the second window through another window, the user can click the menu item R1 in the window control menu M2. After the terminal device detects the click operation on the menu item R1 in the window control menu M2, it can create a new window (e.g., window W2), load the second page into window W2, and display window W2. It can also display the homepage of the first application in the second window, or display the parent page of the second page (e.g., page S2) in the second window, or display the second page in the second window.
[0419] It should be noted that the parent page of a page displayed in the second window can be a page that has been opened in the second window. Specifically, when loading a page displayed in the second window into a primary window, if that page does not have a parent page in the second window, that is, if no other page in the first application has been opened in the second window before that page, then the terminal device can display that page in the second window.
[0420] In another embodiment, the window control menu M2 corresponding to the second window may include a menu item R2 for triggering window saving, such as "Window Saving". When a user wants to save the second page displayed in the second window through another window, the user can click "Window Saving" in the window control menu M2. After the terminal device detects the click operation on "Window Saving" in the window control menu M2, it can create a window W2 for displaying the second page, load the second page into window W2, and display window W2. It can also display the homepage of the first application in the second window, or display the parent page of the second page (e.g., page S2) in the second window, or display the second page in the second window.
[0421] The specific contents of menu bar B2, window control menu M2, and window W2 can be found in the descriptions of the menu bar corresponding to the first desired window, the window control menu corresponding to the first desired window, and the relevant descriptions of the fourth desired window shown in Figure 7 above. They will not be repeated here.
[0422] It should be understood that when a second page is displayed in a second window within the second display area, the user can switch between pages displayed in the second window, meaning they can browse pages within the second window. For example, a new page can be opened in the second window, and the newly opened page will be displayed there.
[0423] It should be noted that the above-described terminal device displaying a first window in a first display area and a second and third window in a second display area, wherein the second display area is smaller than the first display area, and the second and third windows are smaller than the first window, is merely illustrative and should not be construed as a limitation on the embodiments of this application. In the embodiments of this application, when the terminal device displays a first window in a first display area and a second and third window in a second display area, the size of the first display area and the size of the second display area may be the same, and the size of the second window and the size of the first window may be the same.
[0424] Please refer to Figures 19 and 20, which show another set of interface schematic diagrams provided in the embodiments of this application.
[0425] After a user launches application A on a terminal device, the terminal device can display the page of application A. For example, the terminal device can create a main window 1900 and display the page of application A in the main window 1900. The main window 1900 can be a full-screen window. Alternatively, the main window 1900 can be a non-full-screen window. The following example illustrates the situation with the main window 1900 being a full-screen window.
[0426] Specifically, when a terminal device displays a page (e.g., page a) of application A in the main window 1900, the terminal device can display other pages of application A (e.g., pages one level below page a) in the main window 1900 based on user actions on page a (e.g., click actions). It should be understood that when the terminal device displays pages of application A through the main window 1900, the terminal device can establish a page stack corresponding to the main window 1900 to manage the pages displayed in the main window 1900.
[0427] When a page of application A (e.g., page a) is displayed in the main window 19000, the main window 19000 can also display a menu bar 1901. When the menu bar 1901 is clicked, the terminal device can display the window control menu 1902 corresponding to the main window 1900. The window control menu 1902 can include one or more menu items, such as "Multiple windows within an application," "Replace application," and "Close window."
[0428] The menu bar 1901 can be located anywhere in the main window 1900. For example, as shown in Figure 19(a), the menu bar 1901 can be located at the top of the main window 1900.
[0429] When a user is browsing page a of application A, if the user wants to temporarily save page a, as shown in Figure 19(a), the user can click the menu bar 1901 at the top of the main window 1900. As shown in Figure 19(b), after the terminal device detects the click operation on the menu bar 1901, it can display the window control menu 1902, which can display menu items such as "Multi-window within application", "Replace application", and "Close window". After the terminal device displays the window control menu 1902, as shown in Figure 19(b), the user can click "Multi-window within application" to temporarily save page a for later viewing.
[0430] Alternatively, when a user is browsing page a of application A, if the terminal device determines that page a can be temporarily saved to a secondary window for display, the terminal device can display a prompt message. This prompt message can be used to suggest that the user save page a so that it can be displayed through a secondary window. For example, as shown in Figure 19(c), the terminal device can display a pop-up window 2000. Pop-up window 2000 may include the prompt message "Page a can be displayed through a secondary window. Do you want to save page a?", as well as a confirmation button 2001 and a cancel button 2002. The confirmation button 2001 can be used to confirm saving page a, and the cancel button 2002 can be used to refuse saving page a. As shown in Figure 19(c), when the user wants to save page a, the user can click the confirmation button 2001. The following description will use the example of saving a page through clicking on an "in-application multi-window" as an example.
[0431] As shown in Figure 19(d), after the terminal device detects a click on "In-Application Multi-Window" or a click on the confirmation button 2001, it can create a secondary window (e.g., the primary window) 1910, load page a into the primary window 1910, and shrink the size of the main window 1900, reducing the full-screen main window 1900 to a non-full-screen window. Subsequently, the terminal device can display the shrunken main window 1900 in display area a and the primary window 1910 in display area b, so that page a is displayed through the primary window 1910 in display area b. Display areas a and b do not need to overlap.
[0432] In this configuration, the size of display area a can be the same as the size of display area b, the adjusted size of the main window 1900 can be the same as the size of display area a, and the size of the initial window 1910 can be the same as the size of display area b. That is, the terminal device can display the main window 1900 and the initial window 1910 in split-screen mode.
[0433] As shown in Figure 19(d), when page a is first displayed in the main window 1910, the terminal device can display page b, the parent page of page a, in the shrunk main window 1900.
[0434] It should be noted that when the terminal device creates the first requested window 1910, it can establish a corresponding page stack for the first requested window 1910, and the page stack corresponding to the first requested window 1910 is independent of the page stack corresponding to the main window 1900. That is, operations performed on the page displayed in the main window 1900 will not affect the page displayed in the first requested window 1910. Similarly, operations performed on the page displayed in the first requested window 1910 will not affect the page displayed in the main window 1900. It should be understood that the specific content of the page stack corresponding to the first requested window 1910 can be referred to the aforementioned content regarding the page stack corresponding to any of the requested windows; for the sake of simplicity, it will not be repeated here.
[0435] For example, when a terminal device displays page b through the main window 1900 and page a through the first request window 1910, as shown in Figure 20(a), when the user switches page b displayed in the main window 1900 to another page of application A (e.g., page c), the page displayed in the first request window 1910 does not need to change; that is, the first request window 1910 can continue to display page a. It should be understood that page c can be any page of application A. For example, page c can be a page N levels above page b, or a page M levels below page b, or a page at the same level as page b, and so on.
[0436] As shown in Figure 20(a), when page c is displayed in the main window 1900, if the user wants to continue to save page c, the user can click the menu bar 1901 at the top of the main window 1900. After the terminal device detects the click operation on the menu bar 1901, it can display the window control menu 1902.
[0437] After the page is temporarily saved, that is, after the main window 1900 is reduced to a non-full-screen display, the terminal device can adjust the menu items included in the window control menu 1902. For example, a "Full Screen" menu item can be added to the window control menu 1902. "Full Screen" can be used to display the main window 1900 in full screen to meet the user's need to view the main window 1900 in full screen. For example, as shown in Figure 20(b), after the terminal device detects a click operation on the menu bar 1901, it can display menu items such as "Multi-window within application", "Full Screen", "Replace application", and "Close window".
[0438] As shown in Figure 20(b), users can continue to click "In-App Multi-Window" to temporarily save page c for later viewing.
[0439] After the terminal device detects a click on "In-Application Multi-Window," it can create a secondary window (e.g., a second secondary window) 1920 and load page c into the second secondary window 1920 for display. While displaying page c through the second secondary window 1920, the terminal device can display the parent page of page c (e.g., page d) in the main window 1900. The size of the second secondary window 1920 can be the same as the size of the first secondary window 1920.
[0440] For example, the second window 1920 can be located to the left or right of the first window 1910.
[0441] As shown in Figure 20(c), when the second request window 1920 is located to the right of the first request window 1910, the second request window 1920 may be temporarily not displayed on the display interface. As shown in Figure 20(c), when the user performs a preset operation (e.g., a left swipe operation) on the display interface, the terminal device can move the main window 1900 and the first request window 1910 to the left, and can display the second request window 1920 to the right of the first request window 1910. That is, as shown in Figure 20(d), the terminal device can display both the first request window 1910 and the second request window 1920 on the display interface.
[0442] As shown in Figure 20(e), when the second request window 1920 is located to the left of the first request window 1910, after the second request window 1920 is created, the terminal device can display the second request window 1920 on the display interface, that is, the first request window 1910 can be temporarily not displayed on the display interface.
[0443] As shown in Figure 20(e), when the user performs a preset operation (such as a left swipe operation) on the display interface, the terminal device can move the main window 1900 and the secondary window 1920 to the left, and can display the primary window 1910 to the right of the secondary window 1920. That is, as shown in Figure 20(f), the terminal device can display the secondary window 1920 and the primary window 1910 on the display interface.
[0444] It should be noted that when the terminal device creates the second requested window 1920, it can establish a corresponding page stack for the second requested window 1920. This page stack is independent of both the page stack corresponding to the main window 1900 and the page stack corresponding to the first requested window 1910. It should be understood that the specific content of the page stack corresponding to the second requested window 1920 can be referenced from the aforementioned content regarding the page stack of any of the first requested windows; for the sake of simplicity, it will not be repeated here.
[0445] In one embodiment, when a user-stored page is displayed through a secondary window such as the primary window 1910 or the secondary window 1920, each secondary window may also include a menu bar. After the menu bar of a secondary window is clicked, the terminal device can display the window control menu corresponding to that secondary window. The window control menu corresponding to that secondary window includes one or more menu items, such as "Multi-window within application," "Fullscreen window," "Replace application," and "Close window." "Multi-window within application" can be used to temporarily store the page displayed in the secondary window through other secondary windows. "Fullscreen window" can be used to display the secondary window in full screen. "Replace application" can be used to switch the application launched in the secondary window, i.e., it can be used to switch the currently launched application A. "Close window" can be used to close the secondary window. The user can click the menu bar corresponding to a secondary window to display the window control menu corresponding to that secondary window, and can perform related operations on the menu items in the window control menu to operate the secondary window.
[0446] In another embodiment, each window may have a horizontal bar on its side, which can be used to adjust the size of the window. For example, a horizontal bar may be provided on the left or right side of the main window 1900, and dragging the horizontal bar on the side of the main window can adjust the size of the main window 1900. Similarly, a horizontal bar may be provided on the left or right side of a secondary window (e.g., the primary window 1910), and dragging the horizontal bar on the side of the primary window 1910 can adjust the size of the primary window 1910.
[0447] Similarly, in the user interface shown in Figures 14 to 17, after temporarily storing one or more windows, when the user clicks "Tile Windows," the terminal device can display the main window and secondary windows based on the dual-screen mode shown in Figures 19 and 20. For example, the size of display area a can be the same as the size of display area b, and the size of the main window can be the same as the size of the secondary window. The terminal device can display the main window in display area a, display a secondary window in display area b, and adjust the windows displayed on the display interface based on the user's preset operations.
[0448] The display order of each secondary window can be determined based on the temporary storage time of the page corresponding to each secondary window.
[0449] For example, secondary windows that are paused earlier can be displayed earlier; secondary windows that are paused later can be displayed later.
[0450] For example, if the storage time of page a corresponding to the first requested window 1910 is earlier than the storage time of page c corresponding to the second requested window 1920, after the user clicks "Tile Window," the terminal device can display the main window 1900 and the first requested window 1910 on the display interface. When the user performs a preset operation on the display interface (e.g., a left swipe operation), the terminal device can swipe the main window 1900 and the first requested window 1910 to the left to display the first requested window 1910 and the second requested window 1920 on the display interface. Furthermore, when the user performs another preset operation on the display interface (e.g., a right swipe operation), the terminal device can swipe the first requested window 1910 and the second requested window 1920 to the right to display the main window 1900 and the first requested window 1910 on the display interface.
[0451] For example, a secondary window that is paused earlier can be displayed later, and a secondary window that is paused later can be displayed earlier.
[0452] For example, if the storage time of page a corresponding to the first requested window 1910 is earlier than the storage time of page c corresponding to the second requested window 1920, after the user clicks "Tile Window," the terminal device can display the main window 1900 and the second requested window 1920 on the display interface. When the user performs a preset operation on the display interface (e.g., a left swipe operation), the terminal device can swipe the main window 1900 and the second requested window 1920 to the left to display the second requested window 1920 and the first requested window 1910 on the display interface. Furthermore, when the user performs another preset operation on the display interface (e.g., a right swipe operation), the terminal device can swipe the second requested window 1920 and the first requested window 1910 to the right to display the main window 1900 and the second requested window 1920 on the display interface.
[0453] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.
[0454] Corresponding to the application display method described in the above embodiments, this application also provides an application display device, which may include one or more modules. Each module of the application display device can correspondingly implement each step of the application display method.
[0455] It should be noted that the information interaction and execution process between the above-mentioned devices / units are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, and they will not be repeated here.
[0456] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.
[0457] This application also provides a terminal device, which includes at least one memory, at least one processor, and a computer program stored in the at least one memory and executable on the at least one processor. When the processor executes the computer program, it causes the terminal device to implement the steps in any of the above-described method embodiments. For example, the structure of the terminal device can be as shown in Figure 1.
[0458] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a terminal device, causes the terminal device to perform the steps in any of the above method embodiments.
[0459] This application provides a computer program product, which includes a computer program that, when run on a terminal device, causes the terminal device to perform the steps in any of the above method embodiments.
[0460] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments of this application can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable storage medium can include at least: any entity or device capable of carrying computer program code to a device / terminal device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium. Examples include USB flash drives, portable hard drives, magnetic disks, or optical disks.
[0461] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.
[0462] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0463] In the embodiments provided in this application, it should be understood that the disclosed devices / terminal equipment and methods can be implemented in other ways. For example, the device / terminal equipment embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling or direct coupling or communication connection may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.
[0464] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0465] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.
Claims
1. An application display method characterized by comprising: include: The first page of the first application is displayed in the first window; In response to an operation performed on the first page, a second page of the first application is displayed in the first window; the second page is a sub-page of the first page. In response to a first target operation on the first window, the second page is loaded into the second window, and the first page is displayed in the first window.
2. The method of claim 1, wherein, The first window and the second window each have their own page stack; wherein, before the first target operation is detected, the page stack of the first window includes the first page and the second page, and the second page is the top element of the page stack of the first window; when the second page is loaded into the second window and the first page is displayed in the first window, the top element of the page stack of the first window is the first page, the page stack of the second window includes the second page, and the second page is the top element of the page stack of the second window.
3. The method according to claim 1 or 2, characterized in that, The step of loading the second page into the second window in response to a first target operation on the first window includes: In response to a first target operation on the first window, the second page is loaded into the second window and displayed in the second window, wherein the second page is displayed in the second window and the second window does not overlap with the first window.
4. The method of claim 3, wherein, Before loading the second page into the second window in response to a first target operation on the first window, the method further includes: Display the first menu bar in the first window; In response to an operation on the first menu bar, a first window control menu is displayed; the first window control menu includes a first menu item. The step of loading the second page into the second window in response to a first target operation on the first window includes: In response to a first target operation on the first menu item, the second page is loaded into the second window and the second window is displayed.
5. The method of claim 4, wherein, The step of loading the second page into the second window and displaying the second window in response to a first target operation on the first menu item includes: Obtain the declaration information corresponding to the first application; When it is determined from the declaration information that the first application supports multi-window display, in response to the first target operation on the first menu item, the second page is loaded into the second window and the second window is displayed.
6. The method according to claim 1 or 2, characterized in that, After the second page is loaded into the second window, the second window is displayed stacked with the first window, and the second window is located behind the first window.
7. The method according to claim 6, characterized in that, Before loading the second page into the second window in response to a first target operation on the first window, the method further includes: Display the second menu bar in the first window; In response to an operation on the second menu bar, a second window control menu is displayed; the second window control menu includes second menu items. The step of loading the second page into the second window in response to a first target operation on the first window includes: In response to a first target operation on the second menu item, the second page is loaded into the second window.
8. The method according to claim 7, characterized in that, The step of loading the second page into the second window in response to a first target operation on the second menu item includes: In response to a first target operation on the second menu item, the second page is loaded into the second window, and the size of the first window is adjusted; the second window is located behind the adjusted first window, and the adjusted first window partially obscures the second window.
9. The method according to claim 7 or 8, characterized in that, After loading the second page into the second window in response to a first target operation on the second menu item, the method further includes: In response to an operation on the second menu bar, the second window control menu is displayed; the second window control menu includes a third menu item. In response to a second target operation on the third menu item, the second window is displayed.
10. The method according to claim 3, 4, 5 or 9, characterized in that, The display of the second window includes: The first window is minimized and displayed in a first display area, and the second window is displayed in a second display area; the first display area and the second display area do not overlap. Displaying the first page in the first window includes: The first page is displayed in the first display area through a scaled-down first window.
11. The method according to claim 10, characterized in that, After displaying the scaled-down first window in the first display area and the second window in the second display area, the method further includes: In response to a first preset operation on the first window and / or the second window, the second window is displayed in the first display area, and the first window is displayed in the second display area.
12. The method according to claim 10 or 11, characterized in that, After the first page is displayed in the first window, the method further includes: When the third page is displayed in the first window, in response to a third target operation on the first window, the third page is loaded into the third window, the third window is displayed in the second display area, and the second window is displayed in the second display area. In the first display area, a fourth page is displayed through the first window. The third page is the second page or another page of the first application. The fourth page is the parent page of the third page. The third window and the second window do not overlap.
13. The method according to claim 12, characterized in that, When displaying the second window and the third window in the second display area, the method further includes: In response to a second preset operation on the second window and / or the third window, the positions of the second window and the third window in the second display area are swapped.
14. The method according to claim 12 or 13, characterized in that, The size of the second window and the size of the third window are both smaller than the size of the first window after being reduced in size.
15. The method according to any one of claims 12 to 14, characterized in that, When displaying the second window and the third window in the second display area, the method further includes: In response to a third preset operation on the first window, the size of the first display area and the size of the second display area are adjusted. Based on the adjusted size of the first display area, the size of the first window is adjusted, and the adjusted first window is displayed in the first display area. Based on the adjusted size of the second display area, adjust the size of the second window and the size of the third window, and display the adjusted second window and the third window in the second display area.
16. The method according to claim 15, characterized in that, When the adjusted second window and the third window are displayed in the second display area, the second window and the third window are displayed stacked.
17. The method according to claim 16, characterized in that, When the second window is the focused window, the second window is located above the third window; and / or, When the second window is not the focus window, the third window is located on top of the second window.
18. The method according to any one of claims 15 to 17, characterized in that, The adjusted size of the first display area is the same as the adjusted size of the second display area.
19. The method according to any one of claims 3, 4, 5 or 9 to 18, characterized in that, After displaying the second window, the method further includes: In response to a fourth target operation on the second window, the second page is loaded into the fourth window and displayed in the second window, or the homepage of the first application is displayed.
20. The method according to any one of claims 3, 4, 5 or 9 to 18, characterized in that, When the first page is displayed in the first window, after displaying the second window, the method further includes: In response to an operation performed on the second page in the second window, the fifth page of the first application is displayed in the second window, while the first page remains displayed in the first window; wherein the fifth page is a sub-page of the second page.
21. The method according to any one of claims 1 to 20, characterized in that, After the first page is displayed in the first window, the method further includes: In response to an operation performed on the first page, a sixth page of the first application is displayed in the first window, the sixth page being a sub-page of the first page; In response to a fifth target operation on the first window, the sixth page is loaded into the fifth window, and the first page is displayed in the first window.
22. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it causes the terminal device to implement the application display method as described in any one of claims 1 to 21.
23. A computer program product, the computer program product comprising a computer program, characterized in that, When the computer program is executed on a terminal device, it causes the terminal device to implement the application display method as described in any one of claims 1 to 21.
24. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the terminal device, it causes the terminal device to implement the application display method as described in any one of claims 1 to 21.
