CN114047909A - Component construction method and device and server - Google Patents
Component construction method and device and server Download PDFInfo
- Publication number
- CN114047909A CN114047909A CN202210029711.6A CN202210029711A CN114047909A CN 114047909 A CN114047909 A CN 114047909A CN 202210029711 A CN202210029711 A CN 202210029711A CN 114047909 A CN114047909 A CN 114047909A
- Authority
- CN
- China
- Prior art keywords
- component
- software development
- description
- service platform
- acquiring
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the application provides a component construction method, a device and a server, wherein the method comprises the following steps: acquiring component entry file paths and component metadata of a plurality of platforms according to an entry file list through an entry loader; setting received parameter configuration and description of the component, the issuable event and description of the component, and the readable data model of the component through a software development kit; acquiring source codes of all components according to the component entry file path through a software development kit; compiling according to the source code of each component, the configuration and description of the received parameters, the issuable events and descriptions, the readable data model and the component metadata through a software development toolkit to construct a running state component product and a preview state component product. Therefore, by providing a universal standard and various definitions and considering the use mode of multiple scenes, the adaptability of the multi-scene Web application is improved, and the application effect of the constructed component on multiple platforms is effectively improved.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a component construction method, an apparatus, and a server.
Background
At present, for delivering network (Web) application, a low-code tool of the Web application is generally required to be built, the low-code tool supports the expansion of the original tool capability in a self-defined assembly mode, and the construction and packaging mode of the self-defined assembly and a matched scaffold are required to be maintained by a specific team. The software package built by the low code tool can be identified and used by the same low code tool platform. This build packaging standard has the following disadvantages: the packaging product is only supported to be used on a low-code tool platform; the same dependence is introduced into a plurality of components and is driven in when each component is constructed, so that the same resource is transmitted for many times through a network when a page is loaded, and social resource waste is caused; the existing assembly construction packaging scheme lacks a multi-subject scheme, so that the assembly is not strong in adaptation to multi-scene Web application. In conclusion, the existing component construction has the problem of poor application effect.
Disclosure of Invention
In order to solve the technical problem, embodiments of the present application provide a component construction method, an apparatus, and a server.
In a first aspect, an embodiment of the present application provides a component construction method, where the method includes:
acquiring component entry file paths and component metadata of a plurality of platforms according to an entry file list through an entry loader;
setting received parameter configuration and description of the component, the issuable event and description of the component, and the readable data model of the component through a software development kit;
acquiring source codes of all components according to the component entry file path through the software development toolkit;
compiling by the software development toolkit according to the component source codes, the received parameter configuration and description, the issuable event and description, the readable data model and the component metadata to construct a running-state component product and a preview-state component product.
In a second aspect, an embodiment of the present application provides an assembly building apparatus, including:
the first acquisition module is used for acquiring component entry file paths and component metadata of a plurality of platforms according to the entry file list through an entry loader;
the setting module is used for setting the receiving parameter configuration and description of the component, the issuable event and description of the component and the readable data model of the component through a software development kit;
the second acquisition module is used for acquiring the source code of each component according to the component entry file path through the software development toolkit;
and the compiling module is used for compiling according to the component source codes, the received parameter configuration and description, the issuable events and descriptions, the readable data model and the component metadata through the software development toolkit so as to construct a running-state component product and a preview-state component product.
In a third aspect, an embodiment of the present application provides a server, which includes a memory and a processor, where the memory is used to store a computer program, and the computer program executes the component construction method provided in the first aspect when the processor runs.
In a fourth aspect, the present application provides a computer-readable storage medium, which stores a computer program, and when the computer program runs on a processor, the computer program executes the component construction method provided in the first aspect.
According to the component construction method, the device and the server, the entry loader acquires the component entry file paths and the component metadata of a plurality of platforms according to the entry file list; setting received parameter configuration and description of the component, the issuable event and description of the component, and the readable data model of the component through a software development kit; acquiring source codes of all components according to the component entry file path through the software development toolkit; compiling by the software development toolkit according to the component source codes, the received parameter configuration and description, the issuable event and description, the readable data model and the component metadata to construct a running-state component product and a preview-state component product. Therefore, by providing a universal standard and various definitions, considering the use mode of multiple scenes and a scientific interface design specification, developers can interact with data and platforms more easily, the adaptation degree of the multi-scene Web application is improved, and the application effect of the constructed components on multiple platforms is effectively improved.
Drawings
In order to more clearly explain the technical solutions of the present application, the drawings needed to be used in the embodiments are briefly introduced below, and it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope of protection of the present application. Like components are numbered similarly in the various figures.
FIG. 1 is a flow chart of a component building method provided by an embodiment of the present application;
FIG. 2 is another flow chart diagram illustrating a component construction method provided by an embodiment of the present application;
FIG. 3 is a schematic structural diagram of an assembly construction apparatus provided by an embodiment of the present application;
fig. 4 shows a schematic structural diagram of a server provided in an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments.
The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the present application without making any creative effort, shall fall within the protection scope of the present application.
Hereinafter, the terms "including", "having", and their derivatives, which may be used in various embodiments of the present application, are intended to indicate only specific features, numbers, steps, operations, elements, components, or combinations of the foregoing, and should not be construed as first excluding the existence of, or adding to, one or more other features, numbers, steps, operations, elements, components, or combinations of the foregoing.
Furthermore, the terms "first," "second," "third," and the like are used solely to distinguish one from another and are not to be construed as indicating or implying relative importance.
Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the various embodiments of the present application belong. The terms (such as those defined in commonly used dictionaries) should be interpreted as having a meaning that is consistent with their contextual meaning in the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein in various embodiments.
Example 1
The embodiment of the disclosure provides a component construction method.
Specifically, referring to fig. 1, the component construction method includes:
step S101, acquiring component entry file paths and component metadata of a plurality of platforms according to entry file lists through an entry loader.
In this embodiment, the portal loader is a JavaScript loader that dynamically loads a component according to a portal file manifest, and is also a tool for acquiring reusable dependencies by the component.
In this embodiment, the component metadata includes: component basic information and an adaptive interface model. The basic information of the components comprises the information of entry file paths and component introduction, names, versions, component types, applicable industries and the like which are adaptive to a plurality of platforms.
In this embodiment, the entry file list supports configuration of product paths of multiple platforms as expansion points, and plays a self-description role during runtime loading. Component metadata may also be defined in the entry file manifest so that other systems and middleware can identify and process the component. The portal documentation supports manual configuration, and production versions (production) generated by the software development kit.
In this embodiment, the entry file manifest may be configured by widget, facility, json, and in widget, facility, the schema version (schema version), the component version (component version), the component name (id), the Universal Unique Identifier (UUID), the component description (description), the third party manufacturer (vendor), the component tags (tags), the support platform (support platform), the entries (entries), and the like, where the entries include a preview-pointing preview entry, a runtime-pointing entry, and an attribute-pointing attribute definition entry.
It should be added that, for a Universal unique identification code (Universal unique identifier) of a component, if a component with the same component name (id) issues different versions, uuid of the component of different versions should be different.
Step S102, setting receiving parameter configuration and description of the component, the issuable event and description of the component and the readable data model of the component through a software development kit.
In this embodiment, a Software Development Kit (SDK) can smooth out the differences in custom component standards across multiple codeless and low code tool platforms, so that developers need not be concerned with platform-specific constraints in most cases.
In this embodiment, a properties.js file, which is a property definition of a component, may be provided. The aPaaS platform needs to parse this definition and render the property editor on the platform and pass the corresponding property values to the component.
In this embodiment, the main codes of the attribute value delivery process are as follows:
const component = (props) => {
const { text, object, list, number } = tips// get incoming parameters
const [ textValue, setTextValue ] = text;// deconstruction parameter
const [ object value, setObjectvalue ] = object;// deconstruction parameter
const [listValue, setListValue] = list;
const [numberValue, setNumberValue] = number;
}；
It is noted that the attribute category includes a string (string), a number (number), a boolean value (boolean), an object (object), an array (array), a time-of-day (datetime), an expression (expression), a function (function), an asynchronous function (asyncFunction), an exposed method (exposed function), an exposed variable (exposed variables), an event (event), an event trigger (event initiator), an event bus (event bus), a data source (dataSource), a slot (slot), a binary object (blob), a string input component (InputString), and the like.
It is further added that all expressions (expressions) must be asynchronous and subscriptable commitment objects, and the main codes for the expression (expression) parameter value delivery are as follows:
{
the field names shown on "label": Foobar "// apaas
"key": foobar "// field name of the incoming component parameter
Type expression of expression
"component"// providing expression parameters using the expression editor component of apaas
"WidgetProps" {// parameters passed to the component, here requiring that the expression editor must return a number or string
"returnType": [
{
"type": "number"
},
{
"type": "string"
}
]
}
}
Accordingly, the function (function), the asynchronous function (asyncFunction), the method exposed to the outside (exposedFunction), the variable exposed to the outside (exposedVariables), the event (event), the event trigger (eventEmitter), the event bus (eventBus), and the parameter value of the data source (dataSource) may be implemented by the code, which is not limited herein.
In this embodiment, the corresponding Property value may be Input through a Property Input widget (Property Input Widgets). The property input widget may include: user input string (InputString), user input number (InputNumber), date selection, radio selection, checkbox group (CheckboxGroup), expression editor (expression editor), event listener (eventlisener), event selector (EventSelector).
And step S103, acquiring the source code of each component according to the component entry file path through the software development toolkit.
In this embodiment, the component entry file path serves as an extension point and plays a self-describing role when the runtime state loads. Different component entry file paths store corresponding different component code sources.
Step S104, compiling the software development toolkit according to the component source codes, the received parameter configuration and description, the issuable event and description, the readable data model and the component metadata to construct a running state component product and a preview state component product.
It should be noted that existing build packaging tools are all customized for low-code and no-code tool platforms one-to-one, and developers need to build and package manually after writing glue layers for different platforms. The component construction method provided by the embodiment automatically generates a product compatible with a plurality of platforms, and the component construction efficiency is greatly improved.
In this embodiment, the run-state component artifact and the preview-state component artifact are constructed according to a Universal Module Definition (UMD) standard, so that the purpose of cross-platform universality of the constructed artifacts can be achieved through a Universal artifact standard.
In this embodiment, the component construction method may further include the steps of:
generating, by the software development kit, a component configuration manifest according to the received parameter configuration and description, the issuable events and descriptions, the readable data model;
and packaging the component loader, the component configuration list, the entry file list, the running state component product and the preview state component product through the software development toolkit to obtain a packaged product.
In this embodiment, the component configuration list includes information such as configurations, configuration types, data sources, data source structures, and configuration input device types that the components can receive.
In this embodiment, the component loader, the component configuration manifest, the entry file manifest, the run-state component artifact, and the preview-state component artifact are packaged according to a general module definition standard, and the packaged artifact can also run across a codeless and low-code tool platform. Mainly composed of JavaScript and CSS. The packaged product output by the software development kit can realize the repeated use effect of repeated multiplexing of the components on multiple platforms and reassembly of the component products, can optimize the construction logic and the component loading mode, and can achieve the effects of improving the dependence on the multiplexing degree and saving resources.
In this embodiment, referring to fig. 2, the component construction method may further include the following steps:
and step S105, acquiring the component authorization list and the universal unique identification code of each component through the application program development and deployment service platform.
And step S106, judging whether the universal unique identification code exists in the component authorization list or not through the application program development and deployment service platform.
And step S107, if the universal unique identification code exists in the component authorization list, acquiring an authorization deadline corresponding to the universal unique identification code through the application development and deployment service platform.
And step S108, if the authorization time limit is not expired, determining that the packaged product corresponding to the universal unique identification code is in an authorization state through the application program development and deployment service platform.
In this embodiment, component authorization is jointly completed by an application development and deployment service platform (aPaaS) and a backend (Back End), and there are two ways for component authorization: the online authorization method is used for public clouds and the offline authorization method is used for private clouds. The online authorization is accomplished through the OAuth process, followed by an aPaaS query for the component authorization list. And the aPaaS should publish a callback hook for the backend to update the authorization list. The off-line authorization mode is completed by off-line authorization provided by a back end.
In this embodiment, the aPaaS may check the legitimacy and expiration dates of all components used in the client application. The runtime license key will be checked by the WebAssembly function and the checking result should be globally known by the software development kit and the WebAssembly function check should only occur at page load time.
Therefore, authorized components are controlled through the component authorization list, and the control effect is improved.
In this embodiment, the obtaining of the component authorization list through the application development and deployment service platform in step S105 may include the following steps:
and acquiring a private key of an asymmetric encryption algorithm through an application program development and deployment service platform, and decrypting the component authorization list ciphertext according to the private key to obtain the component authorization list.
In this embodiment, the component authorization list is encrypted by a public key, and the aPaaS will obtain a private key to decrypt the file. The decrypted file will contain the uuid list and expiration date of the available components as well as the runtime license key.
In this embodiment, the component construction method may further include the steps of:
encrypting the component authorization list by adopting a public key of an asymmetric encryption algorithm through the software development kit to obtain a component authorization list ciphertext;
and sending the component authorization list ciphertext to each application program development and deployment service platform through the software development toolkit.
Therefore, the component authorization list is encrypted to obtain a component authorization list ciphertext, and the component authorization list ciphertext is sent to the application program development and deployment service platform, so that the security of transmitting the component authorization list can be improved.
In this embodiment, the component construction method may further include the steps of:
acquiring a component label of a component to be installed through an application development and deployment service platform;
searching a target packaging product corresponding to the component to be installed according to the component tag through the application program development and deployment service platform;
and analyzing the target packaging product through the application program development and deployment service platform so as to install a corresponding component.
In this embodiment, the third-party supplier defines the component tag to help the consumer find the corresponding target packaging product to install the corresponding component, thereby improving the component installation efficiency.
In the component construction method provided by this embodiment, component entry file paths and component metadata of multiple platforms are acquired by an entry loader according to an entry file list; setting received parameter configuration and description of the component, the issuable event and description of the component, and the readable data model of the component through a software development kit; acquiring source codes of all components according to the component entry file path through the software development toolkit; compiling by the software development toolkit according to the component source codes, the received parameter configuration and description, the issuable event and description, the readable data model and the component metadata to construct a running-state component product and a preview-state component product. Therefore, by providing a universal standard and various definitions, considering the use mode of multiple scenes and a scientific interface design specification, developers can interact with data and platforms more easily, the adaptation degree of the multi-scene Web application is improved, and the application effect of the constructed components on multiple platforms is effectively improved.
Example 2
In addition, the embodiment of the disclosure provides a component construction device.
Specifically, as shown in fig. 3, the component construction apparatus 300 includes:
a first obtaining module 301, configured to obtain component entry file paths and component metadata of multiple platforms according to an entry file list;
a setting module 302 for setting received parameter configuration and description of components, issuable events and description of components, readable data models of components through a software development kit;
a second obtaining module 303, configured to obtain source codes of the components according to the component entry file path;
a compiling module 304, configured to compile according to the source code of each component, the received parameter configuration and description, the issuable event and description, the readable data model, and the component metadata, so as to construct a run-state component product and a preview-state component product.
In this embodiment, the component building apparatus 300 further includes:
a generating module, configured to generate a component configuration manifest according to the received parameter configuration and description, the issuable event and description, and the readable data model through the software development kit;
and the packaging module is used for packaging the component loader, the component configuration list, the entry file list, the running state component product and the preview state component product through the software development toolkit to obtain a packaged product.
In this embodiment, the component building apparatus 300 further includes:
the third acquisition module is used for acquiring the component authorization list and the universal unique identification code of each component through the application program development and deployment service platform;
the judging module is used for judging whether the universal unique identification code exists in the component authorization list or not through the application program development and deployment service platform;
the fourth obtaining module is used for obtaining the authorization time limit corresponding to the universal unique identification code through the application program development and deployment service platform if the universal unique identification code exists in the component authorization list;
and the determining module is used for determining that the packaged product corresponding to the universal unique identification code is in an authorized state through the application development and deployment service platform if the authorization time limit is not expired.
In this embodiment, the component building apparatus 300 further includes:
the encryption module is used for encrypting the component authorization list by adopting a public key of an asymmetric encryption algorithm through the software development kit to obtain a component authorization list ciphertext;
and the sending module is used for sending the component authorization list ciphertext to each application program development and deployment service platform through the software development toolkit.
In this embodiment, the third obtaining module is further configured to obtain a private key of an asymmetric encryption algorithm through an application development and deployment service platform, and decrypt the component authorization list ciphertext according to the private key to obtain the component authorization list.
In this embodiment, the component building apparatus 300 further includes:
the fifth acquisition module is used for acquiring the component label of the component to be installed through the application development and deployment service platform;
the searching module is used for searching a target packaging product corresponding to the component to be installed according to the component tag through the application program development and deployment service platform;
and the analysis module is used for analyzing the target packaging product through the application program development and deployment service platform so as to install a corresponding component.
In this embodiment, the component metadata includes: component basic information and an adaptive interface model.
The device 300 of this embodiment can implement the device construction method shown in embodiment 1, and is not described herein again to avoid repetition.
In the component constructing apparatus provided in this embodiment, component entry file paths and component metadata of multiple platforms are obtained by an entry loader according to an entry file list; setting received parameter configuration and description of the component, the issuable event and description of the component, and the readable data model of the component through a software development kit; acquiring source codes of all components according to the component entry file path through the software development toolkit; compiling by the software development toolkit according to the component source codes, the received parameter configuration and description, the issuable event and description, the readable data model and the component metadata to construct a running-state component product and a preview-state component product. Therefore, by providing a universal standard and various definitions, considering the use mode of multiple scenes and a scientific interface design specification, developers can interact with data and platforms more easily, the adaptation degree of the multi-scene Web application is improved, and the application effect of the constructed components on multiple platforms is effectively improved.
Example 3
Furthermore, an embodiment of the present disclosure provides a server, including a memory and a processor, where the memory stores a computer program, and the computer program, when running on the processor, executes the component construction method provided in the above method embodiment 1.
The server 400 includes: a transceiver 401, a bus interface and a processor 402, the processor 402 configured to: acquiring component entry file paths and component metadata of a plurality of platforms according to an entry file list through an entry loader;
setting received parameter configuration and description of the component, the issuable event and description of the component, and the readable data model of the component through a software development kit;
acquiring source codes of all components according to the component entry file path through the software development toolkit;
compiling by the software development toolkit according to the component source codes, the received parameter configuration and description, the issuable event and description, the readable data model and the component metadata to construct a running-state component product and a preview-state component product.
In this embodiment, the processor 402 is further configured to: generating, by the software development kit, a component configuration manifest according to the received parameter configuration and description, the issuable events and descriptions, the readable data model;
and packaging the component loader, the component configuration list, the entry file list, the running state component product and the preview state component product through the software development toolkit to obtain a packaged product.
In this embodiment, the component configuration manifest includes component configuration parameters, a configuration type, and a configuration inputter type, and the processor 402 is further configured to: acquiring an assembly authorization list and a universal unique identification code of each assembly through an application program development and deployment service platform;
judging whether the universal unique identification code exists in the component authorization list or not through the application program development and deployment service platform;
if the universal unique identification code exists in the component authorization list, acquiring an authorization period corresponding to the universal unique identification code through the application program development and deployment service platform;
and if the authorization time limit is not expired, determining that the packaged product corresponding to the universal unique identification code is in an authorization state through the application program development and deployment service platform.
In this embodiment, the processor 402 is further configured to: encrypting the component authorization list by adopting a public key of an asymmetric encryption algorithm through the software development kit to obtain a component authorization list ciphertext;
and sending the component authorization list ciphertext to each application program development and deployment service platform through the software development toolkit.
In this embodiment, the processor 402 is further configured to: and acquiring a private key of an asymmetric encryption algorithm through an application program development and deployment service platform, and decrypting the component authorization list ciphertext according to the private key to obtain the component authorization list.
In this embodiment, the processor 402 is further configured to: acquiring a component label of a component to be installed through an application development and deployment service platform;
searching a target packaging product corresponding to the component to be installed according to the component tag through the application program development and deployment service platform;
and analyzing the target packaging product through the application program development and deployment service platform so as to install a corresponding component.
In this embodiment, the component metadata includes: component basic information and an adaptive interface model.
In this embodiment, the server 400 further includes: a memory 403. In FIG. 4, the bus architecture may include any number of interconnected buses and bridges, with various circuits being linked together, particularly one or more processors represented by processor 402 and memory represented by memory 403. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 401 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium. The processor 402 is responsible for managing the bus architecture and general processing, and the memory 403 may store data used by the processor 402 in performing operations.
The server 400 provided in the embodiment of the present invention may execute the steps of the component construction method in embodiment 1, and details are not described again.
In the server provided by this embodiment, the entry loader acquires the component entry file paths and the component metadata of the multiple platforms according to the entry file list; setting received parameter configuration and description of the component, the issuable event and description of the component, and the readable data model of the component through a software development kit; acquiring source codes of all components according to the component entry file path through the software development toolkit; compiling by the software development toolkit according to the component source codes, the received parameter configuration and description, the issuable event and description, the readable data model and the component metadata to construct a running-state component product and a preview-state component product. Therefore, by providing a universal standard and various definitions, considering the use mode of multiple scenes and a scientific interface design specification, developers can interact with data and platforms more easily, the adaptation degree of the multi-scene Web application is improved, and the application effect of the constructed components on multiple platforms is effectively improved.
Example 4
The present application further provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of:
acquiring component entry file paths and component metadata of a plurality of platforms according to an entry file list through an entry loader;
setting received parameter configuration and description of the component, the issuable event and description of the component, and the readable data model of the component through a software development kit;
acquiring source codes of all components according to the component entry file path through the software development toolkit;
compiling by the software development toolkit according to the component source codes, the received parameter configuration and description, the issuable event and description, the readable data model and the component metadata to construct a running-state component product and a preview-state component product.
In this embodiment, the computer program, when executed by the processor, further implements the steps of:
generating, by the software development kit, a component configuration manifest according to the received parameter configuration and description, the issuable events and descriptions, the readable data model;
and packaging the component loader, the component configuration list, the entry file list, the running state component product and the preview state component product through the software development toolkit to obtain a packaged product.
In this embodiment, the computer program, when executed by the processor, further implements the steps of:
acquiring an assembly authorization list and a universal unique identification code of each assembly through an application program development and deployment service platform;
judging whether the universal unique identification code exists in the component authorization list or not through the application program development and deployment service platform;
if the universal unique identification code exists in the component authorization list, acquiring an authorization period corresponding to the universal unique identification code through the application program development and deployment service platform;
and if the authorization time limit is not expired, determining that the packaged product corresponding to the universal unique identification code is in an authorization state through the application program development and deployment service platform.
In this embodiment, the computer program, when executed by the processor, further implements the steps of:
encrypting the component authorization list by adopting a public key of an asymmetric encryption algorithm through the software development kit to obtain a component authorization list ciphertext;
and sending the component authorization list ciphertext to each application program development and deployment service platform through the software development toolkit.
In this embodiment, the computer program, when executed by the processor, further implements the steps of:
and acquiring a private key of an asymmetric encryption algorithm through an application program development and deployment service platform, and decrypting the component authorization list ciphertext according to the private key to obtain the component authorization list.
In this embodiment, the computer program, when executed by the processor, further implements the steps of:
acquiring a component label of a component to be installed through an application development and deployment service platform;
searching a target packaging product corresponding to the component to be installed according to the component tag through the application program development and deployment service platform;
and analyzing the target packaging product through the application program development and deployment service platform so as to install a corresponding component.
In this embodiment, the component metadata includes: component basic information and an adaptive interface model.
In this embodiment, the computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.
The computer-readable storage medium provided in this embodiment may be implemented by the method for constructing the component shown in embodiment 1, and is not described herein again in order to avoid repetition.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or terminal that comprises the element.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present application.
While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the invention is not limited to the precise embodiments described above, which are meant to be illustrative and not restrictive, and that various changes may be made therein by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.
Claims (10)
1. A method of component construction, the method comprising:
acquiring component entry file paths and component metadata of a plurality of platforms according to an entry file list through an entry loader;
setting received parameter configuration and description of the component, the issuable event and description of the component, and the readable data model of the component through a software development kit;
acquiring source codes of all components according to the component entry file path through the software development toolkit;
compiling by the software development toolkit according to the component source codes, the received parameter configuration and description, the issuable event and description, the readable data model and the component metadata to construct a running-state component product and a preview-state component product.
2. The method of claim 1, further comprising:
generating, by the software development kit, a component configuration manifest according to the received parameter configuration and description, the issuable events and descriptions, the readable data model;
and packaging the component loader, the component configuration list, the entry file list, the running state component product and the preview state component product through the software development toolkit to obtain a packaged product.
3. The method of claim 1, further comprising:
acquiring an assembly authorization list and a universal unique identification code of each assembly through an application program development and deployment service platform;
judging whether the universal unique identification code exists in the component authorization list or not through the application program development and deployment service platform;
if the universal unique identification code exists in the component authorization list, acquiring an authorization period corresponding to the universal unique identification code through the application program development and deployment service platform;
and if the authorization time limit is not expired, determining that the packaged product corresponding to the universal unique identification code is in an authorization state through the application program development and deployment service platform.
4. The method of claim 3, further comprising:
encrypting the component authorization list by adopting a public key of an asymmetric encryption algorithm through the software development kit to obtain a component authorization list ciphertext;
and sending the component authorization list ciphertext to each application program development and deployment service platform through the software development toolkit.
5. The method of claim 3, wherein obtaining the component authorization list via the application development deployment service platform comprises:
and acquiring a private key of an asymmetric encryption algorithm through an application program development and deployment service platform, and decrypting the component authorization list ciphertext according to the private key to obtain the component authorization list.
6. The method of claim 2, further comprising:
acquiring a component label of a component to be installed through an application development and deployment service platform;
searching a target packaging product corresponding to the component to be installed according to the component tag through the application program development and deployment service platform;
and analyzing the target packaging product through the application program development and deployment service platform so as to install a corresponding component.
7. The method of claim 1, wherein the component metadata comprises: component basic information and an adaptive interface model.
8. An assembly building apparatus, characterized in that the apparatus comprises:
the first acquisition module is used for acquiring component entry file paths and component metadata of a plurality of platforms according to the entry file list through an entry loader;
the setting module is used for setting the receiving parameter configuration and description of the component, the issuable event and description of the component and the readable data model of the component through a software development kit;
the second acquisition module is used for acquiring the source code of each component according to the component entry file path through the software development toolkit;
and the compiling module is used for compiling according to the component source codes, the received parameter configuration and description, the issuable events and descriptions, the readable data model and the component metadata through the software development toolkit so as to construct a running-state component product and a preview-state component product.
9. A server, comprising a memory and a processor, the memory storing a computer program which, when executed by the processor, performs the component construction method of any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that it stores a computer program which, when run on a processor, performs the component construction method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210029711.6A CN114047909A (en) | 2022-01-12 | 2022-01-12 | Component construction method and device and server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210029711.6A CN114047909A (en) | 2022-01-12 | 2022-01-12 | Component construction method and device and server |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114047909A true CN114047909A (en) | 2022-02-15 |
Family
ID=80196259
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210029711.6A Pending CN114047909A (en) | 2022-01-12 | 2022-01-12 | Component construction method and device and server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114047909A (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20200089524A1 (en) * | 2018-09-17 | 2020-03-19 | Servicenow, Inc. | Wait a duration timer action and flow engine for building automated flows within a cloud based development platform |
| CN113778445A (en) * | 2021-09-15 | 2021-12-10 | 树根互联股份有限公司 | Cross-platform component generation method and device, electronic equipment and storage medium |
-
2022
- 2022-01-12 CN CN202210029711.6A patent/CN114047909A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20200089524A1 (en) * | 2018-09-17 | 2020-03-19 | Servicenow, Inc. | Wait a duration timer action and flow engine for building automated flows within a cloud based development platform |
| CN113778445A (en) * | 2021-09-15 | 2021-12-10 | 树根互联股份有限公司 | Cross-platform component generation method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8307379B2 (en) | Determining an extension to use to process an input object to a call in a program | |
| CN108845940B (en) | Enterprise-level information system automatic function testing method and system | |
| CN107729014B (en) | Page jump method and structure based on Android | |
| US20080301640A1 (en) | Method and system for allocating id of software component | |
| CN106569880B (en) | Method and system for dynamically sharing resources between Android applications | |
| CN108319460A (en) | Method and device for generating application program installation package, electronic equipment and storage medium | |
| CN109284106A (en) | Method for release management, electronic device and the readable storage medium storing program for executing of business rule | |
| CN113298331B (en) | Work order processing method, device and system and electronic equipment | |
| CN106569863B (en) | Resource and code modularization-based android app resource updating and repairing method | |
| CN111475825B (en) | Role authority setting method and device | |
| CN109213533A (en) | A kind of advertisement SDK dynamic loading method, device and terminal | |
| CN113330419A (en) | Equipment application installation method and device | |
| CN105245581A (en) | Application program transmission method and device | |
| CN109033452B (en) | Intelligent construction loading method and system for data warehouse | |
| CN114489676A (en) | Source code processing method, system, storage medium and electronic equipment | |
| CN113032004B (en) | Method, apparatus and program product for managing development jobs in a development environment | |
| CN112416980A (en) | Data service processing method, device and equipment | |
| CN114047909A (en) | Component construction method and device and server | |
| EP2250555A2 (en) | Dynamic intermediate language modification and replacement | |
| CN111861292A (en) | Waybill number generation method, apparatus, server and storage medium | |
| CN111176652A (en) | Application program management method, device, equipment and medium | |
| CN110286907B (en) | Display method and device of public button assembly | |
| CN113918239B (en) | Code implementation method and system | |
| KR20150108151A (en) | System and method for developing application | |
| CN106502754B (en) | Activity component loading method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20220215 |