CN117492748A

CN117492748A - Capability multiplexing method, device, equipment and storage medium based on low-code system

Info

Publication number: CN117492748A
Application number: CN202311501696.1A
Authority: CN
Inventors: 王佳媛; 邓楠; 蒋维
Original assignee: China United Network Communications Group Co Ltd; Unicom Digital Technology Co Ltd; China Unicom Internet of Things Corp Ltd
Current assignee: China United Network Communications Group Co Ltd; Unicom Digital Technology Co Ltd; China Unicom Internet of Things Corp Ltd
Priority date: 2023-11-10
Filing date: 2023-11-10
Publication date: 2024-02-02

Abstract

The method, the device, the equipment and the storage medium for multiplexing the capacity based on the low-code system are applied to equipment deployed with a development platform, and relate to the technical field of computer software. In the process of providing development service through a development platform, if an object in a multiplexing low-code system is detected, a target component library which is packaged with the object is introduced from a content distribution network through a script form, and the object in the target component library is multiplexed, wherein the object comprises a basic component, a page and a composite component. Because the target component library encapsulated with the objects is introduced in the script form, the target component library can be a first component library encapsulated with a page rendering component, a page and a composite component and a second component library encapsulated with a basic component, multiplexing of the objects in the low-code system in other non-low-code systems can be realized, and when the multiplexed objects are pages or composite components, the multiplexed objects can be modified.

Description

Capability multiplexing method, device, equipment and storage medium based on low-code system

Technical Field

The present disclosure relates to the field of computer software technologies, and in particular, to a method, an apparatus, a device, and a storage medium for multiplexing capabilities based on a low-code system.

Background

With the wide application of the internet of things technology and the gradual increase of intelligent devices, a plurality of low-code systems are appeared on the market. The low code system is a software development tool that provides a visual interface and pre-built base components, and a user can generate composite components or pages, such as drag-and-drop composite components or pages, based on the low code system with little programming knowledge. However, for this type of platform, the dependency of the generated composite component or page on the low code system is very high, i.e., the generated composite component or page cannot be migrated to other non-low code systems for reuse.

In the related art, a page or a composite component generated by drawing a low-code system can be embedded in other non-low-code systems through the form of an iframe to multiplex the page or the component in the low-code system, wherein the component comprises the composite component and a base component. But in other non-low code systems, no modifications can be made to the multiplexed components or pages.

Disclosure of Invention

The application provides a capacity multiplexing method, device, equipment and storage medium based on a low-code system, which are used for solving the technical problem that user-defined pages or components cannot be multiplexed in other non-low-code systems.

In a first aspect, the present application provides a capability multiplexing method based on a low-code system, which is applied to a device deployed with a development platform, where the low-code system provides a visual interface and a base component, and responds to an interaction operation of a user on a target base component in the visual interface, generates a first object, encapsulates the first object into a first component library, the first component library further encapsulates a page rendering component, the first component library is deployed in a content distribution network, the content distribution network further includes a second component library encapsulated with the base component, and the first object includes a page and a composite component.

The capacity multiplexing method based on the low-code system comprises the following steps:

in the process of providing development service through a development platform, if a second object in a multiplexing low-code system is detected, introducing a target component library packaged with the second object from a content distribution network through a script form;

multiplexing the second object in the target component library.

In a possible implementation manner, the target component library encapsulated with the second object is introduced from the content distribution network through script form, and the target component library comprises:

acquiring a content distribution network link of a target component library packaged with a second object, wherein the content distribution network link comprises a JavaScript file link and a cascading style sheet file link of the target component library packaged with the second object;

Embedding the JavaScript file link into a head label in a hypertext markup language (Hyper Text Markup Language, abbreviated as HTML) file through a script label;

linking the cascading style sheet file to a head label or a main body label embedded in the HTML file through a linking label;

and running the HTML file and introducing the HTML file into the target component library.

In one possible embodiment, the obtaining a content distribution network link of the target component library encapsulated with the second object includes:

the content delivery network link of the target component library encapsulating the second object is obtained from a document of the content delivery network provider.

In a possible implementation manner, the target component library is a first component library, and the first component library is further encapsulated with a page rendering component, and multiplexes a second object in the target component library, including:

introducing a page rendering component according to the name of the page rendering component in the first component library;

exporting a page JavaScript object notation (JavaScript Object Notation, json for short) from a low code system, and transmitting a page Json body as a parameter to a rendering component in a page rendering component through Javascript codes;

multiplexing the second object in the target component library with the rendering component.

determining an object type of the second object;

determining a target component library packaged with a second object according to the object type;

the target component library is imported from the content distribution network in script form.

In a second aspect, the present application provides a capability multiplexing device based on a low-code system, which is applied to a device deployed with a development platform, where the low-code system provides a visual interface and a base component, and responds to an interaction operation of a user on a target base component in the visual interface, generates a first object, encapsulates the first object into a first component library, and further encapsulates a page rendering component, where the first component library is deployed in a content distribution network, and the content distribution network further includes a second component library encapsulated with the base component, where the first object includes a page and a composite component.

The capacity multiplexing device based on the low code system comprises:

the introducing module is used for introducing a target component library packaged with a second object from the content distribution network in a script form if the second object in the multiplexing low-code system is detected in the process of providing development service through the development platform;

And the multiplexing module is used for multiplexing the second object in the target component library.

In a possible embodiment, the introduction module is specifically configured to:

embedding the JavaScript file link into a head label in the HTML file through a script label;

linking the cascading style sheet file to a head label or a main body label embedded in the HTML file through a link label;

In one possible embodiment, the obtaining a content distribution network link of the target component library encapsulated with the second object includes: the content delivery network link of the target component library encapsulating the second object is obtained from a document of the content delivery network provider.

In a possible implementation manner, the multiplexing module is specifically configured to:

the method comprises the steps that a page Json body is exported from a low-code system, and is transmitted to a rendering component in a page rendering component through a Javascript code as a parameter;

In a possible embodiment, the introducing module is further configured to:

determining an object type of the second object;

In a third aspect, the present application provides an electronic device, comprising:

a memory for storing computer-executable instructions;

a processor for executing computer-executable instructions to implement the low code system based capability multiplexing method of any of the first aspects.

In a fourth aspect, the present application provides a capability multiplexing system, comprising:

the system comprises a low-code system, a first component library, a second component library, a content distribution network and a combination component, wherein the low-code system is used for providing a visual interface and a basic component, responding to the interaction operation of a user on a target basic component in the visual interface, generating a first object and packaging the first object into the first component library, the first component library is deployed in the content distribution network, the content distribution network further comprises a second component library packaged with the basic component, and the first object comprises pages and the combination component;

and the development system is used for providing development services, and introducing a target component library encapsulated with the second object from the content distribution network through a script form to multiplex the second object in the target component library when the second object in the multiplexing low-code system is detected in the process of providing the development services.

In one possible embodiment, the composite assembly includes a template assembly, which is a reusable assembly.

In a fifth aspect, the present application provides a computer-readable storage medium having stored therein computer-executable instructions that, when executed, are configured to implement the low code system-based capability multiplexing method of any one of the first aspects.

In a sixth aspect, the present application provides a computer program product comprising a computer program which, when executed, is adapted to implement the low code system based capability multiplexing method of any one of the first aspects.

In the method, the device, the equipment and the storage medium for multiplexing the capacity based on the low-code system, if the object in the multiplexing low-code system is detected in the process of providing development service through a development platform, a target component library which is packaged with the object is introduced from a content distribution network through a script form, and the object in the target component library is multiplexed, wherein the object comprises a basic component, a page and a composite component. Since the target component library packaged with the objects is introduced from the content distribution network in the script form, wherein the target component library can be a first component library packaged with a page rendering component, a page and a composite component and a second component library packaged with a basic component, multiplexing of the objects in the low-code system in other non-low-code systems can be realized, and when the multiplexed objects are pages or composite components, the multiplexed objects can be modified.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.

