CN111949351B - Page rendering method, device, equipment and computer readable storage medium - Google Patents
Page rendering method, device, equipment and computer readable storage medium Download PDFInfo
- Publication number
- CN111949351B CN111949351B CN202010809562.6A CN202010809562A CN111949351B CN 111949351 B CN111949351 B CN 111949351B CN 202010809562 A CN202010809562 A CN 202010809562A CN 111949351 B CN111949351 B CN 111949351B
- Authority
- CN
- China
- Prior art keywords
- route
- page
- sub
- routing
- matched
- 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
Images
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/451—Execution arrangements for user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/957—Browsing optimisation, e.g. caching or content distillation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
-
- 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
- G06F9/4451—User profiles; Roaming
-
- 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/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
-
- 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)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Human Computer Interaction (AREA)
- Information Transfer Between Computers (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention relates to the technical field of financial science and technology, and discloses a page rendering method, a page rendering device, page rendering equipment and a computer-readable storage medium. The page rendering method comprises the following steps: when a browser page jump request is received, acquiring a page address to be jumped according to the browser page jump request; obtaining a route matched with the address of the page to be jumped from a pre-generated route configuration file, and obtaining a matched route path of the matched route; scoring each matched route according to the matched route path, and determining a target route according to a scoring result; and determining a target component corresponding to the target route according to the route configuration file, and loading the target component to render and obtain a target page corresponding to the address of the page to be skipped. The invention can solve the problem that the route matching scheme is inaccurate in the front-end rendering process.
Description
Technical Field
The present invention relates to the field of financial technology (Fintech), and in particular, to a page rendering method, apparatus, device, and computer-readable storage medium.
Background
With the development of computer technology, more and more technologies are applied in the financial field, and the traditional financial industry is gradually changing to financial technology (Fintech), but higher requirements are also put forward on the technologies due to the requirements of the financial industry on safety and real-time performance.
The existing page rendering mode comprises server rendering and client rendering, and is respectively suitable for different development and business scenes. In the process of page rendering, a browser requests a server, the server is firstly matched with a corresponding route, a processor corresponding to the route is executed, service logic is processed in the processor, and then HTML (Hypertext Mark-up Language) file content is generated according to data and a rendering template and returned to the browser. In this regard, the target generally performs page rendering by means of client rendering.
Client rendering, also known as front-end rendering, may be implemented based on a read Router (a routing solution) application. In the page rendering process, route matching is carried out by comparing path attributes of Route components with browser page addresses, and if a plurality of routes are matched by page paths, the reach Router selects rendering the first Route. However, this matching is not reasonable. For example, the user has defined both a route/order/: order Id (order detail page) and/order/list (order list page) that can be matched to the order detail page and the order list page when the user accesses/order/list. At this time, the read Router will render the first matched order detail page, but it is more reasonable to actually render the order list page. Therefore, the existing route matching scheme is not accurate.
Disclosure of Invention
The invention mainly aims to provide a page rendering method, a page rendering device, page rendering equipment and a computer readable storage medium, and aims to solve the problem that a routing matching scheme is inaccurate in a front-end rendering process.
In order to achieve the above object, the present invention provides a page rendering method, including:
when a browser page jump request is received, acquiring a page address to be jumped according to the browser page jump request;
acquiring a route matched with the address of the page to be jumped from a pre-generated route configuration file, and acquiring a matching route path of the matched route;
scoring each matched route according to the matched route path, and determining a target route according to a scoring result;
and determining a target component corresponding to the target route according to the route configuration file, and loading the target component to render and obtain a target page corresponding to the address of the page to be skipped.
Optionally, the step of scoring each matched route according to the matched route path and determining a target route according to a scoring result includes:
splitting the matched routing path to obtain the number of sub-items of each matched route, and calculating according to the number of the sub-items and a first preset score to obtain a first score;
acquiring the sub-item type of each sub-item of each matched route, and determining a second score of each sub-item of each matched route according to the sub-item type;
adding the first score and the second score to obtain the score of each matched route;
and determining the route corresponding to the maximum value in the scores as a target route.
Optionally, the step of obtaining the sub-item type of each sub-item of each matched route, and determining the second score of each sub-item of each matched route according to the sub-item type includes:
detecting whether each sub item of each matched route comprises a preset special character or not to obtain a first detection result;
detecting whether each sub item of each matched route is a root end or not to obtain a second detection result;
determining the sub-item type of each sub-item according to the first detection result and the second detection result;
and determining a second score of each sub-item of each matched route according to the mapping relation between the sub-item type and the preset sub-item type and the scores.
Optionally, before the step of obtaining the route matched with the address of the page to be skipped from the pre-generated route configuration file and obtaining the matching route path of the matched route, the method further includes:
when a route setting request is received, displaying a page directory setting interface according to the route setting request;
when an input completion instruction triggered by a user based on the page directory setting interface is received, acquiring a page directory input by the user;
traversing the page directory, and detecting whether a sub-routing file exists in a folder corresponding to the currently traversed page directory;
if the sub-routing file exists, the file name of the currently traversed sub-routing file is obtained, the routing type is determined according to the file name, and second routing data are generated according to the routing type and the file name;
obtaining a layout file corresponding to the sub-routing file and first routing data thereof, and updating the first routing data according to the second routing data;
and generating the routing configuration file according to the updated first routing data and the second routing data.
Optionally, the step of obtaining the layout file corresponding to the sub-routing file and the first routing data thereof, and updating the first routing data according to the second routing data includes:
detecting whether a layout file exists in a folder corresponding to a currently traversed page directory;
if the layout file exists in the folder corresponding to the currently traversed page directory, determining the layout file in the folder corresponding to the currently traversed page directory as the layout route corresponding to the sub-route file;
if the folder corresponding to the currently traversed page directory does not have a layout file, detecting whether a corresponding layout route exists in a superior directory of the currently traversed page directory;
if the superior directory of the currently traversed page directory has a corresponding layout route, determining the layout route in the superior directory of the currently traversed page directory as the layout route corresponding to the sub-routing file;
and acquiring first routing data of the layout route, and updating the first routing data of the corresponding layout route according to the second routing data.
Optionally, the step of generating the routing configuration file according to the updated first routing data and the second routing data includes:
executing a preset template on the updated first routing data and the second routing data to generate a dependency induction logic of each route;
writing the dependence introduction logic into a preset routing configuration template to obtain an initial routing configuration file;
and compiling the initial routing configuration file to obtain the routing configuration file.
Optionally, the step of determining a target component corresponding to the target route according to the route configuration file, and loading the target component to render a target page corresponding to the address of the page to be skipped includes:
acquiring a current routing path corresponding to a current page address, and acquiring a target routing path of the target route;
splitting the current routing path to obtain a first subitem array, and splitting the target routing path to obtain a second subitem array;
comparing the first sub-item array with the second sub-item array to obtain a public routing path and a non-public routing path, and determining a target component according to the non-public routing path;
and determining a common routing component according to the common routing path, unloading components except the common routing component in the current routing component corresponding to the current routing path, and loading the target component.
In addition, to achieve the above object, the present invention further provides a page rendering apparatus, including:
the system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring a page address to be jumped according to a browser page jump request when the browser page jump request is received;
the second acquisition module is used for acquiring a route matched with the address of the page to be jumped from a pre-generated route configuration file and acquiring a matched route path of the matched route;
the route grading module is used for grading each matched route according to the matched route path and determining a target route according to a grading result;
and the page rendering module is used for determining a target component corresponding to the target route according to the route configuration file, and loading the target component to render and obtain a target page corresponding to the address of the page to be skipped.
In addition, to achieve the above object, the present invention also provides a page rendering apparatus, including: a memory, a processor and a page rendering program stored on the memory and executable on the processor, the page rendering program, when executed by the processor, implementing the steps of the page rendering method as described above.
In addition, to achieve the above object, the present invention also provides a computer readable storage medium having stored thereon a page rendering program, which when executed by a processor, implements the steps of the page rendering method as described above.
The invention provides a page rendering method, a page rendering device, page rendering equipment and a computer readable storage medium, wherein when a browser page skipping request is received, a page address to be skipped is obtained according to the browser page skipping request; then, obtaining a route matched with the address of the page to be jumped from a pre-generated route configuration file, and obtaining a matched route path of the matched route; scoring each matched route according to the matched route path, and determining a target route according to a scoring result; and then determining a target component corresponding to the target route according to the route configuration file, and loading the target component to render and obtain a target page corresponding to the address of the page to be skipped. According to the method, the matched route is obtained through the pre-generated route configuration file, then the matched route is scored, the target route is determined, the target component corresponding to the target route is further loaded, and the page rendering is achieved.
Drawings
FIG. 1 is a schematic diagram of an apparatus architecture of a hardware operating environment according to an embodiment of the present invention;
FIG. 2 is a schematic flowchart illustrating a page rendering method according to a first embodiment of the present invention;
FIG. 3 is a functional block diagram of a page rendering apparatus according to a first embodiment of the present invention.
The implementation, functional features and advantages of the present invention will be further described with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Referring to fig. 1, fig. 1 is a schematic device structure diagram of a hardware operating environment according to an embodiment of the present invention.
The page rendering device in the embodiment of the present invention may be a smart phone, or may also be a terminal device such as a PC (Personal Computer), a tablet Computer, or a portable Computer.
As shown in fig. 1, the page rendering apparatus may include: a processor 1001, such as a CPU, a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display (Display), an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., a Wi-Fi interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory (e.g., a magnetic disk memory). The memory 1005 may alternatively be a storage device separate from the processor 1001 described previously.
Those skilled in the art will appreciate that the page rendering device architecture shown in FIG. 1 does not constitute a limitation of the page rendering device and may include more or fewer components than shown, or some of the components may be combined, or a different arrangement of components.
As shown in fig. 1, a memory 1005, which is a kind of computer storage medium, may include therein an operating system, a network communication module, a user interface module, and a page rendering program.
In the terminal shown in fig. 1, the network interface 1004 is mainly used for connecting to a backend server and performing data communication with the backend server; the user interface 1003 is mainly used for connecting a client and performing data communication with the client; and the processor 1001 may be configured to call a page rendering program stored in the memory 1005 and perform the following steps of the page rendering method.
Based on the hardware structure, the invention provides various embodiments of the page rendering method.
The invention provides a page rendering method.
Referring to fig. 2, fig. 2 is a flowchart illustrating a page rendering method according to a first embodiment of the present invention.
In this embodiment, the page rendering method includes:
step S10, when a browser page jump request is received, acquiring a page address to be jumped according to the browser page jump request;
the page rendering method of this embodiment is implemented by a page rendering device, which is described by a front-end server, where the front-end server includes a route processor (Router Handler) and also provides an API (Application Programming Interface) for configuring routing information, so as to generate a routing configuration file. Js is implemented based on vue. Vue is a set of progressive frameworks for building user interfaces. Unlike other large frameworks, vue is designed to be applied layer by layer from bottom to top. The core library of Vue only pays attention to the view layer, so that the method is easy to operate and convenient to integrate with a third-party library or an existing project. On the other hand, vue is also fully capable of providing a driver for complex single page Web applications (SPA) when used in conjunction with modern tool chains and various supporting class libraries.
In this embodiment, the route processor provides a push function (for jumping to a different browser address) to be called by a user, when the user clicks a certain button in the browser, the push function is executed in the button logic to jump to a new route, at this time, a browser address url (uniform resource locator) changes, a pop event (an event in a history series of HTML 5) is triggered on a window object of a page, at this time, the route processor receives a browser page jump request, and further obtains a page address to be jumped according to the browser page jump request, specifically, the page address to be jumped can be taken from an object event of the pop event.
Step S20, obtaining a route matched with the address of the page to be jumped from a pre-generated route configuration file, and obtaining a matching route path of the matched route;
and then, obtaining a route matched with the address of the page to be jumped from a pre-generated route configuration file, obtaining a route path of the matched route, distinguishing the route path from other subsequent route paths, and marking the route path of the matched route as a matched route path.
The route configuration file is generated in advance according to a Pages directory set by a user, and the specific generation process may refer to the following second embodiment, which is not described herein again. When matching, a regular matching mode can be adopted for matching, and the specific matching process can refer to the prior art.
Step S30, scoring each matched route according to the matched route path, and determining a target route according to a scoring result;
since the routes obtained by matching usually include a plurality of routes, after the matching route paths of the matching routes are obtained, the matching routes need to be scored according to the matching route paths, and the target route is determined according to the scoring result.
Specifically, step S30 includes:
step a31, splitting the matched routing path to obtain the sub-item number of each matched route, and calculating to obtain a first score according to the sub-item number and a first preset score;
in this embodiment, the scoring process of the route is specifically as follows:
the matching route paths are split firstly to obtain the number of sub-items of each matching route, and a first score is obtained through calculation according to the number of the sub-items and a first preset score. Since the routing path is a character string composed of a plurality of "/", when the matching routing path is split, the matching routing path can be split according to the character of "/", so as to obtain each sub item forming the routing path. The first score is the product of the number of the sub-items and a first preset score, wherein the first preset score is the preset score of the single sub-item.
Step a32, acquiring the sub-item type of each sub-item of each matched route, and determining a second score of each sub-item of each matched route according to the sub-item type;
then, the sub-item type of each sub-item of each matched route is obtained, and the second score of each sub-item of each matched route is determined according to the sub-item type. Wherein the sub-item types include static, dynamic, fuzzy matching and root.
Specifically, step a32 includes:
step a321, detecting whether each sub item of each matched route includes a preset special character, and obtaining a first detection result;
step a322, detecting whether each sub item of each matched route is a root end, and obtaining a second detection result;
step a323, determining the sub-item type of each sub-item according to the first detection result and the second detection result;
step a324, determining a second score of each sub-item of each matched route according to the mapping relation between the sub-item type and the preset sub-item type and the score.
The specific acquisition process of the second score:
firstly, detecting whether each sub item of each matched route comprises a preset special character to obtain a first detection result, wherein the preset characteristic character comprises a first preset special character': "and a second predetermined character". And meanwhile, detecting whether each sub item of each matched route is a root end or not to obtain a second detection result. When detecting the root end, it is judged whether the child item is only "/".
Then, determining the sub-item type of each sub-item according to the first detection result and the second detection result, if the sub-item does not include the first preset special character': "and a second predetermined character", then the sub-item type is determined to be static; if the sub-item includes the first preset special character': ", then the child type is determined to be dynamic; if the sub-item comprises a second preset character "+", determining that the sub-item type is in fuzzy matching; if the child is simply "/", then the child type is determined to be the root.
And further, according to the mapping relation between the sub-item type and the preset sub-item type and the score, determining a second score of each sub-item of each matched route. And the mapping relation between the preset sub-item type and the scores comprises the scores corresponding to different sub-item types. Recording the score corresponding to the sub-item type being static as a second preset score, recording the score corresponding to the sub-item type being dynamic as a third preset score, recording the score corresponding to the sub-item type being fuzzy matching as a fourth preset score, and recording the score corresponding to the sub-item type being root as a fifth preset score. When the value of each score is set, the design is limited based on the principle of a precise matching priority algorithm, and as the more matched sub-items are, the closer to complete matching is, the score (namely, a first preset score) corresponding to each sub-item can be set to be the maximum value; second, since the static priority is greater than the dynamic one than the root, the fuzzy matching has the lowest priority. Therefore, the first preset score > the second preset score > the third preset score > the fifth preset score > the fourth preset score may be set.
Step a33, summing the first score and the second score to obtain the score of each matched route;
step a34, determining the route corresponding to the maximum value in the scores as the target route.
And finally, summing the first score and the second score to obtain the scores of the matched routes, and further determining the route corresponding to the maximum value in the scores as the target route.
For example, when the first preset score is set to 4, the second preset score is set to 3, the third preset score is set to 2, the fourth preset score is set to-1, and the fifth preset score is set to 1, if the matching routing path is/groups/: groupId, the number of sub-items is 2, the first sub-item groups is static, and the second sub-item groupId is dynamic, the matching routing path is determined to be 2 × 4+3+2=13; if the matching routing path is/, the number of the child entries is 1, and the child entries are root ends, the score is determined to be 1 x 4+1=5; if the matching routing path is/groups/: group/users/: userId, the number of sub items is 4, the first sub item groups is static, the second sub item group is dynamic, the third sub item userId is static, and the fourth sub item userId is dynamic, the matching routing path is determined to be scored as 4 x 4+3+2= 26.
And S40, determining a target component corresponding to the target route according to the route configuration file, and loading the target component to render and obtain a target page corresponding to the address of the page to be skipped.
And finally, determining a target component corresponding to the target route according to the route configuration file, and loading the target component to render and obtain a target page corresponding to the address of the page to be skipped. Specifically, the routing configuration file includes routing data of each route, where the routing data at least includes routing path information and component information, and may also include a routing name, a meta tag (an auxiliary tag of an html language head header region), parent-child relationship information, and the like, where the meta tag may be used to mark whether the route needs to be registered, a status tag, and other additional information.
As a determination mode of the target component, the component of the target route can be directly used as the target component, so that the current route component corresponding to the current browser is unloaded, and the target component is loaded, so as to render and obtain the target page corresponding to the address of the page to be skipped.
As another determination method of the target component, a current routing path corresponding to the current page address may be obtained first, a target routing path of the target route is obtained, then, the current routing path is split to obtain a first sub-item array, and the target routing path is split to obtain a second sub-item array; and comparing the first sub-item array with the second sub-item array to obtain a common routing path and a non-common routing path, determining a target component according to the non-common routing path, determining a common routing component according to the common routing path, unloading components except the common routing component in the current routing component corresponding to the current routing path, and loading the target component to render and obtain a target page corresponding to the address of the page to be skipped.
The embodiment of the invention provides a page rendering method, which comprises the steps of obtaining a page address to be jumped according to a browser page jump request when the browser page jump request is received; then, obtaining a route matched with the address of the page to be jumped from a pre-generated route configuration file, and obtaining a matched route path of the matched route; scoring each matched route according to the matched route path, and determining a target route according to a scoring result; and then determining a target component corresponding to the target route according to the route configuration file, and loading the target component to render and obtain a target page corresponding to the address of the page to be skipped. In the embodiment of the invention, the matched route is obtained through the pre-generated route configuration file, then the matched route is graded to determine the target route, and the target component corresponding to the target route is loaded to realize the rendering of the page.
Further, currently, when implementing page rendering using the read Router application, a user is required to manually write a routing configuration (i.e., a mapping relationship between a page path and a rendering component). When the position of the routing component changes, the routing configuration needs to be modified synchronously, which consumes development time, increases the cost of development labor and has low development efficiency.
In view of the above, a second embodiment of the page rendering method according to the present invention is provided based on the first embodiment.
In this embodiment, before the step S20, the page rendering method further includes:
step A, when a route setting request is received, displaying a page directory setting interface according to the route setting request;
in this embodiment, a developer may trigger a route setting request through an initiating terminal (such as a pc, a mobile phone, and the like), and at this time, when the front-end server receives the route setting request, the front-end server may display a page directory setting interface according to the route setting request. The page directory setting interface can display the following path specifications for the user to input:
1 pages
2. and index. Vue # root routing page path index. Html #
3. Handover a.vue # Path/a
4 ├b
5. "index. Vue # Path/b
6. I _ translation @ id
7. L + -) c.vue # path/b/c
8. Outer layer common to all pages under L layout. Vue # root route
9. L:. Vue # Path/.)
Wherein the dynamic routing supports defining parameters in the path, e.g.,/order/1 matching/order/: id routing, where/1 in the path resolves to parameter id =1.
Step B, when an input completion instruction triggered by a user based on the page directory setting interface is received, acquiring a page directory input by the user;
and when the user finishes inputting, and an input finishing instruction triggered by the user based on the page directory setting interface can be received, acquiring a page directory input by the user, namely a pages directory.
Step C, traversing the page directory, and detecting whether a sub-routing file exists in a folder corresponding to the currently traversed page directory;
and then, traversing the page directory through a readdirSync function provided by the node.js, and detecting whether a sub-routing file exists in a folder corresponding to the currently traversed page directory. Specifically, the presence of the sub-route file can be detected by detecting whether a file suffix in the folder has a value of vue other than layout.
If the sub-routing file exists, executing the step D, obtaining the file name of the currently traversed sub-routing file, determining the routing type according to the file name, and generating second routing data according to the routing type and the file name;
and if the sub-routing file exists in the folder corresponding to the currently traversed page directory, acquiring the file name of the currently traversed sub-routing file, and determining the routing type according to the file name. Specifically, when the route type is determined, if the file name is detected to include index. Vue, the route type is determined to be a default route; if the file name is detected to contain the special character of @, determining that the type of the route is a dynamic route; if the file name is detected to comprise the value vue, determining that the routing type is fuzzy matching; if it is detected that only vue is included in the file name, then the route type is determined to be a regular route. Then, second route data is generated according to the route type and the file name. The second routing data at least includes routing path information and component information, and may further include a routing name, a meta tag, parent-child relationship information, and the like.
Further, if the sub-routing file exists in the folder corresponding to the currently traversed page directory, the next directory of the currently traversed page directory is continuously traversed.
Step E, obtaining a layout file corresponding to the sub-routing file and first routing data thereof, and updating the first routing data according to the second routing data;
and after detecting that the sub-routing file exists, acquiring a layout file corresponding to the sub-routing file and first routing data thereof, and updating the first routing data according to the second routing data. It should be noted that, the execution sequence of step D and step E is not sequential.
Specifically, the step E includes:
e1, detecting whether a layout file exists in a folder corresponding to a currently traversed page directory;
if the layout file exists in the folder corresponding to the currently traversed page directory, executing step E21, and determining the layout file in the folder corresponding to the currently traversed page directory as the layout route corresponding to the sub-route file;
if the folder corresponding to the currently traversed page directory does not have the layout file, executing a step E22, and detecting whether a corresponding layout route exists in a superior directory of the currently traversed page directory;
if the superior directory of the currently traversed page directory has a corresponding layout route, executing step E23 to determine the layout route in the superior directory of the currently traversed page directory as the layout route corresponding to the sub-route file;
further, after the steps E21 and E23, the method further includes:
and E3, acquiring the first routing data of the layout route, and updating the first routing data of the corresponding layout route according to the second routing data.
In this embodiment, while detecting whether a sub-routing file exists in a folder corresponding to a currently traversed page directory, the page directory may be traversed through a readdirSync function provided by a node.
If the layout file exists in the folder corresponding to the currently traversed page directory, determining that the layout file in the folder corresponding to the currently traversed page directory is the layout route (namely, the parent route) corresponding to the child route file; if the folder corresponding to the currently traversed page directory does not have the layout file, detecting whether a corresponding layout route exists in a superior directory of the currently traversed page directory, and if the superior directory of the currently traversed page directory has the corresponding layout route, determining the layout route in the superior directory of the currently traversed page directory as the layout route corresponding to the sub-routing file.
Then, first route data of the layout route is acquired. The first routing data at least includes routing path information and component information, and may further include a routing name, a meta tag, and parent-child relationship information. The routing path information of the layout routing is obtained by removing a file suffix according to the path address of the file relative to the src/pages directory, and in addition, special characters in the file name need to be replaced to obtain routing path information conforming to a preset code specification, so that the address url of the page to be jumped is obtained by analyzing according to the replaced routing path information, for example, "@" of the dynamic routing is replaced by ":", "/index" in the default routing is replaced by "/", and "/layout" in the father routing is replaced by "/". Component (component) information is information of a component corresponding to a route, which is an absolute path of a file. The routing name is a name which is a variable used as a code in the follow-up process according to a path address of a file relative to a pages directory, and is used for analyzing a page address url to be jumped, and also needs to accord with a preset code specification, so that some special characters also need to be replaced, for example, "@" of dynamic routing is replaced by "_", a file suffix is removed, and "/" is converted into "_". The meta tag may be used to mark whether the route requires login, status tags, etc. for some additional information. The parent-child relationship information is the relationship between the parent route and the child route.
And after the first routing data of the layout route is acquired, updating the first routing data of the corresponding layout route according to the second routing data. Specifically, the second route data is pushed into the child attribute of the layout route (i.e., the parent route) to update the parent-child relationship information of the parent route.
Further, after the step E, the method further includes:
and step F, generating the routing configuration file according to the updated first routing data and the second routing data.
And finally, generating a routing configuration file according to the updated first routing data and the second routing data.
Specifically, the step F includes:
step F1, executing a preset template on the updated first routing data and the second routing data to generate a dependency induction logic of each route;
step F2, writing the dependency introduction logic into a preset routing configuration template to obtain an initial routing configuration file;
and F3, compiling the initial route configuration file to obtain the route configuration file.
In this embodiment, after the configuration of the route (i.e., the updated first route data and the updated second route data) is obtained through analysis, a container Root with an empty array structure may be created first, and placed in a container Root (Root) with an empty array structure, so as to construct a code of a route configuration file (route.
Specifically, a preset template is executed on the updated first route data and second route data to generate a dependency induction logic of each route, wherein the preset template may optionally be "import { { name } } from '{ { component } }'; ", the Root container can be traversed recursively, the template is executed once for each route item in the Root container, and dependency import (import) logic of each route is generated. Namely, a preset template is executed to obtain a component name and a routing file address (namely routing path information) in routing data corresponding to a route, then { { name } } in the preset template is replaced by the component name, and { { component } } in the preset template is replaced by the routing file address, so that a dependency introducing logic of the route is obtained. For example, the dependency import logical code for the "pages/a.vue" component is "import a from 'project/src/pages/a.vue'", and then write the route. And then, writing the dependency induction logic into a preset routing configuration template to obtain an initial routing configuration file.
Because the initial routing configuration file cannot be directly run by the browser, the initial routing configuration file needs to be compiled to obtain the routing configuration file. At compile time, compilation may be done via webpack (modular packager).
In addition, it should be noted that, in a specific embodiment, the above steps a to F may be performed in the developer side.
By the method, the route configuration file can be intelligently generated, a developer does not need to manually write the route configuration every time, development time and cost can be saved, and the configuration efficiency of the route configuration file is improved.
Further, based on the first embodiment, a third embodiment of the page rendering method of the present invention is provided.
In this embodiment, before the step of "loading the target component to render and obtain the target page corresponding to the address of the page to be skipped", the page rendering method further includes:
step G, acquiring a single file assembly which is written by a user in advance, and compiling the single file assembly;
in the embodiment, since in the Vue project, there is a code organization method called ". Vue single file component", html template, js logic and css styles can be written in the single file component for being loaded subsequently to display the page to be jumped. However, the single file component cannot be directly run by the browser, and therefore, the single file component written in advance by the user needs to be acquired first, and the single file component is compiled, so that the browser can be directly run. Specifically, at compile time, compilation may be performed by webpack (modular packager). The main goal of webpack is to package JavaScript files together, with the packaged files for use in a browser.
At this time, the step of "loading the target component to render and obtain the target page corresponding to the address of the page to be skipped" includes:
and then, after the target component is determined, loading the target component from the compiled single file component to render and obtain a target page corresponding to the address of the page to be jumped. The specific load rendering process may refer to other embodiments.
Here, it should be noted that the step G may be performed simultaneously with the step F3. After the input of the developer is completed, the input page directory and the single file component are obtained, an initial routing configuration file is generated according to the page directory, compiling is carried out, and meanwhile the single file component is compiled. It should be further noted that, in implementation, the above process may also be executed in the developer side and then directly transmitted to the routing processor in the front-end server.
Further, in the process of implementing page jump based on the background frame SpringMVC, complete HTML (hypertext markup language) data needs to be returned to the browser every time a browser page is jumped, so that the page jump speed is slow. However, most applications have fixed contents, such as a head navigation bar, a menu, and the like, and only partial contents actually need to be updated when a browser page is skipped.
In the present embodiment, step S40 includes:
step a41, obtaining a current routing path corresponding to a current page address, and obtaining a target routing path of the target route;
in this embodiment, after the target route is determined, the current routing path corresponding to the current page address may be obtained first, and the target routing path of the target route may be obtained. Namely, the current route corresponding to the current page address is obtained first, and then the route path of the current route is obtained and recorded as the current route path.
Step a42, splitting the current routing path to obtain a first sub-item array, and splitting the target routing path to obtain a second sub-item array;
then, splitting the current routing path to obtain a first sub-item array, and splitting the target routing path to obtain a second sub-item array. In the splitting process of the routing path, the matching routing path can be split according to the character of "/", and each sub item is labeled according to the sequence of the sub items obtained by splitting to obtain a sub item array. For example, if the current routing path is/user/a, the splitting obtains a first sub-entry array as: a [0] = user, a [1] = a. If the target routing path is/user/b, the second sub-item array obtained by splitting is: b [0] = user, b [1] = b.
Step a43, comparing the first sub-item array with the second sub-item array to obtain a public routing path and a non-public routing path, and determining a target component according to the non-public routing path;
and comparing the first sub-item array with the second sub-item array, so that a public routing path and a non-public routing path can be obtained. The specific comparison mode is as follows: judging whether a first sub-item array and a second sub-item array with the same label are equal or not according to the sequence of the label numbers of the arrays from small to large, namely, if the first sub-item array is a [ ], the second sub-item array is b [ ], starting from the label number 0, judging whether a [0] is equal to b [0] or not firstly, if so, continuously judging whether a [1] is equal to b [1] or not, and repeating until a [ n ] and b [ n ] are not equal, wherein the equal part is a common path of the current routing path and the target routing path and is marked as a common routing path, and the non-common routing path is a part of the target routing path different from the current routing path, namely a part of the target routing path except the common routing path. Here, it should be noted that if a [0] is not equal to b [0], the common routing path is determined as the root routing path, i.e. the root end "/".
Further, a target component is determined from the non-common routing path. That is, the target component is determined from the non-common routing path and the routing profile.
Step a44, determining a common routing component according to the common routing path, unloading components except the common routing component in the current routing component corresponding to the current routing path, and loading the target component.
And finally, determining a common routing component according to the common routing path, unloading components except the common routing component in the current routing component corresponding to the current routing path, and loading a target component.
That is, in specific implementation, assuming that the current browser page/user/a and the page/user/B to be skipped have the same part, such as the head navigation bar and the left menu bar, the content of the same part may be designed as a parent route/user, and then the page/user/a and the page/user/B respectively include different part contents (e.g. corresponding to components a and B respectively), the route/user/a and the route/user/B are taken as child routes of the parent route, and when switching from/user/a to/user/B, it may be determined that the target component is B, and at this time, B is loaded after a is unloaded.
In this embodiment, by comparing the current routing path with the target routing path, the closest parent route (i.e., the route corresponding to the common routing path) is found, the old component (i.e., the component in the current routing component other than the common routing component) is unloaded according to the minimum update principle, the new component (i.e., the target component) is loaded, and the page to be skipped is displayed. By the mode, when the browser page jumps, the fixed content part does not need to be updated, so that repeated content updating can be avoided, the page jumping speed can be further improved, and the use experience of a user is improved.
The invention also provides a page rendering device.
Referring to fig. 3, fig. 3 is a functional module diagram of a page rendering device according to a first embodiment of the present invention.
As shown in fig. 3, the page rendering apparatus includes:
the first obtaining module 10 is configured to, when a browser page jump request is received, obtain a page address to be jumped according to the browser page jump request;
a second obtaining module 20, configured to obtain, from a pre-generated routing configuration file, a route matched with the address of the page to be skipped, and obtain a matching routing path of the matched route;
the route scoring module 30 is configured to score each matched route according to the matched route path, and determine a target route according to a scoring result;
and the page rendering module 40 is configured to determine a target component corresponding to the target route according to the route configuration file, and load the target component to render a target page corresponding to the address of the page to be skipped.
Further, the route scoring module 30 includes:
the first calculating unit is used for splitting the matched routing path to obtain the number of sub-items of each matched route, and calculating to obtain a first score according to the number of the sub-items and a first preset score;
the first determining unit is used for acquiring the sub-item type of each sub-item of each matched route and determining the second score of each sub-item of each matched route according to the sub-item type;
the second calculating unit is used for summing the first score and the second score to obtain the score of each matched route;
and the second determining unit is used for determining the route corresponding to the maximum value in the scores as the target route.
Further, the first determining unit is specifically configured to:
detecting whether each sub item of each matched route comprises a preset special character or not to obtain a first detection result;
detecting whether each sub item of each matched route is a root end or not to obtain a second detection result;
determining the sub-item type of each sub-item according to the first detection result and the second detection result;
and determining a second score of each sub-item of each matched route according to the mapping relation between the sub-item type and the preset sub-item type and the scores.
Further, the page rendering apparatus further includes:
the interface display module is used for displaying a page directory setting interface according to the routing setting request when the routing setting request is received;
the third acquisition module is used for acquiring the page directory input by the user when receiving an input completion instruction triggered by the user based on the page directory setting interface;
the first detection module is used for traversing the page directory and detecting whether a sub-routing file exists in a folder corresponding to the currently traversed page directory;
a fourth obtaining module, configured to obtain a filename of a currently traversed sub-routing file if the sub-routing file exists, determine a routing type according to the filename, and generate second routing data according to the routing type and the filename;
the data updating module is used for acquiring a layout file corresponding to the sub-routing file and first routing data thereof, and updating the first routing data according to the second routing data;
and the file generation module is used for generating the routing configuration file according to the updated first routing data and the second routing data.
Further, the data update module comprises:
the first detection unit is used for detecting whether a layout file exists in a folder corresponding to a currently traversed page directory;
a third determining unit, configured to determine, if a layout file exists in the folder corresponding to the currently traversed page directory, that the layout file in the folder corresponding to the currently traversed page directory is a layout route corresponding to the sub-route file;
the second detection unit is used for detecting whether a corresponding layout route exists in a superior directory of the currently traversed page directory if no layout file exists in a folder corresponding to the currently traversed page directory;
a fourth determining unit, configured to determine, if a corresponding layout route exists in a higher-level directory of a currently traversed page directory, that the layout route in the higher-level directory of the currently traversed page directory is the layout route corresponding to the sub-route file;
and the data updating unit is used for acquiring the first routing data of the layout route and updating the first routing data of the corresponding layout route according to the second routing data.
Further, the file generation module includes:
the template execution unit is used for executing a preset template on the updated first route data and the second route data to generate a dependency induction logic of each route;
the logic writing unit is used for writing the dependence introduction logic into a preset routing configuration template to obtain an initial routing configuration file;
and the file compiling unit is used for compiling the initial routing configuration file to obtain the routing configuration file.
Further, the page rendering module 40 includes:
the first obtaining unit is used for obtaining a current routing path corresponding to a current page address and obtaining a target routing path of the target routing;
the path splitting unit is used for splitting the current routing path to obtain a first subitem array and splitting the target routing path to obtain a second subitem array;
the array comparison unit is used for comparing the first sub-item array with the second sub-item array to obtain a public routing path and a non-public routing path, and determining a target assembly according to the non-public routing path;
and the component loading unit is used for determining a common routing component according to the common routing path, unloading components except the common routing component in the current routing component corresponding to the current routing path and loading the target component.
The function implementation of each module in the page rendering device corresponds to each step in the page rendering method embodiment, and the function and implementation process are not described in detail here.
The present invention also provides a computer readable storage medium, on which a page rendering program is stored, which when executed by a processor implements the steps of the page rendering method according to any one of the above embodiments.
The specific embodiment of the computer-readable storage medium of the present invention is substantially the same as the embodiments of the page rendering method described above, and is not described herein again.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system 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 system. Without further limitation, an element defined by the phrases "comprising a," "8230," "8230," or "comprising" does not exclude the presence of other like elements in a process, method, article, or system comprising the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) as described above and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (8)
1. A page rendering method, characterized in that the page rendering method comprises:
when a browser page jump request is received, acquiring a page address to be jumped according to the browser page jump request;
acquiring a route matched with the address of the page to be jumped from a pre-generated route configuration file, and acquiring a matching route path of the matched route;
scoring each matched route according to the matched route path, and determining a target route according to a scoring result;
determining a target component corresponding to the target route according to the route configuration file, and loading the target component to render a target page corresponding to the address of the page to be jumped;
the step of scoring each matched route according to the matched route path and determining a target route according to a scoring result comprises the following steps:
splitting the matched routing path to obtain the number of sub-items of each matched route, and calculating according to the number of the sub-items and a first preset score to obtain a first score;
acquiring the sub-item type of each sub-item of each matched route, and determining a second score of each sub-item of each matched route according to the sub-item type;
adding the first score and the second score to obtain the score of each matched route;
determining the route corresponding to the maximum value in the scores as a target route;
the step of obtaining the sub-item type of each sub-item of each matched route and determining the second score of each sub-item of each matched route according to the sub-item type comprises:
detecting whether each sub item of each matched route comprises a preset special character or not to obtain a first detection result;
detecting whether each sub item of each matched route is a root end or not to obtain a second detection result;
determining the sub-item type of each sub-item according to the first detection result and the second detection result;
and determining a second score of each sub-item of each matched route according to the mapping relation between the sub-item type and the preset sub-item type and the scores.
2. The page rendering method according to claim 1, wherein, before the step of obtaining the route matching the address of the page to be skipped from the pre-generated route configuration file and obtaining the matching route path of the matching route, the method further comprises:
when a route setting request is received, displaying a page directory setting interface according to the route setting request;
acquiring a page directory input by a user when an input completion instruction triggered by the user based on the page directory setting interface is received;
traversing the page directory, and detecting whether a sub-routing file exists in a folder corresponding to the currently traversed page directory;
if the sub-routing files exist, the file names of the currently traversed sub-routing files are obtained, the routing types are determined according to the file names, and second routing data are generated according to the routing types and the file names;
obtaining a layout file corresponding to the sub-routing file and first routing data thereof, and updating the first routing data according to the second routing data;
and generating the routing configuration file according to the updated first routing data and the second routing data.
3. The page rendering method according to claim 2, wherein the step of obtaining the layout file corresponding to the sub-routing file and the first routing data thereof, and updating the first routing data according to the second routing data comprises:
detecting whether a layout file exists in a folder corresponding to a currently traversed page directory;
if the layout file exists in the folder corresponding to the currently traversed page directory, determining the layout file in the folder corresponding to the currently traversed page directory as the layout route corresponding to the sub-route file;
if the folder corresponding to the currently traversed page directory does not have a layout file, detecting whether a corresponding layout route exists in a superior directory of the currently traversed page directory;
if the superior directory of the currently traversed page directory has a corresponding layout route, determining the layout route in the superior directory of the currently traversed page directory as the layout route corresponding to the sub-route file;
and acquiring first route data of the layout route, and updating the first route data of the corresponding layout route according to the second route data.
4. The page rendering method of claim 2, wherein the step of generating the routing profile based on the updated first routing data and the second routing data comprises:
executing a preset template on the updated first routing data and the second routing data to generate a dependency induction logic of each route;
writing the dependency induction logic into a preset routing configuration template to obtain an initial routing configuration file;
and compiling the initial routing configuration file to obtain the routing configuration file.
5. The page rendering method according to claim 1, wherein the step of determining a target component corresponding to the target route according to the route configuration file, and loading the target component to render a target page corresponding to the address of the page to be skipped to obtain the target page includes:
acquiring a current routing path corresponding to a current page address, and acquiring a target routing path of the target route;
splitting the current routing path to obtain a first sub-item array, and splitting the target routing path to obtain a second sub-item array;
comparing the first sub-item array with the second sub-item array to obtain a public routing path and a non-public routing path, and determining a target component according to the non-public routing path;
and determining a common routing component according to the common routing path, unloading components except the common routing component in the current routing component corresponding to the current routing path, and loading the target component.
6. A page rendering apparatus, characterized in that the page rendering apparatus applies the page rendering method according to claim 1, comprising:
the first acquisition module is used for acquiring a page address to be jumped according to a browser page jump request when the browser page jump request is received;
the second acquisition module is used for acquiring a route matched with the address of the page to be jumped from a pre-generated route configuration file and acquiring a matched route path of the matched route;
the route grading module is used for grading each matched route according to the matched route path and determining a target route according to a grading result; the step of scoring each matched route according to the matched route path and determining a target route according to a scoring result comprises the following steps: splitting the matched routing path to obtain the number of sub-items of each matched route, and calculating according to the number of the sub-items and a first preset score to obtain a first score; acquiring the sub-item type of each sub-item of each matched route, and determining a second score of each sub-item of each matched route according to the sub-item type; adding the first score and the second score to obtain the score of each matched route; determining the route corresponding to the maximum value in the scores as a target route; the step of obtaining the sub-item type of each sub-item of each matched route and determining the second score of each sub-item of each matched route according to the sub-item type includes: detecting whether each sub item of each matched route comprises a preset special character or not to obtain a first detection result; detecting whether each sub item of each matched route is a root end or not to obtain a second detection result; determining the sub-item type of each sub-item according to the first detection result and the second detection result; determining a second score of each subentry of each matched route according to the mapping relation between the subentry type and the score and the preset subentry type;
and the page rendering module is used for determining a target component corresponding to the target route according to the route configuration file, and loading the target component to render and obtain a target page corresponding to the address of the page to be skipped.
7. A page rendering apparatus, characterized in that the page rendering apparatus comprises: memory, a processor and a page rendering program stored on the memory and executable on the processor, the page rendering program when executed by the processor implementing the steps of the page rendering method as claimed in any one of claims 1 to 5.
8. A computer-readable storage medium, on which a page rendering program is stored, which when executed by a processor implements the steps of the page rendering method according to any one of claims 1 to 5.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010809562.6A CN111949351B (en) | 2020-08-12 | 2020-08-12 | Page rendering method, device, equipment and computer readable storage medium |
| PCT/CN2021/085841 WO2022033055A1 (en) | 2020-08-12 | 2021-04-07 | Page rendering method, apparatus, and device, and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010809562.6A CN111949351B (en) | 2020-08-12 | 2020-08-12 | Page rendering method, device, equipment and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111949351A CN111949351A (en) | 2020-11-17 |
| CN111949351B true CN111949351B (en) | 2023-04-07 |
Family
ID=73333299
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010809562.6A Active CN111949351B (en) | 2020-08-12 | 2020-08-12 | Page rendering method, device, equipment and computer readable storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN111949351B (en) |
| WO (1) | WO2022033055A1 (en) |
Families Citing this family (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111949351B (en) * | 2020-08-12 | 2023-04-07 | 深圳前海微众银行股份有限公司 | Page rendering method, device, equipment and computer readable storage medium |
| CN112380480A (en) * | 2020-12-02 | 2021-02-19 | 北京皮尔布莱尼软件有限公司 | Page jump method, computing device and storage medium |
| CN112732742B (en) * | 2021-01-12 | 2023-03-28 | 深圳平安医疗健康科技服务有限公司 | Query page creating method and device, computer equipment and storage medium |
| CN112988260B (en) * | 2021-01-25 | 2023-07-04 | 杭州衣科云科技有限公司 | Application cold start optimization method and device, computer equipment and storage medium |
| CN113254100B (en) * | 2021-05-25 | 2023-08-01 | 四川虹魔方网络科技有限公司 | Method for realizing dynamic loading of multistage route based on Vue |
| CN114911458A (en) * | 2021-12-28 | 2022-08-16 | 天翼数字生活科技有限公司 | Configurable integrated scene automation front-end page design scheme |
| CN114528063B (en) * | 2022-04-21 | 2022-07-12 | 苏州万店掌网络科技有限公司 | Page display method, device, equipment and storage medium |
| CN115268914B (en) * | 2022-08-09 | 2023-04-07 | 华润数字科技有限公司 | Micro front-end page generation method, device, equipment and medium based on modularization |
| CN116149757B (en) * | 2023-04-14 | 2023-06-30 | 深圳复临科技有限公司 | Plug-in virtual route realization method, device, computer equipment and storage medium |
| CN116595285B (en) * | 2023-07-19 | 2024-04-16 | 深圳复临科技有限公司 | Route generation method, device, computer equipment and storage medium |
| CN117112021B (en) * | 2023-10-24 | 2024-01-26 | 腾讯科技（深圳）有限公司 | Route configuration generation method, device, equipment and computer readable storage medium |
| CN117312694B (en) * | 2023-11-29 | 2024-02-02 | 深圳市纷享互联科技有限责任公司 | Method, device and storage medium for constructing H5 application based on applet framework |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8880397B2 (en) * | 2011-10-21 | 2014-11-04 | Wal-Mart Stores, Inc. | Systems, devices and methods for list display and management |
| CN103685611A (en) * | 2013-12-31 | 2014-03-26 | 山石网科通信技术有限公司 | Network access processing method and device |
| CN108363815B (en) * | 2015-07-20 | 2021-08-24 | 阿里巴巴（中国）有限公司 | Webpage pre-reading method and device and intelligent terminal equipment |
| CN106610994A (en) * | 2015-10-23 | 2017-05-03 | 北京国双科技有限公司 | Method and device for counting click paths |
| CN106815276B (en) * | 2015-11-27 | 2020-06-16 | 阿里巴巴集团控股有限公司 | Page skipping method and device |
| CN107968841B (en) * | 2017-12-20 | 2021-03-09 | 深圳乐信软件技术有限公司 | Dynamic routing method, device, storage medium and client of network page |
| CN110347942A (en) * | 2019-05-31 | 2019-10-18 | 深圳壹账通智能科技有限公司 | Method for page jump, device, storage medium and computer equipment |
| CN110515683B (en) * | 2019-07-15 | 2022-12-13 | 平安普惠企业管理有限公司 | Method and device for visual configuration of front-end Vue page and storage medium |
| CN111949351B (en) * | 2020-08-12 | 2023-04-07 | 深圳前海微众银行股份有限公司 | Page rendering method, device, equipment and computer readable storage medium |
-
2020
- 2020-08-12 CN CN202010809562.6A patent/CN111949351B/en active Active
-
2021
- 2021-04-07 WO PCT/CN2021/085841 patent/WO2022033055A1/en active Application Filing
Also Published As
| Publication number | Publication date |
|---|---|
| WO2022033055A1 (en) | 2022-02-17 |
| CN111949351A (en) | 2020-11-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111949351B (en) | Page rendering method, device, equipment and computer readable storage medium | |
| US7185271B2 (en) | Methods and systems for implementing auto-complete in a web page | |
| JP5863214B2 (en) | Storage of web browsing calculations with DOM-based isomorphism | |
| US8375325B2 (en) | Customizable, multi-function button | |
| US8005825B1 (en) | Identifying relevant portions of a document | |
| US20010042076A1 (en) | A hypertext reader which performs a reading process on a hierarchically constructed hypertext | |
| US9311303B2 (en) | Interpreted language translation system and method | |
| US9690855B2 (en) | Method and system for searching for a web document | |
| US7886227B2 (en) | Cross-environment context-sensitive help files | |
| CN113032078A (en) | Page display method and device, electronic equipment and computer readable storage medium | |
| CN105354490A (en) | Method and device for processing hijacked browser | |
| JP2002140194A (en) | Information processing method, information processing device and agent system | |
| US20180025359A1 (en) | Customer journey optimized pre-fetching | |
| US20020073124A1 (en) | Network browser | |
| WO2022257588A1 (en) | Code processing method and system, computer cluster, medium and program product | |
| CN116302054A (en) | Development method and device of software project, storage medium and electronic equipment | |
| CN115795193A (en) | Page data extraction method and page automatic testing method | |
| CN109032924A (en) | Identify method, apparatus, equipment and the storage medium of resource type in the page | |
| CN115291887A (en) | Code generation method, device, equipment and storage medium | |
| CN114968220A (en) | Dynamic portal design method and device | |
| JP2006155275A (en) | Information extraction method and information extraction device | |
| CN113885924A (en) | XML configuration file upgrading method and device and readable storage medium | |
| JPH11288412A (en) | Method and system for preparing document, and computer readable recording medium for recording document preparation program | |
| CN113934959A (en) | Program preview method and device, computer equipment and storage medium | |
| CN106909668B (en) | File searching method and system based on website analysis |
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 |