CN114003838A

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

Info

Publication number: CN114003838A
Application number: CN202111273052.2A
Authority: CN
Inventors: 孙道然
Original assignee: Tianjiu Sharing Network Technology Group Co ltd
Current assignee: Tianjiu Sharing Network Technology Group Co ltd
Priority date: 2021-10-29
Filing date: 2021-10-29
Publication date: 2022-02-01

Abstract

The disclosure provides a page display method and device, an electronic device and a computer readable storage medium. The page display method comprises the following steps: acquiring a small window display instruction aiming at a target view page; responding to the small window display instruction, and acquiring and holding the 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 through the view controller. According to the embodiment of the disclosure, the target view page can be subjected to small window display through the obtained view controller of the target view page, so that the view page does not need to be pulled again during small window display, and the purposes of saving resources and improving efficiency are achieved.

Description

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

Technical Field

The present disclosure relates to the field of computer and internet technologies, and in particular, to a page display method and apparatus, an electronic device, and a computer-readable storage medium.

Background

In the related art, when a user views a certain view page (for example, views streaming media in the view page through a large screen), the user is limited to the current screen presentation page, and cannot operate other view pages while viewing the view page, and the user interaction with the view page is limited to the related operation on the current page. For example, when a user watches a live video of a certain clothing on a certain shopping page, the user cannot simultaneously view related information of other shoe products. If the user wants to view or operate other pages, only the current page (for example, the current streaming media page) can be closed, and the user enters other pages to operate.

In the related art, if it is desired to enter other pages from the current page (for example, streaming media page) and then return to the current page, the following steps are required

1. And exiting the current streaming media page.

2. And closing the current streaming media, destroying and releasing the occupation of the current streaming media on system resources.

3. And destroying the current page and releasing the occupation of the current page on the related system resources.

4. And entering other pages for operation.

5. And exiting other pages, re-entering the current streaming media page of the current page, and performing a series of related initialization work.

6. The streaming media information is re-displayed.

The whole process can cause great waste on system resource occupation and system overhead, for example, initialization is performed when the current page is re-entered, on one hand, certain network resources need to be occupied to perform initialization information acquisition, and on the other hand, the system needs to redistribute resources for the display of the current page, so that the load of the system is increased.

And the related interaction of the entering streaming media page is complicated, and a series of initialization work has long waiting time, so that the user experience is poor. Meanwhile, a lot of service logic codes need to be written in a service layer to destroy occupied system resources and re-enter a streaming media page, so that the existing logic is invaded.

Disclosure of Invention

The present disclosure aims to provide a page display method, a page display apparatus, an electronic device, and a computer-readable storage medium, which can display a current page through a small window when entering other pages, without destroying related information of the current page, thereby saving system resources and system overhead.

Additional features and advantages of the disclosure will be set forth in the detailed description which follows, or in part will be obvious from the description, or may be learned by practice of the disclosure.

The embodiment of the disclosure provides a page display method, which includes: acquiring a small window display instruction aiming at a target view page; responding to the small window display instruction, and acquiring and holding the 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 through the view controller.

In some embodiments, the target view page includes an interaction control to be displayed and an interaction control to be hidden; wherein controlling the target view page to be displayed in a small window by the view controller includes: determining the interactive control to be displayed and the interactive control to be hidden in the target view page through the view controller; and when the view controller controls the target view page to be displayed in the small window, displaying the interactive control to be displayed and hiding the interactive control to be hidden.

In some embodiments, the target view page is a view page in a target application, and a target system determines a page jump path in the target application through a target view stack; wherein the method further comprises: responding to a large screen display instruction aiming at the target view page; and delivering the view controller to the target view stack of the target system, so that the target system displays the interactive control to be displayed and the interactive control to be hidden when the target system controls the target view page to display on a large screen through the view controller.

In some embodiments, the target view page includes a plurality of interaction controls; determining the interactive control to be displayed and the interactive control to be hidden in the target view page through the view controller comprises the following steps: determining whether each interactive control in the target view page carries a target mark through the view controller; the view controller determines an interactive control carrying a target mark as the interactive control to be displayed; and the view controller determines the interactive control not carrying the target mark as the interactive control to be hidden.

In some embodiments, the target system comprises a target view stack, the target view stack being a path stack for recording page jump records of a target application, the target application comprising the target view page, the target view stack comprising a view controller of the target view page; before acquiring a small window display instruction for a target view page, the method comprises the following steps: and the target system controls the target view page to display on a large screen through the view controller in the target view stack.

In some embodiments, the target application comprises an intermediate controller; wherein, in response to the small window display instruction, the view controller for acquiring and holding the target view page comprises: and responding to the small window display instruction, the intermediate controller sends view controller acquisition information to the target system aiming at the target view page, so that the intermediate controller acquires and holds the view controller of the target view page from the target system.

In some embodiments, obtaining a widget display instruction for a target view page comprises: acquiring a leaving instruction for leaving the target view page; acquiring a target white list, wherein the target white list is used for recording a small window display list; and if the target white list comprises the target view page, determining that a small window display instruction for the target view page is obtained.

The disclosed embodiment provides a page display device, including: the device comprises a small window display instruction acquisition module, a view controller acquisition module and a small window display module.

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

An embodiment of the present disclosure provides an electronic device, including: one or more processors; a storage device, configured to store one or more programs, and when the one or more programs are executed by the one or more processors, enable the one or more processors to implement any of the page display methods described above.

The embodiment of the present disclosure provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the page display method according to any one of the above items.

Embodiments of the present disclosure provide a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the page display method.

According to the page display method and device, the electronic device and the computer readable storage medium provided by the embodiment of the disclosure, on one hand, the target view page can be displayed through the small window when entering other pages, so that a user can simultaneously view the target view page through the small window when entering a new page, and a plurality of windows can be simultaneously operated conveniently; on the other hand, when the small window is displayed, the page resources are not pulled again, but the view controller of the target view page is directly obtained, and then the target view page is controlled to be displayed in the small window through the view controller, so that the system resources and the system overhead are saved, and the display efficiency is improved.

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

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure. It is to be understood that the drawings in the following description are merely exemplary of the disclosure, and that other drawings may be derived from those drawings by one of ordinary skill in the art without the exercise of inventive faculty.

Fig. 1 shows a schematic diagram of an exemplary system architecture of a page display method or a page display apparatus to which an embodiment of the present disclosure may be applied.

FIG. 2 is a flowchart illustrating a page display method according to an example embodiment.

FIG. 3 illustrates a page display method according to an exemplary embodiment.

FIG. 4 illustrates a page display method according to an exemplary embodiment.

Fig. 5 is a block diagram illustrating a page display apparatus according to an exemplary embodiment.

FIG. 6 illustrates a schematic structural diagram of an electronic device suitable for use in implementing embodiments of the present disclosure.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The same reference numerals denote the same or similar parts in the drawings, and thus, a repetitive description thereof will be omitted.

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

The drawings are merely schematic illustrations of the present disclosure, in which the same reference numerals denote the same or similar parts, and thus, a repetitive description thereof will be omitted. Some of the block diagrams shown in the figures do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.

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

In this specification, the terms "a", "an", "the", "said" and "at least one" are used to indicate the presence of one or more elements/components/etc.; the terms "comprising," "including," and "having" are intended to be inclusive and mean that there may be additional elements/components/etc. other than the listed elements/components/etc.; the terms "first," "second," and "third," etc. are used merely as labels, and are not limiting on the number of their objects.

In order that the above objects, features and advantages of the present invention can be more clearly understood, the present invention will be described in further detail below with reference to the accompanying drawings and specific embodiments, it being understood that the embodiments and features of the embodiments of the present application can be combined with each other without conflict.

The following detailed description of exemplary embodiments of the disclosure refers to the accompanying drawings.

As shown in fig. 1, the system architecture 100 may include

terminal devices

101, 102, 103, a network 104, and a server 105. The network 104 serves as a medium for providing communication links between the

terminal devices

101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.

The user may use the

terminal devices

101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. The

terminal devices

101, 102, 103 may be various electronic devices having display screens and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, wearable devices, virtual reality devices, smart homes, and the like.

The terminal device may, for example, obtain a small window display instruction for a target view page; the terminal device can acquire and hold the view controller of the target view page, for example, in response to the small window display instruction, so that the view controller of the target view page is not destroyed; the terminal device may control the target view page to be displayed in the small window, for example, through the view controller.

It should be understood that the number of terminal devices, networks and servers in fig. 1 is only illustrative, and the terminal device may be a physical server or may be composed of a plurality of servers, and there may be any number of terminal devices, networks and servers according to actual needs.

The server 105 may be a server that provides various services, such as a background management server that provides support for devices operated by users using the

terminal apparatuses

101, 102, 103. The background management server can analyze and process the received data such as the request and feed back the processing result to the terminal equipment.

The server may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server that provides basic cloud computing services such as a cloud service, a cloud database, cloud computing, a cloud function, cloud storage, a Network service, cloud communication, a middleware service, a domain name service, a security service, a CDN (Content Delivery Network), a big data and artificial intelligence platform, and the like, which is not limited in this disclosure.

In order to solve the technical problem mentioned in the background art, in the related art, a floating small window is often used to independently display a target view page (e.g., play a single streaming media). However, when the page is displayed through the floating widget, the related art usually destroys and releases the current page information (including streaming media information, interaction information on the streaming media page, and the like), and then pulls the streaming media information in the page from the background server again to display in the floating widget; when the floating small window is enlarged to display the large screen, the streaming media information in the floating small window needs to be destroyed, then the large screen display page is reinitialized, the streaming media page is entered once again, and all the business logic is reinitialized once.

The business logic refers to processing logic of codes and interaction logic with the server when the page style and data change after operation of the user, so as to provide corresponding service display and operation feedback for the user.

Therefore, the functions of the small window pages displayed by the small windows in the related art are too single (only stream media information is displayed), and all business logic cannot be displayed; moreover, for the floating small window provided by the related art, certain intrusiveness is generated on other apps (applications), and the user experience is influenced.

For example, the live broadcast function of the software of 'a treasure' and 'a li' is only carried out by one live broadcast stream from beginning to end, after the floating small window is set for playing, other function points such as chat rooms and gifts cannot be seen, and only the live broadcast picture is kept. When the live broadcast pictures are played on a large screen, the live broadcast pictures equivalently replace user operation to reenter a live broadcast room, pull the live broadcast stream, reenter a chat room and reload the gift function.

The method adopts the following technical means, reserves all corresponding functions during large-screen display, and reduces the live stream; when the screen is returned to large screen display, the original reserved content is displayed, and the operations of re-pulling the stream and re-initializing are not performed.

FIG. 2 is a flowchart illustrating a page display method according to an example embodiment. The method provided by the embodiment of the present disclosure may be executed by any electronic device with computing processing capability, for example, the method may be executed by the terminal device in the embodiment of fig. 1, but the present disclosure is not limited thereto.

Referring to fig. 2, a page display method provided by an embodiment of the present disclosure may include the following processes.

In some embodiments, a user may view a certain page in a target application through a terminal device, and an operating system in the terminal device may generate a view stack for the target application, where the view stack is used to record a page jump record of the target application.

For example, when a target application runs on a certain terminal device for the first time, the operating system of the terminal device generates a view stack for the target application, and the view stack will include a view controller and a jump path of each independent view in the target application, for example, assuming that the target application is "a treasure" App, where a home page view page- > my X treasure view page- > my order view page- > all view pages are independent pages, and when a return back is clicked, a layer-by-layer return is performed, which is determined by the jump path recorded in the view stack set by the operating system for the target application.

The target application may be a chat application, a browser, a shopping application, a payment application, etc., which is not limited by this disclosure.

The target application may include a plurality of levels of view pages, a target view page is included in the plurality of levels of view pages, and the target view page may be an upper level view page or a lower level view page, which is not limited in this disclosure.

Therefore, a target system of the terminal device (for example, an operating system of the terminal device) where the target application is located may include a target view stack, where the target view stack is a path stack for recording a page jump record 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. By controlling the view controller in the target view stack, the target system of the terminal device can hold the view controller of the target view page, and the display effect of the target view page is controlled by the view controller.

In some embodiments, the target system may control the target view page to be displayed on a large screen through a view controller in the target view stack before acquiring the small window display instruction for the target view page.

Step S202, acquiring a small window display instruction aiming at a target view page.

In some embodiments, when a user views a target view page through a large screen, the target view page may display a control for small window viewing, the user may perform small window viewing on the target view page by triggering the control for small window viewing, and a target application may generate a small window display instruction for the target view page in response to a triggering operation of the control.

In some other embodiments, a small window display white list (which may be referred to as a target white list) may be preset, and the target white list is used to record the small window display list. When the target application acquires a leaving instruction given by a user to leave a target view page (for example, jumping from the target view page to other view pages or exiting from the current view page), the target application acquires the preset target white list; once the target application determines that the target view page is included in the target whitelist, it is determined that a widget display instruction for the target view page is obtained.

In addition, a designated list can be preset, the designated list comprises at least one view page, and when a user jumps to the at least one view page from other view pages of the target application, the view page before jumping is displayed in a small window. Therefore, once the target application receives an instruction to jump from the target view page to a certain view page in the specified list, the instruction is equivalent to obtaining a small window display instruction for the target view page.

For example, assuming that the user is currently watching a live broadcast, the current live broadcast page is a page that needs to set a floating small window, and the point clicks into a "personal details page" of the user, where the "personal details page" may be a view page in at least one view page in the specified list.

In summary, the present disclosure does not limit the generation form of the widget display instruction for the target view page and the trigger condition, and those skilled in the art can set the generation form and the trigger condition according to actual requirements.

Step S204, responding to the small window display instruction, acquiring and holding the view controller of the target view page, so that the view controller of the target view page is not destroyed.

Among other things, the View controller (ViewController) manages the views that form part of the application user interface, and is responsible for loading and processing these views, managing the interactions with these views, and coordinating the responses of the views to changes in the data content they expose. The view controller can also work in coordination with other view controller objects to help manage the overall interface of the application.

The main responsibilities of the view controller include the following: updating the contents of the view in response to changes in the underlying data, in response to user interaction with the view, resizing the view, and managing the layout of the entire interface.

The view controller is the basis for the internal structure of the application. Each application contains at least one view controller, and most applications contain multiple view controllers. Each view controller manages the user interface of the application and the interaction between the interface and the underlying data. The view controller also facilitates transitions between different user interfaces.

In some embodiments, one view page may correspond to one view controller. Generally, after the user exits or jumps from the target view page, the operating system controls to release and destroy the view controller of the target view, and when the user enters the target view page next time, the view controller is created for the target view page in the target view stack.

The destruction of the target view page may refer to the target system deleting the target view page, and specifically may refer to deleting data and instructions related to the target view page.

In this embodiment, in response to a widget display instruction for a target view page, a target application will fetch a view controller of the target view page from a target view stack of an operating system, so as to avoid the operating system destroying the view controller of the target view page.

In some embodiments, the above-mentioned obtaining operation of the view controller may be performed by the target application (i.e. modifying the code of the target application to implement the above-mentioned process), and may also be performed by an intermediate controller in the target application, which is not limited by the present disclosure.

So-called intermediate manager, which is to extract a piece of module code alone to play an intermediate role in cooperation. When a user actively triggers the operation of needing to hover the small window, or when a page jumps, the view controller needing to hover is delivered to the middle manager, and the subsequent operation of changing into the hover small window and the restoration of the large-screen display are finished by the middle manager.

The intermediate controller can be understood as a plug-in which does not depend on any project or any server, and the plug-in can control the zooming-in and zooming-out operations of any terminal display page by being inserted into the corresponding position, and meanwhile, the specific content display on the display page is not influenced.

In some embodiments, if the target application obtains the view controller of the target view page through the intermediate controller, the obtaining and holding the view controller of the target view page in response to the widget display instruction may include the steps of: and the intermediate controller in the target application responds to the small window display instruction, and the intermediate controller sends view controller acquisition information to the target system aiming at the target view page so that the intermediate controller acquires and holds the view controller of the target view page from the target system.

After the view controller of the target view page is obtained, the whole view controller is added to the intermediate controller, held by the intermediate controller and kept in the memory. Wherein the intermediate management can be added to the intermediate controller in the form of code by a developer, which is not limited by the present disclosure.

The disclosed design addresses the idea of using an intermediate controller to manage a view controller that requires a floating widget. Reducing the aggressiveness of the floating widget-related operations to business logic code.

And step S206, controlling the target view page to be displayed in the small window through the view controller.

In some embodiments, the target application may also add a series of gesture operations to the widget while controlling the display of the target view page in the widget, such as pinching, dragging, double-clicking, and the like, which is not limited by the present disclosure.

According to the embodiment, on one hand, the target view page can be displayed through the small window when entering other pages, so that a user can simultaneously view the target view page through the small window when entering a new page, and simultaneous operation can be conveniently performed on a plurality of windows; on the other hand, when the small window is displayed, the page resources are not pulled again, but the view controller of the target view page is directly obtained, and then the target view page is controlled to be displayed in the small window through the view controller, so that the system resources and the system overhead are saved, and the display efficiency is improved.

FIG. 3 illustrates a page display method according to an exemplary embodiment.

In some embodiments, the view controller of the target view page may be used as a floating window carrier, and all business logic and interactive UI control presentations of the original page may be retained.

The reservation is reserved at the code memory level, the memory is not released, the invisible processing is interacted with the server, and the hiding is invisible for a user.

For some pages and interactive UI controls needing to be displayed, only a Tag (the Tag can be a fixed shaping number) needs to be marked in advance, and the Tag is added into an interactive control white list of a floating widget middle manager.

The interactive UI control marked with Tag is displayed to the user (may be referred to as explicit display) no matter displayed through a small window or a large screen, and the interactive UI control not marked with Tag is hidden when displayed through a floating small window and displayed to the user when displayed through a large screen (may be referred to as implicit display, where only data in the memory is retained but displayed through a page).

It will be appreciated that whether or not the tagged or untagged interactive UI controls are actually required to be exposed to the user will also depend on the settings of the target application. For example, if the target application sets that an interactive UI control is only presented when the application is opened, after the application has run for a period of time, no matter whether the interactive UI control has a Tag or not, the interactive UI control will not be displayed when the application is displayed on a large screen.

In some embodiments, if the target view page is exposed in a small window (e.g., a floating small window), some interactive controls are not necessarily exposed, depending on the nature of the product. For example, when the live broadcast is displayed through the floating small window, even if the interactive control of the chat room is displayed, the user does not need to see clearly, at this time, the interactive control of the chat room can be hidden, but the content during the chat is received in real time while the interactive control is hidden, so that the business logic is kept, and the display of the hidden interactive control is realized.

In some embodiments, the target view page includes an interaction control to be displayed and an interaction control to be hidden.

Referring to fig. 3, the above-described page display method may include the following steps.

Step S302, a small window display instruction for the target view page is obtained.

Step S304, responding to the small window display instruction, acquiring and holding the view controller of the target view page, so that the view controller of the target view page is not destroyed.

Step S306, the interactive control to be displayed and the interactive control to be hidden in the target view page are determined through the view controller.

In some embodiments, the target view page includes a plurality of interaction controls, and the target application (or an intermediate controller in the target application) may traverse through all of the interaction controls in the target view page via the view controller to determine which interaction controls are interaction controls to be displayed and which are interaction controls to be hidden.

In some embodiments, the view controller may then be implemented by the following method when determining the interactive control to be displayed and the interactive control to be hidden: determining whether each interactive control in a target view page carries a target mark through a view controller; the view controller determines the interactive control carrying the target mark as an interactive control to be displayed; and the view controller determines the interactive control not carrying the target mark as the interactive control to be hidden.

In some other embodiments, the view controller may treat controls that exist on the interaction control white list as interaction controls to be displayed, and may treat controls that are not on the interaction control white list as interaction controls to be hidden.

And S308, when the view controller controls the target view page to be displayed in the small window, displaying the interactive control to be displayed and hiding the interactive control to be hidden.

According to the embodiment of the disclosure, the intermediate controller is arranged in the target application, so that the change from the large-screen display to the floating small window of the page and the change from the floating small window to the large-screen state are sent to the plug-in corresponding to the intermediate controller, and under the condition of not invading the service logic, the original service logic is completely reserved by using the least integration codes.

According to the technical scheme provided by the implementation, the interactive control in the target view page is marked through the mark so as to realize explicit display (the interactive control can be displayed through the page when displayed in the small window) or implicit display (the memory information is reserved when the small window is displayed, but the interactive control is not displayed through the page). According to the technical scheme provided by the embodiment, when the interactive control to be hidden is implicitly displayed through the small window, the interactive control does not need to be released or destroyed, and then when the interactive control to be hidden is displayed on the large screen, the related information of the interactive control to be hidden does not need to be pulled again, so that on one hand, system resources are saved, and on the other hand, the display efficiency is improved.

FIG. 4 illustrates a page display method according to an exemplary embodiment.

In some embodiments, the target view page is a view page in the target application, and the target system determines a page jump path in the target application through the target view stack.

Referring to fig. 4, the above-described page display method may include the following steps.

Step S402, acquiring a small window display instruction aiming at the target view page.

Step S404, responding to the small window display instruction, acquiring and holding the view controller of the target view page, so that the view controller of the target view page is not destroyed.

And step S406, controlling the target view page to be displayed in the small window through the view controller.

Step S408, in response to the large screen display instruction for the target view page.

And step S410, delivering the view controller to a target view stack of the target system so that the target system controls a target view page to display on a large screen through the view controller.

When a user triggers to restore a large-screen event, a target application (or an intermediate controller inserted in the target application) searches a view stack (a path stack recorded by a moving end page jump generated by the system) stored by an operating system (namely the target system), and returns a view controller of a target view page to the view stack of the operating system, so that the operating system controls a large screen to display the target view page through controlling the view controller.

In some embodiments, when the target system controls the target view page to perform large-screen display through the view controller, the interaction control to be displayed and the interaction control to be hidden are displayed.

It will be appreciated that the need for those interactive controls to be displayed and hidden to be exposed to the user is also dependent on the settings of the target application. For example, if the target application sets that a certain interaction UI control is only presented when the application is opened, after the application has run for a period of time, no matter whether the interaction UI control is to be displayed or hidden, the interaction UI control will not be displayed when displayed on a large screen.

At this time, the service processing is completed when all the floating widgets are restored to the large screen, the target application (or the intermediate controller in the target application) gives up the management right for view control, and the original large screen display state is restored. In the operations, the original service layer only needs to be configured by a plurality of lines of codes, the influence of the service logic codes is reduced to the minimum, the full reservation of the service logic code function is realized, and excessive system resource consumption and waste and poor user experience caused by multiple initializations are avoided.

