Dsl description file management method, device, system, apparatus and medium

Abstract

Embodiments of the present application provide a DSL description file management method, device, system, equipment and medium. The version information of the application program and the identifier of the target front-end page to be rendered are determined through the DSL description file request sent by the application program; at least one candidate DSL description file corresponding to the target front-end page under different versions can be determined according to the identifier of the target front-end page; the target DSL description file corresponding to the version of the application program is determined from the at least one candidate DSL description file according to the version information of the application program and the application program version range supported by each candidate DSL description file; based on this, the target DSL description file can be issued to the application program, and the target front-end page is rendered according to the target DSL description file. Embodiments of the present application can realize unified management and cross-platform dynamic issuance of DSL description files for different platforms, and can realize cross-platform dynamic rendering requirements.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, and particularly relates to a DSL description file management method, device, system, equipment and medium. BACKGROUND

[0002] In the process of application development, optimization and upgrading of some function modules are often involved, and in the process, some components in the function modules may be updated. The updated component is equivalent to a new version component compared with the original component.

[0003] Generally, the component version that can be compatible with different versions of application programs may be different. If the current version of the application program cannot be compatible with the new version of the component, the new version of the component cannot be normally rendered. Therefore, in order to ensure that the component can be normally rendered in the application program in the case of being updated, it is necessary to manage the version correspondence between the component and the application program. SUMMARY

[0004] Aspects of the present application provide a DSL description file management method, device, system, equipment and medium, which are used to manage the version correspondence between the component and the application program.

[0005] The DSL description file management method provided by the embodiment of the present application is applied to a DSL description file management system, the DSL description file management system includes at least one DSL description file corresponding to a front-end page, each DSL description file includes description information of a UI component required by the corresponding front-end page, and the method includes the following steps: receiving a DSL description file request sent by an application program, the DSL description file request including version information of the application program and an identifier of a target front-end page to be rendered; determining at least one candidate DSL description file corresponding to the target front-end page under different versions according to the identifier of the target front-end page, wherein each candidate DSL description file has a corresponding supported application program version range; determining a target DSL description file corresponding to the version of the application program from the at least one candidate DSL description file according to the version information of the application program and the application program version range supported by each candidate DSL description file; and sending the target DSL description file to the application program, so that the application program renders the target front-end page according to the description information included in the target DSL description file.

[0006] In an optional embodiment, the DSL description file management system comprises at least one component library corresponding to each front-end page, the at least one component library has different versions, different versions of the component library support different application version ranges, each version of the component library corresponds to at least one DSL description file, and each component library comprises UI components required by the corresponding front-end page. Accordingly, determining at least one candidate DSL description file corresponding to the target front-end page under different versions according to the identification of the target front-end page comprises: determining at least one candidate component library corresponding to the target front-end page under different versions according to the identification of the target front-end page, and taking at least one DSL description file corresponding to the at least one candidate component library as the at least one candidate DSL description file. Accordingly, determining a target DSL description file corresponding to the version of the application from the at least one candidate DSL description file according to the version information of the application and the application version range supported by each candidate DSL description file comprises: selecting a target component library from the at least one candidate component library according to the version information of the application and the application version range supported by each candidate component library, and selecting the target DSL description file from at least one DSL description file corresponding to the target component library.

[0007] In an optional embodiment, before receiving the request sent by the application, the method further comprises: determining the application version range supported by each component library in the at least one component library corresponding to the same front-end page and the version of each component library; and generating at least one DSL description file corresponding to each component library according to the version of each component library and the application version range supported by each component library.

[0008] In an optional embodiment, determining the application version range supported by each component library in the at least one component library and the version of each component library comprises: obtaining the application version supported by each UI component contained in each component library in the at least one component library; determining the application version range commonly supported by the UI components in each component library according to the application version supported by each UI component, as the application version range supported by each component library; in the case that the application version ranges supported by at least two component libraries are the same, setting the at least two component libraries as the same version; and in the case that the application version ranges supported by at least two component libraries are different, setting the at least two component libraries as different versions.

[0009] In an optional embodiment, at least one DSL description file corresponding to each component library is generated according to the version of each component library and the supported application version range, including: obtaining basic information and layout information of a plurality of UI components contained in each component library; determining a cascade relationship between the plurality of UI components according to the basic information and the layout information; generating at least one DSL description file corresponding to each component library according to the version of each component library and the cascade relationship, and taking the application version range supported by each component library as the application version range supported by the at least one DSL description file corresponding to the component library.

[0010] In an optional embodiment, the target DSL description file is selected from at least one DSL description file corresponding to the target component library, including: selecting a latest version DSL description file from the at least one DSL description file as the target DSL description file.

[0011] Embodiments of the present application also provide a DSL description file management device applied to a DSL description file management system, the DSL description file management system including at least one DSL description file corresponding to a front-end page, each DSL description file including description information of UI components required by the front-end page corresponding thereto, the device including: a receiving module configured to receive a DSL description file request sent by an application, the DSL description file request including version information of the application and an identifier of a target front-end page to be rendered; a first processing module configured to determine at least one candidate DSL description file corresponding to the target front-end page under different versions according to the identifier of the target front-end page; each candidate DSL description file has a corresponding supported application version range; a second processing module configured to determine a target DSL description file corresponding to the version of the application from the at least one candidate DSL description file according to the version information of the application and the application version range supported by each candidate DSL description file; and a sending module configured to send the target DSL description file to the application, so that the application renders the target front-end page according to the description information included in the target DSL description file.

[0012] The embodiment of the present application further provides a DSL description file management system, which comprises: a DSL description file generation device and a DSL description file management device; the DSL description file generation device is used for generating DSL description files corresponding to at least one front-end page in different versions, each DSL description file comprising description information of UI components required by the front-end page corresponding thereto; determining the application version range supported by each DSL description file according to the application version information supported by the UI components contained in each DSL description file; and the DSL description file management device is used for determining at least one candidate DSL description file corresponding to a target front-end page in different versions according to the identification of the target front-end page to be rendered; determining a target DSL description file supporting the version of the application program containing the target front-end page from the at least one candidate DSL description file according to the version information of the application program containing the target front-end page and the application version range supported by each DSL description file; and sending the target DSL description file to the application program so as to render the target front-end page by the application program.

[0013] The embodiment of the present application further provides a DSL description file management system, which comprises: a component library generation device, a DSL description file generation device and a DSL description file management device; the component library generation device is used for generating at least one component library corresponding to at least one front-end page, each component library comprising a plurality of UI components, and the plurality of UI components corresponding to the application version supported thereby; determining the application version range supported by each component library and the version of each component library according to the application version supported by the plurality of UI components contained in each component library respectively; the DSL description file generation device is used for generating DSL description files corresponding to at least one front-end page in different versions, each DSL description file comprising description information of UI components required by the front-end page corresponding thereto; and the DSL description file management device is used for determining at least one candidate component library corresponding to a target front-end page to be rendered according to the identification of the target front-end page; establishing the corresponding relationship between the component library version and the DSL in different versions, and determining a target component library and at least one DSL description file corresponding to the target component library from the at least one candidate component library according to the version information of the application program containing the target front-end page; selecting a target DSL description file from the at least one DSL description file, and sending the target DSL description file to the application program so as to render the target front-end page by the application program.

[0014] The embodiment of the present application further provides a DSL description file management device, comprising a processor and a memory storing a computer program; the processor is used for executing the computer program, so as to: receive a DSL description file request sent by an application program, wherein the DSL description file request comprises version information of the application program and an identifier of a target front-end page to be rendered; determine at least one candidate DSL description file corresponding to the target front-end page under different versions according to the identifier of the target front-end page; wherein each candidate DSL description file has a corresponding supported application program version range; determine a target DSL description file corresponding to the version of the application program from the at least one candidate DSL description file according to the version information of the application program and the application program version range supported by each candidate DSL description file; and send the target DSL description file to the application program, so that the application program renders the target front-end page according to description information included in the target DSL description file.

[0015] The embodiment of the present application further provides a computer readable storage medium storing a computer program, when the computer program is executed by a processor, the processor is caused to implement each step in the method claim.

[0016] In the embodiment of the present application, the DSL description file request sent by the application program can determine the version information of the application program and the identifier of the target front-end page to be rendered; then, according to the identifier of the target front-end page, at least one candidate DSL description file corresponding to the target front-end page under different versions can be determined; and according to the version information of the application program and the application program version range supported by each candidate DSL description file, a target DSL description file corresponding to the version of the application program can be determined from the at least one candidate DSL description file; based on this, the target DSL description file can be sent to the application program, so that the application program renders the target front-end page according to the description information included in the target DSL description file. Based on the platform-independent characteristics of the DSL description file, the embodiment of the present application can realize unified management and cross-platform dynamic distribution of DSL description files of different platforms, and can realize cross-platform dynamic rendering requirements. BRIEF DESCRIPTION OF DRAWINGS

[0017] The accompanying drawings, which are included to provide a further understanding of the present application, constitute a part of the present application and illustrate embodiments of the present application and explanations thereof, and do not constitute improper limitations to the present application. In the drawings:

[0018] Figure 1a A structural schematic diagram of a DSL description file management system provided by the embodiment of the present application is shown in the figure;

[0019] Figure 1bAnother structure diagram of a DSL description file management system provided by an embodiment of the present application is shown in FIG. 2;

[0020] Figure 1c A diagram of a correspondence between a DSL description file and a component library provided by an embodiment of the present application is shown in FIG. 3;

[0021] Figure 2 A flowchart of a DSL description file management method provided by an embodiment of the present application is shown in FIG. 4;

[0022] Figure 3 A structure diagram of a DSL description file management apparatus provided by an embodiment of the present application is shown in FIG. 5;

[0023] Figure 4 A structure diagram of a DSL description file management device provided by an embodiment of the present application is shown in FIG. 6. DETAILED DESCRIPTION

[0024] To make the objectives, technical solutions and advantages of the present application clearer, the technical solutions of the present application will be described below in detail with reference to the embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only some of the embodiments of the present application, but not all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without any creative work fall within the scope of protection of the present application.

[0025] An embodiment of the present application provides a DSL description file management system, which is used to manage domain specific language (DSL) description files of a front-end page in different versions, and to issue corresponding versions of the DSL description files to each platform according to a DSL description file request of each platform. The DSL description file is a platform-independent description file with a general data format obtained by abstracting and re-expressing the front-end page. The DSL description file management system can issue the DSL description file to different platforms, so as to realize cross-platform issuance of the DSL description file, and to render the front-end page dynamically according to the DSL description file by different platforms.

[0026] Figure 1a A structure diagram of a DSL description file management system provided by an embodiment of the present application is shown in FIG. 2; Figure 1aAs shown, the system comprises a DSL description file generation device 10 and a DSL description file management device 20; wherein the DSL description file generation device 10 is configured to generate DSL description files corresponding to at least one front-end page in different versions, and each DSL description file comprises description information of UI components required by the front-end page corresponding thereto. In this embodiment, the DSL description file generation device 10 is further configured to determine an application version range supported by each DSL description file according to application version information supported by the UI components included in each DSL description file, so that the DSL description file management device 20 can issue a DSL description file in a corresponding version to an application according to the application version range supported by each DSL description file, so that the application can render a target front-end page.

[0027] As shown in the Figure 1a In this embodiment, the DSL description file management device 20 is configured to receive DSL description file requests sent by applications of each platform; wherein the DSL description file request comprises version information of the application and an identifier of a target front-end page to be rendered. Based on this, the DSL description file management device 20 can determine at least one candidate DSL description file corresponding to the target front-end page in different versions according to the identifier of the target front-end page to be rendered, and determine a target DSL description file supporting the version of the application from the at least one candidate DSL description file according to the version information of the application and the application version range supported by each DSL description file, and send the target DSL description file to the application, so that the application can render the target front-end page.

[0028] The embodiments of the present application also provide a DSL description file management system, Figure 1b The structure diagram of the DSL description file management system provided in the present application is shown in Figure 1b As shown, the system comprises a component library generation device 30, a DSL description file generation device 10 and a DSL description file management device 20; wherein the DSL description file generation device 10 is similar to the above-mentioned embodiments, and is configured to generate DSL description files corresponding to at least one front-end page in different versions; wherein each DSL description file comprises description information of UI components required by the front-end page corresponding thereto.

[0029] In this embodiment, the component library generation device 30 is configured to generate at least one component library corresponding to at least one front-end page, each component library including a plurality of UI components, and the plurality of UI components included in each component library are the UI components on the front-end page corresponding to each component library; wherein the plurality of UI components correspond to the application version supported thereby. Based on this, the component library generation device 30 can determine the application version range supported by each component library and the version of each component library according to the application version supported by the plurality of UI components included in each component library respectively; wherein the version of the component library refers to that, in the case that there is an update of the UI component in the component library, if the application version range supported by the component library changes, the component library including the updated UI component and the component library including the pre-updated UI component correspond to different versions respectively.

[0030] In this embodiment, as shown in Figure 1b , the DSL description file management device 20 is configured to receive a DSL description file request sent by an application of each platform; wherein the DSL description file request includes the version information of the application and the identification of the target front-end page to be rendered. Based on this, the DSL description file management device 20 can determine at least one candidate component library corresponding to the target front-end page according to the identification of the target front-end page to be rendered, and determine the target component library from the at least one candidate component library according to the version information of the application and the application version range supported by each component library.

[0031] In this embodiment, the plurality of UI components included in each component library can be the plurality of UI components of the front-end page under different versions, and the front-end page under different versions correspond to different DSL description files; based on this, as shown in Figure 1b , the DSL description file management device 20 can further establish the corresponding relationship between the component library and the DSL description file according to the DSL description file corresponding to the UI component included in each component library respectively; and then determine at least one DSL description file corresponding to the target component library according to the corresponding relationship between the component library version and the DSL under different versions, and select the target DSL description file from the at least one DSL description file, and send the target DSL description file to the application, so as to render the target front-end page by the application.

[0032] In the optional embodiment of the present application, the DSL description file management device 20 can also determine the application version range supported by each component library and the version of each component library for at least one component library corresponding to the same front-end page before receiving the request sent by the application. Optionally, the application version supported by each UI component contained in each component library can be obtained, and the application version range commonly supported by the plurality of UI components in each component library can be determined according to the application version supported by each UI component, as the application version range supported by each component library. Further, in the case that the application version range supported by at least two component libraries is the same, the at least two component libraries are set to the same version, and in the case that the application version range supported by at least two component libraries is different, the at least two component libraries are set to different versions.

[0033] Figure 1c The correspondence between the DSL description file corresponding to the front-end page under different versions and the component library of different versions and the application version range supported thereby is shown in the schematic diagram provided by the embodiment of the present application. The application is taken as an example for illustration. As shown in Figure 1c , the four versions corresponding to the front-end page are v1-v4, and the DSL description file of the corresponding version is corresponded under each version, which is used to describe the UI component description information of the front-end page under each version. The UI components corresponding to the front-end page under the v1 version are UI component A, UI component B and UI component C, the versions of the three UI components are all V1, and the application version range commonly supported by the three UI components is v1.0-v1.3. Based on this, it can be determined that the application version range supported by the component library containing the three UI components is v1.0-v1.3, and the current component library version can be defined as v1.0.

[0034] As shown in Figure 1c , the UI components corresponding to the front-end page under the v2 version and the v3 version are UI component A, UI component B and UI component C. The version of UI component A is v2, and the versions of UI component B and UI component C are v1. Since the version of UI component A in the component library of the previous version has changed, the application version range commonly supported by the three UI components becomes v1.1-v1.4. Based on this, it can be determined that the application version range supported by the component library containing the three UI components is v1.1-v1.4. Since the application version range supported by the current component library is different from that of the previous component library, the current component library version can be defined as v1.1.

[0035] As shown in Figure 1cAs shown, the front-end page corresponds to UI component A, UI component B, UI component C and UI component D under the v4 version respectively; wherein, the version of UI component A is v2, the versions of UI component B and UI component C are v1, and the version of UI component D is v1, compared with the previous component library, UI component D is newly added, and the application version range supported by the four UI components is v1.5 or above; based on this, it can be determined that the application version range supported by the component library containing the four UI components is v1.5 or above; since the application version range supported by the current component library is different from that of the previous component library, the current component library version can be defined as v2.0.

[0036] Based on the above, when the DSL description file management device 20 receives a DSL description file request sent by an application of different versions, the target component library supporting the application version can be determined according to the requested application version, and the target DSL description file can be determined from at least one DSL description file corresponding to the target component library, and the target DSL description file is issued to the requested application, so that the application can realize dynamic rendering of the front-end page according to the UI component description information in the target DSL description file. For example, as shown in the figure, Figure 1c As shown, when the DSL description file management device 20 receives a DSL description file request sent by an application of v1.4 version, the version of the target component library can be determined to be v1.1 according to the application version range supported by each version of the component library; further, the target description file can be determined from the two DSL description files corresponding to the component library of v1.1 version and issued to the application of v1.4 version, so that it can dynamically render the front-end page.

[0037] In the embodiments of the present application, the specific manner of generating the DSL description file is not limited. Optionally, in the case where the component library generating device is not included in the DSL description file management system, when generating the DSL description file of the front-end page in different versions, the basic information and layout information of the plurality of UI components corresponding to the front-end page in different versions can be acquired, and the cascade relationship between the plurality of UI components can be determined according to the basic information and layout information of the plurality of UI components. Further, according to the application program version range supported by the plurality of UI components respectively, the application program range supported by the front-end page in different versions can be determined and used as the application program range supported by the DSL description file corresponding to the front-end page in different versions. Then, according to the cascade relationship between the plurality of UI components and the application program range supported by the DSL description file, the DSL description file of the front-end page in different versions can be generated. Based on this, when the DSL description file management device 20 receives the DSL description file request sent by the application program in different versions, the target DSL description file can be directly determined according to the version of the application program and the application program range supported by each DSL description file.

[0038] In another optional embodiment, in the case where the component library generating device is included in the DSL description file management system, when generating at least one DSL description file corresponding to each component library, the basic information and layout information of the plurality of UI components included in each component library can be acquired, and the cascade relationship between the plurality of UI components can be determined according to the basic information and layout information of the plurality of UI components, and at least one DSL description file corresponding to different versions of the component library can be generated according to the version of each component library and the cascade relationship. Further optionally, when generating each DSL description file, the application program version range supported by each component library can be used as the application program version range supported by at least one DSL description file corresponding to each component library, and the correspondence between the DSL description file and the component library can be established, so that in the case where the target component library is determined, at least one candidate DSL description file corresponding to the target component library can be determined. Further optionally, when the target DSL description file is determined in the at least one candidate DSL description file, the latest version DSL description file can be selected from at least one DSL description file corresponding to the target component library as the target DSL description file, which is issued to the application program, so that the application program can dynamically render the front-end page according to the target DSL description file.

[0039] In the embodiments of the present application, the specific content of the DSL description file is not limited. Optionally, the content of the DSL description file can include, in addition to the description information of the UI component in the front-end page, description information of the component library based on the above. As shown in Example 1 and Example 2, in the DSL description file, the name, version, application program version range supported by the component library, and other description information about the creator, type, attribute, supported platform, and the like of the component library can be included. The description information of the names of the plurality of UI components included in the component library and the application program versions supported by the plurality of UI components can also be included. It should be noted that the above is only an example for illustration. The specific content of the description information related to the version management of the DSL description file can be determined according to actual needs, which is not limited herein.

[0040] In the embodiments of the present application, the DSL description file request sent by the application program can determine the version information of the application program and the identifier of the target front-end page to be rendered. Then, according to the identifier of the target front-end page, at least one candidate DSL description file corresponding to the target front-end page under different versions can be determined. According to the version information of the application program and the application program version range supported by each candidate DSL description file, the target DSL description file corresponding to the version of the application program can be determined from the at least one candidate DSL description file. Based on this, the target DSL description file can be sent to the application program. Since the DSL description file in the present application does not have platform dependency, the DSL description file can be cross-platform issued to each platform, so that the application program of each platform can dynamically render the target front-end page according to the description information included in the target DSL description file. Based on the characteristic that the DSL description file has no platform dependency, the embodiments of the present application can realize unified management and cross-platform dynamic issuance of the DSL description file for different platforms, and can realize cross-platform dynamic rendering requirements.

[0041]

[0042] Example 1

[0043]

[0044] Example 2

[0045] Based on the above, the embodiments of the present application also provide a DSL description file management method, which can be applied to the DSL description file management system described above. Figure 2 The flowchart of the DSL description file management method provided by the embodiments of the present application is shown in Figure 2 The method comprises the following steps.

[0046] S1, receiving a DSL description file request sent by an application program, the DSL description file request comprising version information of the application program and identification of a target front-end page to be rendered;

[0047] S2, determining at least one candidate DSL description file corresponding to the target front-end page under different versions according to the identification of the target front-end page; wherein each candidate DSL description file has a corresponding supported application program version range;

[0048] S3, determining a target DSL description file corresponding to the version of the application program from the at least one candidate DSL description file according to the version information of the application program and the application program version range supported by each candidate DSL description file;

[0049] S4, sending the target DSL description file to the application program, so that the application program renders the target front-end page according to the description information included in the target DSL description file.

[0050] In an optional embodiment, the DSL description file management system comprises at least one component library corresponding to at least one front-end page, the at least one component library has different versions, the component libraries of different versions support different application program version ranges, each version of the component library corresponds to at least one DSL description file, and each component library includes UI components required by the corresponding front-end page; accordingly, when determining at least one candidate DSL description file corresponding to the target front-end page under different versions according to the identification of the target front-end page, at least one candidate component library corresponding to the target front-end page under different versions can be determined according to the identification of the target front-end page, and at least one DSL description file corresponding to the at least one candidate component library is taken as the at least one candidate DSL description file; accordingly, when determining a target DSL description file corresponding to the version of the application program from the at least one candidate DSL description file according to the version information of the application program and the application program version range supported by each candidate DSL description file, a target component library can be selected from the at least one candidate component library according to the version information of the application program and the application program version range supported by the at least one candidate component library, and a target DSL description file is selected from at least one DSL description file corresponding to the target component library.

[0051] In an optional embodiment, before receiving the request sent by the application program, the application program version range supported by each component library in at least one component library corresponding to the same front-end page and the version of each component library can also be determined; and at least one DSL description file corresponding to each component library can be generated according to the version of each component library and the supported application program version range.

[0052] In an optional embodiment, when determining the application version range supported by each component library in the at least one component library and the version of each component library, the application version supported by each UI component included in each component library in the at least one component library can be acquired respectively; and the application version range commonly supported by the plurality of UI components in each component library can be determined according to the application version supported by each UI component, as the application version range supported by each component library; in the case that the application version range supported by at least two component libraries is the same, the at least two component libraries are set as the same version; and in the case that the application version range supported by at least two component libraries is different, the at least two component libraries are set as different versions.

[0053] In an optional embodiment, when generating the at least one DSL description file corresponding to each component library according to the version of each component library and the supported application version range, the basic information and layout information of the plurality of UI components included in each component library can be acquired, and the cascade relationship between the plurality of UI components can be determined according to the basic information and the layout information; and the at least one DSL description file corresponding to each component library can be generated according to the version of each component library and the cascade relationship, and the application version range supported by each component library can be set as the application version range supported by the at least one DSL description file corresponding to the component library.

[0054] In an optional embodiment, when selecting the target DSL description file from the at least one DSL description file corresponding to the target component library, the latest version DSL description file can be selected from the at least one DSL description file as the target DSL description file.

[0055] In the embodiments of the present application, the version information of the application and the identifier of the target front-end page to be rendered can be determined through the DSL description file request sent by the application; then, the at least one candidate DSL description file corresponding to the target front-end page under different versions can be determined according to the identifier of the target front-end page; and the target DSL description file corresponding to the version of the application can be determined from the at least one candidate DSL description file according to the version information of the application and the application version range supported by each candidate DSL description file; based on this, the target DSL description file can be sent to the application. Since the DSL description file in the present application does not have platform dependency, the DSL description file can be cross-platform issued to each platform, so that the application of each platform can dynamically render the target front-end page according to the description information included in the target DSL description file. Based on the platform-independent feature of the DSL description file, the embodiments of the present application can realize unified management and cross-platform dynamic issuance of DSL description files for different platforms, and can realize cross-platform dynamic rendering requirements.

[0056] It should be noted that the execution subject of each step of the method provided in the above embodiments can be the same device, or the method can also be executed by different devices as the execution subject. For example, the execution subject of steps S1 to S4 can be device A; for another example, the execution subject of steps S1 to S3 can be device A, and the execution subject of step S4 can be device B; and the like.

[0057] In addition, in some of the processes described in the above embodiments and the accompanying drawings, a plurality of operations appearing in a certain order are included, but it should be clearly understood that these operations can be executed in the order appearing in the text or in parallel, and the serial numbers of the operations such as S1, S2, etc. are only used to distinguish different operations, and the serial numbers themselves do not represent any execution order. In addition, these processes can include more or fewer operations, and the operations can be executed in sequence or in parallel. It should be noted that the "first", "second", and the like described herein are used to distinguish different messages, devices, modules, etc., and do not represent the order of precedence, nor do "first" and "second" represent different types.

[0058] The embodiment of the present application also provides a DSL description file generation device. Applied to a DSL description file management system, wherein the DSL description file management system includes at least one DSL description file corresponding to a front-end page, and each DSL description file includes description information of a UI component required by the front-end page corresponding thereto. The DSL description file generation device can be realized as a virtual device in a communication controller (CCU), such as an application program. As shown in the figure, the DSL description file generation device includes a receiving module 301, a first processing module 302, a second processing module 303, and a sending module 304; wherein: Figure 3

[0059] The receiving module 301 is configured to receive a DSL description file request sent by an application program, wherein the DSL description file request includes version information of the application program and an identifier of a target front-end page to be rendered;

[0060] The first processing module 302 is configured to determine at least one candidate DSL description file corresponding to the target front-end page under different versions according to the identifier of the target front-end page; wherein each candidate DSL description file has a corresponding supported application program version range;

[0061] The second processing module 303 is configured to determine a target DSL description file corresponding to the version of the application program from the at least one candidate DSL description file according to the version information of the application program and the application program version range supported by each candidate DSL description file;

[0062] ​The sending module 304 is configured to send the target DSL description file to the application program, so that the application program renders the target front-end page according to the description information included in the target DSL description file.

[0063] In an optional embodiment, the DSL description file management system comprises at least one component library corresponding to at least one front-end page, the at least one component library has different versions, the component libraries of different versions support different ranges of application program versions, each version of the component library corresponds to at least one DSL description file, and each component library includes the UI components required by the corresponding front-end page; when determining the at least one candidate DSL description file corresponding to the target front-end page under different versions according to the identifier of the target front-end page, the first processing module 302 is configured to determine the at least one candidate component library corresponding to the target front-end page under different versions according to the identifier of the target front-end page, and take the at least one DSL description file corresponding to the at least one candidate component library as the at least one candidate DSL description file; when determining the target DSL description file corresponding to the version of the application program from the at least one candidate DSL description file according to the version information of the application program and the range of application program versions supported by each candidate DSL description file, the second processing module 303 is configured to select the target component library from the at least one candidate component library according to the version information of the application program and the range of application program versions supported by the at least one candidate component library respectively, and select the target DSL description file from the at least one DSL description file corresponding to the target component library.

[0064] In an optional embodiment, before receiving the request sent by the application program, the first processing module 302 is further configured to determine the range of application program versions supported by each component library in the at least one component library corresponding to the same front-end page and the version of each component library, and generate at least one DSL description file corresponding to each component library according to the version of each component library and the range of application program versions supported by each component library.

[0065] In an optional embodiment, when determining the range of application program versions supported by each component library in the at least one component library and the version of each component library, the first processing module 302 is configured to acquire the range of application program versions supported by a plurality of UI components included in each component library in the at least one component library respectively, and determine the range of application program versions supported by the plurality of UI components in each component library in common as the range of application program versions supported by each component library according to the range of application program versions supported by the plurality of UI components respectively; in the case that the range of application program versions supported by at least two component libraries is the same, set the at least two component libraries as the same version; and in the case that the range of application program versions supported by at least two component libraries is different, set the at least two component libraries as different versions.

[0066] In an optional embodiment, the first processing module 302 is configured to: obtain basic information and layout information of the plurality of UI components included in each component library according to the version of each component library and the supported application version range, and determine a cascade relationship between the plurality of UI components according to the basic information and the layout information; and generate at least one DSL description file corresponding to each component library according to the version of each component library and the cascade relationship, and set the application version range supported by each component library as the application version range supported by the at least one DSL description file corresponding to the component library.

[0067] In an optional embodiment, the second processing module 303 is configured to: select a latest version DSL description file from the at least one DSL description file corresponding to the target component library as the target DSL description file when selecting the target DSL description file from the at least one DSL description file corresponding to the target component library.

[0068] It should be noted that the specific functions and implementation processes of the modules in the above apparatus can refer to the method embodiments described above, and will not be described here.

[0069] The embodiments of the present application also provide a DSL description file management device, Figure 4 As shown in the structural schematic diagram of the DSL description file management device, Figure 4 The DSL description file management device includes a processor 41 and a memory 42 storing computer programs; wherein the processor 41 and the memory 42 can be one or more.

[0070] The memory 42 is mainly used for storing computer programs, which can be executed by the processor 41, so that the processor 41 controls the DSL description file management device to realize corresponding functions, complete corresponding actions or tasks. In addition to storing computer programs, the memory 42 can also be configured to store other various data to support operations on the DSL description file management device. Examples of these data include instructions for any application or method operating on the DSL description file management device.

[0071] The memory 42 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.

[0072] In the embodiments of the present application, the implementation form of the processor 41 is not limited, for example, but not limited to CPU, GPU or MCU, etc. The processor 41 can be regarded as a control system of the DSL description file management device, which can be used to execute the computer program stored in the memory 42 to control the DSL description file management device to realize corresponding functions, complete corresponding actions or tasks. It should be noted that, according to the implementation form of the DSL description file management device and the different scenarios it is in, the functions it needs to realize, the actions or tasks it needs to complete will be different; accordingly, the computer program stored in the memory 42 will also be different, and the processor 31 executing different computer programs can control the DSL description file management device to realize different functions, complete different actions or tasks.

[0073] In some optional embodiments, as shown in Figure 4 The DSL description file management device can further include other components such as a display 43, a power supply component 44 and a communication component 45. Figure 4 Only part of the components are shown in the figure, which does not mean that the DSL description file management device only includes Figure 4 The DSL description file management device can also include other components for different application requirements, for example, as shown in Figure 4 The DSL description file management device can also include an audio component 46. As for the components that the DSL description file management device can include, it can be determined according to the product form of the DSL description file management device, which is not limited here.

[0074] In the embodiments of the present application, when the processor executes the computer program in the memory, it is used to: receive a DSL description file request sent by an application program, wherein the DSL description file request includes version information of the application program and an identifier of a target front-end page to be rendered; determine at least one candidate DSL description file corresponding to the target front-end page under different versions according to the identifier of the target front-end page; wherein each candidate DSL description file has a corresponding supported application program version range; determine a target DSL description file corresponding to the version of the application program from the at least one candidate DSL description file according to the version information of the application program and the application program version range supported by each candidate DSL description file; and send the target DSL description file to the application program, so that the application program renders the target front-end page according to the description information included in the target DSL description file. Based on the platform-independent characteristics of the DSL description file, the embodiments of the present application can realize unified management and cross-platform dynamic distribution of DSL description files of different platforms, and can realize cross-platform dynamic rendering requirements.

[0075] It should be noted that the specific functions of the processor in the above electronic device can be referred to the method embodiments described above, and will not be repeated here.

[0076] Correspondingly, the embodiments of the present application also provide a computer readable storage medium storing a computer program, which can implement the steps performed by the DSL description file management device in the above method embodiments when executed.

[0077] The communication component in the above embodiments is configured to facilitate wired or wireless communication between the device where the communication component is located and other devices. The device where the communication component is located can access a wireless network based on a communication standard, such as a WiFi, 2G, 3G, 4G / LTE, 5G, or the like mobile communication network, or a combination thereof. In an example embodiment, the communication component receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In an example embodiment, the communication component further includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0078] The display in the above embodiments includes a screen, which can include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense a touch, a slide, and a gesture on the touch panel. The touch sensor can not only sense a boundary of a touch or a slide action, but also detect a duration and a pressure related to the touch or slide action.

[0079] The power supply component in the above embodiments provides power to various components of the device where the power supply component is located. The power supply component can include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power to the device where the power supply component is located.

[0080] The audio component in the above embodiments can be configured to output and / or input audio signals. For example, the audio component includes a microphone (MIC) configured to receive external audio signals when the device where the audio component is located is in an operation mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals can be further stored in the memory or transmitted via the communication component. In some embodiments, the audio component also includes a speaker for outputting audio signals.

[0081] Those skilled in the art will appreciate that embodiments of the application can be readily used as a method, a system or a computer program product. Accordingly, the application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the application can take the form of a computer program product on one or more computer readable storage media (including, but not limited to, disk memory, CD-ROMs, optical storage devices, etc.) embodying computer readable program code.

[0082] The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks or in the flowchart one or more blocks and / or in the block or blocks of the block diagram.

[0083] These computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instructions which implement the function specified in the flowchart block or blocks or in the flowchart one or more blocks and / or in the block or blocks of the block diagram.

[0084] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks or in the flowchart one or more blocks and / or in the block or blocks of the block diagram.

[0085] In one typical configuration, the computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0086] The memory can include non-persistent memory and / or volatile memory, such as random access memory (RAM) and / or cache memory, non-volatile memory, such as read-only memory (ROM), EPROM, and / or flash memory, etc. The memory is an example of computer readable media.

[0087] Computer-readable media includes permanent and non-permanent, movable and non-movable media that can implement information storage by any method or technology. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information accessible to a computing device. According to the definition herein, computer-readable media does not include transitory media such as modulated data signals and carriers.

[0088] It should also be noted that the terms "comprising", "containing", or any other variant thereof are intended to cover a non-exclusive inclusion, such that a process, method, article or apparatus that comprises a list of elements does not only include those elements, but can also include other elements not expressly listed or inherent to such process, method, article or apparatus. Without more limitations, the element defined by the statement "comprising a" does not exclude the presence of additional identical elements in the process, method, article or apparatus that includes the element.

[0089] The above only describes the embodiments of the present application and is not intended to limit the present application. For those skilled in the art, the present application can have various modifications and changes. Any modification, equivalent replacement, improvement, etc. within the spirit and principle of the present application shall be included in the scope of claims of the present application.

Claims

1. A DSL description file management method, applied to a DSL description file management system, characterized in that, The DSL description file management system includes at least one DSL description file corresponding to a front-end page. Each DSL description file includes description information of the UI components required for its corresponding front-end page. The DSL description file management system includes at least one component library corresponding to at least one front-end page. The at least one component library has different versions, and different versions of the component library support different application version ranges. Each version of the component library corresponds to at least one DSL description file, and each component library includes the UI components required for its corresponding front-end page. The method includes: For at least one component library corresponding to the same front-end page, determine the application version range supported by each component library and the version of each component library; based on the version of each component library and the supported application version range, generate at least one DSL description file corresponding to each component library; Receive a DSL description file request sent by an application, the DSL description file request including the application version information and the identifier of the target front-end page to be rendered; Based on the identifier of the target front-end page, at least one candidate component library corresponding to the target front-end page under different versions is determined, and at least one DSL description file corresponding to the at least one candidate component library is used as the at least one candidate DSL description file; wherein, each candidate DSL description file has a corresponding supported application version range; Based on the application version information and the application version range supported by the at least one candidate component library, a target component library is selected from the at least one candidate component library, and a target DSL description file is selected from the at least one DSL description file corresponding to the target component library; The target DSL description file is sent to the application so that the application can render the target front-end page based on the description information included in the target DSL description file; Determining the application version range supported by each component library in the at least one component library and the version of each component library includes: For each component library in the at least one component library, obtain the application versions supported by the multiple UI components contained therein; Based on the application versions supported by the multiple UI components, the range of application versions commonly supported by the multiple UI components in each component library is determined, and this range is used as the range of application versions supported by each component library. If at least two component libraries support the same application version range, set the at least two component libraries to the same version; If at least two component libraries support different application version ranges, set the at least two component libraries to different versions.

2. The method according to claim 1, characterized in that, Based on the version of each component library and the range of supported application versions, generate at least one DSL description file for each component library, including: Retrieve basic information and layout information of multiple UI components contained in each component library; The cascading relationships between the multiple UI components are determined based on the basic information and layout information; Based on the version of each component library and the cascading relationship, at least one DSL description file is generated for each component library, and the application version range supported by each component library is taken as the application version range supported by the at least one DSL description file corresponding to the component library.

3. The method according to any one of claims 1-2, characterized in that, Selecting a target DSL description file from at least one DSL description file corresponding to the target component library includes: Select the latest version of the DSL description file from the at least one DSL description file as the target DSL description file.

4. A DSL profile management device, applied to a DSL profile management system, characterized in that, The DSL description file management system includes at least one DSL description file corresponding to a front-end page. Each DSL description file includes description information of the UI components required by its corresponding front-end page. The DSL description file management system includes at least one component library corresponding to at least one front-end page. The at least one component library has different versions, and different versions support different application version ranges. Each version of the component library corresponds to at least one DSL description file, and each component library includes the UI components required for its corresponding front-end page. The device includes: The first processing module is configured to, for at least one component library corresponding to the same front-end page, determine the application version range supported by each component library and the version of each component library; and generate at least one DSL description file corresponding to each component library based on the version of each component library and the supported application version range; wherein, determining the application version range supported by each component library and the version of each component library includes: for each component library, obtaining the application versions supported by its multiple UI components respectively; determining the application version range commonly supported by the multiple UI components in each component library based on the application versions supported by the multiple UI components respectively, and using this as the application version range supported by each component library; if at least two component libraries support the same application version range, setting the at least two component libraries to the same version; if at least two component libraries support different application version ranges, setting the at least two component libraries to different versions; The receiving module is used to receive a DSL description file request sent by the application, wherein the DSL description file request includes the version information of the application and the identifier of the target front-end page to be rendered; The first processing module is further configured to determine at least one candidate component library corresponding to different versions of the target front-end page based on the identifier of the target front-end page, and use at least one DSL description file corresponding to the at least one candidate component library as the at least one candidate DSL description file; wherein, each candidate DSL description file has a corresponding supported application version range; The second processing module is used to select a target component library from the at least one candidate component library based on the version information of the application and the application version range supported by the at least one candidate component library, and to select a target DSL description file from at least one DSL description file corresponding to the target component library. The sending module is used to send the target DSL description file to the application, so that the application can render the target front-end page according to the description information included in the target DSL description file.

5. A DSL description file management system, characterized in that, The system includes: a DSL description file generation device and a DSL description file management device; The DSL description file generation device is used to generate DSL description files corresponding to at least one front-end page under different versions. Each DSL description file includes description information of the UI components required by its corresponding front-end page. Based on the application version information supported by the UI components contained in each DSL description file, the device determines the range of application versions supported by each DSL description file. At least one front-end page corresponds to at least one component library, which has different versions. Different versions of the component library support different ranges of application versions. Each version of the component library corresponds to at least one DSL description file, and each component library includes the UI components required by its corresponding front-end page. The DSL description file management device is used to determine at least one candidate component library corresponding to the target front-end page under different versions based on the identifier of the target front-end page to be rendered, and to use at least one DSL description file corresponding to the at least one candidate component library as the at least one candidate DSL description file. Each candidate DSL description file has a corresponding supported range of application versions. Based on the application version information and the application version ranges supported by the at least one candidate component library, a target component library is selected from the at least one candidate component library, and a target DSL description file is selected from the at least one DSL description file corresponding to the target component library. The target DSL description file is sent to the application so that the application can render the target front-end page; When generating DSL description files corresponding to at least one front-end page in different versions, the DSL description file generation device determines, for at least one component library corresponding to the same front-end page, the application version range supported by each component library and the version of each component library; based on the version of each component library and the supported application version range, it generates at least one DSL description file corresponding to each component library; wherein, determining the application version range supported by each component library and the version of each component library includes: for each component library, obtaining the application versions supported by its multiple UI components respectively; determining the application version range commonly supported by the multiple UI components in each component library based on the application versions supported by the multiple UI components respectively, as the application version range supported by each component library; if at least two component libraries support the same application version range, setting the at least two component libraries to the same version; if at least two component libraries support different application version ranges, setting the at least two component libraries to different versions.

6. A DSL description file management system, characterized in that, The system includes: a component library generation device, a DSL description file generation device, and a DSL description file management device; The component library generation device is used to generate at least one component library corresponding to at least one front-end page. Each component library includes multiple UI components, and the multiple UI components correspond to the application versions they support. Based on the application versions supported by the multiple UI components included in each component library, the application version range supported by each component library and the version of each component library are determined. The DSL description file generation device is used to generate DSL description files corresponding to at least one front-end page in different versions. Each DSL description file includes description information of the UI components required for its corresponding front-end page. The at least one component library has different versions, and the different versions of the component library support different application version ranges. Each version of the component library corresponds to at least one DSL description file, and each component library includes the UI components required for its corresponding front-end page. The DSL description file management device is used to determine at least one candidate component library corresponding to different versions of the target front-end page based on the identifier of the target front-end page to be rendered, establish a correspondence between the component library version and the DSL description files of different versions, and use at least one DSL description file corresponding to the at least one candidate component library as at least one candidate DSL description file; wherein, each candidate DSL description file has a corresponding supported application version range; select a target component library from the at least one candidate component library according to the application version information and the application version range supported by the at least one candidate component library, select a target DSL description file from the at least one DSL description file corresponding to the target component library; and send the target DSL description file to the application so that the application can render the target front-end page; When generating DSL description files corresponding to at least one front-end page in different versions, the DSL description file generation device determines, for at least one component library corresponding to the same front-end page, the application version range supported by each component library and the version of each component library; based on the version of each component library and the supported application version range, it generates at least one DSL description file corresponding to each component library; wherein, determining the application version range supported by each component library and the version of each component library includes: for each component library, obtaining the application versions supported by its multiple UI components respectively; determining the application version range commonly supported by the multiple UI components in each component library based on the application versions supported by the multiple UI components respectively, as the application version range supported by each component library; if at least two component libraries support the same application version range, setting the at least two component libraries to the same version; if at least two component libraries support different application version ranges, setting the at least two component libraries to different versions.

7. A DSL description file management device, characterized in that, include: Processor and memory storing computer programs; The processor is configured to execute the computer program for: For at least one component library corresponding to the same front-end page, determine the application version range supported by each component library and the version of each component library; generate at least one DSL description file corresponding to each component library based on the version of each component library and the supported application version range; wherein, determining the application version range supported by each component library and the version of each component library includes: for each component library, obtaining the application versions supported by its multiple UI components respectively; determining the application version range commonly supported by the multiple UI components in each component library based on the application versions supported by the multiple UI components respectively, and using this as the application version range supported by each component library; if at least two component libraries support the same application version range, setting the at least two component libraries to the same version; if at least two component libraries support different application version ranges, setting the at least two component libraries to different versions; Receive a DSL description file request sent by an application, the DSL description file request including the application version information and the identifier of the target front-end page to be rendered; Based on the identifier of the target front-end page, at least one candidate component library corresponding to the target front-end page under different versions is determined, and at least one DSL description file corresponding to the at least one candidate component library is used as the at least one candidate DSL description file; wherein, each candidate DSL description file has a corresponding supported application version range; Based on the application version information and the application version range supported by the at least one candidate component library, a target component library is selected from the at least one candidate component library, and a target DSL description file is selected from the at least one DSL description file corresponding to the target component library; The target DSL description file is sent to the application so that the application can render the target front-end page based on the description information included in the target DSL description file; In this embodiment, at least one front-end page corresponds to at least one component library, and the at least one component library has different versions. Different versions of the component library support different application version ranges. Each version of the component library corresponds to at least one DSL description file, and each component library includes the UI components required by its corresponding front-end page.

8. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it causes the processor to perform the steps of the method according to any one of claims 1-3.

Images