[go: up one dir, main page]

CN113391856B - Cross-task-stack page processing method, device, equipment and medium - Google Patents

Cross-task-stack page processing method, device, equipment and medium Download PDF

Info

Publication number
CN113391856B
CN113391856B CN202110710798.9A CN202110710798A CN113391856B CN 113391856 B CN113391856 B CN 113391856B CN 202110710798 A CN202110710798 A CN 202110710798A CN 113391856 B CN113391856 B CN 113391856B
Authority
CN
China
Prior art keywords
page
routing
task stack
host
task
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202110710798.9A
Other languages
Chinese (zh)
Other versions
CN113391856A (en
Inventor
谢少泽
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing ByteDance Network Technology Co Ltd
Original Assignee
Beijing ByteDance Network Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing ByteDance Network Technology Co Ltd filed Critical Beijing ByteDance Network Technology Co Ltd
Priority to CN202110710798.9A priority Critical patent/CN113391856B/en
Publication of CN113391856A publication Critical patent/CN113391856A/en
Application granted granted Critical
Publication of CN113391856B publication Critical patent/CN113391856B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/445Program loading or initiating
    • G06F9/44521Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/48Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806Task transfer initiation or dispatching
    • G06F9/4812Task transfer initiation or dispatching by interrupt, e.g. masked

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

The embodiment of the disclosure relates to a method, a device, equipment and a medium for processing a cross-task stack page, wherein the method comprises the following steps: when a user accesses the displayed first page of the sub-process, responding to a request message of a second page of the host process to open a routing page of the host process; storing the page information of the second page to the top of the host task stack and displaying the second page through the routing page; in response to the closing operation of the second page, removing the page information of the second page from the top end of the host task stack, and closing the routing page; and acquiring page information of the first page according to a preset target path and displaying the first page, so as to switch the subprocess task stack to the front of the host task stack. Therefore, when the sub-process calls the page of the host process across the task stack, the page can return to the task stack of the sub-process after being closed, the smooth sense of cross-process interaction is achieved, and the immersive experience of a user in the sub-process is improved.

Description

Cross-task-stack page processing method, device, equipment and medium
Technical Field
The present disclosure relates to the field of computer application technologies, and in particular, to a method, an apparatus, a device, and a medium for processing a page across task stacks.
Background
With the development of computer technology, more and more application programs meeting various requirements of users are provided, in order to improve user experience and avoid downloading and installing more application programs by users, a small program which can be used without downloading and installing is provided, and the small program is loaded in a host program to provide related functional services. For example, for the application a, the game applet can be loaded in the application a to provide the game service, and the corresponding game program does not need to be downloaded and installed.
In the related art, a sub-process corresponding to an applet and a host process corresponding to a host application belong to two different processes, and a cross-process is required when the two processes need to perform function interaction. That is, if the sub-process wants to execute the page function from the host process, all the currently opened pages in the host process need to be pulled up to the foreground.
However, in the above cross-process interaction, when the page function of the host process is completed, the page of the host process is returned instead of the page opened in the sub-process, and the user needs to manually pull the page of the child process again, which results in interrupting the use of the sub-process.
Disclosure of Invention
To solve the above technical problem or at least partially solve the above technical problem, the present disclosure provides a method.
The embodiment of the disclosure provides a cross-task-stack page processing method, which comprises the following steps: under the condition of accessing a first page of a displayed subprocess, acquiring a request message for accessing a second page of a host process, responding to the request message to open a routing page of the host process, and further switching a host task stack storing page information of the host process to the front of a subprocess task stack storing the page information of the subprocess; storing the page information of the second page to the top end of the host task stack, and displaying the second page through the routing page; in response to the closing operation of the second page, removing the page information of the second page from the top end of the host task stack, and closing the routing page; and responding to the closing operation of the routing page, acquiring page information of the first page according to a preset target path, displaying the first page, and switching the subprocess task stack to the front of the host task stack.
The embodiment of the present disclosure further provides a cross-task stack page processing apparatus, where the apparatus includes: the task stack opening module is used for acquiring a request message for accessing a second page of a host process under the condition of accessing a first page of a displayed subprocess, responding to the request message to open a routing page of the host process, and further switching a host task stack storing the page information of the host process to the front of a subprocess task stack storing the page information of the subprocess; the display module is used for storing the page information of the second page to the top end of the host task stack and displaying the second page through the routing page; the page closing module is used for responding to the closing operation of the second page, removing the page information of the second page from the top end of the host task stack, and closing the routing page; and the task stack opening module is further configured to, in response to the closing operation of the routing page, acquire page information of the first page according to a preset target path and display the first page, so as to switch the sub-process task stack to the front of the host task stack.
An embodiment of the present disclosure further provides an electronic device, which includes: a processor; a memory for storing the processor-executable instructions; the processor is used for reading the executable instruction from the memory and executing the instruction to realize the page processing method across the task stack provided by the embodiment of the disclosure.
The embodiment of the present disclosure also provides a computer-readable storage medium, where the storage medium stores a computer program, and the computer program is used to execute the cross-task-stack page processing method provided by the embodiment of the present disclosure.
Compared with the prior art, the technical scheme provided by the embodiment of the disclosure has the following advantages:
according to the page processing scheme of the cross-task stack provided by the embodiment of the disclosure, when a user accesses the first page of the displayed sub-process, obtaining a request message for accessing a second page of the host process, opening a routing page of the host process in response to the request message, further switching the host task stack storing the page information of the host process to the front of the sub-process task stack storing the page information of the sub-process, storing the page information of the second page to the top of the host task stack, and displays the second page through the routing page, removes the page information of the second page from the top of the host task stack in response to the closing operation of the second page, and closes the routing page, and further, in response to the closing operation of the routing page, and acquiring page information of the first page according to a preset target path and displaying the first page, so as to switch the subprocess task stack to the front of the host task stack. Therefore, when the sub-process calls the page of the host process across the task stack, the page can return to the task stack of the sub-process after being closed, the smooth sense of cross-process interaction is achieved, and the immersive experience of a user in the sub-process is improved.
Drawings
The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent by referring to the following detailed description when taken in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. It should be understood that the drawings are schematic and that elements and features are not necessarily drawn to scale.
Fig. 1 is a schematic flowchart of a cross-task-stack page processing method in the prior art according to an embodiment of the present disclosure;
fig. 2 is a schematic flowchart of a cross-task-stack page processing method according to an embodiment of the present disclosure;
fig. 3(a) is a schematic diagram of a page processing scenario across task stacks according to an embodiment of the present disclosure;
fig. 3(b) is a schematic diagram of another page processing scenario across task stacks according to an embodiment of the present disclosure;
fig. 4 is a schematic diagram of another page processing scenario across task stacks according to an embodiment of the present disclosure;
fig. 5 is a schematic flowchart of another cross task stack page processing method according to an embodiment of the present disclosure;
fig. 6(a) is a layout diagram of a second page provided in the embodiment of the present disclosure;
fig. 6(b) is a schematic layout diagram of another second page provided in the embodiment of the present disclosure;
fig. 6(c) is a schematic layout diagram of another second page provided by the embodiment of the present disclosure;
fig. 7 is a schematic flowchart of another cross task stack page processing method according to an embodiment of the present disclosure;
fig. 8 is a schematic flowchart of another cross task stack page processing method according to an embodiment of the present disclosure;
fig. 9(a) is a schematic diagram of another page processing scenario across task stacks according to an embodiment of the present disclosure;
fig. 9(b) is a schematic diagram of another page processing scenario across task stacks according to an embodiment of the present disclosure;
fig. 10 is a schematic structural diagram of a cross task stack page processing apparatus according to an embodiment of the present disclosure;
fig. 11 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.
Detailed Description
Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.
It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order, and/or performed in parallel. Moreover, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.
The term "include" and variations thereof as used herein are open-ended, i.e., "including but not limited to". The term "based on" is "based, at least in part, on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions for other terms will be given in the following description.
It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence relationship of the functions performed by the devices, modules or units.
It is noted that references to "a", "an", and "the" modifications in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that "one or more" may be used unless the context clearly dictates otherwise.
The names of messages or information exchanged between devices in the embodiments of the present disclosure are for illustrative purposes only, and are not intended to limit the scope of the messages or information.
Before describing the embodiments of the present disclosure, some technical terms involved in the embodiments of the present disclosure are first defined as follows:
a host process: for example, when the host application carried by the game applet is an application a, the current task execution process of the application a is the host process.
And (3) a sub-process: for example, when the host application carried by the game applet is an application a, the current task execution process of the game applet is a sub-process.
Cross-task interaction: the cross-task interaction in the embodiment of the disclosure refers to task interaction from a subprocess to a host process, and the task has a requirement of returning to the subprocess after the task is completed, for example, when the subprocess is a task process in a mini game, when account authentication in an application a is required, account authentication needs to be performed by crossing to the host process, and after the authentication is completed, the game still needs to be started in the subprocess of the mini game.
Task stack: all pages currently opened in each process are generally generated according to the page opening sequence arrangement, and the task stack contains all opened page information of the running process.
It should be noted that, in the embodiment of the present disclosure, although cross-task interaction between a sub-process and a host process is targeted, in some possible scenarios in the embodiment of the present disclosure, cross-task interaction between the host process and the sub-process should also fall within the scope of the present disclosure, or when the sub-process needs to perform task interaction with other sub-processes, if a task stack is also included in other sub-processes, it should also fall within the scope of the present disclosure. That is, whenever a cross-process interacts, it is within the scope of the embodiments of the present disclosure that pages are included in the task stack of the process that are being transiently crossed.
For example, since the opening of the sub-process is necessarily dependent on the operation of the host process, the task stack of the host process necessarily includes a corresponding page, and thus, as shown in fig. 1, when the task stack of the sub-process includes a plurality of pages, and the task stack of the host process also includes a plurality of pages, if the current sub-process needs to call a certain page a belonging to the host process, the task stack of the host process is pulled to the foreground due to the limitation of the operating system on the task stack, and the task stack of the sub-process is pushed to the background, when the user finishes operating on the page a, the user wants to return to the sub-process in a manner of a point return key or the like, but the result returns to the task stack of the host process, so that the user is interrupted in using the sub-process, and the user needs to manually enter the sub-process again.
In order to solve the above problem, embodiments of the present disclosure provide a cross-task stack page processing method, which is described below with reference to specific embodiments.
Fig. 2 is a flowchart of a cross-task-stack page processing method according to an embodiment of the present disclosure, where the method may be executed by a cross-task-stack page processing apparatus, where the apparatus may be implemented by software and/or hardware, and may be generally integrated in an electronic device. As shown in fig. 2, the method includes:
step 201, under the condition of accessing the displayed first page of the sub-process, acquiring a request message for accessing the second page of the host process, responding to the request message to open a routing page of the host process, and further switching the host task stack storing the page information of the host process to the front of the task stack storing the page information of the sub-process.
In order to enable the routing page to help return to the subprocess task stack, in one embodiment of the present disclosure, a closing operation of the routing page and a target path returning to the first page of the subprocess are set in an associated manner, so that when the closing operation of the routing page is identified, the target path of the first page is called to jump to the first page, and the purpose of returning to the subprocess is achieved.
In another embodiment of the present disclosure, the closing operation of the routing page may also be set in association with a call instruction for returning to the first page of the sub-process, so that, after the closing operation of the routing page is identified, the call execution of the first page jumps to the first page, and the purpose of returning to the sub-process is achieved.
Therefore, in an embodiment of the present disclosure, when a user accesses a first page of a displayed sub-process, after obtaining a request message for accessing a second page of a host process from the first page of the sub-process, the second page is not directly opened, but a routing page of the host process is opened to pull up a host task, so as to be subsequently helped to return to a task stack of the sub-process through the routing page, and according to the definition of the task stack, the task stack includes all page information of a currently running process.
Step 202, storing the page information of the second page to the top of the host task stack, and displaying the second page through the routing page.
In this embodiment, the second page is opened through the routing page and displayed to the accessing user, wherein, because the second page is opened most recently, the second page is currently located at the top of the host task stack and above the first page as shown in fig. 3 (a).
In an embodiment of the present disclosure, since the routing page is located below the second page, in order to avoid an influence of the routing page on the display of the second page, for example, when the second page is semi-transparent, if the routing page includes a complex pattern or a color fill with high saturation, the second page may be displayed as the routing page, the content display of the second page is influenced, and the like, the routing page may be set as a transparent page.
Step 203, responding to the closing operation of the second page, removing the page information of the second page from the top end of the host task stack, and closing the routing page.
The closing operation of the second page may be implemented by triggering a closing control on the second page, may also be implemented by touch tracks, voice, and the like, and may also be automatically triggered after the corresponding page function is executed.
In this embodiment, in order to avoid an increase in operation steps caused by adding a routing page, the closing operation of the second page is directly associated with the closing operation of the routing page located at the top of the host task stack, so that, in response to the closing operation of the second page, the routing page currently located at the top of the host task stack is removed, and a user does not need to separately perform the closing operation of the routing page, thereby reducing the influence of the routing page on the user operation.
And 204, responding to the closing operation of the routing page, acquiring page information of the first page according to a preset target path, displaying the first page, and switching the subprocess task stack to the front of the host task stack.
In this embodiment, in response to a closing operation on a routing page, directly returning page information of a first page according to a preset target path and displaying the first page, and further switching a sub-process task stack to the front of a host task stack, where the preset target path is obviously a call path of the first page.
Therefore, after the second page in the host process is called, the top end of the task stack is still the first page, the use of the sub-process by a user is not interrupted, and the smooth sense of cross-process interaction is realized.
For example, as shown in fig. 3(b) (for convenience of description, in this figure and subsequent figures related to embodiments, different pages are represented by different colors and filling of patterns, and pages filled by the same patterns belong to the same process, wherein for clarity of expression, although a routing page belongs to a host process, a routing page is represented by filling of another color), after a request message for accessing a second page b of the host process from a first page a of a sub-process is obtained, a routing page of the host process is opened, and a host task stack is pulled up.
And then, a second page is opened through the routing page and displayed to an access user, the second page is located at the top of the host task stack and located on the first page at the moment, when a closing control is arranged on the second page in an uplink mode, the routing page located at the top of the host task stack at the moment is removed in response to the triggering operation of the closing control by the user, page information of the first page is obtained according to a preset target path, and the first page is displayed, wherein the page information of the first page comprises a page framework, a page rendering element and the like, and the sub-process task stack corresponding to the first page is switched to the front of the host process.
In summary, in the page processing method across task stacks of the embodiment of the disclosure, when the user accesses the first page of the displayed sub-process, obtaining a request message for accessing a second page of the host process, opening a routing page of the host process in response to the request message, further switching the host task stack storing the page information of the host process to the front of the sub-process task stack storing the page information of the sub-process, storing the page information of the second page to the top of the host task stack, and displays the second page through the routing page, removes the page information of the second page from the top of the host task stack in response to the closing operation of the second page, and closes the routing page, and further, in response to the closing operation of the routing page, and acquiring page information of the first page according to a preset target path and displaying the first page, so as to switch the subprocess task stack to the front of the host task stack. Therefore, when the sub-process calls the page of the host process across the task stack, the page can return to the task stack of the sub-process after being closed, the smooth sense of cross-process interaction is achieved, and the immersive experience of a user in the sub-process is improved.
Based on the above embodiment, the display manner of the second page also has an influence on the immersive experience of the user using the sub-process, for example, as shown in fig. 4, when the second page is displayed on the lower half screen in the half-screen display manner (for example, displayed transparently on the upper half screen), since the task stack of the host process is pulled up by the current foreground, the current user can clearly see the page content of the third page located below the second page in the host process, so that the user can clearly perceive the cross-process.
Therefore, in order to solve the above technical problem, in the embodiments of the present disclosure, the routing page may be further utilized to process display content in a transparent area in the second page, where the display content is related to a sub-process, and thus, a user cannot perceive a cross-process in the foreground.
In one embodiment of the present disclosure, as shown in fig. 5, before opening the second page through the routing page to be displayed to the accessing user, the method further includes:
step 501, detecting whether a transparent area exists in the second page.
In this embodiment, whether the second page has a transparent area may be detected through a page background attribute value in the HTML of the second page, and of course, if the second page is displayed according to a non-full screen size, it may also be understood that a non-displayed half screen is a transparent area, and such a display manner may be found by comparing the size of the second page with the size of the full page.
Wherein, in some possible embodiments, the second page presence transparent area includes: the upper half screen of the second page shown in fig. 6(a) is a content area, and the lower half screen is a transparent area, or the lower half screen of the second page shown in fig. 6(b) is a content area, and the upper half screen is a transparent area, or the plurality of first areas in the second page shown in fig. 6(c) are content areas, and the plurality of second areas are transparent areas.
Of course, what is shown in the drawings in this embodiment is only one possible way, and the existence positions of other transparent areas also belong to the page display way of the second page in the embodiments of the present disclosure, which is not listed here.
Step 502, if the second page has a transparent region, a target cover associated with the sub-process is obtained.
In this embodiment, if the transparent area exists in the second page, in order to avoid the transparent area from displaying the content related to the host process, an object cover associated with the sub-process is obtained, and the object cover is associated with the sub-process, so that the user does not feel a cross-process feeling even if the object cover is displayed in the transparent area.
It should be noted that, in different application scenarios, the manner of acquiring the object cover associated with the sub-process is different, and the following example is given:
example one:
in this example, as shown in FIG. 7, obtaining an object cover associated with a sub-process includes:
step 701, storing a screenshot of a first page, and associating a file path of the screenshot with a routing page.
Step 702, acquiring a screenshot of a first page as a target cover according to the file path.
In this embodiment, the screenshot of the first page is obtained and stored, and the file path storing the screenshot is associated with the routing page, so that the screenshot of the first page is obtained as the target cover page according to the file path. Therefore, the user can visually see the content of the first page in the foreground, and the immersive experience is improved.
Example two:
in this example, as shown in FIG. 8, obtaining an object cover associated with a sub-process includes:
step 801, acquiring the application name of the sub-process.
Step 802, a preset database is queried to obtain an application cover corresponding to the application name as a target cover.
In this embodiment, the application name of the sub-process is obtained, and the preset database is queried to obtain an application cover corresponding to the application name as a target cover, where the application cover may be a publicity cover of the application of the sub-process.
Step 503, setting the background of the routing page according to the target cover page.
In the embodiment, the background of the routing page is set according to the target cover, so that the content displayed through the transparent area of the second page is not the page content of other pages of the host process, but the content associated with the sub-process, and the immersive experience of the user is improved.
In some possible embodiments, all areas of the routing page may be set to all content in the target cover page. For example, as shown in fig. 9(a), when the first page is the "game entry interface", the screenshot of the "game entry interface" is obtained and used as the target cover, so that the routing page is controlled to display the whole screenshot of the "game entry interface", and when the second page is the half-screen display mode and the second page is the user identity authentication page, the half-screen content of the "game entry interface" can be seen at the front end, so as to provide the user with no immersion across processes.
In other possible embodiments, the transparent area of the second page may be matched with the routing page, a target area successfully matched with the transparent area in the routing page is obtained, and then the target area in the routing page is set as part of cover content matched with the target cover. That is, as shown in fig. 9(b), if the first page is the "game entry interface", the screenshot of the "game entry interface" is obtained and is used as the target cover page, so that the target area in the routing page, which is successfully matched with the transparent area, is controlled to display the content of the entire "game entry interface".
In summary, in the page processing method across task stacks in the embodiments of the present disclosure, if the second page has a transparent area, a target cover associated with the sub-process is obtained, and a background of the routing page is set according to the target cover. Thus, the associated content of the sub-process is displayed in the front-end, giving the user a sense of immersion that is not across processes.
In order to implement the above embodiments, the present disclosure further provides a page processing device across task stacks. Fig. 10 is a schematic structural diagram of a cross task stack page processing apparatus, which may be implemented by software and/or hardware, and may be generally integrated in an electronic device. As shown in fig. 10, the apparatus includes: a task stack opening module 1010, a display module 1020, a page closing module 1030, wherein,
a task stack opening module 1010, configured to, when a first page of a displayed sub-process is accessed, obtain a request message for accessing a second page of a host process, open a routing page of the host process in response to the request message, and further switch a host task stack storing page information of the host process to a front side of the sub-process task stack storing the page information of the sub-process;
a display module 1020, configured to store the page information of the second page to the top of the host task stack, and display the second page through the routing page;
a page closing module 1030, configured to remove the page information of the second page from the top of the host task stack in response to a closing operation on the second page, and close the routing page;
in this embodiment, the task stack opening module 1010 is further configured to, in response to a closing operation on the routing page, obtain page information of the first page according to a preset target path and display the first page, so as to switch the subprocess task stack to the front of the host task stack.
The cross-task-stack page processing device provided by the embodiment of the disclosure can execute the cross-task-stack page processing method provided by any embodiment of the disclosure, and has corresponding functional modules and beneficial effects of the execution method.
In order to implement the foregoing embodiments, the present disclosure further provides a computer program product, which includes a computer program/instruction, and when the computer program/instruction is executed by a processor, the computer program/instruction implements the cross-task-stack page processing method in the foregoing embodiments
Fig. 11 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.
Referring now specifically to FIG. 11, a schematic diagram of a structure suitable for implementing an electronic device 1100 in an embodiment of the present disclosure is shown. The electronic device 1100 in the embodiments of the present disclosure may include, but is not limited to, a mobile terminal such as a mobile phone, a notebook computer, a digital broadcast receiver, a PDA (personal digital assistant), a PAD (tablet computer), a PMP (portable multimedia player), a vehicle-mounted terminal (e.g., a car navigation terminal), etc., and a stationary terminal such as a digital TV, a desktop computer, etc. The electronic device shown in fig. 11 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.
As shown in fig. 11, the electronic device 1100 may include a processing means (e.g., a central processing unit, a graphics processor, etc.) 1101 that may perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)1102 or a program loaded from a storage means 1108 into a Random Access Memory (RAM) 1103. In the RAM 1103, various programs and data necessary for the operation of the electronic device 1100 are also stored. The processing device 1101, the ROM 1102, and the RAM 1103 are connected to each other by a bus 1104. An input/output (I/O) interface 1105 is also connected to bus 1104.
Generally, the following devices may be connected to the I/O interface 1105: input devices 1106 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 1107 including, for example, Liquid Crystal Displays (LCDs), speakers, vibrators, and the like; storage devices 1108, including, for example, magnetic tape, hard disk, etc.; and a communication device 1109. The communication means 1109 may allow the electronic device 1100 to communicate wirelessly or wiredly with other devices to exchange data. While fig. 11 illustrates an electronic device 1100 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided.
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 carried on a non-transitory computer readable medium, the computer program containing program code for performing the method illustrated by the flow chart. In such embodiments, the computer program may be downloaded and installed from a network via the communication device 1109, or installed from the storage device 1108, or installed from the ROM 1102. The computer program, when executed by the processing apparatus 1101, performs the above-described functions defined in the cross task stack page processing method of the embodiment of the present disclosure.
It should be noted that the computer readable medium in the present disclosure can 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 disclosure, 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 contrast, in the present disclosure, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, either 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 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 medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.
In some embodiments, the clients, servers may communicate using any currently known or future developed network Protocol, such as HTTP (HyperText Transfer Protocol), and may interconnect with any form or medium of digital data communication (e.g., a communications network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the Internet (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed network.
The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device.
The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: the method comprises the steps of obtaining a request message for accessing a second page of a host process under the condition of accessing a first page of a displayed subprocess, responding to the request message to open a routing page of the host process, further switching a host task stack for storing page information of the host process to the front of the subprocess task stack for storing the page information of the subprocess, storing the page information of a second page to the top end of the host task stack, displaying the second page through the routing page, responding to closing operation of the second page, removing the top end of the host task stack from the page information of the second page, closing the routing page, further responding to closing operation of the routing page, obtaining the page information of the first page according to a preset target path, displaying the first page, and further switching the subprocess task stack to the front of the host task stack. Therefore, when the sub-process calls the page of the host process across the task stack, the page can return to the task stack of the sub-process after being closed, the smooth sense of cross-process interaction is achieved, and the immersive experience of a user in the sub-process is improved.
Computer program code for carrying out operations for the present disclosure may be written in any combination of one or more programming languages, including but not limited to an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
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 disclosure. 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 and/or flowchart illustration, and combinations of blocks in the block diagrams and/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.
The units described in the embodiments of the present disclosure may be implemented by software or hardware. Where the name of an element does not in some cases constitute a limitation on the element itself.
The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), systems on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on 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.
According to one or more embodiments of the present disclosure, the present disclosure provides a page processing method across task stacks, including:
under the condition of accessing a first page of a displayed subprocess, acquiring a request message for accessing a second page of a host process, responding to the request message to open a routing page of the host process, and further switching a host task stack storing page information of the host process to the front of a subprocess task stack storing the page information of the subprocess;
storing the page information of the second page to the top end of the host task stack, and displaying the second page through the routing page;
in response to the closing operation of the second page, removing the page information of the second page from the top end of the host task stack, and closing the routing page;
responding to the closing operation of the routing page, acquiring page information of the first page according to a preset target path, displaying the first page, and switching the subprocess task stack to the front of the host task stack
According to one or more embodiments of the present disclosure, in the page processing method across task stacks provided by the present disclosure, the routing page is set as a transparent page.
According to one or more embodiments of the present disclosure, in the method for processing a page across task stacks provided by the present disclosure, before displaying the second page through the routing page, the method further includes:
detecting whether a transparent area exists in the second page or not;
if the transparent area exists in the second page, acquiring a target cover related to the sub-process;
and setting the background of the routing page according to the target cover.
According to one or more embodiments of the present disclosure, in the method for processing a page across task stacks provided by the present disclosure, the presence of the transparent area on the second page includes:
the upper half screen of the second page is a content area, the lower half screen is a transparent area, or,
the lower half screen of the second page is a content area, the upper half screen is a transparent area, or,
the plurality of first areas in the second page are content areas, and the plurality of second areas are transparent areas.
According to one or more embodiments of the present disclosure, in the method for processing pages across task stacks provided by the present disclosure, the obtaining a target cover page associated with the sub-process includes:
storing the screenshot of the first page, and associating the file path of the screenshot with the routing page;
and acquiring the screenshot of the first page as the target cover according to the file path.
According to one or more embodiments of the present disclosure, in the method for processing pages across task stacks provided by the present disclosure, the obtaining a target cover page associated with the sub-process includes:
acquiring the application name of the sub-process;
and querying a preset database to obtain an application cover corresponding to the application name as the target cover.
According to one or more embodiments of the present disclosure, in a method for processing a page across a task stack provided by the present disclosure, the setting a background of the routing page according to the target cover includes:
setting all areas of the routing page as all content in the object cover.
According to one or more embodiments of the present disclosure, in a method for processing a page across a task stack provided by the present disclosure, the setting a background of the routing page according to the target cover includes:
matching the transparent area of the second page with the routing page to obtain a target area successfully matched with the transparent area in the routing page;
setting the target area in the routing page as a portion of cover content that matches the target cover.
According to one or more embodiments of the present disclosure, in the cross-task-stack page processing method provided by the present disclosure, before the obtaining page information of the first page according to a preset target path and displaying the first page, the method further includes:
and performing association setting on the closing operation of the routing page and the preset target path.
According to one or more embodiments of the present disclosure, the present disclosure provides a page processing apparatus across task stacks, including:
the task stack opening module is used for acquiring a request message for accessing a second page of a host process under the condition of accessing a first page of a displayed subprocess, responding to the request message to open a routing page of the host process, and further switching a host task stack storing the page information of the host process to the front of a subprocess task stack storing the page information of the subprocess;
the display module is used for storing the page information of the second page to the top end of the host task stack and displaying the second page through the routing page;
the page closing module is used for responding to the closing operation of the second page, removing the page information of the second page from the top end of the host task stack, and closing the routing page;
and the task stack opening module is further configured to, in response to the closing operation of the routing page, acquire page information of the first page according to a preset target path and display the first page, so as to switch the sub-process task stack to the front of the host task stack.
According to one or more embodiments of the present disclosure, in the page processing apparatus across task stacks provided by the present disclosure, the routing page is set as a transparent page.
According to one or more embodiments of the present disclosure, the page processing apparatus across task stacks further includes:
the detection module is used for detecting whether the second page has a transparent area;
an obtaining module, configured to obtain a target cover associated with the sub-process when the transparent area exists in the second page;
and the setting module is used for setting the background of the routing page according to the target cover.
According to one or more embodiments of the present disclosure, in a page processing apparatus across a task stack provided by the present disclosure, the presence of the transparent area in the second page includes:
the upper half screen of the second page is a content area, the lower half screen is a transparent area, or,
the lower half screen of the second page is a content area, the upper half screen is a transparent area, or,
the plurality of first areas in the second page are content areas, and the plurality of second areas are transparent areas.
According to one or more embodiments of the present disclosure, in the page processing apparatus across task stacks provided by the present disclosure, the obtaining module is specifically configured to:
storing the screenshot of the first page, and associating the file path of the screenshot with the routing page;
and acquiring the screenshot of the first page as the target cover according to the file path.
According to one or more embodiments of the present disclosure, in the page processing apparatus across task stacks provided by the present disclosure, the obtaining module is specifically configured to:
acquiring the application name of the sub-process;
and querying a preset database to obtain an application cover corresponding to the application name as the target cover.
According to one or more embodiments of the present disclosure, in the page processing apparatus across task stacks provided by the present disclosure, the setting module is specifically configured to:
setting all areas of the routing page as all content in the object cover.
According to one or more embodiments of the present disclosure, in the page processing apparatus across task stacks provided by the present disclosure, the setting module is specifically configured to:
matching the transparent area of the second page with the routing page to obtain a target area successfully matched with the transparent area in the routing page;
setting the target area in the routing page as a portion of cover content that matches the target cover.
According to one or more embodiments of the present disclosure, the page processing apparatus across task stacks further includes:
and the association module is used for performing association setting on the closing operation of the routing page and the return of the preset target path.
In accordance with one or more embodiments of the present disclosure, there is provided an electronic device including:
a processor;
a memory for storing the processor-executable instructions;
the processor is used for reading the executable instructions from the memory and executing the instructions to realize the page processing method across the task stack provided by the disclosure.
According to one or more embodiments of the present disclosure, there is provided a computer-readable storage medium storing a computer program for executing any one of the page processing methods across task stacks provided by the present disclosure.
The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the disclosure herein is not limited to the particular combination of features described above, but also encompasses other embodiments in which any combination of the features described above or their equivalents does not depart from the spirit of the disclosure. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.
Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims (12)

1. A cross task stack page processing method is characterized by comprising the following steps:
under the condition of accessing a first page of a displayed subprocess, acquiring a request message for accessing a second page of a host process, responding to the request message to open a routing page of the host process, and further switching a host task stack for storing page information of the host process to the front of a subprocess task stack for storing the page information of the subprocess;
storing the page information of the second page to the top end of the host task stack, and displaying the second page through the routing page;
responding to the closing operation of the second page, moving the page information of the second page out of the top end of the host task stack, and closing the routing page;
and responding to the closing operation of the routing page, acquiring page information of the first page according to a preset target path, displaying the first page, and switching the subprocess task stack to the front of the host task stack.
2. The method of claim 1,
the routing page is set as a transparent page.
3. The method of claim 1, prior to said displaying said second page via said routing page, further comprising:
detecting whether a transparent area exists in the second page or not;
if the transparent area exists in the second page, acquiring a target cover related to the sub-process;
and setting the background of the routing page according to the target cover.
4. The method of claim 3, wherein the second page having the transparent region comprises:
the upper half screen of the second page is a content area, the lower half screen is a transparent area, or,
the lower half screen of the second page is a content area, the upper half screen is a transparent area, or,
the plurality of first areas in the second page are content areas, and the plurality of second areas are transparent areas.
5. The method of claim 3, wherein the obtaining an object cover associated with the sub-process comprises:
storing the screenshot of the first page, and associating the file path of the screenshot with the routing page;
and acquiring the screenshot of the first page as the target cover according to the file path.
6. The method of claim 3, wherein the obtaining an object cover associated with the sub-process comprises:
acquiring the application name of the sub-process;
and querying a preset database to obtain an application cover corresponding to the application name as the target cover.
7. The method of claim 3, wherein setting the context of the routing page based on the object cover comprises:
setting all areas of the routing page as all content in the object cover.
8. The method of claim 3, wherein setting the context of the routing page based on the object cover comprises:
matching the transparent area of the second page with the routing page to obtain a target area successfully matched with the transparent area in the routing page;
setting the target area in the routing page as a portion of cover content that matches the target cover.
9. The method according to any one of claims 1 to 8, wherein before the obtaining the page information of the first page according to the preset target path and displaying the first page, the method further comprises:
and performing association setting on the closing operation of the routing page and the preset target path.
10. A page processing apparatus across task stacks, comprising:
the task stack opening module is used for acquiring a request message for accessing a second page of the host process under the condition of accessing the first page of the displayed subprocess, responding to the request message to open a routing page of the host process, and further switching the host task stack storing the page information of the host process to the front of the subprocess task stack storing the page information of the subprocess;
the display module is used for storing the page information of the second page to the top end of the host task stack and displaying the second page through the routing page;
the page closing module is used for moving the page information of the second page out of the top end of the host task stack and closing the routing page in response to the closing operation of the second page;
and the task stack opening module is further configured to, in response to the closing operation of the routing page, acquire page information of the first page according to a preset target path and display the first page, so as to switch the sub-process task stack to the front of the host task stack.
11. An electronic device, characterized in that the electronic device comprises:
a processor;
a memory for storing the processor-executable instructions;
the processor is configured to read the executable instructions from the memory and execute the instructions to implement the method for processing a page across a task stack according to any one of claims 1 to 9.
12. A computer-readable storage medium, characterized in that the storage medium stores a computer program for executing the method of page processing across task stacks of any of the preceding claims 1-9.
CN202110710798.9A 2021-06-25 2021-06-25 Cross-task-stack page processing method, device, equipment and medium Active CN113391856B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110710798.9A CN113391856B (en) 2021-06-25 2021-06-25 Cross-task-stack page processing method, device, equipment and medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110710798.9A CN113391856B (en) 2021-06-25 2021-06-25 Cross-task-stack page processing method, device, equipment and medium

Publications (2)

Publication Number Publication Date
CN113391856A CN113391856A (en) 2021-09-14
CN113391856B true CN113391856B (en) 2022-04-15

Family

ID=77623872

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110710798.9A Active CN113391856B (en) 2021-06-25 2021-06-25 Cross-task-stack page processing method, device, equipment and medium

Country Status (1)

Country Link
CN (1) CN113391856B (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113986063B (en) * 2021-11-08 2024-09-10 北京字跳网络技术有限公司 Display control method, device, electronic device and storage medium
CN114691273A (en) * 2022-03-30 2022-07-01 北京字跳网络技术有限公司 User interface return method, apparatus, electronic device and storage medium
CN115440214A (en) * 2022-07-26 2022-12-06 北京罗克维尔斯科技有限公司 Voice control method, device, electronic device, vehicle and storage medium

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108089887A (en) * 2016-11-18 2018-05-29 阿里巴巴集团控股有限公司 A kind of startup control method and device of new added pages
WO2020073980A1 (en) * 2018-10-12 2020-04-16 上海掌门科技有限公司 Method and device for processing guest application, and computer-readable storage medium
CN111176752A (en) * 2019-12-20 2020-05-19 汪佐怀 Method and device for embedding window applet in browser page

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100577366B1 (en) * 2004-09-25 2006-05-10 삼성전자주식회사 Method and device for running heterogeneous Java methods
US8607013B2 (en) * 2007-10-30 2013-12-10 Vmware, Inc. Providing VMM access to guest virtual memory
WO2016003646A1 (en) * 2014-06-30 2016-01-07 Unisys Corporation Enterprise management for secure network communications over ipsec
US20180052759A1 (en) * 2016-08-19 2018-02-22 Ca, Inc. Performance metric contextualization in a distributed computing environment
US11385785B2 (en) * 2019-05-01 2022-07-12 Google Llc Interface for multiple simultaneous interactive views
CN112130937B (en) * 2019-06-24 2025-05-27 北京京东尚科信息技术有限公司 Page display method and device, storage medium, and electronic device
CN111475246A (en) * 2020-04-10 2020-07-31 腾讯科技(深圳)有限公司 Applet page display method, device, terminal and storage medium
CN112861044B (en) * 2021-02-09 2022-10-28 苏州达家迎信息技术有限公司 Page display control method and device, computer equipment and storage medium

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108089887A (en) * 2016-11-18 2018-05-29 阿里巴巴集团控股有限公司 A kind of startup control method and device of new added pages
WO2020073980A1 (en) * 2018-10-12 2020-04-16 上海掌门科技有限公司 Method and device for processing guest application, and computer-readable storage medium
CN111176752A (en) * 2019-12-20 2020-05-19 汪佐怀 Method and device for embedding window applet in browser page

Also Published As

Publication number Publication date
CN113391856A (en) 2021-09-14

Similar Documents

Publication Publication Date Title
US11483264B2 (en) Information interaction method, apparatus, device, storage medium and program product
CN113391856B (en) Cross-task-stack page processing method, device, equipment and medium
US10949490B2 (en) Method and apparatus for displaying webpage content
US20220365985A1 (en) Page jump method and apparatus, electronic device and computer-readable storage medium
CN111790148B (en) Information interaction method and device in game scene and computer readable medium
JP2020504865A (en) Application data processing method, apparatus, and storage medium
EP3835954A1 (en) Method and device for displaying interface, and storage medium
US12067136B2 (en) Display method, display device, and electronic device
US20240411432A1 (en) Video display method and apparatus, and electronic device and storage medium
CN110674481B (en) Account registration method, device, equipment and storage medium of application program
CN110958481A (en) Video page display method and device, electronic equipment and computer readable medium
CN111459364B (en) Icon updating method and device and electronic equipment
CN110865734A (en) Target object display method and device, electronic equipment and computer readable medium
EP3416070A1 (en) Page display method and device and storage medium
US20240040069A1 (en) Image special effect configuration method, image recognition method, apparatus and electronic device
CN112328094A (en) Information input method, cloud input method system and client
CN112256172B (en) Application display method, device, terminal and storage medium
US11809690B2 (en) Human-computer interaction method and apparatus, and electronic device
CN118034540A (en) Content display method, device, equipment, computer-readable storage medium and product
CN110908629A (en) Electronic equipment operation method and device, electronic equipment and storage medium
US20250078330A1 (en) Method for processing comments and electronic device
WO2025045104A1 (en) Interface jump method and apparatus, electronic device, medium and product
CN109683726B (en) Character input method, character input device, electronic equipment and storage medium
CN109976857B (en) Display control method and device of terminal interface, storage medium and electronic equipment
EP4418089A1 (en) Data processing method and apparatus, electronic device, and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant