CN114489721A - DSL description file management method, apparatus, system, device and medium - Google Patents

Abstract

The embodiment of the application provides a DSL description file management method, a device, a system, equipment and a medium. Determining version information of the application program and an identifier of a target front-end page to be rendered through a DSL description file request sent by the application program; 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; determining a target DSL description file corresponding to the version of the application program from at least one candidate DSL description file according to the version information of the application program and the version range of the application program supported by each candidate DSL description file; based on this, the target DSL description file may be issued to the application for rendering the target front-end page by the application according to the target DSL description file. According to the embodiment of the application, the DSL description files of different platforms can be managed in a unified mode and dynamically issued in a cross-platform mode, and dynamic rendering requirements of the cross-platform mode can be met.

Description

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

technical field

The present application relates to the field of computer technology, and in particular, to a DSL description file management method, apparatus, system, device, and medium.

Background technique

In the process of application development, it often involves optimizing and upgrading some functional modules. During this process, it may involve updating some components in the functional modules. Compared with the original components, the updated components are equivalent to a new version of the component.

Usually, different versions of applications may be compatible with different component versions. If the current version of the application cannot be compatible with the new version of the component, the new version of the component cannot be rendered normally. Therefore, in order to ensure that the component can be rendered normally in the application when the component is updated, it is necessary to manage the version correspondence between the component and the application.

SUMMARY OF THE INVENTION

Various aspects of the present application provide a DSL description file management method, apparatus, system, device and medium for managing the version correspondence between components and applications.

An embodiment of the present application provides a DSL description file management method, which 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, and each DSL description file includes all of its corresponding front-end page. The description information of the UI component is required, and the method includes: receiving a DSL description file request sent by an application, where the DSL description file request includes version information of the application and an identifier of the target front-end page to be rendered; The identifier of the front-end page, to determine at least one candidate DSL description file corresponding to the target front-end page under different versions; wherein, each candidate DSL description file has a corresponding supported application version range; according to the version of the application information and an application version range supported by each candidate DSL description file, determine a target DSL description file corresponding to the version of the application from the at least one candidate DSL description file; 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.

In an optional embodiment, 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 the range of application versions supported by the component libraries of different versions. Differently, each version of the component library corresponds to at least one of the DSL description files, and each component library includes the UI components required by its corresponding front-end page; correspondingly, according to the identifier of the target front-end page, determine the target At least one candidate DSL description file corresponding to front-end pages under different versions, including: according to the identifier of the target front-end page, determining at least one candidate component library corresponding to the target front-end page under different versions, and describing the at least one candidate component library At least one DSL description file corresponding to the component library is used as the at least one candidate DSL description file; correspondingly, according to the version information of the application and the application version range supported by each of the candidate DSL description files, from the at least one candidate DSL description file Determining a target DSL description file corresponding to the version of the application in a candidate DSL description file includes: according to the version information of the application and the application version range supported by the at least one candidate component library respectively, from the A target component library is selected from at least one candidate component library, and the target DSL description file is selected from at least one DSL description file corresponding to the target component library.

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

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 includes: for each component library in the at least one component library, obtaining The application version supported by the multiple UI components contained in it; determine the application version range supported by the multiple UI components in each component library according to the application versions supported by the multiple UI components respectively, as the 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 to the same version; when there are at least two component libraries supported In the case where the version ranges of the applications are different, the at least two component libraries are set to different versions.

In an optional embodiment, generating 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, including: obtaining multiple UI components included in each component library basic information and layout information; determine the cascading relationship between the multiple UI components according to the basic information and layout information; generate each component library according to the version of each component library and the cascading relationship corresponding at least one DSL description file, and use 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.

In an optional embodiment, selecting a target DSL description file from at least one DSL description file corresponding to the target component library includes: selecting a DSL description file of the latest version from the at least one DSL description file as the target DSL description file.

An embodiment of the present application further provides a DSL description file management device, which 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, and each DSL description file includes its corresponding front-end page. Description information of the required UI components, the apparatus includes: a receiving module, configured to receive a DSL description file request sent by an application, where the DSL description file request includes version information of the application and the target front-end page to be rendered. identification; a first processing module, configured to determine, according to the identification of the target front-end page, at least one candidate DSL description file corresponding to the target front-end page under different versions; wherein each of the candidate DSL description files has corresponding support the application version range; the second processing module is configured to, according to the version information of the application and the application version range supported by each of the candidate DSL description files, determine from the at least one candidate DSL description file The target DSL description file corresponding to the version of the application; the sending module is configured to send the target DSL description file to the application, so that the application can render the target DSL description file according to the description information included in the target DSL description file. the target front-end page.

