CN115439117A - Page management method, medium and equipment - Google Patents
Page management method, medium and equipment Download PDFInfo
- Publication number
- CN115439117A CN115439117A CN202211049982.4A CN202211049982A CN115439117A CN 115439117 A CN115439117 A CN 115439117A CN 202211049982 A CN202211049982 A CN 202211049982A CN 115439117 A CN115439117 A CN 115439117A
- Authority
- CN
- China
- Prior art keywords
- page
- stack
- management component
- attribute
- attribute information
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/327—Short range or proximity payments by means of M-devices
- G06Q20/3274—Short range or proximity payments by means of M-devices using a pictured code, e.g. barcode or QR-code, being displayed on the M-device
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/954—Navigation, e.g. using categorised browsing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
- G06F16/9558—Details of hyperlinks; Management of linked annotations
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements 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/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/327—Short range or proximity payments by means of M-devices
- G06Q20/3276—Short range or proximity payments by means of M-devices using a pictured code, e.g. barcode or QR-code, being read by the M-device
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Business, Economics & Management (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Data Mining & Analysis (AREA)
- Accounting & Taxation (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Human Computer Interaction (AREA)
- Radar, Positioning & Navigation (AREA)
- Remote Sensing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The present application relates to the field of software technologies, and in particular, to a page management method, medium, and device. The method comprises the following steps: the page management component operates after the application is started and monitors the page stack of the application; the page management component determines a change page indicated by the change information based on the monitored change information of the page stack; the page management component executes the same stack in and out operation as the page stack in the page attribute stack of the page management component on the page attribute information corresponding to the changed page; and the page attribute information in the page attribute stack is used for the application to perform page jump across the system. In the above manner, a page attribute stack is established for storing page attribute information. When the page stack changes, the page attribute of the changed page indicated by the change information is set, so that the page and the page attribute can be synchronized, and the page after each change of the page can be ensured to realize normal operation on the page.
Description
Technical Field
The present application relates to the field of software technologies, and in particular, to a page management method, medium, and device.
Background
In recent years, with the increase of payment modes, the traditional bank card payment mode is greatly impacted, the payment mode selected by a user is convenient to adapt to various scenes, the payment is more convenient, and the Unionpay performs unified management on the payment modes of financial institutions such as banks.
One way to implement this is to access the banking institution to the cloud Software Development Kit (SDK), where a payment and other application functions are accomplished by a jump between the bank page and the cloud SDK page. With more and more banking institutions accessing the cloud network SDK, interaction between the cloud network SDK and system pages of each banking institution is gradually complicated. In the prior art, the return and jump of a page are realized by recording the attribute information of the previous page in the page dimension. However, because the bank page and the cloud network SDK page belong to different systems, when the page is skipped, the cloud network SDK page cannot know whether the bank page records the attribute information of the cloud network SDK page, and if the bank page does not record the attribute information, the page is forcibly skipped or returned, so that the attribute conflict occurs, and the page cannot be normally operated.
Based on this, there is a need for a page management method, medium, and apparatus for ensuring normal operation of a page.
Disclosure of Invention
The embodiment of the application provides a page management method, medium and device, which are used for ensuring normal operation of a page.
In a first aspect, an embodiment of the present application provides a page management method, where the method includes: the method comprises the steps that a page management component runs after an application is started and monitors a page stack of the application; the page stack is used for sequentially storing the pages in the application operation; the page management component determines a changed page indicated by the change information based on the monitored change information of the page stack; the page management component executes stack in and out operation which is the same as the page stack in the page attribute stack of the page management component on the page attribute information corresponding to the changed page; and the page attribute information in the page attribute stack is used for the application to perform cross-system page jump.
In the above manner, a page attribute stack is established for storing page attribute information. When the page stack is changed, the page attribute of the changed page indicated by the change information is set, so that the page and the page attribute can be synchronized. Moreover, any change information in the page stack can be monitored, so that the page attribute can be changed when the page in the page stack is continuously changed for many times, and the normal operation on the page can be realized by the page after each change of the page.
In a possible implementation manner, the determining, by the page management component, a changed page indicated by the change information based on the monitored change information of the page stack includes: the page management component monitors that the change information of the page stack is a newly added first page, and then determines that a second page displayed by the application is a change page indicated by the change information; the page management component executes the same stack in and out operation as the page stack in the page attribute stack of the page management component for the page attribute information corresponding to the changed page, and the operation comprises the following steps: the page management component acquires page attribute information of the second page from the application; and executing stack pushing operation on the page attribute information of the second page in the page attribute stack of the page management component.
Through the method, when the pages in the page stack are added, the corresponding attribute information needs to be added into the attribute stack. On one hand, when the pages are jumped among the pages, the attribute information of the previous page is stored in time, and the phenomenon that the original page attribute is lost and cannot return to the original page after the page attribute disappears and is changed is avoided. On the other hand, in the page jump process, the attribute information of the newly added page is also stored into the page attribute stack, so that page jump and return are normal when a page invisible to a user is added between two pages, and the application range of the page management component is more compatible.
In a possible implementation manner, the determining, by the page management component, a changed page indicated by the change information based on the monitored change information of the page stack includes: the page management component monitors that the change information of the page stack is the third page, and then determines that the change page indicated by the change information is the third page; the page management component executes the same stack in and out operation as the page stack in the page attribute stack of the page management component for the page attribute information corresponding to the changed page, and the operation comprises the following steps: and the page management component executes a stack pulling operation on the page attribute information of the third page in a page attribute stack of the page management component.
By the method, the change of the page attribute stack can be adjusted in time according to the change of the page stack, and when the page is deleted, the attribute information in the page attribute stack is deleted in time. On one hand, the storage space of the page attribute stack can be saved, and on the other hand, the unused attribute information is deleted, so that the target page attribute information can be obtained more conveniently.
In one possible implementation manner, the determining, by the page management component, a changed page indicated by the change information based on the monitored change information of the page stack includes: the page management component monitors that the change information of the page stack is that a fourth page is replaced by a fifth page, and then determines that the change pages indicated by the change information are the fourth page and the fifth page; the page management component executes the same stack in and out operation as the page stack in the page attribute stack of the page management component for the page attribute information corresponding to the changed page, and the operation comprises the following steps: and after the page management component performs a pop operation on the page attribute information of the fourth page in a page attribute stack of the page management component, the page management component performs a push operation on the page attribute information of the fifth page.
Through the mode, after the page is replaced by other pages, the attribute information is replaced in the page attribute stack corresponding to the page, so that the synchronization between the page attribute information and the page is ensured, and the setting of the page attribute is matched with the current page.
In a possible implementation, the method further includes: the page management component monitors the cross-system page jump operation of the application; the cross-system page jump operation is used for indicating jumping to a sixth page; the page management component acquires page attribute information of the sixth page through the page attribute stack; and the page management component pushes the page attribute information of the sixth page to the application. The page management component acquires the page attribute information of the sixth page through the page attribute stack, and the page attribute information includes: and the page management component executes a pop operation on the page attribute information positioned behind the page attribute information of the sixth page in the page attribute stack until the page attribute information of the sixth page is obtained.
Through the method, in the storage mode of stacking, other unnecessary page attribute information is pushed out of the stack, and meanwhile, the required page attribute information is acquired. On one hand, the space of the page attribute stack is saved, and on the other hand, the required page attribute information can be acquired more conveniently.
In a possible implementation, the method further includes: after the page attribute information of the sixth page is obtained, the method further includes: and sequentially executing stack-entering operation on the page attribute information positioned after the page attribute information of the sixth page in the page attribute stack.
By the method, the information stored in the storage structure of the stack is consistent with the actual page jump process, and the stack-out and stack-in operations are more convenient and faster to execute in the page jump.
In a second aspect, an embodiment of the present application provides another page management method, where the method includes an application acquiring a cross-system page jump operation triggered by a user; the cross-system page jump operation is used for indicating jump to a sixth page; the application acquires the sixth page from the page stack of the application and acquires page attribute information of the sixth page based on the page attribute stack of the page management component; and the application displays the sixth page according to the sixth page and the page attribute information of the sixth page.
In a third aspect, an embodiment of the present application provides a page management component, where the page management component is configured to run after an application is started and monitor a page stack of the application; the page stack is used for sequentially storing the pages in the application operation; the page management component is further configured to determine a changed page indicated by the change information based on the monitored change information of the page stack; the page management component is also used for executing stack entering and exiting operations which are the same as the page stack in the page attribute stack of the page management component on the page attribute information corresponding to the changed page; and the page attribute information in the page attribute stack is used for the application to perform cross-system page jump.
In a possible implementation manner, the page management component is specifically configured to determine that a second page displayed by the application is a changed page indicated by the change information if it is monitored that the change information of the page stack is a newly added first page; the page management component is specifically further configured to acquire page attribute information of the second page from the application; and executing stack pushing operation on the page attribute information of the second page in a page attribute stack of the page management component.
In a possible implementation manner, the page management component is specifically configured to determine that a changed page indicated by the change information is the third page if the change information of the page stack is monitored to be deletion of the third page; the page management component is further specifically configured to, in a page attribute stack of the page management component, perform a pop operation on the page attribute information of the third page.
In a possible implementation manner, the page management component is specifically configured to monitor that change information of the page stack is that a fourth page is replaced by a fifth page, and determine that a change page indicated by the change information is the fourth page and the fifth page; the page management component is further specifically configured to, in a page attribute stack of the page management component, perform a pop operation on the page attribute information of the fourth page, and then perform a pop operation on the page attribute information of the fifth page.
In a possible implementation manner, the page management component is further configured to monitor a cross-system page jump operation of the application; the cross-system page jump operation is used for indicating jumping to a sixth page; the page management component acquires page attribute information of the sixth page through the page attribute stack; and pushing the page attribute information of the sixth page to the application.
In a possible implementation manner, the page management component is specifically configured to perform a pop operation on the page attribute information located after the page attribute information of the sixth page in the page attribute stack until the page attribute information of the sixth page is obtained.
In a possible implementation manner, the page management component is further specifically configured to sequentially execute a stacking operation on the page attribute information located after the page attribute information of the sixth page in the page attribute stack.
In a fourth aspect, an embodiment of the present application provides an application, where the application is configured to obtain a cross-system page jump operation triggered by a user; the cross-system page jump operation is used for indicating jump to a sixth page; acquiring the sixth page from the page stack of the application, and acquiring page attribute information of the sixth page based on the page attribute stack of the page management component; and displaying the sixth page according to the sixth page and the page attribute information of the sixth page.
In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed, performs the method of any one of the first and second aspects.
In a sixth aspect, an embodiment of the present application provides a computing device, including: a memory for storing program instructions; and the processor is used for calling the program instructions stored in the memory and executing the method in any one of the first aspect and the second aspect according to the obtained program.
In a seventh aspect, the embodiments of the present application provide a computer program product, which, when run on a processor, implements the method as designed in any one of the first and second aspects above.
The advantageous effects of the second aspect to the seventh aspect may specifically refer to the advantageous effects that can be achieved by any design of the first aspect, and are not described in detail herein.
Drawings
Fig. 1 schematically illustrates a scenario architecture provided by an embodiment of the present application;
fig. 2 schematically illustrates a page jump diagram provided in an embodiment of the present application;
fig. 3 is a schematic diagram illustrating a page management method provided by an embodiment of the present application;
fig. 4 is a schematic diagram illustrating a scenario architecture provided by an embodiment of the present application;
fig. 5 is a schematic diagram illustrating still another scenario architecture provided by an embodiment of the present application;
fig. 6 exemplarily shows a schematic diagram of another page management method provided in the embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention clearer, the present invention will be described in further detail with reference to the accompanying drawings, and it is apparent that the described embodiments are only a part of the embodiments of the present invention, not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Fig. 1 schematically illustrates a scenario architecture diagram provided in an embodiment of the present application. As shown in fig. 1, in a payment process, operations are required to be performed in multiple pages, and the next page is triggered to be entered through the operation of the previous page. As shown in fig. 1, page a is a navigation page, and in the navigation page, a plurality of buttons may be included, such as a scan button, a pay code button, a card management button, etc., and the user enters the next page by clicking one of the buttons. Assuming that the pay code button is clicked on user page a, then incoming page B is the pay code page. The payment code page comprises a payment bar code two-dimensional code display area, a bank card selection button, a payment code receiving button, a privacy policy entrance button and the like. After the merchant scans the payment bar code two-dimensional code and deducts the corresponding amount from the corresponding account, the merchant jumps to the page C, namely the payment completion page. The payment completion page includes a payment success identifier, payment amount, order information, a payment method, a completion button and the like, and the user returns to the page a by clicking the completion button. At this point, the payment process using the pay code is completed.
The payment process may be performed in an application of a bank, for example, by clicking a "scan" button on the home page of the application of the tenderer bank. In the application program of a bank, the jump logic and the page attribute of each page are configured by the bank, so that no fault occurs during the operation of a user. Continuing to take fig. 1 as an example, when the page a jumps to the page B, the attribute a of the page a may be obtained and stored in the page dimension of the page B immediately before the page a is hidden and the page B is to be displayed; and acquiring the attribute of the page B and storing the attribute in the page dimension of the page C before the page B is to be hidden and the page C is to be displayed. If the page C needs to be returned to the page B from the page C, the page C can acquire the attribute of the page B in the page dimension to recover, and the page C returns to the page B. If the page C needs to be returned to the page A from the page C, the page C can obtain the attribute of the page A from the page dimension of the page B for recovery after being returned to the page B, and the page B returns to the page. If the page C needs to be directly returned to the page A without passing through the page B, the return operation from the page C to the page A can be realized by setting a jump logic between the page C and the page A. That is, in an application program, the jump logic between pages is configured, and how to jump and return between pages is determined logic, so that no error occurs.
However, in a scenario that a banking institution accesses the cloud network SDK, a payment page repeatedly jumps between an application page of the bank and a page of the cloud network SDK, and different payment pages belong to different system architectures. Fig. 2 exemplarily shows a page jump schematic diagram provided in the embodiment of the present application, as shown in fig. 2, A1 and A2 represent pages of a bank, and B1, B2, and B3 represent pages of a cloud network SDK. In the application scenario, when jumping from the page A1 to the page B1, the page B1 needs to record the attribute A1 of the page A1 for returning to the page A1; when the page B1 jumps to the page A1, the page A1 needs to record the attribute B1 of the page B1 for returning to the page B1. However, in this scenario, since the page A1, the page B1, and the page A2 belong to different system architectures, it cannot be determined whether the page A2 will record the attribute B1 of the page B1 in the page dimension of the page A2. If page A2 does not have the attribute of attribute B1 of B1 recorded, then an error will occur when a return from page A2 to page B1 is required.
For example, the attribute of the navigation bar in page B1 is "0" (0 indicates that the navigation bar is hidden and 1 indicates that the navigation bar is displayed), and after page B1 jumps to page A2, the attribute of the navigation bar is changed to "1". At this time, if the page A2 is returned to the page B1, since the page A2 does not record that the attribute of the original page B1 is "0", even if the page is displayed as the page B1 at this time, the attribute is still the attribute "1" of the page A1, and the application display and the page attribute are not matched.
In addition, in the scenario of fig. 2, a plurality of pages jump continuously, and if it can be ensured that the next page records the attribute of the previous page, the last page can be returned forward step by step. For example, when it is required to return to the page A1 from the page B3, the page B3 may return to the page B2 according to the recorded attribute B2 of the page B2, and then the page B2 disappears; in the same manner, the page B2 is returned to the page A2, the page A2 is returned to the page B1, and finally the page B1 is returned to the page A1, and the attribute of the page A1 is restored. In the above scenario, since the attribute A1 of the page A1 is not recorded in the page dimension of the page B3, only the page of the previous stage can be returned step by step, and the attribute of the page of the previous stage is set; if returning directly from B3 to A1, although this is achievable in the page dimension, the attributes of page A1 are not recorded in page B3, so if returning directly from B3 to A1, the attributes of the A1 page are incorrect.
Based on the above problem, embodiments of the present application provide a page management method for ensuring normal jumping and returning between pages belonging to different system architectures.
Fig. 3 is a schematic diagram illustrating a page management method provided in an embodiment of the present application, and as shown in fig. 4, the method includes:
In step 302, the page management component determines a changed page indicated by the change information based on the monitored change information of the page stack.
Fig. 4 exemplarily shows a scenario architecture diagram provided in an embodiment of the present application, and the method illustrated in fig. 3 may be performed in the scenario illustrated in fig. 4. The scenario shown in fig. 4 includes a page management component and various page stacks, running in an application.
The page management component comprises page attribute stacks, the page attribute stacks can be in one-to-one correspondence with the page stacks, and the number of stored page attributes in the page stacks can be ensured to be relatively average. If the page attribute stack 1 corresponds to the page stack 1; the page attribute stack 2 corresponds to the page stack 2; page attribute stack 3 corresponds to page stack 3 … … page attribute stack n corresponds to page stack n; if the number of pages in a page stack is small, one page attribute stack can manage one page stack.
The page management stack is a stack for storing pages, and a plurality of pages can be stored in one page stack. If page stack 1 includes all the pages required to perform a payment operation, page stack 2 may be added to store the pages after page stack 1 is full.
Fig. 5 exemplarily shows a schematic diagram of a further scenario architecture provided in the embodiment of the present application, and fig. 5 shows an example where page attribute stack 1 listens to page stack 1. As shown in fig. 5, in one payment operation, the pages that may need to be skipped include A1 page, B1 page, A2 page, B2 page, and B3 page, and a payment process is not completed until the user jumps to B3 page after the display dimension of the pages, i.e., the user sees that the pages are from the A1 page. In the page stack dimension, each page jump adds a page to the page stack. The page attribute stack is used for storing page attribute information. The page attribute information may be used to set the attribute of the display or the stealth of one page. For example, the attribute information may be a gesture attribute. The gesture attributes include: sliding left from the edge of the page, sliding up from the bottom of the page, sliding up and down the scroll bar of the page, sliding left and right the scroll bar of the page, long-pressing the page, etc. For example, the page scroll bar is slid down, the page attribute information may be that the scroll bar can be scrolled, the scroll bar cannot be scrolled, and the like. The information on whether the scroll bar can be scrolled differs from page to page. Therefore, the page attribute information in the page attribute stack needs to perform the same operation as the page in the page stack.
In the above manner, a page attribute stack is established for storing page attribute information. When the page stack is changed, the page attribute of the changed page indicated by the change information is set, so that the page and the page attribute can be synchronized. Moreover, any change information in the page stack can be monitored, so that the page attribute can be changed when the page in the page stack is continuously changed for many times, and the normal operation on the page can be realized by the page after each change of the page.
Several specific page stack change information are presented below:
the first change information is: and the page management component monitors that the change information of the page stack is the newly added first page, and then determines that the second page displayed by the application is the change page indicated by the change information.
The description continues with the scenario architecture shown in fig. 5. And adding a B1 page in the page stack dimension page stack, wherein the change information is the newly added B1 page, the page indicated by the change information is the A1 page, and the corresponding dimension displayed in the application is to jump from the A1 page to the B1 page. It should be noted that, in the scenario shown in fig. 5, in the page stack, the A1 page may be loaded when the application is started, that is, the stack pushing operation of the A1 page is performed.
The page management component acquires page attribute information of the second page from the application corresponding to the change information one; and executing stack pushing operation on the page attribute information of the second page in the page attribute stack of the page management component.
As shown in fig. 5, the page management component acquires page attribute information of the A1 page from the application, and stacks the page attribute information of the A1 page in the page attribute stack.
In another possible implementation manner, after the page A1 jumps to the page B1, a page C is added between the page A1 and the page B1, at this time, the page indicated by the change information is the page C, and then the page C is in the page stack, so that the page C is stacked, and the page C may be above or below the page B1; in the attribute stack, the C page attribute is pushed. For ease of addressing, the C page attribute may be made below the B1 page attribute.
Jumping between other pages in fig. 5 may be performed with reference to jumping from the A1 page to the B1 page, and is not described in detail herein.
After the attribute information of the A1 page is stacked, the method is used for acquiring the A1 page attribute from the page attribute stack according to the page name of the A1 page when the B1 page returns to the A1 page, and resetting the attribute of the A1 page according to the A1 page attribute. It should be noted that when the A1 page jumps to the B1 page, the attribute of the A1 page may be changed, for example, the navigation bar is changed from display to hidden, so if the attribute of the A1 page is not reset when the B1 page returns to the A1 page, the operation of the user in the A1 page may be wrong.
Through the method, when the number of pages in the page stack is increased, the corresponding attribute information needs to be added into the attribute stack. On one hand, when the pages are jumped among the pages, the attribute information of the previous page is stored and viewed in time, and the original page attribute is prevented from being lost after the page attribute disappears and is changed, so that the original page cannot be returned to the original page. On the other hand, in the page jump process, the attribute information of the newly added page is also stored into the page attribute stack, so that the page jump and return are normal when a page which cannot be added by a user exists between two pages, and the application range of the page management component is more compatible.
And change information II: and the page management component monitors that the change information of the page stack is the third page, and then determines that the change page indicated by the change information is the third page.
In one possible implementation, the description continues with the scenario architecture shown in fig. 5. According to the flow in the change information 2, after the page jumps to the B2 page, the B1 page needs to be returned from the B2 page. At this time, in the page stack dimension, the deleted page is the B2 page and the A2 page. And displaying the real-time change page of the dimension change information on the page, namely the B2 page.
And the page management component executes a stack pulling operation on the page attribute information of the third page in a page attribute stack of the page management component corresponding to the change information II.
As shown in fig. 5, the page management component acquires the B2 page attribute and the A2 page attribute from the page attribute stack, and then acquires the B1 page attribute from the page attribute stack according to the page name of the B1 page, so that the attribute of the B1 page can be reset.
In another possible implementation, the pages that pass through can be deleted at any time when the page jumps. For example, in fig. 5, after the page display dimension reaches the B2 page, the application determines that the page does not return to the B2 page, so the B2 page may be deleted in the page stack, and correspondingly, the B2 page attribute may be deleted in the page attribute stack.
By the method, the change of the page attribute stack can be adjusted in time according to the change of the page stack, and when the page is deleted, the attribute information in the page attribute stack is deleted in time. On one hand, the storage space of the page attribute stack can be saved, and on the other hand, the unused attribute information is deleted, so that the target page attribute information can be obtained more conveniently.
Change information three: the page management component monitors that the change information of the page stack is that the fourth page is replaced by the fifth page, and then determines that the change pages indicated by the change information are the fourth page and the fifth page;
the description continues with the scenario architecture shown in fig. 5. And after the A1 page jumps to the B1 page, replacing the A1 page with a D page, wherein the pages indicated by the change information are the D page and the A1 page, and then popping the A1 page and popping the D page in a page stack.
Correspondingly, after the page attribute information of the A1 page is popped in the page attribute stack, the page management component executes a push operation on the page attribute information of the D page.
By the method, after the page is replaced by other pages, the attribute information is replaced in the page attribute stack corresponding to the page, so that the synchronization between the page attribute information and the page is ensured, and the setting of the page attribute is matched with the current page.
In one possible implementation, a page management component monitors a cross-system page jump operation of an application; the cross-system page jump operation is used for indicating jump to a sixth page; the page management component can acquire page attribute information of a sixth page through the page attribute stack; and the page management component pushes the page attribute information of the sixth page to the application.
The description continues with the scenario architecture shown in fig. 5. And according to the flow in the change information II, after the page jumps to the page B3, the payment process is finished. There is a done button on the B3 page and the user returns the page to the original A1 page by clicking on the done button. The page A1 may be a page in an APP of a banking institution, and the page B3, the page B2, the page A2, and the page B1 may be pages in a cloud flash payment APP, in which case, completing one payment operation spans pages of two applications. When the page needs to be returned to the A1 page from the B1 page, the page management component acquires the A1 page attribute information from the page attribute stack according to the page name of the page A1, and pushes the A1 page attribute information to the application where the A1 page is located, so that the application can set the A1 page attribute according to the A1 page attribute information.
Illustratively, when the page attribute information of the sixth page is acquired from the page attribute stack, the B2 page attribute information, the A2 page attribute information, and the B1 page attribute information may all be popped until the A1 page attribute information is acquired.
Through the method, in the storage mode of stacking, other unnecessary page attribute information is pushed out of the stack, and meanwhile, the required page attribute information is acquired. On one hand, the space of the page attribute stack is saved, and on the other hand, the required page attribute information can be acquired more conveniently.
If the pop sequence in the above manner is to be implemented, when stacking page attribute information, stacking can be performed in the order of page jump. As shown in fig. 5, after jumping to the last page B3, B2 page attribute information, A2 page attribute information, and B1 page attribute information, A1 page attribute information are sequentially arranged in the page attribute stack from top to bottom according to the order of page jumping.
By the method, the information stored in the storage structure of the stack is consistent with the actual page jump process, and the stack-out and stack-in operations are more convenient and faster to execute in the page jump.
Based on the same technical concept, the embodiment of the application also provides a page management method. Fig. 6 exemplarily shows a schematic diagram of another page management method provided in an embodiment of the present application, and as shown in the drawing, the method includes:
Based on the same technical concept, the embodiment of the application further provides a page management component, wherein the page management component is used for running after the application is started and monitoring the page stack of the application; the page stack is used for sequentially storing the pages in the application operation; the page management component is further configured to determine a changed page indicated by the change information based on the monitored change information of the page stack; the page management component is also used for executing the same stack in and out operation as the page stack in the page attribute stack of the page management component on the page attribute information corresponding to the changed page; and the page attribute information in the page attribute stack is used for the application to perform cross-system page jump.
In a possible implementation manner, the page management component is specifically configured to monitor that change information of the page stack is a newly added first page, and determine that a second page displayed by the application is a change page indicated by the change information; the page management component is specifically further configured to acquire page attribute information of the second page from the application; and executing stack pushing operation on the page attribute information of the second page in the page attribute stack of the page management component.
In a possible implementation manner, the page management component is specifically configured to monitor that the change information of the page stack is to delete a third page, and determine that the change page indicated by the change information is the third page; the page management component is further specifically configured to, in a page attribute stack of the page management component, perform a pop operation on the page attribute information of the third page.
In a possible implementation manner, the page management component is specifically configured to monitor that change information of the page stack is that a fourth page is replaced by a fifth page, and determine that a change page indicated by the change information is the fourth page and the fifth page; the page management component is further specifically configured to, in a page attribute stack of the page management component, perform a pop operation on the page attribute information of the fourth page, and then perform a pop operation on the page attribute information of the fifth page.
In a possible implementation manner, the page management component is further configured to monitor a cross-system page jump operation of the application; the cross-system page jump operation is used for indicating jump to a sixth page; the page management component acquires page attribute information of the sixth page through the page attribute stack; and pushing the page attribute information of the sixth page to the application.
In a possible implementation manner, the page management component is specifically configured to perform a pop operation on the page attribute information located after the page attribute information of the sixth page in the page attribute stack until the page attribute information of the sixth page is obtained.
In a possible implementation manner, the page management component is further specifically configured to sequentially execute a stacking operation on the page attribute information located after the page attribute information of the sixth page in the page attribute stack.
Based on the same technical concept, an embodiment of the present invention further provides a computing device, including: a memory for storing program instructions;
a processor for calling the program instructions stored in the memory and executing the method illustrated in fig. 3 and 6 according to the obtained program.
Based on the same technical concept, embodiments of the present invention also provide a computer-readable storage medium, which when running on a processor implements the method illustrated in fig. 3 and 6.
Based on the same technical concept, the embodiment of the present invention also provides a computer program product, which when running on a processor implements the method as illustrated in fig. 3 and 6.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.
Claims (10)
1. A page management method, characterized in that the method comprises:
the page management component operates after the application is started and monitors the page stack of the application; the page stack is used for sequentially storing the pages in the application operation;
the page management component determines a change page indicated by the change information based on the monitored change information of the page stack;
the page management component executes stack in and out operation which is the same as the page stack in the page attribute stack of the page management component on the page attribute information corresponding to the changed page; and the page attribute information in the page attribute stack is used for the application to perform cross-system page jump.
2. The method of claim 1, wherein the page management component determines a changed page indicated by the change information based on the monitored change information of the page stack, comprising:
the page management component monitors that the change information of the page stack is a newly added first page, and then determines that a second page displayed by the application is a change page indicated by the change information;
the page management component executes the same stack in and out operation as the page stack in the page attribute stack of the page management component on the page attribute information corresponding to the changed page, and the operation comprises the following steps:
the page management component acquires page attribute information of the second page from the application;
and executing stack pushing operation on the page attribute information of the second page in the page attribute stack of the page management component.
3. The method of claim 1, wherein the page management component determines a changed page indicated by the change information based on the monitored change information of the page stack, comprising:
the page management component monitors that the change information of the page stack is a third page, and then determines that the change page indicated by the change information is the third page;
the page management component executes the same stack in and out operation as the page stack in the page attribute stack of the page management component for the page attribute information corresponding to the changed page, and the operation comprises the following steps:
and the page management component executes a stack pulling operation on the page attribute information of the third page in a page attribute stack of the page management component.
4. The method of claim 1, wherein the page management component determines a changed page indicated by the change information based on the monitored change information of the page stack, comprising:
the page management component monitors that the change information of the page stack is that a fourth page is replaced by a fifth page, and then determines that the change pages indicated by the change information are the fourth page and the fifth page;
the page management component executes the same stack in and out operation as the page stack in the page attribute stack of the page management component for the page attribute information corresponding to the changed page, and the operation comprises the following steps:
and after the page management component performs a pop operation on the page attribute information of the fourth page in a page attribute stack of the page management component, the page management component performs a push operation on the page attribute information of the fifth page.
5. The method of claim 1, wherein the method further comprises:
the page management component monitors the cross-system page jump operation of the application; the cross-system page jump operation is used for indicating jump to a sixth page;
the page management component acquires page attribute information of the sixth page through the page attribute stack;
and the page management component pushes the page attribute information of the sixth page to the application.
6. The method of claim 5, wherein the page management component obtains page attribute information of the sixth page through the page attribute stack, comprising:
and the page management component executes the stack pulling operation on the page attribute information positioned behind the page attribute information of the sixth page in the page attribute stack until the page attribute information of the sixth page is obtained.
7. The method of claim 6, wherein the method further comprises: after the page attribute information of the sixth page is obtained, the method further includes:
and sequentially executing stack-entering operation on the page attribute information positioned after the page attribute information of the sixth page in the page attribute stack.
8. A page management method, characterized in that the method comprises:
the application acquires cross-system page jump operation triggered by a user; the cross-system page jump operation is used for indicating jump to a sixth page;
the application acquires the sixth page from the page stack of the application and acquires page attribute information of the sixth page based on the page attribute stack of the page management component;
and the application displays the sixth page according to the sixth page and the page attribute information of the sixth page.
9. A computer-readable storage medium, characterized in that it stores a computer program which, when executed, performs the method according to any one of claims 1 to 8.
10. A computing device, comprising:
a memory for storing program instructions;
a processor for calling program instructions stored in said memory to execute the method of any one of claims 1 to 8 in accordance with the obtained program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211049982.4A CN115439117A (en) | 2022-08-30 | 2022-08-30 | Page management method, medium and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211049982.4A CN115439117A (en) | 2022-08-30 | 2022-08-30 | Page management method, medium and equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115439117A true CN115439117A (en) | 2022-12-06 |
Family
ID=84243846
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211049982.4A Pending CN115439117A (en) | 2022-08-30 | 2022-08-30 | Page management method, medium and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115439117A (en) |
-
2022
- 2022-08-30 CN CN202211049982.4A patent/CN115439117A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105005429B (en) | A kind of method and terminal of terminal display picture | |
| CN107050850A (en) | The recording and back method of virtual scene, device and playback system | |
| JP6794347B2 (en) | Application interface navigation | |
| CN111324535B (en) | Control abnormity detection method and device and computer equipment | |
| CN111258478B (en) | Method and device for displaying batch object list data and single object detail data | |
| CN106874326A (en) | A kind of item list obtains request processing method and device | |
| WO2024093784A1 (en) | Method and apparatus for displaying notification message, and electronic device | |
| CN113975788A (en) | Entry indexing method and device, computer equipment and storage medium | |
| CN107368235B (en) | Multi-task switching method of function machine and function machine | |
| CN113271486B (en) | Interactive video processing method, device, computer equipment and storage medium | |
| CN112843707B (en) | Method, device, medium and product for processing reloading of game object | |
| CN115439117A (en) | Page management method, medium and equipment | |
| US20230054388A1 (en) | Method and apparatus for presenting audiovisual work, device, and medium | |
| CN109460524A (en) | Method, apparatus, storage medium and the client that the page returns | |
| CN113377975B (en) | Method and device for processing multimedia resources, computer equipment and storage medium | |
| CN113672650B (en) | Method, device, equipment and storage medium for selecting data in page crossing mode | |
| CN114253752A (en) | Application crash processing method, device, equipment and medium | |
| CN111273988B (en) | Account display method and device | |
| CN114442868A (en) | Method, apparatus, device, medium, and program product for displaying distribution status information | |
| CN110221952B (en) | Service data processing method and device and service data processing system | |
| CN108829824B (en) | Resource processing method and device in internet operation activity | |
| KR101699036B1 (en) | Device and method to provide card item | |
| CN111984809A (en) | Image searching method and related device | |
| CN116225602A (en) | Jump management method and device for user interface, electronic equipment and storage medium | |
| CN114159780A (en) | Stacking control method and device of game props, terminal equipment 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 |