CN110543329B - Method for managing application version and mobile terminal - Google Patents
Method for managing application version and mobile terminal Download PDFInfo
- Publication number
- CN110543329B CN110543329B CN201910797595.0A CN201910797595A CN110543329B CN 110543329 B CN110543329 B CN 110543329B CN 201910797595 A CN201910797595 A CN 201910797595A CN 110543329 B CN110543329 B CN 110543329B
- Authority
- CN
- China
- Prior art keywords
- version
- target
- user
- identifier
- version identifier
- 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
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
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)
- Stored Programmes (AREA)
Abstract
The invention discloses a method for managing application versions and a mobile terminal, wherein the method comprises the following steps: receiving a first operation; in response to a first operation, displaying version identifications of multiple versions of the target application, the first operation including one of: executing a first preset operation on a version management control corresponding to the target application by a user and a second preset operation executed by the user in the foreground operation process of the target application; receiving a second operation for a target version identifier in the version identifiers; in response to the second operation, a version management operation corresponding to the second operation is performed. According to the method, the user can display the version identifiers corresponding to the multiple versions of the target application through simple and convenient operation, the mobile terminal can receive and respond to the operation of the user on the target version identifiers in the multiple version identifiers, and corresponding version management operation is executed, so that the user can manage the multiple versions of the target application more conveniently and flexibly, and user experience is improved.
Description
Technical Field
The present invention relates to the field of terminals, and in particular, to a method for managing an application version and a mobile terminal.
Background
With the popularization of mobile terminals, various applications of the mobile terminals are increasing, and users need to manage the various applications. For example, the number of upgrades of various applications is increasing, but the upgraded version may have poor stability, low compatibility, and large user interface and function change, which results in that some users, especially middle-aged and elderly users, are not used to use and need to return to the version before upgrade.
The existing rollback method is that when the application is upgraded, a difference packet is generated based on the difference between the new version application and the old version application, the old version application and the difference are included into a temporary application to be used as the new version application, and after a rollback instruction is received, the difference packet is deleted, and then the old version application is rolled back. The operation of the current mainstream is that a user searches corresponding applications and versions of the corresponding applications from all applications in the setting, and executes rollback operation on the corresponding versions of the applications based on the current rollback method, so that rollback of the application versions is realized, but the operation mode is not convenient enough, and user experience is affected.
Disclosure of Invention
The embodiment of the invention provides a method for managing application versions and a mobile terminal, which are used for solving the problems that the operation mode of the prior art is not convenient enough and the user experience is affected.
In order to solve the technical problems, the invention is realized as follows:
in a first aspect, a method of managing application versions is provided, the method comprising:
receiving a first operation;
in response to the first operation, displaying version identifications of multiple versions of the target application, the first operation including one of: the user executes a first preset operation on a version management control corresponding to the target application and a second preset operation executed by the user in the foreground operation process of the target application;
receiving a second operation for a target version identifier in the version identifiers;
and executing a version management operation corresponding to the second operation in response to the second operation.
In a second aspect, there is provided a mobile terminal comprising:
the first receiving module is used for receiving a first operation;
a display module, configured to display version identifiers of multiple versions of a target application in response to the first operation, where the first operation includes one of the following operations: the user executes a first preset operation on a version management control corresponding to the target application and a second preset operation executed by the user in the foreground operation process of the target application;
a second receiving module, configured to receive a second operation for a target version identifier in the version identifiers;
and the execution module is used for responding to the second operation and executing the version management operation corresponding to the second operation.
In a third aspect, there is provided a mobile terminal comprising a processor, a memory and a computer program stored on the memory and executable on the processor, the computer program implementing the steps of the method according to the first aspect when executed by the processor.
In a fourth aspect, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the method according to the first aspect.
In the embodiment of the invention, the user can enable the mobile terminal to display the version identifications of the multiple versions of the target application in a simple and convenient operation mode, and the mobile terminal can receive and respond to the second operation of the user for the target version identifications in the multiple version identifications to execute corresponding version management operation, so that the management of the multiple versions of the target application by the user is more convenient and flexible, and the user experience is improved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the invention and do not constitute a limitation on the invention. In the drawings:
FIG. 1 is a flow diagram of a method of managing application versions of one embodiment of the invention;
2 (a) -2 (c) are schematic diagrams of a method of displaying version management controls of one embodiment of the invention;
3 (a) -3 (c) are schematic diagrams of a method of selecting a target version identification according to one embodiment of the invention;
FIGS. 4 (a) -4 (c) are schematic diagrams of a method of deleting a target version identification according to one embodiment of the invention;
5 (a) -5 (b) are schematic diagrams of a method of modifying a target version identification of one embodiment of the invention;
FIG. 6 is a flow diagram of a method of managing application versions in accordance with another embodiment of the present invention;
FIG. 7 is a flow diagram of a method of managing application versions in accordance with yet another embodiment of the present invention;
8 (a) -8 (c) are schematic diagrams of a method of selecting a target version identification according to another embodiment of the present invention;
fig. 9 is a schematic structural view of a mobile terminal according to an embodiment of the present invention;
fig. 10 is a schematic structural view of a mobile terminal according to another embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
Fig. 1 is a flow chart illustrating a method for managing application versions according to an embodiment of the present invention, and the method shown in fig. 1 may be performed by a mobile terminal, and the method includes:
s110, receiving a first operation.
S120, displaying version identifiers of multiple versions of the target application in response to the first operation, wherein the first operation comprises one of the following operations: and the user executes a first preset operation on the version management control corresponding to the target application and a second preset operation executed by the user in the foreground running process of the target application.
In some embodiments, in a case that the current interface is a desktop, that is, in a process that the target application is not running in the foreground, each application has a corresponding version management control, the first operation is that a user executes a first preset operation on the version management control corresponding to the target application, the first preset operation may be an operation that the user clicks the version management control corresponding to the target application, and the mobile terminal receives and responds to the first preset operation to display version identifiers of multiple versions of the target application. In the case that the current interface is an interface of the target application, that is, in the process that the target application runs in the foreground, the first operation is a second preset operation executed by a user in the process that the target application runs in the foreground, the second preset operation may be an operation of shaking the mobile terminal, and the mobile terminal receives and responds to the second preset operation to display version identifiers of multiple versions of the target application. The user can execute the first preset operation or the second preset operation based on the running state of the target application, so that the mobile terminal displays multiple versions of the target application to the user in a short time, that is, the user can quickly find the multiple versions of the target application through a simple and convenient operation mode, the time for finding the multiple versions of the target application is reduced, and the user experience is improved.
Optionally, in other embodiments, when the first preset operation is an operation that the user clicks the version management control corresponding to the target application, the method shown in fig. 1 further includes:
hiding the version management control in response to a sliding operation of a user sliding the version management control along a first direction; or alternatively, the first and second heat exchangers may be,
and responding to the sliding operation of the user in a preset area along a second direction, and displaying the version management control, wherein the second direction is opposite to the first direction.
In general, the version management control is not displayed by default, after the version of the target application is upgraded or in response to the sliding operation of the user along the second direction in the preset area, the version management control corresponding to the target application is displayed, and in order to improve the operability of the version management control, in response to the sliding operation of the user sliding the version management control along the first direction, the version management control is hidden, so that the desktop display is simpler, wherein the first direction is opposite to the second direction. And otherwise, responding to the sliding operation of the user along the second direction in the preset area, and displaying the version management control.
For example, the version management control is in the lower left corner of the application, and the version management control is represented in the form of a hint point. As shown in fig. 2 (a), by default, the lower left corner areas of the letter, calendar, caption, and map do not display a hint point. As shown in fig. 2 (b), the user performs a sliding operation in the right direction in the area below the letter. As shown in fig. 2 (c), the mobile terminal displays a hint point in response to a sliding operation of a user in a right direction. Otherwise, in response to a sliding operation of the user sliding the cue point in the left direction, the cue point will disappear from the interface.
S130, receiving a second operation aiming at a target version identifier in the version identifiers.
And S140, responding to the second operation, and executing a version management operation corresponding to the second operation.
In some embodiments, the user may manage multiple versions of the target application according to his own usage habits, with the version identifications of the multiple versions of the target application displayed. The mobile terminal receives and responds to the operation of the user aiming at the target version identifications of the plurality of version identifications, and executes corresponding version management operation. Therefore, the management of multiple versions of the target application by the user is more convenient, convenient and flexible, and the user experience is improved.
For example, in the case that the target version is lower than the current version, if the user returns to the target version, the returning operation of the target version is performed in response to the second operation of selecting the target version identifier corresponding to the target version by the user. And if the target version is deleted, responding to a second operation of deleting the target version identifier corresponding to the target version by the user, and executing the deleting operation of the target version.
Optionally, in some embodiments, the second operation is an operation of selecting the target version identifier, where a version corresponding to the target version identifier is lower than a current version of the target application;
wherein the version management operation includes:
acquiring an installation package corresponding to the target version identifier;
and installing the installation package.
Specifically, in some embodiments, in response to an operation of selecting the target version identifier, if the target version corresponding to the target version identifier is the lowest version, the installation package corresponding to the target version identifier is directly acquired and installed. If the target version corresponding to the target version identifier is not the lowest version, namely the target version is the upgraded version, determining an installation package corresponding to the target version identifier based on a difference package between the lowest version and the target version and an installation package of the lowest version, and acquiring and installing the installation package. The method and the device provide the user with the shortcut interaction mode for backing the low version, are convenient for the user to carry out degradation on the upgraded version, and are simple in operation mode, high in efficiency and capable of improving user experience.
It should be appreciated that the difference package of the target version is formed of code that is added, changed or subtracted based on the installation package of the last version of the target version. That is, the difference between the installation package of the target version and the installation package of the previous version is formed.
For example, the target application has four versions, namely an A version, a B version, a C version and a D version, in sequence from the lowest version to the highest version, wherein the A version is the lowest version, the A version only has an installation package, the B version, the C version and the D version are updated versions, and each time the versions are updated, the installation package and the difference package of the corresponding versions are generated. However, in order to save the storage space of the mobile terminal, the installation package of the corresponding version is automatically deleted after the installation of the installation package is completed, so that the version B, the version C and the version D have only difference packages.
And under the condition that the current version of the target application is the D version, if the current version is returned to the A version, responding to the operation of clicking the version identification corresponding to the A version, directly acquiring the installation package of the A version and installing the installation package. If the C version is returned, responding to the operation of clicking the version identification corresponding to the C version, and synthesizing the C version installation package based on the difference package of the A version installation package, the B version installation package and the C version installation package, and acquiring the C version installation package and the C version installation package.
Alternatively, the target application is a WeChat, and the version management control is represented in the form of a hint point. As shown in fig. 3 (a), an operation of clicking a hint point of a lower area of a letter by a user is responded. As shown in fig. 3 (b), the desktop background becomes semitransparent, and simultaneously, a version switching bullet frame is displayed, the content of the version switching bullet frame includes a bullet frame name, version identifiers corresponding to a plurality of versions of the target application, and a checkbox corresponding to the identifier, wherein the bullet frame name is version switching, version identifiers corresponding to the highest version to the lowest version are v7.1.0, V7.2.2, V7.3.1 and V8.0.0 respectively, the current version of the target application is a version with a version identifier of V8.0.0, and the checkbox corresponding to V8.0.0 is gray and in a state that the checkbox cannot be checked; whereas the checkboxes corresponding to v7.1.0, V7.2.2, V7.3.1 are shown black and in a checkable state. That is, when the target application is in a certain version, the check box corresponding to the version identifier of the version displays gray and is in a state that the check box cannot be checked; otherwise, the frame is displayed in black and in a state of being able to be checked. As shown in fig. 3 (c), if the version is rolled back to the version of version identifier V7.3.1, in response to clicking on the version identifier V7.3.1, the installation package corresponding to the version identifier is acquired and installed.
Optionally, in other embodiments, the version management operation is one of:
if the target version corresponding to the target version identifier is the lowest version, deleting an installation package corresponding to the target version identifier and a difference package corresponding to the version identifier of the next lowest version, and determining a target installation package of the next lowest version based on the installation package corresponding to the target version identifier and the difference package corresponding to the version identifier of the next lowest version;
if the target version corresponding to the target version identifier is the highest version, deleting the difference packet corresponding to the target version identifier; the method comprises the steps of,
if the target version corresponding to the target version identifier is not the lowest version and is not the highest version, deleting the difference packet corresponding to the target version identifier and the initial difference packet corresponding to the version identifier of the next version higher than the target version, and taking the target difference packet as the final difference packet corresponding to the version identifier of the next version, wherein the target difference packet is determined based on the difference packet corresponding to the target version identifier and the initial difference packet corresponding to the version identifier of the next version.
For example, the target application has eight versions in total, the lowest version has only an installation package, and if the other versions only need a difference package, the installation package of the lowest version and the difference package of the next lowest version are deleted, and the target installation package formed by the installation package of the lowest version and the difference package of the next lowest version is determined as the final installation package of the next lowest version, namely the next lowest version is changed into the lowest version. If the highest version, i.e., the eighth version, is deleted, the difference package of the highest version is deleted. If the third version is deleted, deleting the third version of the difference packet and the fourth version of the initial difference packet, and determining a target difference packet formed by the third version of the difference packet and the fourth version of the initial difference packet as a fourth version of the final difference packet. On the one hand, the storage space of the mobile terminal can be saved; on the other hand, the dislike or unusual version of the user can be deleted, so that the user is prevented from selecting the dislike or unusual version, and the user experience is improved.
Alternatively, if the version identified as V7.2.2 is deleted, as shown in fig. 4 (a), the operation of sliding the version identified as V7.2.2 in the left direction is responded. As shown in fig. 4 (b), a delete button is displayed. As shown in fig. 4 (c), the version identified as V7.2.2 is deleted. The specific process of the deletion is as follows: deleting the corresponding difference packet V7.2.2 and the initial difference packet V7.3.1, clathrating the primary difference packet V7.2.2 and the primary difference packet V7.3.1 into a target difference packet, and determining the target difference packet as a final difference packet V7.3.1.
Optionally, in some embodiments, the version management operation includes:
displaying an editing frame;
and in response to the input operation of the user on the editing box, modifying the target version identification into the identification input by the user.
In order to facilitate the user to better manage and distinguish each version of the target application according to the user's own understanding, the user can modify the version identifier corresponding to each version into the identifier which is easy to identify by the user. For example, the target application has three versions, and the version identifiers corresponding to the three versions are A, B, C respectively, if the user feels that the version identifier B is good, and wants to modify the version identifier B into good. And displaying the edit box in response to the pressing operation of B, wherein the pressing time of the pressing operation is longer than the preset time, and modifying the version identifier as B to be good in response to the input operation of the user on the edit box. And the user can quickly identify the version mark as a good version, so that the user experience is improved.
Alternatively, if the target version identifier V7.2.2 is modified to be the normal version, as shown in fig. 5 (a), the mobile terminal responds to the pressing operation of V7.2.2, and the pressing time of the pressing operation is longer than the preset time, and displays the edit box. As shown in fig. 5 (b), the mobile terminal modifies the version identification V7.2.2 to be a cis version in response to an input operation of the user with respect to the edit box.
Optionally, in other embodiments, the method further comprises:
and hiding the version identifications of the multiple versions of the target application in response to an operation of clicking on the desktop or an interface of the target application.
Specifically, if the current interface is a desktop, if the target version identifier of the target application is not selected, clicking the desktop to hide the target version identifier of the target application, and if the current interface is an interface of the target application, if the target version identifier of the target application is not selected, clicking the interface of the target application to hide the target version identifier of the target application.
For example, the existing prompt point is used as a version management entry, so that the use habit and thinking habit of the user can be delayed. As shown in fig. 6, by default, the hint point in the lower left corner of the target application is not displayed. After the target application is upgraded or in response to a sliding operation of the user in the right direction in the lower area of the target application, a prompt point in the lower left corner of the target application is displayed. And responding to the operation of clicking the prompt point by the user, and popping up a version switching bullet frame which comprises version identifiers of multiple versions of the target application. If the target version is lower than the current version of the target application, if the target version is returned to the target version of the target application, responding to the operation of clicking the target version identifier corresponding to the target version by a user, closing the version switching bullet frame, and acquiring an installation package corresponding to the target version identifier and installing the installation package by the background. If the target version is deleted, a deleting button is displayed to delete the target version in response to the operation of sliding the target version identifier corresponding to the target version along the left direction. If the target version identifier is renamed, responding to the pressing operation of the target version identifier, displaying an editing box for renaming the target version identifier, and responding to the input operation of a user aiming at the editing box, wherein the pressing time of the pressing operation is longer than the preset time, and modifying the identifier input by the user. If the target version identification of the target application is not selected, clicking the desktop, closing the version switching bullet frame, and hiding the target version identification of the target application. In response to a sliding operation in the left direction in the lower area of the target application, the cue point is hidden.
Or, the prompt point is not needed to be used as an entry for upgrading and backspacing of the target application, and the version switching frame is only needed to be opened in the target application in a shaking mode, so that the entry is shallower, the interactivity is stronger, and each version of the target application can be switched in the target application at any time. As shown in fig. 7, in response to an operation of opening a target application, the target application is operated in the foreground, in response to an operation of shaking the mobile terminal, a version switching frame is popped up, the version switching frame includes multiple versions of the target application, if the target version is lower than a current version of the target application, if the target version is returned to the target version of the target application, in response to an operation of clicking a target version identifier corresponding to the target version by a user, the version switching frame is closed, and an installation package corresponding to the target version identifier is acquired and installed in the background. If the target version is deleted, a deleting button is displayed to delete the target version in response to the operation of sliding the target version identifier corresponding to the target version along the left direction. If the target version identifier is renamed, responding to the pressing operation of the target version identifier, wherein the pressing time of the pressing operation is longer than the preset time, displaying an editing box, and responding to the input operation of a user for the editing box, renaming the target version identifier. If the target version identification of the target application is not selected, clicking the interface of the target application, and closing the target version identification of the hidden target application.
Specifically, in the case that the target version is lower than the current version of the target application, the specific operation procedure of returning the current version to the target version is as follows: after the target application is opened, as shown in fig. 8 (a), the interface of the target application is the current version UI interface, and if the user is not used to use the current version in the use process of the target application and wants to return to the previous version, namely the target version, as shown in fig. 8 (b), in response to the operation of shaking the mobile terminal, the popup version switches the popup frame, and meanwhile, the target application interface becomes semitransparent.
And responding to the operation of clicking the target version identifier corresponding to the target version by the user, closing the version switching bullet frame, exiting the foreground by the target application, and acquiring and installing the installation package corresponding to the target version identifier in the background. As shown in fig. 8 (c), after the installation is completed, the interface of the target application is a target UI interface.
In the embodiment of the invention, the user can enable the mobile terminal to display the version identifications of the multiple versions of the target application in a simple and convenient operation mode, and the mobile terminal can respond to the second operation of the user for the version identifications of the multiple versions to execute corresponding version management operation, so that the user can manage the multiple versions of the target application more conveniently and flexibly, and the user experience is improved.
The method of managing application versions according to the embodiment of the present invention is described in detail above with reference to fig. 1 to 8, and the mobile terminal according to the embodiment of the present application will be described in detail below with reference to fig. 9. As shown in fig. 9, the mobile terminal 90 includes:
a first receiving module 91 for receiving a first operation;
a display module 92, configured to display version identifiers of multiple versions of the target application in response to the first operation, where the first operation includes one of the following operations: the user executes a first preset operation on a version management control corresponding to the target application and a second preset operation executed by the user in the foreground operation process of the target application;
a second receiving module 93, configured to receive a second operation for a target version identifier in the version identifiers;
and an execution module 94, configured to execute, in response to the second operation, a version management operation corresponding to the second operation.
In the embodiment of the invention, the user can enable the mobile terminal to display the version identifications of the multiple versions of the target application in a simple and convenient operation mode, and the mobile terminal can receive and respond to the second operation of the user for the target version identifications in the multiple version identifications to execute corresponding version management operation, so that the management of the multiple versions of the target application by the user is more convenient and flexible, and the user experience is improved.
Optionally, as an embodiment, the second operation is an operation of selecting the target version identifier, where a version corresponding to the target version identifier is lower than a current version of the target application;
wherein the execution module 94 includes:
the rollback sub-module is used for acquiring an installation package corresponding to the target version identifier;
the rollback sub-module is further used for installing the installation package.
Optionally, as an embodiment, the execution module 94 includes:
the deleting sub-module is used for deleting the installation package corresponding to the target version identifier and the difference package corresponding to the version identifier of the next lower version if the target version corresponding to the target version identifier is the lowest version, and determining the target installation package of the next lower version based on the installation package corresponding to the target version identifier and the difference package corresponding to the version identifier of the next lower version;
if the target version corresponding to the target version identifier is the highest version, deleting the difference packet corresponding to the target version identifier; the method comprises the steps of,
if the target version corresponding to the target version identifier is not the lowest version and is not the highest version, deleting the difference packet corresponding to the target version identifier and the initial difference packet corresponding to the version identifier of the next version higher than the target version, and taking the target difference packet as the final difference packet corresponding to the version identifier of the next version, wherein the target difference packet is determined based on the difference packet corresponding to the target version identifier and the initial difference packet corresponding to the version identifier of the next version.
Optionally, as an embodiment, the execution module 94 includes:
the display sub-module is used for displaying the editing frame;
and the modification sub-module is used for responding to the input operation of the user on the editing box and modifying the target version identification into the identification input by the user.
Optionally, as an embodiment, the display module is further configured to:
hiding the version management control in response to a sliding operation of a user sliding the version management control along a first direction; or alternatively, the first and second heat exchangers may be,
and responding to the sliding operation of the user in a preset area along a second direction, and displaying the version management control, wherein the second direction is opposite to the first direction.
The mobile terminal provided by the embodiment of the present invention can implement each process implemented by the mobile terminal in the method embodiments of fig. 1 to 8, and in order to avoid repetition, a description is omitted here.
Fig. 10 is a schematic diagram of a hardware structure of a mobile terminal implementing various embodiments of the present invention, where the mobile terminal 100 includes, but is not limited to: radio frequency unit 101, network module 102, audio output unit 103, input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, processor 110, and power supply 111. Those skilled in the art will appreciate that the mobile terminal structure shown in fig. 10 is not limiting of the mobile terminal and that the mobile terminal may include more or fewer components than shown, or may combine certain components, or a different arrangement of components. In the embodiment of the invention, the mobile terminal comprises, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palm computer, a vehicle-mounted terminal, a wearable device, a pedometer and the like.
Wherein the processor 110 is configured to control the user input unit 107 to receive a first operation; in response to the first operation, the control display unit 106 displays version identifications of a plurality of versions of the target application, the first operation including one of: the user executes a first preset operation on a version management control corresponding to the target application and a second preset operation executed by the user in the foreground operation process of the target application; control user input unit 107 receives a second operation for a target one of the version identifications; and executing a version management operation corresponding to the second operation in response to the second operation.
In the embodiment of the invention, the user can enable the mobile terminal to display the version identifications of the multiple versions of the target application in a simple and convenient operation mode, and the mobile terminal can receive and respond to the second operation of the user for the target version identifications in the multiple version identifications to execute corresponding version management operation, so that the management of the multiple versions of the target application by the user is more convenient and flexible, and the user experience is improved.
It should be understood that, in the embodiment of the present invention, the radio frequency unit 101 may be configured to receive and send information or signals during a call, specifically, receive downlink data from a base station, and then process the received downlink data with the processor 110; and, the uplink data is transmitted to the base station. Typically, the radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 101 may also communicate with networks and other devices through a wireless communication system.
The mobile terminal provides wireless broadband internet access to the user through the network module 102, such as helping the user to send and receive e-mail, browse web pages, access streaming media, etc.
The audio output unit 103 may convert audio data received by the radio frequency unit 101 or the network module 102 or stored in the memory 109 into an audio signal and output as sound. Also, the audio output unit 103 may also provide audio output (e.g., a call signal reception sound, a message reception sound, etc.) related to a specific function performed by the mobile terminal 100. The audio output unit 103 includes a speaker, a buzzer, a receiver, and the like.
The input unit 104 is used for receiving an audio or video signal. The input unit 104 may include a graphics processor (Graphics Processing Unit, GPU) 1041 and a microphone 1042, the graphics processor 1041 processing image data of still pictures or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 106. The image frames processed by the graphics processor 1041 may be stored in the memory 109 (or other storage medium) or transmitted via the radio frequency unit 101 or the network module 102. Microphone 1042 may receive sound and be capable of processing such sound into audio data. The processed audio data may be converted into a format output that can be transmitted to the mobile communication base station via the radio frequency unit 101 in the case of a telephone call mode.
The mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor and a proximity sensor, wherein the ambient light sensor can adjust the brightness of the display panel 1061 according to the brightness of ambient light, and the proximity sensor can turn off the display panel 1061 and/or the backlight when the mobile terminal 100 moves to the ear. As one of the motion sensors, the accelerometer sensor can detect the acceleration in all directions (generally three axes), and can detect the gravity and direction when stationary, and can be used for recognizing the gesture of the mobile terminal (such as horizontal and vertical screen switching, related games, magnetometer gesture calibration), vibration recognition related functions (such as pedometer and knocking), and the like; the sensor 105 may further include a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, etc., which are not described herein.
The display unit 106 is used to display information input by a user or information provided to the user. The display unit 106 may include a display panel 1061, and the display panel 1061 may be configured in the form of a liquid crystal display (Liquid Crystal Display, LCD), an Organic Light-Emitting Diode (OLED), or the like.
The user input unit 107 may be used to receive input numeric or character information and to generate key signal inputs related to user settings and function control of the mobile terminal. Specifically, the user input unit 107 includes a touch panel 1071 and other input devices 1072. The touch panel 1071, also referred to as a touch screen, may collect touch operations thereon or thereabout by a user (e.g., operations of the user on the touch panel 1071 or thereabout using any suitable object or accessory such as a finger, stylus, etc.). The touch panel 1071 may include two parts of a touch detection device and a touch controller. The touch detection device detects the touch azimuth of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts the touch information into touch point coordinates, and sends the touch point coordinates to the processor 110, and receives and executes commands sent by the processor 110. Further, the touch panel 1071 may be implemented in various types such as resistive, capacitive, infrared, and surface acoustic wave. The user input unit 107 may include other input devices 1072 in addition to the touch panel 1071. In particular, other input devices 1072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein.
Further, the touch panel 1071 may be overlaid on the display panel 1061, and when the touch panel 1071 detects a touch operation thereon or nearby, the touch operation is transmitted to the processor 110 to determine the type of touch event, and then the processor 110 provides a corresponding visual output on the display panel 1061 according to the type of touch event. Although in fig. 10, the touch panel 1071 and the display panel 1061 are two independent components for implementing the input and output functions of the mobile terminal, in some embodiments, the touch panel 1071 may be integrated with the display panel 1061 to implement the input and output functions of the mobile terminal, which is not limited herein.
The interface unit 108 is an interface through which an external device is connected to the mobile terminal 100. For example, the external devices may include a wired or wireless headset port, an external power (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 108 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the mobile terminal 100 or may be used to transmit data between the mobile terminal 100 and an external device.
The processor 110 is a control center of the mobile terminal, connects various parts of the entire mobile terminal using various interfaces and lines, and performs various functions of the mobile terminal and processes data by running or executing software programs and/or modules stored in the memory 109 and calling data stored in the memory 109, thereby performing overall monitoring of the mobile terminal. Processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor that primarily handles operating systems, user interfaces, applications, etc., with a modem processor that primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 110.
The mobile terminal 100 may further include a power source 111 (e.g., a battery) for supplying power to the respective components, and preferably, the power source 111 may be logically connected to the processor 110 through a power management system, so as to perform functions of managing charging, discharging, and power consumption management through the power management system.
In addition, the mobile terminal 100 includes some functional modules, which are not shown, and will not be described herein.
Preferably, the embodiment of the present invention further provides a mobile terminal, including a processor 110, a memory 109, and a computer program stored in the memory 109 and capable of running on the processor 110, where the computer program when executed by the processor 110 implements each process of the method embodiments shown in fig. 1 to 8 and achieves the same technical effects, and for avoiding repetition, a detailed description is omitted herein.
The embodiment of the present invention further provides a computer readable storage medium, on which a computer program is stored, where the computer program when executed by a processor implements each process of the method embodiments shown in fig. 1 to 8 and achieves the same technical effects, and in order to avoid repetition, a detailed description is omitted here. Wherein the computer readable storage medium is selected from Read-Only Memory (ROM), random access Memory (Random Access Memory, RAM), magnetic disk or optical disk.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method according to the embodiments of the present invention.
The embodiments of the present invention have been described above with reference to the accompanying drawings, but the present invention is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those having ordinary skill in the art without departing from the spirit of the present invention and the scope of the claims, which are to be protected by the present invention.
Claims (10)
1. A method of managing application versions, the method comprising:
receiving a first operation;
in response to the first operation, displaying version identifications of multiple versions of the target application, the first operation including one of: the user executes a first preset operation on a version management control corresponding to the target application and a second preset operation executed by the user in the foreground operation process of the target application;
receiving a second operation for a target version identifier in the version identifiers;
executing a version management operation corresponding to the second operation in response to the second operation;
the version management operation is one of the following operations:
if the target version corresponding to the target version identifier is the lowest version, deleting an installation package corresponding to the target version identifier and a difference package corresponding to the version identifier of the next lowest version, and determining a target installation package of the next lowest version based on the installation package corresponding to the target version identifier and the difference package corresponding to the version identifier of the next lowest version;
if the target version corresponding to the target version identifier is the highest version, deleting the difference packet corresponding to the target version identifier; the method comprises the steps of,
if the target version corresponding to the target version identifier is not the lowest version and is not the highest version, deleting the difference packet corresponding to the target version identifier and the initial difference packet corresponding to the version identifier of the next version higher than the target version, and taking the target difference packet as the final difference packet corresponding to the version identifier of the next version, wherein the target difference packet is determined based on the difference packet corresponding to the target version identifier and the initial difference packet corresponding to the version identifier of the next version.
2. The method of claim 1, wherein the second operation is an operation of selecting the target version identification, the target version identification corresponding to a version lower than a current version of the target application;
wherein the version management operation includes:
acquiring an installation package corresponding to the target version identifier;
and installing the installation package.
3. The method of claim 1, wherein the version management operation comprises:
displaying an editing frame;
and in response to the input operation of the user on the editing box, modifying the target version identification into the identification input by the user.
4. A method according to any one of claims 1-3, wherein the method further comprises:
hiding the version management control in response to a sliding operation of a user sliding the version management control along a first direction; or alternatively, the first and second heat exchangers may be,
and responding to the sliding operation of the user in a preset area along a second direction, and displaying the version management control, wherein the second direction is opposite to the first direction.
5. A mobile terminal, the mobile terminal comprising:
the first receiving module is used for receiving a first operation;
a display module, configured to display version identifiers of multiple versions of a target application in response to the first operation, where the first operation includes one of the following operations: the user executes a first preset operation on a version management control corresponding to the target application and a second preset operation executed by the user in the foreground operation process of the target application;
a second receiving module, configured to receive a second operation for a target version identifier in the version identifiers;
an execution module, configured to execute a version management operation corresponding to the second operation in response to the second operation;
the execution module comprises:
the deleting sub-module is used for deleting the installation package corresponding to the target version identifier and the difference package corresponding to the version identifier of the next lower version if the target version corresponding to the target version identifier is the lowest version, and determining the target installation package of the next lower version based on the installation package corresponding to the target version identifier and the difference package corresponding to the version identifier of the next lower version;
if the target version corresponding to the target version identifier is the highest version, deleting the difference packet corresponding to the target version identifier; the method comprises the steps of,
if the target version corresponding to the target version identifier is not the lowest version and is not the highest version, deleting the difference packet corresponding to the target version identifier and the initial difference packet corresponding to the version identifier of the next version higher than the target version, and taking the target difference packet as the final difference packet corresponding to the version identifier of the next version, wherein the target difference packet is determined based on the difference packet corresponding to the target version identifier and the initial difference packet corresponding to the version identifier of the next version.
6. The mobile terminal of claim 5, wherein the second operation is an operation of selecting the target version identification, the target version identification corresponding to a version lower than a current version of the target application;
wherein the execution module comprises:
the rollback sub-module is used for acquiring an installation package corresponding to the target version identifier;
the rollback sub-module is further used for installing the installation package.
7. The mobile terminal of claim 5, wherein the execution module comprises:
the display sub-module is used for displaying the editing frame;
and the modification sub-module is used for responding to the input operation of the user on the editing box and modifying the target version identification into the identification input by the user.
8. The mobile terminal according to any of the claims 5-7, wherein the display module is further configured to:
hiding the version management control in response to a sliding operation of a user sliding the version management control along a first direction; or alternatively, the first and second heat exchangers may be,
and responding to the sliding operation of the user in a preset area along a second direction, and displaying the version management control, wherein the second direction is opposite to the first direction.
9. A mobile terminal, comprising: memory, a processor and a computer program stored on the memory and executable on the processor, which when executed by the processor, performs the steps of the method according to any one of claims 1 to 4.
10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, implements the steps of the method according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910797595.0A CN110543329B (en) | 2019-08-27 | 2019-08-27 | Method for managing application version and mobile terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910797595.0A CN110543329B (en) | 2019-08-27 | 2019-08-27 | Method for managing application version and mobile terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110543329A CN110543329A (en) | 2019-12-06 |
| CN110543329B true CN110543329B (en) | 2023-05-05 |
Family
ID=68710680
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910797595.0A Active CN110543329B (en) | 2019-08-27 | 2019-08-27 | Method for managing application version and mobile terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110543329B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114237979A (en) * | 2021-11-23 | 2022-03-25 | 维沃移动通信有限公司 | Data switching method, device and electronic device |
| CN116679872B (en) * | 2022-11-15 | 2024-08-30 | 荣耀终端有限公司 | Redundant installation package cleaning method |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105893080A (en) * | 2016-03-28 | 2016-08-24 | 努比亚技术有限公司 | Application management method and device |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5732275A (en) * | 1996-01-11 | 1998-03-24 | Apple Computer, Inc. | Method and apparatus for managing and automatically updating software programs |
| US10133875B2 (en) * | 2016-01-29 | 2018-11-20 | Konica Minolta Laboratory U.S.A., Inc. | Digital rights management system implementing version control |
| CN107967153B (en) * | 2017-12-13 | 2021-04-02 | 维沃移动通信有限公司 | Application program management method and mobile terminal |
| CN108563378B (en) * | 2018-04-25 | 2020-06-16 | 维沃移动通信有限公司 | Message management method and terminal |
| CN109725805B (en) * | 2018-12-28 | 2021-07-30 | 维沃移动通信有限公司 | Alarm clock setting method and terminal |
-
2019
- 2019-08-27 CN CN201910797595.0A patent/CN110543329B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105893080A (en) * | 2016-03-28 | 2016-08-24 | 努比亚技术有限公司 | Application management method and device |
Non-Patent Citations (1)
| Title |
|---|
| ANDROID智能手机开发软件版本管理系统设计与实现;张向军;《知网》;1-25 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110543329A (en) | 2019-12-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108536365B (en) | Image sharing method and terminal | |
| WO2019174611A1 (en) | Application configuration method and mobile terminal | |
| CN108845853B (en) | Application program starting method and mobile terminal | |
| CN110837327B (en) | Message viewing method and terminal | |
| CN111338530B (en) | Control method of application program icon and electronic equipment | |
| CN109857297B (en) | Information processing method and terminal equipment | |
| CN108334272B (en) | Control method and mobile terminal | |
| CN110308834B (en) | Setting method of application icon display mode and terminal | |
| CN111459349B (en) | Application recommendation method and electronic equipment | |
| CN109407948B (en) | Interface display method and mobile terminal | |
| CN110209331A (en) | Information cuing method and terminal | |
| CN110928619B (en) | Wallpaper setting method and device, electronic equipment and medium | |
| CN107748640A (en) | One kind puts out screen display methods and mobile terminal | |
| CN110096203B (en) | Screenshot method and mobile terminal | |
| CN108491148A (en) | A kind of application sharing method and terminal | |
| CN110995924B (en) | Account management method and electronic equipment | |
| CN110543329B (en) | Method for managing application version and mobile terminal | |
| CN109284146B (en) | Light application starting method and mobile terminal | |
| CN109597546B (en) | Icon processing method and terminal equipment | |
| WO2019096043A1 (en) | Application icon management method and mobile terminal | |
| CN111638842B (en) | Display control method and device and electronic equipment | |
| CN111399715B (en) | Interface display method and electronic equipment | |
| CN111240551B (en) | Application program control method and electronic equipment | |
| CN111130995B (en) | Image control method, electronic device, and storage medium | |
| CN110471682B (en) | Application program updating method and mobile terminal |
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 |