CN113672214B

CN113672214B - Template sharing method and device

Info

Publication number: CN113672214B
Application number: CN202110806998.4A
Authority: CN
Inventors: 王佳佳; 魏灵峰; 周源
Original assignee: Weibo Internet Technology China Co Ltd
Current assignee: Weibo Internet Technology China Co Ltd
Priority date: 2021-07-16
Filing date: 2021-07-16
Publication date: 2024-04-05
Anticipated expiration: 2041-07-16
Also published as: CN113672214A

Abstract

The embodiment of the invention provides a template sharing method and a template sharing device, which realize that a front-end display page required by generating front-end data instead of front-end or back-end codes is modified by arranging at least one pre-created page template and an attribute template relation record at the front end and arranging an attribute page address relation record and a configuration page address relation record at the back end, so that the effects of sharing the front-end by a plurality of business parties and avoiding the need of re-online and regression test when generating a new display page are achieved, and the new display page can be previewed in real time.

Description

Template sharing method and device

Technical Field

The invention relates to the field of webpage development, in particular to a template sharing method and device.

Background

Existing front-end technology requires multiparty coordination when creating a new page, such as page code writing, page pattern design, text description, etc. It can be seen that page generation in the prior art is cumbersome and can be completed only by cooperation of multiple persons. When the existing front-end technology is applied specifically, each business party needs independent front-end service, and when different businesses need similar front-end display effects, only the front-end service can be developed respectively, and the vehicle is manufactured repeatedly, so that huge waste of resources is caused. The existing front-end technology mainly focuses on page display, an HTML page needs to be newly built at the front end when one page is added, and modification of page elements is completed by one online at each time, so that edition is frequently issued, and even if small modification is performed at one time, one regression test is performed on the whole project, so that a great amount of manpower resource consumption is caused. When the page effect is achieved, key information is acquired from a rear-end interface by the existing front-end technology, the front-end is responsible for constructing a main page structure, but the rear-end still needs to adapt to each page in a code writing mode, and when the page is changed, the front-end code is required to be on line even if the front-end code is not required to be on line. The prior front-end technology only makes simple data binding when using the template, and replaces the data of the back-end to the front-end page, but has a certain force to be not apprehended when facing to complex use scenes and style modification problems. Existing front-end technology requires that the effect of the page be seen after the page development is completed, either in a test environment or after an online deployment.

In carrying out the present invention, the applicant has found that at least the following problems exist in the prior art:

the front page cannot be dynamically generated, and when the front page is added or modified, the front page has to be re-online and retested.

Disclosure of Invention

The embodiment of the invention provides a template sharing method and a template sharing device, which are used for decoupling a page address from a display page through pre-creating a plurality of page templates and through corresponding relations among the page address, the template name, the page templates and configuration information, and dynamically generating the display page through obtaining the page templates and the configuration information corresponding to the display page, so that the problems that the front-end page needs to be re-online and regression testing is solved when the front-end page is added or modified.

In order to achieve the above object, in one aspect, an embodiment of the present invention provides a template sharing method, including:

when a page acquisition command aiming at a specific display page is received, analyzing a page address of the specific display page from the page acquisition command; the page address is used for accessing the display page through the Internet;

obtaining template attributes of a page template corresponding to the specific display page by inquiring a preset attribute page address relation record according to the analyzed page address;

Obtaining a page template corresponding to the specific display page by inquiring a pre-established attribute template relation record according to the template attribute of the page template corresponding to the specific display page; wherein the page template corresponding to the specific display page is one of at least one pre-created page template;

obtaining configuration information corresponding to the specific display page by inquiring a preset configuration page address relation record according to the analyzed page address;

generating the specific display page according to the page template and the configuration information corresponding to the specific display page;

wherein each page template in the at least one page template has different template attributes respectively; each page template is composed of components for generating a presentation page.

Further, before the page obtaining command for the specific display page is received and the page address is resolved from the page obtaining command, the method further comprises:

creating at least one page template, and setting a unique template attribute for each page template;

and storing the template attributes of each page template and the respective storage positions in a one-to-one correspondence manner in an attribute template relationship record.

Further, the creating at least one page template and setting a unique template attribute for each page template includes:

developing various page elements for page presentation as components;

and constructing page templates corresponding to the display requirements by using the components according to the specified at least one display requirement, and setting the unique template attribute of each page template.

acquiring page addresses, configuration information and template attributes corresponding to each display page;

the page address of each acquired display page and the template attribute are added into the attribute page address relation record according to a one-to-one correspondence;

and adding the acquired page addresses of the display pages and the configuration information into the configuration page address relation record according to a one-to-one correspondence.

Further, the generating the specific display page according to the page template and the configuration information corresponding to the specific display page includes:

acquiring an intersection set of the components recorded in the configuration information and the components recorded in the page template as a display component set;

Generating the specific display page according to the layout and the style of the display assembly set in the page template;

updating the layout and the style of the corresponding components in the specific display page according to the layout and the style of all or part of the components in the display component set recorded in the configuration information;

and displaying the data to be displayed in the corresponding components in the specific display page according to the binding relation between each component in the display component set and the data to be displayed, which are recorded in the configuration information.

In another aspect, an embodiment of the present invention provides a template sharing apparatus, including:

the page acquisition command receiving unit is used for analyzing the page address of the specific display page from the page acquisition command when the page acquisition command aiming at the specific display page is received; the page address is used for accessing the display page through the Internet;

the template attribute query unit is used for obtaining template attributes of the page template corresponding to the specific display page by querying a preset attribute page address relation record according to the analyzed page address;

the page template acquisition unit is used for acquiring the page template corresponding to the specific display page by inquiring a preset attribute template relation record according to the template attribute of the page template corresponding to the specific display page; wherein the page template corresponding to the specific display page is one of at least one pre-created page template;

The configuration information acquisition unit is used for acquiring configuration information corresponding to the specific display page by inquiring a preset configuration page address relation record according to the analyzed page address;

the display page generating unit is used for generating the specific display page according to the page template and the configuration information corresponding to the specific display page;

Further, the method further comprises the following steps:

the page template creation unit is used for creating at least one page template and setting each unique template attribute for each page template;

and the attribute template position relation construction unit is used for storing the template attribute of each page template and the storage position of each page template in a one-to-one correspondence relation in the attribute template relation record.

Further, the page template creation unit includes:

the assembly modularization module is used for developing various page elements for page display into assemblies;

and the page template creation module is used for constructing page templates corresponding to each display requirement by using the component according to the specified at least one display requirement and setting the unique template attribute of each page template.

Further, the method further comprises the following steps:

the display page information receiving unit is used for acquiring page addresses, configuration information and template attributes corresponding to each display page;

the attribute page address relation construction unit is used for adding the acquired page addresses of the display pages and the template attributes into the attribute page address relation record according to a one-to-one correspondence;

the configuration page address relation construction unit is used for adding the acquired page addresses of the display pages and the configuration information into the configuration page address relation record according to a one-to-one correspondence.

Further, the presentation page generation unit includes:

the effective component determining module is used for obtaining an intersection set of the components recorded in the configuration information and the components recorded in the page template as a display component set;

the display page generation module is used for generating the specific display page according to the layout and the style of the display assembly set in the page template;

the display page adjusting module is used for updating the layout and the style of the corresponding components in the specific display page according to the layout and the style of all or part of the components in the display component set recorded in the configuration information;

And the data filling module is used for displaying the data to be displayed in the corresponding components in the specific display page according to the binding relation between the components in the display component set and the data to be displayed, which are recorded in the configuration information.

The technical scheme has the following beneficial effects: by creating a plurality of page templates in advance according to various possible requirements, and by creating a mapping relation between page addresses and first template attributes, a mapping relation between page addresses and configuration information, a mapping relation between first template attributes and page templates, and dynamically generating a display page for the specified requirements at runtime by combining configuration information edited according to the specified requirements with preset page templates, the display page for the specified requirements is generated by modifying back-end data instead of generating the display page for the specified requirements by adding static codes, the display page for the specified requirements is provided under the condition that a server does not need to be on line again, the on line again and the retest are avoided, the inefficiency caused by modifying codes is avoided, and the system instability possibly caused by modifying codes is avoided. Further, the layout of each page template is structured, one page corresponds to a plurality of components, one component corresponds to a plurality of page units, each display page has configuration information and page template corresponding, the configuration information is data-bound with the components in the display page, and thus, modifying the configuration information is equivalent to adjusting the display page. The configuration information is subjected to floor in the database and is subjected to addition, deletion and modification through a special background page, so that the background of the page is not changed online; outside the standardized page component, partial patterns of the component in the display page are controlled by the back end through setting configuration information, such as width and height of the card, background color and the like, and the back end can control the patterns of the front end so as to meet the personalized requirements of users; providing a background configuration function of the page, and after filling in the configuration items, according to the adaptation rules, the service access party can preview the style of the display page before submitting the configuration items, and can modify the page in real time according to the requirement, so that the subsequent problems caused by filling-in errors are avoided. Further, at least one page template and attribute template relationship record is deployed at the front end; the attribute page address relation record, the configuration page address relation record and the configuration information are deployed at the back end; the front end performs operations such as adding, deleting, modifying, inquiring and the like on the attribute page address relation record, the configuration page address relation record and the configuration information through an access interface provided by the rear end; the background of a plurality of business parties can be accessed to the back end, the required display page is created by configuring the data of the back end, the sharing of the page template of the front end to various demands of the business parties is realized, the requirement of each business party is avoided to independently develop the code of the front end page, the online and regression testing caused by the operations of adding, deleting, modifying and the like of the front end page is avoided, and the service providing efficiency and stability of the whole system are improved.

Drawings

In order to more clearly illustrate the embodiments of the invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a flow chart of a template sharing method;

FIG. 2 is a block diagram of a template sharing apparatus;

fig. 3 is another structural diagram of a template sharing apparatus.

Detailed Description

The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.

In one aspect, as shown in fig. 1, an embodiment of the present invention provides a template sharing method, including:

S100, when a page acquisition command aiming at a specific display page is received, analyzing a page address of the specific display page from the page acquisition command; the page address is used for accessing the display page through the Internet;

s101, obtaining template attributes of a page template corresponding to the specific display page by inquiring a preset attribute page address relation record according to the analyzed page address;

s102, obtaining a page template corresponding to the specific display page by inquiring a pre-established attribute template relation record according to the template attribute of the page template corresponding to the specific display page; wherein the page template corresponding to the specific display page is one of at least one pre-created page template;

s103, obtaining configuration information corresponding to the specific display page by inquiring a preset configuration page address relation record according to the analyzed page address;

s104, generating the specific display page according to the page template and the configuration information corresponding to the specific display page;

In one embodiment, the page acquisition command at least includes a page address, i.e. URL address, corresponding to the specific presentation page, where the page address may be an absolute address including a complete server domain name, and preferably may be a relative address not including a server domain name;

at least one page template pre-created for various page display requirements; each page template has different template attributes, and the corresponding page template can be uniquely determined through the template attributes;

the specific display page is one of various display pages created by a business party, and each display page is provided with a corresponding page address, configuration information and a page template; when each presentation page is created, at least page addresses, configuration information and template attributes of page templates corresponding to the presentation page are required to be provided; different display pages are provided with different page addresses correspondingly, and the corresponding display pages can be accessed through the page addresses; each presentation page is generated by a corresponding page template and corresponding configuration information; the configuration information comprises binding relations between data to be displayed and components in the page template; the configuration information also comprises the layout and the style of all or part of the components on the display page; the data to be presented is the data that is desired to be presented through the presentation page.

Template attributes of the page templates corresponding to each display page are stored in an attribute page address relation record in a one-to-one correspondence manner with corresponding page addresses in advance; specific implementations of the attribute page address relationship record include, but are not limited to, tables in a database or routing tables stored in a specified file.

Specific implementations of the attribute template relationship records include, but are not limited to, tables in a database or routing tables stored in a specified file. In some embodiments, the attribute template relationship record may be a one-to-one correspondence of the template attribute of each page template to the storage location of the page template, and the page template itself is obtained through the storage location of the page template; in other embodiments, the attribute template relationship record may also record the template attribute of each page template and the page template itself in a one-to-one correspondence; for example, one data column is defined in a table in the database for recording the template properties of each page template, and another data column is defined for recording the page template itself, the template properties of each page template being stored in the same row of the table as the page template itself. The page template itself may be obtained directly from the table of the database by querying the template properties of the page template.

Obtaining a page template corresponding to the specific display page by inquiring a pre-established attribute template relation record according to the template attribute of the page template corresponding to the specific display page, preferably, obtaining a storage position of the page template corresponding to the specific display page by inquiring a pre-established attribute template relation record according to the template attribute of the page template corresponding to the specific display page, and obtaining the page template corresponding to the specific display page according to the storage position of the page template; the template attribute of each page template and the respective storage position of each page template are stored in an attribute template relation record in a one-to-one correspondence mode in advance; template attributes of the page template may be, but are not limited to, template names, e.g., template ID values, etc.; the page templates have respective storage positions, for example, can be stored in different file catalogues, can also be stored in the same file catalogue, and are distinguished by file names; specific implementations of the attribute template relationship records include, but are not limited to, tables in a database or routing tables stored in a specified file;

the corresponding page address of each display page and the corresponding configuration information are stored in a configuration page address relation record in a one-to-one correspondence mode in advance; specific implementations of configuration page address relationship records include, but are not limited to, tables in a database or routing tables stored in a specified file;

The at least one pre-created page template, the attribute page address relation record, the attribute template relation record and the configuration page address relation record can be deployed and stored on the same physical server or different physical servers, and can also be deployed and stored in the same or different modules. Preferably, at least one pre-created page template and an attribute template relationship record are stored in a front-end module, and an attribute page address relationship record and a configuration page address relationship record are stored in a back-end module, and the front-end module accesses the attribute page address relationship record and the configuration page address relationship record through a back-end interface provided by the back-end module; the front-end module and the back-end module may be deployed on the same hardware server, or may be deployed on different hardware servers.

In one embodiment, a user wishes to access a particular presentation page; the user inputs a page address corresponding to a specific display page in a browser address bar, or clicks a link in a current display page, the address of the link is set to be the page address corresponding to the specific display page, at the moment, the browser or the current display page wants to send a page acquisition command aiming at the specific display page to the front end, the front end obtains the page address corresponding to the specific display page from the received page acquisition command, and according to the page address, the template attribute of a page template corresponding to the page address (namely corresponding to the specific display page) is obtained from an attribute page address relation record of the rear end through accessing the rear end interface; querying an attribute template relation record at the front end by using the template attribute to obtain a storage position of the page template uniquely identified by the template attribute; reading the page template from a storage location of the page template; the front end continuously queries the configuration page address relation record of the rear end through the rear end interface according to the page address to obtain configuration information related to the specific display page; each page template provides a plurality of display pages corresponding to each configuration information by combining with the plurality of configuration information; generating a specific display page by the page template corresponding to the specific display page and the configuration information; for example, a page template comprises various types of card display, table adding and deleting and modifying, echorts diagram display, task display, microblog stream display and other components, and configuration information only comprises various types of card display, table adding and deleting and modifying, echorts diagram display, and a display page generated according to the page template and the configuration information comprises various types of card display, table adding and deleting and modifying, echorts diagram display components, but does not comprise task display, microblog stream display and other components; and the layout and style of some or all components can be specified in the configuration information, so that the display page can be redefined according to the layout and style in the configuration information on the basis of the layout and style of each component on the page template. By editing the configuration information according to the specified requirements and applying the edited configuration information on the specified page template, the display page meeting the specified requirements can be dynamically generated by modifying the back-end data at the running time without modifying any front-end or back-end codes. After the specific display page is generated, the specific display page is returned to a sending end of the page acquisition command so that the specific display page is displayed on the sending end, and the sending end comprises a processing module and a display module; the processing module may include a processor capable of performing computing operations and the display module is configured to display the specific presentation page including but not limited to.

The embodiment of the invention has the following technical effects: by creating a plurality of page templates in advance according to various possible requirements, and by creating a mapping relation between page addresses and template attributes, a mapping relation between page addresses and configuration information, a mapping relation between template attributes and page templates, and dynamically generating a display page for the specified requirements at runtime by combining configuration information edited according to the specified requirements with a preset page template, the display page for the specified requirements is generated by modifying back-end data instead of generating the display page for the specified requirements by adding static codes, so that the display page for the specified requirements is provided under the condition that a server does not need to be subjected to online test again, the online test again is avoided, the inefficiency caused by retesting is avoided, and the system instability possibly caused by modifying codes is avoided. Because the display page is not generated by the newly added code, but is generated by configuring the back-end data, the same front-end service can provide services for a plurality of service access parties by dynamically generating the display page for each service access party.

Preferably, the at least one page template and the attribute template relationship record are deployed at the front end; the attribute page address relation record, the configuration page address relation record and the configuration information are deployed at the back end; the front end performs operations such as adding, deleting, modifying, inquiring and the like on the attribute page address relation record, the configuration page address relation record and the configuration information through an access interface provided by the back end.

In one embodiment, at least one pre-created page template and an attribute template relationship record are deployed in the front end, and in general, various possible display requirements are estimated in advance, corresponding page templates are created according to the various display requirements, template attributes serving as unique identifiers are set for each page template, and an attribute template relationship record is created; the pre-created page templates can meet new display requirements in the normal case, so that the front-end page templates are not required to be frequently updated or added in the normal case during the service providing of the system; even when a new page template is needed to be added when a new display requirement is met, the new page template can be directly added to the front end, and the relation record of the attribute template is modified, so that the influence on the existing display page is avoided. According to the technical scheme, the effect of separating the front-end page template from the back-end data is achieved, so that when a new display page is added, only the attribute page address relation record, the configuration page address relation record and the configuration information data of the back-end are required to be added or modified, and the front-end code and the data and the back-end code are not required to be modified. On the basis, the background of a plurality of business parties can be connected into the front end and the back end, and the required display page is created by configuring the data of the back end, so that the sharing of the page template of the front end to various demands of the business parties is realized, the requirement of each business party is avoided to independently develop the code of the front end page, and the online and regression testing caused by the operations of adding, deleting, changing and the like of the front end page is avoided, and the service providing efficiency and stability of the whole system are improved.

Further, before the step of analyzing the page address of the specific presentation page from the page acquisition command when the page acquisition command for the specific presentation page is received, the method further comprises:

In one embodiment, various common functions used for displaying the page are developed into components, such as various card displays, table adding, deleting and modifying, echartists diagram display, task display, microblog stream display and the like; various page display requirements require various page components and various layouts and styles, a plurality of page templates are correspondingly created in advance according to the appointed various page display requirements, and template attributes capable of uniquely identifying the page templates are appointed for each page template, preferably, the template attributes can be but not limited to template attributes capable of uniquely identifying each page template respectively by using a template name, a template file name, a unique ID value appointed for each page template and the like; storing all the pre-created page templates in an attribute template relation record according to the one-to-one correspondence between the respective template attributes and the respective storage positions; the attribute template relation record is used for inquiring the storage position of the page template uniquely identified by the template attribute according to the template attribute, and further the page template uniquely identified by the template attribute can be obtained according to the obtained storage position.

developing various page elements for page presentation as components;

In one embodiment, a rich page template is provided; the common functions in the display page, such as various card displays, table addition and deletion and modification, echartis graph displays, task displays, microblog stream displays and the like, are developed into components, the components are required by the service, and the components are combined into common page templates by combining various factors such as page layout, patterns and the like; structuring the layout of each page template, wherein one page template corresponds to a plurality of components, one component corresponds to a plurality of page units, creating a corresponding page template according to various appointed display requirements, and appointing a unique template attribute corresponding to the page template; in various page display requirements, a large number of repeated page components are used, the page elements are developed into components, when the new display requirements are met, the components can be quickly utilized to construct a new page template, the existing components are conveniently recycled to assemble the page templates aiming at the various display requirements, the efficiency is remarkably improved, and errors caused by repeated coding are avoided.

And generating preview pages of the display pages according to the page addresses, the configuration information and the template attributes corresponding to the display pages.

The configuration information corresponding to each display page comprises components contained in each display page; the configuration information corresponding to each display page also comprises the layout and the style of all or part of the components contained in each display page; the configuration information corresponding to each display page also comprises the binding relation between the components contained in each display page and the data to be displayed of each display page;

In one embodiment, after various required page templates are created in advance for various display requirements, a service access party applies for an access system, the system distributes service numbers for service parties and generates manager accounts, the service access party logs in the system and builds a display page in a page configuration background, specifically, the method comprises filling necessary page configuration information such as page names, page addresses (namely page URLs), page positions, template attributes of the page templates (preferably, the template attributes can be specifically template names), rights required for accessing the page and the like, filling data interface addresses (namely, the sources for indicating the data to be displayed) according to the template requirements, and binding the data to be displayed with components in the display page through the configuration information; the method can also generate preview pages to preview each display page in real time according to page addresses, configuration information and template attributes corresponding to each display page, realize the effect of real-time preview pages and submit the configuration information after satisfaction; in some embodiments, the corresponding relation among the configuration information, the page address and the template attribute of the page template is stored in the back end of the system in the form of readable and writable data, preferably in the form of attribute page address relation record and configuration page address relation record, so that a new display page is generated for the front end of the new service. In the process of generating the new display page, the codes of the front end or the back end are not changed, and only the data recorded by the back end and related to the new display page are newly added or modified.

The embodiment of the invention has the following technical effects: by adding or modifying the back-end data related to the display page, the display page is added or modified under the condition that the front-end code and the back-end code are not modified, the service access party only needs to add or modify the related information of the display page by the page configuration background, a developer does not need to modify the front-end code and the back-end code, the display page can be added or modified without re-online and regression testing, the effect of the display page can be checked in real time during the generation of the display page, the effect is verified without waiting for online, and the efficiency of creating the display page by the service party is obviously improved.

In one embodiment, a page template may be matched with a plurality of different configuration files to obtain a plurality of different presentation pages. Generally, when a display page needs to be created for a specified display requirement, a page template capable of meeting the specified display requirement is selected from at least one page template, and then according to the specified display requirement and components provided by the page template, the components needed in the display page are bound with the data to be displayed specified in the specified display requirement in a one-to-one correspondence manner in configuration information. The components required in the presentation page (as well as the components contained in the configuration information) may be a subset or all of the components contained in the page template; for example, for components that do not exist in the configuration information, components that exist in the page template do not appear in the final presentation page; the layout and style of the corresponding components in the generated presentation page can also be controlled according to the layout and style of some or all components of the configuration information record.

The embodiment of the invention has the following technical effects: the layout of each page template is structured, one page corresponds to a plurality of components, one component corresponds to a plurality of page units, each display page is provided with configuration information and a page template corresponding, the configuration information is bound with the components in the display page in a data mode, and thus, the modification of the configuration information is equivalent to the adjustment of the display page. The configuration information is subjected to floor in the database and is subjected to addition, deletion and modification through a special background page, so that the background of the page is not changed online; outside the standardized page component, partial patterns of the component in the display page are controlled by the back end through setting configuration information, such as width and height of the card, background color and the like, and the back end can control the patterns of the front end so as to meet the personalized requirements of users; providing a background configuration function of the page, and after filling in the configuration items, according to the adaptation rules, the service access party can preview the style of the display page before submitting the configuration items, and can modify the page in real time according to the requirement, so that the subsequent problems caused by filling-in errors are avoided.

On the other hand, as shown in fig. 2, an embodiment of the present invention further provides a template sharing apparatus, including:

A page acquisition command receiving unit 200, configured to, when a page acquisition command for a specific display page is received, parse a page address of the specific display page from the page acquisition command; the page address is used for accessing the display page through the Internet;

the template attribute query unit 201 is configured to obtain template attributes of a page template corresponding to the specific display page by querying a preset attribute page address relationship record according to the parsed page address;

a page template obtaining unit 202, configured to obtain a page template corresponding to the specific display page by querying a preset attribute template relationship record according to a template attribute of the page template corresponding to the specific display page; wherein the page template corresponding to the specific display page is one of at least one pre-created page template;

a configuration information obtaining unit 203, configured to obtain configuration information corresponding to the specific display page by querying a preset configuration page address relationship record according to the parsed page address;

a display page generating unit 204, configured to generate the specific display page according to a page template and configuration information corresponding to the specific display page;

Further, the method further comprises the following steps:

Further, the page template creation unit includes:

Further, the method further comprises the following steps:

Further, the presentation page generation unit 204 includes:

The template sharing device provided in the embodiment of the present invention corresponds to the template sharing method provided in the foregoing embodiment one by one, and a person skilled in the art may understand the embodiment in the template sharing device according to the foregoing embodiment in the template sharing method without objection, which is not described herein.

The foregoing technical solutions of the embodiments of the present invention will be described in detail with reference to specific application examples, and reference may be made to the foregoing related description for details of the implementation process that are not described.

Technical terms used in the embodiments of the present invention are described as follows:

front end template engine: the front-end template engine can greatly save code quantity and improve maintainability when the html pages with the same structure are repeatedly generated according to different data. The template engine plays a role in separating data from view, the templates correspond to the views, focus on how the data is presented, data is prepared for the templates, focus on which data can be presented.

Data binding: the data binding refers to a mapping relationship between a front-end View layer and a Model layer, and is divided into unidirectional data binding and bidirectional data binding.

And (3) assembly: the components of the page are presented.

Display page: one presentation page corresponds to one piece of configuration information.

A unit: logically the finest granularity of components will not be split any more.

VUE: the VUE is a progressive JavaScript framework for constructing a user interface, only focuses on a view layer, adopts a design of bottom-up incremental development, and realizes the view component of responsive data binding and combination through an API as simple as possible, so that the MVVM is simpler.

MVVM: MVVM is a shorthand for Model-View-ViewModel, a software architecture Model. MVVM abstracts the state and behavior of View therein, separating the development of graphical user interfaces from the development of business logic or backend logic (data model).

NGINX: NGINX is a high-performance HTTP and reverse proxy web server, and provides IMAP/POP3/SMTP services, and NGINX has the advantages of lightweight, high scalability, high reliability, low memory consumption, and the like.

Front-end routing: the front-end routing is to give the tasks of different contents or pages corresponding to different routes to the front-end, and the front-end routing is realized by the service end returning different pages according to different page URLs.

And (3) templating: templating is an integral idea. In short, the template regards a section of UI style and the corresponding function as an independent whole, and the whole has the same function and style no matter where to use, so that the code multiplexing is realized, and the integral idea is the template. The templatization can increase reusability, flexibility and system design, thereby improving development efficiency.

Sharing front end: the shared front end is a front end shared by a plurality of micro service background, so that development quantity is reduced, and working efficiency is improved. The microservice background includes, but is not limited to, a background for a business access party to maintain a presentation page.

The following describes an embodiment of the present invention by taking a structure diagram of a technical scheme of the embodiment of the present invention as shown in fig. 3 as an example, where the embodiment of the present invention mainly comprises a front-end routing module, a template module, a state management module, a server unified interface module, a template adaptation module, a service processing module, a rights management module, and a data storage module.

Front-end routing module: storing the corresponding relation between the template name (namely the template attribute) and the page template, and obtaining the corresponding relation between the page address and the template name from a Server (namely a Server in FIG. 3), thereby obtaining the corresponding relation between the page address and the page template; the corresponding relationship between the display page and the URL (i.e., the page address) in the embodiment of the present invention is not directly defined at the front end, the front end (i.e., the Web end in fig. 3) defines the corresponding relationship between the path of the page template and the template name (i.e., the attribute template relationship record), and the rear end (i.e., the Server end in fig. 3) defines the corresponding relationship between the URL (i.e., the page address) and the template name, so that the front end can resolve the corresponding relationship between the URL (i.e., the page address) and the template path (i.e., the template storage location) after acquiring the data from the rear end. The corresponding relation (namely, attribute page address relation record) between the URL (namely, page address) at the rear end and the template name is stored in the database, so that the dynamic addition, deletion and modification are convenient, and the dynamic addition, deletion and modification of the display page are realized.

And (3) a template module: the method comprises the steps of including all page templates, components and the like at the front end, and rendering a real page only by providing data. The embodiment of the invention provides rich front-end templates, common functions such as various card display, table adding and deleting and modifying, echartis graph display, task display, microblog flow display and the like are developed into components, the components are required for service arrangement, and the components are combined into common templates by combining various factors such as page layout, patterns and the like.

And a state management module: each page template is composed of a plurality of different components, data transmission among the different components is needed by a state management module, the state values of all the components are stored and managed in a centralized mode, the state is ensured to change in a predictable mode by corresponding rules, and the data transmission among the different components is convenient.

And the unified interface module: the front end is mainly provided with unified interface service, and comprises an authentication interface, a data interface, a configuration interface and the like, wherein the authentication interface judges authority through a user name, a service number and a URL, and the data interface returns data through judging the URL and the user name.

And a template adapting module: each front-end page template corresponds to one piece of configuration information, and each type of configuration information corresponds to one table in the database. In order to facilitate configuration generation, the back end formulates a corresponding back end template class for each front end page template, acquires configuration information corresponding to the display page from the database by taking the URL as a main key, and returns the configuration information to the front end for page rendering.

And a service processing module: and the system is responsible for processing business related transactions such as external data, log reporting, monitoring alarm, big data calculation and the like.

And the permission management module is used for: is responsible for the functions of user management, page authority management, user authentication and the like.

And a data storage module: and the whole data of the storage system comprises user data, page data, access service data, configuration information, authority information and the like.

Firstly, a service access party applies for an access system, the system distributes a service number for the service party and generates an administrator account, the access party logs in to the system and then builds a new page in a page configuration background, necessary page configuration information such as page names, page URLs, page positions, page templates, authorities required for accessing the page and the like are filled in, data interface addresses are filled in according to the template requirements, page effects are previewed, the configuration information is submitted after satisfaction, the information is stored in the system background, a new page is generated for the front end of the new service, the administrator can also add a new user for the service in the background, when the user accesses the new page, the system can identify authorities of login users, judge whether the service and the authorities of the page are owned, configuration information corresponding to the page URLs is obtained from a database after authentication is passed, the front end service is provided by a unified interface module, the front end analyzes a front end page template path corresponding to the page address through the corresponding relation between the locally defined template names and the template paths and the corresponding relation between the URLs returned by the interfaces and the template names, and the complete visual display page is rendered according to the configuration information and the page rendering page.

The technical effects of the embodiment of the invention are as follows:

the embodiment of the invention utilizes rich front-end templates (namely page templates), and a developer can finish the addition of the page by only providing data adapting to the front-end templates at an interface layer, thereby saving time and labor.

The embodiment of the invention can allow different service parties to access the front-end system, and can have the front-end service of the user by providing corresponding data interfaces according to rules and setting configuration information configuration rights in the background, thereby reducing the waste of resources;

the embodiment of the invention utilizes the thought of a Router route manager of Vue.js, and is different from the prior art that the corresponding relation between the page address URL and the page template path is defined at the front end;

according to the embodiment of the invention, the layout of each page template is structured, one page template corresponds to a plurality of components, one component corresponds to a plurality of units, each display page is provided with configuration information and page templates corresponding to the configuration information, the configuration information and the components in the display page are subjected to data binding, and thus, the modification of the configuration information is equivalent to the adjustment of the display page. The configuration information is subjected to floor in the database and is subjected to addition, deletion and modification through a special background page, so that the background of the page is not changed online;

In the embodiment of the invention, besides providing the standardized page component, part of patterns are controlled by the back end, such as the width and the height of the card, the background color and the like, and the back end can control the patterns of the front end so as to meet the personalized requirements of users.

The embodiment of the invention provides a background configuration function of the page, after filling in configuration items in configuration information, a user can preview the page style before submitting the page according to the adaptation rule and modify the page in real time according to the requirement, so that the subsequent problem caused by filling errors is avoided.

In summary, the embodiment of the invention uses the front-end sharing scheme based on the template and the background configuration to templet all the pages, generates the display pages corresponding to the configuration information one by one, constructs and uniformly stores the configuration information at the rear end, facilitates the management of the configuration information, and solves the huge cost caused by frequent online of the front end. The method provides a mode of accessing multiple service parties, shares front-end service, automatically realizes authority separation between services, greatly facilitates the use of the service parties, and avoids repeated wheel making. The embodiment of the invention provides a large number of front-end adaptation templates and components, supports the optional combination pages of the echartis chart, the table, the video, the audio and various card, and saves the time of front-end development. The embodiment of the invention provides a front-end page preview function, and does not need to be deployed to view page effects in advance and modify the page effects in real time. The embodiment of the invention realizes the sharing of the front-end service, the matching of the page background and the automatic isolation of the authority.

It should be understood that the specific order or hierarchy of steps in the processes disclosed are examples of exemplary approaches. Based on design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged without departing from the scope of the present disclosure. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

In the foregoing detailed description, various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments of the subject matter require more features than are expressly recited in each claim. Rather, as the following claims reflect, invention lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate preferred embodiment of this invention.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. As will be apparent to those skilled in the art; various modifications to these embodiments will be readily apparent, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

The foregoing description includes examples of one or more embodiments. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the aforementioned embodiments, but one of ordinary skill in the art may recognize that many further combinations and permutations of various embodiments are possible. Accordingly, the embodiments described herein are intended to embrace all such alterations, modifications and variations that fall within the scope of the appended claims. Furthermore, as used in the specification or claims, the term "comprising" is intended to be inclusive in a manner similar to the term "comprising," as interpreted when employed as a transitional word in a claim. Furthermore, any use of the term "or" in the specification of the claims is intended to mean "non-exclusive or".

Those of skill in the art will further appreciate that the various illustrative logical blocks (illustrative logical block), units, and steps described in connection with the embodiments of the invention may be implemented by electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components (illustrative components), elements, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design requirements of the overall system. Those skilled in the art may implement the described functionality in varying ways for each particular application, but such implementation is not to be understood as beyond the scope of the embodiments of the present invention.

The various illustrative logical blocks or units described in the embodiments of the invention may be implemented or performed with a general purpose processor, a digital signal processor, an Application Specific Integrated Circuit (ASIC), a field programmable gate array or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described. A general purpose processor may be a microprocessor, but in the alternative, the general purpose processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration.

The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. In an example, a storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC, which may reside in a user terminal. In the alternative, the processor and the storage medium may reside as distinct components in a user terminal.

In one or more exemplary designs, the above-described functions of embodiments of the present invention may be implemented in hardware, software, firmware, or any combination of the three. If implemented in software, the functions may be stored on a computer-readable medium or transmitted as one or more instructions or code on the computer-readable medium. Computer readable media includes both computer storage media and communication media that facilitate transfer of computer programs from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer. For example, such computer-readable media may include, but is not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to carry or store program code in the form of instructions or data structures and other data structures that may be read by a general or special purpose computer, or a general or special purpose processor. Further, any connection is properly termed a computer-readable medium, e.g., if the software is transmitted from a website, server, or other remote source via a coaxial cable, fiber optic cable, twisted pair, digital Subscriber Line (DSL), or wireless such as infrared, radio, and microwave, and is also included in the definition of computer-readable medium. The disks (disks) and disks (disks) include compact disks, laser disks, optical disks, DVDs, floppy disks, and blu-ray discs where disks usually reproduce data magnetically, while disks usually reproduce data optically with lasers. Combinations of the above may also be included within the computer-readable media.

The foregoing description of the embodiments has been provided for the purpose of illustrating the general principles of the invention, and is not meant to limit the scope of the invention, but to limit the invention to the particular embodiments, and any modifications, equivalents, improvements, etc. that fall within the spirit and principles of the invention are intended to be included within the scope of the invention.

Claims

1. A template sharing method, comprising:

generating the specific display page according to the page template and the configuration information corresponding to the specific display page, including:

according to the binding relation between each component in the display component set and each data to be displayed, which is recorded in the configuration information, displaying each data to be displayed in the corresponding component in the specific display page;

wherein each page template in the at least one page template has different template attributes respectively; each page template consists of components and is used for generating a display page; the attribute page address relation record, the configuration page address relation record and the configuration information are deployed at the back end; each page template provides a plurality of display pages corresponding to each configuration information by combining with the plurality of configuration information; each presentation page has a configuration information and page template corresponding thereto, the configuration information including binding relationships between the data to be presented and components in the page template.

2. The template sharing method of claim 1, further comprising, before the parsing out the page address of the specific presentation page from the page fetch command when the page fetch command for the specific presentation page is received:

3. The template sharing method of claim 2, wherein creating at least one page template and setting a respective unique template attribute for each page template comprises:

developing various page elements for page presentation as components;

4. The template sharing method of claim 1, further comprising, before the parsing out the page address of the specific presentation page from the page fetch command when the page fetch command for the specific presentation page is received:

5. A template sharing apparatus, comprising:

the display page generation unit comprises:

the data filling module is used for displaying the data to be displayed in the corresponding components in the specific display page according to the binding relation between the components in the display component set and the data to be displayed, which are recorded in the configuration information;

6. The template sharing apparatus of claim 5, further comprising:

7. The template sharing apparatus of claim 6, wherein the page template creation unit includes:

8. The template sharing apparatus of claim 5, further comprising: