CN106293671B - Method and device for generating component template - Google Patents
Method and device for generating component template Download PDFInfo
- Publication number
- CN106293671B CN106293671B CN201510303258.3A CN201510303258A CN106293671B CN 106293671 B CN106293671 B CN 106293671B CN 201510303258 A CN201510303258 A CN 201510303258A CN 106293671 B CN106293671 B CN 106293671B
- Authority
- CN
- China
- Prior art keywords
- template
- master page
- attribute information
- identifier
- description file
- 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
Abstract
The invention relates to a method and a device for generating a component template, which comprises the following steps: detecting whether a description file for generating a target component template is received; when the description file is received, whether a master page corresponding to the template identifier exists locally or not is searched; and when a master page corresponding to the template identifier exists locally, generating a target assembly template according to the master page and the attribute information. In this way, when the component template corresponding to the template identifier needs to be generated, since the master page corresponding to the template identifier is already generated, the user only needs to write the description file of the component template corresponding to the template identifier, wherein the code amount of the description file is very low. That is, each time a component template needs to be generated, the user only needs to write a description file of the component template with a low code amount. Therefore, the invention can save a large amount of human resources and reduce the labor cost.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a method and a device for generating a component template.
Background
With the rapid development of technology, components have been indispensable application elements in web pages, which are generally composed of a piece of HTML (Hypertext Markup Language) or JS (JavaScript, interpreted scripting Language) code; components are currently typically generated through component templates.
In the field of web pages, various components are used, and since element types are precisely described in the components, any component needs to be generated by a component template corresponding to the component.
However, each component template needs to be written manually, and because the code amount for writing one component template is very large, when the number of component templates needing to be written is very large, very large human resources are required, and the labor cost is high.
Disclosure of Invention
To overcome the problems in the related art, the present invention provides a method and an apparatus for generating a component template.
According to a first aspect of embodiments of the present invention, there is provided a method of generating a component template, the method comprising:
detecting whether a description file for generating a target component template is received; the description file comprises a template identifier of the target assembly template and at least one attribute message;
when the description file is received, searching whether a master page corresponding to the template identifier exists locally; the master page comprises at least one attribute information bit;
and when a master page corresponding to the template identifier exists locally, generating a target assembly template according to the master page and the attribute information.
Further, the method further comprises:
acquiring a reference assembly template corresponding to the template identifier;
acquiring attribute information bits in the reference component template;
deleting the attribute information in the attribute information bit;
and filling position occupying information in the attribute information position to obtain a master page corresponding to the template identifier.
Wherein, the searching whether a master page corresponding to the template identifier exists locally comprises:
acquiring a corresponding relation between a preset template mark and a mark of a master page;
searching whether the identification of the master page corresponding to the template identification exists in the corresponding relation;
when the identification of the master page corresponding to the template identification is found in the corresponding relation, determining the master page corresponding to the found identification of the master page as the master page corresponding to the template identification;
and when the identification of the master page corresponding to the template identification is not found in the corresponding relation, determining that the master page corresponding to the template identification does not exist locally.
Wherein the generating a target component template according to the master page and the attribute information comprises:
for each attribute information in the description file, acquiring an attribute information bit of the attribute information in the master page;
deleting the placeholder information in the acquired attribute information bits;
and filling the attribute information into the acquired attribute information bits to realize generation of the target component template.
Wherein the detecting whether the description file for generating the target component template is received comprises:
detecting whether a description file which is input by a user and is used for generating a target component template is received;
or;
and detecting whether a description file which is sent by other equipment and is used for generating the target component template is received.
According to a second aspect of embodiments of the present invention, there is provided an apparatus for generating a component template, the apparatus comprising:
the detection module is used for detecting whether a description file for generating the target component template is received or not; the description file comprises a template identifier of the target assembly template and at least one attribute message;
the searching module is used for searching whether a master page corresponding to the template identifier exists locally or not when the description file is received; the master page comprises at least one attribute information bit;
and the generating module is used for generating a target component template according to the master page and the attribute information when the master page corresponding to the template identifier exists locally.
Further, the apparatus further comprises:
the first acquisition module is used for acquiring a reference assembly template corresponding to the template identifier;
the second acquisition module is used for acquiring the attribute information bits in the reference component template;
the deleting module is used for deleting the attribute information in the attribute information bit;
and the filling module is used for filling the position occupied information in the attribute information position to obtain a master page corresponding to the template identifier.
Wherein the search module comprises:
the first acquisition unit is used for acquiring the corresponding relation between the preset template mark and the mark of the master page;
a searching unit, configured to search whether an identifier of the master page corresponding to the template identifier exists in the correspondence;
a first determining unit, configured to determine, when the identifier of the master page corresponding to the template identifier is found in the correspondence, the master page corresponding to the found identifier of the master page as the master page corresponding to the template identifier;
and a second determining unit, configured to determine that there is no master page corresponding to the template identifier locally when the identifier of the master page corresponding to the template identifier is not found in the correspondence.
Wherein the generating module comprises:
a second obtaining unit, configured to obtain, for each piece of attribute information in the description file, an attribute information bit of the attribute information in the master page;
a deleting unit, configured to delete the placeholder information in the obtained attribute information bits;
and the filling unit is used for filling the attribute information into the acquired attribute information bits so as to generate the target component template.
Wherein the detection module comprises:
the system comprises a first detection unit, a second detection unit and a control unit, wherein the first detection unit is used for detecting whether a description file which is input by a user and is used for generating a target component template is received;
and the second detection unit is used for detecting whether the description file which is sent by other equipment and used for generating the target component template is received.
The technical scheme provided by the embodiment of the invention can have the following beneficial effects: in the invention, a master page corresponding to a template identifier is generated in advance according to an assembly template corresponding to the template identifier, when a target assembly template corresponding to the template identifier needs to be generated, only a description file of the target assembly template needs to be acquired, and then the target assembly template is generated according to the master page corresponding to the template identifier and the description file.
The master page corresponding to the template identifier is generated in advance only once, and then the master page can be utilized whenever the component template corresponding to the template identifier needs to be generated. Therefore, the user only needs to write the description file of the component template corresponding to the template identification, wherein the code amount of the description file is low. That is, each time a component template needs to be generated, the user only needs to write a description file of the component template with a low code amount. Compared with the prior art that the assembly template is completely compiled by a user, the embodiment of the invention can save a large amount of human resources and reduce the labor cost.
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 invention, as claimed.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
FIG. 1 is a flow diagram illustrating a method of generating a component template in accordance with an exemplary embodiment.
FIG. 2 is a flow diagram illustrating a method of generating a component template in accordance with an exemplary embodiment.
FIG. 3 is a flow diagram illustrating a method of generating a component template in accordance with an exemplary embodiment.
FIG. 4 is a block diagram illustrating an apparatus for generating a component template 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 embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the invention, as detailed in the appended claims.
FIG. 1 is a flow diagram illustrating a method of generating a component template, as shown in FIG. 1, including the following steps, according to an exemplary embodiment.
In step S101, detecting whether a description file for generating a target component template is received;
the description file comprises a template identifier of the target assembly template and at least one attribute message;
the component templates are used for generating components, the types of the components are various, such as button-type components and input-type components, each type of component can only be generated by using the component template of the type corresponding to the component, for example, the button-type components can only be generated by using the button-type component templates, and the input-type components can only be generated by using the input-type component templates.
Therefore, the template identifier may be a type of the component template, for example, the template identifier of the button-type component template may be a button, and the template identifier of the input-type component template may be an input.
The attribute information of the component template includes: the type, rendering mode, size and dimension of the components which can be generated according to the component template, and the like.
The description file may be a description file sent by another device or a description file locally input by a user, and therefore, this step may specifically be: detecting whether a description file which is input by a user and is used for generating a target component template is received; or detecting whether a description file which is sent by other equipment and is used for generating the target component template is received.
When the description file is received, in step S102, whether a master page corresponding to the template identifier exists locally is searched for;
the master page comprises at least one attribute information bit; the attribute information bits may be populated with attribute information. An assembly template is obtained when attribute information is filled in the bits of the master page and the attribute information.
In the embodiment of the present invention, a master page corresponding to the template identifier needs to be generated in advance and stored in a local preset master page library.
Specifically, the step of generating the master page corresponding to the template identifier may be specifically implemented by the following process, including:
11) acquiring a reference assembly template corresponding to the template identification;
specifically, one component template is selected from the generated component templates corresponding to the template identifier, the selected component template is copied, and the copied component template is used as a reference component template.
For example, assume that the reference component template can be:
<button type＝“button”class＝“btn btn-success btn-sm”>{{button.text}}</button>。
12) acquiring attribute information bits in the reference assembly template;
after the reference assembly template corresponding to the template identifier is obtained, the reference assembly template can be displayed in a display screen, and a user can select an attribute information bit in the reference assembly template; thus, in this step, the user's selected attribute information bits in the reference component template may be received.
For example, the user may select, from the above-mentioned reference component template, a position where a button in "button" is located as an attribute information bit, and a position where btn btn-success btn-sm in "btn btn-success btn-sm" is located as an attribute information bit; therefore, in this step, the attribute information bit selected by the user can be received.
13) Deleting the attribute information in the attribute information bit;
for example, deleting attribute information button in type ═ button ", and deleting attribute information btn-success btn-sm in the genus class ═ btn-success btn-sm", results in a deleted component template: the method includes the steps of { { button.
14) And filling the acquired attribute information bits with the position occupying information to obtain the master page corresponding to the template identifier.
The placeholder information may be a placeholder, etc.
For example, the component template after deletion: filling the position occupation information [ type ] in the attribute information bit "" of < button type ═ and { { button.text } } type } and filling the position occupation information [ type ] ] in the attribute information bit "" of the class ═ to obtain a master page: < button type ═ type ] ] "class [ [ class ] ]" { { button.
After the master page corresponding to the template identifier is obtained, when the component template corresponding to the template identifier needs to be generated, the component template corresponding to the template identifier can be obtained only by filling the attribute information of the component template corresponding to the template identifier into the attribute information bits in the master page.
Further, the master page corresponding to the template identifier is stored in a preset master page library, and the identifier of the master page corresponding to the template identifier and the template identifier are stored as a record in the corresponding relationship between the preset template identifier and the identifier of the master page.
When there is a master page corresponding to the template identifier locally, in step S103, a target component template is generated according to the master page and the attribute information contained in the description file.
And when the master page corresponding to the template identifier exists locally, acquiring the master page corresponding to the template identifier, and filling each attribute information in the description file into the attribute information bit in the master page to obtain the target assembly template.
When there is no master page corresponding to the template identifier, it indicates that no master page corresponding to the template identifier has been generated in advance, and therefore, the master page corresponding to the template identifier may be generated according to the flow 11) to 14) above, and then the target component template may be generated according to the generated master page corresponding to the template identifier and the attribute information included in the description file.
In the embodiment shown in fig. 1 of the present invention, a master page corresponding to a template identifier is generated in advance according to an assembly template corresponding to the template identifier, when an object assembly template corresponding to the template identifier needs to be generated, only a description file of the object assembly template needs to be acquired, and then the object assembly template is generated according to the master page corresponding to the template identifier and the description file. The master page corresponding to the template identifier is generated in advance only once, and then the master page can be utilized whenever the component template corresponding to the template identifier needs to be generated. Therefore, the user only needs to write the description file of the component template corresponding to the template identification, wherein the code amount of the description file is low. That is, each time a component template needs to be generated, the user only needs to write a description file of the component template with a low code amount. Compared with the prior art that the assembly template is completely compiled by a user, the embodiment of the invention can save a large amount of human resources and reduce the labor cost.
In another embodiment of the present invention, referring to fig. 2, step S102 includes:
in step S201, a correspondence between a preset template identifier and an identifier of a master page is obtained;
the correspondence is set locally in advance by the user.
In step S202, whether an identifier of the master page corresponding to the template identifier in the description file exists is searched for in the correspondence;
specifically, one record in the correspondence relationship, which includes the template identifier and the identifier of the master page, is obtained, the template identifier in the description file is compared with the template identifier in the record, and if the template identifier in the description file is the same as the template identifier in the record, the identifier of the master page in the record is determined as the identifier of the master page corresponding to the template identifier in the description file; if the template identification in the description file is different from the template identification in the record, acquiring the next record in the corresponding relationship; continuing to execute the steps until the last record is obtained, and if the template identifier in the description file is the same as the template identifier in the last record, determining the identifier of the master page in the last record as the identifier of the master page corresponding to the template identifier in the description file; and if the template identification in the description file is different from the template identification in the last record, determining that the corresponding relation does not have the identification of the master page corresponding to the template identification in the description file.
When the identifier of the master page corresponding to the template identifier in the description file is found in the corresponding relationship, in step S203, determining the master page corresponding to the found identifier of the master page as the master page corresponding to the template identifier in the description file;
the corresponding relation is synchronous with the master page library, namely, when a master page corresponding to a template identifier is newly added in the master page library, the identifier of the newly added master page and the template identifier of the newly added master page are taken as a record and added into the corresponding relation; when a master page is deleted from the master page library, a record including an identifier of the master page is deleted from the correspondence. That is, the master page corresponding to the identifier of the master page in each record in the corresponding relationship is stored in a preset master page library; the identifier of each master page in the preset master page library is stored in one record in the corresponding relationship.
Therefore, in this step, when the identifier of the master page corresponding to the template identifier in the description file is found in the correspondence, it indicates that the master page corresponding to the template identifier in the description file is stored in the preset master page library, that is, it is determined that the master page corresponding to the template identifier in the description file exists locally, and the master page corresponding to the found identifier of the master page is determined as the master page corresponding to the template identifier in the description file. When the identification of the master page corresponding to the template identification in the description file is not found in the corresponding relationship, it indicates that the master page corresponding to the template identification in the description file is not stored in the preset master page library, that is, it is determined that the master page corresponding to the template identification in the description file does not exist locally,
when the identifier of the master page corresponding to the template identifier in the description file is not found in the correspondence relationship, in step S204, it is determined that the master page corresponding to the template identifier in the description file does not exist locally.
In another embodiment of the present invention, referring to fig. 3, step S103 includes:
in step S301, for each attribute information in the description file, an attribute information bit of the attribute information in the master page is acquired;
for each attribute information in the description file, acquiring an attribute identifier corresponding to the attribute information, searching the position occupied by the same attribute identifier in the master page, and taking the position occupied by the same attribute identifier as an attribute information bit for filling the attribute information;
for example, assume that the description file is:
in the description file, the attribute information is type, botton in button and btn btn-success in classx, the attribute mark corresponding to the attribute information button is type, and the attribute mark corresponding to the attribute information btn-success is classx;
assume that the acquired page of the master is:
<button type＝“[[type]]”class＝“[[classx]]”>{{button.text}}</button>；
and finding the occupancy information which is the same as the attribute identification type in the master page, finding the occupancy information which is the same as the attribute identification type [ [ type ] ], and taking the position of the occupancy information which is the same as the attribute identification type [ [ type ] ] as an attribute information bit for filling the attribute information botton.
And searching the occupancy information which is the same as the attribute identifier classx in the master page, searching the occupancy information which is the same as the attribute identifier classx [ [ classx ] ], and taking the position of the occupancy information which is the same as the attribute identifier classx [ [ classx ] ] as an attribute information bit for filling the attribute information btn btn-success.
In step S302, the placeholder information in the attribute information bit is deleted;
for example, for a master page:
<button type＝“[[type]]”class＝“[[classx]]”>{{button.text}}</button>；
the placeholder information "[ [ type ] ]" in the master page is deleted, and the placeholder information "[ [ classx ] ]" in the master page is deleted.
Obtaining a master page with the occupied information deleted: the method comprises the following steps of (1) setting a button type ═ class { { button.
In step S303, the attribute information is filled in the attribute information bits.
To enable generation of a target component template.
For example, the attribute information button and btn btn-success are respectively filled into the master page with the placeholder information deleted, wherein the master page has the placeholder information deleted, and the type of the button is ═ class ═ and { { button. And obtaining a target component template (button type, class, btn btn-success, > { { button.
FIG. 4 is a block diagram illustrating an apparatus for generating a component template in accordance with an example embodiment. Referring to fig. 4, the apparatus includes:
the detection module 11 is configured to detect whether a description file for generating a target component template is received; the description file comprises a template identifier of the target assembly template and at least one attribute message;
the searching module 12 is configured to search whether a master page corresponding to the template identifier exists locally when the description file is received; the master page comprises at least one attribute information bit;
and the generating module 13 is configured to generate a target component template according to the master page and the attribute information when the master page corresponding to the template identifier exists locally.
In the embodiment shown in fig. 4 of the present invention, a master page corresponding to a template identifier is generated in advance according to a component template corresponding to the template identifier, when an object component template corresponding to the template identifier needs to be generated, only a description file of the object component template needs to be acquired, and then the object component template is generated according to the master page corresponding to the template identifier and the description file. The master page corresponding to the template identifier is generated in advance only once, and then the master page can be utilized whenever the component template corresponding to the template identifier needs to be generated. Therefore, the user only needs to write the description file of the component template corresponding to the template identification, wherein the code amount of the description file is low. That is, each time a component template needs to be generated, the user only needs to write a description file of the component template with a low code amount. Compared with the prior art that the assembly template is completely compiled by a user, the embodiment of the invention can save a large amount of human resources and reduce the labor cost.
Further, the apparatus further comprises:
the first acquisition module is used for acquiring a reference assembly template corresponding to the template identifier;
the second acquisition module is used for acquiring the attribute information bits in the reference component template;
the deleting module is used for deleting the attribute information in the attribute information bit;
and the filling module is used for filling the position occupied information in the attribute information position to obtain a master page corresponding to the template identifier.
Wherein, the searching module 12 comprises:
the first acquisition unit is used for acquiring the corresponding relation between the preset template mark and the mark of the master page;
a searching unit, configured to search whether an identifier of the master page corresponding to the template identifier exists in the correspondence;
a first determining unit, configured to determine, when the identifier of the master page corresponding to the template identifier is found in the correspondence, the master page corresponding to the found identifier of the master page as the master page corresponding to the template identifier;
and a second determining unit, configured to determine that there is no master page corresponding to the template identifier locally when the identifier of the master page corresponding to the template identifier is not found in the correspondence.
Wherein the generating module 13 includes:
a second obtaining unit, configured to obtain, for each piece of attribute information in the description file, an attribute information bit of the attribute information in the master page;
a deleting unit, configured to delete the placeholder information in the obtained attribute information bits;
and the filling unit is used for filling the attribute information into the acquired attribute information bits so as to generate the target component template.
Wherein the detection module 11 comprises:
the system comprises a first detection unit, a second detection unit and a control unit, wherein the first detection unit is used for detecting whether a description file which is input by a user and is used for generating a target component template is received;
and the second detection unit is used for detecting whether the description file which is sent by other equipment and used for generating the target component template is received.
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.
Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the invention and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.
It will be understood that the invention 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 invention is limited only by the appended claims.
Claims (8)
1. A method of generating a component template, the method comprising:
detecting whether a description file for generating a target component template is received; the description file comprises a template identifier of the target assembly template and at least one attribute message;
when the description file is received, searching whether a master page corresponding to the template identifier exists locally; the master page comprises at least one attribute information bit;
when a master page corresponding to the template identifier exists locally, generating a target assembly template according to the master page and the attribute information;
when the master page corresponding to the template identification does not exist locally, acquiring a reference assembly template corresponding to the template identification;
acquiring attribute information bits in the reference component template;
deleting the attribute information in the attribute information bit;
filling position occupying information in the attribute information position to obtain a master page corresponding to the template mark, and generating a target assembly template according to the master page and the attribute information.
2. The method of claim 1, wherein said finding whether there is a master page corresponding to the template identifier locally comprises:
acquiring a corresponding relation between a preset template mark and a mark of a master page;
searching whether the identification of the master page corresponding to the template identification exists in the corresponding relation;
when the identification of the master page corresponding to the template identification is found in the corresponding relation, determining the master page corresponding to the found identification of the master page as the master page corresponding to the template identification;
and when the identification of the master page corresponding to the template identification is not found in the corresponding relation, determining that the master page corresponding to the template identification does not exist locally.
3. The method of claim 1, wherein generating a target component template from the master page and the attribute information comprises:
for each attribute information in the description file, acquiring an attribute information bit of the attribute information in the master page;
deleting the placeholder information in the acquired attribute information bits;
and filling the attribute information into the acquired attribute information bits to realize generation of the target component template.
4. The method of claim 1, wherein the detecting whether a description file for generating a target component template is received comprises:
detecting whether a description file which is input by a user and is used for generating a target component template is received;
or;
and detecting whether a description file which is sent by other equipment and is used for generating the target component template is received.
5. An apparatus for generating a component template, the apparatus comprising:
the detection module is used for detecting whether a description file for generating the target component template is received or not; the description file comprises a template identifier of the target assembly template and at least one attribute message;
the searching module is used for searching whether a master page corresponding to the template identifier exists locally or not when the description file is received; the master page comprises at least one attribute information bit;
the generating module is used for generating a target component template according to the master page and the attribute information when the master page corresponding to the template identifier exists locally;
the first acquisition module is used for acquiring a reference assembly template corresponding to the template identifier when a master page corresponding to the template identifier does not exist locally;
the second acquisition module is used for acquiring the attribute information bits in the reference component template;
the deleting module is used for deleting the attribute information in the attribute information bit;
and the filling module is used for filling the position occupation information in the attribute information position to obtain a master page corresponding to the template identifier, and generating the target assembly template according to the master page and the attribute information.
6. The apparatus of claim 5, wherein the lookup module comprises:
the first acquisition unit is used for acquiring the corresponding relation between the preset template mark and the mark of the master page;
a searching unit, configured to search whether an identifier of the master page corresponding to the template identifier exists in the correspondence;
a first determining unit, configured to determine, when the identifier of the master page corresponding to the template identifier is found in the correspondence, the master page corresponding to the found identifier of the master page as the master page corresponding to the template identifier;
and a second determining unit, configured to determine that there is no master page corresponding to the template identifier locally when the identifier of the master page corresponding to the template identifier is not found in the correspondence.
7. The apparatus of claim 5, wherein the generating module comprises:
a second obtaining unit, configured to obtain, for each piece of attribute information in the description file, an attribute information bit of the attribute information in the master page;
a deleting unit, configured to delete the placeholder information in the obtained attribute information bits;
and the filling unit is used for filling the attribute information into the acquired attribute information bits so as to generate the target component template.
8. The apparatus of claim 5, wherein the detection module comprises:
the system comprises a first detection unit, a second detection unit and a control unit, wherein the first detection unit is used for detecting whether a description file which is input by a user and is used for generating a target component template is received;
and the second detection unit is used for detecting whether the description file which is sent by other equipment and used for generating the target component template is received.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510303258.3A CN106293671B (en) | 2015-06-04 | 2015-06-04 | Method and device for generating component template |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510303258.3A CN106293671B (en) | 2015-06-04 | 2015-06-04 | Method and device for generating component template |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106293671A CN106293671A (en) | 2017-01-04 |
| CN106293671B true CN106293671B (en) | 2020-03-13 |
Family
ID=57656676
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510303258.3A Active CN106293671B (en) | 2015-06-04 | 2015-06-04 | Method and device for generating component template |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106293671B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107203453B (en) * | 2017-05-23 | 2020-06-16 | 苏州浪潮智能科技有限公司 | Method and device for generating equipment view and electronic equipment |
| CN109799994B (en) * | 2019-01-14 | 2022-02-18 | 腾讯科技（武汉）有限公司 | Terminal component generation method and device |
| CN111399832B (en) * | 2020-03-06 | 2024-03-08 | 北京奇艺世纪科技有限公司 | Page editing method and device |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120102386A1 (en) * | 2010-10-20 | 2012-04-26 | Microsoft Corporation | Customization of Display Templates |
| CN102201009B (en) * | 2011-06-21 | 2013-02-27 | 深圳市凯立德科技股份有限公司 | Form generating method and device |
| CN103019684B (en) * | 2012-11-20 | 2016-03-16 | 北京思特奇信息技术股份有限公司 | A kind of method of the configuration service page based on dynamic template |
-
2015
- 2015-06-04 CN CN201510303258.3A patent/CN106293671B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN106293671A (en) | 2017-01-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10565293B2 (en) | Synchronizing DOM element references | |
| US9501458B2 (en) | Executing a populated code template to generate a browser-executable software program to present a web page as a mobile application | |
| CN109101425B (en) | Index point burying method and device for dynamic page AB test | |
| EP2924593A1 (en) | Method and apparatus for constructing documents | |
| US20160283204A1 (en) | Editing software products using text mapping files | |
| US20140164900A1 (en) | Appending content with annotation | |
| CN105824830B (en) | Method, client and equipment for displaying page | |
| CN103597469A (en) | Live browser tooling in an integrated development environment | |
| CN104281644A (en) | Filename information display method and device | |
| CN106933887A (en) | A kind of data visualization method and device | |
| US11074037B2 (en) | Voice broadcast method and apparatus | |
| CN106293671B (en) | Method and device for generating component template | |
| CN106648571B (en) | Method and device for calibrating application interface | |
| US9141867B1 (en) | Determining word segment boundaries | |
| CN103279457A (en) | Method and device for generating diagram based on Excel | |
| US10698653B2 (en) | Selecting multimodal elements | |
| CN105512096B (en) | A kind of optimization method and device based on font embedded in document | |
| CN113204401B (en) | Browser rendering method, terminal and storage medium | |
| US20160062601A1 (en) | Electronic device with touch screen and method for moving application functional interface | |
| CN107621951B (en) | View level optimization method and device | |
| CN104461310B (en) | A kind of page comparison method and system | |
| CN111428452B (en) | Annotation data storage method and device | |
| US20140337709A1 (en) | Method and apparatus for displaying web page | |
| US10176152B2 (en) | Method and system for assigning a content item as a link target to a managed object | |
| CN110874216B (en) | Complete code generation method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20200922 Address after: Grand Cayman Islands Patentee after: Innovative advanced technology Co.,Ltd. Address before: Grand Cayman Islands Patentee before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20200922 Address after: Grand Cayman Islands Patentee after: Advanced innovation technology Co.,Ltd. Address before: Grand Cayman Islands Patentee before: Alibaba Group Holding Ltd. |
|
| TR01 | Transfer of patent right |