CN113268234A - Page generation method, device, terminal and storage medium - Google Patents
Page generation method, device, terminal and storage medium Download PDFInfo
- Publication number
- CN113268234A CN113268234A CN202110536225.9A CN202110536225A CN113268234A CN 113268234 A CN113268234 A CN 113268234A CN 202110536225 A CN202110536225 A CN 202110536225A CN 113268234 A CN113268234 A CN 113268234A
- Authority
- CN
- China
- Prior art keywords
- component
- target
- page
- component library
- library
- 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.)
- Withdrawn
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
Abstract
The disclosure discloses a page generation method, a page generation device, a terminal and a storage medium, and belongs to the technical field of internet. The method comprises the following steps: determining conversion plug-ins of any two component libraries in the plurality of component libraries to obtain a plurality of conversion plug-ins; responding to the conversion of the source file, and determining the component library identifier of a source component library used by the source file and the component library identifier of a target component library to be converted of the source file; determining a target conversion plug-in from a plurality of conversion plug-ins based on the component library identification of the source component library and the component library identification of the target component library; converting the page components used by the source file into page components in a target component library based on the target conversion plug-in to obtain a target file; and generating a target page based on the target file. According to the scheme, the source file can be converted through the target conversion plug-in, so that developers are not required to convert the source file, the conversion speed of the source file is increased, and the research and development efficiency of the application program is improved.
Description
Technical Field
The present disclosure relates to the field of internet technologies, and in particular, to a page generation method, an apparatus, a terminal, and a storage medium.
Background
With the development of internet technology, various applications are emerging. The business functions that an application can support are becoming more and more extensive. In the application program development process, different business functions are developed by different development teams, and different development teams use different component libraries for developing pages. Therefore, the page development lacks specifications, so that the page styles of all functions of the application program are different, and the later page development efficiency is low.
In the related art, in order to ensure that pages generated by the same application program are consistent, developers are generally required to rewrite pages with different functions by using a uniform component library, so as to migrate the pages.
In the related art, the page needs to be rewritten according to the unified component library, and the workload is large, so that the research and development efficiency of the application program is low.
Disclosure of Invention
The embodiment of the disclosure provides a page generation method, a page generation device, a terminal and a storage medium, which can improve the research and development efficiency of an application program. The technical scheme is as follows:
in one aspect, a page generation method is provided, and the method includes:
determining conversion plug-ins of any two component libraries in the plurality of component libraries to obtain a plurality of conversion plug-ins, wherein each conversion plug-in is marked with component library identifications of the two component libraries corresponding to the conversion plug-ins;
responding to the conversion of a source file, and determining a component library identifier of a source component library used by the source file and a component library identifier of a target component library to be converted by the source file;
determining a target conversion plug-in from the plurality of conversion plug-ins based on the component library identification of the source component library and the component library identification of the target component library;
converting the page components used by the source file into page components in the target component library based on the target conversion plug-in to obtain a target file;
and generating a target page based on the target file.
In some embodiments, the converting, based on the target conversion plug-in, a page component used by the source file into a page component in the target component library to obtain a target file includes:
converting the source file into a syntax tree;
traversing the source file based on the syntax tree;
for the traversed page components in the syntax tree, converting the page components into page components in the target component library through the target conversion plug-in;
and forming the page components in the converted target component library into the target file until the syntax tree is traversed completely.
In some embodiments, the converting, by the target conversion plug-in, the page component into a page component in the target component library includes:
determining a storage path of the page component in the source component library through the target conversion plug-in;
determining a storage path of the page component with the same function in the target component library through the target conversion plug-in based on the storage path of the page component in the source component library;
calling a page component in the target component library from the storage path of the target component library.
In some embodiments, the method further comprises:
if the page component does not exist in the target component library, determining a component identifier of the page component;
generating a conversion log based on the component identification;
and displaying prompt information, wherein the prompt information is used for prompting the conversion of the page component corresponding to the component identifier in the conversion log.
In some embodiments, the determining the conversion plug-ins of any two component libraries in the plurality of component libraries to obtain a plurality of conversion plug-ins includes:
determining a plurality of component libraries;
for any pair of component libraries in the plurality of component libraries, respectively determining page components which are used for representing the same function in any pair of component libraries;
and determining conversion plug-ins corresponding to the two component libraries based on the corresponding relation of the page components representing the same function in any pair of component libraries.
In some embodiments, the determining, based on the correspondence relationship between any pair of page components representing the same function in the component libraries, a conversion plug-in corresponding to the two component libraries includes:
acquiring a library folder of any pair of component libraries, wherein the library folder is used for storing a storage path of a page component in the component library;
determining the storage path of the page components for representing the same function in the any pair of component libraries from the library folder;
and determining the conversion plug-in according to the storage path of the page component representing the same function and the component library identification of any pair of component libraries.
In some embodiments, the source component library is a component library of a system that has stopped maintenance; alternatively, the first and second electrodes may be,
the source component library is a component library of page components to be unified.
In another aspect, an apparatus for generating a page is provided, the apparatus including:
the system comprises a first determining module, a second determining module and a third determining module, wherein the first determining module is used for determining conversion plugins of any two component libraries in a plurality of component libraries to obtain a plurality of conversion plugins, and each conversion plugin is marked with component library identifications of the two component libraries corresponding to the conversion plugins;
the second determination module is used for responding to the conversion of the source file and determining the component library identifier of a source component library used by the source file and the component library identifier of a target component library to be converted of the source file;
a third determining module, configured to determine a target conversion plug-in from the plurality of conversion plug-ins based on the component library identifier of the source component library and the component library identifier of the target component library;
the conversion module is used for converting the page components used by the source file into page components in the target component library based on the target conversion plug-in to obtain a target file;
and the generating module is used for generating a target page based on the target file.
In some embodiments, the conversion module comprises:
a first conversion unit for converting the source file into a syntax tree;
the traversal unit is used for traversing the source file based on the syntax tree;
the second conversion unit is used for converting the page components in the traversed syntax tree into page components in the target component library through the target conversion plug-in;
and the composition unit is used for composing the page components in the converted target component library into the target file until the syntax tree is traversed.
In some embodiments, the second conversion unit is configured to determine, by the target conversion plug-in, a storage path of the page component in the source component library; determining a storage path of the page component with the same function in the target component library through the target conversion plug-in based on the storage path of the page component in the source component library; calling a page component in the target component library from the storage path of the target component library.
In some embodiments, the apparatus further comprises:
a fourth determining module, configured to determine a component identifier of the page component if the page component does not exist in the target component library;
a second generation module for generating a conversion log based on the component identification;
and the display module is used for displaying prompt information, and the prompt information is used for prompting the conversion of the page component corresponding to the component identifier in the conversion log.
In some embodiments, the first determining module comprises:
a first determination unit configured to determine a plurality of component libraries;
a second determining unit, configured to determine, for any pair of component libraries in the plurality of component libraries, page components used for representing the same function in the any pair of component libraries, respectively;
and a third determining unit, configured to determine, based on a correspondence relationship between page components representing the same function in the any pair of component libraries, a conversion plug-in corresponding to the two component libraries.
In some embodiments, the third determining unit is configured to obtain a library folder of the any pair of component libraries, where the library folder is used to store storage paths of page components in the component library; determining the storage path of the page components for representing the same function in the any pair of component libraries from the library folder; and determining the conversion plug-in according to the storage path of the page component representing the same function and the component library identification of any pair of component libraries.
In some embodiments, the source component library is a component library of a system that has stopped maintenance; or the source component library is a component library of page components to be unified.
In another aspect, a terminal is provided and includes one or more processors and one or more memories, where at least one program code is stored in the one or more memories, and the at least one program code is loaded and executed by the one or more processors to implement the operations performed by the page generation method as described in the method embodiments of the present disclosure.
In another aspect, a non-transitory computer-readable storage medium is provided, in which at least one program code is stored, and the at least one program code is loaded and executed by a processor to implement the operations performed by the page generation method as described in the method embodiments of the present disclosure.
In another aspect, a computer program product or a computer program is provided, the computer program product or the computer program comprising computer program code, the computer program code being stored in a computer readable storage medium. The processor of the terminal reads the computer program code from the computer-readable storage medium, and executes the computer program code, so that the terminal performs the page generation method provided in the various alternative implementations of the above-described aspects.
In the embodiment of the disclosure, the target conversion plug-in used for converting the source file is determined through the source component library and the target file library of the source file, so that the source file can be converted through the target conversion plug-in, developers are not required to convert the source file, the conversion speed of the source file is increased, and the research and development efficiency of the application program is increased.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.
FIG. 1 is a diagram illustrating a system architecture in accordance with one method of page generation according to an exemplary embodiment of the present disclosure;
FIG. 2 is a flowchart illustrating a method of page generation in accordance with an exemplary embodiment;
FIG. 3 is a flowchart illustrating a method of page generation in accordance with an exemplary embodiment;
FIG. 4 is a flowchart illustrating a method of page generation in accordance with an exemplary embodiment;
FIG. 5 is a flowchart illustrating a method of page generation in accordance with an exemplary embodiment;
FIG. 6 is a block diagram illustrating a page generation apparatus in accordance with an exemplary embodiment;
fig. 7 is a block diagram illustrating a structure of a terminal according to an exemplary embodiment.
Detailed Description
To make the objects, technical solutions and advantages of the present disclosure more apparent, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
Fig. 1 is a system architecture diagram illustrating a page generation method according to an exemplary embodiment of the present disclosure. The system architecture diagram includes a terminal 101 and a server 102. The terminal 101 and the server 102 are connected to each other through a network.
The terminal 101 is a terminal 101 for performing page design. The terminal 101 is installed with a target application program, and the target application program is used for providing a page development platform for page developers. The terminal 101 logs in to the server 102 through the target application. The server 102 stores at least one component library, and the component library includes page components for implementing page functions. The terminal 101 writes a source file corresponding to a page in the target application program, determines a page component constituting the page based on the source file, acquires the page component from a component library of the server 102, and performs rendering based on the page component to obtain a target page.
The terminal 101 is a mobile phone, a computer, a tablet computer, or a wearable device. The server 102 may be a single server, a server cluster composed of a plurality of servers, a cloud server, or the like. In the embodiments of the present disclosure, this is not particularly limited.
Fig. 2 is a flowchart illustrating a page generation method according to an exemplary embodiment, where the page generation method includes the following steps, as shown in fig. 2:
step 201: and determining conversion plug-ins of any two component libraries in the plurality of component libraries to obtain a plurality of conversion plug-ins, wherein each conversion plug-in is marked with component library identifications of the two component libraries corresponding to the conversion plug-ins.
Step 202: in response to converting the source file, determining a component library identifier of a source component library used by the source file and a component library identifier of a target component library to be converted by the source file.
Step 203: and determining a target conversion plug-in from the plurality of conversion plug-ins based on the component library identification of the source component library and the component library identification of the target component library.
Step 204: and converting the page components used by the source file into page components in the target component library based on the target conversion plug-in to obtain the target file.
Step 205: and generating a target page based on the target file.
In some embodiments, converting the page components used by the source file into page components in the target component library based on the target conversion plug-in to obtain the target file includes:
converting the source file into a syntax tree;
traversing the source file based on the syntax tree;
for the page components in the traversed syntax tree, converting the page components into page components in a target component library through a target conversion plug-in;
and forming the page components in the converted target component library into a target file until the syntax tree is traversed.
In some embodiments, converting, by the target conversion plug-in, the page component to a page component in the target component library comprises:
determining a storage path of the page component in a source component library through a target conversion plug-in;
determining the storage path of the page components with the same function in the target component library through the target conversion plug-in based on the storage path of the page components in the source component library;
and calling the page component in the target component library from the storage path of the target component library.
In some embodiments, the method further comprises:
if the page component does not exist in the target component library, determining a component identifier of the page component;
generating a conversion log based on the component identification;
and displaying prompt information, wherein the prompt information is used for prompting the conversion of the page component corresponding to the component identifier in the conversion log.
In some embodiments, determining the conversion plug-ins of any two component libraries of the plurality of component libraries, resulting in a plurality of conversion plug-ins, comprises:
determining a plurality of component libraries;
respectively determining page components which are used for expressing the same function in any pair of component libraries for any pair of component libraries in a plurality of component libraries;
and determining conversion plug-ins corresponding to the two component libraries based on the corresponding relation of any page components representing the same function in the component libraries.
In some embodiments, determining a conversion plug-in corresponding to two component libraries based on any correspondence relationship between page components representing the same function in the component libraries comprises:
acquiring a library folder of any pair of component libraries, wherein the library folder is used for storing a storage path of a page component in a component library;
determining page components for representing the same function from the library folder, and storing paths in any pair of component libraries;
and determining the conversion plug-in according to the storage path of the page component for representing the same function and the component library identification of any pair of component libraries.
In some embodiments, the source component library is a component library of a system that has stopped maintenance; alternatively, the first and second electrodes may be,
the source component library is a component library of page components to be unified.
In the embodiment of the disclosure, the target conversion plug-in used for converting the source file is determined through the source component library and the target file library of the source file, so that the source file can be converted through the target conversion plug-in, developers are not required to convert the source file, the conversion speed of the source file is increased, and the research and development efficiency of the application program is increased.
In the embodiment of the disclosure, before the terminal converts the source file, a plurality of conversion plug-ins are generated according to different component libraries, and in the process of converting the page, the corresponding conversion plug-ins are obtained for conversion. Fig. 3 is a flowchart of a page generation method according to an exemplary embodiment, and as shown in fig. 3, in this embodiment, a description is given by taking generation of a plurality of conversion plug-ins as an example. The page generation method comprises the following steps:
step 301: the terminal determines a plurality of component libraries.
In this step, the terminal determines component libraries corresponding to a plurality of commonly used systems. The component libraries are corresponding to page components used by pages with different functions of the written application program. Or the plurality of component libraries are randomly selected. For example, the plurality of component libraries are MTDUI (a component library), ElementUI (a Vue 2.0.0-based component library), musei (a vue 2.0-based component library), iView (a vue.
The number and the type of the plurality of component libraries are set as needed, and in the embodiment of the present application, the number and the type of the plurality of component libraries are not particularly limited.
Step 302: the terminal respectively determines page components which are used for expressing the same function in any pair of component libraries for any pair of component libraries in the plurality of component libraries.
In this step, the terminal pairwise pairs the component libraries in the plurality of component libraries to obtain a plurality of pairs of component libraries. And for each component library, the component library and other component libraries are respectively grouped to obtain the multiple pairs of component libraries.
For each pair of component libraries, the terminal determines page components representing the same function in the pair of component libraries. In some embodiments, the terminal takes any one component library of the pair of component libraries as a source component library and takes the other component library as a target component. And traversing from the source component library, and searching the page component which has the same function with the page component in the source component library from the target component. And correspondingly storing each group of page components representing the same function in the pair of component libraries.
Step 303: and the terminal determines conversion plug-ins corresponding to the two component libraries based on the corresponding relation of any page components with the same function in the component library.
In this step, the terminal correspondingly stores the corresponding relationship of the page components representing the same function in the component library and the component library identifier of the component library to obtain the conversion plug-in of the component library. The process is realized by the following steps 3031-3033, and comprises the following steps:
step 3031: the terminal acquires a library folder of any pair of component libraries.
The library folder is used for storing storage paths of page components in the component library.
For each pair of component libraries, the terminal obtains the library folder of each component library in the pair of component libraries. And for the library folder of each component library, the terminal acquires the attribute information of the component library and determines the library folder of the component library from the attribute information.
Step 3032: the terminal determines page components for representing the same function from the library folder, and the storage path of the page components in any pair of component libraries.
In some embodiments, the storage path of each page component and the component identification of that page component are stored in the library folder. In this step, the terminal determines the component identifier of the page component, and determines the storage path corresponding to the component identifier from the library folder according to the component identifier, thereby obtaining the storage path of the page component in the component library.
It should be noted that, in the embodiment of the present disclosure, the order in which the terminal determines the storage paths of the page components in the component library is not particularly limited.
Another point to be noted is that for each pair of component libraries, which represents potentially many pairs of page components of the same function, the storage path of each page component in the pair of page components in the component library is determined by step 3032 for each pair.
Step 3033: and the terminal determines the conversion plug-in according to the storage path of the page assembly for expressing the same function and the assembly library identification of any pair of assembly libraries.
In this step, the terminal stores the corresponding relationship of the multiple groups of page components with the same function under the same component library identifier to obtain the conversion plug-in.
In the implementation mode, the conversion plug-in is obtained by storing the storage path of the corresponding page component, the process of determining the conversion plug-in is simple and convenient, the efficiency of generating the conversion plug-in is improved, and the conversion plug-in stops storing the storage path of the page component, so that the size of the conversion plug-in is reduced.
It should be noted that, for each pair of component libraries, different component libraries are the same or different as the conversion plug-in corresponding to the source component library, and this is not specifically limited in the embodiment of the present disclosure.
In the embodiment of the disclosure, the target conversion plug-in used for converting the source file is determined through the source component library and the target file library of the source file, so that the source file can be converted through the target conversion plug-in, developers are not required to convert the source file, the conversion speed of the source file is increased, and the research and development efficiency of the application program is increased.
In addition, in the implementation mode, the page components are generated in advance according to the component libraries, so that the target conversion plug-in can be directly obtained according to the source file in the page conversion process, and the efficiency of page component processing is improved.
In the embodiment of the disclosure, in response to the need to convert the source file, the terminal converts the source file based on the target conversion plug-in. Fig. 4 is a flowchart illustrating a page generating method according to an exemplary embodiment, and as shown in fig. 4, in this embodiment, a description is given by taking the generation of multiple conversion plug-ins as an example. The page generation method comprises the following steps:
step 401: the terminal determines conversion plug-ins of any two component libraries in the multiple component libraries to obtain multiple conversion plug-ins.
And each conversion plug-in is marked with the component library identifications of the two component libraries corresponding to the conversion plug-ins.
This step is realized by the step 301 and the step 303, which are not described herein again.
Step 402: in response to converting the source file, the terminal determines a component library identifier of a source component library used by the source file and a component library identifier of a target component library to be converted by the source file.
The source file is a source file corresponding to a page needing component library conversion. The source file is a code file, an instruction file, etc. The source component library is a component library used for writing a source file, and the target component library is a component library into which the source file needs to be converted. The component library comprises a plurality of components, and each component is used for composing a file.
In this step, the terminal receives the source file input by the user, and triggers the conversion of the input source file. Or the terminal determines that the source component library used by the source file is the target component library and determines that the source file needs to be converted. Wherein, the source component library is a component library of a system which is stopped to be maintained; or the source component library is a component library of page components to be unified.
Accordingly, in some embodiments, the source component library corresponding to the source file is a component library that has stopped maintenance. That is, the page component cannot determine that the source file needs to be converted when maintained by the source component library. For example, during the use of an application, pages in the application all need to be updated and maintained. When the tuple component library corresponding to the source file of any page in the application program is not updated or maintained any more, the component library used by the page component needs to be converted into other component libraries in use.
In some embodiments, the source file is a source file that requires a uniform type of page correspondence. For example, in the same application, the source component libraries used by the source files of different pages of the application are different, and in this step, the component libraries used by the source files of different pages are unified.
In the implementation mode, the component library which is not maintained any more or needs the page components of the same type is converted, so that the component library is prevented from being rewritten, and the workload of developers is reduced.
The component library identifier is an identifier that can be used to represent the component library, such as the name, number, etc. of the component library. In the embodiments of the present disclosure, the component library identification is not particularly limited. For example, the component library is identified as ui-element, ui-mtd, and the like.
In this step, referring to fig. 5, the terminal acquires file information of the source file, and parses the component library identifier of the source component library used by the source file from the file information.
In some embodiments, the component library of the target component library is the component library identification entered by the user. In some embodiments, the target component library identification is a component library identification determined from a maintenance target of the current application. For example, the terminal determines that the application program corresponding to the file needs a unified component library, determines the component library as a target component library, and obtains a component library identifier of the target component library. The process of determining the component library identifier of the target component library by the terminal is similar to the process of determining the component library identifier of the source component library by the terminal, and is not repeated here.
Step 403: and the terminal determines the target conversion plug-in from the plurality of conversion plug-ins based on the component library identification of the source component library and the component library identification of the target component library.
In this step, the terminal determines a target conversion plug-in for converting the page component in the source component library into the page component in the target component library from the plurality of conversion plug-ins.
In some embodiments, the conversion plug-in is a conversion plug-in capable of converting two component libraries to each other. In this step, the terminal only needs to determine the target conversion plug-in with the corresponding identifier matching with the component library identifier of the source component library and the component library identifier of the target component library from the plurality of conversion plug-ins.
In some embodiments, the conversion plug-in is a conversion plug-in for converting source files from a source component library to a target component library unidirectionally. In this step, the terminal determines a target conversion plug-in for converting from the source component library to the target component library from among the plurality of conversion plug-ins.
For example, if the source file is a file written based on an element component library, the target component library is mtd component libraries, and the target conversion plug-in is an element2mtd plug-in. Or, the source file is a file written based on the muse component library, the target component library is mtd component library, and the target conversion plug-in is the muse2mtd plug-in. Or, the source file is a file written based on the iView component library, the target component library is mtd component library, and the target conversion plug-in is an iView2mtd plug-in.
And after the terminal determines the target conversion plug-in, loading the target conversion plug-in so as to convert the source file by using the target conversion plug-in.
Step 404: the terminal converts the source file into a syntax tree.
The syntax tree is a representation mode of a source file corresponding to the abstract syntax structure of the source file. The Syntax Tree is any type of Syntax Tree, for example, AST (Abstract Syntax Tree).
Continuing to refer to fig. 5, in this step, the terminal determines the syntax structure of the source file, and generates a syntax tree corresponding to the source file according to the syntax structure of the source file and the file content of the source file.
Step 405: and traversing the source file by the terminal based on the syntax tree.
In this step, the terminal traverses the source file by traversing the syntax tree.
Step 406: and for the page components in the traversed syntax tree, converting the page components into page components in a target component library through a target conversion plug-in.
And the terminal traverses one node in the syntax tree each time in the process of traversing the syntax tree. During the traversal, the terminal determines whether page components corresponding to the source file exist in the syntax tree. And if the grammar tree has page components corresponding to the source file, acquiring the page components for conversion. And if the grammar tree does not have the page component corresponding to the source file, writing the converted page component into the target file.
In the implementation mode, the page components are traversed through the syntax tree, so that the conversion speed of the page components is improved, the page components are prevented from being omitted, and the conversion efficiency of the page components is improved.
With continued reference to fig. 5, when the terminal converts the page component, after the terminal traverses the page component, the target conversion plug-in determines whether the page component supports conversion. And if the page component supports conversion, converting the page component. The process is realized by the following steps 4061-:
step 4601: and the terminal determines the storage path of the page component in the source component library through the target conversion plug-in.
In this step, the terminal determines, through the target conversion plug-in, a library folder of the source component library and a component identifier corresponding to the page component, determines a storage path corresponding to the component identifier from the library folder, and determines the storage path as a storage path of the page component in the source component library.
Step 4062: and the terminal determines the storage path of the page components with the same functions in the target component library through the target conversion plug-in based on the storage path of the page components in the source component library.
The target conversion plug-in stores the corresponding relation of the storage positions of the page components with the same function in the active component library and the target component library. In this step, the storage path of the storage path in the source component library in the target component library is determined by the target conversion plug-in.
Step 4063: and the terminal calls the page components in the target component library from the storage path of the target component library.
In this step, the terminal determines, from the target component library, a page component in the target component library corresponding to the page component in the source file according to the storage path of the target component library.
In the implementation mode, the conversion plug-in determines the storage path of the page component gathered in the target component library, and calls the page component through the storage path without converting all the page components, so that the conversion efficiency of the page component is improved.
It should be noted that, after the terminal executes step 4063, it is determined whether traversal of the syntax tree is completed, and if not, the page component continues to be obtained, and the page component is converted through steps 4061 and 4063.
Another point to account for is that there may not be a page component in the target component library that corresponds to the source component library. Therefore, a page component in the syntax tree may not support conversion, and with continued reference to fig. 5, when the page component does not support conversion, the terminal records the page component for subsequent manual conversion of the page component. The process is as follows: if the page component does not exist in the target component library, the terminal determines the component identification of the page component; generating a conversion log based on the component identification; and displaying prompt information, wherein the prompt information is used for prompting the conversion of the page component corresponding to the component identifier in the conversion log.
In the implementation mode, in the traversal process, the page components which do not support automatic conversion are recorded in the conversion log, so that prompt information can be generated according to the conversion log to prompt developers that the page components are not converted successfully, page components are prevented from being omitted, the page components cannot be converted into all the page components in the target component library, and the conversion accuracy is improved.
Step 407: and the terminal forms the page components in the converted target component library into a target file until the syntax tree is traversed.
In this step, after the terminal completes traversal of the syntax tree, the syntax tree corresponding to the target component library is obtained, and the syntax tree is converted into a target file.
Step 408: and the terminal generates a target page based on the target file.
In this step, the terminal performs page rendering based on the target file to obtain a target page.
In the embodiment of the disclosure, the target conversion plug-in used for converting the source file is determined through the source component library and the target file library of the source file, so that the source file can be converted through the target conversion plug-in, developers are not required to convert the source file, the conversion speed of the source file is increased, and the research and development efficiency of the application program is increased.
Fig. 6 is a block diagram illustrating a page generating apparatus according to an exemplary embodiment, as shown in fig. 6, the page generating apparatus including:
a first determining module 601, configured to determine conversion plug-ins of any two component libraries in the multiple component libraries to obtain multiple conversion plug-ins, where each conversion plug-in is marked with component library identifiers of two component libraries corresponding to the conversion plug-in;
a second determining module 602, configured to determine, in response to converting the source file, a component library identifier of a source component library used by the source file and a component library identifier of a target component library to be converted in the source file;
a third determining module 603, configured to determine a target conversion plug-in from the plurality of conversion plug-ins based on the component library identifier of the source component library and the component library identifier of the target component library;
a conversion module 604, configured to convert, based on the target conversion plug-in, a page component used by the source file into a page component in the target component library, so as to obtain a target file;
a generating module 605 configured to generate a target page based on the target file.
In some embodiments, the conversion module 604, comprises:
a first conversion unit for converting the source file into a syntax tree;
the traversal unit is used for traversing the source file based on the syntax tree;
the second conversion unit is used for converting the page components in the traversed syntax tree into page components in a target component library through a target conversion plug-in;
and the composition unit is used for composing the page components in the converted target component library into a target file until the syntax tree is traversed.
In some embodiments, the second conversion unit is configured to determine, by the target conversion plug-in, a storage path of the page component in the source component library; determining the storage path of the page components with the same function in the target component library through the target conversion plug-in based on the storage path of the page components in the source component library; and calling the page component in the target component library from the storage path of the target component library.
In some embodiments, the apparatus further comprises:
the fourth determining module is used for determining the component identifier of the page component if the page component does not exist in the target component library;
a second generating module 605, configured to generate a conversion log based on the component identifier;
and the display module is used for displaying prompt information, and the prompt information is used for prompting the conversion of the page component corresponding to the component identifier in the conversion log.
In some embodiments, the first determining module 601 includes:
a first determination unit configured to determine a plurality of component libraries;
the second determining unit is used for respectively determining page components which are used for expressing the same function in any pair of component libraries in the plurality of component libraries;
and the third determining unit is used for determining the conversion plug-ins corresponding to the two component libraries based on the corresponding relation of any page component expressing the same function in the component libraries.
In some embodiments, the third determining unit is configured to obtain a library folder of any pair of component libraries, where the library folder is used to store a storage path of a page component in the component library; determining page components for representing the same function from the library folder, and storing paths in any pair of component libraries; and determining the conversion plug-in according to the storage path of the page component for representing the same function and the component library identification of any pair of component libraries.
In some embodiments, the source component library is a component library of a system that has stopped maintenance; or the source component library is a component library of page components to be unified.
In the embodiment of the disclosure, the target conversion plug-in used for converting the source file is determined through the source component library and the target file library of the source file, so that the source file can be converted through the target conversion plug-in, developers are not required to convert the source file, the conversion speed of the source file is increased, and the research and development efficiency of the application program is increased.
It should be noted that: the page generating apparatus provided in the foregoing embodiment is only illustrated by dividing the functional modules when generating a page, and in practical applications, the function distribution may be completed by different functional modules according to needs, that is, the internal structure of the terminal is divided into different functional modules to complete all or part of the functions described above. In addition, the page generation apparatus and the page generation method provided by the above embodiments belong to the same concept, and specific implementation processes thereof are described in the method embodiments for details, which are not described herein again.
Fig. 7 shows a block diagram of a terminal 700 according to an exemplary embodiment of the present disclosure. The terminal 700 may be: a smart phone, a tablet computer, an MP3 player (Moving Picture Experts Group Audio Layer III, motion video Experts compression standard Audio Layer 3), an MP4 player (Moving Picture Experts Group Audio Layer IV, motion video Experts compression standard Audio Layer 4), a notebook computer, or a desktop computer. Terminal 700 may also be referred to by other names such as user equipment, portable terminal, laptop terminal, desktop terminal, and so on.
In general, terminal 700 includes: a processor 701 and a memory 702.
The processor 701 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and so on. The processor 701 may be implemented in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), and a PLA (Programmable Logic Array). The processor 701 may also include a main processor and a coprocessor, where the main processor is a processor for Processing data in an awake state, and is also called a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor 701 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content required to be displayed on the display screen. In some embodiments, the processor 701 may further include an AI (Artificial Intelligence) processor for processing computing operations related to machine learning.
In some embodiments, the terminal 700 may further optionally include: a peripheral interface 703 and at least one peripheral. The processor 701, the memory 702, and the peripheral interface 703 may be connected by buses or signal lines. Various peripheral devices may be connected to peripheral interface 703 via a bus, signal line, or circuit board. Specifically, the peripheral device includes: at least one of radio frequency circuitry 704, touch screen display 705, camera 706, camera assembly 706, audio circuitry 707, positioning assembly 708, and power source 709.
The peripheral interface 703 may be used to connect at least one peripheral related to I/O (Input/Output) to the processor 701 and the memory 702. In some embodiments, processor 701, memory 702, and peripheral interface 703 are integrated on the same chip or circuit board; in some other embodiments, any one or two of the processor 701, the memory 702, and the peripheral interface 703 may be implemented on a separate chip or circuit board, which is not limited in this embodiment.
The Radio Frequency circuit 704 is used for receiving and transmitting RF (Radio Frequency) signals, also called electromagnetic signals. The radio frequency circuitry 704 communicates with communication networks and other communication devices via electromagnetic signals. The rf circuit 704 converts an electrical signal into an electromagnetic signal to transmit, or converts a received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 704 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a subscriber identity module card, and so forth. The radio frequency circuitry 704 may communicate with other terminals via at least one wireless communication protocol. The wireless communication protocols include, but are not limited to: the world wide web, metropolitan area networks, intranets, generations of mobile communication networks (2G, 3G, 4G, and 5G), Wireless local area networks, and/or WiFi (Wireless Fidelity) networks. In some embodiments, the radio frequency circuit 704 may also include NFC (Near Field Communication) related circuits, which are not limited by this disclosure.
The display screen 705 is used to display a UI (User Interface). The UI may include graphics, text, icons, video, and any combination thereof. When the display screen 705 is a touch display screen, the display screen 705 also has the ability to capture touch signals on or over the surface of the display screen 705. The touch signal may be input to the processor 701 as a control signal for processing. At this point, the display 705 may also be used to provide virtual buttons and/or a virtual keyboard, also referred to as soft buttons and/or a soft keyboard. In some embodiments, the display 705 may be one, providing the front panel of the terminal 700; in other embodiments, the display 705 can be at least two, respectively disposed on different surfaces of the terminal 700 or in a folded design; in still other embodiments, the display 705 may be a flexible display disposed on a curved surface or on a folded surface of the terminal 700. Even more, the display 705 may be arranged in a non-rectangular irregular pattern, i.e. a shaped screen. The Display 705 may be made of LCD (Liquid Crystal Display), OLED (Organic Light-Emitting Diode), or the like.
The camera assembly 706 is used to capture images or video. Optionally, camera assembly 706 includes a front camera and a rear camera. Generally, a front camera is disposed at a front panel of the terminal, and a rear camera is disposed at a rear surface of the terminal. In some embodiments, the number of the rear cameras is at least two, and each rear camera is any one of a main camera, a depth-of-field camera, a wide-angle camera and a telephoto camera, so that the main camera and the depth-of-field camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize panoramic shooting and VR (Virtual Reality) shooting functions or other fusion shooting functions. In some embodiments, camera assembly 706 may also include a flash. The flash lamp can be a monochrome temperature flash lamp or a bicolor temperature flash lamp. The double-color-temperature flash lamp is a combination of a warm-light flash lamp and a cold-light flash lamp, and can be used for light compensation at different color temperatures.
The audio circuitry 707 may include a microphone and a speaker. The microphone is used for collecting sound waves of a user and the environment, converting the sound waves into electric signals, and inputting the electric signals to the processor 701 for processing or inputting the electric signals to the radio frequency circuit 704 to realize voice communication. For the purpose of stereo sound collection or noise reduction, a plurality of microphones may be provided at different portions of the terminal 700. The microphone may also be an array microphone or an omni-directional pick-up microphone. The speaker is used to convert electrical signals from the processor 701 or the radio frequency circuit 704 into sound waves. The loudspeaker can be a traditional film loudspeaker or a piezoelectric ceramic loudspeaker. When the speaker is a piezoelectric ceramic speaker, the speaker can be used for purposes such as converting an electric signal into a sound wave audible to a human being, or converting an electric signal into a sound wave inaudible to a human being to measure a distance. In some embodiments, the audio circuitry 707 may also include a headphone jack.
The positioning component 708 is used to locate the current geographic Location of the terminal 700 for navigation or LBS (Location Based Service). The Positioning component 708 can be a Positioning component based on the GPS (Global Positioning System) in the united states, the beidou System in china, the graves System in russia, or the galileo System in the russian eu.
In some embodiments, terminal 700 also includes one or more sensors 710. The one or more sensors 710 include, but are not limited to: acceleration sensor 711, gyro sensor 712, pressure sensor 713, fingerprint sensor 714, optical sensor 715, and proximity sensor 716.
The acceleration sensor 711 can detect the magnitude of acceleration in three coordinate axes of a coordinate system established with the terminal 700. For example, the acceleration sensor 711 may be used to detect components of the gravitational acceleration in three coordinate axes. The processor 701 may control the touch screen 705 to display the user interface in a landscape view or a portrait view according to the gravitational acceleration signal collected by the acceleration sensor 711. The acceleration sensor 711 may also be used for acquisition of motion data of a game or a user.
The gyro sensor 712 may detect a body direction and a rotation angle of the terminal 700, and the gyro sensor 712 may cooperate with the acceleration sensor 711 to acquire a 3D motion of the terminal 700 by the user. From the data collected by the gyro sensor 712, the processor 701 may implement the following functions: motion sensing (such as changing the UI according to a user's tilting operation), image stabilization at the time of photographing, game control, and inertial navigation.
Pressure sensors 713 may be disposed on a side bezel of terminal 700 and/or an underlying layer of touch display 705. When the pressure sensor 713 is disposed on a side frame of the terminal 700, a user's grip signal on the terminal 700 may be detected, and the processor 701 performs right-left hand recognition or shortcut operation according to the grip signal collected by the pressure sensor 713. When the pressure sensor 713 is disposed at a lower layer of the touch display 705, the processor 701 controls the operability control on the UI interface according to the pressure operation of the user on the touch display 705. The operability control comprises at least one of a button control, a scroll bar control, an icon control and a menu control.
The fingerprint sensor 714 is used for collecting a fingerprint of a user, and the processor 701 identifies the identity of the user according to the fingerprint collected by the fingerprint sensor 714, or the fingerprint sensor 714 identifies the identity of the user according to the collected fingerprint. When the user identity is identified as a trusted identity, the processor 701 authorizes the user to perform relevant sensitive operations, including unlocking a screen, viewing encrypted information, downloading software, paying, changing settings, and the like. The fingerprint sensor 714 may be disposed on the front, back, or side of the terminal 700. When a physical button or a vendor Logo is provided on the terminal 700, the fingerprint sensor 714 may be integrated with the physical button or the vendor Logo.
The optical sensor 715 is used to collect the ambient light intensity. In one embodiment, the processor 701 may control the display brightness of the touch display 705 based on the ambient light intensity collected by the optical sensor 715. Specifically, when the ambient light intensity is high, the display brightness of the touch display screen 705 is increased; when the ambient light intensity is low, the display brightness of the touch display 705 is turned down. In another embodiment, processor 701 may also dynamically adjust the shooting parameters of camera assembly 706 based on the ambient light intensity collected by optical sensor 715.
A proximity sensor 716, also referred to as a distance sensor, is typically disposed on a front panel of the terminal 700. The proximity sensor 716 is used to collect the distance between the user and the front surface of the terminal 700. In one embodiment, when the proximity sensor 716 detects that the distance between the user and the front surface of the terminal 700 gradually decreases, the processor 701 controls the touch display 705 to switch from the bright screen state to the dark screen state; when the proximity sensor 716 detects that the distance between the user and the front surface of the terminal 700 gradually becomes larger, the processor 701 controls the touch display 705 to switch from the breath screen state to the bright screen state.
Those skilled in the art will appreciate that the configuration shown in fig. 7 is not intended to be limiting of terminal 700 and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components may be used.
In some embodiments, a computer-readable storage medium is further provided, in which at least one program code is stored, and the at least one program code is loaded and executed by the terminal, so as to implement the multimedia resource presentation method in the foregoing embodiments. The computer readable storage medium may be a memory. For example, the computer-readable storage medium may be a ROM (Read-Only Memory), a RAM (Random Access Memory), a CD-ROM (Compact Disc Read-Only Memory), a magnetic tape, a floppy disk, an optical data storage device, and the like.
In some embodiments, a computer program product or computer program is provided, the computer program product or computer program comprising computer program code stored in a computer readable storage medium. The processor of the terminal reads the computer program code from the computer-readable storage medium, and executes the computer program code, so that the terminal performs the page generation method provided in the various alternative implementations of the above-described aspects.
In some embodiments, the computer program according to the embodiments of the present application may be deployed to be executed on one computer device or on multiple computer devices located at one site, or may be executed on multiple computer devices distributed at multiple sites and interconnected by a communication network, and the multiple computer devices distributed at the multiple sites and interconnected by the communication network may constitute a block chain system
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
The above disclosure is intended to cover alternative embodiments of the disclosure, and not to limit the disclosure to the particular forms disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the disclosure.
Claims (10)
1. A page generation method, characterized in that the method comprises:
determining conversion plug-ins of any two component libraries in the plurality of component libraries to obtain a plurality of conversion plug-ins, wherein each conversion plug-in is marked with component library identifications of the two component libraries corresponding to the conversion plug-ins;
responding to the conversion of a source file, and determining a component library identifier of a source component library used by the source file and a component library identifier of a target component library to be converted by the source file;
determining a target conversion plug-in from the plurality of conversion plug-ins based on the component library identification of the source component library and the component library identification of the target component library;
converting the page components used by the source file into page components in the target component library based on the target conversion plug-in to obtain a target file;
and generating a target page based on the target file.
2. The method of claim 1, wherein converting the page components used by the source file into page components in the target component library based on the target conversion plug-in to obtain a target file comprises:
converting the source file into a syntax tree;
traversing the source file based on the syntax tree;
for the traversed page components in the syntax tree, converting the page components into page components in the target component library through the target conversion plug-in;
and forming the page components in the converted target component library into the target file until the syntax tree is traversed completely.
3. The method of claim 2, wherein the converting, by the target conversion plug-in, the page component into a page component in the target component library comprises:
determining a storage path of the page component in the source component library through the target conversion plug-in;
determining a storage path of the page component with the same function in the target component library through the target conversion plug-in based on the storage path of the page component in the source component library;
calling a page component in the target component library from the storage path of the target component library.
4. The method of claim 3, further comprising:
if the page component does not exist in the target component library, determining a component identifier of the page component;
generating a conversion log based on the component identification;
and displaying prompt information, wherein the prompt information is used for prompting the conversion of the page component corresponding to the component identifier in the conversion log.
5. The method of claim 1, wherein determining the transformation plug-ins for any two of the plurality of component libraries results in a plurality of transformation plug-ins, comprising:
determining a plurality of component libraries;
for any pair of component libraries in the plurality of component libraries, respectively determining page components which are used for representing the same function in any pair of component libraries;
and determining conversion plug-ins corresponding to the two component libraries based on the corresponding relation of the page components representing the same function in any pair of component libraries.
6. The method of claim 5, wherein determining the conversion plug-in corresponding to the two component libraries based on the correspondence relationship between any pair of page components representing the same function in the component libraries comprises:
acquiring a library folder of any pair of component libraries, wherein the library folder is used for storing a storage path of a page component in the component library;
determining the storage path of the page components for representing the same function in the any pair of component libraries from the library folder;
and determining the conversion plug-in according to the storage path of the page component representing the same function and the component library identification of any pair of component libraries.
7. The method of any of claims 1-6, wherein the source component library is a component library of a system that has stopped maintenance; alternatively, the first and second electrodes may be,
the source component library is a component library of page components to be unified.
8. An apparatus for generating a page, the apparatus comprising:
the system comprises a first determining module, a second determining module and a third determining module, wherein the first determining module is used for determining conversion plugins of any two component libraries in a plurality of component libraries to obtain a plurality of conversion plugins, and each conversion plugin is marked with component library identifications of the two component libraries corresponding to the conversion plugins;
the second determination module is used for responding to the conversion of the source file and determining the component library identifier of a source component library used by the source file and the component library identifier of a target component library to be converted of the source file;
a third determining module, configured to determine a target conversion plug-in from the plurality of conversion plug-ins based on the component library identifier of the source component library and the component library identifier of the target component library;
the conversion module is used for converting the page components used by the source file into page components in the target component library based on the target conversion plug-in to obtain a target file;
and the first generation module is used for generating a target page based on the target file.
9. A terminal, characterized in that the terminal comprises one or more processors and one or more memories having stored therein at least one program code, which is loaded and executed by the one or more processors to implement the operations executed by the page generation method according to any one of claims 1 to 7.
10. A non-transitory computer-readable storage medium having stored therein at least one program code, the at least one program code being loaded into and executed by a processor to perform operations performed by the page generation method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110536225.9A CN113268234A (en) | 2021-05-17 | 2021-05-17 | Page generation method, device, terminal and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110536225.9A CN113268234A (en) | 2021-05-17 | 2021-05-17 | Page generation method, device, terminal and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113268234A true CN113268234A (en) | 2021-08-17 |
Family
ID=77231320
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110536225.9A Withdrawn CN113268234A (en) | 2021-05-17 | 2021-05-17 | Page generation method, device, terminal and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113268234A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113672224A (en) * | 2021-08-20 | 2021-11-19 | 上海哔哩哔哩科技有限公司 | Method and device for generating small program page code and computer equipment |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109062572A (en) * | 2018-08-02 | 2018-12-21 | 深圳乐信软件技术有限公司 | A kind of component call method, apparatus, equipment and storage medium |
| CN110990008A (en) * | 2019-11-28 | 2020-04-10 | 北京三快在线科技有限公司 | Method, device, storage medium and electronic equipment for updating page |
| CN111666526A (en) * | 2020-06-17 | 2020-09-15 | 广州市百果园信息技术有限公司 | Page generation method, device, equipment and storage medium |
| US20210011690A1 (en) * | 2018-08-10 | 2021-01-14 | Google Llc | Design system for creating graphical content |
| CN112231619A (en) * | 2020-10-15 | 2021-01-15 | 北京三快在线科技有限公司 | Conversion method, conversion device, electronic equipment and storage medium |
| CN112269576A (en) * | 2020-08-07 | 2021-01-26 | 北京沃东天骏信息技术有限公司 | Component display method and device, server and storage medium |
| CN112433799A (en) * | 2020-11-25 | 2021-03-02 | 平安普惠企业管理有限公司 | Page generation method, device, equipment and medium |
-
2021
- 2021-05-17 CN CN202110536225.9A patent/CN113268234A/en not_active Withdrawn
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109062572A (en) * | 2018-08-02 | 2018-12-21 | 深圳乐信软件技术有限公司 | A kind of component call method, apparatus, equipment and storage medium |
| US20210011690A1 (en) * | 2018-08-10 | 2021-01-14 | Google Llc | Design system for creating graphical content |
| CN110990008A (en) * | 2019-11-28 | 2020-04-10 | 北京三快在线科技有限公司 | Method, device, storage medium and electronic equipment for updating page |
| CN111666526A (en) * | 2020-06-17 | 2020-09-15 | 广州市百果园信息技术有限公司 | Page generation method, device, equipment and storage medium |
| CN112269576A (en) * | 2020-08-07 | 2021-01-26 | 北京沃东天骏信息技术有限公司 | Component display method and device, server and storage medium |
| CN112231619A (en) * | 2020-10-15 | 2021-01-15 | 北京三快在线科技有限公司 | Conversion method, conversion device, electronic equipment and storage medium |
| CN112433799A (en) * | 2020-11-25 | 2021-03-02 | 平安普惠企业管理有限公司 | Page generation method, device, equipment and medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113672224A (en) * | 2021-08-20 | 2021-11-19 | 上海哔哩哔哩科技有限公司 | Method and device for generating small program page code and computer equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110674022B (en) | Behavior data acquisition method and device and storage medium | |
| CN110841285B (en) | Interface element display method and device, computer equipment and storage medium | |
| CN108132790B (en) | Method, apparatus and computer storage medium for detecting a garbage code | |
| CN111949680A (en) | Data processing method and device, computer equipment and storage medium | |
| CN111459466B (en) | Code generation method, device, equipment and storage medium | |
| CN112256320A (en) | Version number generation method, device, terminal and storage medium | |
| CN110677713B (en) | Video image processing method and device and storage medium | |
| CN111737100A (en) | Data acquisition method, device, equipment and storage medium | |
| CN109783176B (en) | Page switching method and device | |
| CN107943484B (en) | Method and device for executing business function | |
| CN112560435B (en) | Text corpus processing method, device, equipment and storage medium | |
| CN112118353A (en) | Information display method, device, terminal and computer readable storage medium | |
| CN111666076A (en) | Layer adding method, device, terminal and storage medium | |
| CN109107163B (en) | Analog key detection method and device, computer equipment and storage medium | |
| CN113268234A (en) | Page generation method, device, terminal and storage medium | |
| CN112230910A (en) | Page generation method, device, equipment and storage medium of embedded program | |
| CN112597417B (en) | Page updating method and device, electronic equipment and storage medium | |
| CN111294320B (en) | Data conversion method and device | |
| CN113076452A (en) | Application classification method, device, equipment and computer readable storage medium | |
| CN113051015A (en) | Page rendering method and device, electronic equipment and storage medium | |
| CN112231619A (en) | Conversion method, conversion device, electronic equipment and storage medium | |
| CN110851435B (en) | Data storage method and device | |
| CN111145723A (en) | Method, device, equipment and storage medium for converting audio | |
| CN113010175A (en) | Anonymous function information acquisition method, device, equipment and readable storage medium | |
| CN113342645B (en) | Method, device, equipment and storage medium for testing business function |
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 | ||
| WW01 | Invention patent application withdrawn after publication | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20210817 |