Detailed Description
Reference will now be made in detail to embodiments of the present application, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are exemplary only for the purpose of explaining the present application and are not to be construed as limiting the present application.
A method and apparatus for managing application icons in a mobile terminal according to an embodiment of the present application are described below with reference to the accompanying drawings.
Fig. 1 is a flowchart of a method for managing application icons in a mobile terminal according to an embodiment of the present application.
As shown in fig. 1, a method for managing application icons in a mobile terminal according to an embodiment of the present application includes the following steps.
S101, acquiring a plurality of application icons corresponding to application programs in the mobile terminal, wherein the application icons are respectively located in different desktop groups, and only one application icon can exist in one desktop group.
In one embodiment of the present application, one or more icons may be created for each application based on the actual needs of the user. The user can put the established icons into different desktop groups respectively according to the needs.
It should be noted that, for the same application, only one icon of the application can exist in the same desktop group, and a plurality of icons cannot exist simultaneously.
For example, application a has 3 corresponding icons. The three icons can be placed into three desktop groupings, respectively, and neither of the three icons can be placed into the same desktop grouping.
That is, there is a one-to-many relationship between the application and the icon. In the process of deleting the icons of the application programs, when the last icon of the application program is deleted, and the other one only deletes the icon of the application program.
In embodiments of the present application, a correspondence between a desktop grouping and the icons it includes may be established. For example, if icons of applications a and b are included in desktop group 1, then desktop group 1 corresponds to icons a and b. If icons of the applications a, b, d and h are included in the desktop group 2, the desktop group 2 corresponds to the icons a, b, d and h.
And S102, receiving an operation instruction of a user, and correspondingly controlling the application program and the application program icons according to the operation instruction.
In the embodiment of the application, the operation instruction of the user may include a drag operation, an icon deletion operation, an icon adding operation, and the like.
It should be understood that the management interface may be provided by the mobile terminal or the PC side application program, and the operation instruction of the user may be received through the management interface. The application program may be an icon management program built in the system, or an application management program selected and installed by the user.
Specifically, in one embodiment of the present application, the group to which the application icon belongs may be controlled by a drag operation, that is, the operation instruction is a drag operation. FIG. 2a is a flowchart illustrating drag management of an application icon according to an embodiment of the present application. Fig. 2b and 2c are schematic diagrams illustrating drag management of an application icon according to an embodiment of the present application.
As shown in fig. 2a, drag management of an application icon includes the following steps.
S201, acquiring a target position of the dragging operation.
The dragging operation can be gesture dragging or mouse dragging.
Therefore, the target position of the dragging operation can be determined according to the gesture track or the end point of the mouse moving track.
The track end point of the dragging operation can be any position on the desktop, such as a blank area of the desktop, or an area where desktop groups are located, or an area where application icons are located.
S202, judging whether the desktop group where the target position is located or the desktop has the dragged application program icon.
Further, the area range of which desktop group the target position belongs to can be judged, so that the desktop group where the target position is located is determined. And then, whether the desktop group in which the target position is located or the desktop has the dragged application icon or not can be judged according to the corresponding relation between the desktop group and the application icon included in the desktop group.
S203, if the icon exists, prompting the user that the target position cannot create the dragged application icon.
Therefore, two icons of the same application program cannot be added into the same desktop group, and management confusion and space waste can be avoided.
For example, as shown in fig. 2b, the trace of the dragging operation is from M point to N point in the figure. The M point is the initial position of the dragged application icon a. Point N is the target location of the dragged application icon a. The point N is located at the desktop group label 1, but the desktop group label 1 does not have the application program icon a, so that the current application existing in the label 1 can be prompted, namely the user is prompted to be incapable of dragging the icon. Thus, it can be ensured that only one icon for a certain application exists on the same desktop group or desktop.
And S204, if the icon does not exist, moving the dragged application icon to the target position.
Specifically, if the desktop group in which the target location is located does not have the dragged application icon, the dragged application icon may be added to the desktop group in which the target location is located.
If the dragged application icon does not exist on the desktop where the target location is located, the dragged application icon may be placed at the target location.
If another application icon currently exists on the desktop where the target location is located, the another application icon and the dragged application icon can be combined into a new desktop group and placed at the target location.
For example, as shown in fig. 2c, the trace of the drag operation is from M point to N point in the figure. The M point is the initial position of the dragged application icon a. Point N is the target location of the dragged application icon a. The point N is located at the desktop group "label 1", and if the application icon a does not exist in the desktop group "label 1", the dragged application icon a may be added to the desktop group "label 1".
It should be appreciated that in one embodiment of the present application, moving the dragged application icon to the target location refers to copying the dragged application icon and placing the copied icon at the target location, while the dragged application icon still exists at its original location.
In another embodiment of the present application, the dragged application icon is moved to the target position, or the dragged application icon is moved from its initial position to the target position. That is, the dragged application icon no longer exists at its initial position.
The user can select any one of the two modes as desired.
In another embodiment of the present application, the group to which the application icon belongs may be controlled by a delete operation, i.e., the operation instruction is an icon delete operation. Specifically, the user can call the icon deletion interface through a preset operation. For example, the icon deletion interface can be invoked by long-pressing the desktop, or long-pressing groups of the desktop, or long-pressing the application icon, etc. The icon deleting interface is provided with a deleting button, and a user can input icon deleting operation by triggering the deleting button. For example, fig. 3a is a schematic diagram of an icon deletion interface according to an embodiment of the present application.
Therefore, whether the icon can be newly built or not can be determined by judging whether the icon of the same application program exists in the target position of the newly built icon or not, and management confusion and space waste can be effectively avoided.
FIG. 3b is a flowchart of managing the deletion of application icons according to an embodiment of the present application.
As shown in fig. 3b, the deletion management of the application icon includes the following steps.
S301, judging whether the application program icon to be deleted is the last icon of the corresponding application program.
S302, if the icon is the last icon of the corresponding application program, the icon of the application program to be deleted is deleted, and meanwhile, the corresponding application program is deleted.
And S303, if the icon is not the last icon of the corresponding application program, deleting the icon of the application program to be deleted.
For example, fig. 3c is a schematic diagram illustrating deletion management of an application icon according to an embodiment of the present application. As shown in fig. 3c, when the user presses the "tab 1" group of the desktop for a long time in the desktop, the icon deletion interface of the "tab 1" group of the desktop may be entered. When the user clicks the icon b in the icon deletion interface of the desktop group "tab 1", since the icon b still exists in the desktop, the icon b in "tab 1" is not the last icon of the application b, and only the icon b in "tab 1" can be deleted. When the user returns to the desktop, the user can call up the icon deletion interface corresponding to the desktop again and click the icon b, at the moment, the icon b on the desktop is the last icon of the application program b, and therefore when the icon b on the desktop is deleted, the application program b is deleted at the same time.
Therefore, the one-to-many relation between the application programs and the icons can be established, the user requirements can be met, whether the application programs are only deleted or deleted at the same time can be determined according to the number of the icons corresponding to the application programs, and the fact that the corresponding application programs are deleted only when the last icon in the system is deleted is achieved.
In another embodiment of the present application, the application icons in the mobile terminal can be managed through a management interface provided by the application in the mobile terminal or the PC.
FIG. 4 is a schematic diagram of a management interface provided by an application according to one embodiment of the present application. As shown in fig. 4, the management interface may include an application presentation area P and an icon layout presentation area Q.
The application program display area P provides a list of acquired application programs, and whether each application program in the list is currently installed and a label (desktop group) to which the application program belongs.
The layout of the current application icons is provided in the icon layout exposure area Q, including the desktop layout (main menu layout) and the layout in each desktop group (tab). That is, the icon layout display area Q provides the existing application icons in the desktop and the desktop groups, and provides the application icons included in each desktop group. In addition, the icon layout display area Q may provide a correspondence of desktops to application icons and desktop groupings, as well as a correspondence of desktop groupings to diameters of application icons included therein.
In the embodiment of the application, an operation instruction of a user can be received through the application program display area; or receiving an operation instruction of a user through the icon layout display area; or receiving an operation instruction of a user through the application program display area and the icon layout display area.
Fig. 5a to 5d are schematic diagrams illustrating icon management in a mobile terminal through a management interface provided by an application according to an embodiment of the present application. Here, a management interface in the PC side is taken as an example for explanation. The PC side has previously synchronized the correspondence between desktop packets (labels) on the mobile device and application icons.
As shown in fig. 5a, when the user clicks the add-on button "+" of the application 1 in the application list displayed in the application display region P, the setting float may pop up. The user can select the tag to be added to the application program 1 from the existing tags in the setting floating layer, and after the user selects the tag, the icon of the application program 1 can be displayed in the tag list corresponding to the icon layout display area Q and can be synchronized to the mobile device. Or, the user may select to create a new tab for the application program 1 in the setting floating layer, and after the user selects the new tab group, a new tab group may be added in the icon layout display area Q, so that the user selects the new tab name, and the icon of the application program 1 is displayed in the new tab group.
As shown in fig. 5b, the user may add a label to the dragged application by dragging the application in the application list in the application display area P to a certain grouped page in the right icon layout display area Q.
When the user needs to delete the tab of the application program, the user can right click the target tab position of the target application program in the application program display area P to invoke the delete control, as shown in fig. 5 c. Alternatively, as shown in fig. 5d, the icon of the target application program may be dragged out of the range of the target label directly in the right icon layout display area Q.
It should be understood that the management operation of the application icons by the PC terminal or the mobile terminal can be synchronized to other terminals logging in the same user account. As shown in fig. 5e, when the PC connects to another device, the user may be prompted to "synchronize the tag information of the application", and if the user clicks to confirm the synchronization information, the modified application icon grouping information of the PC may be synchronized into the device.
To sum up, the method for managing application icons in a mobile terminal according to the embodiment of the present application can obtain application icons corresponding to applications, and correspondingly control the applications according to an operation instruction of a user, so that the icons of the applications are respectively located in different desktop groups, and only one icon exists in each desktop group, thereby implementing displaying the icon of the same application in the multiple desktop groups, and completing management of the icon of the same application in the multiple desktop groups through simple operations, which is more convenient and easy to operate.
Corresponding to the embodiment of the method for managing the application program icons in the mobile terminal, the application also provides a device for managing the application program icons in the mobile terminal. Since the management apparatus for application icons in a mobile terminal provided in the embodiment of the present application corresponds to the management method for application icons in a mobile terminal provided in the above embodiment, the implementation of the management method for application icons in the foregoing mobile terminal is also applicable to the management apparatus for application icons in a mobile terminal provided in the embodiment, and will not be described in detail in the embodiment.
Fig. 6 is a schematic structural diagram of an apparatus for managing application icons in a mobile terminal according to an embodiment of the present application.
As shown in fig. 6, the apparatus for managing application icons in a mobile terminal according to an embodiment of the present application includes: an acquisition module 10, a receiving module 20 and a control module 30.
Specifically, the obtaining module 10 is configured to obtain a plurality of application icons corresponding to application programs in the mobile terminal, where the application icons are respectively located in different desktop groups, and only one application icon may exist in one desktop group.
In one embodiment of the present application, one or more icons may be created for each application based on the actual needs of the user. The user can put the established icons into different desktop groups respectively according to the needs.
It should be noted that, for the same application, only one icon of the application can exist in the same desktop group, and a plurality of icons cannot exist simultaneously.
For example, application a has 3 corresponding icons. The three icons can be placed into three desktop groupings, respectively, and neither of the three icons can be placed into the same desktop grouping.
That is, there is a one-to-many relationship between the application and the icon. In the process of deleting the icons of the application programs, when the last icon of the application program is deleted, and the other one only deletes the icon of the application program.
In embodiments of the present application, a correspondence between a desktop grouping and the icons it includes may be established. For example, if icons of applications a and b are included in desktop group 1, then desktop group 1 corresponds to icons a and b. If icons of the applications a, b, d and h are included in the desktop group 2, the desktop group 2 corresponds to the icons a, b, d and h.
The receiving module 20 is used for receiving an operation instruction of a user.
In the embodiment of the application, the operation instruction of the user may include a drag operation, an icon deletion operation, an icon adding operation, and the like.
It should be understood that a management interface may be provided through the mobile terminal or the PC side application, and the receiving module 20 receives an operation instruction of the user through the management interface. The application program may be an icon management program built in the system, or an application management program selected and installed by the user.
The control module 30 is configured to perform corresponding control on the application program and the plurality of application program icons according to the operation instruction.
Specifically, in an embodiment of the present application, the control module 30 may control the group to which the application icon belongs through a dragging operation, that is, the operation instruction is a dragging operation. The control module 30 may be specifically configured to perform the steps shown in fig. 2 a.
In another embodiment of the present application, the control module 30 may control the group to which the application icon belongs by a deletion operation, that is, the operation instruction is an icon deletion operation. Specifically, the user can call the icon deletion interface through a preset operation. For example, the icon deletion interface can be invoked by long-pressing the desktop, or long-pressing groups of the desktop, or long-pressing the application icon, etc. The icon deleting interface is provided with a deleting button, and a user can input icon deleting operation by triggering the deleting button. The control module 30 may be specifically adapted to perform the steps illustrated in fig. 3 b.
In another embodiment of the present application, the application icons in the mobile terminal can be managed through a management interface provided by the application in the mobile terminal or the PC. As shown in fig. 4, the management interface may include an application presentation area P and an icon layout presentation area Q.
In an embodiment of the present application, the receiving module 20 may receive an operation instruction of a user through the application program display area; or receiving an operation instruction of a user through the icon layout display area; or receiving an operation instruction of a user through the application program display area and the icon layout display area.
Fig. 5a to 5d are schematic diagrams illustrating icon management in a mobile terminal through a management interface provided by an application according to an embodiment of the present application.
Here, a management interface in the PC side is taken as an example for explanation. The PC side has previously synchronized the correspondence between desktop packets (labels) on the mobile device and application icons.
As shown in fig. 5a, when the user clicks the add-on button "+" of the application 1 in the application list displayed in the application display region P, the setting float may pop up. The user can select the tag to be added to the application program 1 from the existing tags in the setting floating layer, and after the user selects the tag, the icon of the application program 1 can be displayed in the tag list corresponding to the icon layout display area Q and can be synchronized to the mobile device. Or, the user may select to create a new tab for the application program 1 in the setting floating layer, and after the user selects the new tab group, a new tab group may be added in the icon layout display area Q, so that the user selects the new tab name, and the icon of the application program 1 is displayed in the new tab group.
As shown in fig. 5b, the user may add a label to the dragged application by dragging the application in the application list in the application display area P to a certain grouped page in the right icon layout display area Q.
As shown in fig. 5c, when the user needs to delete the tab of the application program, the user can right click the position of the target tab of the target application program in the application program display area P to invoke the delete control; or directly dragging the icon of the target application program out of the range of the target label in the right icon layout display area Q.
It should be understood that the management operation of the application icons by the PC terminal or the mobile terminal can be synchronized to other terminals logging in the same user account. As shown in fig. 5d, when the PC is connected to other devices, the user may be prompted to "synchronize the tag information of the application", and if the user clicks to confirm the synchronization information, the modified application icon grouping information of the PC may be synchronized into the device.
To sum up, the management device for application icons in a mobile terminal according to the embodiment of the present application can obtain application icons corresponding to applications, and correspondingly control the applications according to an operation instruction of a user, so that the icons of the applications are respectively located in different desktop groups, and only one icon exists in each desktop group, thereby implementing that the icons of the same application are displayed in the multiple desktop groups, and the management of the icons of the same application in the multiple desktop groups corresponding to the same application can be completed through a simple operation, which is more convenient and easy to operate.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and the scope of the preferred embodiments of the present application includes other implementations in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present application.
The logic and/or steps represented in the flowcharts or otherwise described herein, e.g., an ordered listing of executable instructions that can be considered to implement logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
It should be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.
In addition, functional units in the embodiments of the present application may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may also be stored in a computer readable storage medium.
The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc.
In the description herein, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
While embodiments of the present application have been shown and described, it will be understood by those of ordinary skill in the art that: various changes, modifications, substitutions and alterations can be made to the embodiments without departing from the principles and spirit of the application, the scope of which is defined by the claims and their equivalents.