CN112256320B - Version number generation method, device, terminal and storage medium - Google Patents
Version number generation method, device, terminal and storage medium Download PDFInfo
- Publication number
- CN112256320B CN112256320B CN202011219290.0A CN202011219290A CN112256320B CN 112256320 B CN112256320 B CN 112256320B CN 202011219290 A CN202011219290 A CN 202011219290A CN 112256320 B CN112256320 B CN 112256320B
- Authority
- CN
- China
- Prior art keywords
- target object
- file
- version number
- identifier
- code
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 39
- 238000004590 computer program Methods 0.000 claims description 14
- 230000008878 coupling Effects 0.000 claims description 9
- 238000010168 coupling process Methods 0.000 claims description 9
- 238000005859 coupling reaction Methods 0.000 claims description 9
- 238000005538 encapsulation Methods 0.000 claims description 4
- 238000004806 packaging method and process Methods 0.000 abstract description 5
- 238000007726 management method Methods 0.000 description 14
- 230000002093 peripheral effect Effects 0.000 description 10
- 230000001133 acceleration Effects 0.000 description 9
- 230000006870 function Effects 0.000 description 8
- 238000012545 processing Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 7
- 238000004891 communication Methods 0.000 description 6
- 230000003287 optical effect Effects 0.000 description 5
- 239000000919 ceramic Substances 0.000 description 2
- 239000004973 liquid crystal related substance Substances 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000009877 rendering Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000007423 decrease Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000004927 fusion Effects 0.000 description 1
- 230000001788 irregular Effects 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012858 packaging process Methods 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 230000006641 stabilisation Effects 0.000 description 1
- 238000011105 stabilization Methods 0.000 description 1
- 239000010409 thin film Substances 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the application provides a version number generation method, a version number generation device, a terminal and a storage medium. The method comprises the following steps: acquiring a first file identification of a code file of a target object, wherein the target object refers to a software product with a version replacement; generating a version number of the target object based on the first file identification; and packaging the object information of the target object to obtain a compressed file corresponding to the target object, wherein the object information of the target object comprises the version number of the target object. According to the technical scheme provided by the embodiment of the application, the version number is generated according to the unique identifier of the code file of the software product before the file package of the software product, so that the automatic generation of the version number is realized, the manual participation is not needed, the labor cost is saved, and the generation efficiency of the version number can be improved.
Description
Technical Field
The embodiment of the application relates to the technical field of Internet, in particular to a version number generation method, a version number generation device, a terminal and a storage medium.
Background
Currently, software products released by application program manufacturers often have version replacement so as to achieve the purposes of adding functions, repairing vulnerabilities and the like.
When a software product is version-changed, a version number is typically used to identify the version of the software product. In the related art, a software product is manually selected by a technician to select an unused version number before the file is packaged. For example, version number of software product A is 1.0, 2.0, etc.
In the related art, the version number generation process needs to be manually participated, and the efficiency of generating the version number is low.
Disclosure of Invention
The embodiment of the application provides a version number generation method, a version number generation device, a version number generation terminal and a storage medium, and the generation efficiency of version numbers is improved. The technical scheme is as follows:
in one aspect, an embodiment of the present application provides a version number generating method, where the method includes:
acquiring a first file identification of a code file of a target object, wherein the target object refers to a software product with version replacement;
generating a version number of the target object based on the first file identification;
And encapsulating the object information of the target object to obtain a compressed file corresponding to the target object, wherein the object information of the target object comprises the version number of the target object.
On the other hand, an embodiment of the present application provides a version number generating device, which includes:
The device comprises an identification acquisition module, a storage module and a storage module, wherein the identification acquisition module is used for acquiring a first file identification of a code file of a target object, and the target object refers to a software product with version replacement;
the version number generation module is used for generating the version number of the target object based on the first file identification;
And the file generation module is used for carrying out file encapsulation on the object information of the target object to obtain a compressed file corresponding to the target object, wherein the object information of the target object comprises the version number of the target object.
In yet another aspect, an embodiment of the present application provides a terminal, where the terminal includes a processor and a memory, where the memory stores a computer program, and the computer program is loaded and executed by the processor to implement the version number generation method according to the aspect.
In yet another aspect, an embodiment of the present application provides a computer readable storage medium having a computer program stored therein, the computer program being loaded and executed by a processor to implement a version number generation method as described in one aspect.
In yet another aspect, embodiments of the present application provide a computer program product, the computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions so that the computer device performs the version number generation method described above.
The technical scheme provided by the embodiment of the application has the following beneficial effects:
By generating the version number according to the unique identification of the code file of the software product before the file is packaged, the version number is automatically generated without manual participation, the labor cost is saved, and the generation efficiency of the version number can be improved. In addition, the corresponding code files are different when the software product is subjected to version replacement each time, and the unique identifiers of the code files are also different, so that the fact that the version numbers cannot be repeated can be effectively ensured.
Drawings
FIG. 1 is a flow chart of a version number generation method provided by one embodiment of the present application;
FIG. 2 is a flowchart of a version number generation method according to another embodiment of the present application;
FIG. 3 is a schematic diagram of generating a version number provided by one embodiment of the present application;
FIG. 4 is a flowchart of a version number generation method according to another embodiment of the present application;
FIG. 5 is a schematic view of a folder provided in one embodiment of the application;
FIG. 6 is a schematic diagram of generating a version number provided by one embodiment of the present application;
FIG. 7 is a block diagram of a version number generation apparatus provided by one embodiment of the present application;
Fig. 8 is a block diagram illustrating a structure of a terminal according to an embodiment of the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the embodiments of the present application will be described in further detail with reference to the accompanying drawings.
According to the technical scheme provided by the embodiment of the application, the version number is generated according to the unique identifier of the code file of the software product before the file package of the software product, so that the automatic generation of the version number is realized, the manual participation is not needed, the labor cost is saved, and the generation efficiency of the version number can be improved. In addition, the corresponding code files are different when the software product is subjected to version replacement each time, and the unique identifiers of the code files are also different, so that the fact that the version numbers cannot be repeated can be effectively ensured.
According to the technical scheme provided by the embodiment of the application, the execution main body of each step is a terminal. The terminal has a file packaging function, for example, the terminal packages information about a code file of a target object written by a technician into a compressed file. In the embodiment of the application, in the file packaging process, the terminal automatically generates the version number of the target object.
Optionally, a code management tool is installed in the terminal, the code management tool and a code file of the target object are stored in the same folder, and an execution subject of each step may be the code management tool. In the embodiment of the present application, explanation will be given by taking an execution subject of each step as an example.
Referring to fig. 1, a flowchart of a version number generation method according to an embodiment of the present application is shown. The method comprises the following steps:
step 101, a first file identification of a code file of a target object is obtained.
The target object refers to a software product for which version changes exist. Target objects include, but are not limited to, plug-ins, applications, software drivers, and the like. In the embodiment of the application, only the target object is taken as an example for explanation. The first file identifies a code file for uniquely identifying the target object.
In one possible implementation, the first file identification is a unique identification code of the last commit record of the code file of the target object. Illustratively, the first file is identified as b7e625cf2d2d37122269.
In another possible implementation, the first file identification is a commit timestamp of a last commit record of the code file of the target object. Illustratively, the last commit record of the code file of the target object has a commit timestamp of 17 points 17 minutes 10/2020, and the first file is identified as 2010171738.
In yet another possible implementation, the first file identification is a combination of a unique identification code of the last commit record of the code file of the target object and a commit timestamp.
And the terminal acquires the first file identification when the version number of the target object needs to be generated. Optionally, the terminal obtains the first file identifier when the code file of the target object is subjected to file encapsulation.
Step 102, based on the first file identification, generating a version number of the target object.
In the embodiment of the application, the terminal automatically generates the version number of the target object based on the first file identification, manual setting by a technician is not needed, labor cost required for generating the version number is saved, and the generation efficiency of the version number is improved. In addition, the corresponding code files are different when the software product is subjected to version replacement each time, and the unique identifiers of the code files are also different, so that the fact that the version numbers cannot be repeated can be effectively ensured.
Optionally, the terminal directly determines the first file identifier as the version number of the target object.
Optionally, the terminal splices the first file identifier with the object identifier of the target object to obtain the version number of the target object.
Optionally, when the target object depends on the host software product, the terminal splices the first file identifier, the object identifier of the target object, and the product identifier of the host software product to obtain the version number of the target object.
And 103, packaging the object information of the target object to obtain a compressed file corresponding to the target object.
The object information of the target object contains the version number of the target object. In addition, the object information of the target object includes other information such as the name of the target object. When the target object depends on the host software product, the object information of the target object also includes a product identification of the host software product, such as a name of the host software product.
The compressed file corresponding to the target object is in a preset format, and the preset format is set by default by the terminal or is set by the user definition of the technician. Illustratively, the compressed file corresponding to the target object is a file with a suffix name of apz, or the compressed file corresponding to the target object is a file with a suffix name of zip, or the compressed file corresponding to the target object is a file with a suffix name of zar.
After obtaining the compressed file corresponding to the target object, the terminal uploads the compressed file corresponding to the target object to the server, and the subsequent server reads the object information of the target object from the compressed file, generates a unique identifier of the host software product, and then performs unique association with the plug-in version. When a technician issues a new version of the target object, the user terminal requests to acquire the new version of the target object from the server through the unique identification of the host software product.
In summary, according to the technical scheme provided by the embodiment of the application, the version number is generated according to the unique identifier of the code file of the software product before the software product is packaged, so that the version number is automatically generated, manual participation is not needed, labor cost is saved, and the generation efficiency of the version number can be improved. In addition, the corresponding code files are different when the software product is subjected to version replacement each time, and the unique identifiers of the code files are also different, so that the fact that the version numbers cannot be repeated can be effectively ensured.
Taking the target object as a plug-in, the plug-ins are divided into coupled plug-ins and uncoupled plug-ins. The uncoupled plugin is a plugin which does not need to depend on a host application program when the file is packaged, and the coupled plugin is a plugin which does not need to depend on the host application program when the file is packaged. The version number generation modes of the two types of plug-ins are different, and the version number generation modes of the two types of plug-ins are respectively explained below.
In one possible implementation, please refer to fig. 2, which illustrates a flowchart of a version number generation method according to an embodiment of the present application. The method comprises the following steps:
Step 201, a first file identification of a code file of a target object is obtained.
In the embodiment of the application, the target object is a non-coupling plug-in. Optionally, the folder storing the code file of the target object further includes a code management tool, and the terminal obtains the first file identifier through the code management tool.
In one possible implementation, the terminal obtains, as the first file identifier, a unique identifier of the last submitted record of the code file of the target object.
In another possible implementation, the terminal obtains, as the first file identifier, a commit timestamp of a last commit record of the code file of the target object.
In yet another possible implementation manner, the terminal obtains the unique identification code of the last submitted record of the code file of the target object and the submitted timestamp, and combines the unique identification code and the submitted timestamp to obtain the first file identification.
Step 202, obtaining an object identifier of a target object.
Object identification of a target object is used to uniquely identify the target object, such as the name of the target object. Optionally, the terminal obtains the object identifier of the target object through a code management tool.
And 203, splicing the object identifier of the target object and the first file identifier to obtain the version number of the target object.
And the terminal splices the characters included in the object identifier of the target object with the characters included in the first file identifier to obtain the version number of the target object.
Optionally, a preset symbol is used to connect the object identifier of the target object with the first file identifier, where the preset symbol is set by default by the terminal or set by a technician in a user-defined manner. Illustratively, the preset symbol is a connector "_". In one example, referring to fig. 3, the first file identifier is b7e625cf2d2d37122269, the object identifier of the target object (i.e., the name of the target object) is plug in1, and then the version number of the target object is plug in1_b7e625cf2d2d37122269.
It should be noted that, in the embodiment of the present application, the arrangement order of the object identifier of the target object and the first file identifier is not limited. In one possible implementation, the object identifier of the target object is preceded and the first file identifier is followed. In another possible implementation, the object identifier of the target object is followed by the first file identifier.
And 204, packaging the object information of the target object to obtain a compressed file corresponding to the target object.
The object information of the target object contains the version number of the target object.
In summary, according to the technical scheme provided by the embodiment of the application, for the target object independent of the host software product, the terminal splices the unique identifier of the code file of the target object with the object identifier of the target object to obtain the version number of the target object, so that the version number is automatically generated, manual participation is not needed, the labor cost is saved, and the generation efficiency of the version number can be improved. In addition, the corresponding code files are different when the software product is subjected to version replacement each time, and the unique identifiers of the code files are also different, so that the fact that the version numbers cannot be repeated can be effectively ensured.
Referring to fig. 4, a flowchart of a version number generation method according to an embodiment of the present application is shown. The method comprises the following steps:
Step 401, storing the code file of the target object and the code file of the hosting software product into the same folder.
When the target object depends on the hosting software product, the code files of the target object and the code files of the hosting application are stored in the same folder, which corresponds to a database, which may be located locally at the terminal or in a remote database. When the folder is opened, the terminal reads the code file from the database for viewing by the relevant technician.
Optionally, the folder further stores a code management tool, where the code management tool is configured to obtain the first file identifier and/or the second file identifier.
Referring in conjunction to FIG. 5, a schematic diagram of a folder provided by one embodiment of the present application is shown. The folder 51 includes code management tools 511, code files 512 for target objects, code files 513 for hosting software products.
Step 402, a first file identification of a code file of a target object is obtained.
The target object refers to a software product for which version changes exist. In the embodiment of the application, the target object is a coupling plug-in. Optionally, the folder storing the code file of the target object further includes a code management tool, and the terminal obtains the first file identifier through the code management tool.
In step 403, when the target object depends on the host software product, a second file identification of the code file of the host software product is obtained.
The second file identifies a code file for uniquely identifying the hosting software product. Optionally, the terminal obtains the object identifier of the target object through a code management tool.
In one possible implementation, the terminal obtains the unique identification code of the last submitted record of the code file of the host software product as the second file identification.
In another possible implementation, the terminal obtains a commit timestamp of a last commit record of the code file of the host software product as the second file identification.
In yet another possible implementation, the terminal obtains the unique identification code of the last commit record of the code file of the host software product and the commit timestamp, and combines the two to obtain the second file identification.
Step 404, obtaining an object identifier of the target object.
And step 405, splicing the object identifier of the target object, the first file identifier and the second file identifier to obtain the version number of the target object.
Step 406, file packaging is performed on the object information of the target object to obtain a compressed file corresponding to the target object, where the object information of the target object includes the version number of the target object.
The terminal splices the characters included in the object identification of the target object, the characters included in the first file identification and the characters included in the second file identification to obtain the version number of the target object.
Optionally, the object identifier of the target object, the first file identifier and the second file identifier are connected by using a preset symbol, and the preset symbol is set by default by the terminal or is set by a technician in a self-defining way. Illustratively, the preset symbol is a connector "_". In one example, referring to fig. 6, the first file is identified as b7e625cf2d2d37122269, the object identification of the target object (i.e., the name of the target object) is plugin2, the second file is identified as 7c78b16109a280dad80e, and the version number of the target object is plugin 2b 7e625cf2d 371222697c78b16109a280dad80e.
It should be noted that, in the embodiment of the present application, the arrangement sequence of the object identifier, the first file identifier, and the second file identifier of the target object is not limited.
In summary, according to the technical scheme provided by the embodiment of the application, for the target object depending on the host software product, the terminal splices the unique identifier of the code file of the target object, the unique identifier of the code file of the host software product and the object identifier of the target object to obtain the version number of the target object, thereby realizing automatic generation of the version number, saving labor cost and improving the generation efficiency of the version number. In addition, the corresponding code files are different when the software product is subjected to version replacement each time, and the unique identifiers of the code files are also different, so that the fact that the version numbers cannot be repeated can be effectively ensured.
The following are device embodiments of the application, for which reference is made to the technical details disclosed in the method embodiments described above, for parts not specifically stated in the device embodiments.
Referring to fig. 7, a block diagram of a version number generating apparatus according to an exemplary embodiment of the present application is shown. The version number generating means may be implemented as all or part of the terminal by software, hardware or a combination of both. The version number generation device comprises:
The identifier obtaining module 701 is configured to obtain a first file identifier of a code file of a target object, where the target object is a software product with a version change.
And the version number generation module 702 is configured to generate a version number of the target object based on the first file identifier.
The file generating module 703 is configured to perform file encapsulation on object information of the target object, so as to obtain a compressed file corresponding to the target object, where the object information of the target object includes a version number of the target object.
In summary, according to the technical scheme provided by the embodiment of the application, the version number is generated according to the unique identifier of the code file of the software product before the software product is packaged, so that the version number is automatically generated, manual participation is not needed, labor cost is saved, and the generation efficiency of the version number can be improved. In addition, the corresponding code files are different when the software product is subjected to version replacement each time, and the unique identifiers of the code files are also different, so that the fact that the version numbers cannot be repeated can be effectively ensured.
In an alternative embodiment provided based on the embodiment shown in fig. 7, the version number generating module 702 is configured to:
obtaining an object identifier of the target object;
And splicing the object identifier of the target object and the first file identifier to obtain the version number of the target object.
In an alternative embodiment provided based on the embodiment shown in fig. 7, the version number generating module 702 is configured to:
when the target object depends on a host software product, acquiring a second file identification of a code file of the host software product;
obtaining an object identifier of the target object;
And splicing the object identifier of the target object, the first file identifier and the second file identifier to obtain the version number of the target object.
Optionally, the version number generating module 702 is configured to:
Acquiring a unique identification code of a last submitted record of a code file of the host software product as the second file identification; and/or the number of the groups of groups,
And acquiring a commit time stamp of the last commit record of the code file of the host software product as the second file identifier.
In an alternative embodiment provided based on the embodiment shown in fig. 7, the identifier obtaining module 701 is configured to:
Acquiring a unique identification code of a last submitted record of a code file of the target object as the first file identification; and/or the number of the groups of groups,
And acquiring a commit time stamp of the last commit record of the code file of the target object as the first file identifier.
In an alternative embodiment provided based on the embodiment shown in fig. 7, the apparatus further comprises: a file storage module (not shown in fig. 7).
And the file storage module is used for storing the code file of the target object and the code file of the host software product into the same folder.
Optionally, the folder further stores a code management tool, where the code management tool is configured to obtain the first file identifier and/or the second file identifier.
It should be noted that, when the apparatus provided in the foregoing embodiment performs the functions thereof, only the division of the foregoing functional modules is used as an example, in practical application, the foregoing functional allocation may be performed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules, so as to perform all or part of the functions described above. In addition, the apparatus and the method embodiments provided in the foregoing embodiments belong to the same concept, and specific implementation processes of the apparatus and the method embodiments are detailed in the method embodiments and are not repeated herein.
Fig. 8 shows a block diagram of a terminal 800 according to an exemplary embodiment of the present application. The terminal 800 may be: smart phones, tablet computers, MP3 players, MP4 players, notebook computers or desktop computers. Terminal 800 may also be referred to by other names of user devices, portable terminals, laptop terminals, desktop terminals, and the like.
In general, the terminal 800 includes: a processor 801 and a memory 802.
Processor 801 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and the like. The processor 801 may be implemented in at least one hardware form of Digital Signal Processing (DSP), field-Programmable gate array (fieldprogrammable GATE ARRAY, FPGA), programmable logic array (Programmable Logic Array, PLA). The processor 801 may also include a main processor, which is a processor for processing data in an awake state, also referred to as a central processor (Central Processing Unit, CPU), and a coprocessor; a coprocessor is a low-power processor for processing data in a standby state. In some embodiments, the processor 801 may integrate with an image processor (Graphics Processing Unit, GPU) that is responsible for rendering and rendering of the content that the display screen is required to display.
Memory 802 may include one or more computer-readable storage media, which may be non-transitory. Memory 802 may also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in memory 802 is used to store a computer program for execution by processor 801 to implement the version number generation method provided by the method embodiments of the present application.
In some embodiments, the terminal 800 may further optionally include: a peripheral interface 803, and at least one peripheral. The processor 801, the memory 802, and the peripheral interface 803 may be connected by a bus or signal line. Individual peripheral devices may be connected to the peripheral device interface 803 by buses, signal lines, or a circuit board. Specifically, the peripheral device includes: at least one of radio frequency circuitry 804, a touch display 805, a camera assembly 806, audio circuitry 807, a positioning assembly 808, and a power supply 809.
Peripheral interface 803 may be used to connect at least one Input/Output (I/O) related peripheral device to processor 801 and memory 802. In some embodiments, processor 801, memory 802, and peripheral interface 803 are integrated on the same chip or circuit board; in some other embodiments, either or both of the processor 801, the memory 802, and the peripheral interface 803 may be implemented on separate chips or circuit boards, which is not limited in this embodiment.
The Radio Frequency circuit 804 is configured to receive and transmit Radio Frequency (RF) signals, also known as electromagnetic signals. The radio frequency circuit 804 communicates with a communication network and other communication devices via electromagnetic signals. The radio frequency circuit 804 converts an electrical signal into an electromagnetic signal for transmission, or converts a received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 804 includes: antenna systems, RF transceivers, one or more amplifiers, tuners, oscillators, digital signal processors, codec chipsets, subscriber identity module cards, and so forth. The radio frequency circuitry 804 may communicate with other terminals via at least one wireless communication protocol. The wireless communication protocol includes, but is not limited to: the world wide web, metropolitan area networks, intranets, generation mobile communication networks (2G, 3G, 4G, and 5G), wireless local area networks, and/or wireless fidelity (WIRELESS FIDELITY, WIFI) networks. In some embodiments, the radio frequency circuit 804 may also include a circuit related to Near Field Communication (NFC), which is not limited by the present application.
The display 805 is used to display a User Interface (UI). The UI may include graphics, text, icons, video, and any combination thereof. When the display 805 is a touch display, the display 805 also has the ability to collect touch signals at or above the surface of the display 805. The touch signal may be input as a control signal to the processor 801 for processing. At this time, the display 805 may also be used to provide virtual buttons and/or virtual keyboards, also referred to as soft buttons and/or soft keyboards. In some embodiments, the display 805 may be one, providing a front panel of the terminal 800; in other embodiments, the display 805 may be at least two, respectively disposed on different surfaces of the terminal 800 or in a folded design; in still other embodiments, the display 805 may be a flexible display disposed on a curved surface or a folded surface of the terminal 800. Even more, the display 805 may be arranged in an irregular pattern other than rectangular, i.e., a shaped screen. The display 805 may be made of a Liquid crystal display (Liquid CRYSTAL DISPLAY, LCD), an Organic Light-Emitting Diode (OLED), or other materials.
The camera assembly 806 is used to capture images or video. Optionally, the camera assembly 806 includes a front camera and a rear camera. Typically, the front camera is disposed on the front panel of the terminal and the rear camera is disposed on the rear surface of the terminal. In some embodiments, the at least two rear cameras are any one of a main camera, a depth camera, a wide-angle camera and a tele camera, so as to realize that the main camera and the depth camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize a panoramic shooting and Virtual Reality (VR) shooting function or other fusion shooting functions. In some embodiments, the camera assembly 806 may also include a flash. The flash lamp can be a single-color temperature flash lamp or a double-color temperature flash lamp. The dual-color temperature flash lamp refers to a combination of a warm light flash lamp and a cold light flash lamp, and can be used for light compensation under different color temperatures.
Audio circuitry 807 may include a microphone and a speaker. The microphone is used for collecting sound waves of users and the environment, converting the sound waves into electric signals, inputting the electric signals to the processor 801 for processing, or inputting the electric signals to the radio frequency circuit 804 for voice communication. For stereo acquisition or noise reduction purposes, a plurality of microphones may be respectively disposed at different portions of the terminal 800. The microphone may also be an array microphone or an omni-directional pickup microphone. The speaker is used to convert electrical signals from the processor 801 or the radio frequency circuit 804 into sound waves. The speaker may be a conventional thin film speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, not only the electric signal can be converted into a sound wave audible to humans, but also the electric signal can be converted into a sound wave inaudible to humans for ranging and other purposes. In some embodiments, audio circuit 807 may also include a headphone jack.
The location component 808 is utilized to locate the current geographic location of the terminal 800 to enable navigation or location based services (Location Based Service, LBS). The positioning component 808 may be a positioning component based on the U.S. global positioning system (Global Positioning System, GPS), the chinese beidou system, or the russian galileo system.
A power supply 809 is used to power the various components in the terminal 800. The power supply 809 may be an alternating current, direct current, disposable battery, or rechargeable battery. When the power supply 809 includes a rechargeable battery, the rechargeable battery may be a wired rechargeable battery or a wireless rechargeable battery. The wired rechargeable battery is a battery charged through a wired line, and the wireless rechargeable battery is a battery charged through a wireless coil. The rechargeable battery may also be used to support fast charge technology.
In some embodiments, the terminal 800 also includes one or more sensors 810. The one or more sensors 810 include, but are not limited to: acceleration sensor 811, gyroscope sensor 812, pressure sensor 813, fingerprint sensor 814, optical sensor 815, and proximity sensor 816.
The acceleration sensor 811 can detect the magnitudes of accelerations on three coordinate axes of the coordinate system established with the terminal 800. For example, the acceleration sensor 811 may be used to detect components of gravitational acceleration in three coordinate axes. The processor 801 may control the touch display screen 805 to display a user interface in a landscape view or a portrait view according to the gravitational acceleration signal acquired by the acceleration sensor 811. Acceleration sensor 811 may also be used for the acquisition of motion data of a game or user.
The gyro sensor 812 may detect a body direction and a rotation angle of the terminal 800, and the gyro sensor 812 may collect a 3D motion of the user to the terminal 800 in cooperation with the acceleration sensor 811. The processor 801 may implement the following functions based on the data collected by the gyro sensor 812: motion sensing (e.g., changing UI according to a tilting operation by a user), image stabilization at shooting, game control, and inertial navigation.
The pressure sensor 813 may be disposed at a side frame of the terminal 800 and/or at a lower layer of the touch display 805. When the pressure sensor 813 is disposed on a side frame of the terminal 800, a grip signal of the terminal 800 by a user may be detected, and the processor 801 performs left-right hand recognition or shortcut operation according to the grip signal collected by the pressure sensor 813. When the pressure sensor 813 is disposed at the lower layer of the touch display screen 805, the processor 801 controls the operability control on the UI interface according to the pressure operation of the user on the touch display screen 805. The operability controls include at least one of a button control, a scroll bar control, an icon control, and a menu control.
The fingerprint sensor 814 is used to collect a fingerprint of a user, and the processor 801 identifies the identity of the user based on the fingerprint collected by the fingerprint sensor 814, or the fingerprint sensor 814 identifies the identity of the user based on the collected fingerprint. Upon recognizing that the user's identity is a trusted identity, the processor 801 authorizes the user to perform relevant sensitive operations including unlocking the screen, viewing encrypted information, downloading software, paying for and changing settings, etc. The fingerprint sensor 814 may be provided on the front, back, or side of the terminal 800. When a physical key or vendor Logo is provided on the terminal 800, the fingerprint sensor 814 may be integrated with the physical key or vendor Logo.
The optical sensor 815 is used to collect the ambient light intensity. In one embodiment, the processor 801 may control the display brightness of the touch display screen 805 based on the intensity of ambient light collected by the optical sensor 815. Specifically, when the intensity of the ambient light is high, the display brightness of the touch display screen 805 is turned up; when the ambient light intensity is low, the display brightness of the touch display screen 805 is turned down. In another embodiment, the processor 801 may also dynamically adjust the shooting parameters of the camera module 806 based on the ambient light intensity collected by the optical sensor 815.
A proximity sensor 816, also referred to as a distance sensor, is typically provided on the front panel of the terminal 800. The proximity sensor 816 is used to collect the distance between the user and the front of the terminal 800. In one embodiment, when the proximity sensor 816 detects that the distance between the user and the front of the terminal 800 gradually decreases, the processor 801 controls the touch display 805 to switch from the bright screen state to the off screen state; when the proximity sensor 816 detects that the distance between the user and the front surface of the terminal 800 gradually increases, the processor 801 controls the touch display 805 to switch from the off-screen state to the on-screen state.
Those skilled in the art will appreciate that the structure shown in fig. 8 is not limiting and that more or fewer components than shown may be included or certain components may be combined or a different arrangement of components may be employed.
In an exemplary embodiment, there is also provided a computer-readable storage medium having stored therein a computer program loaded and executed by a processor of a terminal to implement the version number generation method in the above-described method embodiment.
Alternatively, the above-mentioned computer readable storage medium may be a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic tape, a floppy disk, an optical data storage device, or the like.
In an exemplary embodiment, there is also provided a computer program product including computer instructions stored in a computer-readable storage medium, the computer instructions being read from the computer-readable storage medium by a processor of a computer device, the computer instructions being executed by the processor to cause the computer device to perform the version number generation method provided in the above aspect or various alternative implementations of the aspect.
The foregoing description of the exemplary embodiments of the application is not intended to limit the application to the particular embodiments disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the application.
Claims (8)
1. A version number generation method, the method comprising:
acquiring a first file identification of a code file of a target object, wherein the target object refers to a plug-in with version replacement;
Acquiring an object identification of the target object under the condition that the target object is a non-coupling plug-in; splicing the object identifier of the target object and the first file identifier to obtain the version number of the target object, wherein the uncoupled plug-in is a plug-in which does not need to rely on a host software product when the file is packaged;
acquiring a second file identification of the code file of the host software product under the condition that the target object is a coupling plug-in; obtaining an object identifier of the target object; splicing the object identifier of the target object, the first file identifier and the second file identifier to obtain the version number of the target object, wherein the coupling plug-in is a plug-in which depends on the host software product when the file is packaged;
And encapsulating the object information of the target object to obtain a compressed file corresponding to the target object, wherein the object information of the target object comprises the version number of the target object.
2. The method of claim 1, wherein the obtaining a second file identification of the code file of the host software product comprises:
Acquiring a unique identification code of a last submitted record of a code file of the host software product as the second file identification; and/or the number of the groups of groups,
And acquiring a commit time stamp of the last commit record of the code file of the host software product as the second file identifier.
3. The method according to claim 1 or 2, wherein the obtaining the first file identification of the code file of the target object comprises:
Acquiring a unique identification code of a last submitted record of a code file of the target object as the first file identification; and/or the number of the groups of groups,
And acquiring a commit time stamp of the last commit record of the code file of the target object as the first file identifier.
4. The method according to claim 1 or 2, wherein, in the case that the target object is the coupling plug-in, before the obtaining the first file identification of the code file of the target object, further comprises:
and storing the code file of the target object and the code file of the host software product into the same folder.
5. The method of claim 4, wherein the folder further stores a code management tool for obtaining the first file identification and/or the second file identification.
6. A version number generation apparatus, the apparatus comprising:
the device comprises an identifier acquisition module, a storage module and a storage module, wherein the identifier acquisition module is used for acquiring a first file identifier of a code file of a target object, and the target object refers to a plug-in with version replacement;
The version number generation module is used for acquiring an object identifier of the target object under the condition that the target object is a non-coupling plug-in; splicing the object identifier of the target object and the first file identifier to obtain the version number of the target object, wherein the uncoupled plug-in is a plug-in which does not need to rely on a host software product when the file is packaged; acquiring a second file identification of the code file of the host software product under the condition that the target object is a coupling plug-in; obtaining an object identifier of the target object; splicing the object identifier of the target object, the first file identifier and the second file identifier to obtain the version number of the target object, wherein the coupling plug-in is a plug-in which depends on the host software product when the file is packaged;
And the file generation module is used for carrying out file encapsulation on the object information of the target object to obtain a compressed file corresponding to the target object, wherein the object information of the target object comprises the version number of the target object.
7. A terminal comprising a processor and a memory, the memory storing a computer program, the computer program being loaded by the processor and executing the version number generation method according to any one of claims 1 to 5.
8. A computer-readable storage medium, in which a computer program is stored, the computer program being loaded and executed by a processor to implement the version number generation method of any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011219290.0A CN112256320B (en) | 2020-11-04 | 2020-11-04 | Version number generation method, device, terminal and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011219290.0A CN112256320B (en) | 2020-11-04 | 2020-11-04 | Version number generation method, device, terminal and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112256320A CN112256320A (en) | 2021-01-22 |
| CN112256320B true CN112256320B (en) | 2024-05-14 |
Family
ID=74268909
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011219290.0A Active CN112256320B (en) | 2020-11-04 | 2020-11-04 | Version number generation method, device, terminal and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112256320B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112783533A (en) * | 2021-02-03 | 2021-05-11 | 北京达佳互联信息技术有限公司 | Version information updating method, version information updating device, terminal and storage medium |
| CN112817616B (en) * | 2021-03-02 | 2022-12-09 | 福州汇思博信息技术有限公司 | PKG file management method and terminal |
| CN114461614B (en) * | 2022-04-12 | 2022-06-28 | 北京安华金和科技有限公司 | Sensitive data identification processing method and system |
| CN115599437B (en) * | 2022-10-26 | 2023-10-20 | 北京领雁科技股份有限公司 | Software version processing method and device, electronic equipment and storage medium |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101359293A (en) * | 2008-09-04 | 2009-02-04 | 腾讯科技（深圳）有限公司 | Method and apparatus for making part update pack |
| CN102043612A (en) * | 2009-10-10 | 2011-05-04 | 英业达股份有限公司 | Version number maintenance system and maintenance method thereof |
| CN103123583A (en) * | 2012-12-19 | 2013-05-29 | 深圳市共进电子股份有限公司 | Realizing method for automatically recording software version number |
| CN109032631A (en) * | 2018-07-12 | 2018-12-18 | 腾讯科技（深圳）有限公司 | Application program service packs acquisition methods, device, computer equipment and storage medium |
| CN109086071A (en) * | 2018-08-22 | 2018-12-25 | 平安普惠企业管理有限公司 | A kind of method and server of management software version information |
| CN110348219A (en) * | 2019-06-13 | 2019-10-18 | 晶晨半导体(上海)股份有限公司 | Version comparison method, system, computer equipment and readable storage medium storing program for executing |
| CN110442377A (en) * | 2019-08-13 | 2019-11-12 | 网易（杭州）网络有限公司 | Service packs generation method, using update method, device and electronic equipment |
| CN110457335A (en) * | 2019-08-09 | 2019-11-15 | 重庆紫光华山智安科技有限公司 | A kind of identity generation method, device and computer readable storage medium |
| CN110674518A (en) * | 2019-09-26 | 2020-01-10 | 海南新软软件有限公司 | Equipment identification information generation method, device and system |
| CN111447248A (en) * | 2019-01-16 | 2020-07-24 | 网宿科技股份有限公司 | File transmission method and device |
| CN111638905A (en) * | 2020-05-12 | 2020-09-08 | 中信百信银行股份有限公司 | Version number generation method and device, electronic equipment and readable storage medium |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080005195A1 (en) * | 2006-06-30 | 2008-01-03 | Microsoft Corporation | Versioning synchronization for mass p2p file sharing |
| US8645934B2 (en) * | 2010-05-06 | 2014-02-04 | International Business Machines Corporation | Simultaneous compiler binary optimizations |
| CN108228894B (en) * | 2018-02-05 | 2023-07-04 | 腾讯科技（深圳）有限公司 | Method, device and terminal for checking recently used files |
-
2020
- 2020-11-04 CN CN202011219290.0A patent/CN112256320B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101359293A (en) * | 2008-09-04 | 2009-02-04 | 腾讯科技（深圳）有限公司 | Method and apparatus for making part update pack |
| CN102043612A (en) * | 2009-10-10 | 2011-05-04 | 英业达股份有限公司 | Version number maintenance system and maintenance method thereof |
| CN103123583A (en) * | 2012-12-19 | 2013-05-29 | 深圳市共进电子股份有限公司 | Realizing method for automatically recording software version number |
| CN109032631A (en) * | 2018-07-12 | 2018-12-18 | 腾讯科技（深圳）有限公司 | Application program service packs acquisition methods, device, computer equipment and storage medium |
| CN109086071A (en) * | 2018-08-22 | 2018-12-25 | 平安普惠企业管理有限公司 | A kind of method and server of management software version information |
| CN111447248A (en) * | 2019-01-16 | 2020-07-24 | 网宿科技股份有限公司 | File transmission method and device |
| CN110348219A (en) * | 2019-06-13 | 2019-10-18 | 晶晨半导体(上海)股份有限公司 | Version comparison method, system, computer equipment and readable storage medium storing program for executing |
| CN110457335A (en) * | 2019-08-09 | 2019-11-15 | 重庆紫光华山智安科技有限公司 | A kind of identity generation method, device and computer readable storage medium |
| CN110442377A (en) * | 2019-08-13 | 2019-11-12 | 网易（杭州）网络有限公司 | Service packs generation method, using update method, device and electronic equipment |
| CN110674518A (en) * | 2019-09-26 | 2020-01-10 | 海南新软软件有限公司 | Equipment identification information generation method, device and system |
| CN111638905A (en) * | 2020-05-12 | 2020-09-08 | 中信百信银行股份有限公司 | Version number generation method and device, electronic equipment and readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112256320A (en) | 2021-01-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112256320B (en) | Version number generation method, device, terminal and storage medium | |
| CN109101213B (en) | Method, device and storage medium for controlling sound card to transmit audio | |
| CN113204298B (en) | Method and device for displaying release progress, electronic equipment and storage medium | |
| CN111949680A (en) | Data processing method and device, computer equipment and storage medium | |
| CN108848492B (en) | Method, device, terminal and storage medium for starting user identity identification card | |
| CN110677713B (en) | Video image processing method and device and storage medium | |
| CN109783176B (en) | Page switching method and device | |
| CN111192072A (en) | User grouping method and device and storage medium | |
| CN112612539B (en) | Data model unloading method and device, electronic equipment and storage medium | |
| CN110825465B (en) | Log data processing method and device, electronic equipment and storage medium | |
| CN110737692A (en) | data retrieval method, index database establishment method and device | |
| CN117215990A (en) | Inter-core communication method and device of multi-core chip and multi-core chip | |
| CN110971840A (en) | Video mapping method and device, computer equipment and storage medium | |
| CN113051015B (en) | Page rendering method and device, electronic equipment and storage medium | |
| CN113408989B (en) | Automobile data comparison method and device and computer storage medium | |
| CN112612540B (en) | Data model configuration method, device, electronic equipment and storage medium | |
| CN112597417B (en) | Page updating method and device, electronic equipment and storage medium | |
| CN114595019A (en) | Theme setting method, device and equipment of application program and storage medium | |
| CN113076452A (en) | Application classification method, device, equipment and computer readable storage medium | |
| CN110764808B (en) | Client upgrade detection method, device and computer readable storage medium | |
| CN111275561B (en) | Method, device, computer equipment and storage medium for acquiring association relation | |
| CN111522576B (en) | Application management method, device, equipment and computer storage medium | |
| CN111414563B (en) | Webpage interaction method, device, computer equipment and storage medium | |
| CN114827061B (en) | Notification message display method, notification message display device, terminal and storage medium | |
| CN113746831B (en) | Authority verification method and device and storage medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |