CN114579201B - Execution method, device and equipment of window component - Google Patents
Execution method, device and equipment of window component Download PDFInfo
- Publication number
- CN114579201B CN114579201B CN202210196492.0A CN202210196492A CN114579201B CN 114579201 B CN114579201 B CN 114579201B CN 202210196492 A CN202210196492 A CN 202210196492A CN 114579201 B CN114579201 B CN 114579201B
- Authority
- CN
- China
- Prior art keywords
- foreground
- window component
- task stack
- stack
- component
- 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 46
- 238000005096 rolling process Methods 0.000 claims description 3
- 230000001419 dependent effect Effects 0.000 claims description 2
- 238000003860 storage Methods 0.000 description 16
- 238000010586 diagram Methods 0.000 description 14
- 230000006870 function Effects 0.000 description 9
- 238000004891 communication Methods 0.000 description 8
- 230000006872 improvement Effects 0.000 description 8
- 238000004590 computer program Methods 0.000 description 7
- 230000008569 process Effects 0.000 description 7
- 230000000694 effects Effects 0.000 description 6
- 238000012545 processing Methods 0.000 description 6
- 101100289200 Caenorhabditis elegans lite-1 gene Proteins 0.000 description 5
- 230000008859 change Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 5
- 230000009471 action Effects 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 3
- 238000013461 design Methods 0.000 description 3
- 238000012546 transfer Methods 0.000 description 3
- 238000004519 manufacturing process Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 239000007858 starting material Substances 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 229920001296 polysiloxane Polymers 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 239000010979 ruby Substances 0.000 description 1
- 229910001750 ruby Inorganic materials 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/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- 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
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- User Interface Of Digital Computer (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the specification discloses a method, a device and equipment for executing a window component. Receiving a starting instruction of a user to a window component; when the window component does not assign a class attribute, determining a foreground task stack in the plurality of task stacks, wherein the class attribute is used for representing stack attribute of the window component; determining whether the foreground task stack is an independent task stack; and when the foreground task stack is an independent task stack, starting to execute the window component from the foreground task stack so as to display an interface corresponding to the window component. Thus, the implementation can be launched onto the foreground stack in the multi-tasking stack no matter how the implementation is set inside the launched window component.
Description
Technical Field
The present disclosure relates to the field of internet technologies, and in particular, to a method, an apparatus, and a device for executing a window component.
Background
When a plurality of task stacks are started in an Android operating system, if a result transfer object of a window assembly (Activity) to be started is not empty, the Android system defaults to use the task stack of the starter to execute the window assembly and display a corresponding interface. This results in that when backing up, the user may be backing up into the main interface of the application, beyond the mind expectations of the user, reducing the user experience.
Based on this, there is a need for a more convenient implementation of the window assembly.
Disclosure of Invention
One or more embodiments of the present disclosure provide a method, an apparatus, a device, and a storage medium for executing a window component, so as to solve the following technical problems: there is a need for a more convenient implementation of the window assembly.
To solve the above technical problems, one or more embodiments of the present specification are implemented as follows:
In a first aspect, an execution method of a window component provided in an embodiment of the present disclosure is applied to an application for starting a plurality of task stacks, where the method includes: receiving a starting instruction of a user for a window component; when the window component does not assign a class attribute, determining a foreground task stack in the plurality of task stacks, wherein the class attribute is used for representing stack attribute of the window component; determining whether the foreground task stack is an independent task stack; and when the foreground task stack is an independent task stack, starting to execute the window component from the foreground task stack so as to display an interface corresponding to the window component.
In a second aspect, an embodiment of the present disclosure provides an execution apparatus of a window component, applied to an application for starting a plurality of task stacks, where the apparatus includes: the receiving module is used for receiving a starting instruction of a user to the window assembly; the determining module is used for determining a foreground task stack in the plurality of task stacks when the window component does not assign a class attribute, wherein the class attribute is used for representing stack attributes of the window component; the judging module is used for determining whether the foreground task stack is an independent task stack or not; and the execution module starts to execute the window component from the foreground task stack when the foreground task stack is an independent task stack so as to display an interface corresponding to the window component.
In a third aspect, embodiments of the present disclosure provide an electronic device, including:
At least one processor; and
A memory communicatively coupled to the at least one processor; wherein,
The memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of the first aspect.
In a fourth aspect, embodiments of the present description provide a non-volatile computer storage medium having stored thereon computer-executable instructions that, when read by a computer in the storage medium, cause one or more processors to perform the method as described in the first aspect.
The above-mentioned at least one technical solution adopted by one or more embodiments of the present disclosure can achieve the following beneficial effects: receiving a starting instruction of a user to a window component; when the window component does not assign a class attribute, determining a foreground task stack in the plurality of task stacks, wherein the class attribute is used for representing stack attribute of the window component; determining whether the foreground task stack is an independent task stack; and when the foreground task stack is an independent task stack, starting to execute the window component from the foreground task stack so as to display an interface corresponding to the window component. Therefore, no matter how the window assembly is arranged in the started window assembly, the window assembly can be started to the foreground stack in the multi-task stack, and when the user needs to fall back, the window assembly can sequentially return to an interface expected by the user according to the clicking sequence of the user, so that the user experience is improved.
Drawings
In order to more clearly illustrate the embodiments of the present description or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some of the embodiments described in the present description, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a diagram of the state change of a multi-task stack when a window component is started, which is related to the prior art;
FIG. 2 is a flowchart of a method for executing a window module according to an embodiment of the present disclosure;
FIG. 3 is a schematic diagram of a state change of a multi-tasking stack when a window component is launched in a payment application according to an embodiment of the present disclosure;
Fig. 4 is a schematic structural diagram of an execution device of a window assembly according to an embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.
Detailed Description
The embodiment of the specification provides a method, a device, equipment and a storage medium for executing a window component.
In order to make the technical solutions in the present specification better understood by those skilled in the art, the technical solutions in the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, shall fall within the scope of the present application.
In an Android system, due to the bottom layer design of an operating system, when a plurality of task stacks are started in the system at the same time, a resultTo object of a window component (Activity) to be started is not empty, and then the task stack of a starter can be used to start a new Activity regardless of stack attributes of related tasks.
For example, the user performs the following operations within the payment application: 1. a payment application is initiated. 2. An applet is launched that uses a separate stack within the payment application. 3. The payment code is initiated within the applet. 4. At the payment code page, the user clicks back.
At this point, the home page of the payment application will be returned. This is in fact beyond the user's expectations, as the user is in fact expecting to be desirous of returning to the home page of the applet.
As shown in fig. 1, fig. 1 is a schematic diagram of state change of a multi-task stack when a window component is started in the prior art. In steps 1 and 2 in the foregoing procedure, the window component corresponding to the applet is in the independent task stack lite1 (current foreground task stack), and the two window components of the payment code and payment application front page are in the main task stack main (current background task stack).
Due to the bottom design of the android system, after the window component of the payment code is started in the step 3, the front and back task stacks are exchanged once (main goes to the front stage and lite1 goes to the back stage), which results in returning to the payment application home page corresponding to the main task stack main when the step 4 returns. Based on this, the embodiments of the present disclosure provide a more convenient implementation scheme of the window component, so as to improve the user experience.
As shown in fig. 2, fig. 2 is a flowchart of a method for executing a window component according to an embodiment of the present disclosure, which is applied to an application for starting a plurality of task stacks, and includes the following steps:
s201: and receiving a starting instruction of a user for the window assembly.
In the present embodiment, each window component (Activity) within an application needs to be listed in advance and stack properties of the associated task stack are declared.
For example, a window component declared as a different task stack may launch onto a different task stack by declaring the task stack to which the window component belongs (i.e., declaring a class attribute of the window component) by the TASKAFFINITY attribute (i.e., class attribute) of the window component within AndroidManifest. The window components with different task stack names are supported to be started simultaneously in the same application.
When the application supports the multi-task stack, a user can generate a starting instruction for the window component through clicking, sliding, touching and other operations in the application.
S203, when the window component does not assign the class attribute, determining a foreground task stack in the plurality of task stacks, wherein the class attribute is used for representing the stack attribute of the window component.
As previously described, the window component may be launched by pre-declaring its class properties, and thus, when launched, by the task stack to which its class properties correspond. In practical applications, however, there will be some window components that will not be declared class attributes in advance. For example, for a payment code/paycode in a payment application, its class attributes may not typically be declared in advance in order to be satisfied that may be invoked by various applets within the application.
At this time, corresponding interfaces can be used to determine the foreground stack and the background stack in the application. Specifically, the foreground task stack may be a stack where an application that is currently in the foreground and running, visible, and capable of interacting with a user is located. The background task stack may be currently in the stack of an application in the background that is not visible nor interactable with the user.
For example, when the applet is opened in the payment application, at this time, the task stack where the applet is located is a foreground stack, and the task stack where the application is located is a background task stack. Furthermore, when the user opens the payment code in the applet, the task stack where the payment code is located is a foreground stack, and at this time, the stacks corresponding to the applet and the payment application are background task stacks.
For another example, when the communication application is in a chat interface with any friend, the task stack of the communication application is a foreground task stack and the background task stack is empty. When clicking on a webpage link in the chat content of the friend, the communication application opens the webpage with a built-in browser, and then can click on the webpage to open, so that the webpage can be opened and browsed by a third-party browser. At this time, the display interface jumps from the communication application to the third-party browser, and the task stack of the third-party browser is a foreground task stack and the task stack of the communication application is a background task stack. When the user clicks the return button, the window component of the third-party browser is popped off, the display interface returns to the communication application from the third-party browser, at the moment, the task stack of the communication application becomes a foreground task stack, and a background task stack is empty.
S205, determining whether the foreground task stack is an independent task stack.
Specifically, the attribute values of the activities of the independent stack and the dependent stack are different. Thus, the current application process foreground task stack may be obtained for the management interface activitymanaager. Whether the Activity attribute value of the independent stack is detected or not can be detected through the related attribute value (for example, baseActivity attribute) of the returned object through the management interface.
S207, when the foreground task stack is an independent task stack, starting to execute the window component from the foreground task stack so as to display an interface corresponding to the window component.
By executing the window component in the foreground task stack, the switching of the foreground and background task stacks does not occur after the window component is started, and the page for starting the window component can be naturally returned when the user returns.
Receiving a starting instruction of a user to a window component; when the window component does not assign a class attribute, determining a foreground task stack in the plurality of task stacks, wherein the class attribute is used for representing stack attribute of the window component; determining whether the foreground task stack is an independent task stack; and when the foreground task stack is an independent task stack, starting to execute the window component from the foreground task stack so as to display an interface corresponding to the window component. Therefore, no matter how the window assembly is arranged in the started window assembly, the window assembly can be started to the foreground stack in the multi-task stack, and when the user needs to fall back, the window assembly can sequentially return to an interface expected by the user according to the clicking sequence of the user, so that the user experience is improved.
In one embodiment, when the foreground task stack is a non-independent task stack, acquiring a start file corresponding to the window component; and executing the starting file corresponding to the window component. When the foreground task stack is an independent task stack, the page corresponding to the foreground task stack at the moment is not a focus page expected by a user, so that a window component does not need to be started and executed in the foreground task stack.
In one embodiment, when the execution of the window component is initiated from the foreground task stack, the execution may be performed in the following manner: determining a foreground component in a foreground task stack; and executing the window component from the foreground component.
In particular, multiple window components may also exist simultaneously in one foreground task stack or background task stack. When a foreground task stack contains at least 2 window components, the foreground component is the window component positioned at the top of the stack in the foreground task stack; when only one window component is included in the foreground task stack, then that window component may be determined directly as the foreground component.
For example, assume that in a payment application there are a total of A, B, C, D window components, where window component C is the primary task, further window component A, B has a start mode (launchMode) of standard and window component C, D has a start mode of SINGLETASK, and the class attribute (TASKAFFINITY) of window component C, D is set to a string (say lite 1) that is different from the package name of the application. This ensures that A, B is in the task stack named package name lite1 and C, D is in a different task stack.
If the application is opened at this time, first, C is started, and then window components D, A, B are opened sequentially, that is, the order in which each window component is started is C- > D- > a- > B. Then, at this time, the foreground task stack lite1 is respectively two window components A, B from the bottom to the top, and the background task stack is respectively two window components C, D from the bottom to the top.
At this time, the window component B is the foreground component in the foreground task stack. If a foreground task stack needs to be called to start a window component E, the window component E is actually proxy-executed by a foreground component (i.e., window component B) located at the top of the stack in the foreground task stack. By the method, the window component E can be kept at the top of a foreground task stack when being executed by the agent, so that when a user needs to fall back, the window component E can be kept to fall back to a fall-back interface expected by the user when falling back in sequence.
In one embodiment, for proxy execution of the window component from the foreground component, the specific manner may be: and acquiring an intention message file, wherein the intention message file is used for indicating to call and execute a starting file corresponding to the window component. Sending the intent message file to the foreground component; the foreground component invokes execution of the startup file based on the intent message file.
In the present embodiment, the intent message file may be an intent file (or may also be referred to as an intent object) that passes messages between components. The Intint file may be pre-generated based on the window component to be executed and invoked when needed.
The Intent file may include information encapsulated therein such as: component name (ComponentName), action (Action), category (Category), data (Data), attachment information (Extra), flags (Flag), and the like.
Wherein the component name specifies the component to be accessed; the actions indicate what operations are performed and the type is used to characterize the type of window component to be performed; the data is used to filter components that meet the conditions, and to do some simple data transfer, including such things as data type, uniform resource identifier (Uniform Resource Identifier, or URI), etc., which in fact indicates the address of the intent file; the attachment information is used to transfer parameters for a calling party (i.e., foreground component) and to obtain parameters for a called party (i.e., window component to be started), etc.
And completing message transmission between a foreground component and the window component to be started through the intention message file, so that the proxy executes the call to execute the starting file on the basis of the intention message file on the foreground component, and the window component is placed on the foreground component in the foreground stack. In fact, after execution is completed, the foreground component in the foreground stack becomes the window component.
In one embodiment, the method further includes receiving a rollback instruction from a user, and rolling back from an interface window corresponding to the window component to an interface corresponding to the foreground task stack. Since the foreground component in the foreground stack is already the window component at this time, the window component will be rolled back in sequence when rolling back, and no switching between the foreground task stack and the background task stack will occur, at this time, the window component can be naturally returned to the interface for starting the window component when the user returns.
In order to make the examples of the present specification more clear, a specific embodiment will be described below.
It is assumed that in a payment application, the user initiates the payment application and initiates the applet interface in the payment application. At this time, the applet is a foreground task stack, its class attribute is pre-designated lite1, and the home page of the payment application is invisible to the user, i.e. becomes a background task stack, and its class attribute is pre-designated main.
When the user initiates a payment code or a collection code in the applet interface, at this point, the class attribute is not specified because the initiation mode of the payment code is singletask. Its class attribute will be considered as the class attribute of the payment application (to main). At this time, if the payment code is directly started, as shown in fig. 1, the home page of the payment application is switched to the foreground task stack.
After the scheme of the application is adopted, the switching of the foreground and background task stacks can not occur. As shown in fig. 3. Fig. 3 is a schematic diagram of a state change of a multi-task stack when a window component is started in a payment application according to an embodiment of the present disclosure.
The system first determines that a foreground component in the foreground stack is an applet, and then sends an intent message file to the applet component, thereby executing a window component of the payment code over the applet component. In this case, the foreground stack includes two components, i.e., a payment code and an applet interface, and after the payment code is started, the payment code becomes the foreground component.
When the user rolls back, namely, the user rolls back sequentially from top to bottom in the foreground task stack, the user can roll back to the interface of the applet (namely, the interface of the payment code started by the user), so that the user's expectations are met, and the user's operation experience in the applet of the payment application is improved.
Based on the same thought, one or more embodiments of the present disclosure further provide apparatuses and devices corresponding to the above method, as shown in fig. 4 and fig. 5.
In a second aspect, as shown in fig. 4, fig. 4 is a schematic structural diagram of an execution device of a window assembly provided in an embodiment of the present disclosure, where the execution device is applied to an application for starting a plurality of task stacks, and the device includes:
The receiving module 401 receives a starting instruction of a user for the window assembly;
a determining module 403, configured to determine a foreground task stack of the plurality of task stacks when the window component does not specify a class attribute, where the class attribute is used to characterize a stack attribute of the window component;
a judging module 405, configured to determine whether the foreground task stack is an independent task stack;
and the execution module 407 is used for starting the execution of the window component from the foreground task stack when the foreground task stack is an independent task stack so as to display an interface corresponding to the window component.
Optionally, the executing module 407 obtains a start file corresponding to the window component when the foreground task stack is an independent task stack; and executing the starting file corresponding to the window component.
Optionally, the execution module 407 determines a foreground component in the foreground task stack to which the foreground component belongs; and executing the window component from the foreground component.
Optionally, the executing module 407 obtains an intention message file, where the intention message file is used to instruct to invoke and execute a start file corresponding to the window component; sending the intent message file to the foreground component; the foreground component invokes execution of the startup file based on the intent message file.
Optionally, the receiving module 401 receives a rollback instruction of the user, and rolls back from the interface window corresponding to the window component to the interface corresponding to the foreground task stack.
Optionally, in the device, the interface corresponding to the window component includes an interface for displaying a payment code or a collection code, and the interface corresponding to the foreground task stack includes an applet interface in the application.
In a third aspect, as shown in fig. 5, fig. 5 is a schematic structural diagram of an electronic device provided in one or more embodiments of the present disclosure, where the device includes:
At least one processor; and
A memory communicatively coupled to the at least one processor; wherein,
The memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of the first aspect.
Based on the same idea, in a fourth aspect, one or more embodiments of the present disclosure further provide a non-volatile computer storage medium corresponding to the above method, where computer executable instructions are stored, and when the computer reads the computer executable instructions in the storage medium, the instructions cause one or more processors to perform the method as described in the first aspect.
In the 90 s of the 20 th century, improvements to one technology could clearly be distinguished as improvements in hardware (e.g., improvements to circuit structures such as diodes, transistors, switches, etc.) or software (improvements to the process flow). However, with the development of technology, many improvements of the current method flows can be regarded as direct improvements of hardware circuit structures. Designers almost always obtain corresponding hardware circuit structures by programming improved method flows into hardware circuits. Therefore, an improvement of a method flow cannot be said to be realized by a hardware entity module. For example, a programmable logic device (Programmable Logic Device, PLD) (e.g., field programmable gate array (Field Programmable GATE ARRAY, FPGA)) is an integrated circuit whose logic functions are determined by user programming of the device. A designer programs to "integrate" a digital system onto a PLD without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Moreover, nowadays, instead of manually manufacturing integrated circuit chips, such programming is mostly implemented with "logic compiler (logic compiler)" software, which is similar to the software compiler used in program development and writing, and the original code before being compiled is also written in a specific programming language, which is called hardware description language (Hardware Description Language, HDL), but HDL is not just one, but a plurality of kinds, such as ABEL(Advanced Boolean Expression Language)、AHDL(Altera Hardware Description Language)、Confluence、CUPL(Cornell University Programming Language)、HDCal、JHDL(Java Hardware Description Language)、Lava、Lola、MyHDL、PALASM、RHDL(Ruby Hardware Description Language), and VHDL (Very-High-SPEED INTEGRATED Circuit Hardware Description Language) and Verilog are currently most commonly used. It will also be apparent to those skilled in the art that a hardware circuit implementing the logic method flow can be readily obtained by merely slightly programming the method flow into an integrated circuit using several of the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, application SPECIFIC INTEGRATED Circuits (ASICs), programmable logic controllers, and embedded microcontrollers, examples of controllers include, but are not limited to, the following microcontrollers: ARC625D, atmel AT91SAM, microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic of the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller in a pure computer readable program code, it is well possible to implement the same functionality by logically programming the method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers, etc. Such a controller may thus be regarded as a kind of hardware component, and means for performing various functions included therein may also be regarded as structures within the hardware component. Or even means for achieving the various functions may be regarded as either software modules implementing the methods or structures within hardware components.
The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. One typical implementation is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being functionally divided into various units, respectively. Of course, the functions of each element may be implemented in one or more software and/or hardware elements when implemented in the present specification.
It will be appreciated by those skilled in the art that the present description may be provided as a method, system, or computer program product. Accordingly, the present specification embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present description embodiments may take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
The present description is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the specification. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations 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.
In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
The description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for apparatus, devices, non-volatile computer storage medium embodiments, the description is relatively simple, as it is substantially similar to method embodiments, with reference to the section of the method embodiments being relevant.
The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
The foregoing is merely one or more embodiments of the present description and is not intended to limit the present description. Various modifications and alterations to one or more embodiments of this description will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, or the like, which is within the spirit and principles of one or more embodiments of the present description, is intended to be included within the scope of the claims of the present description.
Claims (9)
1. An execution method of a window component, applied to an application for starting a plurality of task stacks, comprises the following steps:
receiving a starting instruction of a user for a window component;
when the window component does not assign a class attribute, determining a foreground task stack in the plurality of task stacks, wherein the class attribute is used for representing stack attribute of the window component;
determining whether the foreground task stack is an independent task stack;
when the foreground task stack is an independent task stack, starting to execute the window component from the foreground task stack so as to display an interface corresponding to the window component;
Wherein, starting execution of the window component from the foreground task stack comprises: determining a foreground component in a foreground task stack; acquiring an intention message file, wherein the intention message file is used for indicating to call and execute a starting file corresponding to the window component; sending the intent message file to the foreground component; the foreground component invokes execution of the startup file based on the intent message file.
2. The method of claim 1, further comprising:
when the foreground task stack is an independent task stack, acquiring a starting file corresponding to the window component;
and executing the starting file corresponding to the window component.
3. The method of claim 1, further comprising:
And receiving a rollback instruction of a user, and rolling back to an interface corresponding to the foreground task stack from an interface window corresponding to the window component.
4. The method of claim 3, wherein the interface corresponding to the window component comprises an interface that presents a payment code or a collection code, and the interface corresponding to the foreground task stack comprises an applet interface in an application.
5. An execution apparatus of a window component, applied to an application that starts a plurality of task stacks, the apparatus comprising:
the receiving module is used for receiving a starting instruction of a user to the window assembly;
the determining module is used for determining a foreground task stack in the plurality of task stacks when the window component does not assign a class attribute, wherein the class attribute is used for representing stack attributes of the window component;
The judging module is used for determining whether the foreground task stack is an independent task stack or not;
The execution module starts to execute the window component from the foreground task stack when the foreground task stack is an independent task stack so as to display an interface corresponding to the window component;
The execution module determines foreground components in a foreground task stack; acquiring an intention message file, wherein the intention message file is used for indicating to call and execute a starting file corresponding to the window component; sending the intent message file to the foreground component; the foreground component invokes execution of the startup file based on the intent message file.
6. The device of claim 5, wherein the execution module obtains a start file corresponding to the window component when the foreground task stack is a dependent task stack; and executing the starting file corresponding to the window component.
7. The apparatus of claim 5, wherein the receiving module receives a rollback instruction from a user, and rollbacks from an interface window corresponding to the window component to an interface corresponding to the foreground task stack.
8. The apparatus of claim 7, wherein the interface corresponding to the window component comprises an interface that exposes a payment code or a collection code, and the interface corresponding to the foreground task stack comprises an applet interface in an application.
9. An electronic device, comprising:
At least one processor; and
A memory communicatively coupled to the at least one processor; wherein,
The memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210196492.0A CN114579201B (en) | 2022-03-01 | 2022-03-01 | Execution method, device and equipment of window component |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210196492.0A CN114579201B (en) | 2022-03-01 | 2022-03-01 | Execution method, device and equipment of window component |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114579201A CN114579201A (en) | 2022-06-03 |
| CN114579201B true CN114579201B (en) | 2024-05-31 |
Family
ID=81777048
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210196492.0A Active CN114579201B (en) | 2022-03-01 | 2022-03-01 | Execution method, device and equipment of window component |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114579201B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102685729A (en) * | 2011-02-14 | 2012-09-19 | 微软公司 | Background transfer service for applications on mobile devices |
| WO2016146056A1 (en) * | 2015-03-19 | 2016-09-22 | 阿里巴巴集团控股有限公司 | Page switching method and device |
| CN108184021A (en) * | 2017-12-28 | 2018-06-19 | 维沃移动通信有限公司 | A kind of application operation condition control method and mobile terminal |
| CN113805962A (en) * | 2021-08-31 | 2021-12-17 | 北京百度网讯科技有限公司 | Application page display method and device and electronic equipment |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10620772B2 (en) * | 2015-07-29 | 2020-04-14 | Microsoft Technology Licensing, Llc | Universal back navigation for multiple windows |
-
2022
- 2022-03-01 CN CN202210196492.0A patent/CN114579201B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102685729A (en) * | 2011-02-14 | 2012-09-19 | 微软公司 | Background transfer service for applications on mobile devices |
| WO2016146056A1 (en) * | 2015-03-19 | 2016-09-22 | 阿里巴巴集团控股有限公司 | Page switching method and device |
| CN108184021A (en) * | 2017-12-28 | 2018-06-19 | 维沃移动通信有限公司 | A kind of application operation condition control method and mobile terminal |
| CN113805962A (en) * | 2021-08-31 | 2021-12-17 | 北京百度网讯科技有限公司 | Application page display method and device and electronic equipment |
Non-Patent Citations (1)
| Title |
|---|
| Android应用交互及任务栈处理;陆志平;胡晨骏;;计算机系统应用;20170615(06);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114579201A (en) | 2022-06-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107463367B (en) | Transition animation realization method and device | |
| CN108549562A (en) | A kind of method and device of image load | |
| CN108924029B (en) | Method and device for sending customer service data | |
| CN111835864B (en) | Method and system for starting application | |
| CN108628688B (en) | Message processing method, device and equipment | |
| CN111639278B (en) | Webpage loading method and device | |
| CN109947643B (en) | A/B test-based experimental scheme configuration method, device and equipment | |
| CN112000329B (en) | Data display method, device, equipment and medium | |
| CN111768303A (en) | Transaction processing method, device, equipment and system | |
| CN117093352B (en) | Template-based computing cluster job scheduling system, method and device | |
| CN114547024A (en) | SQL statement risk detection method, device, equipment and medium | |
| CN110262749B (en) | Webpage operation method, device, container, equipment and medium | |
| CN112015569A (en) | Message reminding processing method and device | |
| CN118426988A (en) | Message reminding processing method and device | |
| CN114115016B (en) | Data processing method, device, equipment and medium | |
| CN114579201B (en) | Execution method, device and equipment of window component | |
| CN111008044A (en) | Application program recovery method and system and electronic equipment | |
| CN111459573A (en) | Method and device for starting intelligent contract execution environment | |
| CN108769152B (en) | Service refresh policy registration method, service refresh request method, device and equipment | |
| CN112579938B (en) | Page loading method and device, storage medium and electronic equipment | |
| CN108628615A (en) | A kind of discarded code detection method, device and equipment | |
| CN115391185A (en) | Applet pressure testing method, device and equipment | |
| CN111880922A (en) | Processing method, device and equipment for concurrent tasks | |
| CN112583733A (en) | Interface traffic shaping method and device, storage medium and electronic equipment | |
| CN112306710A (en) | Service processing system, interface calling method and device |
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 |