CN112256320A - Version number generation method, device, terminal and storage medium - Google Patents
Version number generation method, device, terminal and storage medium Download PDFInfo
- Publication number
- CN112256320A CN112256320A CN202011219290.0A CN202011219290A CN112256320A CN 112256320 A CN112256320 A CN 112256320A CN 202011219290 A CN202011219290 A CN 202011219290A CN 112256320 A CN112256320 A CN 112256320A
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 41
- 238000005538 encapsulation Methods 0.000 claims abstract description 15
- 238000004590 computer program Methods 0.000 claims description 12
- 230000001419 dependent effect Effects 0.000 claims description 2
- 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 9
- 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
- 230000008569 process Effects 0.000 description 3
- 239000000919 ceramic Substances 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 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
- 230000004927 fusion Effects 0.000 description 1
- 230000001788 irregular Effects 0.000 description 1
- 239000004973 liquid crystal related substance 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
- 238000004806 packaging method and process Methods 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 230000006641 stabilisation Effects 0.000 description 1
- 238000011105 stabilization Methods 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/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
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 identifier of a code file of a target object, wherein the target object refers to a software product with a version replaced; generating a version number of the target object based on the first file identifier; and performing 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. 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 subjected to file encapsulation, 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.
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
At present, software products released by application program manufacturers usually have version replacement so as to achieve the purposes of increasing functions, repairing bugs and the like.
When a software product is subjected to a version change, the version number is generally used to identify the version of the software product. In the related art, before a software product is packaged in a file, a technician manually selects an unused version number. For example, software product A has a version number of 1.0, 2.0, and so on.
In the related technology, the generation process of the version number needs manual participation, and the generation efficiency of 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 terminal and a storage medium, and generation efficiency of the version number is improved. The technical scheme is as follows:
in one aspect, an embodiment of the present application provides a version number generation method, where the method includes:
acquiring a first file identifier of a code file of a target object, wherein the target object is a software product with a version replaced;
generating a version number of the target object based on the first file identifier;
and performing 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 another aspect, an embodiment of the present application provides a version number generation apparatus, where the apparatus includes:
the identification acquisition module is used for acquiring a first file identification of a code file of a target object, wherein the target object is a software product with a version replacement;
the version number generation module is used for generating the version number of the target object based on the first file identifier;
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 an aspect.
In yet another aspect, the present application provides a computer-readable storage medium, in which a computer program is stored, and the computer program is loaded and executed by a processor to implement the version number generation method according to an aspect.
In yet another aspect, embodiments of the present application provide a computer program product, the computer program product or computer program including 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 executes the version number generation method.
The technical scheme provided by the embodiment of the application can bring the beneficial effects of at least comprising:
the version number is generated according to the unique identification 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, the labor cost is saved, and the generation efficiency of the version number can be improved. In addition, because the corresponding code files of the software product are different when the version is replaced every time, and the unique identifiers of the code files are different, the version number can be effectively ensured not to be repeated.
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 flow chart of a version number generation method provided by 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 provided by another embodiment of the present application;
FIG. 5 is a schematic view of a folder provided by one embodiment of the present 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 in an embodiment of the present application;
fig. 8 is a block diagram of a terminal according to an embodiment of the present application.
Detailed Description
To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below 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 software product is subjected to file encapsulation, 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, because the corresponding code files of the software product are different when the version is replaced every time, and the unique identifiers of the code files are different, the version number can be effectively ensured not to be repeated.
According to the technical scheme provided by the embodiment of the application, the execution main body of each step is the terminal. The terminal has a file encapsulation function, for example, the terminal encapsulates information related to a code file of a target object written by a technician into a compressed file. In the embodiment of the application, in the process of packaging the file, the terminal automatically generates the version number of the target object.
Alternatively, the terminal is installed with a code management tool, the code management tool and the code file of the target object are stored in the same folder, and the execution subject of each step may also be the code management tool. In the embodiments of the present application, only the main body of execution of each step is taken as an example for explanation.
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:
Target objects refer to software products for which version replacement exists. Target objects include, without limitation, plug-ins, applications, software drivers, and the like. In the embodiment of the present 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 a last-submitted record of the code file of the target object. Illustratively, the first file is identified as b7e625cf2d2d 37122269.
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 10/17/2020 for 17 o' clock 38 minutes 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 a last commit record of the code file of the target object and a commit timestamp.
And the terminal acquires the first file identifier when the version number of the target object needs to be generated. Optionally, the terminal obtains the first file identifier when performing file encapsulation on the code file of the target object.
And 102, generating a version number of the target object based on the first file identifier.
In the embodiment of the application, the terminal automatically generates the version number of the target object based on the first file identifier without manual setting by technical personnel, so that the labor cost for generating the version number is saved, and the generation efficiency of the version number is improved. In addition, because the corresponding code files of the software product are different when the version is replaced every time, and the unique identifiers of the code files are different, the version number can be effectively ensured not to be repeated.
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 and 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, performing file encapsulation on 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 is dependent on the host software product, the object information of the target object also includes a product identification of the host software product, such as the 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 a default of a terminal or is set by a technician in a self-defined mode. 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.
And after the terminal obtains the compressed file corresponding to the target object, uploading the compressed file corresponding to the target object to the server, reading the object information of the target object from the compressed file by the subsequent server, generating the unique identifier of the host software product, and then performing unique association with the plug-in version in the unique identifier. When the technician releases the target object of the new version, the user terminal requests to acquire the target object of the new version from the server through the unique identifier of the host software product.
To sum up, 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 subjected to file encapsulation, 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, because the corresponding code files of the software product are different when the version is replaced every time, and the unique identifiers of the code files are different, the version number can be effectively ensured not to be repeated.
Taking the target object as an example of a plug-in, the plug-ins are divided into coupled plug-ins and uncoupled plug-ins. The coupled plug-in is a plug-in which does not need to depend on the host application program when the file is packaged, and the uncoupled plug-in is a plug-in which does need to depend on the host application program when the file is packaged. The generation modes of the version numbers of the two types of plug-ins are different, and the generation modes of the version numbers of the two types of plug-ins are explained below respectively.
In one possible implementation, please refer to fig. 2, which shows a flowchart of a version number generation method provided in an embodiment of the present application. The method comprises the following steps:
In the embodiment of the application, the target object is an uncoupled plug-in. Optionally, the folder in which the code file of the target object is stored further includes a code management tool, and the terminal obtains the first file identifier through the code management tool.
In one possible implementation manner, the terminal acquires the unique identification code of the last submission record of the code file of the target object as the first file identifier.
In another possible implementation manner, the terminal obtains a commit timestamp of a last commit record of the code file of the target object as the first file identifier.
In another possible implementation manner, the terminal obtains the unique identification code of the last submission record of the code file of the target object and the submission timestamp, and combines the unique identification code and the submission timestamp to obtain the first file identifier.
The object identification of the 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 the terminal splices the characters included by the object identifier of the target object with the characters included by the first file identifier to obtain the version number of the target object.
Optionally, the object identifier of the target object is connected to the first file identifier by using a preset symbol, where the preset symbol is set by a default of the terminal, or set by a technician in a self-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 plugin1, and the version number of the target object is plugin1_ b7e625cf2d2d 37122269.
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 before and the first file identifier is after. In another possible implementation, the object identification of the target object is subsequent and the first file identification is previous.
And step 204, performing file encapsulation on 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.
To sum up, according to the technical scheme provided by the embodiment of the application, for a target object independent of a 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, because the corresponding code files of the software product are different when the version is replaced every time, and the unique identifiers of the code files are different, the version number can be effectively ensured not to be repeated.
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 host software product in the same folder.
When the target object depends on the host software product, the code file of the target object and the code file of the host application program are stored in the same folder, the folder corresponds to a database, and the database can be arranged in the local terminal or the remote database. When the folder is opened, the terminal reads the code file from the database for viewing by the associated technician.
Optionally, the folder further stores a code management tool, and the code management tool is configured to obtain the first file identifier and/or the second file identifier.
Referring collectively to FIG. 5, a diagram of a folder provided by one embodiment of the present application is shown. The folder 51 includes a code management tool 511, a code file 512 for the target object, and a code file 513 for the host software product.
Target objects refer to software products for which version replacement exists. In the embodiment of the application, the target object is a coupling plug-in. Optionally, the folder in which the code file of the target object is stored 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 identifier of the code file of the host software product is obtained.
The second file identifies a code file that uniquely identifies the host software product. Optionally, the terminal obtains the object identifier of the target object through a code management tool.
In one possible implementation manner, the terminal acquires the unique identification code of the last submission record of the code file of the host software product as the second file identification.
In another possible implementation manner, the terminal obtains a submission timestamp of a last submission record of the code file of the host software product as the second file identifier.
In another possible implementation manner, the terminal obtains the unique identification code of the last submission record of the code file of the host software product and the submission timestamp, and combines the unique identification code and the submission timestamp to obtain the second file identifier.
And the terminal splices the characters included by the object identifier of the target object, the characters included by the first file identifier and the characters included by the second file identifier to obtain the version number of the target object.
Optionally, the object identifier, the first file identifier, and the second file identifier of the target object are connected by a preset symbol, where the preset symbol is set by a default of a terminal, or set by a technician in a self-defined manner. 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 plugin2_ b7e625cf2d2d371222697c 16109a280dad80 e.
It should be noted that, in the embodiment of the present application, the order of the object identifier, the first file identifier, and the second file identifier of the target object is not limited.
To sum up, 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, 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, because the corresponding code files of the software product are different when the version is replaced every time, and the unique identifiers of the code files are different, the version number can be effectively ensured not to be repeated.
In the following, embodiments of the apparatus of the present application are described, and for portions of the embodiments of the apparatus not described in detail, reference may be made to technical details disclosed in the above-mentioned method embodiments.
Referring to fig. 7, a block diagram of a version number generation apparatus provided in an exemplary embodiment of the present application is shown. The version number generation 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 replacement.
A version number generating module 702, 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 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 a version number of the target object.
To sum up, 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 subjected to file encapsulation, 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, because the corresponding code files of the software product are different when the version is replaced every time, and the unique identifiers of the code files are different, the version number can be effectively ensured not to be repeated.
In an optional embodiment provided based on the embodiment shown in fig. 7, the version number generating module 702 is configured to:
acquiring 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 optional 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 identifier of a code file of the host software product;
acquiring 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 the last submission record of the code file of the host software product as the second file identifier; and/or the presence of a gas in the gas,
and acquiring a submission timestamp of the last submission record of the code file of the host software product as the second file identifier.
In an optional embodiment provided based on the embodiment shown in fig. 7, the identifier obtaining module 701 is configured to:
acquiring a unique identification code of the last submitted record of the code file of the target object as the first file identifier; and/or the presence of a gas in the gas,
and acquiring a submission timestamp of the last submission 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, and 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 implements the functions thereof, only the division of the functional modules is illustrated, and in practical applications, the functions may be distributed by different functional modules according to needs, that is, the internal structure of the apparatus may be divided into different functional modules to implement all or part of the functions described above. In addition, the apparatus and method embodiments provided by the above embodiments belong to the same concept, and specific implementation processes thereof are described in the method embodiments for details, which are not described herein again.
Fig. 8 shows a block diagram of a terminal 800 according to an exemplary embodiment of the present application. The terminal 800 may be: a smartphone, a tablet, an MP3 player, an MP4 player, a laptop, or a desktop computer. The terminal 800 may also be referred to by other names such as user equipment, portable terminal, laptop terminal, desktop terminal, etc.
In general, the terminal 800 includes: a processor 801 and a memory 802.
The processor 801 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and so forth. The processor 801 may be implemented in at least one hardware form of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). The processor 801 may also include a main processor and a coprocessor, where the main processor is a processor for Processing data in an awake state, and is also called a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor 801 may be integrated with a Graphics Processing Unit (GPU) which is responsible for rendering and drawing the content required to be displayed on the display screen.
In some embodiments, the terminal 800 may further include: a peripheral interface 803 and at least one peripheral. The processor 801, memory 802 and peripheral interface 803 may be connected by bus or signal lines. Various peripheral devices may be connected to peripheral interface 803 by a bus, signal line, or circuit board. Specifically, the peripheral device includes: at least one of a radio frequency circuit 804, a touch screen display 805, a camera assembly 806, an audio circuit 807, a positioning assembly 808, and a power supply 809.
The peripheral interface 803 may be used to connect at least one Input/Output (I/O) related peripheral to the processor 801 and the memory 802. In some embodiments, the processor 801, memory 802, and peripheral interface 803 are integrated on the same chip or circuit board; in some other embodiments, any one or two of the processor 801, the memory 802, and the peripheral interface 803 may be implemented on separate chips or circuit boards, which are not limited by this embodiment.
The Radio Frequency circuit 804 is used for receiving and transmitting Radio Frequency (RF) signals, also called electromagnetic signals. The radio frequency circuitry 804 communicates with communication networks and other communication devices via electromagnetic signals. The rf circuit 804 converts an electrical signal into an electromagnetic signal to be transmitted, or converts a received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 804 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a subscriber identity module card, and so forth. The radio frequency circuit 804 may communicate with other terminals via at least one wireless communication protocol. The wireless communication protocols include, but are not limited to: the world wide web, metropolitan area networks, intranets, generations of mobile communication networks (2G, 3G, 4G, and 5G), Wireless local area networks, and/or Wireless Fidelity (WiFi) networks. In some embodiments, the rf circuit 804 may further include Near Field Communication (NFC) related circuits, which are not limited in this application.
The camera assembly 806 is used to capture images or video. Optionally, camera assembly 806 includes a front camera and a rear camera. Generally, a front camera is disposed at a front panel of the terminal, and a rear camera is disposed at a rear surface of the terminal. In some embodiments, the number of the rear cameras is at least two, and each rear camera is any one of a main camera, a depth-of-field camera, a wide-angle camera and a telephoto camera, so that the main camera and the depth-of-field camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize panoramic shooting and a Virtual Reality (VR) shooting function or other fusion shooting functions. In some embodiments, camera assembly 806 may also include a flash. The flash lamp can be a monochrome temperature flash lamp or a bicolor temperature flash lamp. The double-color-temperature flash lamp is a combination of a warm-light flash lamp and a cold-light flash lamp, and can be used for light compensation at different color temperatures.
The audio circuit 807 may include a microphone and a speaker. The microphone is used for collecting sound waves of a user and the environment, converting the sound waves into electric signals, and inputting the electric signals to the processor 801 for processing or inputting the electric signals to the radio frequency circuit 804 to realize voice communication. For the purpose of stereo sound collection or noise reduction, a plurality of microphones may be provided at different portions of the terminal 800. The microphone may also be an array microphone or an omni-directional pick-up microphone. The speaker is used to convert electrical signals from the processor 801 or the radio frequency circuit 804 into sound waves. The loudspeaker can be a traditional film loudspeaker or a piezoelectric ceramic loudspeaker. When the speaker is a piezoelectric ceramic speaker, the speaker can be used for purposes such as converting an electric signal into a sound wave audible to a human being, or converting an electric signal into a sound wave inaudible to a human being to measure a distance. In some embodiments, the audio circuitry 807 may also include a headphone jack.
The positioning component 808 is operative to locate a current geographic position of the terminal 800 for implementing navigation or Location Based Service (LBS). The Positioning component 808 may be a Positioning component based on the Global Positioning System (GPS) in the united states, the beidou System in china, or the galileo System in russia.
In some embodiments, terminal 800 also includes one or more sensors 810. The one or more sensors 810 include, but are not limited to: acceleration sensor 811, gyro sensor 812, pressure sensor 813, fingerprint sensor 814, optical sensor 815 and proximity sensor 816.
The acceleration sensor 811 may detect the magnitude of acceleration in three coordinate axes of the coordinate system established with the terminal 800. For example, the acceleration sensor 811 may be used to detect the components of the gravitational acceleration in three coordinate axes. The processor 801 may control the touch screen 805 to display the user interface in a landscape view or a portrait view according to the gravitational acceleration signal collected by the acceleration sensor 811. The acceleration sensor 811 may also be used for acquisition of motion data of a game or a user.
The gyro sensor 812 may detect a body direction and a rotation angle of the terminal 800, and the gyro sensor 812 may cooperate with the acceleration sensor 811 to acquire a 3D motion of the user with respect to the terminal 800. From the data collected by the gyro sensor 812, the processor 801 may implement the following functions: motion sensing (such as changing the UI according to a user's tilting operation), image stabilization at the time of photographing, game control, and inertial navigation.
Pressure sensors 813 may be disposed on the side bezel of terminal 800 and/or underneath touch display 805. When the pressure sensor 813 is disposed on the side frame of the terminal 800, the holding signal of the user to the terminal 800 can be detected, and the processor 801 performs left-right hand recognition or shortcut operation according to the holding signal collected by the pressure sensor 813. When the pressure sensor 813 is disposed at a 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 control comprises at least one of a button control, a scroll bar control, an icon control and a menu control.
The fingerprint sensor 814 is used for collecting a fingerprint of the user, and the processor 801 identifies the identity of the user according to the fingerprint collected by the fingerprint sensor 814, or the fingerprint sensor 814 identifies the identity of the user according to the collected fingerprint. Upon identifying that the user's identity is a trusted identity, the processor 801 authorizes the user to perform relevant sensitive operations including unlocking a screen, viewing encrypted information, downloading software, paying for and changing settings, etc. Fingerprint sensor 814 may be disposed on the front, back, or side of terminal 800. When a physical button or a vendor Logo is provided on the terminal 800, the fingerprint sensor 814 may be integrated with the physical button or the 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 screen 805 based on the ambient light intensity collected by the optical sensor 815. Specifically, when the ambient light intensity is high, the display brightness of the touch display screen 805 is increased; when the ambient light intensity is low, the display brightness of the touch display 805 is turned down. In another embodiment, the processor 801 may also dynamically adjust the shooting parameters of the camera assembly 806 based on the ambient light intensity collected by the optical sensor 815.
A proximity sensor 816, also known 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 surface of the terminal 800. In one embodiment, when the proximity sensor 816 detects that the distance between the user and the front surface of the terminal 800 gradually decreases, the processor 801 controls the touch display 805 to switch from the bright screen state to the dark screen state; when the proximity sensor 816 detects that the distance between the user and the front surface of the terminal 800 becomes gradually larger, the processor 801 controls the touch display 805 to switch from the screen-on state to the screen-on state.
Those skilled in the art will appreciate that the configuration shown in fig. 8 is not intended to be limiting of terminal 800 and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components may be used.
In an exemplary embodiment, there is also provided a computer-readable storage medium having stored therein a computer program, which is loaded and executed by a processor of a terminal to implement the version number generation method in the above-described method embodiments.
Alternatively, the computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), 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 computer instructions stored in a computer-readable storage medium, which are read by a processor of a computer device from the computer-readable storage medium, and the processor executes the computer instructions to make the computer device execute the version number generation method provided in the foregoing aspect or various alternative implementations of the aspect.
The above description is only exemplary of the present application and should not be taken as limiting the present application, and any modifications, equivalents, improvements and the like that are made within the spirit and principle of the present application should be included in the protection scope of the present application.
Claims (10)
1. A method for generating a version number, the method comprising:
acquiring a first file identifier of a code file of a target object, wherein the target object is a software product with a version replaced;
generating a version number of the target object based on the first file identifier;
and performing 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.
2. The method of claim 1, wherein generating the version number of the target object based on the first file identifier comprises:
acquiring 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.
3. The method of claim 1, wherein generating the version number of the target object based on the first file identifier comprises:
when the target object depends on a host software product, acquiring a second file identifier of a code file of the host software product;
acquiring 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.
4. The method of claim 3, wherein obtaining the second file identification of the code file of the host software product comprises:
acquiring a unique identification code of the last submission record of the code file of the host software product as the second file identifier; and/or the presence of a gas in the gas,
and acquiring a submission timestamp of the last submission record of the code file of the host software product as the second file identifier.
5. The method according to any one of claims 1 to 4, wherein the obtaining of the first file identifier of the code file of the target object comprises:
acquiring a unique identification code of the last submitted record of the code file of the target object as the first file identifier; and/or the presence of a gas in the gas,
and acquiring a submission timestamp of the last submission record of the code file of the target object as the first file identifier.
6. The method of any of claims 1 to 4, wherein, when the target object is dependent on the host software product, prior to obtaining the first file identification of the code file of the target object, further comprising:
and storing the code file of the target object and the code file of the host software product into the same folder.
7. The method of claim 6, wherein the folder further stores a code management tool, and wherein the code management tool is configured to obtain the first file identifier and/or the second file identifier.
8. An apparatus for generating a version number, the apparatus comprising:
the identification acquisition module is used for acquiring a first file identification of a code file of a target object, wherein the target object is a software product with a version replacement;
the version number generation module is used for generating the version number of the target object based on the first file identifier;
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.
9. A terminal characterized in that it comprises a processor and a memory, said memory storing a computer program which is loaded by said processor and which executes a version number generation method according to any of claims 1 to 7.
10. A computer-readable storage medium, in which a computer program is stored, which is loaded and executed by a processor to implement a version number generation method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011219290.0A CN112256320B (en) | 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 | Version number generation method, device, terminal and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112256320A true CN112256320A (en) | 2021-01-22 |
| CN112256320B CN112256320B (en) | 2024-05-14 |
Family
ID=
Cited By (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 |
| CN112817616A (en) * | 2021-03-02 | 2021-05-18 | 福州汇思博信息技术有限公司 | PKG file management method and terminal |
| CN114461614A (en) * | 2022-04-12 | 2022-05-10 | 北京安华金和科技有限公司 | Sensitive data identification processing method and system |
| CN115599437A (en) * | 2022-10-26 | 2023-01-13 | 北京领雁科技股份有限公司（Cn） | Software version processing method and device, electronic equipment and storage medium |
Citations (14)
| 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 |
| 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 |
| US20110276954A1 (en) * | 2010-05-06 | 2011-11-10 | International Business Machines Corporation | Simultaneous compiler binary optimizations |
| 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 |
| US20200278949A1 (en) * | 2018-02-05 | 2020-09-03 | Tencent Technnology (Shenzhen) Company Limited | Method and apparatus for viewing previously used file, and terminal |
| CN111638905A (en) * | 2020-05-12 | 2020-09-08 | 中信百信银行股份有限公司 | Version number generation method and device, electronic equipment and readable storage medium |
Patent Citations (14)
| 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 |
| 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 |
| US20110276954A1 (en) * | 2010-05-06 | 2011-11-10 | International Business Machines Corporation | Simultaneous compiler binary optimizations |
| CN103123583A (en) * | 2012-12-19 | 2013-05-29 | 深圳市共进电子股份有限公司 | Realizing method for automatically recording software version number |
| US20200278949A1 (en) * | 2018-02-05 | 2020-09-03 | Tencent Technnology (Shenzhen) Company Limited | Method and apparatus for viewing previously used file, and terminal |
| 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 |
Cited By (5)
| 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 |
| CN112817616A (en) * | 2021-03-02 | 2021-05-18 | 福州汇思博信息技术有限公司 | PKG file management method and terminal |
| CN114461614A (en) * | 2022-04-12 | 2022-05-10 | 北京安华金和科技有限公司 | Sensitive data identification processing method and system |
| CN115599437A (en) * | 2022-10-26 | 2023-01-13 | 北京领雁科技股份有限公司（Cn） | Software version processing method and device, electronic equipment and storage medium |
| CN115599437B (en) * | 2022-10-26 | 2023-10-20 | 北京领雁科技股份有限公司 | Software version processing method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110362328B (en) | OTA (over the air) upgrading method and device and computer equipment | |
| CN110308956B (en) | Application interface display method and device and mobile terminal | |
| CN109101213B (en) | Method, device and storage medium for controlling sound card to transmit audio | |
| CN110769313B (en) | Video processing method and device and storage medium | |
| CN108897659B (en) | Method, device and storage medium for modifying log level | |
| CN111949680A (en) | Data processing method and device, computer equipment and storage medium | |
| CN113076051A (en) | Slave control terminal synchronization method, device, terminal and storage medium | |
| CN110677713B (en) | Video image processing method and device and storage medium | |
| CN110784370B (en) | Method and device for testing equipment, electronic equipment and medium | |
| CN109783176B (en) | Page switching method and device | |
| CN109117466B (en) | Table format conversion method, device, equipment and storage medium | |
| CN111192072A (en) | User grouping method and device and storage medium | |
| CN107943484B (en) | Method and device for executing business function | |
| CN111881423A (en) | Method, device and system for limiting function use authorization | |
| CN109033473B (en) | Picture sharing method and device and computer readable storage medium | |
| CN111008083A (en) | Page communication method and device, electronic equipment and storage medium | |
| CN110471613B (en) | Data storage method, data reading method, device and system | |
| CN114595019A (en) | Theme setting method, device and equipment of application program and storage medium | |
| CN113408989A (en) | Automobile data comparison method and device and computer storage medium | |
| CN108632459B (en) | Communication information notification method and device and computer readable storage medium | |
| CN113268234A (en) | Page generation method, device, terminal and storage medium | |
| CN113076452A (en) | Application classification method, device, equipment and computer readable storage medium | |
| CN112256320B (en) | Version number generation method, device, terminal and storage medium | |
| CN111158791A (en) | Configuration file updating method, device and system and storage medium | |
| CN112256320A (en) | Version number generation method, device, terminal 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 |