CN114138289A - Component issuing method and device, electronic equipment and storage medium - Google Patents
Component issuing method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN114138289A CN114138289A CN202111452453.4A CN202111452453A CN114138289A CN 114138289 A CN114138289 A CN 114138289A CN 202111452453 A CN202111452453 A CN 202111452453A CN 114138289 A CN114138289 A CN 114138289A
- Authority
- CN
- China
- Prior art keywords
- component
- target
- dependent
- target component
- issuing
- 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
- 238000000034 method Methods 0.000 title claims abstract description 46
- 230000001419 dependent effect Effects 0.000 claims abstract description 172
- 238000013507 mapping Methods 0.000 claims abstract description 56
- 230000006835 compression Effects 0.000 claims description 32
- 238000007906 compression Methods 0.000 claims description 32
- 238000012545 processing Methods 0.000 claims description 17
- 238000004590 computer program Methods 0.000 claims description 10
- 238000004806 packaging method and process Methods 0.000 claims description 9
- 238000004891 communication Methods 0.000 description 10
- 238000010586 diagram Methods 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 4
- 230000005236 sound signal Effects 0.000 description 4
- 230000004044 response Effects 0.000 description 3
- 230000001133 acceleration Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 230000001172 regenerating effect Effects 0.000 description 2
- OKTJSMMVPCPJKN-UHFFFAOYSA-N Carbon Chemical compound [C] OKTJSMMVPCPJKN-UHFFFAOYSA-N 0.000 description 1
- 208000033748 Device issues Diseases 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 229910021389 graphene Inorganic materials 0.000 description 1
- 238000003384 imaging method Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The present disclosure relates to a component issuing method, device, electronic apparatus, and storage medium, the method including: aiming at each target assembly in a target assembly set, obtaining a dependent assembly mapping relation corresponding to each target assembly; determining a dependent component of each target component in the target component library based on the mapping relation of each dependent component to obtain a dependent component set corresponding to each target component; generating a resource acquisition address corresponding to each dependent component set; and issuing a component issuing document including each resource acquisition address. By adopting the method and the device, the target program can be prevented from occupying a larger storage space, and the development efficiency of the target program is improved.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method and an apparatus for issuing a component, an electronic device, and a storage medium.
Background
A component may refer to the encapsulation of one or more code segments that perform their respective functions as one or more separate parts.
When a program is developed by using a UI (user interface) component library, developers often need to introduce all components in the UI component library for a target program, which easily causes the target program to occupy a large storage space.
Disclosure of Invention
The present disclosure provides a component publishing method, device, electronic device and storage medium, so as to at least solve the problem that a target program occupies a large storage space in the related art. The technical scheme of the disclosure is as follows:
according to a first aspect of the embodiments of the present disclosure, there is provided a component issuing method, including:
aiming at each target assembly in a target assembly set, obtaining a dependent assembly mapping relation corresponding to each target assembly;
determining a dependent component of each target component in the target component library based on the mapping relation of each dependent component to obtain a dependent component set corresponding to each target component;
generating a resource acquisition address corresponding to each dependent component set;
and issuing a component issuing document including each resource acquisition address.
In one possible implementation manner, the obtaining, for each target component in the target component set, a component dependency corresponding to each target component includes:
reading a component configuration file corresponding to the target component;
and determining a dependent component mapping relation corresponding to the target component according to the dependent component description information in the component configuration file.
In one possible implementation manner, the determining, in the target component library, a dependent component of each target component based on each dependent component mapping relationship to obtain a dependent component set corresponding to each target component includes:
determining a dependent component of each target component in the target component library based on each dependent component mapping relation;
adding a dependent component of the target component to a file directory corresponding to the target component;
and carrying out compression and packaging processing on the files in the file directory to obtain a dependent component compression package of the target component.
In one possible implementation manner, the generating a resource obtaining address corresponding to each dependent component set includes:
sending the dependent component compression packet of the target component to a target server; the target server is used for storing the data resource corresponding to the dependency component compressed packet and generating a resource acquisition address of the dependency component compressed packet;
and receiving the resource acquisition address returned by the target server.
In one possible implementation, the publishing a component publication document including each of the resource acquisition addresses includes:
receiving an acquisition request sent by a user terminal aiming at the component release document;
and responding to the acquisition request, and sending the component publishing document to the user terminal.
In one possible implementation manner, the determining, in the target component library, a dependent component of each target component based on each dependent component mapping relationship to obtain a dependent component set corresponding to each target component includes:
determining a component name corresponding to the dependent component of the target component according to the mapping relation of the dependent component corresponding to the target component;
and querying the dependent component of the target component in the target component library according to the component name.
According to a second aspect of embodiments of the present disclosure, there is provided a component issuing device including:
the acquisition unit is configured to execute the steps of acquiring a dependent component mapping relation corresponding to each target component in a target component set;
a determining unit configured to determine a dependent component of each target component in the target component library based on each dependent component mapping relationship, so as to obtain a dependent component set corresponding to each target component;
the generating unit is configured to generate a resource acquisition address corresponding to each dependent component set;
and the issuing unit is configured to execute issuing of a component issuing document including each of the resource acquisition addresses.
In a possible implementation manner, the obtaining unit is specifically configured to perform reading of a component configuration file corresponding to the target component; and determining a dependent component mapping relation corresponding to the target component according to the dependent component description information in the component configuration file.
In a possible implementation manner, the determining unit is specifically configured to perform determining, in the target component library, a dependent component of each target component based on each dependent component mapping relationship; adding a dependent component of the target component to a file directory corresponding to the target component; and carrying out compression and packaging processing on the files in the file directory to obtain a dependent component compression package of the target component.
In one possible implementation, the generating unit is specifically configured to execute sending the dependent component compression packet of the target component to a target server; the target server is used for storing the data resource corresponding to the dependency component compressed packet and generating a resource acquisition address of the dependency component compressed packet; and receiving the resource acquisition address returned by the target server.
In one possible implementation manner, the publishing unit is specifically configured to execute receiving an acquisition request sent by a user terminal for the component publishing document; and responding to the acquisition request, and sending the component publishing document to the user terminal.
In a possible implementation manner, the determining unit is specifically configured to determine, according to the dependent component mapping relationship corresponding to the target component, a component name corresponding to the dependent component of the target component; and querying the dependent component of the target component in the target component library according to the component name.
According to a third aspect of the embodiments of the present disclosure, there is provided an electronic device, including a memory and a processor, where the memory stores a computer program, and the processor implements the component issuing method according to the first aspect or any one of the possible implementation manners of the first aspect when executing the computer program.
According to a fourth aspect of embodiments of the present disclosure, there is provided a storage medium having stored thereon a computer program which, when executed by a processor, implements a component distribution method as set forth in the first aspect or any one of the possible implementations of the first aspect.
According to a fifth aspect of embodiments of the present disclosure, there is provided a computer program product, the program product comprising a computer program, the computer program being stored in a readable storage medium, from which at least one processor of a device reads and executes the computer program, so that the device performs the component issuing method of any one of the possible implementations of the first aspect.
The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects: aiming at each target assembly in the target assembly set, determining the dependent assembly of each target assembly in the target assembly library by acquiring the mapping relation of the dependent assembly corresponding to each target assembly and based on the mapping relation of each dependent assembly, obtaining the dependent assembly set corresponding to each target assembly, regenerating a resource acquisition address corresponding to each dependent assembly set, and finally, issuing a document by issuing an assembly comprising each resource acquisition address; therefore, when a developer develops a target program, the developer can obtain the file resources of the dependent components of each component through the resource obtaining address in the component publishing document without reading the source code of each component, and meanwhile, the developer does not need to introduce all components in the UI component library aiming at the target program, so that redundant data of a target program data packet is reduced, and the target program can be prevented from occupying redundant storage space.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the disclosure and are not to be construed as limiting the disclosure.
FIG. 1 is a diagram of an application environment illustrating a component publishing method in accordance with an exemplary embodiment.
FIG. 2 is a flow diagram illustrating a component publication method in accordance with an exemplary embodiment.
FIG. 3 is a flow diagram illustrating another component publication method in accordance with an illustrative embodiment.
FIG. 4 is a block diagram illustrating a component issuing device in accordance with an exemplary embodiment.
FIG. 5 is a block diagram illustrating an electronic device in accordance with an example embodiment.
Detailed Description
In order to make the technical solutions of the present disclosure better understood by those of ordinary skill in the art, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the disclosure described herein are capable of operation in sequences other than those illustrated or otherwise described herein. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
It should also be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for presentation, analyzed data, etc.) referred to in the present disclosure are both information and data that are authorized by the user or sufficiently authorized by various parties.
The component publishing method provided by the disclosure can be applied to the application environment shown in fig. 1. The electronic device 104 obtains a dependent component mapping relationship corresponding to each target component in the target component set; the electronic device 104 determines the dependent components of the target components in the target component library based on the mapping relationship of the dependent components to obtain a dependent component set corresponding to each target component; the electronic device 104 generates resource acquisition addresses corresponding to the dependent component sets; the electronic device 104 issues a component issue document including each resource acquisition address to the terminal 102.
Fig. 2 is a flowchart illustrating a component publishing method, according to an exemplary embodiment, for use in an electronic device, as shown in fig. 2, including the following steps.
In step S210, for each target component in the target component set, a dependent component mapping relationship corresponding to each target component is obtained.
Wherein, the dependent component mapping relationship may refer to a mapping relationship between the target component and the dependent component of the target component.
Wherein the component may be a UI (user interface) component.
Wherein a set of target components may refer to a set of UI components.
In a specific implementation, for each target component in the target component set, the electronic device may obtain a dependent component mapping relationship corresponding to each target component. The electronic equipment can read a component configuration file corresponding to the target component; then, the electronic device may determine a dependent component mapping relationship corresponding to the target component according to the dependent component description information in the component configuration file.
In step S220, based on the mapping relationship between the dependent components, the dependent component of each target component is determined in the target component library, and a dependent component set corresponding to each target component is obtained.
In specific implementation, the electronic device may determine a component identifier corresponding to a dependent component of the target component according to the dependent component mapping relationship corresponding to the target component; and querying the dependent component of the target component in the target component library according to the component identification.
In step S230, a resource acquisition address corresponding to each dependent component set is generated.
In a specific implementation, the electronic device may upload a dependent component set corresponding to each target component to a Content Delivery Network (CDN) in the form of a compressed packet.
In step S240, a component issue document including the respective resource acquisition addresses is issued.
In a specific implementation, the electronic device may publish a component publication document including the resource acquisition addresses.
The component publishing method comprises the steps of obtaining a dependent component mapping relation corresponding to each target component in a target component set aiming at each target component, determining the dependent component of each target component in a target component library based on the dependent component mapping relation, obtaining the dependent component set corresponding to each target component, regenerating a resource obtaining address corresponding to each dependent component set, and finally, publishing a document by publishing the component comprising each resource obtaining address; therefore, when a developer develops a target program, the developer can obtain the file resources of the dependent components of each component through the resource obtaining address in the component publishing document without reading the source code of each component, and meanwhile, the developer does not need to introduce all components in the UI component library aiming at the target program, so that redundant data of a target program data packet is reduced, and the target program can be prevented from occupying redundant storage space.
In an exemplary embodiment, for each target component in the target component set, obtaining a component dependency corresponding to each target component includes: reading a component configuration file corresponding to a target component; and determining a dependent component mapping relation corresponding to the target component according to the dependent component description information in the component configuration file.
The component configuration file comprises information for describing the component dependency relationship corresponding to the target component.
In a specific implementation, in the process that the electronic device obtains the component dependency relationship corresponding to each target component for each target component in the target component set, the electronic device can read a component configuration file corresponding to the target component; then, the electronic device may determine a dependent component mapping relationship corresponding to the target component according to the dependent component description information in the component configuration file.
According to the technical scheme of the embodiment, the mapping relation of the dependent component corresponding to the target component can be accurately determined by reading the component configuration file corresponding to the target component and according to the dependent component description information in the component configuration file.
In an exemplary embodiment, determining the dependent component of each target component in the target component library based on the mapping relationship of each dependent component to obtain a dependent component set corresponding to each target component includes: determining the dependent components of the target components in the target component library based on the mapping relation of the dependent components; adding a dependent component of the target component to a file directory corresponding to the target component; and carrying out compression and packaging processing on the files in the file directory to obtain a dependent component compression package of the target component.
In a specific implementation, in the process that the electronic device determines the dependent component of each target component in the target component library based on the mapping relationship of each dependent component to obtain the dependent component set corresponding to each target component, the electronic device may determine the dependent component of each target component in the target component library based on the mapping relationship of each dependent component. The electronic equipment adds the dependent component of the target component to a file directory corresponding to the target component; and carrying out compression and packaging processing on the files in the file directory to obtain a dependent component compression package of the target component.
Specifically, the electronic device can read the dependency information in the configuration file for each ui component and place all dependent components of the component into the same directory by performing a node script recursion. Then, the electronic equipment automatically performs zip compression processing on the directory through the node script to form a zip compression package of the dependent component of the target component.
According to the technical scheme of the embodiment, the dependent components of the target components are determined in the target component library based on the mapping relation of the dependent components; adding a dependent component of the target component to a file directory corresponding to the target component; and compressing and packaging the files in the file directory to obtain a dependency component compression package of the target component, thereby realizing compression and packaging of the dependency components corresponding to each target component and facilitating subsequent distribution of the dependency components of each component.
In an exemplary embodiment, generating the resource obtaining address corresponding to each dependent component set includes: sending a dependent component compression packet of the target component to the target server; and receiving the resource acquisition address returned by the target server.
The target server is used for storing the data resources corresponding to the dependency component compression packet and generating the resource acquisition address of the dependency component compression packet. In practical applications, the target server may be a server in a Content Delivery Network (CDN).
In a specific implementation, in a process of generating a resource obtaining address corresponding to each dependent component set, the electronic device may upload a dependent component compression packet of a target component to a server in a Content Delivery Network (CDN). A server in a Content Delivery Network (CDN) may store the received data resource corresponding to the dependent component compressed packet in a preset database, generate a resource acquisition address of the dependent component compressed packet, send the resource acquisition address to the electronic device, and enable the electronic device to receive the resource acquisition address returned by the target server.
According to the technical scheme of the embodiment, the dependent component compression packet of the target component is sent to the target server, so that the target server stores the data resource corresponding to the dependent component compression packet and generates the resource acquisition address of the dependent component compression packet, and the resource acquisition address corresponding to each dependent component set is generated.
In an exemplary embodiment, publishing a component publication document including resource acquisition addresses includes: receiving an acquisition request sent by a user terminal aiming at a component release document; in response to the acquisition request, the sending component issues the document to the user terminal.
In a specific implementation, in a process that an electronic device issues a component issuing document including resource acquiring addresses, when a user needs to acquire the component issuing document, the user may send an acquisition request for the component issuing document through a user terminal, and after receiving the acquisition request sent by the user terminal for the component issuing document, the electronic device sends the component issuing document to the user terminal in response to the acquisition request, so that the user terminal can receive the component issuing document. After the user terminal receives the component release document, the user can obtain the address through the resource in the component release document and obtain the required dependent component compression package of the UI component.
According to the technical scheme of the embodiment, an acquisition request sent by a user terminal aiming at a component release document is received; and responding to the acquisition request, and sending the component release document to the user terminal, so that the requirement of a developer can be responded in time, and the component release document can be sent to the user terminal of the developer in time.
In an exemplary embodiment, the method further comprises: responding to an access operation of at least one resource acquisition address in the component issuing document, and determining a target component corresponding to the accessed resource acquisition address; sending a compressed packet acquisition request aiming at a target component to a target server; the target server is used for responding to the compressed packet acquisition request and returning a dependent component compressed packet corresponding to the target component; and receiving the dependent component compression package returned by the target server.
In a specific implementation, the electronic device may determine, in response to an access operation to at least one resource acquisition address in the component issuing document, a target component corresponding to the accessed resource acquisition address; then, the electronic device sends a compressed packet acquisition request for the target component to the target server for the target server to receive the compressed packet acquisition request.
After the target server receives the compressed packet acquisition request, the target server responds to the compressed packet acquisition request and returns the dependent component compressed packet corresponding to the target component to the user terminal, so that the user terminal receives the dependent component compressed packet returned by the target server.
In an exemplary embodiment, determining the dependent component of each target component in the target component library based on the mapping relationship of each dependent component to obtain a dependent component set corresponding to each target component includes: determining a component name corresponding to the dependent component of the target component according to the mapping relation of the dependent component corresponding to the target component; and querying the dependent component of the target component in the target component library according to the component name.
In a specific implementation, in the process that the electronic device determines the dependent component of each target component in the target component library based on the mapping relationship of each dependent component to obtain the dependent component set corresponding to each target component, the electronic device may determine the component name corresponding to the dependent component of the target component according to the mapping relationship of the dependent component corresponding to the target component; then, the electronic device searches out the component corresponding to the component name in the target component library based on the component name, and the component is used as the dependent component of the target component.
According to the technical scheme of the embodiment, the component name corresponding to the dependent component of the target component is determined according to the mapping relation of the dependent component corresponding to the target component, and the dependent component of the target component is accurately inquired in the target component library according to the component name.
Fig. 3 is a flow chart illustrating another component publishing method, as shown in fig. 3, for use in the electronic device of fig. 1, according to an example embodiment, including the following steps.
In step S310, for each target component in the target component set, a component configuration file corresponding to the target component is read.
In step S320, determining a dependent component mapping relationship corresponding to the target component according to the dependent component description information in the component configuration file.
In step S330, based on each dependency component mapping relationship, a dependency component of each target component is determined in the target component library, and the dependency component of the target component is added to the file directory corresponding to the target component.
In step S340, performing compression and packaging processing on the files in the file directory to obtain a dependent component compression package of the target component.
In step S350, sending the dependent component compression package of the target component to the target server; and the target server is used for storing the data resource corresponding to the dependency component compressed packet and generating a resource acquisition address of the dependency component compressed packet.
In step S360, the resource obtaining address returned by the target server is received.
In step S370, a component issue document including each of the resource acquisition addresses is issued.
It should be noted that, for the specific limitations of the above steps, reference may be made to the specific limitations of the component issuing method, and details are not described herein again.
It should be understood that although the steps in the flowcharts of fig. 2 and 3 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2 and 3 may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed in turn or alternately with other steps or at least some of the other steps.
It is understood that the same/similar parts between the embodiments of the method described above in this specification can be referred to each other, and each embodiment focuses on the differences from the other embodiments, and it is sufficient that the relevant points are referred to the descriptions of the other method embodiments.
FIG. 4 is a block diagram illustrating a component publication apparatus according to an example embodiment. Referring to fig. 4, the apparatus includes:
an obtaining unit 410, configured to perform, for each target component in a target component set, obtaining a dependent component mapping relationship corresponding to each target component;
a determining unit 420, configured to determine, in the target component library, a dependent component of each target component based on each dependent component mapping relationship, so as to obtain a dependent component set corresponding to each target component;
a generating unit 430 configured to perform generation of a resource acquisition address corresponding to each dependent component set;
the publishing unit 440 is configured to perform publishing of the component publishing document including each of the resource acquiring addresses.
In a possible implementation manner, the obtaining unit 410 is specifically configured to perform reading of a component configuration file corresponding to the target component; and determining a dependent component mapping relation corresponding to the target component according to the dependent component description information in the component configuration file.
In a possible implementation manner, the determining unit 420 is specifically configured to perform determining, in the target component library, a dependent component of each target component based on each dependent component mapping relationship; adding a dependent component of the target component to a file directory corresponding to the target component; and carrying out compression and packaging processing on the files in the file directory to obtain a dependent component compression package of the target component.
In a possible implementation, the generating unit 430 is specifically configured to execute sending the dependent component compression packet of the target component to a target server; the target server is used for storing the data resource corresponding to the dependency component compressed packet and generating a resource acquisition address of the dependency component compressed packet; and receiving the resource acquisition address returned by the target server.
In a possible implementation manner, the publishing unit 440 is specifically configured to execute receiving an obtaining request sent by a user terminal for the component publishing document; and responding to the acquisition request, and sending the component publishing document to the user terminal.
In a possible implementation manner, the determining unit 420 is specifically configured to determine, according to the dependent component mapping relationship corresponding to the target component, a component name corresponding to the dependent component of the target component; and querying the dependent component of the target component in the target component library according to the component name.
With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
Fig. 5 is a block diagram illustrating an electronic device 500 for performing a component publication method in accordance with an example embodiment. For example, the electronic device 500 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a gaming console, a tablet device, a medical device, a fitness device, a personal digital assistant, and so forth.
Referring to fig. 5, electronic device 500 may include one or more of the following components: processing component 502, memory 504, power component 506, multimedia component 508, audio component 510, interface to input/output (I/O) 512, sensor component 514, and communication component 516.
The processing component 502 generally controls overall operation of the electronic device 500, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing components 502 may include one or more processors 520 to execute instructions to perform all or a portion of the steps of the methods described above. Further, the processing component 502 can include one or more modules that facilitate interaction between the processing component 502 and other components. For example, the processing component 502 can include a multimedia module to facilitate interaction between the multimedia component 508 and the processing component 502.
The memory 504 is configured to store various types of data to support operations at the electronic device 500. Examples of such data include instructions for any application or method operating on the electronic device 500, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 504 may be implemented by any type or combination of volatile or non-volatile storage devices, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk, optical disk, or graphene memory.
The power supply component 506 provides power to the various components of the electronic device 500. The power components 506 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the electronic device 500.
The multimedia component 508 includes a screen providing an output interface between the electronic device 500 and a user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 508 includes a front facing camera and/or a rear facing camera. The front camera and/or the rear camera may receive external multimedia data when the electronic device 500 is in an operating mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.
The audio component 510 is configured to output and/or input audio signals. For example, the audio component 510 includes a Microphone (MIC) configured to receive external audio signals when the electronic device 500 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may further be stored in the memory 504 or transmitted via the communication component 516. In some embodiments, audio component 510 also includes a speaker for outputting audio signals.
The I/O interface 512 provides an interface between the processing component 502 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.
The sensor assembly 514 includes one or more sensors for providing various aspects of status assessment for the electronic device 500. For example, the sensor assembly 514 may detect an open/closed state of the electronic device 500, the relative positioning of components, such as a display and keypad of the electronic device 500, the sensor assembly 514 may detect a change in the position of the electronic device 500 or components of the electronic device 500, the presence or absence of user contact with the electronic device 500, orientation or acceleration/deceleration of the device 500, and a change in the temperature of the electronic device 500. The sensor assembly 514 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 514 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 514 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 516 is configured to facilitate wired or wireless communication between the electronic device 500 and other devices. The electronic device 500 may access a wireless network based on a communication standard, such as WiFi, a carrier network (such as 2G, 3G, 4G, or 5G), or a combination thereof. In an exemplary embodiment, the communication component 516 receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 516 further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
In an exemplary embodiment, the electronic device 500 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components for performing the above-described methods.
In an exemplary embodiment, a computer-readable storage medium comprising instructions, such as the memory 504 comprising instructions, executable by the processor 520 of the electronic device 500 to perform the above-described method is also provided. For example, the computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
In an exemplary embodiment, a computer program product is also provided, which includes instructions executable by the processor 520 of the electronic device 500 to perform the above-described method.
It should be noted that the descriptions of the above-mentioned apparatus, the electronic device, the computer-readable storage medium, the computer program product, and the like according to the method embodiments may also include other embodiments, and specific implementations may refer to the descriptions of the related method embodiments, which are not described in detail herein.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (10)
1. A method for publishing a component, comprising:
aiming at each target assembly in a target assembly set, obtaining a dependent assembly mapping relation corresponding to each target assembly;
determining a dependent component of each target component in the target component library based on the mapping relation of each dependent component to obtain a dependent component set corresponding to each target component;
generating a resource acquisition address corresponding to each dependent component set;
and issuing a component issuing document including each resource acquisition address.
2. The component publishing method according to claim 1, wherein the obtaining, for each target component in the target component set, the component dependency corresponding to each target component comprises:
reading a component configuration file corresponding to the target component;
and determining a dependent component mapping relation corresponding to the target component according to the dependent component description information in the component configuration file.
3. The component publishing method according to claim 1, wherein the determining, based on the dependency component mapping relationship, the dependent component of each target component in the target component library to obtain a dependent component set corresponding to each target component includes:
determining a dependent component of each target component in the target component library based on each dependent component mapping relation;
adding a dependent component of the target component to a file directory corresponding to the target component;
and performing compression and packaging processing on the file directory to obtain a dependent component compression package of the target component.
4. The component issuing method according to claim 3, wherein the generating a resource acquisition address corresponding to each dependent component set includes:
sending the dependent component compression packet of the target component to a target server; the target server is used for storing the data resource corresponding to the dependency component compressed packet and generating a resource acquisition address of the dependency component compressed packet;
and receiving the resource acquisition address returned by the target server.
5. The component issuing method according to claim 1, wherein the issuing of the component issue document including each of the resource acquisition addresses includes:
receiving a document acquisition request sent by a user terminal aiming at the component release document;
and responding to the document acquisition request, and sending the component issuing document to the user terminal.
6. The component publishing method according to claim 1, wherein the determining, based on the dependency component mapping relationship, the dependent component of each target component in the target component library to obtain a dependent component set corresponding to each target component includes:
determining a component name corresponding to the dependent component of the target component according to the mapping relation of the dependent component corresponding to the target component;
and querying the dependent component of the target component in the target component library according to the component name.
7. A component dispensing apparatus, comprising:
the acquisition unit is configured to execute the steps of acquiring a dependent component mapping relation corresponding to each target component in a target component set;
a determining unit configured to determine a dependent component of each target component in the target component library based on each dependent component mapping relationship, so as to obtain a dependent component set corresponding to each target component;
the generating unit is configured to generate a resource acquisition address corresponding to each dependent component set;
and the issuing unit is configured to execute issuing of a component issuing document including each of the resource acquisition addresses.
8. An electronic device, comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the component issuing method according to any one of claims 1 to 6.
9. A computer-readable storage medium, wherein instructions in the computer-readable storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the component issuing method of any one of claims 1 to 6.
10. A computer program product comprising instructions which, when executed by a processor of an electronic device, enable the electronic device to perform the component issuing method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111452453.4A CN114138289A (en) | 2021-11-30 | 2021-11-30 | Component issuing method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111452453.4A CN114138289A (en) | 2021-11-30 | 2021-11-30 | Component issuing method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114138289A true CN114138289A (en) | 2022-03-04 |
Family
ID=80387011
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111452453.4A Pending CN114138289A (en) | 2021-11-30 | 2021-11-30 | Component issuing method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114138289A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160124736A1 (en) * | 2003-12-02 | 2016-05-05 | International Business Machines Corporation | Script generation engine and mapping semantic models for target platform |
| US20160308949A1 (en) * | 2015-04-17 | 2016-10-20 | Emc Corporation | Content resource management |
| CN112416425A (en) * | 2020-11-20 | 2021-02-26 | 微医云(杭州)控股有限公司 | APP construction method and device, computer equipment and storage medium |
| CN113238795A (en) * | 2021-05-14 | 2021-08-10 | 北京达佳互联信息技术有限公司 | Component distribution method, device, electronic equipment, storage medium and program product |
-
2021
- 2021-11-30 CN CN202111452453.4A patent/CN114138289A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160124736A1 (en) * | 2003-12-02 | 2016-05-05 | International Business Machines Corporation | Script generation engine and mapping semantic models for target platform |
| US20160308949A1 (en) * | 2015-04-17 | 2016-10-20 | Emc Corporation | Content resource management |
| CN112416425A (en) * | 2020-11-20 | 2021-02-26 | 微医云(杭州)控股有限公司 | APP construction method and device, computer equipment and storage medium |
| CN113238795A (en) * | 2021-05-14 | 2021-08-10 | 北京达佳互联信息技术有限公司 | Component distribution method, device, electronic equipment, storage medium and program product |
Non-Patent Citations (1)
| Title |
|---|
| 孙浩: "大数据组件部署和管理平台的设计与实现", 《中国优秀硕士学位论文全文数据库 信息科技辑》, 15 December 2020 (2020-12-15), pages 138 - 174 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108304475B (en) | Data query method and device and electronic equipment | |
| CN104462296B (en) | File management method and device and terminal | |
| CN106547547B (en) | data acquisition method and device | |
| CN105049219B (en) | Flow booking method and system, mobile terminal and server | |
| CN105094904A (en) | Application program installation method and device | |
| CN115185717B (en) | Interface calling method and device, electronic equipment and storage medium | |
| CN107402767B (en) | Method and device for displaying push message | |
| CN113901353A (en) | Information display method, device and system, electronic equipment and server | |
| CN106506808B (en) | Method and device for prompting communication message | |
| CN106447747B (en) | Image processing method and device | |
| CN109245992B (en) | Request processing method and device, electronic equipment and storage medium | |
| CN110908814A (en) | Message processing method and device, electronic equipment and storage medium | |
| CN107885464B (en) | Data storage method, device and computer readable storage medium | |
| CN110764847A (en) | User information processing method and device, electronic equipment and storage medium | |
| CN113778687B (en) | Memory allocation information processing method and device, electronic equipment and storage medium | |
| CN106941556B (en) | Method and device for determining information of converged communication contact persons | |
| CN112862349B (en) | Data processing method, device and equipment based on ABS service data | |
| CN110457084B (en) | Loading method and device | |
| CN110995767B (en) | Request processing method and device | |
| CN114268802A (en) | Virtual space display method and device, electronic equipment and storage medium | |
| CN114567790A (en) | Information display method and device, electronic equipment and storage medium | |
| CN114138289A (en) | Component issuing method and device, electronic equipment and storage medium | |
| CN109032583B (en) | Data interaction method and device | |
| CN112860625A (en) | Data acquisition method, data storage method, device, equipment and storage medium | |
| CN107257384B (en) | Service state monitoring 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 |