An embodiment of the present application further provides a DSL description file management system, the system includes: a DSL description file generation device and a DSL description file management device; the DSL description file generation device is configured to generate a different version from at least one front-end page The corresponding DSL description file below, each DSL description file includes the description information of the UI components required by its corresponding front-end page; according to the application version information supported by the UI components contained in each DSL description file, determine what each DSL description file supports. application version range; the DSL description file management device is used 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 to be rendered; The version information of the application of the front-end page and the application version range supported by each DSL description file, and the target DSL description file that supports the version of the application is determined from the at least one candidate DSL description file; The DSL description file is sent to the application, so that the application can render the target front-end page.

An embodiment of the present application further provides a DSL description file management system, 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 and at least one front end At least one component library corresponding to the page, each component library includes multiple UI components, and the multiple UI components correspond to the application versions supported by them; according to the application programs supported by the multiple UI components included in each component library version, to determine the application version range supported by each component library and the version of each component library; the DSL description file generating 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 UI components required by its corresponding front-end page; the DSL description file management device is used to determine at least one candidate corresponding to the target front-end page according to the identifier of the target front-end page to be rendered A component library; establishing a corresponding relationship between a component library version and DSLs of different versions, and determining a target component library and the target from the at least one candidate component library according to the version information of the application including the target front-end page at least one DSL description file corresponding to the component library; select a target DSL description file from the at least one DSL description file, and send the target DSL description file to the application, so that the application can render the The target front-end page.

An embodiment of the present application further provides a DSL description file management device, including: a processor and a memory storing a computer program; the processor is configured to execute the computer program, so as to: receive a DSL description sent by an application program A file request, the DSL description file request includes the version information of the application and the identifier of the target front-end page to be rendered; according to the identifier of the target front-end page, at least one corresponding to the target front-end page under different versions is determined A candidate DSL description file; wherein each candidate DSL description file has a corresponding supported application version range; according to the version information of the application and the application version range supported by each candidate DSL description file, from the determining a target DSL description file corresponding to the version of the application program in the at least one candidate DSL description file; sending the target DSL description file to the application program, so that the application program can use the target DSL description file according to the target DSL description file The included description information renders the target front-end page.

Embodiments of the present application further provide a computer-readable storage medium storing a computer program, and when the computer program is executed by a processor, the processor causes the processor to implement the steps in the method claims.

In the embodiment 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; furthermore, according to the identifier of the target front-end page, it can be determined that the target front-end page is in different versions At least one candidate DSL description file corresponding to the following; and according to the version information of the application and the application version range supported by each candidate DSL description file, the target DSL corresponding to the version of the application can be determined from the at least one candidate DSL description file. description file; based on this, the target DSL description file can be sent 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. Based on the feature that DSL description files have no platform dependency, the embodiments of the present application can implement unified management and cross-platform dynamic distribution of DSL description files of different platforms, and can realize cross-platform dynamic rendering requirements.

Description of drawings

The drawings described herein are used to provide further understanding of the present application and constitute a part of the present application. The schematic embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation of the present application. In the attached image:

FIG. 1a is a schematic structural diagram of a DSL description file management system provided by an embodiment of the present application;

FIG. 1b is a schematic structural diagram of another DSL description file management system provided by an embodiment of the present application;

FIG. 1c is a schematic diagram of the correspondence between a DSL description file and a component library provided by an embodiment of the present application;

2 is a flowchart of a method for managing a DSL description file provided by an embodiment of the present application;

FIG. 3 provides a schematic structural diagram of an apparatus for managing a DSL description file according to an embodiment of the present application;

FIG. 4 is a schematic structural diagram of a DSL description file management device according to an embodiment of the present application.

Detailed ways

In order to make the objectives, technical solutions and advantages of the present application clearer, the technical solutions of the present application will be clearly and completely described below with reference to the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

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 front-end pages under different versions, and request each platform to request a DSL description file for each platform. Distribute the corresponding version of the DSL description file; among them, the DSL description file is a description file with a general data format without platform characteristics obtained by abstracting and re-expressing the front-end page. The DSL description file does not depend on the specific application of the front-end page. Platform, the DSL description file management system can distribute DSL description files to different platforms, so as to achieve cross-platform distribution of DSL description files, so that different platforms can dynamically render front-end pages according to the DSL description files.

FIG. 1a is a schematic structural diagram of a DSL description file management system provided in this embodiment. As shown in FIG. 1a, the system includes a DSL description file generation device 10 and a DSL description file management device 20; wherein, the DSL description file generation device 10 is used for A DSL description file corresponding to at least one front-end page in different versions is generated, and each DSL description file includes description information of UI components required by the corresponding front-end page. In this embodiment, the DSL description file generating device 10 is further configured to determine the range of application versions supported by each DSL description file according to the application version information supported by the UI components contained in each DSL description file, for the DSL description The file management device 20 delivers the DSL description file of the corresponding version to the application according to the application version range supported by each DSL description file, so that the application can render the target front-end page.

As shown in FIG. 1a, in this embodiment, the DSL description file management device 20 is configured to receive a DSL description file request sent by an application program of each platform; wherein, the DSL description file request includes the version information of the application program and the target to be rendered The identity of the front-end page. 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 under different versions according to the identifier of the target front-end page to be rendered, and according to the version information of the application and each DSL description file The supported application version range, determine the target DSL description file of the version that supports the application from at least one candidate DSL description file, and send the target DSL description file to the application, so that the application can render the target front-end page.

An embodiment of the present application further provides a DSL description file management system. FIG. 1b is a schematic structural diagram of the DSL description file management system provided in this embodiment. As shown in FIG. 1b, the system includes a component library generation device 30 and a DSL description file generation device 10. and a DSL description file management device 20; wherein, the function of the DSL description file generation device 10 is similar to that of the above-mentioned embodiment, and is used to generate a DSL description file corresponding to at least one front-end page under different versions; wherein, each DSL description file includes It corresponds to the description information of the UI components required by the front-end page.

In this embodiment, the component library generating device 30 is configured 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 included in each component library are UI components on the front-end page corresponding to each component library; wherein, multiple UI components correspond to the application versions they support. 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 versions supported by the multiple UI components included in each component library; The version of the library means that when there is an update of UI components in the component library, if the version range of the application supported by the component library changes, the component library containing the updated UI components will be the same as the one containing the UI components before the update. The component libraries correspond to different versions.

In this embodiment, as shown in FIG. 1b, the DSL description file management device 20 is configured to receive a DSL description file request sent by an application program of each platform; wherein, the DSL description file request includes the version information of the application program and the target to be rendered The identity of the front-end page. 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 identifier of the target front-end page to be rendered, and according to the version information of the application and the application version supported by each component library The scope determines the target component library from at least one candidate component library.

In this embodiment, the multiple UI components contained in each component library may be multiple UI components of the front-end page under different versions, and the front-end page corresponds to different DSL description files under different versions; based on this, as shown in the figure As shown in 1b, the DSL description file management device 20 can also establish the corresponding relationship between the component library and the DSL description file according to the DSL description files corresponding to the UI components contained in each component library; Correspondence between DSLs, determine at least one DSL description file corresponding to the target component library, 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 that the application can render the target front page.

In an optional embodiment of the present application, before receiving the request sent by the application, the DSL description file management device 20 may further determine, for at least one component library corresponding to the same front-end page, the application supported by each component library in the at least one component library Program version range and version of each component library. Optionally, for each component library in at least one component library, the application versions supported by the multiple UI components contained therein may be obtained, and the number of application versions in each component library may be determined according to the application versions supported by the multiple UI components respectively. The application version range supported by each UI component is used as the application version range supported by each component library. Further, in the case where the application version ranges supported by at least two component libraries are the same, the at least two component libraries are set to the same version, and in the case where the application version ranges supported by at least two component libraries are different, Set at least two component libraries to different versions.

FIG. 1c is a schematic diagram of the correspondence between the DSL description files corresponding to different versions of the front-end page provided by the embodiment of the present application, the component libraries of different versions, and the range of application versions supported by them; wherein, the application is illustrated by taking APP as an example. . As shown in Figure 1c, the four versions corresponding to the front-end page are v1-v4, and each version has a corresponding version of the DSL description file, which is used to describe the UI component description information of the front-end page in each version. Among them, the corresponding UI components of the front-end page in the v1 version are UI component A, UI component B, and UI component C. The versions of these three UI components are all V1, and the application version range 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 these three UI components is v1.0-v1.3, and the current component library version can be defined as v1.0.

