CN114356487A - Method and device for loading task bullet layer - Google Patents

Method and device for loading task bullet layer Download PDF

Info

Publication number
CN114356487A
CN114356487A CN202210017487.9A CN202210017487A CN114356487A CN 114356487 A CN114356487 A CN 114356487A CN 202210017487 A CN202210017487 A CN 202210017487A CN 114356487 A CN114356487 A CN 114356487A
Authority
CN
China
Prior art keywords
route
task
main
sub
layer
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202210017487.9A
Other languages
Chinese (zh)
Inventor
张敏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Jingdong Technology Holding Co Ltd
Original Assignee
Jingdong Technology Holding Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Jingdong Technology Holding Co Ltd filed Critical Jingdong Technology Holding Co Ltd
Priority to CN202210017487.9A priority Critical patent/CN114356487A/en
Publication of CN114356487A publication Critical patent/CN114356487A/en
Pending legal-status Critical Current

Links

Images

Landscapes

  • Information Transfer Between Computers (AREA)

Abstract

The invention discloses a method and a device for loading a task bullet layer, and relates to the technical field of computers. One embodiment of the method comprises: loading a main page of a project by using a main route of a route manager, wherein the main page is used for triggering and executing a preset task; after a main page of the project receives a task triggering instruction, a sub-route corresponding to the task in the route manager is called through the main route, and a bullet layer of the task is loaded through the sub-route to execute the task. The implementation method can realize the decoupling among the assemblies, does not need to maintain the interaction and communication of the parent-child assemblies, reduces the interaction complexity, simultaneously realizes the service logic decoupling, reduces the development complexity, and is convenient for subsequent extension and iterative maintenance.

Description

Method and device for loading task bullet layer
Technical Field
The invention relates to the technical field of computers, in particular to a method and a device for loading a task bullet layer.
Background
The pop-up layer effect is a relatively common interaction effect in the H5 activity, such as clicking pop-up activity rules, lottery results, and the like, and the use of the pop-up layer in the project can achieve relatively good user experience, and is also a relatively mainstream interaction scheme at present. The active bullet layer has the characteristics of individuation and strong interaction complexity, and currently, the H5 active bullet layer processing method uses bullet layer components, and the bullet layer components generally exist as sub-components and have parent-child relationship with project main business components. Taking a note taking machine project as an example, in the existing scheme, the note taking machine is packaged by an assembly to serve as a parent assembly, a task function is packaged into a bullet layer assembly to serve as a child assembly, and interaction and communication exist between the parent assembly and the child assembly.
In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art:
because the assemblies have parent-child relationship, interaction and communication of parent-child assemblies need to be maintained, interaction complexity is increased, and development complexity is increased due to service logic coupling, and subsequent iterative maintenance is not facilitated.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method and an apparatus for loading a task bullet layer, which can implement decoupling between components, do not need to maintain interaction and communication of parent and child components, reduce interaction complexity, implement service logic decoupling, reduce development complexity, and facilitate subsequent iterative maintenance.
To achieve the above object, according to an aspect of an embodiment of the present invention, there is provided a method of loading a task bullet layer.
A method of loading a mission shell, comprising: loading a main page of a project by using a main route of a route manager, wherein the main page is used for triggering and executing a preset task; after a main page of the project receives a task triggering instruction, a sub-route corresponding to the task in the route manager is called through the main route, and a bullet layer of the task is loaded through the sub-route to execute the task.
Optionally, before the loading the main page of the project by using the main route of the route manager, the method includes: presetting the main route and the sub-route, wherein the main route is used for loading a main page of the project by rendering a main component of the project, and the sub-route is used for loading a popup layer of the task by rendering a popup layer component of the task.
Optionally, the setting of the sub-route includes setting a positioning attribute and a hierarchy attribute of the sub-route, the positioning attribute is used for fixedly positioning the bullet layer relative to the window of the main page, and the hierarchy attribute is used for displaying the bullet layer on the uppermost layer of the page.
Optionally, the invoking of the sub-route corresponding to the task in the route manager by the main route includes: and calling a sub-route of the task through the main route according to the name attribute of the elastic layer component, wherein the value of the name attribute has a corresponding relation with the sub-route.
Optionally, the loading, by the sub-route, the bullet layer of the task includes: and simultaneously displaying the main page of the project and the pop-up layer page of the task, wherein the pop-up layer page is always positioned on the upper layer of the main page of the project before the pop-up layer page is closed.
According to another aspect of the embodiment of the invention, a device for loading a mission shell is provided.
An apparatus for loading a layer of mission projectiles, comprising: the main page loading module is used for loading a main page of a project by utilizing a main route of the route manager, and the main page is used for triggering and executing a preset task; and the task elastic layer loading module is used for calling a sub-route corresponding to the task in the route manager through the main route after the main page of the project receives a task triggering instruction, and loading the elastic layer of the task through the sub-route so as to execute the task.
Optionally, the system further includes a routing setting module, configured to: presetting the main route and the sub-route, wherein the main route is used for loading a main page of the project by rendering a main component of the project, and the sub-route is used for loading a popup layer of the task by rendering a popup layer component of the task.
Optionally, the route setting module is further configured to set a positioning attribute and a hierarchy attribute of the sub-route, where the positioning attribute is used to fixedly position the popup layer with respect to the window of the main page, and the hierarchy attribute is used to display the popup layer on the uppermost layer of the page.
Optionally, a sub-route of the task is invoked through the main route according to a name attribute of the missile layer component, and a corresponding relationship exists between a value of the name attribute and the sub-route.
Optionally, the task elastic layer loading module is further configured to: and simultaneously displaying the main page of the project and the pop-up layer page of the task, wherein the pop-up layer page is always positioned on the upper layer of the main page of the project before the pop-up layer page is closed.
According to yet another aspect of an embodiment of the present invention, an electronic device is provided.
An electronic device, comprising: one or more processors; the memory is used for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors are enabled to realize the method for loading the task bullet layer provided by the embodiment of the invention.
According to yet another aspect of an embodiment of the present invention, a computer-readable medium is provided.
A computer readable medium, on which a computer program is stored, the program, when executed by a processor, implementing a method for loading a task bullet layer as provided by an embodiment of the invention.
One embodiment of the above invention has the following advantages or benefits: loading a main page of a project by using a main route of a route manager, wherein the main page is used for triggering and executing a preset task; after a main page of the project receives a task triggering instruction, a sub-route corresponding to the task in the route manager is called through the main route, and a bullet layer of the task is loaded through the sub-route to execute the task. The decoupling between the assemblies can be realized, the interaction and the communication of parent-child assemblies do not need to be maintained, the interaction complexity is reduced, meanwhile, the service logic decoupling is also realized, the development complexity is reduced, and the subsequent extension and iterative maintenance are facilitated.
Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
FIG. 1 is a schematic diagram of the main steps of a method of loading a mission shell according to one embodiment of the invention;
FIG. 2 is a schematic main page view of a project according to one embodiment of the present invention;
FIG. 3 is a schematic illustration of a bullet layer of an item according to one embodiment of the present invention;
FIG. 4 is a schematic flow diagram of loading a mission shell layer according to one embodiment of the invention;
FIG. 5 is a schematic block diagram of the main components of an apparatus for loading a mission shell according to one embodiment of the present invention;
FIG. 6 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;
fig. 7 is a schematic block diagram of a computer system suitable for use in implementing a terminal device or server of an embodiment of the invention.
Detailed Description
Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
Fig. 1 is a schematic diagram of the main steps of a method for loading a mission shell according to one embodiment of the present invention.
As shown in fig. 1, the method for loading a task bullet layer according to an embodiment of the present invention mainly includes the following steps S101 to S102.
Step S101: loading a main page of a project by using a main route of a route manager, wherein the main page is used for triggering and executing a preset task;
step S102: after a main page of the project receives a task triggering instruction, a sub-route corresponding to the task in the route manager is called through the main route, and a bullet layer of the task is loaded through the sub-route to execute the task.
The project comprises one or more tasks, and the execution of the tasks can be triggered through the main page. Such as a cash dispenser project including a task of scoring coins, the task being presented to the user by the popup layer.
The main route and the sub-route are preset before the main page of the project is loaded by the main route of the route manager.
The main route is used for loading a main page of the project through a main component of the rendering project, and the sub route is used for loading a popup layer of the task through a popup layer component of the rendering task.
Setting the sub-route comprises setting a positioning attribute and a hierarchy attribute of the sub-route, wherein the positioning attribute is used for fixedly positioning the bullet layer relative to the window of the main page, and the hierarchy attribute is used for displaying the bullet layer on the uppermost layer of the page.
And calling the sub-route of the task through the main route according to the name attribute of the elastic layer component, wherein the value of the name attribute has a corresponding relation with the sub-route.
The main route and the sub-route are realized based on an vue-router route manager, vue is a set of progressive framework for constructing a user interface, router is a mechanism and is equivalent to a manager for managing the route, vue-router is a routing manager of Vue.
And loading the popup layer of the task through the sub-route, specifically, simultaneously displaying a main page of the project and a popup layer page of the task, wherein the popup layer page is always positioned on the upper layer of the main page of the project before the popup layer page is closed.
The embodiment of the invention uses the sub-route to process the bullet layer, realizes the decoupling of component interaction, reduces the interaction complexity, uses the sub-route to process the bullet layer and realizes the decoupling of service logic by means of vuex, reduces the development complexity and is convenient for subsequent maintenance.
The following describes the method for loading the task bullet layer according to the embodiment of the present invention in detail by taking the item of the money carrier as an example, in this example, the item is the money carrier main body.
The following route settings may be made: the main route HomePage, the rendering component is HomeComponent, namely the main body of the money extracting machine; the child routes TaskPage and the render component is TaskComponent, a task.
Setting the sub-route comprises setting a router-view (route view) of the sub-route, specifically adding a child-like to the router-view of the sub-route, setting a positioning attribute as fixed, and setting a hierarchy attribute zIndex as 999, thereby realizing the following bullet layer effects: and the window is fixedly positioned relative to the window and is displayed on the uppermost layer.
After a user clicks a button, a main page of the project receives a task triggering instruction of the project, the main route calls a sub-route through a route name attribute (name attribute), namely a rendering task component, and a task component is a popup component of the task in the embodiment of the invention. Fig. 2 and 3 are schematic page effects of an embodiment of the present invention, where fig. 2 is a schematic main page of a project according to an embodiment of the present invention, fig. 3 is a schematic elastic layer of the project according to an embodiment of the present invention, according to the examples of fig. 2 and 3, a business scenario in which a user performs a task and earns points can be implemented, when the task is closed, and at the same time, the points can be updated in vuex store (vue for storing data), the updating will be embodied at a first-page point presentation, and meanwhile, a goback of a history object using a browser can return to a main route, and the history object is a part of a window object and can be accessed through a window.
The process of loading a task popup layer according to an embodiment of the present invention is as shown in fig. 4, a main route is set, a main component is loaded through the main route, the main component is specifically a coin presenter UI (user interface) in this example, a user clicks a button on the coin presenter UI, a loading sub-component, namely, the task UI is triggered, when the task UI is loaded, a popup layer effect is simulated by specifically setting a sub-route router-view in advance to show the task UI popup layer, after a task operation is performed, the popup layer is closed, an integral update is performed, and then the main route is returned. For example, html is the main interface access route of the money carrier, html is the task interface access route, and the money carrier is loaded in a sub-route mode.
In the scheme in the prior art, a project home page component and a task component have a parent-child relationship, extra methods and variables are needed to maintain communication and interaction of the parent-child components, and the complexity of interaction is increased invisibly. In the embodiment of the invention, the bullet layer is processed by using the sub-route, the project home page component and the task component are completely decoupled, each component only pays attention to the component, and the parent-child relationship does not exist among the components, so that the interaction and the communication caused by the parent-child relationship are avoided, and the interaction complexity is greatly reduced. In addition, the scheme in the prior art can cause the intersection of business logic, the subsequent iterative maintenance is always restrained by each other, and the subsequent development is complicated and inefficient. The data are managed by using the sub-routing processing bullet layer and by means of vuex, so that the project and task functions of the money elevator can be completely decoupled logically, service logics are independent, and the development complexity is greatly reduced. The money-picking machine projects and the like have task functions, sign-in functions, friend assistance functions and the like, and the cross of a plurality of groups of parent-child assemblies and a plurality of service logics is realized through the prior art scheme, for example, the sign-in function needs to be developed to take account of the money-picking machine service logics, and the friend assistance needs to be developed to take account of the money-picking machine service logics, so that the problems of complexity and inefficiency are inevitably brought in the development process and the subsequent maintenance iteration.
Fig. 5 is a schematic block diagram of a main block of an apparatus for loading a mission shell according to an embodiment of the present invention.
As shown in fig. 5, the apparatus 500 for loading a mission bomb layer according to the embodiment of the present invention mainly includes: a main page loading module 501 and a task popup loading module 502.
A main page loading module 501, configured to load a main page of a project by using a main route of the route manager, where the main page is used to trigger execution of a preset task.
And the task elastic layer loading module 502 is configured to, after receiving a task triggering instruction on a main page of the project, invoke a sub-route corresponding to the task in the route manager through the main route, and load the elastic layer of the task through the sub-route to execute the task.
The apparatus 500 for loading a task bullet layer may further include a routing setting module for: the main route and the sub-route are preset.
The master route is used to load the master page of the project through the master component of the rendering project.
The sub-routes are used to load the bullet layer of the task through the bullet layer component of the rendering task.
The routing setting module is also used for setting the positioning attribute and the hierarchy attribute of the sub-routing, the positioning attribute is used for fixedly positioning the bullet layer relative to the window of the main page, and the hierarchy attribute is used for displaying the bullet layer on the uppermost layer of the page.
And calling the sub-route of the task through the main route according to the name attribute of the elastic layer component, wherein the value of the name attribute has a corresponding relation with the sub-route.
The primary and secondary routes are implemented based on an vue-router route manager.
The embodiment of the invention can simultaneously display the main page of the project and the pop-up page of the task, and the pop-up page is always positioned on the upper layer of the main page of the project before the pop-up page is closed.
In addition, the specific implementation content of the device for loading the task bullet layer in the embodiment of the present invention has been described in detail in the above method for loading the task bullet layer, so that repeated content is not described herein.
Fig. 6 shows an exemplary system architecture 600 to which the method for loading a task bullet layer or the apparatus for loading a task bullet layer according to the embodiments of the present invention can be applied.
As shown in fig. 6, the system architecture 600 may include terminal devices 601, 602, 603, a network 604, and a server 605. The network 604 serves to provide a medium for communication links between the terminal devices 601, 602, 603 and the server 605. Network 604 may include various types of connections, such as wire, wireless communication links, or fiber optic cables, to name a few.
A user may use the terminal devices 601, 602, 603 to interact with the server 605 via the network 604 to receive or send messages or the like. The terminal devices 601, 602, 603 may have installed thereon various communication client applications, such as shopping applications, web browser applications, search applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only).
The terminal devices 601, 602, 603 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 605 may be a server providing various services, such as a background management server (for example only) providing support for shopping websites browsed by users using the terminal devices 601, 602, 603. The backend management server may analyze and perform other processing on the received data such as the product information query request, and feed back a processing result (for example, target push information, product information — just an example) to the terminal device.
It should be noted that the method for loading a task bullet layer provided by the embodiment of the present invention is generally executed by the server 605, and accordingly, the device for loading a task bullet layer is generally disposed in the server 605.
It should be understood that the number of terminal devices, networks, and servers in fig. 6 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 7, shown is a block diagram of a computer system 700 suitable for use in implementing a terminal device or server of an embodiment of the present application. The terminal device or the server shown in fig. 7 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.
As shown in fig. 7, the computer system 700 includes a Central Processing Unit (CPU)701, which can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)702 or a program loaded from a storage section 708 into a Random Access Memory (RAM) 703. In the RAM 703, various programs and data necessary for the operation of the system 700 are also stored. The CPU 701, the ROM 702, and the RAM 703 are connected to each other via a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.
The following components are connected to the I/O interface 705: an input portion 706 including a keyboard, a mouse, and the like; an output section 707 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 708 including a hard disk and the like; and a communication section 709 including a network interface card such as a LAN card, a modem, or the like. The communication section 709 performs communication processing via a network such as the internet. A drive 710 is also connected to the I/O interface 705 as needed. A removable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 710 as necessary, so that a computer program read out therefrom is mounted into the storage section 708 as necessary.
In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 709, and/or installed from the removable medium 711. The computer program executes the above-described functions defined in the system of the present application when executed by the Central Processing Unit (CPU) 701.
It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In this application, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor comprises a main page loading module and a task popup loading module. Where the names of these modules do not in some cases constitute a limitation on the module itself, for example, the master page load module may also be described as a "module for loading the master page of a project with the master route of the route manager".
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to comprise: loading a main page of a project by using a main route of a route manager, wherein the main page is used for triggering and executing a preset task; after a main page of the project receives a task triggering instruction, a sub-route corresponding to the task in the route manager is called through the main route, and a bullet layer of the task is loaded through the sub-route to execute the task.
According to the technical scheme of the embodiment of the invention, the main page of the project is loaded by using the main route of the route manager, after the main page of the project receives the task triggering instruction, the sub-route corresponding to the task in the route manager is called up through the main route, and the bullet layer of the task is loaded through the sub-route to execute the task. The decoupling between the assemblies can be realized, the interaction and the communication of parent-child assemblies do not need to be maintained, the interaction complexity is reduced, meanwhile, the service logic decoupling is also realized, the development complexity is reduced, and the subsequent extension and iterative maintenance are facilitated.
The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims (10)

1. A method of loading a mission shell, comprising:
loading a main page of a project by using a main route of a route manager, wherein the main page is used for triggering and executing a preset task;
after a main page of the project receives a task triggering instruction, a sub-route corresponding to the task in the route manager is called through the main route, and a bullet layer of the task is loaded through the sub-route to execute the task.
2. The method of claim 1, wherein loading the main page of the item using the main route of the route manager is preceded by:
presetting the main route and the sub-route, wherein the main route is used for loading a main page of the project by rendering a main component of the project, and the sub-route is used for loading a popup layer of the task by rendering a popup layer component of the task.
3. The method of claim 2, wherein setting the sub-route comprises setting a positioning attribute and a hierarchy attribute of the sub-route, wherein the positioning attribute is used for fixedly positioning the bullet layer relative to the window of the main page, and the hierarchy attribute is used for displaying the bullet layer on the uppermost page.
4. The method according to claim 2, wherein evoking the sub-route corresponding to the task in the route manager through the main route comprises:
and calling a sub-route of the task through the main route according to the name attribute of the elastic layer component, wherein the value of the name attribute has a corresponding relation with the sub-route.
5. The method of claim 1, wherein loading the bullet layer of the task through the sub-route comprises:
and simultaneously displaying the main page of the project and the pop-up layer page of the task, wherein the pop-up layer page is always positioned on the upper layer of the main page of the project before the pop-up layer page is closed.
6. An apparatus for loading a layer of mission projectiles, comprising:
the main page loading module is used for loading a main page of a project by utilizing a main route of the route manager, and the main page is used for triggering and executing a preset task;
and the task elastic layer loading module is used for calling a sub-route corresponding to the task in the route manager through the main route after the main page of the project receives a task triggering instruction, and loading the elastic layer of the task through the sub-route so as to execute the task.
7. The apparatus of claim 6, further comprising a routing setup module to:
presetting the main route and the sub-route, wherein the main route is used for loading a main page of the project by rendering a main component of the project, and the sub-route is used for loading a popup layer of the task by rendering a popup layer component of the task.
8. The apparatus of claim 7, wherein the route setup module is further configured to set a positioning attribute and a hierarchy attribute of the sub-route, the positioning attribute is configured to fix a position of the bullet layer with respect to the window of the main page, and the hierarchy attribute is configured to display the bullet layer at an uppermost layer of the page.
9. An electronic device, comprising:
one or more processors;
a memory for storing one or more programs,
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method recited in any of claims 1-5.
10. A computer-readable medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-5.
CN202210017487.9A 2022-01-07 2022-01-07 Method and device for loading task bullet layer Pending CN114356487A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210017487.9A CN114356487A (en) 2022-01-07 2022-01-07 Method and device for loading task bullet layer

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210017487.9A CN114356487A (en) 2022-01-07 2022-01-07 Method and device for loading task bullet layer

Publications (1)

Publication Number Publication Date
CN114356487A true CN114356487A (en) 2022-04-15

Family

ID=81106720

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210017487.9A Pending CN114356487A (en) 2022-01-07 2022-01-07 Method and device for loading task bullet layer

Country Status (1)

Country Link
CN (1) CN114356487A (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111143729A (en) * 2019-12-11 2020-05-12 中国平安财产保险股份有限公司 Optimization method, device, equipment and storage medium based on single-page application
CN112486382A (en) * 2020-11-20 2021-03-12 完美世界(北京)软件科技发展有限公司 Interface logic execution method and device, electronic equipment and medium
CN112667326A (en) * 2019-09-30 2021-04-16 北京国双科技有限公司 Display method and device of popup page, computer equipment and storage medium
CN113076163A (en) * 2021-04-16 2021-07-06 北京京东拓先科技有限公司 Card rendering method and device
CN113190776A (en) * 2021-05-11 2021-07-30 上海哔哩哔哩科技有限公司 Popup window display method and system

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112667326A (en) * 2019-09-30 2021-04-16 北京国双科技有限公司 Display method and device of popup page, computer equipment and storage medium
CN111143729A (en) * 2019-12-11 2020-05-12 中国平安财产保险股份有限公司 Optimization method, device, equipment and storage medium based on single-page application
CN112486382A (en) * 2020-11-20 2021-03-12 完美世界(北京)软件科技发展有限公司 Interface logic execution method and device, electronic equipment and medium
CN113076163A (en) * 2021-04-16 2021-07-06 北京京东拓先科技有限公司 Card rendering method and device
CN113190776A (en) * 2021-05-11 2021-07-30 上海哔哩哔哩科技有限公司 Popup window display method and system

Similar Documents

Publication Publication Date Title
CN110795195B (en) Webpage rendering method and device, electronic equipment and storage medium
EP3822777A1 (en) Methods for processing mini program, and related devices
CN110473036B (en) Method and device for generating order number
CN113010827B (en) Page rendering method and device, electronic equipment and storage medium
US11706172B2 (en) Method and device for sending information
CN110706093A (en) Accounting processing method and device
CN111666293A (en) Database access method and device
CN111831461A (en) Method and device for processing business process
CN111881392A (en) Page display method and device
US11294651B2 (en) Code execution method, device, and rendering apparatus
CN114035865B (en) Method, device and equipment for starting small program and storage medium
CN113076153A (en) Interface calling method and device
CN113760488A (en) Method, device, equipment and computer readable medium for scheduling task
CN114443076A (en) Mirror image construction method, device, equipment and storage medium
CN114297278A (en) Method, system and device for quickly writing batch data
CN114500481A (en) Service request processing method, system and device
CN112819638A (en) Transaction weight judging method, device, equipment and computer readable medium
CN112596854A (en) Method and device for continuously integrating running of assembly line
WO2023169193A1 (en) Method and device for generating smart contract
EP3951687A2 (en) Business content output method, apparatus, storage medium and program product
CN114356487A (en) Method and device for loading task bullet layer
CN114090118A (en) Method, device and equipment for starting small program and storage medium
CN111966877B (en) Front-end service method, device, equipment and storage medium
CN107256244A (en) Data processing method and system
CN110909269B (en) Log reporting 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