Page display method and device, electronic equipment and computer readable storage medium

Abstract

The present disclosure provides a page display method and device, electronic equipment and a computer readable storage medium. The page display method comprises: obtaining a small window display instruction for a target view page; in response to the small window display instruction, obtaining and holding a view controller of the target view page, so that the view controller of the target view page is not destroyed; and controlling the target view page to be displayed in a small window by the view controller. The embodiment of the present disclosure can display the target view page in a small window through the obtained view controller of the target view page, so that the view page does not need to be pulled again when displayed in a small window, thereby achieving the purposes of saving resources and improving efficiency.

Description

Technical Field

[0001] This disclosure relates to the field of computer and Internet technology, and in particular to a page display method and apparatus, electronic device and computer-readable storage medium. Background Technology

[0002] In related technologies, when a user views a specific view page (e.g., watching a live stream on that view page on a large screen), they are restricted to the page displayed on that screen and cannot interact with other view pages simultaneously. User interaction with the view page is limited to actions related to the current page. For example, when a user watches a live stream video of clothing on a shopping page, they cannot simultaneously view information about other shoe products. If the user wants to view or interact with other pages, they must close the current page (e.g., the current live stream page) and navigate to another page.

[0003] In related technologies, if you want to navigate from the current page (taking a streaming media page as an example) to another page and then return to the current page, you need to go through the following steps.

[0004] 1. Exit the current streaming media page.

[0005] 2. Close the current streaming media, destroy and release the system resources occupied by the current streaming media.

[0006] 3. Delete the current page, releasing the system resources occupied by the current page.

[0007] 4. Proceed to other pages to perform operations.

[0008] 5. Exit other pages and re-enter the current streaming media page to perform a series of related initialization tasks.

[0009] 6. Redisplay streaming information.

[0010] The entire process described above will cause significant waste in system resource usage and system overhead. For example, when re-entering the current page, initialization will be performed. On the one hand, certain network resources are required to obtain initialization information, and on the other hand, the system needs to reallocate resources for the display of the current page, which increases the system load.

[0011] Furthermore, the interactions related to entering the streaming media page are cumbersome, and the series of initialization tasks take a long time, resulting in a poor user experience. At the same time, destroying system resources and re-entering the streaming media page also requires writing a lot of business logic code at the business level, which infringes on existing logic. Summary of the Invention

[0012] The purpose of this disclosure is to provide a page display method, apparatus, electronic device, and computer-readable storage medium that can display the current page in a small window when entering other pages, without destroying the relevant information of the current page, thus saving system resources and system overhead.

[0013] Other features and advantages of this disclosure will become apparent from the following detailed description, or may be learned in part from practice of this disclosure.

[0014] This disclosure provides a page display method, including: obtaining a window display instruction for a target view page; in response to the window display instruction, obtaining and holding a view controller of the target view page so that the view controller of the target view page is not destroyed; and controlling the target view page to be displayed in a window through the view controller.

[0015] In some embodiments, the target view page includes interactive controls to be displayed and interactive controls to be hidden; wherein, controlling the display of the target view page in a small window through the view controller includes: determining the interactive controls to be displayed and the interactive controls to be hidden in the target view page through the view controller; and when the target view page is displayed in the small window through the view controller, displaying the interactive controls to be displayed and hiding the interactive controls to be hidden.

[0016] In some embodiments, the target view page is a view page in a target application, and the target system determines the page navigation path in the target application through a target view stack; wherein, the method further includes: responding to a large-screen display instruction for the target view page; delivering the view controller to the target view stack of the target system, so that when the target system controls the target view page to be displayed for large-screen display through the view controller, the interactive controls to be displayed and the interactive controls to be hidden are displayed.

[0017] In some embodiments, the target view page includes multiple interactive controls; wherein, determining the interactive controls to be displayed and the interactive controls to be hidden in the target view page by the view controller includes: determining whether each interactive control in the target view page carries a target marker; the view controller determines the interactive controls carrying the target marker as the interactive controls to be displayed; and the view controller determines the interactive controls not carrying the target marker as the interactive controls to be hidden.

[0018] In some embodiments, the target system includes a target view stack, which is a path stack for recording page jump records of the target application. The target application includes the target view page, and the target view stack includes a view controller for the target view page. Before obtaining a small window display instruction for the target view page, the method includes: the target system controlling the target view page to perform large-screen display through the view controller in the target view stack.

[0019] In some embodiments, the target application includes an intermediate controller; wherein, in response to the pop-up display instruction, acquiring and holding the view controller of the target view page includes: in response to the pop-up display instruction, the intermediate controller sends view controller acquisition information to the target system for the target view page, so that the intermediate controller acquires and holds the view controller of the target view page from the target system.

[0020] In some embodiments, obtaining a pop-up display instruction for a target view page includes: obtaining a leave instruction to leave the target view page; obtaining a target whitelist, the target whitelist being used to record a pop-up display list; and determining that the target view page is included in the target whitelist, thus determining that a pop-up display instruction for the target view page has been obtained.

[0021] This disclosure provides a page display device, including: a small window display instruction acquisition module, a view controller acquisition module, and a small window display module.

[0022] The small window display instruction acquisition module is used to acquire a small window display instruction for the target view page; the view controller acquisition module can be used to acquire and hold the view controller of the target view page in response to the small window display instruction, so that the view controller of the target view page is not destroyed; the small window display module can be used to control the target view page to be displayed in a small window through the view controller.

[0023] This disclosure provides an electronic device comprising: one or more processors; and a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the page display method described above.

[0024] This disclosure provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the page display method as described in any of the preceding embodiments.

[0025] This disclosure provides a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the page display method described above.

[0026] The page display method, apparatus, electronic device, and computer-readable storage medium provided in this disclosure can, on the one hand, display the target view page in a small window when entering other pages, allowing users to view the target view page in a small window while entering a new page, facilitating simultaneous operation on multiple windows; on the other hand, when displaying the small window, this disclosure does not re-fetch page resources but directly obtains the view controller of the target view page, and then controls the display of the target view page in the small window through the view controller, which saves system resources and system overhead and improves display efficiency.

[0027] It should be understood that the above general description and the following detailed description are merely exemplary and do not limit this disclosure. Attached Figure Description

[0028] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0029] Figure 1 A schematic diagram of an exemplary system architecture that can be applied to the page display method or page display apparatus of the embodiments of this disclosure is shown.

[0030] Figure 2 This is a flowchart illustrating a page display method according to an exemplary embodiment.

[0031] Figure 3 This is a page display method illustrated according to an exemplary embodiment.

[0032] Figure 4 This is a page display method illustrated according to an exemplary embodiment.

[0033] Figure 5 This is a block diagram illustrating a page display device according to an exemplary embodiment.

[0034] Figure 6 A schematic diagram of the structure of an electronic device suitable for implementing embodiments of the present disclosure is shown. Detailed Implementation

[0035] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the embodiments set forth herein; rather, they are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted.

[0036] The features, structures, or characteristics described in this disclosure can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a thorough understanding of embodiments of this disclosure. However, those skilled in the art will recognize that the technical solutions of this disclosure can be practiced with one or more specific details omitted, or other methods, components, apparatuses, steps, etc., can be employed. In other instances, well-known methods, apparatuses, implementations, or operations are not shown or described in detail to avoid obscuring various aspects of this disclosure.

[0037] The accompanying drawings are merely illustrative of this disclosure, and the same reference numerals in the drawings denote the same or similar parts, thus omitting repeated descriptions of them. Some block diagrams shown in the drawings do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0038] The flowchart shown in the accompanying drawings is merely illustrative and does not necessarily include all content and steps, nor does it require execution in the described order. For example, some steps may be broken down, while others may be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0039] In this specification, the terms “a,” “an,” “the,” “the,” and “at least one” are used to indicate the presence of one or more elements / components / etc.; the terms “comprising,” “including,” and “having” are used to indicate an open-ended inclusion and to mean that there may be other elements / components / etc. in addition to the listed elements / components / etc.; the terms “first,” “second,” and “third,” etc., are used only as markings and are not a limitation on the number of objects.

[0040] To better understand the above-mentioned objectives, features and advantages of the present invention, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be noted that, unless otherwise specified, the embodiments and features in the embodiments of this application can be combined with each other.

[0041] The exemplary embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0042] Figure 1 A schematic diagram of an exemplary system architecture that can be applied to the page display method or page display apparatus of the embodiments of this disclosure is shown.

[0043] like Figure 1 As shown, system architecture 100 may include terminal devices 101, 102, and 103, a network 104, and a server 105. Network 104 serves as the medium for providing communication links between terminal devices 101, 102, and 103 and server 105. Network 104 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.

[0044] Users can use terminal devices 101, 102, and 103 to interact with server 105 via network 104 to receive or send messages, etc. Terminal devices 101, 102, and 103 can be various electronic devices with displays and web browsing capabilities, including but not limited to smartphones, tablets, laptops, desktop computers, wearable devices, virtual reality devices, smart home devices, etc.

[0045] The terminal device may, for example, obtain a pop-up display instruction for the target view page; the terminal device may, for example, in response to the pop-up display instruction, obtain and hold the view controller of the target view page so that the view controller of the target view page is not destroyed; the terminal device may, for example, control the display of the target view page in the pop-up window through the view controller.

[0046] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. A terminal device can be a single physical server or a combination of multiple servers. Depending on actual needs, there can be any number of terminal devices, networks, and servers.

[0047] Server 105 can be a server that provides various services, such as a backend management server that supports the devices operated by users using terminal devices 101, 102, and 103. The backend management server can analyze and process received requests and other data, and feed the processing results back to the terminal devices.

[0048] A server can be a standalone physical server, a server cluster or a distributed system consisting of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. This disclosure does not impose any restrictions on this.

[0049] To address the technical issues mentioned in the background, many related technologies employ floating windows to independently display the target view page (e.g., playing a single streaming media stream). However, when displaying a page through a floating window, these technologies typically destroy and release the current page information (including streaming media information and interactive information on the streaming media page), and then retrieve the streaming media information from the backend server to display it in the floating window. When enlarging the floating window for large-screen display, the streaming media information in the floating window needs to be destroyed, and then the large-screen display page needs to be reinitialized, requiring a re-entry into the streaming media page, and all business logic also needs to be reinitialized.

[0050] Business logic refers to the page style after a user performs an operation, the code processing logic when data changes, and the interaction logic with the server, in order to provide users with corresponding service displays and operation feedback.

[0051] Therefore, the small window page displayed in the related technologies has too limited functionality (only displaying streaming media information) and cannot display all business logic; moreover, the floating small window provided by the related technologies will have a certain degree of intrusion on other Apps (Applications) and affect the user experience.

[0052] For example, the live streaming functions of apps like Taobao and Lili only have one live stream running from beginning to end. After setting up a floating window for playback, other functions such as chat rooms and gifts are no longer visible; only the live stream screen remains. When this live stream screen is displayed on a large screen, it's equivalent to re-entering the live stream room on behalf of the user, re-retrieving the live stream, re-entering the chat room, and reloading the gift function.

[0053] This disclosure employs the following technical means to retain all functions corresponding to the large-screen display and to reduce the size of the live stream; when returning to the large-screen display, it simply displays the previously retained content, rather than re-fetching the stream and re-initializing the process.

[0054] Figure 2This is a flowchart illustrating a page display method according to an exemplary embodiment. The method provided in this disclosure can be executed by any electronic device with computing power, for example, the method can be executed by the above-described... Figure 1 The terminal device in the embodiments is used to perform the execution, but this disclosure is not limited thereto.

[0055] Reference Figure 2 The page display method provided in this embodiment may include the following process.

[0056] In some embodiments, a user can view a page in a target application through a terminal device. The operating system in the terminal device will generate a view stack for the target application, which is used to record the page navigation records of the target application.

[0057] For example, when a target application is run for the first time on a terminal device, the operating system of that terminal device will generate a view stack for the target application. This view stack will include the view controller and navigation path for each independent view in the target application. For example, suppose the target application is the "Taobao" App, where the homepage view page -> My Taobao view page -> My Orders view page -> All View Pages are all independent pages. When you click the back button, you go back one level at a time. This is determined by the navigation path recorded in the view stack set by the operating system for the target application.

[0058] The target application can be a chat application, browser, shopping application, payment application, etc., and this disclosure does not impose any restrictions on it.

[0059] The target application may include multiple levels of view pages, including a target view page. The target view page may have a parent view page or a child view page, etc., and this disclosure does not limit this.

[0060] Therefore, the target system (e.g., the operating system of the terminal device where the target application resides) can include a target view stack. This target view stack is a path stack used to record page navigation records of the target application. The target application includes target view pages, and the target view stack includes view controllers for those target view pages. By controlling the view controllers in the target view stack, the target system of the terminal device can hold the view controller for the target view page and manipulate its display effects through that view controller.

[0061] In some embodiments, before obtaining instructions to display a small window for the target view page, the target system can control the target view page to be displayed on a large screen through the view controller in the target view stack.

[0062] Step S202: Obtain the small window display instruction for the target view page.

[0063] In some embodiments, when a user views a target view page on a large screen, the target view page may display a control for viewing in a small window. The user can trigger the control for viewing in a small window to view the target view page in a small window. In response to the triggering operation of the control, the target application will generate a small window display instruction for the target view page.

[0064] In other embodiments, a whitelist for displaying pop-ups (which may be called a target whitelist) can be pre-defined. The target whitelist is used to record the list of pop-up displays. When the target application receives a user's exit instruction to leave the target view page (e.g., to jump from the target view page to another view page, or to exit the current view page), the target application will retrieve the pre-defined target whitelist. Once the target application determines that the target view page is included in the target whitelist, it determines that it has obtained a pop-up display instruction for the target view page.

[0065] Additionally, a pre-defined list can be set, which includes at least one view page. When a user navigates from another view page in the target application to this at least one view page, the previous view page will be displayed in a small window. Therefore, once the target application receives an instruction to navigate from the target view page to a view page in the specified list, it is equivalent to receiving an instruction to display a small window for the target view page.

[0066] For example, suppose a user is currently watching a live stream, and the current live stream page is the page that needs to be set as a floating window. At this time, clicking to enter the user's "personal details page" can be a view page from at least one view page in the specified list.

[0067] In summary, this disclosure does not limit the generation format or triggering conditions of the small window display instruction for the target view page, and those skilled in the art can set it according to actual needs.

[0068] In step S204, in response to the pop-up display instruction, the view controller of the target view page is acquired and held so that the view controller of the target view page is not destroyed.

[0069] The view controller manages the views that make up the application's user interface. It is responsible for loading and processing these views, managing interactions with them, and coordinating how the views respond to changes in the data they display. View controllers can also coordinate with other view controller objects to help manage the overall application interface.

[0070] The main responsibilities of a view controller include: updating the view's content in response to changes in the underlying data, responding to user interactions with the view, adjusting the view size, and managing the layout of the entire interface.

[0071] View controllers form the foundation of an application's internal structure. Every application contains at least one view controller, and most applications contain multiple view controllers. Each view controller manages the application's user interface and the interaction between that interface and the underlying data. View controllers also facilitate transitions between different user interfaces.

[0072] In some embodiments, a view page can correspond to a view controller. Generally, when a user exits or navigates from a target view page, the operating system will release and destroy the view controller of that target view. The next time the user enters the target view page, a new view controller will be created for that target view page in the target view stack.

[0073] The destruction of the target view page can refer to the target system deleting the target view page, specifically the deletion of the data and instructions related to the target view page.

[0074] In this embodiment, in response to a window display instruction for the target view page, the target application retrieves the view controller of the target view page from the target view stack of the operating system to prevent the operating system from destroying the view controller of the target view page.

[0075] In some embodiments, the acquisition operation of the view controller described above can be completed by the target application (i.e., by modifying the code of the target application to implement the above process), or it can be completed by an intermediate controller in the target application. This disclosure does not limit this.

[0076] The so-called middle manager is a separate module of code that acts as an intermediary for coordination. When a user actively triggers an operation that requires a floating window, or when navigating between pages, they simply hand over the view controller that needs to be floating to the middle manager. The middle manager then handles the subsequent operation of creating the floating window and restoring the main screen display.

[0077] The intermediate controller here can be understood as a plugin that does not depend on any project or server. As long as this plugin is inserted into the corresponding position, it can control the zooming in and out operation of any terminal display page without affecting the specific content displayed on the page.

[0078] In some embodiments, if the target application obtains the view controller of the target view page through an intermediate controller, then in response to a pop-up display instruction, obtaining and holding the view controller of the target view page may include the following steps: in response to the pop-up display instruction, the intermediate controller in the target application sends view controller acquisition information to the target system for the target view page, so that the intermediate controller obtains and holds the view controller of the target view page from the target system.

[0079] After obtaining the view controller of the target view page, the entire view controller is added to the intermediate controller and held by the intermediate controller in memory. This disclosure does not restrict how the intermediate controller can be added by developers through code.

[0080] This disclosure proposes using the concept of an intermediate controller to manage view controllers that require floating windows. This reduces the intrusiveness of floating window-related operations on business logic code.

[0081] Step S206: Control the target view page to be displayed in the small window through the view controller.

[0082] In some embodiments, while controlling the display of the target view page in the small window, the target application can also add a series of gesture operations to the small window, such as pinch, drag, double-tap, etc., which are not limited in this disclosure.

[0083] In this embodiment, on the one hand, the target view page can be displayed in a small window when entering other pages, allowing users to view the target view page in a small window while entering a new page, facilitating simultaneous operation on multiple windows; on the other hand, when displaying the small window, this disclosure does not re-fetch page resources but directly obtains the view controller of the target view page, and then controls the display of the target view page in the small window through the view controller, which saves system resources and system overhead and improves display efficiency.

[0084] Figure 3 This is a page display method illustrated according to an exemplary embodiment.

[0085] In some embodiments, the view controller of the target view page can be used as a floating window carrier, retaining all the business logic and interactive UI control display of the original page.

[0086] The retention here refers to retention at the code memory level, without releasing the memory, and the interaction with the server is handled implicitly, while hiding means making it invisible to the user.

[0087] For some pages and interactive UI controls that need to be displayed, you only need to pre-label them with tags (the tag can be a fixed integer number) and add them to the whitelist of interactive controls in the floating window middle manager.

[0088] Among them, interactive UI controls marked with tags will be displayed to the user whether displayed in a small window or on a large screen (this can be called explicit display), while those without tags will be hidden when displayed in a floating small window and displayed to the user on a large screen (this can be called implicit display, that is, only the data in memory is retained but displayed through the page).

[0089] Understandably, whether interactive UI controls, whether tagged or not, actually need to be displayed to the user depends on the target application's settings. For example, if the target application sets a certain interactive UI control to only appear when the application is open, then after the application has been running for a period of time, regardless of whether the interactive UI control is tagged, it will not be displayed on the large screen.

[0090] In some embodiments, when displaying the target view page in a small window (e.g., a floating window), some interactive controls are not necessarily displayed, depending on the nature of the product. For example, when displaying a live stream through a floating window, even if the chat room interactive controls are displayed, the user may not be able to see them clearly. In this case, the chat room interactive controls can be hidden. However, while hiding the interactive controls, it is still necessary to receive chat content in real time. Therefore, the business logic is retained, but the display of interactive controls is hidden.

[0091] In some embodiments, the target view page includes interactive controls to be displayed and interactive controls to be hidden.

[0092] refer to Figure 3 The above page display method may include the following steps.

[0093] Step S302: Obtain the small window display instruction for the target view page.

[0094] In step S304, in response to the pop-up display instruction, the view controller of the target view page is acquired and held so that the view controller of the target view page is not destroyed.

[0095] Step S306: Determine the interactive controls to be displayed and the interactive controls to be hidden in the target view page through the view controller.

[0096] In some embodiments, the target view page includes multiple interactive controls. The target application (or an intermediate controller in the target application) can traverse all interactive controls in the target view page through the view controller to determine which interactive controls are to be displayed and which are to be hidden.

[0097] In some embodiments, the view controller can determine which interactive controls to be displayed and which interactive controls to be hidden by the following method: the view controller determines whether each interactive control in the target view page carries a target marker; the view controller determines the interactive controls carrying the target marker as interactive controls to be displayed; the view controller determines the interactive controls not carrying the target marker as interactive controls to be hidden.

[0098] In other embodiments, the view controller can use controls that are on the interactive control whitelist as interactive controls to be displayed, and controls that are not on the interactive control whitelist as interactive controls to be hidden.

[0099] In step S308, when the target view page is displayed in the small window by controlling the view controller, the interactive controls to be displayed are shown and the interactive controls to be hidden are hidden.

[0100] In this embodiment of the disclosure, by setting an intermediate controller in the target application, the change from a large screen display to a floating window and the change from a floating window back to a large screen state are handled by the plugin corresponding to the intermediate controller. Without intruding on the business logic, the original business logic is fully preserved using minimal integration code.

[0101] The technical solution provided in this embodiment marks interactive controls in the target view page with tags to achieve explicit display (displayed through the page when displayed in a small window) or implicit display (retaining memory information when displayed in a small window, but not displayed through the page). The technical solution provided in this embodiment eliminates the need to release or destroy the interactive control when implicitly displaying it through a small window. Therefore, when displaying the hidden interactive control on a large screen, there is no need to re-fetch its relevant information, saving system resources and improving display efficiency.

[0102] Figure 4 This is a page display method illustrated according to an exemplary embodiment.

[0103] In some embodiments, the target view page is a view page in the target application, and the target system determines the page navigation path in the target application through the target view stack.

[0104] refer to Figure 4 The above page display method may include the following steps.

[0105] Step S402: Obtain the small window display instruction for the target view page.

[0106] In step S404, in response to the pop-up display instruction, the view controller of the target view page is acquired and held so that the view controller of the target view page is not destroyed.

[0107] Step S406: Control the target view page to be displayed in the small window through the view controller.

[0108] Step S408, in response to a large-screen display instruction for the target view page.

[0109] Step S410: The view controller is delivered to the target view stack of the target system so that the target system can control the target view page for large-screen display through the view controller.

[0110] When a user triggers the restore screen event, the target application (or the intermediate controller inserted in the target application) will look for the view stack (the path stack of mobile terminal page jump records generated by the system) saved by the operating system (i.e. the target system), and return the view controller of the target view page to the operating system's view stack, so that the operating system can control the large screen to display the target view page by controlling the view controller.

[0111] In some embodiments, when the target system controls the target view page to be displayed on a large screen through the view controller, it displays interactive controls to be displayed and interactive controls to be hidden.

[0112] Understandably, whether interactive controls to be displayed or hidden actually need to be shown to the user depends on the target application's settings. For example, if the target application sets a certain interactive UI control to only appear when the application is open, then after the application has been running for a period of time, regardless of whether the interactive UI control is to be displayed or hidden, it will not be displayed on the large screen.

[0113] At this point, all floating windows have completed their restoration to the main screen, and the target application (or its intermediate controller) will relinquish control over the view, restoring the original main screen display state. These operations require only a few lines of code configuration from the original business layer, minimizing the impact on business logic code while fully preserving its functionality. Furthermore, it avoids excessive system resource consumption and waste, as well as a poor user experience, caused by multiple initializations.

[0114] The technical solution provided in this embodiment achieves a smooth transition between the small-window display and the large-screen display of the target view page by transferring the target view page controller (i.e., transferring the view controller of the target view page from the target view stack of the target system to the intermediate controller when the small window is displayed, so that the intermediate controller holds the view controller and thus prevents the view controller of the target view page from being destroyed; and transferring the view controller of the target view page from the intermediate controller to the target view stack of the target system when the large screen is displayed, so that the target system holds and controls the view controller). This eliminates the need for resource destruction and re-fetching, greatly saving system resources and improving display efficiency, thereby enhancing the user experience. On the other hand, the technical solution provided in this embodiment does not require releasing or destroying the interactive control to be hidden when the small window is displayed, so there is no need to re-fetch the relevant information of the interactive control to be hidden when the large screen is displayed, saving system resources and improving display efficiency.

[0115] The technical solution of this invention is designed as follows:

[0116] 1. Set up the view controller that needs to display the floating window.

[0117] 2. The floating window is triggered by user clicks or page navigation.

[0118] 3. The manager saves and displays the state of interactive UI controls based on the user's tag, and performs related interactive operations.

[0119] 4. The manager adds drag-and-drop and click gesture interactions to the floating window, as well as drag-and-drop window edge restrictions.

[0120] 5. When a user triggers the restore screen event, the intermediate controller is responsible for finding the view stack controlled by the system where the current floating window is located, and returning the view controller of the target view page to the view stack; when restoring to the original screen state, the original page UI display is restored, instead of destroying and rebuilding the original view controller.

[0121] The beneficial effects of the technical solution disclosed herein are as follows:

[0122] 1. You can switch freely between a floating window and a large screen without destroying or re-initializing the original page during the switch, reducing unnecessary consumption of system memory and the number of interactions with the server.

[0123] 2. The state transition animations are smooth and the recovery speed is fast, resulting in a good user experience.

[0124] 3. The business logic of the large screen is fully preserved, and the latest state is restored immediately. The real-time interaction is better than the floating window method provided by the system and the effect of separately managing the streaming media player.

[0125] 4. The floating window manager has low code intrusion, does not affect business logic, and has strong applicability, suitable for all pages based on view controllers.

[0126] 5. Wide range of applications: The standalone player provided by the system is only suitable for playing one streaming media at a time, and its interactive events are limited by the system. Standalone floating window players are also only suitable for playing one streaming media at a time; their creation and destruction consume excessive system resources and background interaction platforms, and restoring the state can easily cause timing deviations in streaming media playback. This floating window manager, however, does not have these problems. It can be used to display multiple streaming media on the same page, and it can also be used on pages where streaming media frequently switches.

[0127] Figure 5 This is a block diagram illustrating a page display device according to an exemplary embodiment. (Refer to...) Figure 5 The page display device 500 provided in this embodiment may include: a small window display instruction acquisition module 501, a view controller acquisition module 502, and a small window display module 503.

[0128] The small window display instruction acquisition module 501 can be used to acquire a small window display instruction for the target view page; the view controller acquisition module 502 can be used to acquire and hold the view controller of the target view page in response to the small window display instruction, so that the view controller of the target view page is not destroyed; the small window display module 503 can be used to control the target view page to be displayed in a small window through the view controller.

[0129] In some embodiments, the target view page includes interactive controls to be displayed and interactive controls to be hidden; wherein, the small window display module 503 may include: a hidden interactive control determination submodule and a hidden display submodule.

[0130] The hidden interactive control determination submodule can be used to determine the interactive controls to be displayed and the interactive controls to be hidden in the target view page through the view controller; the hidden display submodule can be used to display the interactive controls to be displayed and hide the interactive controls to be hidden when the target view page is displayed in a small window through the view controller.

[0131] In some embodiments, the target view page is a view page in the target application, and the target system determines the page jump path in the target application through the target view stack; wherein, the page display device 500 may further include: a large screen display instruction acquisition module and a large screen display module.

[0132] The large screen display instruction acquisition module can be used to respond to large screen display instructions for the target view page; the large screen display module can be used to deliver the view controller to the target view stack of the target system, so that the target system can control the target view page to perform large screen display through the view controller.

[0133] In some embodiments, the large-screen display module may include a control full-display submodule.

[0134] The full control display submodule can be used to display interactive controls to be displayed and interactive controls to be hidden when the target system controls the target view page to be displayed on a large screen through the view controller.

[0135] In some embodiments, the target system includes a target view stack, which is a path stack for recording page jump records of the target application. The target application includes a target view page, and the target view stack includes a view controller of the target view page. The target application includes an intermediate controller. Before obtaining the small window display instruction for the target view page, the page display device 500 may further include a large screen display module.

[0136] The large-screen display module can be used by the target system to control the target view page for large-screen display through the view controller in the target view stack.

[0137] In some embodiments, the view controller acquisition module 502 may include: an intermediate controller acquisition view controller submodule.

[0138] The intermediate controller's view controller acquisition submodule can be used to respond to a small window display instruction. The intermediate controller sends view controller acquisition information to the target system for the target view page so that the intermediate controller can obtain and hold the view controller of the target view page from the target system.

[0139] In some embodiments, the small window display instruction acquisition module 501 may include: an exit instruction acquisition submodule, a whitelist determination submodule, and a subordinate relationship determination submodule.

[0140] The module includes a "Leave Instruction Acquisition" submodule, which can be used to acquire the leave instruction for leaving the target view page; a "Whitelist Determination" submodule, which can be used to acquire the target whitelist, which records the list of items to be displayed in the pop-up window; and a "Subordination Determination" submodule, which can be used to determine if the target whitelist includes the target view page, thus confirming that a pop-up display instruction for the target view page has been acquired.

[0141] Since the functions of the device 500 have been described in detail in their respective method embodiments, they will not be repeated here.

[0142] The modules and / or sub-modules described in the embodiments of this application can be implemented in software or hardware. The described modules and / or sub-modules can also be located in a processor. The names of these modules and / or sub-modules do not, in some cases, constitute a limitation on the module and / or sub-module itself.

[0143] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0144] Furthermore, the above figures are merely illustrative of the processes included in the method according to exemplary embodiments of this disclosure and are not intended to be limiting. It is readily understood that the processes shown in the above figures do not indicate or limit the temporal order of these processes. Additionally, it is readily understood that these processes may be executed synchronously or asynchronously, for example, in multiple modules.

[0145] Figure 6 A schematic diagram of an electronic device suitable for implementing embodiments of the present disclosure is shown. It should be noted that... Figure 6 The electronic device 600 shown is merely an example and should not be construed as limiting the functionality and scope of use of the embodiments disclosed herein.

[0146] like Figure 6 As shown, the electronic device 600 includes a central processing unit (CPU) 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage section 608 into a random access memory (RAM) 603. The RAM 603 also stores various programs and data required for the operation of the electronic device 600. The CPU 601, ROM 602, and RAM 603 are interconnected via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0147] The following components are connected to I / O interface 605: an input section 606 including a keyboard, mouse, etc.; an output section 607 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN card, modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to I / O interface 605 as needed. A removable medium 611, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 610 as needed so that computer programs read from it can be installed into storage section 608 as needed.

[0148] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable storage medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 609, and / or installed from removable medium 611. When the computer program is executed by central processing unit (CPU) 601, it performs the functions defined above in the system of this application.

[0149] It should be noted that the computer-readable storage medium disclosed herein may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium may be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable storage medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable storage medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0150] In another aspect, this application also provides a computer-readable storage medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable storage medium carries one or more programs that, when executed by the device, enable the device to perform the following functions: acquiring a window display instruction for a target view page; in response to the window display instruction, acquiring and holding a view controller of the target view page so that the view controller is not destroyed; and controlling the display of the target view page in the window through the view controller.

[0151] According to one aspect of this application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in various optional implementations of the above embodiments.

[0152] Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions of the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) and includes several instructions to cause a computing device (such as a personal computer, server, mobile terminal, or smart device, etc.) to execute the method according to the embodiments of this disclosure, for example... Figure 2 , Figure 3 ,or Figure 4 One or more of the steps shown.

[0153] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not claimed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the claims.

[0154] It should be understood that this disclosure is not limited to the detailed structures, drawing arrangements or implementations shown herein; rather, this disclosure is intended to cover various modifications and equivalent arrangements contained within the spirit and scope of the appended claims.

Claims

1. A page display method, characterized in that, include: The target application runs on a terminal device, and the operating system on the terminal device generates a target view stack for the target application. The target view stack is a path stack used to record the page jump records of the target application. The target application includes a target view page, and the target view stack includes the view controller of the target view page. The operating system controls the target view page to be displayed on a large screen through the view controller in the target view stack; The target application obtains a pop-up display instruction for the target view page; In response to the small window display instruction, the intermediate controller in the target application sends a view controller acquisition message to the operating system for the target view page, so that the intermediate controller can acquire and hold the view controller of the target view page from the operating system, so that the view controller of the target view page is not destroyed. The intermediate controller is a plugin in the target application; The intermediate controller controls the display of the target view page in the small window through the view controller; When the large screen restoration event is triggered, the target application returns the view controller of the target view page to the view stack of the operating system, so that the operating system can control the target view page to display on the large screen through the view controller.

2. The method according to claim 1, characterized in that, The target view page includes interactive controls to be displayed and interactive controls to be hidden; wherein, controlling the display of the target view page in a small window through the view controller includes: The view controller determines the interactive controls to be displayed and the interactive controls to be hidden in the target view page. When the target view page is displayed in the small window by the view controller, the interactive control to be displayed is shown, and the interactive control to be hidden is hidden.

3. The method according to claim 2, characterized in that, The target view page includes multiple interactive controls; wherein, determining the interactive controls to be displayed and the interactive controls to be hidden in the target view page through the view controller includes: The view controller determines whether each interactive control in the target view page carries a target marker. The view controller identifies the interactive control carrying the target marker as the interactive control to be displayed; The view controller identifies interactive controls that do not carry the target marker as the interactive controls to be hidden.

4. The method according to claim 1, characterized in that, Retrieve instructions for displaying a small window for the target view page, including: Obtain the exit command to leave the target view page; Obtain the target whitelist, which is used to record the list displayed in the small window; If the target whitelist includes the target view page, then it is determined that a pop-up display instruction for the target view page has been obtained.

5. A page display device, characterized in that, The target application runs on a terminal device, and the operating system on the terminal device generates a target view stack for the target application. The target view stack is a path stack used to record the page jump records of the target application. The target application includes a target view page, and the target view stack includes the view controller of the target view page. The operating system controls the target view page for large-screen display through the view controller in the target view stack; wherein, the device includes: The pop-up display instruction acquisition module is used to obtain pop-up display instructions for the target view page from the target application. A view controller acquisition module is used to respond to the small window display instruction by sending view controller acquisition information to the operating system for the target view page through an intermediate controller in the target application, so that the intermediate controller can acquire and hold the view controller of the target view page from the operating system, so that the view controller of the target view page is not destroyed; wherein the intermediate controller is a plugin in the target application. The small window display module is used to control the display of the target view page in the small window through the view controller; The large-screen display module is used so that when a large-screen restoration event is triggered, the target application returns the view controller of the target view page to the view stack of the operating system, so that the operating system can control the target view page to perform large-screen display through the view controller.

6. An electronic device, characterized in that, include: Memory; as well as A processor coupled to the memory, the processor being used to execute the page display method as described in any one of claims 1-4 based on instructions stored in the memory.

7. A computer-readable storage medium having a program stored thereon that, when executed by a processor, implements the page display method as described in any one of claims 1-4.

Images