As shown in Figure 1c, the corresponding UI components of the front-end page under the v2 version and the v3 version are UI component A, UI component B and UI component C respectively; among them, the version of UI component A is v2, and the version of UI component B and UI component C is version is v1. Compared with the previous version of the component library, the version of UI component A has changed, resulting in the application version range supported by these three UI components becoming v1.1-v1.4; Based on this, it can be determined that the application version range supported by the component library containing these three UI components is v1.1-v1.4; since the current component library supports a different application version range compared with the previous component library, therefore, The current component library version can be defined as v1.1.

As shown in Figure 1c, the corresponding UI components of the front-end page in the v4 version are UI component A, UI component B, UI component C and UI component D; among them, the version of UI component A is v2, and the version of UI component B and UI component is The version of C is v1, and the version of UI component D is v1. Compared with the previous version of the component library, UI component D is newly added. The application version range supported by these four UI component functions is v1.5 or above; Based on this, it can be determined that the application version range supported by the component library including these four UI components is v1.5 or above; since the current component library The version can be defined as v2.0.

Based on the above, when the DSL description file management device 20 receives a DSL description file request sent by an application of a different version, it can determine a target component library that supports the application version according to the requested application version, and correspondingly from the target component library Determine the target DSL description file in at least one of the DSL description files, and deliver the target DSL description file to the requesting application, so that the application can dynamically render the front-end page according to the UI component description information in the target DSL description file. For example, as shown in Fig. 1c, when the DSL description file management device 20 receives a DSL description file request initiated by an APP of version v1.4, it can determine the version of the target component library according to the application version range supported by each version of the component library It is v1.1; further, the target description file can be determined from the two DSL description files corresponding to the component library of version v1.1 and delivered to the APP of version v1.4 for it to dynamically render the front-end page.

In the embodiment of the present application, the specific method of generating the DSL description file is not limited. Optionally, in the case where the component library generation device is not included in the DSL description file management system, the DSL description file of the front-end page under different versions is generated. , the basic information and layout information of multiple UI components corresponding to different versions of the front-end page can be obtained, and the cascading relationship between multiple UI components can be determined according to the basic information and layout information of multiple UI components; further, according to The range of application versions supported by multiple UI components can determine the range of applications supported by the front-end page under different versions and serve as the range of applications supported by the corresponding DSL description files of the front-end page under different versions; further, according to multiple UI The cascading relationship between components and the application scope supported by the DSL description file can generate DSL description files for front-end pages under different versions. Based on this, when the DSL description file management device 20 receives DSL description file requests sent by applications of different versions, it can directly determine the target DSL description file according to the version of the application and the application range supported by each DSL description file.

In another optional embodiment, when the DSL description file management system includes a component library generating device, when generating at least one DSL description file corresponding to each component library, multiple Basic information and layout information of each UI component, and determine the cascading relationship between multiple UI components according to the basic information and layout information of multiple UI components, and generate different versions according to the version and cascading relationship of each component library At least one DSL description file corresponding to the component library. Further optionally, when generating each DSL description file, the application version range supported by each component library can also be used as the application version range supported by at least one DSL description file corresponding to each component library, and the DSL description file can be established. The corresponding relationship with the component library, so that when 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 at least one candidate DSL description file, the latest version of the DSL description file may be selected from at least one DSL description file corresponding to the target component library, and issued to the application as the target DSL description file. program, so that the application can dynamically render the front-end page according to the target DSL description file.

In the embodiment of the present application, the specific content of the DSL description file is not limited. Optionally, the content of the DSL description file may include the description of the component library based on the above, in addition to the description information of the UI components in the front-end page. information. As shown in Example 1 and Example 2 below, in the DSL description file, you can include the name and version of the component library, the application version range supported by the component library, and other description information about the creator, type, properties, supported platforms, etc., and also It can include the names of the multiple UI components contained in the component library and the description information of the application versions supported by them. It should be noted that the following is only an exemplary description, and the specific content of the description information related to the version management of the DSL description file can be determined according to actual requirements, which is not limited herein.

In the embodiment 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; furthermore, according to the identifier of the target front-end page, it can be determined that the target front-end page is in different versions At least one candidate DSL description file corresponding to the following; and according to the version information of the application and the application version range supported by each candidate DSL description file, the target DSL corresponding to the version of the application can be determined from the at least one candidate DSL description file. Description file; based on this, the target DSL description file can be sent to the application. Since the DSL description file in this application is not platform-dependent, it is possible to distribute the DSL description file to each platform across platforms, so that the applications of each platform can dynamically render the target front end according to the description information included in the target DSL description file. page. Based on the feature that DSL description files have no platform dependency, the embodiments of the present application can implement unified management and cross-platform dynamic distribution of DSL description files of different platforms, and can realize cross-platform dynamic rendering requirements.

Example 1

Example 2

Based on the above, an embodiment of the present application further provides a DSL description file management method, which can be applied to the above DSL description file management system. FIG. 2 is a flowchart of a DSL description file management method provided by an embodiment of the present application. As shown in FIG. 2 , the method includes:

S1. Receive a DSL description file request sent by an application, where the DSL description file request includes version information of the application and an identifier of the target front-end page to be rendered;

S2. 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 version range;

S3. According to the version information of the application and the application version range supported by each candidate DSL description file, determine a target DSL description file corresponding to the version of the application from at least one candidate DSL description file;

S4. 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.

In an optional embodiment, the DSL description file management system includes at least one component library corresponding to at least one front-end page, at least one component library has different versions, and different versions of the component library support different application version ranges. The component library of the version corresponds to at least one DSL description file, and each component library includes the UI components required by its corresponding front-end page; accordingly, according to the identification of the target front-end page, it is determined that the target front-end page corresponds to at least one of the different versions. When there is a candidate DSL description file, at least one candidate component library corresponding to the target front-end page under different versions can be determined according to the identifier of the target front-end page, and at least one DSL description file corresponding to the at least one candidate component library can be used as the at least one candidate DSL description Correspondingly, when determining the target DSL description file corresponding to the version of the application from 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, the target DSL description file corresponding to the version of the application can be determined according to the The version information of the application and the application version range supported by the at least one candidate component library respectively, select the target component library from the at least one candidate component library, and select the target DSL description file from at least one DSL description file corresponding to the target component library.

In an optional embodiment, before receiving the request sent by the application, the application version range and each component supported by each component library in the at least one component library may also be determined for at least one component library corresponding to the same front-end page. the version of the library; and generating 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.

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, you can obtain the information contained in the component library for each component library in the at least one component library. The application versions supported by the multiple UI components respectively; and the application version range supported by the multiple UI components in each component library is determined according to the application versions supported by the multiple UI components respectively, as the applications supported by each component library Version range; set at least two component libraries to the same version if the application version range supported by at least two component libraries is the same; and if the application version range supported by at least two component libraries is different , set at least two component libraries to different versions.

In an optional embodiment, when 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, multiple UIs contained in each component library can be obtained. Basic information and layout information of components, and determine the cascading relationship between multiple UI components according to the basic information and layout information; and generate at least one DSL corresponding to each component library according to the version and cascading relationship of each component library description file, and use the application version range supported by each component library as the application version range supported by at least one DSL description file corresponding to the component library.

In an optional embodiment, when the target DSL description file is selected from at least one DSL description file corresponding to the target component library, the latest version of the DSL description file may be selected from the at least one DSL description file as the target DSL description file.

In the embodiment 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; furthermore, according to the identifier of the target front-end page, it can be determined that the target front-end page is in different versions At least one candidate DSL description file corresponding to the following; and according to the version information of the application and the application version range supported by each candidate DSL description file, the target DSL corresponding to the version of the application can be determined from the at least one candidate DSL description file. Description file; based on this, the target DSL description file can be sent to the application. Since the DSL description file in this application is not platform-dependent, it is possible to distribute the DSL description file to each platform across platforms, so that the applications of each platform can dynamically render the target front end according to the description information included in the target DSL description file. page. Based on the feature that DSL description files have no platform dependency, the embodiments of the present application can implement unified management and cross-platform dynamic distribution of DSL description files of different platforms, and can realize cross-platform dynamic rendering requirements.

It should be noted that, the execution subject of each step of the method provided in the above-mentioned embodiments may be the same device, or the method may also be executed by different devices. For example, the execution subject of steps S1 to S4 may be device A; for another example, the execution subject of steps S1 to S3 may be device A, and the execution subject of step S4 may be device B; and so on.

In addition, in some of the processes described in the above embodiments and the accompanying drawings, multiple operations appearing in a specific order are included, but it should be clearly understood that these operations may be performed out of the order in which they appear in this document or performed in parallel , the sequence numbers of the operations, such as S1, S2, etc., are only used to distinguish different operations, and the sequence numbers themselves do not represent any execution order. Additionally, these flows may include more or fewer operations, and these operations may be performed sequentially or in parallel. It should be noted that the descriptions such as "first" and "second" in this document are used to distinguish different messages, devices, modules, etc., and do not represent a sequence, nor do they limit "first" and "second" are different types.

The embodiment of the present application also provides an apparatus for generating a DSL description file. It is 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 UI components required by its corresponding front-end page. The DSL description file generating device may be implemented as a virtual device in a Communication Control Unit (CCU), such as an application program. As shown in FIG. 3 , the apparatus for generating a DSL description file includes a receiving module 301, a first processing module 302, a second processing module 303 and a sending module 304; wherein:

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

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 version range;

The second processing module 303 is configured to determine a target DSL description file corresponding to the version of the application from 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;

The sending module 304 is configured 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.

In an optional embodiment, the DSL description file management system includes at least one component library corresponding to at least one front-end page, at least one component library has different versions, and different versions of the component library support different application version ranges. The component library of the version corresponds to at least one DSL description file, and each component library includes the UI components required by its corresponding front-end page; the first processing module 302 determines, according to the identifier of the target front-end page, that the target front-end page corresponds to different versions When the at least one candidate DSL description file is selected, it is used to determine 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 use at least one DSL description file corresponding to the at least one candidate component library as at least one A candidate DSL description file; the second processing module 303 determines a target DSL corresponding to the version of the application from 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 When describing the file, it is used to select 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 the at least one candidate component library, and select the target component library from the at least one DSL description file corresponding to the target component library. Select the target DSL description file.

In an optional embodiment, before the receiving module 301 receives the request sent by the application, the first processing module 302 is further configured to, for at least one component library corresponding to the same front-end page, determine that each component library in the at least one component library supports The application version range of each component library and the version of each component library; and 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.

In an optional embodiment, when the first processing module 302 determines the application version range supported by each component library in the at least one component library and the version of each component library, library, obtain the application versions supported by the multiple UI components contained in it; and determine the application version range jointly supported by the multiple UI components in each component library according to the application versions supported by the multiple UI components respectively, as each The range of application versions supported by the component library; in the case where the version range of the application supported by at least two component libraries is the same, set at least two component libraries to the same version; and in the case of applications supported by at least two component libraries In the case of different version ranges, set at least two component libraries to different versions.

In an optional embodiment, the first processing module 302 is configured to obtain each component library when generating 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. Basic information and layout information of multiple UI components contained in the library, and determine the cascading relationship between multiple UI components according to the basic information and layout information; and generate each component according to the version and cascading relationship of each component library at least one DSL description file corresponding to the library, and the application version range supported by each component library is used as the application version range supported by the at least one DSL description file corresponding to the component library.

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

It should be noted that, for the specific functions and implementation processes of the modules in the foregoing apparatus, reference may be made to the foregoing method embodiments, and details are not described herein again.

An embodiment of the present application further provides a DSL description file management device. FIG. 4 is a schematic structural diagram of the DSL description file management device. As shown in FIG. 4 , the DSL description file management device includes: a processor 41 and a memory 42 storing a computer program ; wherein, the processor 41 and the memory 42 may be one or more.

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

Memory 42, which may be implemented by any type of volatile or non-volatile storage device or 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 Memory, Flash Memory, Magnetic or Optical Disk.

In the embodiments of the present application, the implementation form of the processor 41 is not limited, for example, it may be, but not limited to, a CPU, a GPU, or an MCU. The processor 41 can be regarded as a control system of the DSL description file management device, and can be used to execute the computer program stored in the memory 42 to control the DSL description file management device to implement corresponding functions and complete corresponding actions or tasks. It is worth noting that, according to the different implementation forms and scenarios of the DSL description file management device, the functions to be implemented, actions or tasks to be completed will be different; correspondingly, the computer programs stored in the memory 42 will also have Differently, the processor 31 executes different computer programs to control the DSL description file management device to implement different functions and complete different actions or tasks.

In some optional embodiments, as shown in FIG. 4 , the DSL description file management device may further include: a display 43 , a power supply component 44 , and a communication component 45 and other components. Fig. 4 only schematically shows some components, which does not mean that the DSL description file management device only includes the components shown in Fig. 4. For different application requirements, the DSL description file management device may also include other components. In the case of interactive requirements, as shown in FIG. 4 , the DSL description file management device may further include an audio component 46 . The components that can be included in the DSL description file management device may depend on the product form of the DSL description file management device, which is not limited here.

In this embodiment of the present application, when the processor executes the computer program in the memory, it is configured to: receive a DSL description file request sent by an application, where the DSL description file request includes version information of the application and a target front end to be rendered The identifier of the page; 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 is determined; wherein, each candidate DSL description file has a corresponding supported application version range; according to the version of the application information and the application version range supported by each candidate DSL description file, determine the target DSL description file corresponding to the version of the application from at least one candidate DSL description file; send the target DSL description file to the application for the application The target front-end page is rendered according to the description information included in the target DSL description file. Based on the feature that DSL description files have no platform dependency, the embodiments of the present application can implement unified management and cross-platform dynamic distribution of DSL description files of different platforms, and can realize cross-platform dynamic rendering requirements.

It should be noted that, with regard to the specific functions of the processor in the above electronic device, reference may be made to the above method embodiments, and details are not described herein again.

Correspondingly, the embodiments of the present application further provide a computer-readable storage medium storing a computer program, and when the computer program is executed, each step in the above method embodiment that can be executed by the DSL description file management device can be implemented.

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

The display in the above-described embodiments includes a screen, and the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touch, swipe, and gestures on the touch panel. The touch sensor may not only sense the boundaries of a touch or swipe action, but also detect the duration and pressure associated with the touch or swipe action.

The power supply components in the above embodiments provide power for various components of the equipment where the power supply components are located. A power supply assembly may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the equipment in which the power supply assembly is located.

The audio components of the above-described embodiments may be configured to output and/or input audio signals. For example, the audio component includes a microphone (MIC) that is configured to receive external audio signals when the device in which the audio component is located is in operating modes, such as call mode, recording mode, and speech recognition mode. The received audio signal may be further stored in memory or transmitted via the communication component. In some embodiments, the audio assembly further includes a speaker for outputting audio signals.

As will be appreciated by those skilled in the art, the embodiments of the present application may be provided as a method, a system, or a computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present application. It will be understood that each flow and/or block in the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to the processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing device to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing device produce Means for implementing the functions specified in a flow or flow of a flowchart and/or a block or blocks of a block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory result in an article of manufacture comprising instruction means, the instructions The apparatus implements the functions specified in the flow or flow of the flowcharts and/or the block or blocks of the block diagrams.

These computer program instructions can also be loaded on a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process such that The instructions provide steps for implementing the functions specified in the flow or blocks of the flowcharts and/or the block or blocks of the block diagrams.

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

Memory may include non-persistent memory in computer readable media, random access memory (RAM) and/or non-volatile memory in the form of, for example, read only memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media includes both persistent and non-permanent, removable and non-removable media, and storage of information may be implemented by any method or technology. Information may be computer readable instructions, data structures, modules of programs, 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 technology, Compact Disc Read Only Memory (CD-ROM), Digital Versatile Disc (DVD) or other optical storage, Magnetic tape cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media, such as modulated data signals and carrier waves.

It should also be noted that the terms "comprising", "comprising" or any other variation thereof are intended to encompass a non-exclusive inclusion such that a process, method, article or device comprising a series of elements includes not only those elements, but also Other elements not expressly listed, or which are inherent to such a process, method, article of manufacture, or apparatus are also included. Without further limitation, an element qualified by the phrase "comprising a..." does not preclude the presence of additional identical elements in the process, method, article of manufacture, or device that includes the element.

The above descriptions are merely examples of the present application, and are not intended to limit the present application. Various modifications and variations of this application are possible for those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this application shall be included within the scope of the claims of this application.

Claims (11)

1. A DSL description file management method is applied to a DSL description file management system, and is characterized in that the DSL description file management system comprises DSL description files corresponding to at least one front end page, and each DSL description file comprises description information of a UI component required by the corresponding front end page, and the method comprises the following steps:

receiving 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;

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 of the candidate DSL profiles has a corresponding range of supported application versions;

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 version range of the application program 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.

2. The method of claim 1, wherein the DSL profile management system comprises at least one component library corresponding to at least one front-end page, wherein the at least one component library has different versions, the version range of applications supported by the component libraries of different versions is different, at least one DSL profile corresponds to each version of the component library, and each component library comprises UI components required by its corresponding front-end page;

correspondingly, determining at least one candidate DSL profile corresponding to the target front-end page under different versions according to the identifier of the target front-end page includes:

determining 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 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 profile corresponding to the version of the application from the at least one candidate DSL profile according to the version information of the application and the range of application versions supported by each candidate DSL profile, comprises:

and selecting a target component library from the at least one candidate component library according to the version information of the application program and the version range of the application program respectively supported by the at least one candidate component library, and selecting the target DSL description file from at least one DSL description file corresponding to the target component library.

3. The method of claim 1 or 2, wherein prior to receiving the request sent by the application, the method further comprises:

determining an application program version range supported by each component library in at least one component library and a version of each component library aiming at least one component library corresponding to the same front-end page;

and generating at least one DSL description file corresponding to each component library according to the version of each component library and the supported application program version range.

4. The method of claim 3, wherein determining the range of application versions supported by each component library of the at least one component library and the version of each component library comprises:

aiming at each component library in the at least one component library, acquiring application program versions respectively supported by a plurality of UI components contained in the component library;

determining an application version range commonly supported by the plurality of UI components in each component library according to the application versions respectively supported by the plurality of UI components, and taking the application version range commonly supported by the plurality of UI components in each component library as the application version range supported by each component library;

under the condition that the application program version range supported by at least two component libraries is the same, setting the at least two component libraries to be the same version;

and in the case that the application program version range supported by at least two component libraries is different, setting the at least two component libraries to different versions.

5. The method of claim 4, wherein generating 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 comprises:

acquiring basic information and layout information of a plurality of UI components contained in each component library;

determining a cascade relation among the plurality of UI components according to the basic information and the layout information;

and generating at least one DSL description file corresponding to each component library according to the version of each component library and the cascade relation, and taking the application program version range supported by each component library as the application program version range supported by the at least one DSL description file corresponding to the component library.

6. The method of any of claims 4-5, wherein selecting a target DSL profile from the at least one DSL profile corresponding to the target component library comprises:

selecting a latest version of a DSL description file from the at least one DSL description file as the target DSL description file.

7. A DSL description file management device is applied to a DSL description file management system, the DSL description file management system comprises DSL description files corresponding to at least one front-end page, each DSL description file comprises description information of a UI component required by the corresponding front-end page, and the device comprises:

a receiving module, configured to receive a DSL description file request sent by an application program, where the DSL description file request includes version information of the application program and an identifier of a target front-end page to be rendered;

a first processing module, configured to determine, according to the identifier of the target front-end page, at least one candidate DSL profile corresponding to the target front-end page in different versions; wherein each of the candidate DSL profiles has a corresponding range of supported application versions;

a second processing module, configured to determine, according to version information of the application and an application version range supported by each candidate DSL profile, a target DSL profile corresponding to the version of the application from among the at least one candidate DSL profile;

and the sending module is used for 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.

8. A DSL profile management system, said system comprising: a DSL description file generation device and a DSL description file management device;

the DSL description file generating device is used for generating DSL description files corresponding to at least one front-end page under different versions, and each DSL description file comprises description information of a UI component required by the corresponding front-end page; determining the version range of the application program supported by each DSL description file according to the version information of the application program supported by the UI component contained in each DSL description file;

the DSL description file management device is used for determining at least one candidate DSL description file corresponding to a target front-end page under different versions according to the identifier of the target front-end page to be rendered; determining a target DSL description file supporting 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 version range of the application program supported by each DSL description file; and sending the target DSL description file to the application program for rendering the target front-end page by the application program.

9. A DSL profile management system, said system comprising: the device comprises component library generating equipment, DSL description file generating equipment and DSL description file management equipment;

the component library generating device is used for generating at least one component library corresponding to at least one front-end page, each component library comprises a plurality of UI components, and the UI components correspond to application program versions supported by the UI components; determining an application program version range supported by each component library and a version of each component library according to application program versions supported by a plurality of UI components included in each component library;

the DSL description file generating device is used for generating DSL description files corresponding to at least one front-end page under different versions, and each DSL description file comprises description information of a UI component required by the corresponding front-end page;

the DSL description file management device is used for determining at least one candidate component library corresponding to a target front-end page according to the identifier of the target front-end page to be rendered; establishing a corresponding relation between a component library version and DSLs of 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 version information of the application program; 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 for rendering the target front-end page by the application program.

10. A DSL profile management apparatus, comprising: a processor and a memory storing a computer program;

the processor to execute the computer program to:

receiving 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;

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 of the candidate DSL profiles has a corresponding range of supported application versions;

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 version range of the application program 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.

11. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, causes the processor to carry out the steps of the method according to any one of claims 1 to 6.

Images