CN114116075B - A method, device, electronic device and storage medium for obtaining page parameters - Google Patents
A method, device, electronic device and storage medium for obtaining page parameters Download PDFInfo
- Publication number
- CN114116075B CN114116075B CN202111358097.XA CN202111358097A CN114116075B CN 114116075 B CN114116075 B CN 114116075B CN 202111358097 A CN202111358097 A CN 202111358097A CN 114116075 B CN114116075 B CN 114116075B
- Authority
- CN
- China
- Prior art keywords
- page
- parameters
- manager
- current
- current page
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 57
- 238000003860 storage Methods 0.000 title claims abstract description 16
- 230000004044 response Effects 0.000 claims description 30
- 238000004590 computer program Methods 0.000 claims description 7
- 230000009191 jumping Effects 0.000 abstract description 10
- 238000007726 management method Methods 0.000 description 45
- 230000006870 function Effects 0.000 description 27
- 230000000694 effects Effects 0.000 description 19
- 238000010586 diagram Methods 0.000 description 17
- 230000008569 process Effects 0.000 description 13
- 238000012545 processing Methods 0.000 description 11
- 238000004891 communication Methods 0.000 description 10
- 238000005516 engineering process Methods 0.000 description 6
- 230000004048 modification Effects 0.000 description 6
- 238000012986 modification Methods 0.000 description 6
- 230000003287 optical effect Effects 0.000 description 5
- 238000012546 transfer Methods 0.000 description 5
- 238000004080 punching Methods 0.000 description 4
- 230000005236 sound signal Effects 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 3
- 230000001133 acceleration Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000011084 recovery Methods 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000003384 imaging method Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Classifications
-
- 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/448—Execution paradigms, e.g. implementations of programming paradigms
- G06F9/4482—Procedural
- G06F9/4484—Executing subprograms
- G06F9/4486—Formation of subprogram jump address
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)
- Read Only Memory (AREA)
Abstract
The disclosure relates to a method, a device, electronic equipment and a storage medium for acquiring page parameters of a current page, wherein the method comprises the steps of acquiring the page parameters of the current page, determining corresponding parameters in a page manager associated with the current page according to the page parameters of the current page, responding to a jump instruction of the current page, jumping from the current page to a target page, associating the target page with the current page and the page manager, and acquiring parameters required by the target page from the page manager. Therefore, parameters in the pages associated with the page manager can be managed through the page manager, reading and writing of all parameters from an intent component of the last page are not needed when each page jumps, the operation is convenient, and parameter omission and loss are not easy to occur.
Description
Technical Field
The disclosure relates to the field of short videos, and in particular relates to a method and device for acquiring page parameters, electronic equipment and a storage medium.
Background
With the complexity of APP (Application) service, in some scenarios, when a page is jumped, some parameters need to be transferred from a previous page to a subsequent page, for example, in a card-punching attack event in a short video APP, after a user determines to participate in the event from an event page, a client acquires an event identifier of the event, and transfers the event identifier from a video shooting page to a video publishing page, and when the video is finally published, the event identifier is uploaded to a server together with the video, and if the server detects the event identifier, the user is considered to successfully play the card to participate in the event.
In the prior art, parameters can be transferred through the intent components among pages, and each page needs to write all parameters into the intent components of the page, so that after the page is jumped, the jumped page can acquire the required parameters from the intent components of the previous page.
However, in the above page parameter obtaining manner, each page needs to write all parameters into the content component of the corresponding page, so that the operation is complicated, omission occurs easily, the parameters are lost, and the execution of the APP service is affected.
Disclosure of Invention
The disclosure provides a method, a device, electronic equipment and a storage medium for acquiring page parameters, which are used for at least solving the problems of complicated acquisition of the page parameters and easy loss of the parameters in the related technology. The technical scheme of the present disclosure is as follows:
According to a first aspect of an embodiment of the present disclosure, there is provided a page parameter obtaining method, including:
Acquiring page parameters of a current page, and determining corresponding parameters in a page manager associated with the current page according to the page parameters of the current page;
in response to a jump instruction of the current page, jumping from the current page to a target page, wherein the target page and the current page are associated with the page manager;
and acquiring parameters required by the target page from the page manager.
Optionally, the obtaining the page parameter of the current page, determining, according to the page parameter of the current page, a corresponding parameter in a page manager associated with the current page, includes:
If the current page is determined to be the first page of a preset scene, creating a page manager of the preset scene, initializing parameters in the created page manager, and determining corresponding parameters in the page manager associated with the current page based on the parameters in the initialized page manager, wherein the parameters in the initialized page manager comprise the page parameters of the current page;
if the current page is not the first page of the preset scene, acquiring page parameters of the current page from a page manager associated with the current page, wherein the parameters in the page manager associated with the current page are determined based on the page parameters of the last page of the current page, updating the page parameters of the current page in response to an input instruction of the page parameters of the current page, and updating the corresponding parameters in the page management associated with the current page according to the updated page parameters of the current page.
Optionally, the initializing parameters in the created page manager includes:
Acquiring preset parameters corresponding to the preset scene and initial values of the preset parameters, initializing parameters in the created page manager, acquiring page parameters of the current page from the initialized parameters of the page manager, or,
And acquiring the page parameters and page parameter values in the current page, and initializing the parameters in the created page manager.
Optionally, after determining the corresponding parameter in the page manager associated with the current page based on the parameter in the initialized page management, the method further includes:
and responding to an input instruction of the page parameters of the current page, updating the page parameters of the current page, and determining the value of the parameters in the created page manager according to the updated page parameters of the current page.
Optionally, the page parameters of the current page include modifiable parameters and non-modifiable parameters, and the method further includes:
After the page parameters of the current page are obtained, writing the modifiable parameters and the values of each modifiable parameter into a preset component of the current page;
And responding to an instruction for returning the current page, reading the non-modifiable parameter from the page manager, acquiring the modifiable parameter from a preset component of the current page, displaying the current page based on the non-modifiable parameter in the page manager and the modifiable parameter acquired from the preset component, and modifying the value of the corresponding parameter in the page manager according to the value of the modifiable parameter of the preset component.
Optionally, the method further comprises:
After any page associated with the page manager is opened, generating a key value pair of the any page;
adding the key value pair of any page to the page manager;
in response to a page close instruction for the any page associated with the page manager, the key value pair for the any page is deleted from the page manager.
Optionally, the method further comprises:
counting the number of key value pairs in the page manager;
and deleting the page manager in the condition that the number is zero.
Optionally, the method further comprises:
And responding to a parameter expansion instruction of the page parameters of the current page, and adding the page parameters in the page manager.
According to a second aspect of the embodiments of the present disclosure, there is provided a page parameter acquiring apparatus, including:
A first acquisition unit configured to perform acquisition of a page parameter of a current page, and determine a corresponding parameter in a page manager associated with the current page according to the page parameter of the current page;
a jump unit configured to execute a jump instruction in response to the current page, to jump from the current page to a target page, the target page and the current page being associated with the page manager;
And a second acquisition unit configured to perform parameters required for acquiring the target page from the page manager.
Optionally, the first obtaining unit is configured to perform:
If the current page is determined to be the first page of a preset scene, creating a page manager of the preset scene, initializing parameters in the created page manager, and determining corresponding parameters in the page manager associated with the current page based on the parameters in the initialized page manager, wherein the parameters in the initialized page manager comprise the page parameters of the current page;
if the current page is not the first page of the preset scene, acquiring page parameters of the current page from a page manager associated with the current page, wherein the parameters in the page manager associated with the current page are determined based on the page parameters of the last page of the current page, updating the page parameters of the current page in response to an input instruction of the page parameters of the current page, and updating the corresponding parameters in the page management associated with the current page according to the updated page parameters of the current page.
Optionally, the first obtaining unit is further configured to perform:
Acquiring preset parameters corresponding to the preset scene and initial values of the preset parameters, initializing parameters in the created page manager, acquiring page parameters of the current page from the initialized parameters of the page manager, or,
And acquiring the page parameters and page parameter values in the current page, and initializing the parameters in the created page manager.
Optionally, the first obtaining unit is further configured to perform:
And responding to an input instruction of the page parameters of the current page, updating the page parameters of the current page, and determining the value of the corresponding parameters in the page manager according to the updated page parameters of the current page.
Optionally, the parameters in the current page include modifiable parameters and non-modifiable parameters, and the apparatus further includes:
The storage unit is configured to execute the preset component for writing the modifiable parameters and the values of each modifiable parameter into the current page after acquiring the page parameters of the current page;
And the return unit is configured to execute an instruction for responding to the current page, read the non-modifiable parameter from the page manager, acquire the modifiable parameter from a preset component of the current page, display the current page based on the non-modifiable parameter in the page manager and the modifiable parameter acquired from the preset component, and modify the value of the corresponding parameter in the page manager according to the value of the modifiable parameter of the preset component.
Optionally, the apparatus further includes:
The system comprises a statistics unit, a key value pair generation unit and a page management unit, wherein the statistics unit is configured to generate a key value pair of any page after any page associated with the page manager is opened, add the key value pair of any page into the page manager, and delete the key value pair of any page from the page manager in response to a page closing instruction for the any page associated with the page manager.
Optionally, the statistics unit is further configured to perform:
counting the number of key value pairs in the page manager;
and deleting the page manager in the condition that the number is zero.
Optionally, the apparatus further includes:
and an editing unit configured to execute a parameter expansion instruction in response to a page parameter for the current page, the page parameter being added in the page manager.
According to a third aspect of the embodiments of the present disclosure, there is provided a page parameter acquiring electronic device, including:
A processor;
a memory for storing the processor-executable instructions;
Wherein the processor is configured to execute the instructions to implement the page parameter acquisition method of any one of the above.
According to a fourth aspect of embodiments of the present disclosure, there is provided a computer-readable storage medium, which when executed by a processor of a page parameter acquiring electronic device, causes the page parameter acquiring electronic device to perform the page parameter acquiring method of any one of the above.
According to a fifth aspect of embodiments of the present disclosure, there is provided a computer program product comprising a computer program/instruction which, when executed by a processor, implements the page parameter obtaining method of any one of the above.
The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:
The method comprises the steps of obtaining page parameters of a current page, determining corresponding parameters in a page manager associated with the current page according to the page parameters of the current page, responding to a jump instruction of the current page, jumping from the current page to a target page, associating the target page with the current page in the same page manager, and obtaining parameters required by the target page from the page manager.
Therefore, when the page jumps, any target page after the jump can acquire required target parameters from the page manager under the condition that the target page and the current page are related to the same page manager, that is, the parameters in the page related to the target page can be managed through the page manager, reading and writing of all parameters from an agent component of the last page are not required when each page jumps, the operation is more convenient, and parameter omission and loss are not easy to occur.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure and do not constitute an undue limitation on the disclosure.
Fig. 1 is a flowchart illustrating a page parameter acquisition method according to an exemplary embodiment.
FIG. 2 is a diagram of the relationship of individual page activities to base classes BaseActivity in accordance with an example embodiment.
FIG. 3 is a logical illustration of managing singleton management objects ActivitySession in accordance with one illustrative embodiment.
FIG. 4 is a class diagram of a single instance management object ActivitySession, shown in accordance with an example embodiment.
FIG. 5 is a class diagram of one parameter CommonParams shown according to an example embodiment.
Fig. 6 is a schematic diagram of processing logic for one parameter CommonParams shown in accordance with an example embodiment.
FIG. 7 is a diagram illustrating a page jump of a business process, according to an example embodiment.
Fig. 8 is a block diagram illustrating a page parameter acquiring apparatus according to an exemplary embodiment.
FIG. 9 is a block diagram of an electronic device for page parameter acquisition, according to an example embodiment.
Fig. 10 is a block diagram illustrating an apparatus for page parameter acquisition, according to an example embodiment.
Detailed Description
In order to enable those skilled in the art to better understand the technical solutions of the present disclosure, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the foregoing figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the disclosure described herein may be capable of operation in sequences other than those illustrated or described herein. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.
Fig. 1 is a flowchart illustrating a page parameter acquiring method, as shown in fig. 1, used in a user device that can interact with a user, according to an exemplary embodiment.
In step S11, the page parameters of the current page are acquired, and corresponding parameters in the page manager associated with the current page are determined according to the page parameters of the current page.
In the present disclosure, the current page may be a page in a browser or a page in an application, which is not limited specifically.
In one implementation, obtaining the page parameter of the current page, determining the corresponding parameter in the page manager associated with the current page according to the page parameter of the current page may include the following two cases:
If the current page is determined to be the first page of the preset scene, a page manager of the preset scene is created, parameters in the created page manager are initialized, corresponding parameters in the page manager associated with the current page are determined based on the initialized parameters in the page manager, and the initialized parameters in the page manager comprise the page parameters of the current page.
If the current page is not the first page of the preset scene, acquiring page parameters of the current page from a page manager associated with the current page, wherein the parameters in the page manager associated with the current page are determined based on the page parameters of the last page of the current page, updating the page parameters of the current page in response to an input instruction of the page parameters of the current page, and updating the corresponding parameters in the page management associated with the current page according to the updated page parameters of the current page.
Therefore, the page manager of the preset scene is automatically created, so that the page manager is more flexible to create, the parameter management is facilitated, and the operation required to be executed by a user is simplified.
The preset scene may correspond to any service, that is, if the current page is the first page of any pre-identified service flow, a page manager corresponding to the service flow is created, and each parameter required in the service flow is included in the page manager.
In one implementation, initializing parameters included in the created page manager may specifically include obtaining preset parameters corresponding to a preset scene and initial values of each preset parameter, initializing parameters in the created page manager, and obtaining page parameters of a current page from the initialized parameters of the page manager. That is, the parameters and the initial values corresponding to each preset scene are preset, the current page can acquire the required page parameters and the initial values thereof from the page manager, the value of each parameter does not need to be determined from the current page, and the user operation required on the current page is simplified.
In another implementation, the parameters included in the created page manager are initialized, specifically, the parameters of the page in the current page and the values of the parameters of the page are obtained, and the parameters in the created page manager are initialized. That is, the parameters and the initial values of the parameters in the page manager are created by using the page parameters and the page parameter values of the current page, so that the page manager is more flexible to create, and the preset operation required by a user is reduced.
In the present disclosure, after determining the corresponding parameters in the page manager associated with the current page based on the initialized parameters in the page management, the page parameters of the current page may also be updated in response to an input instruction of the page parameters of the current page, and the values of the parameters in the created page manager may be determined according to the updated page parameters of the current page.
That is, when the page parameters of the current page are updated, the corresponding parameters in the page manager are updated accordingly, so that the parameters between pages associated with the same page manager are convenient to unify, and the condition of parameter transmission errors is reduced.
In step S12, in response to the jump instruction of the current page, jumping from the current page to a target page, the target page being associated with the same page manager as the current page.
The page jump instruction is used for indicating the user equipment to jump from the current page to the next page, and for convenience of description, the page after jumping is called a target page. The page jump instruction may be generated according to a user operation, for example, different target pages may correspond to different key areas in the current page, and according to a user selection operation on any key area, the target page that the user needs to jump may be determined, so as to generate the page jump instruction.
Or the page jump instruction may be preset, for example, the jump sequence between the pages may be preset, and when the browsing time of the user on the current page reaches the first preset duration, the page jump instruction is automatically generated to instruct the user equipment to jump from the current page to the next page which is preset, that is, the target page.
After the page jumps, the current page can be directly closed, so that the occupation of the current service to system resources is reduced. Or the current page can continue to run in the background, and the current page is closed after a page closing instruction is received or a second preset time period is passed, so that if the page fails to jump or the target page is wrong, the page before the jump can be quickly switched to, and the stability of the current service is improved. The setting may be specifically performed according to a user's requirement, which is not limited in the present disclosure.
In step S13, parameters required for the target page are acquired from the page manager.
In this step, after the jump to the target page, it may be first determined whether the target page and the current page are associated with the same page manager, if so, it indicates that the target page and the current page participate in the transfer of the same set of parameters, and these parameters are stored in the page manager, so that the parameters required by the target page may be obtained from the page manager. If the target page and the current page are not associated with the same page manager, the target page and the current page are indicated to correspond to different parameters, and parameter transmission is not needed between the target page and the current page. The parameters required by the current page and the target page may be all parameters in the page manager, or may be a part of parameters therein, which is not limited in particular.
In one implementation, the page standard parameter may be modified on the user device, specifically, the value of the page parameter may be obtained in response to a modification instruction for the page parameter of the current page, and the value of the corresponding parameter in the page manager is determined, so that the parameter obtained from the page manager by the page after the current page is the parameter after modification, thereby implementing modification and update of the parameter in the transfer process.
The parameters in the current page include modifiable parameters and non-modifiable parameters, the modifiable parameters are parameters that may be modified in the business process, the non-modifiable parameters are parameters that may not be modified in the business process, and in one implementation, after the page parameters of the current page are obtained, the modifiable parameters and the values of each modifiable parameter may be written into a preset component of the current page.
It can be understood that the non-modifiable parameters are not modified, can be obtained from the page manager at any time, and are not updated with version errors, so that the data redundancy can be reduced without writing into a preset component of the current page for caching. And for the modifiable parameters, the modifiable parameters are written into a preset component of the current page to be cached, so that the subsequent maintenance and recovery of the modifiable parameters are facilitated.
The preset component of the current page may be an intent component of the Android platform, or may also be a Map object or an array object of other platforms, which may achieve the same effect, and is not limited in detail.
For example, after writing the modifiable parameters into the component of the target page, the current page may be returned from any page in response to a page return instruction for the current page at any page, while the non-modifiable parameters are read from the page manager, the modifiable parameters are obtained from the preset component of the current page, the current page is displayed based on the non-modifiable parameters in the page manager and the modifiable parameters obtained from the preset component, and the values of the corresponding parameters in the page manager are modified according to the values of the modifiable parameters of the preset component.
That is, if the current page is jumped back from other pages, the modifiable parameters cached in the preset component of the current page can be read, and the modifiable parameters in the page manager are modified, so that the modifiable parameters in the page manager are modified to the values of the previous jump to the current page, and recovery in the parameter transfer and return processes is ensured.
In one implementation, the number of pages in an open state associated with the page manager can also be counted, specifically, after any page associated with the page manager is opened, a key value pair of any page is generated, the key value pair of any page is added to the page manager, and the key value pair of any page is deleted from the page manager in response to a page closing instruction for any page associated with the page manager.
In this way, the number of pages in an open state associated with the page manager may be determined based on the number of key-value pairs in the page manager, which may be stored in the key-value pair manager, facilitating management of the pages associated with the page manager.
Furthermore, the number of key-value pairs in the page manager may be counted, and in case the number is zero, the page manager may be deleted. That is, when the page manager does not have an associated page in an open state, the page manager is deleted, thereby avoiding leakage of data and also reducing redundant data.
In another implementation manner, the page parameters can be added in the page manager in response to the parameter expansion instruction of the page parameters of the current page, so that the parameters which can be transferred in the page jump process can be increased, and the dynamic modification of the parameters in the page manager is realized, and the operation is more flexible.
In this disclosure, if any pages are associated with the same page manager, it means that the pages inherit the base class of the same single management object, where the single management object may be denoted as ActivitySession, the base class of the single management object may be denoted as BaseActivity, the base class BaseActivity includes the parameter CommonParams, the parameter CommonParams is a parameter that needs to be transferred between pages, the pages participating in the transfer of the same set of parameters may be denoted as inheriting different activities of the same base class BaseActivity, in other words, each page Activity includes the base class BaseActivity of the single management object, and the data of the parameter CommonParams may be read from the base class BaseActivity of the single management object.
For example, as shown in fig. 2, a schematic diagram of the relationship between each page Activity and the base class BaseActivity in one implementation is shown, where STARTACTIVITY, XXXXXACTIVITY, i.e., i.a., i. FINALLYACTIVITY, respectively correspond to the pages from the first page to the last page in a certain business process, and these pages all inherit the base class BaseActivity, in other words, these pages are all associated with the same page manager.
As shown in fig. 3, a logic diagram for managing the singleton management object ActivitySession is shown. The single-instance management object ActivitySession includes a base class BaseActivity and Map < String > object, and the base class BaseActivity includes a onCreate class and a onDestory class.
After the current page is opened, onCreate classes can be called, if the current page Activity is the first page of any business process, a single-instance management object ActivitySession corresponding to the business process is created, the current page Activity is added to the Map object, and a ADDACTIVITY function is called each time a new target page Activity is opened, the target page Activity is added to the Map object for management.
When the current page Activity is closed, a removeActivity function in the onDestory class is called, the current page Activity is removed from the Map object, and the singleton management object ActivitySession is deleted if the Map object is empty.
Therefore, management of the single management object ActivitySession can be achieved through onCreate and onDestory, and ActivitySession achieves self life cycle management through a reference counting principle, and when all pages are finished, map objects are empty, the Map objects can be destroyed, so that memory leakage is avoided.
As shown in FIG. 4, a class diagram of a single instance management object ActivitySession in one implementation includes ISINSTANCE functions, MACTIVITYMAP functions, mCommonParams functions, GETINSTANCE functions, ADDACTIVITYMAP functions, removeActivity functions, and getCommonParams functions. The ISINSTANCE function is used for defining a single-case management object ActivitySession, mActivityMap function, a Map < String > object, a mCommonParams function, a parameter CommonParams and a GETINSTANCE function, wherein the single-case management object ActivitySession, mActivityMap function is used for defining a page in an open state corresponding to the single-case management object, the Map < String > object is used for counting the page in the open state, the GETINSTANCE function is used for creating a single-case management object ActivitySession, addActivityMap function, the page is added into a Map array, the removeActivity function is used for removing the page from the Map object, and the getCommonParams function is used for acquiring the parameter CommonParams from the single-case management object ActivitySession.
As shown in fig. 5, a class diagram of parameters CommonParams in one implementation is shown, where field functions are used to define the data type of CommonParams, initData functions are used to read data stored in component content of any page, SETINTENTDATA functions are used to store data to component content of any page.
As shown in fig. 6, a processing logic diagram of a parameter CommonParams in an implementation manner is shown, where after a current page is opened, onCreate class may be called, if the current page Activity is the first page of any business flow, a single-instance management object ActivitySession corresponding to the business flow is created, a initData function is used to read a parameter in a component content of the current page, initialize memory data of the parameter mCommonParams, and add the current page Activity to a Map object, and, every time a new target page Activity is opened, a ADDACTIVITY function is called to add the target page Activity to the Map object for management, and, at the same time, a SETINTENTDATA function is used to write the memory data of the parameter mCommonParams into the component content of the target page Activity, for example, an Android system content function may be called, and data is stored in the component content of the target page Activity. Therefore, when the target page needs to read and write data, the current parameter value can be directly read and written through the memory data defined in CommonParams, and the operation is convenient and fast without concern about the key to acquire from the component content.
When returning to the current page from any page, the onResume class may be called, and the memory data of parameter mCommonParams may be reinitialized according to the value of the target parameter in the component content of the target page.
After the current page is opened, STARTACTIVITY functions can be called, whether the page parameters of the current page need to be modified or not is judged according to the specific service of the current page, if not, no operation is executed, and if a modification instruction for the page parameters is received, the data of the parameters mCommonParams in the single-instance management object ActivitySession are modified. The jump flow for the next page may then be returned.
When the current page Activity is closed, a removeActivity function in the onDestory class is called, the current page Activity is removed from the Map object, and the singleton management object ActivitySession is deleted if the Map object is empty.
In order to facilitate understanding, the technical solution provided in the present disclosure is described below by means of a specific embodiment. FIG. 7 is a schematic diagram of a page jump of a business process in one implementation. The jump flow of the whole production page is managed by a page manager, wherein the page manager is a single-instance management object ActivitySession, and parameters CommonParams comprise ACTIVITYID and tags (topic labels).
The method comprises the steps of jumping from an active card punching page to a shooting page, wherein the shooting page is the first page of the business flow, creating a single management object ActivitySession after entering the shooting page, acquiring ACTIVITYID and tag from component content of the shooting page, and initializing ACTIVITYID: "666" and tag: "# in parameters CommonParams in the single management object ActivitySession for card punching today.
If the shot page is jumped to an edit page or other target page such as an album, the onCreate class is called, and tag "# today is checked in" to be written into the component content of the target page, ACTIVITYID can be omitted from writing, and ACTIVITYID values can not be modified in the whole business process, so that the target page can be directly read and used in the single-instance management object ActivitySession.
If the shot page is jumped to the one-key-out page, a tag is required to be added in the following step, "# one-key-out", and then parameters CommonParams in the single management object ActivitySession are modified when the shot page is jumped to the edit page, and the tag is modified from "# today's punch card" to "# today's punch card # one-key-out".
If the one-key out page jumps to the editing page, the onCreate class can be called, the tag is read from the single-case management object ActivitySession and written into the component content of the editing page, and then when the one-key out page jumps to the release page, the release page directly reads the tag from the parameter CommonParams of the single-case management object ActivitySession, displays the tag in the text editing box "# today and # one-key out as a release work document, and reads ACTIVITYID and reports the release work document to the server when the release button is clicked.
If the return key is clicked on the one-key out page to return to the shooting page, then onResume classes can be called, tag: "# today card punching" can be obtained from the component content of the shooting page, and the value of the tag in the parameter CommonParams of the single-instance management object ActivitySession is updated.
In the present disclosure, if other pages are newly added in any business process, only the page is required to be associated with the business process page manager, so that the parameters can be guaranteed to be transmitted under the normal transmission of the page, and the new writing code is not required to be transmitted to the next page, so that the operation is more convenient.
In view of the foregoing, in the technical solution provided in the embodiments of the present disclosure, when a page jumps, any target page after jumping may obtain a required target parameter from the page manager when the target page and the current page are associated with the same page manager, that is, the parameters in the page associated with the target page may be managed by the page manager, and reading and writing of all parameters from an intent component of a previous page do not need to be performed by each page when the page jumps, so that the operation is relatively convenient, and parameter omission and loss are not easy to occur.
FIG. 8 is a block diagram illustrating a page parameter acquisition device according to an exemplary embodiment, the device comprising:
A first acquisition unit configured to perform acquisition of a page parameter of a current page, and determine a corresponding parameter in a page manager associated with the current page according to the page parameter of the current page;
a jump unit configured to execute a jump instruction in response to the current page, to jump from the current page to a target page, the target page and the current page being associated with the page manager;
And a second acquisition unit configured to perform parameters required for acquiring the target page from the page manager.
In one embodiment of the method of the present invention,
The first acquisition unit is configured to perform:
If the current page is determined to be the first page of a preset scene, creating a page manager of the preset scene, initializing parameters in the created page manager, and determining corresponding parameters in the page manager associated with the current page based on the parameters in the initialized page manager, wherein the parameters in the initialized page manager comprise the page parameters of the current page;
if the current page is not the first page of the preset scene, acquiring page parameters of the current page from a page manager associated with the current page, wherein the parameters in the page manager associated with the current page are determined based on the page parameters of the last page of the current page, updating the page parameters of the current page in response to an input instruction of the page parameters of the current page, and updating the corresponding parameters in the page management associated with the current page according to the updated page parameters of the current page.
In one implementation, the first obtaining unit is further configured to perform:
Acquiring preset parameters corresponding to the preset scene and initial values of the preset parameters, initializing parameters in the created page manager, acquiring page parameters of the current page from the initialized parameters of the page manager, or,
And acquiring the page parameters and page parameter values in the current page, and initializing the parameters in the created page manager.
In one implementation, the first obtaining unit is further configured to perform:
And responding to an input instruction of the page parameters of the current page, updating the page parameters of the current page, and determining the value of the corresponding parameters in the page manager according to the updated page parameters of the current page.
In one implementation, the parameters in the current page include modifiable parameters and non-modifiable parameters, the apparatus further comprising:
The storage unit is configured to execute the preset component for writing the modifiable parameters and the values of each modifiable parameter into the current page after acquiring the page parameters of the current page;
The system comprises a page manager, a return unit, a parameter obtaining unit and a parameter modifying unit, wherein the page manager is used for obtaining the parameter modifying parameters from preset components of the current page, the return unit is used for executing an instruction for responding to return of the current page, returning the current page from any page, reading the non-modifiable parameters from the page manager, displaying the current page based on the non-modifiable parameters in the page manager and the modifiable parameters obtained from the preset components, and modifying the values of the corresponding parameters in the page manager according to the values of the modifiable parameters of the preset components.
In one implementation, the apparatus further comprises:
The system comprises a statistics unit, a key value pair generation unit and a page management unit, wherein the statistics unit is configured to generate a key value pair of any page after any page associated with the page manager is opened, add the key value pair of any page into the page manager, and delete the key value pair of any page from the page manager in response to a page closing instruction for the any page associated with the page manager.
In one implementation, the statistics unit is further configured to perform:
counting the number of key value pairs in the page manager;
and deleting the page manager in the condition that the number is zero.
In one implementation, the apparatus further comprises:
and an editing unit configured to execute a parameter expansion instruction in response to a page parameter for the current page, the page parameter being added in the page manager.
In view of the foregoing, in the technical solution provided in the embodiments of the present disclosure, when a page jumps, any target page after jumping may obtain a required target parameter from the page manager when the target page and the current page are associated with the same page manager, that is, the parameters in the page associated with the target page may be managed by the page manager, and reading and writing of all parameters from an intent component of a previous page do not need to be performed by each page when the page jumps, so that the operation is relatively convenient, and parameter omission and loss are not easy to occur.
The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.
FIG. 9 is a block diagram of an electronic device for page parameter acquisition, according to an example embodiment.
In an exemplary embodiment, a computer-readable storage medium is also provided, such as a memory, comprising instructions executable by a processor of an electronic device to perform the above-described method. Alternatively, the computer readable storage medium may be ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.
In an exemplary embodiment, a computer program product is also provided which, when run on a computer, causes the computer to implement the method of page parameter acquisition described above.
In view of the foregoing, in the technical solution provided in the embodiments of the present disclosure, when a page jumps, any target page after jumping may obtain a required target parameter from the page manager when the target page and the current page are associated with the same page manager, that is, the parameters in the page associated with the target page may be managed by the page manager, and reading and writing of all parameters from an intent component of a previous page do not need to be performed by each page when the page jumps, so that the operation is relatively convenient, and parameter omission and loss are not easy to occur.
Fig. 10 is a block diagram illustrating an apparatus 800 for page parameter acquisition, according to an example embodiment.
For example, apparatus 800 may be a mobile phone, computer, digital broadcast electronic device, messaging device, game console, tablet device, medical device, exercise device, personal digital assistant, or the like.
Referring to FIG. 10, the apparatus 800 may include one or more of a processing component 802, a memory 804, a power component 806, a multimedia component 808, an audio component 810, an input/output (I/O) interface 812, a sensor component 814, and a communication component 816.
The processing component 802 generally controls overall operation of the apparatus 800, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to perform all or part of the steps of the methods described above. Further, the processing component 802 can include one or more modules that facilitate interactions between the processing component 802 and other components. For example, the processing component 802 can include a multimedia module to facilitate interaction between the multimedia component 808 and the processing component 802.
The memory 804 is configured to store various types of data to support operations at the device 800. Examples of such data include instructions for any application or method operating on the device 800, contact data, phonebook data, messages, pictures, videos, and the like. The memory 804 may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.
Power supply component 807 provides power to the various components of device 800. Power supply component 807 can include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for device 800.
The multimedia component 808 includes a screen between the device 800 and the user that provides an output interface. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or slide action, but also the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front camera and/or a rear camera. The front camera and/or the rear camera may receive external multimedia data when the device 800 is in an operational mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have focal length and optical zoom capabilities.
The audio component 810 is configured to output and/or input audio signals. For example, the audio component 810 includes a Microphone (MIC) configured to receive external audio signals when the device 800 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may be further stored in the memory 804 or transmitted via the communication component 816. In some embodiments, audio component 810 further includes a speaker for outputting audio signals.
The I/O interface 812 provides an interface between the processing component 802 and peripheral interface modules, which may be a keyboard, click wheel, buttons, etc. These buttons may include, but are not limited to, a home button, a volume button, an activate button, and a lock button.
The sensor assembly 814 includes one or more sensors for providing status assessment of various aspects of the apparatus 800. For example, the sensor assembly 814 may detect an on/off state of the device 800, a relative positioning of the components, such as a display and keypad of the apparatus 800, the sensor assembly 814 may also detect a change in position of the apparatus 800 or one component of the apparatus 800, the presence or absence of user contact with the apparatus 800, an orientation or acceleration/deceleration of the apparatus 800, and a change in temperature of the apparatus 800. The sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an acceleration sensor, a gyroscopic sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 816 is configured to facilitate communication between the apparatus 800 and other devices, either in a wired or wireless manner. The device 800 may access a wireless network based on a communication standard, such as WiFi, an operator network (e.g., 2G, 3G, 4G, or 5G), or a combination thereof. In one exemplary embodiment, the communication component 816 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component 816 further includes a Near Field Communication (NFC) module to facilitate short range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.
In an exemplary embodiment, the apparatus 800 may be implemented by one or more Application Specific Integrated Circuits (ASICs), digital Signal Processors (DSPs), digital Signal Processing Devices (DSPDs), programmable Logic Devices (PLDs), field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic elements for executing the methods described in the first and second aspects.
In an exemplary embodiment, a non-transitory computer readable storage medium is also provided, such as memory 804 including instructions executable by processor 820 of apparatus 800 to perform the above-described method. Alternatively, for example, the storage medium may be a non-transitory computer-readable storage medium, which may be, for example, ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.
In an exemplary embodiment, there is also provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the page parameter acquisition method of any of the above embodiments.
In view of the foregoing, in the technical solution provided in the embodiments of the present disclosure, when a page jumps, any target page after jumping may obtain a required target parameter from the page manager when the target page and the current page are associated with the same page manager, that is, the parameters in the page associated with the target page may be managed by the page manager, and reading and writing of all parameters from an intent component of a previous page do not need to be performed by each page when the page jumps, so that the operation is relatively convenient, and parameter omission and loss are not easy to occur.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (19)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111358097.XA CN114116075B (en) | 2021-11-16 | 2021-11-16 | A method, device, electronic device and storage medium for obtaining page parameters |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111358097.XA CN114116075B (en) | 2021-11-16 | 2021-11-16 | A method, device, electronic device and storage medium for obtaining page parameters |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114116075A CN114116075A (en) | 2022-03-01 |
| CN114116075B true CN114116075B (en) | 2025-02-25 |
Family
ID=80396806
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111358097.XA Active CN114116075B (en) | 2021-11-16 | 2021-11-16 | A method, device, electronic device and storage medium for obtaining page parameters |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114116075B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105630461A (en) * | 2014-10-27 | 2016-06-01 | 航天信息股份有限公司 | Managing method of android application interface |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140325089A1 (en) * | 2013-04-28 | 2014-10-30 | Tencent Technology (Shenzhen) Company Limited | Method, terminal, server and system for page jump |
| CN104346158B (en) * | 2013-08-09 | 2017-11-21 | 华为终端（东莞）有限公司 | A kind of method and user equipment for handling the cascade page |
| CN110109665A (en) * | 2018-10-18 | 2019-08-09 | 神思旭辉医疗信息技术有限责任公司 | A kind of front end UI system and method based on container encapsulation |
| CN112380480B (en) * | 2020-12-02 | 2024-05-31 | 北京皮尔布莱尼软件有限公司 | Page jump method, computing device and storage medium |
| CN112711727B (en) * | 2020-12-30 | 2024-10-25 | 广州市诚毅科技软件开发有限公司 | Webpage skipping method and device of mobile terminal |
-
2021
- 2021-11-16 CN CN202111358097.XA patent/CN114116075B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105630461A (en) * | 2014-10-27 | 2016-06-01 | 航天信息股份有限公司 | Managing method of android application interface |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114116075A (en) | 2022-03-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106534562B (en) | File deletion method and device | |
| CN112632184A (en) | Data processing method and device, electronic equipment and storage medium | |
| CN110704030A (en) | Interface configuration information generation method and device, electronic equipment and storage medium | |
| CN107239351B (en) | Pasting method and device | |
| CN113778687B (en) | Memory allocation information processing method and device, electronic equipment and storage medium | |
| CN106708967B (en) | Page display method and device | |
| CN111538574B (en) | Task stack management method, device, terminal and storage medium | |
| CN113076504A (en) | Skeleton screen generation method, device, equipment and storage medium | |
| CN107463372B (en) | Data-driven page updating method and device | |
| CN108153488B (en) | Data self-adding method and device | |
| CN113010157A (en) | Code generation method and device | |
| CN114116075B (en) | A method, device, electronic device and storage medium for obtaining page parameters | |
| CN115203618B (en) | Page processing method and device, electronic equipment and storage medium | |
| CN110008135B (en) | Information processing method and device and electronic equipment | |
| CN113360708B (en) | Video playing method and device, electronic equipment and storage medium | |
| CN113391804B (en) | Page generation method and device, electronic equipment and storage medium | |
| CN111290882B (en) | Data file backup method, data file backup device and electronic equipment | |
| CN108021399B (en) | Note processing method, device and equipment and storage medium | |
| CN108762944B (en) | Processing method, device, equipment and medium of business system | |
| CN108427568B (en) | User interface updating method and device | |
| CN114531493B (en) | Request processing method and device, electronic equipment and storage medium | |
| CN113760425B (en) | Method, device and equipment for changing display mode of application program | |
| CN111104110A (en) | Global style sharing method, global style sharing device and electronic device | |
| CN114385572B (en) | Method and device for converting Java object list and DBF file | |
| CN114416085B (en) | Data processing method and device, electronic 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |