CN106569800B - Front-end interface generation method and device - Google Patents
Front-end interface generation method and device Download PDFInfo
- Publication number
- CN106569800B CN106569800B CN201610905421.8A CN201610905421A CN106569800B CN 106569800 B CN106569800 B CN 106569800B CN 201610905421 A CN201610905421 A CN 201610905421A CN 106569800 B CN106569800 B CN 106569800B
- Authority
- CN
- China
- Prior art keywords
- template
- analyzer
- end interface
- json format
- interface
- 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
- 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
-
- 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
- G06F16/986—Document structures and storage, e.g. HTML extensions
Abstract
The disclosure relates to a front-end interface generation method and device. The method comprises the following steps: receiving a template calling request from an application platform, wherein the template calling request comprises identification information of a template; acquiring a front-end interface template in a JSON format corresponding to the identification information; and sending the JSON format front-end interface template to the application platform so that the application platform can adopt a first template analyzer to analyze the JSON format front-end interface template to obtain a first visual interface. The front-end interface generation method disclosed by the invention can be suitable for various types of application platforms, and is simple and convenient to operate.
Description
Technical Field
The present disclosure relates to the field of network technologies, and in particular, to a front-end interface generation method and apparatus.
Background
The front end is often referred to as the foreground portion of the website and may include the presentation and structural layers of the website. In the related art, the front-end interface may be built by, for example, generating an interface having a style of a front-end frame through front-end frame software such as boottrap, or generating a template stored in an HTML (HyperText Markup Language) format through a template website, and calling the template when the template is used.
However, the front-end interface built by adopting the template website mode is often limited, and cannot provide cooperation and interaction among multiple components, and cannot realize cross-platform use. In addition, if the template stored in the HTML format is modified in the later stage, the template in the earlier stage needs to be modified one by one, which is inconvenient to use.
Disclosure of Invention
In order to overcome the problems in the related art, the present disclosure provides a front-end interface generation method and apparatus.
According to a first aspect of the embodiments of the present disclosure, there is provided a front-end interface generating method, including:
receiving a template calling request from an application platform, wherein the template calling request comprises identification information of a template;
acquiring a front-end interface template in a JSON format corresponding to the identification information;
and sending the JSON format front-end interface template to the application platform so that the application platform can adopt a first template analyzer to analyze the JSON format front-end interface template to obtain a first visual interface.
For the above method, in a possible implementation manner, the method further includes:
generating a front-end interface template in a hypertext markup language (HTML) format according to the universal component selected by the user on a template editing page;
and converting the front-end interface template in the HTML format into the front-end interface template in the JSON format, and storing the front-end interface template in the JSON format and the corresponding identification information thereof into a database.
For the above method, in a possible implementation manner, the method further includes:
defining the universal component on a template editing page; or
And after the front-end interface template in the JSON format is called, defining the general assembly through a callback function.
For the above method, in a possible implementation manner, the method further includes:
under the condition that a first template analyzer obtaining request of the application platform is received, the first template analyzer is sent to the application platform, so that the application platform loads the first template analyzer.
For the above method, in a possible implementation manner, the method further includes:
modifying the first template parser to a second template parser;
and under the condition of receiving a second template analyzer acquisition request of the application platform, sending a second template analyzer to the application platform so as to enable the application platform to load the second template analyzer, wherein the second template analyzer can analyze the JSON format front-end interface template into a second visual interface.
According to a second aspect of the embodiments of the present disclosure, there is provided a front-end interface generating method, including:
sending a template calling request to a front-end automation platform, wherein the template calling request comprises identification information of a template;
receiving a front-end interface template in a JSON format corresponding to the identification information and sent by the front-end automation platform;
and adopting a first template analyzer to analyze the JSON format front-end interface template to obtain a first visual interface.
For the above method, in a possible implementation manner, the method further includes:
sending a first template analyzer acquisition request to the front-end automation platform;
and loading the first template analyzer under the condition of receiving the first template analyzer sent by the front-end automation platform.
For the above method, in a possible implementation manner, the method further includes:
sending a second template analyzer acquisition request to the front-end automation platform;
and loading the second template analyzer under the condition of receiving the second template analyzer sent by the front-end automation platform, wherein the second template analyzer can analyze the JSON format front-end interface template into a second visual interface.
According to a third aspect of the embodiments of the present disclosure, there is provided a front-end interface generating apparatus including:
the template calling request receiving module is used for receiving a template calling request from an application platform, wherein the template calling request comprises identification information of a template;
a JSON format front-end interface template obtaining module, configured to obtain a JSON format front-end interface template corresponding to the identification information;
and the JSON format front-end interface template sending module is used for sending the JSON format front-end interface template to the application platform so that the application platform can adopt a first template analyzer to analyze the JSON format front-end interface template to obtain a first visual interface.
For the above apparatus, in a possible implementation manner, the method further includes:
the front-end interface template generating module in the HTML format is used for editing a page on a template and generating a front-end interface template in the HTML format of the hypertext markup language according to the universal component selected by a user;
and the JSON format front-end interface template generating module is used for converting the HTML format front-end interface template into the JSON format front-end interface template and storing the JSON format front-end interface template and the corresponding identification information thereof into a database.
For the above apparatus, in a possible implementation manner, the method further includes:
the definition module is used for editing a page on a template and defining the general component; or
And after the front-end interface template in the JSON format is called, defining the general assembly through a callback function.
For the above apparatus, in a possible implementation manner, the method further includes:
the first template parser sending module is used for sending the first template parser to the application platform under the condition that a first template parser obtaining request of the application platform is received, so that the application platform loads the first template parser.
For the above apparatus, in a possible implementation manner, the method further includes:
the template analyzer modification module is used for modifying the first template analyzer into a second template analyzer;
and the second template parser sending module is configured to send a second template parser to the application platform under the condition that a second template parser acquisition request of the application platform is received, so that the application platform loads the second template parser, where the second template parser can parse the JSON-format front-end interface template into a second visual interface.
According to a fourth aspect of the embodiments of the present disclosure, there is provided a front-end interface generating apparatus including:
the template calling request sending module is used for sending a template calling request to a front-end automation platform, wherein the template calling request comprises identification information of a template;
a JSON format front-end interface template receiving module, configured to receive a JSON format front-end interface template corresponding to the identification information and sent by the front-end automation platform;
and the JSON format front-end interface template analysis module is used for analyzing the JSON format front-end interface template by adopting a first template analyzer to obtain a first visual interface.
For the above apparatus, in a possible implementation manner, the method further includes:
the first template analyzer acquisition request sending module is used for sending a first template analyzer acquisition request to the front-end automation platform;
and the first template analyzer loading module is used for loading the first template analyzer under the condition of receiving the first template analyzer sent by the front-end automation platform.
For the above apparatus, in a possible implementation manner, the method further includes:
the second template analyzer acquisition request sending module is used for sending a second template analyzer acquisition request to the front-end automation platform;
and the second template analyzer loading module is used for loading the second template analyzer under the condition of receiving the second template analyzer sent by the front-end automation platform, wherein the second template analyzer can analyze the JSON format front-end interface template into a second visual interface.
According to a fifth aspect of the embodiments of the present disclosure, there is provided a front-end interface generating apparatus including:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
receiving a template calling request from an application platform, wherein the template calling request comprises identification information of a template;
acquiring a front-end interface template in a JSON format corresponding to the identification information;
and sending the JSON format front-end interface template to the application platform so that the application platform can adopt a first template analyzer to analyze the JSON format front-end interface template to obtain a first visual interface.
According to a sixth aspect of the embodiments of the present disclosure, there is provided a front-end interface generating apparatus including:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
sending a template calling request to a front-end automation platform, wherein the template calling request comprises identification information of a template;
receiving a front-end interface template in a JSON format corresponding to the identification information and sent by the front-end automation platform;
and adopting a first template analyzer to analyze the JSON format front-end interface template to obtain a first visual interface.
The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects: by the front-end interface generation method and device, the application platform can call the JSON format front-end interface template, and the JSON format front-end interface template is analyzed by the template analyzer to obtain the visual interface. The front-end interface generation method and device can be suitable for various types of application platforms, and are simple and convenient to operate.
Further, according to the front-end interface generation method and device disclosed by the invention, a user can make a front-end interface template in an HTML format in a front-end automation platform according to the development requirements of the user. The front-end automation platform further converts the front-end interface template in the HTML format into the front-end interface template in the JSON format and stores the front-end interface template in the database, so that the template storage and the user calling are facilitated, and the development efficiency and the user experience can be improved.
Further, the front-end interface generation method and device disclosed by the invention can realize uniform modification of the front-end interface template through modification of the template parser. For example, the front-end interface template may be beautified by upgrading the template parser. In addition, a plurality of template resolvers can be written, so that the same front-end interface template can have a plurality of visual interface forms.
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 flow chart illustrating a front-end interface generation method in accordance with an exemplary embodiment.
FIG. 2 is a schematic diagram of a front-end automation platform and application platform illustrating a front-end interface generation method in accordance with an exemplary embodiment.
FIG. 3 is a flow chart illustrating an implementation of a front-end interface generation method in accordance with an illustrative embodiment.
FIG. 4 is a flowchart illustrating an implementation of a front-end interface generation method in accordance with an illustrative embodiment.
FIG. 5 is a flowchart illustrating an implementation of a front-end interface generation method in accordance with an illustrative embodiment.
FIG. 6 is a flow chart illustrating a method for generating a front-end interface in accordance with an exemplary embodiment.
FIG. 7 is a flowchart illustrating an implementation of a front-end interface generation method in accordance with an illustrative embodiment.
FIG. 8 is a flowchart illustrating an implementation of a front-end interface generation method in accordance with an illustrative embodiment.
Fig. 9 is a block diagram illustrating a front-end interface generating apparatus according to an example embodiment.
Fig. 10 is a block diagram illustrating a front-end interface generating apparatus according to an example embodiment.
Fig. 11 is a block diagram illustrating a front-end interface generating apparatus according to an example embodiment.
Fig. 12 is another block diagram illustrating a front-end interface generating apparatus according to an example embodiment.
Fig. 13 is another block diagram illustrating a front-end interface generating apparatus according to an example embodiment.
Fig. 14 is a block diagram illustrating an apparatus 800 for front-end interface generation in accordance with an example embodiment.
Detailed Description
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 flow chart illustrating a front-end interface generation method in accordance with an exemplary embodiment. As shown in fig. 1, the front-end interface generation method may include the following steps.
In step S101, a template calling request from an application platform is received, where the template calling request includes identification information of a template.
The application platform may be various types of website building platforms, which is not limited herein. The present embodiment does not limit the type of the Identification information of the template, and for example, the Identification information may include a template Name (Name), a template number (ID), and the like, which is not limited herein.
In step S102, a front-end interface template in the JSON format corresponding to the identification information is acquired.
In this embodiment, the identification information of the template and the template have a corresponding relationship (or mapping relationship). Through the identification information of the template, a front-end interface template in a JSON format corresponding to the identification information of the template can be searched and obtained from a database. The database can be used for storing the identification information of the template and the corresponding front-end interface template in the JSON format.
In this embodiment, the front-end interface template may be stored in JSON-formatted data. The JSON (JavaScript Object Notation) may be a lightweight data exchange format. The JSON format is easy to read and write, and the template analyzer is easy to analyze into a visual interface, so that the analysis rate can be improved. Furthermore, the JSON format is more advantageous for storage and transmission than the HTML (Hyper Text Markup Language) format.
In step S103, a JSON-formatted front-end interface template is sent to the application platform, so that the application platform can use the first template parser to parse the JSON-formatted front-end interface template to obtain a first visual interface.
The template parser of this embodiment may be written in js (javascript) language. The template parser can read variable values and parse template statements, thereby converting abstract JSON data into a visual interface. When the front-end interface template is to be modified, the modification of the front-end interface template can be realized through the modification of the template parser.
As an example of this embodiment, a website background developer uses the front-end automation platform of this embodiment to perform website building. As shown in fig. 2, the front-end automation platform receives a template call request including a template ID (identification information of the template) from the application platform (step S101). The front-end automation platform searches for a template JSON (i.e., a front-end interface template in JSON format) corresponding to the template ID from the database according to the template ID (step S102), and sends the template JSON to the application platform (step S103). After receiving the template JSON, the application platform parses the template JSON by using, for example, a template parser with a version number V1.1 (an example of a first template parser), and generates a corresponding visualization interface.
By the front-end interface generation method, the application platform can call the front-end interface template in the JSON format, and the front-end interface template in the JSON format is analyzed by the template analyzer to obtain the visual interface. The front-end interface generation method of the embodiment can be suitable for various types of application platforms, is simple and convenient to operate, and can improve the reusability of the page, so that the development efficiency is improved, and the maintenance cost is reduced.
FIG. 3 is a flow chart illustrating an implementation of a front-end interface generation method in accordance with an illustrative embodiment. As shown in fig. 3, the front-end interface generating method may include the following steps.
In step S301, a front-end interface template in the HTML format is generated on the template editing page according to the general component selected by the user.
The template editing page of the embodiment may be a page provided for developers to edit templates. For example, the template editing page may have a preview area and a function area. The functional area may have a plurality of common components that are preset for selection by a developer. The generic data and methods can be simply encapsulated by generic components, such as function selection boxes.
The developer can select the general components from the functional area and drag the general components to the preview area, so that the front-end interface template in the HTML format is generated. As an example of this embodiment, a developer develops a front-end interface template, wherein the front-end interface template has a region selection box, and the developer can select a general component of the region selection box from the function bar and drag the general component to the preview region.
In step S302, the front-end interface template in the HTML format is converted into a front-end interface template in the JSON format, and the front-end interface template in the JSON format and the identification information corresponding to the front-end interface template are stored in the database.
As shown in FIG. 2, the front-end automation platform may include a template editing module, a parser module, a component HTML-JSON map package module, and a database module. The template editing plate can provide a template editing page, and developers can edit the template in the template editing page.
Further, after the front-end interface template in the HTML format is completed, the completed front-end interface template in the HTML format can be converted into the front-end interface template in the JSON format through the component HTML-JSON mapping packet module, and the converted front-end interface template in the JSON format is stored in the database. The database can be used for storing the identification information of the template and the corresponding front-end interface template in the JSON format.
Through the identification information of the template, a front-end interface template in a JSON format corresponding to the identification information of the template can be searched and obtained from a database. The application platform can call a JSON format front-end interface template, and the JSON format front-end interface template is analyzed through the template analyzer to obtain a visual interface. The front-end interface generation method of the embodiment can be suitable for various types of application platforms, and is simple and convenient to operate.
By the front-end interface generation method, developers can generate the front-end interface template in the HTML format in the template editing page by dragging the universal component and the like. Further, the front-end automation platform can convert the front-end interface template from an HTML format to a JSON format, store the front-end interface template in the JSON format in a database, and analyze JSON data into final HTML data through a self-made template analyzer. And when the templates need to be uniformly modified, the template analyzer can be modified to achieve the purpose of modifying each template.
Furthermore, the application platform can be called according to the identification information of the template, and the operation is simple and convenient. The front-end automation platform can be used by a plurality of application platforms, front-end development resources can be released, and project development speed is improved, so that non-front-end developers can develop a front-end interface (Form).
FIG. 4 is a flowchart illustrating an implementation of a front-end interface generation method in accordance with an illustrative embodiment. As shown in fig. 4, the front-end interface generation method may include the following steps.
In step S401, in the case of receiving a first template parser acquisition request of the application platform, the first template parser is sent to the application platform, so that the application platform loads the first template parser.
As an example of this embodiment, as shown in fig. 2, if a template parser for parsing a certain template JSON is not installed in the application platform, and it is assumed that the version number of the template parser is V1.1. The application platform may send a template parser acquisition request to the front-end automation platform, which may include the version number V1.1 described above. After receiving the request, the front-end automation platform may send a JS file corresponding to the template parser with the version number V1.1 to the application platform. Further, when the application platform receives the JS file returned by the front-end automation platform, the JS file can be loaded in the program of the application platform, so that the function of analyzing the JSON-format front-end interface template is realized.
In step 402, a template invocation request is received from an application platform, the template invocation request including identification information of a template. The description of this step can be found in step S101.
In step 403, a front-end interface template in the JSON format corresponding to the identification information is obtained. The description of this step can be found in step S102.
In step 404, a JSON-formatted front-end interface template is sent to the application platform, so that the application platform can parse the JSON-formatted front-end interface template by using the first template parser to obtain a first visual interface. The description of this step can be found in step S103.
In one possible implementation, the method further includes: the generic components are defined.
The embodiment does not limit the definition mode of the general components, for example, the general components can be defined on a template editing page; the interaction behavior can also be customized through an externally exposed interface of the template parser, for example, after the front-end interface template is called, the generic component is defined through a callback function. Wherein, defining the common component may be defining the content of the common component, such as text, attribute, and the like. Furthermore, interactive behavior between components can also be provided through the template parser.
As an example of this embodiment, a developer develops a front-end interface template, where there is a region selection box in the front-end interface template. The developer does not know that the region selection box has several options during development, such as east city region, west city region, hai lake region, etc., or Beijing city, Shanghai city, Tianjin city, etc. The developer can further define the generic component so that the visual interface has certain operational implications.
In one possible implementation, as shown in fig. 5, the method further includes:
in step S400, the first template parser is modified to a second template parser.
In step S401', in the case of receiving a second template parser acquisition request of the application platform, the second template parser is sent to the application platform, so that the application platform loads the second template parser.
The second template analyzer can analyze the front-end interface template in the JSON format into a second visual interface.
Steps S402 and S403 are then performed.
Finally, in step 404', the JSON-formatted front-end interface template is sent to the application platform, so that the application platform can parse the JSON-formatted front-end interface template by using the second template parser to obtain a second visual interface.
In this embodiment, the second template parser may have an association with the first template parser. For example, the second template parser may be the upgraded template parser of the first template parser. In addition, the second template parser may not have a relationship with the first template parser, and is not limited herein.
Further, a plurality of template resolvers may be stored in the front-end automation platform. By writing a plurality of template resolvers, the front-end interface template in the same JSON format can have a plurality of expression forms. Developers can independently select template resolvers with different versions according to development requirements of the developers, such as interface style requirements. In addition, in the process of upgrading the template parser, if a developer wants the original template style, the developer only needs to refer to the original template parser.
The front-end interface generation method of the embodiment can realize the uniform modification of the front-end interface template through the modification of the template parser. For example, the front-end interface template may be beautified by upgrading the template parser. In addition, a plurality of template resolvers can be written, so that the same front-end interface template can have a plurality of visual interface forms.
FIG. 6 is a flow chart illustrating a method for generating a front-end interface in accordance with an exemplary embodiment. As shown in fig. 6, the front-end interface generation method may include the following steps.
In step S601, a template calling request is sent to the front-end automation platform, where the template calling request includes identification information of a template.
The front-end interface generation method of the embodiment can be applied to an application platform. The application platform may be various types of website building platforms, which is not limited herein. The present embodiment does not limit the type of the Identification information of the template, and for example, the Identification information may include a template Name (Name), a template number (ID), and the like, which is not limited herein.
In step S602, a front-end interface template in JSON format, which is sent by the front-end automation platform and corresponds to the identification information, is received.
As shown in FIG. 2, the front-end automation platform may include a template editing module, a parser module, a component HTML-JSON map package module, and a database module. The identification information of the template and the template have a corresponding relationship (or called mapping relationship). Through the identification information of the template, the front-end automation platform can search and obtain a JSON format front-end interface template corresponding to the identification information of the template from a database, and sends the JSON format front-end interface template to the application platform.
In step S603, the front-end interface template in the JSON format is parsed by the first template parser to obtain a first visual interface.
As an example of this embodiment, a website background developer uses the front-end automation platform of this embodiment to perform website building, where a website to be built may be referred to as an application platform. As shown in fig. 2, the application platform sends a template calling request including a template ID (identification information of the template) to the front-end automation platform (step S601). The front-end automation platform receives a template calling request from the application platform (step S101). Then, the front-end automation platform searches for a template JSON (i.e., a front-end interface template in JSON format) corresponding to the template ID from the database according to the template ID (step S102), and sends the template JSON to the application platform (step S103). The application platform receives the template JSON (step S602), and parses the template JSON using, for example, a template parser with a version number V1.1 (an example of a first template parser), and generates a corresponding visualization interface (step S603).
By the front-end interface generation method, the application platform can call the front-end interface template in the JSON format, and the front-end interface template in the JSON format is analyzed by the template analyzer to obtain the visual interface. The front-end interface generation method of the embodiment can be suitable for various types of application platforms, is simple and convenient to operate, and can improve the reusability of the page, so that the development efficiency is improved, and the maintenance cost is reduced.
FIG. 7 is a flowchart illustrating an implementation of a front-end interface generation method in accordance with an illustrative embodiment. As shown in fig. 7, the front-end interface generation method may include the following steps.
In step S701, a first template parser acquisition request is sent to the front-end automation platform.
In step S702, in the case of receiving the first template parser transmitted by the front-end automation platform, the first template parser is loaded.
In step S703, a template calling request is sent to the front-end automation platform, where the template calling request includes identification information of a template. The description of this step can be found in step S601.
In step S704, a front-end interface template in the JSON format corresponding to the identification information and sent by the front-end automation platform is received. The description of this step can be found in step S602.
In step S705, a first template parser is used to parse the JSON-formatted front-end interface template to obtain a first visual interface. The description of this step can be referred to step S603.
In one possible implementation, as shown in fig. 8, the method further includes:
in step S701', a second template parser acquisition request is sent to the front-end automation platform.
In step S702', upon receiving the second template parser sent by the front-end automation platform, the second template parser is loaded.
The second template analyzer can analyze the front-end interface template in the JSON format into a second visual interface.
Then steps S703 and S704 are performed.
Finally, in step S705', the front-end interface template in the JSON format is parsed by using a second template parser to obtain a second visual interface.
In this embodiment, the second template parser may have an association with the first template parser. For example, the second template parser may be the upgraded template parser of the first template parser. In addition, the second template parser may not have a relationship with the first template parser, and is not limited herein.
Further, a plurality of template resolvers may be stored in the front-end automation platform. By writing a plurality of template resolvers, the front-end interface template in the same JSON format can have a plurality of expression forms. Developers can independently select template resolvers with different versions according to development requirements of the developers, such as interface style requirements. In addition, in the process of upgrading the template parser, if a developer wants the original template style, the developer only needs to refer to the original template parser.
The front-end interface generation method of the embodiment can realize the uniform modification of the front-end interface template through the modification of the template parser. For example, the front-end interface template may be beautified by upgrading the template parser. In addition, a plurality of template resolvers can be written, so that the same front-end interface template can have a plurality of visual interface forms.
Fig. 9 is a block diagram illustrating a front-end interface generating apparatus according to an example embodiment. Referring to fig. 9, the apparatus includes a template call request receiving module 11, a JSON-formatted front-end interface template obtaining module 13, and a JSON-formatted front-end interface template transmitting module 15.
Wherein the template calling request receiving module 11 is configured to receive a template calling request from an application platform, the template calling request including identification information of a template. The JSON-format front-end interface template obtaining module 13 is configured to obtain a JSON-format front-end interface template corresponding to the identification information. The JSON-formatted front-end interface template sending module 15 is configured to send the JSON-formatted front-end interface template to the application platform, so that the application platform can use a first template parser to parse the JSON-formatted front-end interface template to obtain a first visual interface.
Fig. 10 is a block diagram illustrating a front-end interface generating apparatus according to an example embodiment. Referring to fig. 10, the apparatus includes a template call request receiving module 11, a JSON-formatted front-end interface template obtaining module 13, and a JSON-formatted front-end interface template transmitting module 15.
In a possible implementation manner, the apparatus further includes a front-end interface template generation module 21 in HTML format and a front-end interface template generation module 23 in JSON format. The HTML-formatted front-end interface template generation module 21 is configured to generate a hypertext markup language HTML-formatted front-end interface template in a template editing page according to the general-purpose component selected by the user. The JSON-formatted front-end interface template generating module 23 is configured to convert the HTML-formatted front-end interface template into the JSON-formatted front-end interface template, and store the JSON-formatted front-end interface template and the identification information corresponding to the front-end interface template in the database.
In a possible implementation, the apparatus further comprises a definition module 25. The definition module 25 is configured to define the generic component on a template editing page; or after the front-end interface template in the JSON format is called, the general component is defined through a callback function.
In a possible implementation manner, the apparatus further includes a first template parser sending module 31. The first template parser sending module 31 is configured to send a first template parser to the application platform in a case of receiving a first template parser acquiring request of the application platform, so that the application platform loads the first template parser.
In a possible implementation manner, the apparatus further includes a template parser modification module 33 and a second template parser transmission module 35. The template parser modification module 33 is configured to modify the first template parser to a second template parser. The second template parser sending module 35 is configured to, in a case that a second template parser obtaining request of the application platform is received, send a second template parser to the application platform so that the application platform loads the second template parser, where the second template parser can parse the JSON-formatted front-end interface template into a second visualization interface.
With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
By the front-end interface generating device, the application platform can call the front-end interface template in the JSON format, and the front-end interface template in the JSON format is analyzed by the template analyzer to obtain the visual interface. The front-end interface generating device of the embodiment can be suitable for various types of application platforms, and is simple and convenient to operate.
The front-end interface generation method and the front-end interface generation device of the embodiment can realize uniform modification of the front-end interface template through modification of the template parser. For example, the front-end interface template may be beautified by upgrading the template parser. In addition, a plurality of template resolvers can be written, so that the same front-end interface template can have a plurality of visual interface forms.
Fig. 11 is a block diagram illustrating a front-end interface generating apparatus according to an example embodiment. Referring to fig. 11, the apparatus includes a template call request transmission module 41, a JSON-formatted front-end interface template reception module 43, and a JSON-formatted front-end interface template parsing module 45.
Wherein the template invocation request sending module 41 is configured to send a template invocation request to the front-end automation platform, where the template invocation request includes identification information of the template. The JSON-formatted front-end interface template receiving module 43 is configured to receive the JSON-formatted front-end interface template corresponding to the identification information, which is sent by the front-end automation platform. The JSON-formatted front-end interface template parsing module 45 is configured to parse the JSON-formatted front-end interface template to obtain a first visual interface by using a first template parser.
In one possible implementation manner, referring to fig. 12, the apparatus further includes a first template parser acquisition request sending module 51 and a first template parser loading module 53. The first template parser retrieval request sending module 51 is configured to send a first template parser retrieval request to the front-end automation platform. The first template parser loading module 53 is configured to load the first template parser upon receiving the first template parser sent by the front-end automation platform.
In a possible implementation manner, referring to fig. 13, the apparatus further includes a second template parser acquisition request sending module 61 and a second template parser loading module 63. The second template parser retrieval request sending module 61 is configured to send a second template parser retrieval request to the front-end automation platform. The second template parser loading module 63 is configured to load the second template parser in a case of receiving the second template parser sent by the front-end automation platform, where the second template parser can parse the JSON-formatted front-end interface template into a second visualization interface.
With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
By the front-end interface generating device, the application platform can call the front-end interface template in the JSON format, and the front-end interface template in the JSON format is analyzed by the template analyzer to obtain the visual interface. The front-end interface generating device of the embodiment can be suitable for various types of application platforms, and is simple and convenient to operate.
Further, the front-end interface generating device of this embodiment may implement unified modification on the front-end interface template by modifying the template parser. For example, the front-end interface template may be beautified by upgrading the template parser. In addition, a plurality of template resolvers can be written, so that the same front-end interface template can have a plurality of visual interface forms.
Fig. 14 is a block diagram illustrating an apparatus 800 for front-end interface generation in accordance with an example embodiment. For example, the apparatus 800 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, an exercise device, a personal digital assistant, and the like.
Referring to fig. 14, the apparatus 800 may include one or more of the following components: processing component 802, memory 804, power component 806, multimedia component 808, audio component 810, input/output (I/O) interface 812, sensor component 814, and communication component 816.
The processing component 802 generally controls overall operation of the device 800, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing components 802 may include one or more processors 820 to execute instructions to perform all or a portion of the steps of the methods described above. Further, the processing component 802 can include one or more modules that facilitate interaction between the processing component 802 and other components. For example, the processing component 802 can include a multimedia module to facilitate interaction between the multimedia component 808 and the processing component 802.
The memory 804 is configured to store various types of data to support operations at the apparatus 800. Examples of such data include instructions for any application or method operating on device 800, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 804 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
The multimedia component 808 includes a screen that provides an output interface between the device 800 and a user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front facing camera and/or a rear facing camera. The front camera and/or the rear camera may receive external multimedia data when the device 800 is in an operating mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.
The audio component 810 is configured to output and/or input audio signals. For example, the audio component 810 includes a Microphone (MIC) configured to receive external audio signals when the apparatus 800 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may further be stored in the memory 804 or transmitted via the communication component 816. In some embodiments, audio component 810 also includes a speaker for outputting audio signals.
The I/O interface 812 provides an interface between the processing component 802 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.
The sensor assembly 814 includes one or more sensors for providing various aspects of state assessment for the device 800. For example, the sensor assembly 814 may detect the open/closed status of the device 800, the relative positioning of components, such as a display and keypad of the device 800, the sensor assembly 814 may also detect a change in the position of the device 800 or a component of the device 800, the presence or absence of user contact with the device 800, the orientation or acceleration/deceleration of the device 800, and a change in the temperature of the device 800. Sensor assembly 814 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 816 is configured to facilitate communications between the apparatus 800 and other devices in a wired or wireless manner. The device 800 may access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 816 receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 816 further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
In an exemplary embodiment, the apparatus 800 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components for performing the above-described methods.
In an exemplary embodiment, a non-transitory computer-readable storage medium comprising instructions, such as the memory 804 comprising instructions, executable by the processor 820 of the device 800 to perform the above-described method is also provided. For example, the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (10)
1. A front-end interface generation method is characterized by comprising the following steps:
under the condition that a first template analyzer obtaining request of an application platform is received, sending a first template analyzer to the application platform so that the application platform loads the first template analyzer, wherein the first template analyzer is used for reading variable values and analyzing template statements;
receiving a template calling request from the application platform, wherein the template calling request comprises identification information of a template;
acquiring a front-end interface template in a JSON format corresponding to the identification information;
sending the JSON format front-end interface template to the application platform so that the application platform can adopt the first template analyzer to analyze the JSON format front-end interface template to obtain a first visual interface;
the method further comprises the following steps:
modifying the first template parser to a second template parser;
and under the condition of receiving a second template analyzer acquisition request of the application platform, sending the second template analyzer to the application platform so as to load the second template analyzer on the application platform, wherein the second template analyzer can analyze the JSON format front-end interface template into a second visual interface, and the first visual interface and the second visual interface are different expression forms of the JSON format front-end interface template.
2. The method of claim 1, further comprising:
generating a front-end interface template in a hypertext markup language (HTML) format according to the universal component selected by the user on a template editing page;
and converting the front-end interface template in the HTML format into the front-end interface template in the JSON format, and storing the front-end interface template in the JSON format and the corresponding identification information thereof into a database.
3. The method of claim 2, further comprising:
defining the universal component on a template editing page; or
And after the front-end interface template in the JSON format is called, defining the general assembly through a callback function.
4. A front-end interface generation method is characterized by comprising the following steps:
sending a first template analyzer acquisition request to a front-end automation platform;
loading a first template analyzer sent by the front-end automation platform under the condition of receiving the first template analyzer, wherein the first template analyzer is used for reading variable values and analyzing template statements;
sending a template calling request to the front-end automation platform, wherein the template calling request comprises identification information of a template;
receiving a front-end interface template in a JSON format corresponding to the identification information and sent by the front-end automation platform;
adopting the first template analyzer to analyze the JSON format front-end interface template to obtain a first visual interface;
the method further comprises the following steps:
sending a second template analyzer acquisition request to the front-end automation platform;
and loading a second template analyzer under the condition of receiving the second template analyzer sent by the front-end automation platform, wherein the second template analyzer can analyze the JSON format front-end interface template into a second visual interface, and the first visual interface and the second visual interface are different expression forms of the JSON format front-end interface template.
5. A front-end interface generating apparatus, comprising:
the device comprises a first template analyzer sending module, a first template analyzer sending module and a second template analyzer sending module, wherein the first template analyzer sending module is used for sending a first template analyzer to an application platform under the condition that a first template analyzer obtaining request of the application platform is received, so that the first template analyzer is loaded on the application platform, and the first template analyzer is used for reading variable values and analyzing template statements;
the template calling request receiving module is used for receiving a template calling request from the application platform, wherein the template calling request comprises identification information of a template;
a JSON format front-end interface template obtaining module, configured to obtain a JSON format front-end interface template corresponding to the identification information;
a JSON-formatted front-end interface template sending module, configured to send the JSON-formatted front-end interface template to the application platform, so that the application platform can parse the JSON-formatted front-end interface template by using the first template parser to obtain a first visual interface;
the device further comprises:
the template analyzer modification module is used for modifying the first template analyzer into a second template analyzer;
and the second template parser sending module is used for sending a second template parser to the application platform under the condition that a second template parser obtaining request of the application platform is received, so that the application platform loads the second template parser, the second template parser can parse the JSON format front-end interface template into a second visual interface, and the first visual interface and the second visual interface are different expression forms of the JSON format front-end interface template.
6. The apparatus of claim 5, further comprising:
the front-end interface template generating module in the HTML format is used for editing a page on a template and generating a front-end interface template in the HTML format of the hypertext markup language according to the universal component selected by a user;
and the JSON format front-end interface template generating module is used for converting the HTML format front-end interface template into the JSON format front-end interface template and storing the JSON format front-end interface template and the corresponding identification information thereof into a database.
7. The apparatus of claim 6, further comprising:
the definition module is used for editing a page on a template and defining the general component; or
And after the front-end interface template in the JSON format is called, defining the general assembly through a callback function.
8. A front-end interface generating apparatus, comprising:
the first template analyzer acquisition request sending module is used for sending a first template analyzer acquisition request to a front-end automation platform;
the first template analyzer loading module is used for loading a first template analyzer under the condition of receiving the first template analyzer sent by the front-end automation platform, and the first template analyzer is used for reading variable values and analyzing template statements;
the template calling request sending module is used for sending a template calling request to the front-end automation platform, wherein the template calling request comprises identification information of a template;
a JSON format front-end interface template receiving module, configured to receive a JSON format front-end interface template corresponding to the identification information and sent by the front-end automation platform;
the JSON format front-end interface template analysis module is used for analyzing the JSON format front-end interface template by adopting the first template analyzer to obtain a first visual interface;
the device further comprises:
the second template analyzer acquisition request sending module is used for sending a second template analyzer acquisition request to the front-end automation platform;
and the second template analyzer loading module is used for loading the second template analyzer under the condition of receiving the second template analyzer sent by the front-end automation platform, the second template analyzer can analyze the JSON format front-end interface template into a second visual interface, and the first visual interface and the second visual interface are different expression forms of the JSON format front-end interface template.
9. A front-end interface generating apparatus, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
under the condition that a first template analyzer obtaining request of an application platform is received, sending a first template analyzer to the application platform so that the application platform loads the first template analyzer, wherein the first template analyzer is used for reading variable values and analyzing template statements;
receiving a template calling request from the application platform, wherein the template calling request comprises identification information of a template;
acquiring a front-end interface template in a JSON format corresponding to the identification information;
sending the JSON format front-end interface template to the application platform so that the application platform can adopt the first template analyzer to analyze the JSON format front-end interface template to obtain a first visual interface;
the processor is further configured to:
modifying the first template parser to a second template parser;
and under the condition of receiving a second template analyzer acquisition request of the application platform, sending the second template analyzer to the application platform so as to load the second template analyzer on the application platform, wherein the second template analyzer can analyze the JSON format front-end interface template into a second visual interface, and the first visual interface and the second visual interface are different expression forms of the JSON format front-end interface template.
10. A front-end interface generating apparatus, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to:
sending a first template analyzer acquisition request to a front-end automation platform;
loading a first template analyzer sent by the front-end automation platform under the condition of receiving the first template analyzer, wherein the first template analyzer is used for reading variable values and analyzing template statements;
sending a template calling request to the front-end automation platform, wherein the template calling request comprises identification information of a template;
receiving a front-end interface template in a JSON format corresponding to the identification information and sent by the front-end automation platform;
adopting the first template analyzer to analyze the JSON format front-end interface template to obtain a first visual interface;
the processor is further configured to:
sending a second template analyzer acquisition request to the front-end automation platform;
and loading a second template analyzer under the condition of receiving the second template analyzer sent by the front-end automation platform, wherein the second template analyzer can analyze the JSON format front-end interface template into a second visual interface, and the first visual interface and the second visual interface are different expression forms of the JSON format front-end interface template.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610905421.8A CN106569800B (en) | 2016-10-17 | 2016-10-17 | Front-end interface generation method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610905421.8A CN106569800B (en) | 2016-10-17 | 2016-10-17 | Front-end interface generation method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106569800A CN106569800A (en) | 2017-04-19 |
| CN106569800B true CN106569800B (en) | 2020-10-23 |
Family
ID=58533077
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610905421.8A Active CN106569800B (en) | 2016-10-17 | 2016-10-17 | Front-end interface generation method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106569800B (en) |
Families Citing this family (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107562496B (en) * | 2017-07-21 | 2021-03-30 | 创新先进技术有限公司 | Method and device for page configuration and page display |
| CN107943455A (en) * | 2017-08-11 | 2018-04-20 | 成都萌想科技有限责任公司 | A kind of list rendering system based on JSON data formats |
| CN107765956B (en) * | 2017-08-30 | 2021-02-26 | Oppo广东移动通信有限公司 | User interface editing method, device, terminal and computer readable storage medium |
| CN107818143B (en) * | 2017-10-16 | 2021-12-17 | 中国银联股份有限公司 | Page configuration and generation method and device |
| CN107798084A (en) * | 2017-10-17 | 2018-03-13 | 广东广业开元科技有限公司 | The visual edit generation system and device of a kind of web front-end page |
| CN107704243B (en) * | 2017-10-19 | 2020-12-01 | 用友网络科技股份有限公司 | Front-end interface construction method and device, computer equipment and storage medium |
| CN107861725B (en) * | 2017-11-22 | 2020-12-22 | 北京酷我科技有限公司 | iOS data reverse automatic analysis strategy |
| CN108228169B (en) * | 2017-12-08 | 2020-10-13 | 平安科技（深圳）有限公司 | Chart making method, device, equipment and medium based on eCharts tool |
| CN108256124A (en) * | 2018-02-26 | 2018-07-06 | 成都步速者科技股份有限公司 | Method for building website, device, server and storage medium |
| CN109240688A (en) * | 2018-08-13 | 2019-01-18 | 重庆金融资产交易所有限责任公司 | Interface development method, electronic device and readable storage medium storing program for executing |
| CN110083790A (en) * | 2019-04-30 | 2019-08-02 | 珠海随变科技有限公司 | Page editing method, page output method, device, computer equipment and medium |
| CN110286896B (en) * | 2019-06-28 | 2023-03-31 | 百度在线网络技术（北京）有限公司 | Visual editing method, device, equipment and storage medium |
| CN112114805B (en) * | 2020-08-27 | 2023-05-12 | 长沙市到家悠享网络科技有限公司 | Page generation method, device and equipment |
| CN112099793B (en) * | 2020-09-25 | 2023-08-22 | 成都极米科技股份有限公司 | Interface generation method and device, electronic equipment and storage medium |
| CN115587271A (en) * | 2022-09-29 | 2023-01-10 | 花瓣云科技有限公司 | Page management method, electronic equipment and medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101729590A (en) * | 2008-10-15 | 2010-06-09 | 北大方正集团有限公司 | Method, system and device for providing web page |
| CN102446221A (en) * | 2011-12-22 | 2012-05-09 | 南京联创科技集团股份有限公司 | Dynamic tree structured directory retrieval method in BS (browser/server) structure software |
| CN103544024A (en) * | 2013-11-12 | 2014-01-29 | 深圳如果技术有限公司 | Method and system for generating browser page and terminal device |
| CN104216926A (en) * | 2013-06-05 | 2014-12-17 | 上海缪思信息科技有限公司 | Page generating method, template engine and processor |
| CN105824787A (en) * | 2016-03-15 | 2016-08-03 | 江苏中威科技软件系统有限公司 | Control method and system for dynamic configuration of HTML template |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7191395B2 (en) * | 2002-03-12 | 2007-03-13 | International Business Machines Corporation | Method and system for stylesheet-centric editing |
| CN102455903B (en) * | 2010-10-29 | 2014-12-10 | 卓望数码技术（深圳）有限公司 | Method for generating user application interface |
| CN102567422A (en) * | 2010-12-27 | 2012-07-11 | 北大方正集团有限公司 | Page display method and equipment |
| CA2860374C (en) * | 2011-12-23 | 2020-11-17 | Airstrip Ip Holdings, Llc | Systems and methods for developing multi-platform applications for computing devices |
| US20150317156A1 (en) * | 2014-05-01 | 2015-11-05 | Ca, Inc. | Systems and Methods for Automated Generation of Interactive Documentation Based on Web Application Description Language Files |
-
2016
- 2016-10-17 CN CN201610905421.8A patent/CN106569800B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101729590A (en) * | 2008-10-15 | 2010-06-09 | 北大方正集团有限公司 | Method, system and device for providing web page |
| CN102446221A (en) * | 2011-12-22 | 2012-05-09 | 南京联创科技集团股份有限公司 | Dynamic tree structured directory retrieval method in BS (browser/server) structure software |
| CN104216926A (en) * | 2013-06-05 | 2014-12-17 | 上海缪思信息科技有限公司 | Page generating method, template engine and processor |
| CN103544024A (en) * | 2013-11-12 | 2014-01-29 | 深圳如果技术有限公司 | Method and system for generating browser page and terminal device |
| CN105824787A (en) * | 2016-03-15 | 2016-08-03 | 江苏中威科技软件系统有限公司 | Control method and system for dynamic configuration of HTML template |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106569800A (en) | 2017-04-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106569800B (en) | Front-end interface generation method and device | |
| US10705780B2 (en) | Method, device, and storage medium for displaying application page | |
| CN109032606B (en) | Native application compiling method and device and terminal | |
| US10909203B2 (en) | Method and device for improving page display effect via execution, conversion and native layers | |
| CN107423106B (en) | Method and apparatus for supporting multi-frame syntax | |
| CN110874217B (en) | Interface display method and device for quick application and storage medium | |
| CN106547547B (en) | data acquisition method and device | |
| CN105808305B (en) | Static resource loading method and device | |
| CN110928543A (en) | Page processing method and device and storage medium | |
| CN104063424B (en) | Web page picture shows method and demonstration device | |
| CN105808304B (en) | Code deployment method, device and system | |
| CN110704030A (en) | Interface configuration information generation method and device, electronic equipment and storage medium | |
| US11210449B2 (en) | Page display method and device and storage medium | |
| CN111079040B (en) | Resource sniffing method, device, terminal, server and storage medium | |
| CN105468606B (en) | Webpage saving method and device | |
| CN111695064B (en) | Buried point loading method and device | |
| CN107679205B (en) | Multimedia data playing method and device, computer equipment and storage medium | |
| CN114025317B (en) | Method, device, server, terminal and storage medium for spreading multimedia resources | |
| CN112486617B (en) | Ciphertext data processing architecture, method, apparatus and machine readable medium | |
| CN115686590A (en) | Firmware upgrading method and device, computing equipment and storage medium | |
| CN114546436A (en) | Micro front-end service updating method and device, electronic equipment and storage medium | |
| CN112860625A (en) | Data acquisition method, data storage method, device, equipment and storage medium | |
| CN112182449A (en) | Page loading method and device, electronic equipment and storage medium | |
| CN111131000B (en) | Information transmission method, device, server and terminal | |
| CN110659081B (en) | File processing method and device for program object and electronic equipment |
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 |