According to the technical scheme provided by the implementation, on one hand, the transition between the small-window display and the large-screen display of the target view page is realized through the transfer of the target view page controller (namely, the view controller of the target view page is transferred 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 further the view controller of the target view page is not destroyed; on the other hand, according to the technical scheme provided by the embodiment, when the interactive control to be hidden is displayed on the small window, the interactive control does not need to be released or destroyed, and then, when the interactive control to be hidden is displayed on the large screen, the related information of the interactive control to be hidden does not need to be pulled again, so that on one hand, system resources are saved, and on the other hand, the display efficiency is improved.

The technical scheme of the invention is designed as follows:

1. a view controller is provided that needs to display the floating widget.

2. And the user actively triggers by clicking operation or triggers the floating small window when the page jumps.

3. And the manager performs storage and display and hiding processing on the state of the interactive UI control according to the Tag marked by the user, and executes related interactive operation.

4. The manager adds relevant dragging, click gesture interaction and dragging window edge limitation to the floating small window.

5. A user triggers a large screen recovery event, the intermediate controller is responsible for searching a view stack controlled by a system where the current floating small window is located, and the view controller of the target view page returns to the view stack; and when the original large screen state is recovered, the original page UI display is recovered instead of destroying the reconstructed original view controller.

The technical scheme of the disclosure has the beneficial effects that:

1. the suspended small window and the large screen are switched at will, the original page cannot be destroyed and reinitialized during the switching period, unnecessary consumption of a system memory is reduced, and interaction times with a server are reduced.

2. The state switching animation is excessively smooth, the recovery speed is high, and the user experience is good.

3. And completely reserving business logic when the large screen is displayed, and recovering the business logic to be in the latest state, wherein the interaction instantaneity is better than that of a suspended small window mode provided by a system and the effect of independently managing the streaming media player.

4. The suspended small window manager has low code intrusiveness, does not influence business layer logic, has strong applicability and is suitable for all pages based on the view controller.

5. The application range is wide, the independent player provided based on the system is only suitable for playing one stream media, and the interactive event is limited by the system. The independent suspension small window player is also only suitable for playing one streaming media, excessive system resources and a background interaction platform are consumed in the creating and destroying process, and the time deviation of the streaming media playing is easily caused when the state is recovered. The floating widget rear manager does not have the problems. The method can be used for displaying a plurality of streaming media on the same page, and can also be used for frequently switching the streaming media.

Fig. 5 is a block diagram illustrating a page display apparatus according to an exemplary embodiment. Referring to fig. 5, a page display apparatus 500 provided by an embodiment of the present disclosure may include: a widget display instruction acquisition module 501, a view controller acquisition module 502, and a widget display module 503.

The widget display instruction obtaining module 501 may be configured to obtain a widget display instruction for a target view page; the view controller acquiring module 502 may be configured to acquire and hold a view controller of a target view page in response to a widget display instruction, so that the view controller of the target view page is not destroyed; the widget display module 503 may be used to control the display of the target view page in the widget through the view controller.

In some embodiments, the target view page includes an interaction control to be displayed and an interaction control to be hidden; among them, the small window display module 503 may include: and the hidden interaction control determining sub-module and the hidden display sub-module.

The hidden interaction control determining submodule can be used for determining an interaction control to be displayed and an interaction control to be hidden in a target view page through a view controller; the hidden display sub-module can be used for displaying the interactive control to be displayed and hiding the interactive control to be hidden when the view controller controls the target view page to be displayed in the small window.

In some embodiments, the target view page is a view page in the target application, and the target system determines a page jump path in the target application through the target view stack; among them, the page display apparatus 500 may further include: the device comprises a large-screen display instruction acquisition module and a large-screen display module.

The large-screen display instruction acquisition module can be used for responding to a large-screen display instruction aiming at a target view page; the large-screen display module can be used for delivering the view controller to a target view stack of the target system so that the target system controls the target view page to be displayed in a large screen mode through the view controller.

In some embodiments, the large screen display module may include: and the control displays the sub-module in a full mode.

The control full-display sub-module can be used for displaying the interaction control to be displayed and the interaction control to be hidden when the target system controls the target view page to display in a large screen through the view controller.

In some embodiments, the target system includes a target view stack, the target view stack being a path stack for recording page jump records of the target application, the target application including a target view page, the target view stack including a view controller of the target view page, the target application including an intermediate controller; before acquiring the widget display instruction for the target view page, the page display apparatus 500 may further include: and a page large-screen display module.

The page large-screen display module can be used for the target system to control the target view page to display on a large screen through the view controller in the target view stack.

In some embodiments, the view controller acquisition module 502 may include: the intermediate controller obtains a view controller sub-module.

The intermediate controller obtains the view controller submodule may be configured to, in response to the widget display instruction, send, by the intermediate controller, view controller obtaining 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.

In some embodiments, the widget display instruction obtaining module 501 may include: the system comprises a leaving instruction acquisition sub-module, a white list determination sub-module and a dependency relationship determination sub-module.

The leaving instruction acquisition submodule can be used for acquiring a leaving instruction for leaving the target view page; the white list determining submodule can be used for acquiring a target white list, and the target white list is used for recording a small window display list; the affiliation determination sub-module may be configured to determine that the target view page is included in the target white list, and then determine that a small window display instruction for the target view page is obtained.

Since the functions of the apparatus 500 have been described in detail in the corresponding method embodiments, the disclosure is not repeated herein.

The modules and/or sub-modules described in the embodiments of the present application may be implemented by software or hardware. The modules and/or sub-modules described may also be provided in a processor. Wherein the names of the modules and/or sub-modules do not in some way constitute a limitation of the modules and/or sub-modules themselves.

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

Furthermore, the above-described figures are merely schematic illustrations of processes included in methods according to exemplary embodiments of the present disclosure, and are not intended to be limiting. It will be readily understood that the processes shown in the above figures are not intended to indicate or limit the chronological order of the processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, e.g., in multiple modules.

FIG. 6 illustrates a schematic structural diagram of an electronic device suitable for use in implementing embodiments of the present disclosure. It should be noted that the electronic device 600 shown in fig. 6 is only an example, and should not bring any limitation to the functions and the scope of the application of the embodiments of the present disclosure.

As shown in fig. 6, the electronic apparatus 600 includes a Central Processing Unit (CPU)601 that 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. In the RAM 603, various programs and data necessary for the operation of the electronic apparatus 600 are also stored. The CPU 601, ROM 602, and RAM 603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.

The following components are connected to the I/O interface 605: an input portion 606 including a keyboard, a mouse, and the like; an output portion 607 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 608 including a hard disk and the like; and a communication section 609 including a network interface card such as a LAN card, a modem, or the like. The communication section 609 performs communication processing via a network such as the internet. The driver 610 is also connected to the I/O interface 605 as needed. A removable medium 611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 610 as necessary, so that a computer program read out therefrom is mounted into the storage section 608 as necessary.

In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program containing program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 609, and/or installed from the removable medium 611. The above-described functions defined in the system of the present application are executed when the computer program is executed by the Central Processing Unit (CPU) 601.

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

As another aspect, the present application also provides a computer-readable storage medium, which may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable storage medium carries one or more programs which, when executed by a device, cause the device to perform functions including: acquiring a small window display instruction aiming at a target view page; responding to the small window display instruction, acquiring and holding the 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 the small window through the view controller.

According to an aspect of the application, a computer program product or computer program is provided, comprising computer instructions, the computer instructions being stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the method provided in the various alternative implementations of the embodiments described above.

Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution of the embodiment of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.), and includes several instructions for enabling a computing device (which may be a personal computer, a server, a mobile terminal, or a smart device, etc.) to execute the method according to the embodiment of the present disclosure, such as the steps shown in one or more of fig. 2, fig. 3, or fig. 4.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It is to be understood that the disclosure is not limited to the details of construction, the arrangements of the drawings, or the manner of implementation that have been set forth herein, but on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

Claims

1. A page display method, comprising:

acquiring a small window display instruction aiming at a target view page;

responding to the small window display instruction, and acquiring and holding the 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 through the view controller.

2. The method of claim 1, wherein the target view page comprises an interactive control to be displayed and an interactive control to be hidden; wherein controlling the target view page to be displayed in a small window by the view controller includes:

determining the interactive control to be displayed and the interactive control to be hidden in the target view page through the view controller;

and when the view controller controls the target view page to be displayed in the small window, displaying the interactive control to be displayed and hiding the interactive control to be hidden.

3. The method of claim 2, wherein the target view page is a view page in a target application, and a target system determines a page jump path in the target application through a target view stack; wherein the method further comprises:

responding to a large screen display instruction aiming at the target view page;

and delivering the view controller to the target view stack of the target system, so that the target system displays the interactive control to be displayed and the interactive control to be hidden when the target system controls the target view page to display on a large screen through the view controller.

4. The method of claim 2, wherein the target view page comprises a plurality of interactive controls; determining the interactive control to be displayed and the interactive control to be hidden in the target view page through the view controller comprises the following steps:

determining whether each interactive control in the target view page carries a target mark through the view controller;

the view controller determines an interactive control carrying a target mark as the interactive control to be displayed;

and the view controller determines the interactive control not carrying the target mark as the interactive control to be hidden.

5. The method of claim 1, wherein a target system comprises a target view stack, the target view stack is a path stack for recording page jump records of a target application, the target application comprises the target view page, and the target view stack comprises a view controller of the target view page; before acquiring a small window display instruction for a target view page, the method comprises the following steps:

and the target system controls the target view page to display on a large screen through the view controller in the target view stack.

6. The method of claim 5, wherein the target application comprises an intermediate controller; wherein, in response to the small window display instruction, the view controller for acquiring and holding the target view page comprises:

and responding to the small window display instruction, the intermediate controller sends view controller acquisition information to the target system aiming at the target view page, so that the intermediate controller acquires and holds the view controller of the target view page from the target system.

7. The method of claim 1, wherein obtaining a small window display instruction for a target view page comprises:

acquiring a leaving instruction for leaving the target view page;

acquiring a target white list, wherein the target white list is used for recording a small window display list;

and if the target white list comprises the target view page, determining that a small window display instruction for the target view page is obtained.

8. A page display apparatus, comprising:

the small window display instruction acquisition module is used for acquiring a small window display instruction aiming at a target view page;

the view controller acquisition module is used for responding to the small window display instruction and acquiring and holding the view controller of the target view page so that the view controller of the target view page is not destroyed;

and the small window display module is used for controlling the target view page to be displayed in the small window through the view controller.

9. An electronic device, comprising:

a memory; and

a processor coupled to the memory, the processor being configured to perform the page display method of any of claims 1-7 based on instructions stored in the memory.

10. A computer-readable storage medium on which a program is stored, which when executed by a processor implements the page display method according to any one of claims 1 to 7.