Fig. 1 is a flow chart of a capability multiplexing method based on a low-code system according to an embodiment of the present application;

FIG. 2 is a schematic flow chart of introducing a target component library encapsulated with a second object from a content distribution network in script form according to an embodiment of the present application;

fig. 3 is a specific flowchart of a second object in the reuse target component library according to an embodiment of the present application;

fig. 4 is a specific schematic diagram of a capability multiplexing method based on a low-code system according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of a capability multiplexing device based on a low-code system according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Specific embodiments thereof have been shown by way of example in the drawings and will herein be described in more detail. These drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the accompanying claims.

It should be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present application are information and data authorized by the user or fully authorized by each party, and the collection, use and processing of the related data need to comply with the related laws and regulations and standards of the related country and region, and provide corresponding operation entries for the user to select authorization or rejection.

With the development of the internet of things, development tasks are more and more for developers, functions of a front-end interface are repeated and similar, if the developers want to multiplex old functions and interfaces, the functions and interfaces are multiplexed in a mode of copying codes, but the old codes are lost due to the fact that patterns are not in line with user interface specifications, copying is incomplete or the old codes are changed along with task personnel. The advent of low code systems has followed the problem of solving the above-mentioned developer.

The low-code system is a development tool or platform, provides a graphical interface, a drag-and-drop component and a visual development tool, can enable a user to drag and configure a page or component wanted by the user, simplifies and automates a development process, accelerates the delivery speed of an application program, and reduces the time and complexity of manually writing codes.

Existing low-code systems typically generate a composite component or page that the user wants by dragging, but the generated component or page is strongly dependent on the low-code system, and the user-configured component or page cannot be reused in another system after the platform is detached. Some researchers then cannot leave the low-code system by storing the name of the page or component and the corresponding Json volume in the database, but the method can still only be read and parsed in the low-code system. Some researchers multiplex the common components through a user interface type component library similar to an element ui in the form of packaged components, and although the method can be used away from a low-code system, the method cannot multiplex the customized composite components or pages in the user low-code system, and only the packaged partial individual components can be multiplexed.

In order to address the pain points, the application provides a technical scheme for multiplexing the capacity based on the low-code system, which not only can flexibly drag the configuration page, but also can directly multiplex the dragged components or components into other development systems for use, and is not limited to the low-code system.

The capacity multiplexing method based on the low-code system is applied to equipment deployed with a development platform, the low-code system provides a visual interface and a basic component, responds to interaction operation of a user on a target basic component in the visual interface, generates a first object, encapsulates the first object into a first component library, encapsulates a page rendering component, deploys the first component library in a content delivery network (Content Delivery Network, CDN for short), the content delivery network is a cloud CDN for example, the content delivery network further comprises a second component library encapsulated with the basic component, and the first object comprises pages and composite components.

It will be appreciated that encapsulating objects into component libraries requires extracting the components that are desired to be encapsulated from the application, ensuring that the components that are desired to be encapsulated can operate in a separate environment. Then creating a new folder as a library project of the packaging component, entering the folder to initialize the new project, selecting a proper construction tool according to the project, configuring the construction tool to compile and package the library. An entry file is defined in the library engineering as the primary entry point of the library, where the file may be a separate JavaScript file. Documents are written for the components, describing how to use and integrate the library. Finally, a build command is executed to generate library files for the production environment, and the built library is issued to a package manager. After the object is packaged to the target component library, the packaged component library is required to be packaged into a JavaScript packet independently, and then the JavaScript packet is uploaded to a content distribution network. It is added that the template component (e.g., device map, device list, device attribute), page rendering component (including page component, rendering component) and base component (e.g., button, breadcrumb) of the low code system need to be packaged separately, e.g., packaged as a library a, and base component packaged as B library.

Further, it is necessary to keep the packaged component unique identification code consistent with the component unique identification code in the component resource table in packaging the object into the component library, because this ensures that the correct component can be accurately identified and located when the component is used. Keeping the unique component identification codes of the package consistent with the unique component identification codes in the component resource table first requires that a set of explicit naming conventions be ensured, and a unique identification code be assigned to each component in creating the component library. And then, in the component library, the unique identification code of the component is associated with the related information of the component, tasks such as packaging the component are processed by utilizing an automation tool, and the consistency of the unique identification of the component is not destroyed by any modification and update through the continuous integration and test flow of automation.

Optionally, before performing the capability multiplexing component based on the low code system, it is necessary to treat all supported components of the low code system as a resource, create a component table in advance using a database, and then store all supported component information of all low code systems, including component names, component types, component unique identification codes, data types of component support rendering, and the like.

The following describes the technical solutions of the present application and how the technical solutions of the present application solve the above technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.

Fig. 1 is a flow chart of a capability multiplexing method based on a low-code system according to an embodiment of the present application. As shown in fig. 1, the capability multiplexing method based on the low-code system includes:

s101, if a second object in the multiplexing low-code system is detected in the process of providing development service through a development platform, introducing a target component library packaged with the second object from a content distribution network through a script form.

It will be appreciated that when a second object of the multiplexed low code system is detected, a target component library encapsulating the second object needs to be imported from the content distribution network in script form. The second object may be a base component or a composite component. The basic components are core modules for constructing low-code application programs, provide various common functions and characteristics, can help developers to quickly build the application, simplify the development process and reduce the technical threshold, and are common in the basic components such as buttons, breadcrumbs and the like.

Composite components are higher-level modules built based on multiple base components provided by a low-code system. The composite component contains template components, which are common tools in a low-code system, mainly used for creating and managing reusable pages or components, and common template components contain device maps, device lists, device attributes, and the like.

The page rendering component can comprise a page component and a rendering component, wherein the page component is an independent module or element forming a complete page, has specific functions and interactions, and can improve the speed of developers by using the page component. Further, a rendering component is a page or component that combines data and templates to generate a final presentation to a user, with which components can be multiplexed in other low-code systems.

The target component library may be a first component library in which a page rendering component, a page, and a composite component are packaged, and a second component library in which a base component is packaged. It can be understood that if the second object is a base component, the target component library is a second component library; if the second object is a composite component or page, the target component library is the first component library. For the implementation manner of deploying the first component library and the second component library to the content distribution network, reference may be made to the foregoing, and details are not repeated herein.

S102, multiplexing a second object in the target component library.

Optionally, the second object in the multiplexing target component library may be directly used for existing second objects, or new components or pages may be created by modifying and expanding the second object after multiplexing. The generating manner of the second object may be set according to the specific situation, for example, in a low-code system, a user generally generates a new component or page through dragging.

In the embodiment of the application, in the process of providing development service through a development platform, if a second object in a multiplexing low-code system is detected, introducing a target component library packaged with the second object from a content distribution network through a script form, multiplexing the second object in the target component library, and modifying a multiplexed component or page in other non-low-code systems, wherein the second object comprises a basic component, a page and a composite component. Since the target component library packaged with the objects is introduced from the content distribution network in the script form, wherein the target component library can be a first component library packaged with a page rendering component, a page and a composite component and a second component library packaged with a basic component, multiplexing of the objects in the low-code system in other non-low-code systems can be realized, and when the multiplexed objects are pages or composite components, the multiplexed objects can be modified.

On the basis of the above embodiment, in one implementation, the target component library encapsulated with the second object is introduced from the content distribution network in S101 through a script form, referring to fig. 2, and fig. 2 is a schematic flow chart provided in the embodiment of the present application for introducing the target component library encapsulated with the second object from the content distribution network through a script form. As shown in fig. 2, includes:

s201, acquiring a content distribution network link of a target component library packaged with a second object, wherein the content distribution network link comprises a JavaScript file link and a cascading style sheet file link of the target component library packaged with the second object.

It will be appreciated that obtaining a content distribution network link to a target component library having a second object includes: the content delivery network link of the target component library encapsulating the second object is obtained from a document of the content delivery network provider. By acquiring the content distribution network link of the target component library encapsulating the second object from the document of the content distribution network provider, the user can be assisted in correctly setting up and using the content distribution network.

S202, embedding the JavaScript file link into a head label in the HTML file through a script label.

Optionally, the JavaScript file link is tagged with a header embedded in the HTML file by a script tag. The header tags in the HTML file are typically used to define meta-information for the page, introduce external resources, and configure other settings associated with the page. Supplementary note that script tags are mainly used to embed or link JavaScript code in HTML files.

S203, linking the cascading style sheet file to a head label or a main body label embedded in the HTML file through a link label.

It will be appreciated that cascading style sheet file links are header tags or body tags that are embedded into the HTML file by link tags. The main body tag in the HTML file is mainly used for defining main contents of the page document. Further, link tags are typically used in HTML files to link external resources.

S204, running the HTML file and introducing the HTML file into a target component library.

According to the embodiment of the application, the target component library packaged with the second object is introduced from the content distribution network in the script form, so that the efficiency of developers can be improved, and rapid development is easier.

Further, the target component library is a first component library, and the first component library is further packaged with a page rendering component, and a specific flowchart of multiplexing the second object in the target component library is shown in fig. 3. Fig. 3 is a specific flowchart of a second object in the reuse target component library according to an embodiment of the present application. As shown in fig. 3, includes:

s301, introducing a page rendering component according to the name of the page rendering component in the first component library.

S302, a page Json body is exported from the low-code system, and the page Json body is used as a parameter to a rendering component in the page rendering components through a Javascript code.

It will be appreciated that the Json body is a lightweight data exchange format, typically used to transfer and store data between different platforms or languages. The Json body consists of two main parts, bond and value. Wherein the key is a character string and the value may be a character string, a numerical value, a boolean value, an array, an object or a null value. By combining pairs of key values, a Json body can be created. It is added that key pairs are separated by a colon, and different key pairs are separated by commas.

Further, the low-code system can automatically export the Json body of the current page, and then the automatically exported Json body of the page is used as a parameter to a rendering component in the page rendering components through Javascript codes.

S303, multiplexing a second object in the target component library by using the rendering component.

Alternatively, the rendering component refers to using one component as a sub-component of another component, and by the rendering component, the components can be combined and multiplexed in different forms without changing the logical relationship of the original components.

In addition, the embodiment of the application enables other development systems to refer to the components of the low-code system based on the capability of the low-code system to independently extract and precipitate the components, and enables the other development systems to realize multiplexing of the pages or the composite components and templates by exporting the json body content of the pages of the low-code system and transmitting the json body content as parameters to the rendering component.

Optionally, the introducing the target component library encapsulated with the second object from the content distribution network through script form further comprises: determining an object type of the second object; determining a target component library packaged with a second object according to the object type; the target component library is imported from the content distribution network in script form.

As an example, if it is desired to multiplex simple components on other non-low code systems, a user may directly introduce and use base components in the target component library, such as buttons, breadcrumbs, etc. If the self-defined pages or the self-defined composite components dragged from the low-code system are multiplexed in other non-low-code systems, the user needs to introduce a rendering component in a target component library, the self-derived page Json bodies from the low-code system are transmitted to the rendering component as parameters, and then the rendering component multiplexes the dragged self-defined pages or the self-defined composite components.

According to the embodiment, the target component library packaged with the second object is determined through the second object type, and the target component library is introduced from the content distribution network through the script form, so that a user can be helped to introduce the target component library in a targeted mode, and efficiency is improved.

Illustratively, a template component and a page rendering component of a low-code system are packaged into an A library, namely, a first component library is the A library; and packaging the basic components into a B library, namely, the first component library is the B library. If the type of the multiplexing component in other non-low code systems is a component in the A library, directly multiplexing the basic component, if the type of the multiplexing component is a component in the B library, introducing a rendering component in the B library, transmitting a page Json body automatically derived from the low code system as a parameter to the rendering component, multiplexing the dragged custom page or the custom composite component by using the rendering component, and referring to FIG. 4, FIG. 4 is a specific schematic diagram of a capability multiplexing method based on the low code system according to the embodiment of the application.

Fig. 5 is a schematic structural diagram of a capability multiplexing device based on a low-code system according to an embodiment of the present application. The capacity multiplexing device based on the low-code system is applied to equipment deployed with a development platform, the low-code system provides a visual interface and a basic component, responds to interaction operation of a user on a target basic component in the visual interface, generates a first object, encapsulates the first object into a first component library, encapsulates a page rendering component, deploys the first component library in a content distribution network, and further comprises a second component library encapsulated with the basic component, wherein the first object comprises pages and composite components;

As shown in fig. 5, the capability multiplexing apparatus 500 based on the low code system includes:

an import module 501, configured to import, from a content distribution network, a target component library encapsulated with a second object in a script form if the second object in the multiplexed low-code system is detected during a process of providing development services through a development platform;

and the multiplexing module 502 is configured to multiplex the second object in the target component library.

In one possible implementation, the introducing module 501 is specifically configured to:

In a possible implementation manner, the multiplexing module 502 is specifically configured to:

In one possible implementation, the introducing module 501 is further configured to:

determining an object type of the second object;

The capacity multiplexing device based on the low-code system provided by the embodiment of the application can execute the technical scheme shown in the embodiment of the method, and the implementation principle and the beneficial effects are similar, and are not repeated.

It should be noted that, it should be understood that the division of the modules of the above apparatus is merely a division of a logic function, and may be fully or partially integrated into a physical entity or may be physically separated. And these modules may all be implemented in software in the form of calls by the processing element; or can be realized in hardware; the method can also be realized in a form of calling software by a processing element, and the method can be realized in a form of hardware by a part of modules. For example, the processing module may be a processing element that is set up separately, may be implemented in a chip of the above-mentioned apparatus, or may be stored in a memory of the above-mentioned apparatus in the form of program codes, and the functions of the above-mentioned processing module may be called and executed by a processing element of the above-mentioned apparatus. The implementation of the other modules is similar. In addition, all or part of the modules can be integrated together or can be independently implemented. The processing element here may be an integrated circuit with signal processing capabilities. In implementation, each step of the above method or each module above may be implemented by an integrated logic circuit of hardware in a processor element or an instruction in a software form.

For example, the modules above may be one or more integrated circuits configured to implement the methods above, such as: one or more application specific integrated circuits (Application Specific Integrated Circuit, abbreviated as ASIC), or one or more microprocessors (Digital Signal Processor, abbreviated as DSP), or one or more field programmable gate arrays (Field Programmable Gate Array, abbreviated as FPGA), or the like. For another example, when a module is implemented in the form of program code deployed by a processing element, the processing element may be a general-purpose processor, such as a central processing unit (Central Processing Unit, CPU) or other processor that may invoke the program code. For another example, the modules may be integrated together and implemented in the form of a System-On-a-Chip (SOC).

Fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application. As shown in fig. 6, an electronic device 600 provided in an embodiment of the present application may include: a processor 601 and a memory 602, wherein:

a memory 602 for storing computer-executable instructions;

a processor 601 for executing computer-executable instructions stored in a memory 602 to implement the low code system based capability multiplexing method described in the foregoing method embodiments.

It should be appreciated that the processor 601 may be a central processing unit (Central Processing Unit, CPU for short), but may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP for short), application specific integrated circuits (Application Specific Integrated Circuit, ASIC for short), etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in a processor for execution. The memory 602 may include a high-speed random access memory (Random Access Memory, abbreviated as RAM), and may further include a non-volatile memory NVM (non-volatile memory), such as at least one magnetic disk memory, and may also be a U-disk, a removable hard disk, a read-only memory, a magnetic disk, or an optical disk.

Optionally, the electronic device 600 may also include a communication interface 603. In a specific implementation, if the communication interface 603, the memory 602, and the processor 601 are implemented independently, the communication interface 603, the memory 602, and the processor 601 may be connected to each other through buses and perform communication with each other. The bus may be an industry standard architecture (Industry Standard Architecture, ISA) bus, an external device interconnect (Peripheral Component, PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, among others. Buses may be divided into address buses, data buses, control buses, etc., but do not represent only one bus or one type of bus.

Alternatively, in a specific implementation, if the communication interface 603, the memory 602, and the processor 601 are integrated on a chip, the communication interface 603, the memory 602, and the processor 601 may complete communication through internal interfaces.

The embodiment of the application also provides a capability multiplexing system, which comprises a low-code system, a first object and a second component library, wherein the low-code system is used for providing a visual interface and a basic component, responding to the interaction operation of a user on a target basic component in the visual interface, generating the first object, packaging the first object into the first component library, the first component library is deployed in a content distribution network, the content distribution network further comprises a second component library packaged with the basic component, and the first object comprises a page and a composite component. The composite component comprises a template component and a page rendering component, wherein the template component is a reusable component.

Embodiments of the present application also provide a computer readable storage medium having stored therein computer executable instructions that when executed are configured to implement the low code system based capability multiplexing method described in any of the foregoing embodiments.

It is understood that the computer readable storage medium may be implemented by any type or combination of volatile or non-volatile Memory devices, such as static random access Memory (Static Random Access Memory, SRAM for short), electrically erasable programmable Read-Only Memory (Electrically Erasable Programmable Read Only Memory, EEPROM for short), erasable programmable Read-Only Memory (Erasable Programmable Read Only Memory, EPROM for short), programmable Read-Only Memory (Programmable Read Only Memory, PROM for short), read Only Memory (ROM for short), magnetic Memory, flash Memory, magnetic disk, or optical disk. A readable storage medium can be any available medium that can be accessed by a general purpose or special purpose computer.

An exemplary computer readable storage medium is coupled to the processor such the processor can read information from, and write information to, the computer readable storage medium. In the alternative, the computer-readable storage medium may be integral to the processor. The processor and the computer readable storage medium may reside in an ASIC. The processor and the computer-readable storage medium may also reside as discrete components in an electronic device.

The integrated modules, which are implemented in the form of software functional modules, may be stored in a computer readable storage medium. The software functional modules described above are stored in a computer-readable storage medium and include instructions for causing an electronic device (which may be a personal computer, a server, or a network device, etc.) or a processor to perform some steps of the methods described in the various embodiments of the present application.

The present application also provides a computer program product comprising a computer program which, when executed, implements the low code system based capability multiplexing method described in any of the previous embodiments.

It should be noted that, for simplicity of description, the foregoing method embodiments are all expressed as a series of action combinations, but it should be understood by those skilled in the art that the present application is not limited by the order of actions described, as some steps may be performed in other order or simultaneously in accordance with the present application. Further, those skilled in the art will also appreciate that the embodiments described in the specification are all alternative embodiments, and that the acts and modules referred to are not necessarily required in the present application.

It should be further noted that, although the steps in the flowchart are sequentially shown as indicated by arrows, the steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least a portion of the steps in the flowcharts may include a plurality of sub-steps or stages that are not necessarily performed at the same time, but may be performed at different times, the order in which the sub-steps or stages are performed is not necessarily sequential, and may be performed in turn or alternately with at least a portion of the sub-steps or stages of other steps or other steps.

In the foregoing embodiments, the descriptions of the embodiments are emphasized, and for parts of one embodiment that are not described in detail, reference may be made to related descriptions of other embodiments. The technical features of the above embodiments may be combined in any way, and for brevity, all of the possible combinations of the technical features of the above embodiments are not described, but should be considered as the scope of the description

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It is to be understood that the present application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims

1. The capacity multiplexing method based on the low-code system is characterized by being applied to equipment deployed with a development platform, wherein the low-code system provides a visual interface and a basic component, responds to the interactive operation of a user acting on a target basic component in the visual interface, generates a first object, encapsulates the first object into a first component library, is deployed in a content distribution network, is further encapsulated with a page rendering component, and further comprises a second component library encapsulated with the basic component, and the first object comprises a page and a composite component;

in the process of providing development service through the development platform, if a second object in the low-code system is detected to be multiplexed, introducing a target component library packaged with the second object from the content distribution network through a script form;

multiplexing the second object in the target component library.

2. The low code system based capability multiplexing method of claim 1, wherein the introducing the target component library encapsulating the second object from the content distribution network through a script form comprises:

acquiring a content distribution network link of a target component library packaged with the second object, wherein the content distribution network link comprises a JavaScript file link and a cascading style sheet file link of the target component library packaged with the second object;

embedding the JavaScript file link into a head label in a hypertext markup language (HTML) file through a script label;

3. The low code system based capability multiplexing method of claim 2, wherein the obtaining a content distribution network link encapsulating a target component library of the second object comprises:

and acquiring the content distribution network link of the target component library packaged with the second object from the document of the content distribution network provider.

4. A method of multiplexing capabilities based on a low-code system according to any one of claims 1 to 3, wherein the target component library is the first component library, and the multiplexing of the second object in the target component library comprises:

exporting a page JavaScript object representation Json from the low-code system, and transmitting the page Json as a parameter to a rendering component in the page rendering components through Javascript codes;

multiplexing a second object in the target component library with the rendering component.

5. A method of multiplexing capabilities based on a low-code system according to any one of claims 1 to 3, wherein the introducing, from the content distribution network, a target component library encapsulating the second object in script form, comprises:

Determining an object type of the second object;

determining a target component library packaged with the second object according to the object type;

6. A capability multiplexing device based on a low-code system, which is characterized by being applied to equipment deployed with a development platform, wherein the low-code system provides a visual interface and a basic component, responds to the interactive operation of a user on a target basic component in the visual interface, generates a first object, encapsulates the first object into a first component library, is deployed in a content distribution network, and further comprises a second component library encapsulated with the basic component, and the first object comprises a page and a composite component;

the capacity multiplexing device based on the low-code system comprises:

the introducing module is used for introducing a target component library packaged with a second object from the content distribution network in a script form if the second object in the low-code system is detected to be multiplexed in the process of providing development service through the development platform;

7. An electronic device, comprising: a processor, and a memory communicatively coupled to the processor;

the memory stores computer-executable instructions;

the processor executes computer-executable instructions stored in the memory to implement the method of any one of claims 1 to 5.

8. A capability multiplexing system, comprising:

the system comprises a low-code system, a first component library and a second component library, wherein the low-code system is used for providing a visual interface and a basic component, responding to the interaction operation of a user on a target basic component in the visual interface, generating a first object, and packaging the first object into the first component library, wherein the first component library is further packaged with a page rendering component, is deployed in a content distribution network, and further comprises a second component library packaged with the basic component, and the first object comprises a page and a composite component;

and the development system is used for providing development service, and introducing a target component library encapsulated with the second object from the content distribution network through a script form when the second object in the low-code system is detected to be multiplexed in the process of providing the development service so as to multiplex the second object in the target component library.

9. The capability multiplexing system of claim 8, wherein the composite component comprises a template component that is a reusable component.

10. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor are adapted to carry out the method of any one of claims 1 to 5.