Low-code platform development method and apparatus

Abstract

Embodiments of the present application provide a low-code platform development method and device, the method comprising: obtaining first component information generated in a first engine, the first component information including the identities of a plurality of first components and the component attributes of each first component; determining an executable file of a second engine according to the first component information; determining data source information, the data source information including the information of at least one data source associated with a first component; wherein the executable file and the data source information are used to render a visual page in the second engine of a smart device. The development efficiency of light service applications is improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a low-code platform development method and device. Background Technology

[0002] Lightweight service applications can run on smart devices without installation, providing users with convenient services. For example, a smart device could be a smart speaker with a screen, and a lightweight service application could be a package tracking service.

[0003] Among related technologies, the development efficiency of lightweight service applications is relatively low. Summary of the Invention

[0004] This application provides a low-code platform development method and apparatus to improve the development efficiency of lightweight service applications.

[0005] In a first aspect, embodiments of this application provide a low-code platform development method, including:

[0006] Obtain the first component information generated in the first engine, the first component information including the identifiers of multiple first components and the component attributes of each first component;

[0007] Based on the information of the first component, determine the executable file of the second engine;

[0008] The data source information is determined, which includes information about at least one data source associated with the first component; wherein the executable file and the data source information are used to render a visual page in the second engine of the smart device.

[0009] In one possible implementation, determining the executable file of the second engine based on the first component information includes:

[0010] The first component information is converted to obtain the second component information, which is in Abstract Syntax Tree (AST) format.

[0011] The executable file is determined based on the information from the second component.

[0012] In one possible implementation, determining the executable file based on the second component information includes:

[0013] Send the second component information to the cloud server;

[0014] Receive the executable file corresponding to the second component information sent by the cloud server.

[0015] In one possible implementation, sending the second component information to the cloud server includes:

[0016] Determine the Function as a Service (FaaS) interface corresponding to the cloud server;

[0017] The second component information is sent to the cloud server by calling the FaaS interface.

[0018] In one possible implementation, determining the executable file based on the second component information includes:

[0019] The second component information is parsed and processed to obtain the project code;

[0020] The executable file is obtained by compiling the project code using multiple threads.

[0021] In one possible implementation, determining the data source information includes:

[0022] Display component page, the component page including the plurality of first components;

[0023] For any one of the at least one first component, in response to a data source association operation on the first component, a data source list is displayed, the data source list including multiple data sources;

[0024] In response to a data source selection operation entered in the data source list, the first component and the selected data source are associated;

[0025] The data source information is generated based on the information of the data source associated with each of the at least one first component.

[0026] In one possible implementation, in response to a data source association operation on the first component, a list of data sources is displayed, including:

[0027] In response to the data source association operation of the first component, a first data type of the data displayed by the first component is determined;

[0028] Obtain the similarity between the first data type and the data types of each data source in the data source set;

[0029] Based on the similarity between the first data type and the data types of each data source in the data source set, the data source list is determined in the data source set and displayed, wherein the similarity between the first data type and the data types of each data source in the data source list is greater than or equal to a first preset threshold.

[0030] In one possible implementation, determining the first data type of the data displayed by the first component includes:

[0031] Determine the text component corresponding to the first component, wherein the text component includes the first text;

[0032] The first text is subjected to semantic recognition processing to determine the first data type.

[0033] In one possible implementation, associating the first component with the selected data source includes:

[0034] Determine the standard data source information corresponding to the first component, and the current data source information of the selected data source;

[0035] Determine the matching degree between the standard data source information and the current data source information;

[0036] Perform an integrity check on the current data source information and obtain the check result;

[0037] When the matching degree is greater than or equal to the second preset threshold and the verification result is a successful verification, the first component and the selected data source are associated.

[0038] In one possible implementation, the method further includes:

[0039] When the matching degree is less than the second preset threshold, or when the verification result is that the verification failed, a prompt message is generated and displayed, wherein the prompt message is used to indicate that the selected data source is abnormal.

[0040] In one possible implementation, obtaining the first component information includes:

[0041] The component page includes a component list area, a component display area, and an attribute editing area. The component list area includes multiple components, the component display area is used to display the selected component, and the attribute editing area is used to edit the attributes of the selected component.

[0042] In response to a selection operation input on the plurality of first components in the component list area, the plurality of first components are displayed in the component display area;

[0043] In response to an editing operation input to the first component in the attribute editing area, the component attributes of the first component are obtained.

[0044] Secondly, embodiments of this application provide a low-code platform application method, the method further comprising:

[0045] Acquire voice information and extract keywords from the voice information;

[0046] Determine user intent based on the keywords;

[0047] Based on the user's intent, determine the executable file and data source information;

[0048] The target page is obtained by rendering the page based on the executable file and the data source information, and then the target page is displayed.

[0049] Thirdly, embodiments of this application provide a low-code platform development apparatus, applicable to electronic devices. The low-code platform development apparatus includes: an acquisition module, a first determination module, and a second determination module, wherein...

[0050] The acquisition module is used to acquire first component information generated in the first engine, wherein the first component information includes the identifiers of multiple first components and the component attributes of each first component;

[0051] The first determining module is used to determine the executable file of the second engine based on the first component information;

[0052] The second determining module is used to determine data source information, which includes information about at least one data source associated with the first component; wherein the executable file and the data source information are used to render a visual page in the second engine of the smart device.

[0053] In one possible implementation, the first determining module is specifically used for:

[0054] The first component information is converted to obtain the second component information, which is in Abstract Syntax Tree (AST) format.

[0055] The executable file is determined based on the information from the second component.

[0056] In one possible implementation, the first determining module is specifically used for:

[0057] Send the second component information to the cloud server;

[0058] Receive the executable file corresponding to the second component information sent by the cloud server.

[0059] In one possible implementation, the first determining module is specifically used for:

[0060] Determine the Function as a Service (FaaS) interface corresponding to the cloud server;

[0061] The second component information is sent to the cloud server by calling the FaaS interface.

[0062] In one possible implementation, the first determining module is specifically used for:

[0063] The second component information is parsed and processed to obtain the project code;

[0064] The executable file is obtained by compiling the project code using multiple threads.

[0065] In one possible implementation, the second determining module is specifically used for:

[0066] Display component page, the component page including the plurality of first components;

[0067] For any one of the at least one first component, in response to a data source association operation on the first component, a data source list is displayed, the data source list including multiple data sources;

[0068] In response to a data source selection operation entered in the data source list, the first component and the selected data source are associated;

[0069] The data source information is generated based on the information of the data source associated with each of the at least one first component.

[0070] In one possible implementation, the second determining module is specifically used for:

[0071] In response to the data source association operation of the first component, a first data type of the data displayed by the first component is determined;

[0072] Obtain the similarity between the first data type and the data types of each data source in the data source set;

[0073] Based on the similarity between the first data type and the data types of each data source in the data source set, the data source list is determined in the data source set and displayed, wherein the similarity between the first data type and the data types of each data source in the data source list is greater than or equal to a first preset threshold.

[0074] In one possible implementation, the second determining module is specifically used for:

[0075] Determine the text component corresponding to the first component, wherein the text component includes the first text;

[0076] The first text is subjected to semantic recognition processing to determine the first data type.

[0077] In one possible implementation, the second determining module is specifically used for:

[0078] Determine the standard data source information corresponding to the first component, and the current data source information of the selected data source;

[0079] Determine the matching degree between the standard data source information and the current data source information;

[0080] Perform an integrity check on the current data source information and obtain the check result;

[0081] When the matching degree is greater than or equal to the second preset threshold and the verification result is a successful verification, the first component and the selected data source are associated.

[0082] In one possible implementation, the acquisition module is specifically used for:

[0083] The component page includes a component list area, a component display area, and an attribute editing area. The component list area includes multiple components, the component display area is used to display the selected component, and the attribute editing area is used to edit the attributes of the selected component.

[0084] In response to a selection operation input on the plurality of first components in the component list area, the plurality of first components are displayed in the component display area;

[0085] In response to an editing operation input to the first component in the attribute editing area, the component attributes of the first component are obtained.

[0086] In one possible implementation, the low-code platform development apparatus further includes: a generation module.

[0087] The generation module is used to generate and display a prompt message when the matching degree is less than the second preset threshold or the verification result is a verification failure. The prompt message is used to indicate that the selected data source is abnormal.

[0088] Fourthly, embodiments of this application provide a low-code platform application device applicable to smart devices. The low-code platform application device includes: an acquisition module, a first determination module, a second determination module, and a rendering module, wherein...

[0089] The acquisition module is used to acquire voice information and extract keywords from the voice information;

[0090] The first determining module is used to determine the user's intent based on the keywords;

[0091] The second determining module is used to determine the executable file and data source information based on the user's intent;

[0092] The rendering module is used to render the page according to the executable file and the data source information to obtain the target page and display the target page.

[0093] Fifthly, embodiments of this application provide an electronic device, including: a memory and a processor;

[0094] The memory stores computer-executed instructions;

[0095] The processor executes computer execution instructions stored in the memory, causing the processor to perform the low-code platform development method according to any one of the first aspects.

[0096] Sixthly, embodiments of this application provide an electronic device, including: a memory and a processor;

[0097] The memory stores computer-executed instructions;

[0098] The processor executes computer execution instructions stored in the memory, causing the processor to perform the low-code platform application method according to any one of the second aspects.

[0099] In a seventh aspect, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the low-code platform development method described in any of the first aspects.

[0100] Eighthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the low-code platform application method described in any of the second aspects.

[0101] Ninthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the low-code platform development method shown in any of the first aspects.

[0102] In a tenth aspect, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the low-code platform application method shown in any of the second aspects.

[0103] This application provides a low-code platform development method and apparatus. An electronic device can obtain first component information generated in a first engine, and can perform format conversion processing on the first component information to obtain second component information. Then, based on the second component information, it determines the executable file of the second engine. The electronic device can determine data source information, which may include information about at least one data source associated with the first component. The executable file and data source information can be used to render a visual page in the second engine of the smart device. Because the component information generated in the first engine can be converted into an executable file that can be used in the second engine during the development of a lightweight service application, the lightweight service application can run in the second engine, quickly realizing the conversion from an electronic device to a smart device and improving the development efficiency of lightweight service applications. Attached Figure Description

[0104] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0105] Figure 1 A schematic diagram illustrating an application scenario provided for an exemplary embodiment of this application;

[0106] Figure 2 A flowchart illustrating a low-code platform development method provided for an exemplary embodiment of this application;

[0107] Figure 3 A schematic diagram of a component page provided for an exemplary embodiment of this application;

[0108] Figure 4 A schematic diagram illustrating the data source association operation provided for an exemplary embodiment of this application;

[0109] Figure 5 A flowchart illustrating another low-code platform development method provided for an exemplary embodiment of this application;

[0110] Figure 6A Illustration of prompting information provided for exemplary embodiments of this application Figure 1 ;

[0111] Figure 6B Illustration of prompting information provided for exemplary embodiments of this application Figure 2 ;

[0112] Figure 7 A flowchart illustrating a low-code platform application method provided for an exemplary embodiment of this application;

[0113] Figure 8A schematic diagram of the system architecture provided for an exemplary embodiment of this application;

[0114] Figure 9 A schematic diagram illustrating the process of a low-code platform development method provided as an exemplary embodiment of this application;

[0115] Figure 10 A schematic diagram of a low-code platform development apparatus provided as an exemplary embodiment of this application;

[0116] Figure 11 A schematic diagram of another low-code platform development apparatus provided as an exemplary embodiment of this application;

[0117] Figure 12 A schematic diagram of the structure of a low-code platform application device provided for an exemplary embodiment of this application;

[0118] Figure 13 This is a schematic diagram of the structure of an electronic device provided as an exemplary embodiment of this application. Detailed Implementation

[0119] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0120] Figure 1 This is a schematic diagram illustrating an application scenario provided for an exemplary embodiment of this application. For example... Figure 1 As shown, it includes an electronic device 101, a cloud server 102, and a smart device 103. For example, the electronic device 101 can be a computer, and the smart device 103 can be a smart speaker with a screen.

[0121] Within Electronic Device 101, a visual platform for building lightweight service applications can be run. Staff can use this platform to build lightweight service applications. For example... Figure 1 As shown, a lightweight service application can be a weather service card for today, which may include the following information: date 2022-07-05, location city is Hangzhou, weather is sunny, temperature is 25℃, and tips such as "It is recommended to wear short sleeves, the ultraviolet rays are weak, and it is suitable for exercise".

[0122] When building a lightweight service application in electronic device 101, electronic device 101 can generate component information corresponding to the lightweight service application and send the component information to cloud server 102. Cloud server 102 can store the component information in real time and process the component information to obtain the executable file corresponding to the lightweight service application.

[0123] When a user uses smart device 103, smart device 103 can obtain the user's voice information and determine the corresponding lightweight service application based on the user's voice information. Smart device 103 can download the executable file corresponding to the lightweight service application from cloud server 102, and determine the target page corresponding to the lightweight service application based on the executable file to display the target page, such as... Figure 1 As shown.

[0124] Among related technologies, the development efficiency of lightweight service applications is relatively low.

[0125] In this embodiment, lightweight service applications can be quickly built in a visual building platform for lightweight service applications on electronic devices, and these applications can be applied to smart devices. Because the component information generated in the first engine can be converted into an executable file that can be used in the second engine during the lightweight service application building process, the lightweight service application can run in the second engine, quickly realizing the conversion from electronic devices to smart devices and improving the development efficiency of lightweight service applications.

[0126] The technical solutions shown in this application will now be described in detail through specific embodiments. It should be noted that the following embodiments may exist independently or in combination with each other; for identical or similar content, the description will not be repeated in different embodiments.

[0127] The technical solution of this application may include two processes: a low-code platform development process and a low-code platform usage process. Below, in conjunction with... Figure 2 First, we will explain the process of developing a low-code platform.

[0128] Figure 2 This is a flowchart illustrating a low-code platform development method provided for an exemplary embodiment of this application. Please refer to [link / reference]. Figure 2 The method may include:

[0129] S201. Obtain the information of the first component generated in the first engine.

[0130] The execution subject of this application embodiment can be an electronic device or a low-code platform development device installed in an electronic device. The low-code platform development device can be implemented through software or through a combination of software and hardware. The low-code platform development device can be a processor in an electronic device. For ease of understanding, the following description will use an electronic device as the execution subject.

[0131] The primary engine can be an engine set up in the browser of an electronic device. For example, the primary engine can be a JavaScript engine used to execute JavaScript code.

[0132] The first component information may include identifiers for multiple first components, as well as component attributes for each first component. The programming language used for the first component information can be JavaScript, and the corresponding component description format can be Domain Specific Language (DSL) format.

[0133] In an optional embodiment, the first component information can be obtained by: displaying a component page, the component page including a component list area, a component display area, and an attribute editing area, the component list area including multiple components, the component display area for displaying the selected component, and the attribute editing area for editing the attributes of the selected component; in response to a selection operation input on multiple first components in the component list area, displaying multiple first components in the component display area; and in response to an editing operation input on a first component in the attribute editing area, obtaining the component attributes of the first component.

[0134] Below, in conjunction with Figure 3 The component page will be described.

[0135] Figure 3 A schematic diagram of a component page provided for an exemplary embodiment of this application. Please refer to... Figure 3 Interface 301 is a component display page, which may include a component list area, a component display area, and an attribute editing area.

[0136] like Figure 3 As shown, the component list area can include multiple components such as text components, number components, shape components, image components, and video components. The shape components can include multiple components such as rectangle components, circle components, and line components.

[0137] In response to the selection of multiple first components in the component list area, multiple first components can be displayed in the component display area. For example... Figure 3As shown, the component display area can display selected rounded rectangle components, date components, positioning components, line components, multiple text components, number components, etc. Any first component can be selected to perform operations. For example, the rounded rectangle component can be used to draw the outline of a service card, the date component can display today's date as "2022-07-05", the positioning component can specify the location city as "Hangzhou", text component 1 can be filled with "Today's temperature", text component 2 can be filled with "Weather:", text component 3 can display "Sunny", text component 4 can be filled with "Temperature:", the number component can display "25", text component 5 can be filled with "℃", text component 6 can be filled with "Tips:", and text component 7 can display "It is recommended to wear short sleeves; the ultraviolet radiation is weak, suitable for exercise". The content in text components 1, 2, 4, 5, and 6 is fixed, while the content in text components 3, number components, and 7 is dynamic.

[0138] When operating on any first component, you can enter its properties in the property editing area. For example, selecting a line in the component display area will display the line's size, position, general settings, line style, etc., in the property editing area. Multiple component properties of the line component can be edited in the property editing area. For example, you can edit the line's opacity to 60%, visibility (including fixed value, display), line width to 2.0 points, and type to solid line, among other component properties.

[0139] For any given first component, after entering an editing operation on the first component in the attribute editing area, the electronic device can respond to the editing operation entered on the first component and obtain the component attributes of the first component.

[0140] S202. Based on the information of the first component, determine the executable file of the second engine.

[0141] The second engine can be an engine set up within the smart device. For example, the second engine could be an AssemblyScript engine used to execute AssemblyScript code.

[0142] In one optional embodiment, the executable file of the second engine can be determined by: performing a format conversion process on the first component information to obtain the second component information; and determining the executable file based on the second component information.

[0143] Since the first component information is in DSL format and is generated when multiple first components are edited, it records a large amount of editing-state related information, such as the component identifier and component attributes of each first component, making it quite complex. Therefore, the first component information can be format converted, that is, the editing-state related information can be simplified or deleted to obtain the second component information. The second component information can include information related to multiple first components in the runtime state. The programming language used for the second component information can be AssemblyScript, and the corresponding format can be Abstract Syntax Tree (AST) format.

[0144] For example, if the description of color 1 in the first component information is: "Red chromaticity value is 255, green chromaticity value is 48, blue chromaticity value is 48", then the first component information can be simplified to obtain the second component information. The description of color 1 in the second component information can be: "Red, Green, Blue (255, 48, 48)".

[0145] It should be noted that the programming structure of DSL format and AST format is basically the same, but AST format has been simplified and deleted compared to DSL format. This can reduce redundant fields and improve packaging speed.

[0146] After receiving the second component information, the electronic device can send the second component information to the cloud server and obtain the corresponding executable file from the cloud server; alternatively, it can process the second component information to obtain the corresponding executable file. The executable file can include multiple runtime related information of the first component, and the corresponding format can be Ahead-Of-Time (AOT) format.

[0147] Optionally, if the electronic device processes the second component information to obtain an executable file corresponding to the second component information, the electronic device may also send the executable file corresponding to the second component information to the cloud server.

[0148] S203. Determine the data source information.

[0149] The data source information may include information about at least one data source associated with the first component.

[0150] In an optional embodiment, the data source information can be determined by: displaying a component page, which includes a plurality of first components; for any one of the at least one first component, in response to a data source association operation on the first component, displaying a data source list, which includes a plurality of data sources; in response to a data source selection operation entered in the data source list, associating the first component with the selected data source; and generating data source information based on the information of the data sources associated with each of the at least one first component.

[0151] Below, in conjunction with Figure 4 This section explains the data source association operations.

[0152] Figure 4 This is a schematic diagram illustrating the data source association operation provided for an exemplary embodiment of this application. Please refer to [link to relevant documentation]. Figure 4 This includes interfaces 401, 402, and 403.

[0153] Selecting the date component in the component display area of ​​interface 401 will display its size, position, and general settings in the property editing area. Clicking the "Associate Data" control in the property editing area will initiate data source association. Clicking the "Associate Data" control will display the "Associate Data Source" editing control in the property editing area. Clicking the "Associate Data Source" editing control will also display a list of data sources, as shown in interface 402.

[0154] Interface 402 can include a list of data sources and a data source configuration area. The data source list can include multiple data sources. For example, the data source list can include multiple data sources such as data source getdate, data source 2, and data source 3. These multiple data sources can be pre-saved or newly added. Editing and deleting operations can be performed on any data source.

[0155] Selecting the data source `getdate` in the data source list will display its configuration in response to this selection. The data source configuration allows you to choose between an official service as the data source type, an existing data source as `getdate`, and the data source's return results, which may include multiple fields and their values. For example, the return results might include: the field "lunarDate" with the value "2022-06-07", the field "Time" with the value "2022-07-05 14:55", the field "WeekNum" with the value "Tuesday", and the field "SolarDate" with the value "2022-07-05". In the data fields section, you can select multiple fields based on the return results to display a field list. You can then select a target field from this list. For example, you can select the `solardate` field.

[0156] After selecting the solardate field, you can associate the date component with the data source getdate. Once the association is successful, the information of the successfully associated data source, namely "Official Service - getdate - solarDate", will be displayed in the "Associated Data Source" edit control. The date component can then determine today's date as 2022-07-05 based on the data source getdate and display it as "2022-07-05" as shown in page 403.

[0157] Optionally, after associating with a data source, the electronic device can generate data source information based on the information of the data source associated with each of the at least one first component. The data source information may include the identifier of the first component and information about the associated data source. This data source information may be in DSL format.

[0158] For example, if the data source associated with the date component is "official service-getdate-solarDate", the electronic device can generate data source information based on this information. The data source information can include the date component's identifier, the data source's identifier, and the data source's attributes.

[0159] Optionally, after determining the data source information, the electronic device can send the data source information to the cloud server so that the cloud server can store the data source information.

[0160] It should be noted that the executable file determined in step S202 and the data source information determined in step S203 can be used to render a visual page in the second engine of the smart device.

[0161] In this embodiment, the electronic device can obtain first component information generated in the first engine, and can perform format conversion processing on the first component information to obtain second component information. Then, based on the second component information, it can determine the executable file of the second engine. The electronic device can determine data source information, which may include information about at least one data source associated with the first component. The executable file and data source information can be used to render a visual page in the second engine of the smart device. Because the component information generated in the first engine can be converted into an executable file that can be used in the second engine during the development of a lightweight service application, the lightweight service application can run in the second engine, quickly realizing the conversion from an electronic device to a smart device and improving the development efficiency of lightweight service applications.

[0162] Below, in Figure 2 Based on the illustrated embodiments, combined with Figure 5 The above-mentioned low-code platform development methods will be explained in further detail.

[0163] Figure 5 A flowchart illustrating another low-code platform development method provided for an exemplary embodiment of this application. Please refer to... Figure 5 The method may include:

[0164] S501, Obtain the information of the first component generated in the first engine.

[0165] The first component information may include the identifiers of multiple first components, as well as the component attributes of each first component.

[0166] It should be noted that the execution process of step S501 can be referred to the execution process of step S201, and will not be repeated here.

[0167] S502. Perform format conversion processing on the first component information to obtain the second component information.

[0168] Since the programming language used for the first component information can be JavaScript, and the corresponding format is DSL, the electronic device can perform format conversion processing on the first component information. That is, it can simplify or delete relevant information in the editing state to obtain the second component information. The programming language used for the second component information can be AssemblyScript, and the corresponding format can be AST.

[0169] Compared to the first component information, the second component information has fewer redundant fields, which helps to improve packaging speed.

[0170] S503. Determine the executable file based on the information from the second component.

[0171] Optionally, determining the executable file based on the second component information can include the following two methods:

[0172] Method 1: Obtain the executable file corresponding to the second component information through a cloud server.

[0173] In this method, electronic devices can send second component information to the cloud server and receive the executable file corresponding to the second component information sent by the cloud server.

[0174] In one optional embodiment, the second component information can be sent to the cloud server by: determining the Function as a Service (FaaS) interface corresponding to the cloud server; and sending the second component information to the cloud server by calling the FaaS interface.

[0175] The cloud server can be used to generate the corresponding executable file based on the information from the second component.

[0176] FaaS interfaces can support cloud services for the development and management of lightweight application services.

[0177] After obtaining the second component information, the electronic device can determine the corresponding FaaS interface of the cloud server and send the second component information to the cloud server by calling the FaaS interface. The cloud server can parse and process the second component information, converting it into corresponding project code, and use multi-threading to compile the project code to generate an executable file corresponding to the second component information. After obtaining the executable file, the cloud server can send the executable file to the electronic device, allowing the electronic device to receive the executable file corresponding to the second component information.

[0178] Optionally, after the cloud server generates the executable file corresponding to the second component information, it can store the executable file.

[0179] Method 2: Generate the executable file corresponding to the second component information locally.

[0180] In this method, the electronic device can parse and process the information of the second component to obtain the engineering code, and then compile the engineering code through multi-threading to obtain an executable file.

[0181] Optionally, after the electronic device generates the executable file corresponding to the second component information, it can send the executable file to the cloud server. After receiving the executable file, the cloud server can store it.

[0182] S504, associate the first component with the selected data source.

[0183] Optionally, a data source association operation can be performed on the first component on the component page. In response to the data source association operation on the first component, the electronic device can display a list of data sources. In the data source list, a data source that needs to be associated can be selected, so that the electronic device associates the first component with the selected data source.

[0184] In an optional embodiment, in response to a data source association operation on the first component, a list of data sources can be displayed as follows: in response to a data source association operation on the first component, a first data type of the data displayed by the first component is determined; the similarity between the first data type and the data types of each data source in the data source set is obtained; based on the similarity between the first data type and the data types of each data source in the data source set, a list of data sources is determined in the data source set, and the list of data sources is displayed.

[0185] Optionally, the first data type of the data displayed by the first component can be determined by: determining the text component corresponding to the first component, wherein the text component includes the first text; and performing semantic recognition processing on the first text to determine the first data type.

[0186] For example, if the interface associated with the data source is like Figure 4 As shown in interface 402, if the first component is a date component, the electronic device can determine the text component corresponding to the date component. The text component may include the first text "date". The electronic device can perform semantic recognition processing on the first text, that is, it can perform semantic recognition processing on "date" to determine that the first data type of the data displayed in the first component is date.

[0187] Optionally, after the electronic device determines the first data type of the data displayed by the first component, it can determine the similarity between the first data type and the data types of each data source in the data source set.

[0188] For example, if the first component is a date component, and the corresponding first data type is date, and the data source set includes 20 data sources, namely data source 1, data source 2, data source 3, ..., data source 20, where data source 1 is a number, data source 2 is a date, data source 3 is a date, ..., and data source 20 is text, then the electronic device can determine the similarity between the first data type and the data types of these 20 data sources. Assume the electronic device can determine that the first data type "date" has an 80% similarity to the data type of data source 1, a 90% similarity to the data type of data source 2, a 95% similarity to the data type of data source 3, ..., and a 10% similarity to the data type of data source 20.

[0189] After the electronic device determines the similarity between the first data type and the data types of each data source in the data source set, it can determine a list of data sources in the data source set based on these multiple similarities and then display the list of data sources. The similarity between the first data type and the data types of each data source in the data source list is greater than or equal to a first preset threshold.

[0190] For example, if the first component is a date component, and the corresponding first data type is date, and the data source set includes 20 data sources, namely data source 1, data source 2, data source 3, ..., data source 20, and the electronic device can determine the similarity between the first data type and the data types of these 20 data sources. Assume the electronic device can determine that the first data type "date" has a similarity of 80% with the data type of data source 1, 90% with the data type of data source 2, 95% with the data type of data source 3, ..., and a similarity of 10% with the data type of data source 20. If the first preset threshold is 80%, then since the first data type "date" has a similarity greater than the first preset threshold with the data types of data source 1, data source 2, and data source 3 respectively, the electronic device can determine a list of data sources in the data source set. This list can include data source 1, data source 2, and data source 3. The electronic device can then display a list of data sources including data source 1, data source 2, and data source 3.

[0191] In one optional embodiment, the first component and the selected data source can be associated as follows: determine the standard data source information corresponding to the first component and the current data source information of the selected data source; determine the matching degree between the standard data source information and the current data source information; perform an integrity check on the current data source information to obtain the check result. Based on the matching degree and the check result, the first component and the selected data source are associated.

[0192] The electronic device can determine the standard data source information based on the first component. The standard data source information may include the format, type, and content of the standard data source. For example, if the first component is a date component, the electronic device can determine that the standard data source information includes fields such as SolarDate based on the date component.

[0193] The current data source information can include the format, type, and content of the selected data source.

[0194] After the electronic device determines the standard data source based on the information of the first component and determines the current data source information of the selected data source, it can match the standard data source information and the current data source information to determine the degree of matching.

[0195] For example, if the first component is a date component, the electronic device can determine, based on the date component, that the standard data source information includes fields such as lunarDate, Time, WeekNum, and SolarDate, as well as the corresponding values ​​of each field; if the current data source information includes fields such as lunarDate, Time, WeekNum, and SolarDate, as well as the corresponding values ​​of each field, the electronic device can determine that the matching degree between the standard data source information and the current data source information is 90%; if the current data source information includes fields such as WeekNum, as well as the corresponding values ​​of each field, the electronic device can determine that the matching degree between the standard data source information and the current data source information is 25%.

[0196] Optionally, the electronic device can perform integrity verification on the current data source information and obtain the verification result.

[0197] For example, if the current data source is `getdate`, the electronic device can perform integrity checks on the content and structure of that data source to obtain a check result. If the content or structure of the data source is incomplete, the check result is "check failed"; if the content and structure of the data source are complete, the check result is "check passed".

[0198] Optionally, associating the first component with the selected data source can include the following two scenarios:

[0199] Case 1: The matching degree is greater than or equal to the second preset threshold, and the verification result is "verification passed".

[0200] In this case, it indicates that the selected data source is correct, and the electronic device can associate the first component with the selected data source.

[0201] For example, if the first component is a date component and the selected data source is data source getdate, if the electronic device determines that the standard data source information includes fields such as lunarDate, Time, WeekNum, and SolarDate, as well as the corresponding values ​​of each field; and the current data source information includes fields such as lunarDate, Time, WeekNum, and SolarDate, as well as the corresponding values ​​of each field, and the second preset threshold is 80%, assuming the electronic device determines that the matching degree between the standard data source information and the current data source information is 90%, then the matching degree is greater than the second preset threshold; and if the electronic device determines that the integrity verification result of the current data source information is verified as passed, then the electronic device can associate the date component with the data source getdate.

[0202] Case 2: The matching degree is less than the second preset threshold, or the verification result is that the verification failed.

[0203] In this situation, indicating an anomaly in the selected data source, the electronic device can generate and display a notification message. This message serves to indicate the anomaly in the selected data source.

[0204] For example, if the first component is a date component and the selected data source is data source getdate, if the electronic device determines that the standard data source information includes fields such as lunarDate, Time, WeekNum, and SolarDate, as well as the corresponding values ​​of each field; and the current data source information includes fields such as WeekNum, as well as the corresponding values ​​of each field, and the second preset threshold is 80%, assuming the electronic device determines that the matching degree between the standard data source information and the current data source information is 25%, then the matching degree is less than the second preset threshold; or if the electronic device determines that the integrity verification result of the current data source information is that the verification failed, then the electronic device can determine that the selected data source is abnormal.

[0205] Optionally, data source anomalies can include the following two situations:

[0206] Case 21: No data source was associated.

[0207] In this case, the message "No data source associated" may be displayed.

[0208] Figure 6A Illustration of prompting information provided for exemplary embodiments of this application Figure 1 Please see. Figure 6A If the first component is not associated with the selected data source, the message "Not associated with data source" can be displayed in response to the selection of the first component.

[0209] Case 22: Data source error.

[0210] In this case, the message "Data source error" may be displayed.

[0211] Figure 6B Illustration of prompting information provided for exemplary embodiments of this application Figure 2 Please see. Figure 6B If the first component is a date component, and the associated data source is "official service-getdate-weeknum", which includes fields such as weeknum and their corresponding values, but does not include the solardate field and its corresponding value, then the associated data source is incorrect. This will cause the date displayed in the date component to be the abnormal data 1900-00-00, and the prompt message "data source error" will be displayed.

[0212] S505. Determine the data source information.

[0213] The data source information may include information about at least one data source associated with the first component.

[0214] It should be noted that the execution process of step S505 can be referred to the execution process of step S203, and will not be repeated here.

[0215] In this embodiment, the electronic device can obtain first component information generated in the first engine, and can perform format conversion processing on the first component information to obtain second component information. Then, based on the second component information, it can determine the executable file of the second engine. When associating the first component with a selected data source, the electronic device can determine the first data type of the data displayed by the first component, and determine a list of data sources in the data source set based on the similarity between the first data type and the data types of each data source in the data source set, and display the data source list. The electronic device can also compare and verify the current data source information of the selected data source to check the accuracy of the selected data source. After successful association, the electronic device can determine the data source information. The executable file and data source information can be used to render a visual page in the second engine of the smart device. Because the component information generated in the first engine can be converted into an executable file that can be used in the second engine during the construction of a lightweight service application, the lightweight service application can run in the second engine, quickly realizing the conversion from electronic device to smart device and improving the development efficiency of lightweight service applications.

[0216] The above Figure 2 and Figure 5 The embodiments shown are schematic diagrams of low-code platform development methods. Below, in conjunction with... Figure 7 This section explains the process of applying low-code platforms.

[0217] Figure 7 A flowchart illustrating a low-code platform application method provided for an exemplary embodiment of this application. Please refer to [link / reference]. Figure 7 The method may include:

[0218] S701. Obtain voice information and extract keywords from the voice information.

[0219] For example, if a user inputs the voice message "Check today's weather in Hangzhou" into a smart device, the smart device can obtain the voice message and extract the keywords "Hangzhou", "today", and "weather" from it.

[0220] S702. Determine user intent based on keywords.

[0221] For example, if the keywords are "Hangzhou", "today" and "weather", the smart device can determine that the user wants to check the weather in Hangzhou today based on the keywords.

[0222] S703. Determine the executable file and data source information based on the user's intent.

[0223] Optionally, the smart device can determine the corresponding lightweight service application based on the user's intent, and then download the corresponding executable file and data source information from the cloud server based on the lightweight service application.

[0224] For example, if a smart device determines that a user wants to check today's weather in Hangzhou, the smart device can identify the corresponding lightweight service application as "Today's Temperature Card." The smart device can then download the executable file and data source information corresponding to "Today's Temperature Card" from the cloud server. The executable file can include runtime information about multiple components within "Today's Temperature Card," and the data source information can include details about the data sources associated with the various components within "Today's Temperature Card."

[0225] S704. Render the page based on the executable file and data source information to obtain the target page and display it.

[0226] For example, if the executable file and data source information are the same as those for today's temperature card, the smart device can render the page based on the executable file and data source information to obtain and display the target page. The target page can display: today's date 2022-07-05, the location city is Hangzhou, the weather is sunny, the temperature is 25℃, and tips, etc.

[0227] In this embodiment, the smart device can acquire voice information and extract keywords from it, thereby determining the user's intent based on the keywords. The smart device can then determine the corresponding lightweight service application based on the user's intent, and consequently, the corresponding executable file and data source information. The smart device can then render the page based on the executable file and data source information to obtain and display the target page. Because the component information generated in the first engine can be converted into an executable file that can be used in the second engine during the lightweight service application development process, the lightweight service application can run in the second engine, quickly realizing the conversion from electronic device to smart device and improving the development efficiency of lightweight service applications.

[0228] Below, based on any of the above embodiments, combined with Figure 8 The system architecture corresponding to the above methods will be explained.

[0229] Figure 8 A schematic diagram of the system architecture provided for an exemplary embodiment of this application. Please refer to... Figure 8 This includes electronic devices, cloud servers, and smart devices.

[0230] The electronic device may include a first engine, within which a lightweight service application building platform can run. This platform can display component pages, which may include a component list area, a component display area, and a property editing area.

[0231] The component list area can include multiple components. Multiple first components can be selected in the component list area, and the component display area can display these multiple first components. The component properties of these multiple first components can be edited in the property editing area.

[0232] In response to an operation inputting the multiple first components, the electronic device can generate first component information, which may include identifiers of the multiple first components and component attributes of each first component. The programming language used for the first component information may be JavaScript, and the corresponding format may be DSL format. The electronic device may save the first component information in a background service.

[0233] For any given first component, a selected data source can be associated with it. After successful association, the electronic device can save the selected data source in the background service, and generate data source information based on the information of the data sources associated with each of the first components in at least one first component, and save the data source information in the background service.

[0234] Optionally, the electronic device can send data source information to the cloud server.

[0235] The electronic device can perform format conversion processing on the first component information in DSL format to obtain the second component information in AST format. The electronic device can then send the second component information to a cloud server.

[0236] After obtaining the second component information, the cloud server can parse and process this information to obtain the project code, which can then be compiled to produce an executable file. The executable file can be in AOT format.

[0237] Optionally, the cloud server can store the executable file and data source information.

[0238] When a user uses a smart device, the device can determine the corresponding lightweight service application based on the user's voice information. The smart device can then download the corresponding executable file and data source information for that lightweight service application from a cloud server. Finally, the smart device can run the lightweight service application in a second engine based on the executable file and data source information, providing services to the user.

[0239] In this embodiment, the electronic device can obtain first component information generated in the first engine and perform format conversion processing on the first component information to obtain second component information. The electronic device can send the second component information to the cloud server so that the cloud server can determine the executable file based on the second component information. The electronic device can determine data source information and send the data source information to the cloud server. The data source information may include information about at least one data source associated with the first component. The smart device can determine the executable file and data source information corresponding to the lightweight service application and render a visual page in the second engine based on the executable file and data source information. Because the component information generated in the first engine can be converted into an executable file that can be used in the second engine during the construction of the lightweight service application, the lightweight service application can run in the second engine, quickly realizing the conversion from electronic device to smart device and improving the development efficiency of lightweight service applications.

[0240] Below, based on any of the above embodiments, the low-code platform development method will be fully described.

[0241] Figure 9 For a process illustration of the low-code platform development method provided as an exemplary embodiment of this application, please refer to [link / reference]. Figure 9 The method may include:

[0242] S901, The electronic device acquires the first component information generated in the first engine.

[0243] It should be noted that the specific execution process of step S901 can be found in step S201, and will not be repeated here.

[0244] S902, The electronic device performs format conversion processing on the information of the first component to obtain the information of the second component.

[0245] Since the programming language used for the first component information can be JavaScript, and the corresponding format is DSL, the electronic device can perform format conversion processing on the first component information. That is, it can simplify or delete relevant information in the editing state to obtain the second component information. The programming language used for the second component information can be AssemblyScript, and the corresponding format can be AST.

[0246] Compared to the first component information, the second component information has fewer redundant fields, which helps to improve packaging speed.

[0247] S903, Electronic equipment determines data source information.

[0248] It should be noted that the specific execution process of step S903 can be found in step S203, and will not be repeated here.

[0249] S904. The electronic device sends the second component information and data source information to the cloud server.

[0250] Optionally, after obtaining the second component information, the electronic device can determine the corresponding FaaS interface of the cloud server and call the FaaS interface to send the second component information to the cloud server.

[0251] Optionally, the electronic device can send data source information to the cloud server so that the cloud server can store the data source information.

[0252] S905, the cloud server determines the executable file based on the information from the second component.

[0253] Optionally, the cloud server can parse and process the second component information, convert the second component information into corresponding project code, and enable multi-threading to compile the project code to generate an executable file corresponding to the second component information.

[0254] S906: Smart devices acquire voice information to determine user intent.

[0255] Optionally, users can input voice information into the smart device so that the smart device can receive the voice information.

[0256] Optionally, smart devices can extract keywords from voice information and determine user intent based on those keywords.

[0257] S907: Smart devices determine lightweight service applications based on user intent.

[0258] For example, if a smart device determines that a user wants to check today's weather in Hangzhou, the smart device can determine that the corresponding lightweight service application is today's temperature card.

[0259] S908, The smart device sends the identifier of the light service application to the cloud server.

[0260] For example, if a smart device identifies the lightweight service application as "Today's Temperature Card", the smart device can send the identifier 1 of "Today's Temperature Card" to the cloud server.

[0261] S909 and the cloud server send the executable file and data source information corresponding to the light service application to the smart device based on the identification of the light service application.

[0262] Optionally, the cloud server may store the identifier, executable file, and data source information of the lightweight application.

[0263] For example, if the cloud server receives identifier 1 of today's temperature card, the cloud server can determine the executable file and data source information corresponding to today's temperature card based on identifier 1, and send the executable file and data source information corresponding to today's temperature card to the smart device.

[0264] S910: The smart device renders the page based on the executable file and data source information to obtain the target page and displays the target page.

[0265] Optionally, after receiving the executable file and data source information sent by the cloud server, the smart device can run a lightweight service application based on the executable file and data source information, that is, perform page rendering, obtain the target page, and display the target page.

[0266] In this embodiment, the electronic device can obtain first component information generated in the first engine and perform format conversion processing on the first component information to obtain second component information. The electronic device can send the second component information to the cloud server so that the cloud server can determine the executable file based on the second component information. The electronic device can determine data source information and send the data source information to the cloud server. The data source information may include information about at least one data source associated with the first component. The smart device can determine the executable file and data source information corresponding to the lightweight service application and render a visual page in the second engine based on the executable file and data source information. Because the component information generated in the first engine can be converted into an executable file that can be used in the second engine during the construction of the lightweight service application, the lightweight service application can run in the second engine, quickly realizing the conversion from electronic device to smart device and improving the development efficiency of lightweight service applications.

[0267] Figure 10 A schematic diagram of a low-code platform development apparatus provided as an exemplary embodiment of this application can be found in the following image: Figure 10 It includes: an acquisition module 11, a first determination module 12, and a second determination module 13, wherein,

[0268] The acquisition module 11 is used to acquire first component information generated in the first engine, wherein the first component information includes the identifiers of multiple first components and the component attributes of each first component;

[0269] The first determining module 12 is used to determine the executable file of the second engine based on the first component information;

[0270] The second determining module 13 is used to determine data source information, which includes information about at least one data source associated with the first component; wherein the executable file and the data source information are used to render a visual page in the second engine of the smart device.

[0271] The low-code platform development apparatus provided in this application embodiment can execute the technical solutions shown in the above method embodiments. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0272] In one possible implementation, the first determining module 12 is specifically used for:

[0273] The first component information is converted to obtain the second component information, which is in Abstract Syntax Tree (AST) format.

[0274] The executable file is determined based on the information from the second component.

[0275] In one possible implementation, the first determining module 12 is specifically used for:

[0276] Send the second component information to the cloud server;

[0277] Receive the executable file corresponding to the second component information sent by the cloud server.

[0278] In one possible implementation, the first determining module 12 is specifically used for:

[0279] Determine the Function as a Service (FaaS) interface corresponding to the cloud server;

[0280] The second component information is sent to the cloud server by calling the FaaS interface.

[0281] In one possible implementation, the first determining module 12 is specifically used for:

[0282] The second component information is parsed and processed to obtain the project code;

[0283] The executable file is obtained by compiling the project code using multiple threads.

[0284] In one possible implementation, the second determining module 13 is specifically used for:

[0285] Display component page, the component page including the plurality of first components;

[0286] For any one of the at least one first component, in response to a data source association operation on the first component, a data source list is displayed, the data source list including multiple data sources;

[0287] In response to a data source selection operation entered in the data source list, the first component and the selected data source are associated;

[0288] The data source information is generated based on the information of the data source associated with each of the at least one first component.

[0289] In one possible implementation, the second determining module 13 is specifically used for:

[0290] In response to the data source association operation of the first component, a first data type of the data displayed by the first component is determined;

[0291] Obtain the similarity between the first data type and the data types of each data source in the data source set;

[0292] Based on the similarity between the first data type and the data types of each data source in the data source set, the data source list is determined in the data source set and displayed, wherein the similarity between the first data type and the data types of each data source in the data source list is greater than or equal to a first preset threshold.

[0293] In one possible implementation, the second determining module 13 is specifically used for:

[0294] Determine the text component corresponding to the first component, wherein the text component includes the first text;

[0295] The first text is subjected to semantic recognition processing to determine the first data type.

[0296] In one possible implementation, the second determining module 13 is specifically used for:

[0297] Determine the standard data source information corresponding to the first component, and the current data source information of the selected data source;

[0298] Determine the matching degree between the standard data source information and the current data source information;

[0299] Perform an integrity check on the current data source information and obtain the check result;

[0300] When the matching degree is greater than or equal to the second preset threshold and the verification result is a successful verification, the first component and the selected data source are associated.

[0301] In one possible implementation, the acquisition module 11 is specifically used for:

[0302] The component page includes a component list area, a component display area, and an attribute editing area. The component list area includes multiple components, the component display area is used to display the selected component, and the attribute editing area is used to edit the attributes of the selected component.

[0303] In response to a selection operation input on the plurality of first components in the component list area, the plurality of first components are displayed in the component display area;

[0304] In response to an editing operation input to the first component in the attribute editing area, the component attributes of the first component are obtained.

[0305] The low-code platform development apparatus provided in this application embodiment can execute the technical solutions shown in the above method embodiments. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0306] Figure 11 For a schematic diagram of another low-code platform development apparatus provided as an exemplary embodiment of this application, please refer to [link to schematic diagram]. Figure 12 ,exist Figure 11 Based on the illustrated embodiment, the low-code platform development apparatus further includes: a generation module 14.

[0307] The generation module 14 is used to generate and display a prompt message when the matching degree is less than the second preset threshold or the verification result is a verification failure. The prompt message is used to indicate that the selected data source is abnormal.

[0308] The low-code platform development apparatus provided in this application embodiment can execute the technical solutions shown in the above method embodiments. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0309] Figure 12 A schematic diagram of a low-code platform application device provided as an exemplary embodiment of this application can be applied to smart devices. Please refer to [link / reference]. Figure 12 The low-code platform application device 20 may include: an acquisition module 21, a first determination module 22, a second determination module 23, and a rendering module 24, wherein,

[0310] The acquisition module 21 is used to acquire voice information and extract keywords from the voice information;

[0311] The first determining module 22 is used to determine the user's intent based on the keywords;

[0312] The second determining module 23 is used to determine the executable file and data source information based on the user's intent;

[0313] The rendering module 24 is used to render the page according to the executable file and the data source information to obtain the target page and display the target page.

[0314] The low-code platform application device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be described again here.

[0315] An exemplary embodiment of this application provides a structural schematic diagram of an electronic device. Please refer to [link / reference]. Figure 13 The electronic device 30 may include a processor 31 and a memory 32. Exemplarily, the processor 31 and the memory 32 are interconnected via a bus 33.

[0316] The memory 32 stores computer-executed instructions;

[0317] The processor 31 executes the computer execution instructions stored in the memory 32, causing the processor 31 to execute the low-code platform development method or low-code platform application method as shown in the above method embodiments.

[0318] Accordingly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the low-code platform development method or low-code platform application method described in the above method embodiments.

[0319] Accordingly, embodiments of this application may also provide a computer program product, including a computer program, which, when executed by a processor, can implement the low-code platform development method or low-code platform application method shown in the above method embodiments.

[0320] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can 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.) containing computer-usable program code.

[0321] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0322] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0323] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

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

[0325] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0326] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can 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 technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0327] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0328] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A low-code platform development method, characterized in that, include: Obtain the first component information generated in the first engine, the first component information including the identifiers of multiple first components and the component attributes of each first component; The first component information is converted to obtain the second component information, which is in Abstract Syntax Tree (AST) format. Based on the second component information, a second engine executable file is determined; the executable file is obtained by parsing the second component information to obtain project code, and then compiling the project code through multi-threading. The executable file is in a pre-compilation format; The data source information is determined, which includes information about at least one data source associated with the first component; wherein the executable file and the data source information are used to render a visual page in the second engine of the smart device; Determine the data source information, including: Display component page, the component page including the plurality of first components; For any one of the at least one first component, in response to the data source association operation of the first component, a text component corresponding to the first component is determined, wherein the text component includes first text; Perform semantic recognition processing on the first text to determine the first data type; Obtain the similarity between the first data type and the data types of each data source in the data source set; Based on the similarity between the first data type and the data types of each data source in the data source set, a list of data sources is determined in the data source set and displayed. The similarity between the first data type and the data types of each data source in the data source list is greater than or equal to a first preset threshold. The data source list includes multiple data sources. In response to a data source selection operation entered in the data source list, the first component and the selected data source are associated; The data source information is generated based on the information of the data source associated with each of the at least one first component.

2. The method according to claim 1, characterized in that, The executable file is determined based on the second component information, including: Send the second component information to the cloud server; Receive the executable file corresponding to the second component information sent by the cloud server.

3. The method according to claim 2, characterized in that, Send the second component information to the cloud server, including: Determine the Function as a Service (FaaS) interface corresponding to the cloud server; The second component information is sent to the cloud server by calling the FaaS interface.

4. The method according to claim 1, characterized in that, The executable file is determined based on the second component information, including: The second component information is parsed and processed to obtain the project code; The executable file is obtained by compiling the project code using multiple threads.

5. The method according to claim 1, characterized in that, Associating the first component with the selected data source includes: Determine the standard data source information corresponding to the first component, and the current data source information of the selected data source; Determine the matching degree between the standard data source information and the current data source information; Perform an integrity check on the current data source information and obtain the check result; When the matching degree is greater than or equal to the second preset threshold and the verification result is a successful verification, the first component and the selected data source are associated.

6. The method according to claim 5, characterized in that, The method further includes: When the matching degree is less than the second preset threshold, or when the verification result is that the verification failed, a prompt message is generated and displayed, wherein the prompt message is used to indicate that the selected data source is abnormal.

7. The method according to any one of claims 1-6, characterized in that, Obtain information about the first component, including: The component page includes a component list area, a component display area, and an attribute editing area. The component list area includes multiple components, the component display area is used to display the selected component, and the attribute editing area is used to edit the attributes of the selected component. In response to a selection operation input on the plurality of first components in the component list area, the plurality of first components are displayed in the component display area; In response to an editing operation input to the first component in the attribute editing area, the component attributes of the first component are obtained.

8. An electronic device, characterized in that, include: Memory and processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the low-code platform development method as described in any one of claims 1 to 7.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the low-code platform development method according to any one of claims 1 to 7.

10. A computer program product comprising a computer program that, when executed by a processor, implements the low-code platform development method according to any one of claims 1 to 7.

Images