CN114816169B

CN114816169B - Desktop icon display method and device and storage medium

Info

Publication number: CN114816169B
Application number: CN202210749882.6A
Authority: CN
Inventors: 郭佳民
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2022-06-29
Filing date: 2022-06-29
Publication date: 2022-11-04
Anticipated expiration: 2042-06-29
Also published as: CN114816169A

Abstract

The application provides a desktop icon display method, desktop icon display equipment and a storage medium. In the method, the simplified desktop icons corresponding to the desktop icons are obtained, and the simplified desktop icons are fused with the current desktop background, so that the desktop background is shielded by the desktop icons as little as possible, and the visual experience effect of a user is improved.

Description

Desktop icon display method and device and storage medium

Technical Field

The present application relates to the field of electronic technologies, and in particular, to a method and an apparatus for displaying a desktop icon, and a storage medium.

Background

At present, electronic devices are occupying an increasingly important position in people's lives. In order to achieve an attractive appearance, a user usually selects a favorite picture as a desktop background (wallpaper), but as more and more application programs can be installed in the electronic device, desktop icons and application names corresponding to the application programs seriously block the desktop background, and the visual experience effect of the user is seriously influenced.

Disclosure of Invention

In order to solve the technical problem, the application provides a desktop icon display method, a desktop icon display device and a desktop icon storage medium, and aims to fuse the desktop icon and a desktop background so that the desktop background is shielded by the desktop icon as little as possible, and therefore the visual experience effect of a user is improved.

In a first aspect, the present application provides a method for displaying desktop icons. The method comprises the following steps: displaying a first interface, wherein a first background and a first desktop icon are displayed in the first interface, and the first desktop icon is located at a first position and blocks a first area of the first background at the first position; and responding to the first operation, replacing the first desktop icon at the first position with a second desktop icon, and fusing the second desktop icon with the content of the first area.

The first interface is, for example, an interface corresponding to a desktop (or a main page) of the electronic device.

The first desktop icon is a desktop icon corresponding to an application program needing to be displayed on a desktop in the electronic device.

Illustratively, the first desktop icon is an original desktop icon provided by the application site, and includes, for example, a regularly-shaped border, a background color, a graphic line, and the like.

In addition, the first desktop icon may be one or more.

For example, when a plurality of first desktop icons are provided, the content of each first desktop icon is different, and each first desktop icon corresponds to a different application program. For example, the first desktop icon may be a desktop icon corresponding to a camera application, a desktop icon corresponding to a calendar application, a desktop icon corresponding to a map application, and the like, which are not listed here, and this application is not limited thereto.

The first background is, for example, wallpaper displayed on the current desktop of the electronic device.

And the second desktop icon corresponds to the same application program as the first desktop icon.

The second desktop icon and the first background are fused, namely the second desktop icon can shield the first background as little as possible compared with the first desktop icon, and can be fused with the first background into a whole visually.

The first operation may be an operation performed when the user starts the function of displaying the simplified desktop icon by using any one of the function modes of starting the display of the simplified desktop icon. For a way to turn on the function of displaying the simplified desktop icon, see the description below.

Therefore, the first desktop icon displayed in the first interface and corresponding to the same application program is replaced by the second desktop icon which can shield the first background as little as possible and can be fused with the first background into a whole visually, and the visual experience effect of a user is improved.

According to a first aspect, prior to replacing the first desktop icon at the first location with the second desktop icon, the method further comprises: acquiring an application name of an application program corresponding to the first desktop icon; searching a simplified desktop icon corresponding to the application name in a local desktop icon database, wherein the simplified desktop icon is a desktop icon simplified based on the first desktop icon; if the simplified desktop icon corresponding to the application name is found in the local desktop icon database, fusing the simplified desktop icon with the content of the first area to obtain a second desktop icon; if the simplified desktop icon corresponding to the application name is not found in the local desktop icon database, acquiring a user-defined simplified desktop icon; and fusing the user-defined simplified desktop icon with the content of the first area to obtain a second desktop icon.

The simplified desktop icon may be, for example, a desktop icon with a border and a background color removed in a regular shape and only a graphic line reserved.

The simplified desktop icons stored in the local desktop icon database may be actively obtained from the cloud desktop icon database according to a preset period, or the original desktop icons are processed by the electronic device and then stored locally before the function of displaying the simplified desktop icons is started.

The simplified desktop icons stored in the local desktop icon database can be actively sent to the electronic device by the cloud according to a preset period or a preset condition.

The simplified desktop icons stored in the cloud desktop icon database may be generated and managed in a manner of generating simplified desktop icons, which is described below, for example.

Before the user-defined simplified desktop icon is obtained, the user-defined simplified desktop icon can be searched in a cloud desktop icon database according to the application name, if the user-defined simplified desktop icon is found, the searched simplified desktop icon is updated to a local desktop icon database, and if the user-defined simplified desktop icon cannot be obtained through searching.

The customized simplified desktop icon can be drawn by the user, or can be a general simplified desktop icon pre-stored in a local desktop icon database or a cloud desktop icon database.

Therefore, no matter the simplified desktop icon is found or the simplified desktop icon is customized, the simplified desktop icon can be fused with the first background, the first background can be shielded as little as possible, and the second desktop icon can be fused with the first background into a whole visually.

In addition, because the second desktop icon is obtained by fusing the simplified desktop icon and the first background, the second desktop icon finally displayed on the first interface can be ensured to be simpler, so that the first interface looks cleaner and tidier, and the visual experience effect of a user is improved.

According to the first aspect, or any implementation manner of the first aspect, fusing the simplified desktop icon with the content of the first area to obtain a second desktop icon, includes: extracting a gray value of the first area, and performing fuzzification processing on the gray value of the first area to obtain a fuzzy gray value of the first area; extracting a gray value of the simplified desktop icon, and performing fuzzification processing on the gray value of the simplified desktop icon to obtain a fuzzy gray value of the simplified desktop icon; and performing overlapping fitting on the fuzzy gray value of the first area and the fuzzy gray value of the simplified desktop icon to obtain a second desktop icon.

The first region is, for example, a desktop background region in a desktop background, which is described below, so that the blurring process of the gray values of the first region and the simplified desktop icons specifically blurs the gray values belonging to the same gray value distribution range into a gray value, such as the gray value located in the middle region in the gray value distribution range.

Therefore, the gray value included by each simplified desktop icon and the corresponding desktop background area can be reduced, the main contents of the simplified icons and the desktop background area are reserved as far as possible, and meanwhile, the second desktop icon based on the fusion of the simplified icons and the desktop background area can be better fused with the first background into a whole.

According to the first aspect, or any implementation manner of the first aspect, the blurred grayscale value of the background area and the blurred grayscale value of the simplified desktop icon are subjected to overlap fitting based on the following formula:

wherein the content of the first and second substances,

coordinates of pixel points representing the same location in the first region and the simplified desktop icon,

in the first area

The blurred gray values corresponding to the pixel points of the location,

in the icon representing simplified desktop

The blurred gray values corresponding to the pixel points of the location,

representing the gray values after gray value fitting.

According to the first aspect, or any implementation manner of the first aspect, the obtaining a customized simplified desktop icon includes: responding to a second operation, and displaying a second interface, wherein the second interface comprises a simplified desktop icon drawing area; and responding to the third operation, acquiring the desktop icon drawn in the simplified desktop icon drawing area, and taking the desktop icon as a self-defined simplified desktop icon.

The second operation is, for example, an operation in which the user clicks a desktop popup to remind the user that there is no simplified desktop icon corresponding to the first desktop icon, or an operation in which the application opens the second interface through a desktop icon simplification module described below.

The second interface can also comprise a control for determining the use of the desktop icon drawn by the user, so that when the user clicks the control, a third operation is triggered.

Therefore, the user can conveniently set the simplified desktop icons meeting the use requirements of the user according to the requirements by providing the user with an entrance for drawing the customized simplified desktop icons.

According to a first aspect, or any implementation of the first aspect above, after replacing the first desktop icon at the first location with the second desktop icon, the method further comprises: and replacing the second desktop icon at the first position with the first desktop icon in response to the fourth operation.

The fourth operation may be an operation performed when the user closes the function of displaying the simplified desktop icon by using any one of the function manners of closing the display of the simplified desktop icon. For ways to turn off the function of displaying the simplified desktop icon, see the description below.

Therefore, after the user closes the function of displaying the simplified desktop icons, the desktop icons displayed on the first interface can be restored to the style of the first desktop icons, so that the desktop icons corresponding to each application program are clearly visible, the user can conveniently check the operation, and the mistaken touch is avoided.

According to a first aspect, or any implementation of the first aspect above, after replacing the first desktop icon at the first location with the second desktop icon, the method further comprises: in response to a fifth operation, replacing the first background with a second background, wherein the second desktop icon occludes a second area of the second background at the first position; and replacing the second desktop icon at the first position with a third desktop icon, wherein the third desktop icon is fused with the content of the second area.

Wherein the fifth operation may be an operation of the user to switch the first background, i.e., the wallpaper.

Wherein the second background is wallpaper different from the first background.

And the third desktop icon corresponds to the same application program as the second desktop icon.

The second area and the first area are areas of different desktop backgrounds corresponding to the same position in the first interface.

The third desktop icon and the second background are fused, namely the third desktop icon can shield the second background as little as possible compared with the second desktop icon, and can be fused with the second background into a whole visually.

Because the first background is different from the wallpaper corresponding to the second background, and the second desktop icon is fused with the first background, when the second background is switched to, the second desktop icon cannot be fused with the second background and shields the second background, so that the second background can be shielded as little as possible by replacing the second desktop icon with the third desktop icon fused with the second background, and the visual experience effect of the user can be ensured after the wallpaper is changed.

Regarding the processing manner for replacing the second desktop icon with the third desktop icon, the processing manner is similar to the processing manner for replacing the first desktop icon with the second desktop icon, and specific implementation details may be referred to the above description, and are not described herein again.

According to a first aspect, or any implementation of the first aspect above, after replacing the first desktop icon at the first location with the second desktop icon, the method further comprises: responding to the sixth operation, installing the application program, and displaying a fourth desktop icon in the first interface after the application program is successfully installed, wherein the fourth desktop icon is a desktop icon of the application program and is located at the second position, and the third area of the first background at the second position is shielded by the fourth desktop icon; and replacing the fourth desktop icon at the second position with a fifth desktop icon, and fusing the fifth desktop icon with the content of the third area.

Wherein the sixth operation may be an operation of downloading and installing a new application.

And the fourth desktop icon is a desktop icon corresponding to the newly installed application program.

Because the fourth desktop icon is a desktop icon corresponding to the newly installed application program, that is, an original desktop icon provided by a manufacturer of the application program, in this case, the fourth desktop icon cannot be fused with the first background and blocks the first background, when the fourth desktop icon of the newly installed application program is detected to appear on the first interface, the fourth desktop icon is replaced by a fifth desktop icon fused with the first background, so that the first background can be blocked as little as possible, and the visual experience effect of the user can be ensured after the new desktop icon is added to the first interface.

Regarding the processing manner of replacing the fourth desktop icon with the fifth desktop icon, the processing manner of replacing the first desktop icon with the second desktop icon is similar, and specific implementation details may be referred to the above description, and are not described herein again.

According to a first aspect, or any implementation of the first aspect above, after replacing the first desktop icon at the first location with the second desktop icon, the method further comprises: in response to a seventh operation, interchanging the positions of the second desktop icon at the first position and the fifth desktop icon at the second position; and replacing the fifth desktop icon at the second position with a sixth desktop icon, replacing the second desktop icon at the first position with a seventh desktop icon, fusing the sixth desktop icon with the content of the first area, and fusing the seventh desktop icon with the content of the third area.

The seventh operation may be an operation of interchanging the positions of any two desktop icons displayed in the first interface, such as interchanging the positions of the second desktop icon and the fifth desktop icon as described above.

The sixth desktop icon and the fifth desktop icon correspond to the same application program, but are located at the position of the second desktop icon; the seventh desktop icon is the same as the application program corresponding to the second desktop icon, but the position of the seventh desktop icon is the position of the fifth desktop icon.

Because the color and the content of the background area of the first background at the position of the second desktop icon are possibly different from the color and the content of the background area of the first background at the position of the fifth desktop icon, after the positions of the second desktop icon and the fifth desktop icon are exchanged, the second desktop icon and the fifth desktop icon are possibly not fused with the first background to shield the first background, and after the positions of the second desktop icon and the fifth desktop icon are exchanged, the fifth desktop icon is replaced by the sixth desktop icon, and the second desktop icon is replaced by the seventh desktop icon, so that the first background can be shielded as little as possible, and the visual experience effect of a user can be ensured after new desktop icons are added to the first interface.

Regarding the processing manner of replacing the fifth desktop icon with the sixth desktop icon and the processing manner of replacing the second desktop icon with the seventh desktop icon, both are similar to the processing manner of replacing the first desktop icon with the second desktop icon, and specific implementation details may refer to the above description, which is not described herein again.

According to a first aspect, or any implementation of the first aspect above, after replacing the first desktop icon at the first location with the second desktop icon, the method further comprises: in response to the eighth operation, deleting the second desktop icon at the first position; moving a fifth desktop icon at the second location to the first location; and replacing the fifth desktop icon at the first position with a sixth desktop icon, wherein the sixth desktop icon is fused with the content of the first area.

Wherein, the eighth operation may be an operation of deleting any one or several desktop icons.

And the sixth desktop icon is the same as the application program corresponding to the fifth desktop icon, but the position of the sixth desktop icon is the position of the second desktop icon.

Due to the fact that any one or more desktop icons are deleted, the desktop icons displayed in the first interface are rearranged, for example, the rearranged positions are generally moved forward in sequence of the desktop icons behind the deleted desktop icons, in this case, the rearranged desktop icons cannot be fused with the first background, and the first background is shielded, so that after the second desktop icon is deleted, the fifth desktop icon is replaced by the sixth desktop icon fused with the first background, the first background can be shielded as little as possible, and the visual experience effect of a user can be guaranteed after new desktop icons are added to the first interface.

Regarding the processing manner for replacing the fifth desktop icon with the sixth desktop icon, the specific implementation details may refer to the above description, and are not described herein again, similar to the processing manner for replacing the first desktop icon with the second desktop icon.

In a second aspect, the present application provides an electronic device. The electronic device includes: a memory and a processor, the memory and the processor coupled; the memory stores program instructions that, when executed by the processor, cause the electronic device to perform the instructions of the first aspect or any possible implementation of the first aspect.

In a third aspect, the present application provides a computer readable medium for storing a computer program comprising instructions for performing the method of the first aspect or any possible implementation manner of the first aspect.

In a fourth aspect, the present application provides a computer program comprising instructions for carrying out the method of the first aspect or any possible implementation manner of the first aspect.

In a fifth aspect, the present application provides a chip comprising a processing circuit, a transceiver pin. Wherein the transceiver pin and the processing circuit are in communication with each other via an internal connection path, and the processing circuit is configured to perform the method of the first aspect or any one of the possible implementations of the first aspect to control the receiving pin to receive signals and to control the sending pin to send signals.

Drawings

Fig. 1 is a schematic diagram of an exemplary application scenario;

fig. 2 is a schematic diagram illustrating a hardware structure of a mobile phone;

fig. 3 is a schematic diagram of a software structure of an exemplary mobile phone;

FIG. 4 is a schematic diagram of an exemplary application scenario;

FIG. 5 is a schematic diagram of an exemplary application scenario;

FIG. 6 is a schematic diagram of an exemplary application scenario;

FIG. 7 is a schematic diagram illustrating exemplary interaction between a mobile phone and a cloud to obtain a simplified desktop icon;

FIG. 8 is a flowchart illustrating a method for displaying desktop icons according to an embodiment of the present application;

FIG. 9 is a schematic diagram of an exemplary gray value distribution;

fig. 10 is a flowchart illustrating a specific implementation of step S108 in fig. 8;

FIG. 11 is a diagram illustrating an exemplary extraction of desktop icons and background areas where the desktop icons are located;

FIG. 12a is a diagram illustrating an exemplary grayscale value extracted from a background region;

FIG. 12b is a simplified schematic diagram illustrating the blurring of gray scale values of a background region;

FIG. 13 is a schematic diagram illustrating an exemplary blurred simplification of the grayscale values of desktop icons;

FIG. 14 is a diagram illustrating an exemplary desktop icon after gray-value overlapping the background area shown in FIG. 12b and the desktop icon shown in FIG. 13;

fig. 15 is an interaction diagram of each module when the display method of a desktop icon provided by the embodiment of the present application is implemented.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, of the embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone.

The terms "first" and "second," and the like, in the description and in the claims of the embodiments of the present application are used for distinguishing between different objects and not for describing a particular order of the objects. For example, the first target object and the second target object, etc. are specific sequences for distinguishing different target objects, rather than describing target objects.

In the embodiments of the present application, words such as "exemplary" or "for example" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

In the description of the embodiments of the present application, the meaning of "a plurality" means two or more unless otherwise specified. For example, a plurality of processing units refers to two or more processing units; the plurality of systems refers to two or more systems.

Before describing the technical solution of the embodiment of the present application, a description is first given of a display scheme of an existing desktop icon (an icon of an application program displayed on a desktop) with reference to the accompanying drawings.

With the popularization of electronic devices, the number of functions supported by the electronic devices is increased, and the number of applications allowed to be installed is increased. At present, many users pursue a great way to a simple style, do not like an application of displaying icons (icons) on a desktop in a particularly fancy manner, and some users want the desktop to be capable of displaying favorite wallpaper completely, that is, the content of the wallpaper is shielded by the applied icons as little as possible. The mainstream way for displaying the current application icon on the desktop is to use a rectangular picture (or other regular shape) + the application name.

The following description will take a hand as an example, and explain the mainstream desktop icon display scheme with reference to fig. 1, and also take other electronic devices as an example, which will not be described again.

Referring to fig. 1, for example, when a desktop (or a main page) of a mobile phone displays a wallpaper 10a as shown in fig. 1, and desktop icons of installed applications, such as the icons 10b-1 to 10b-20 shown in fig. 1, are displayed in the page, because there are many installed applications, the icons (the icons 10b-1 to 10 b-20) occupy a larger display area of the desktop, so that the wallpaper 10a of the desktop is blocked by a large area and cannot be completely displayed, thereby resulting in a poor visual experience effect for a user.

It should be noted that, in practical applications, the wallpaper 10a may be a picture obtained by the user from a network according to personal preferences, may also be a picture obtained from a local gallery, and may also be a picture taken through a camera, which is not limited in this embodiment.

In addition, the desktop icons displayed on the desktop are not limited to the number shown in fig. 1.

In addition, the specific pictures corresponding to each desktop icon are different, and fig. 1 is only for convenience of illustration, and therefore the desktop icon is represented by a letter "a", but in actual application, the desktop icons corresponding to different applications are different.

It should be understood that the above description is only an example for better understanding of the technical solution of the present embodiment, and is not to be taken as the only limitation of the present embodiment.

Based on the technical problems of the existing desktop icon display scheme described above, the desktop icon display method and the electronic device provided by the embodiment of the application are provided, and the desktop icon and the desktop background (wallpaper) are fused, so that the desktop background is shielded by the desktop icon as little as possible, and the visual experience effect of a user is improved.

In order to better describe the desktop icon display method and the electronic device provided in the embodiment of the present application, taking the electronic device as a mobile phone as an example, a hardware structure and a software structure of the mobile phone are described with reference to fig. 2 and 3, respectively.

Referring to fig. 2, a schematic diagram of a hardware structure of the mobile phone 100 is shown.

As shown in fig. 2, the cellular phone 100 may include: the mobile terminal includes a processor 110, an external memory interface 120, an internal memory 121, a Universal Serial Bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, a Subscriber Identity Module (SIM) card interface 195, and the like.

For example, in some implementations, the sensor module 180 may include a pressure sensor, a gyroscope sensor, a barometric pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, etc., which are not limited herein.

Furthermore, it should be noted that the processor 110 may include one or more processing units, such as: the processor 110 may include an Application Processor (AP), a modem processor, a Graphics Processing Unit (GPU), an Image Signal Processor (ISP), a controller, a memory, a video codec, a Digital Signal Processor (DSP), a baseband processor, and/or a neural-Network Processing Unit (NPU), etc. The different processing units may be separate devices or may be integrated into one or more processors.

It is understood that the controller may be the neural center and the command center of the cell phone 100. In practical application, the controller can generate an operation control signal according to the instruction operation code and the timing signal to complete the control of instruction fetching and instruction execution.

It should also be noted that the processor 110 may be provided with a memory for storing instructions and data. In some implementations, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that have just been used or recycled by the processor 110. If the processor 110 needs to use the instruction or data again, it can be called directly from the memory. Avoiding repeated accesses reduces the latency of the processor 110, thereby increasing the efficiency of the system.

For example, in some implementations, processor 110 may include one or more interfaces. The interface may include an integrated circuit (I2C) interface, an integrated circuit built-in audio (I2S) interface, a Pulse Code Modulation (PCM) interface, a universal asynchronous receiver/transmitter (UART) interface, a Mobile Industry Processor Interface (MIPI), a general-purpose input/output (GPIO) interface, a Subscriber Identity Module (SIM) interface, and/or a Universal Serial Bus (USB) interface, etc.

Continuing with fig. 2, the charge management module 140 is illustratively configured to receive a charging input from a charger. The charger may be a wireless charger or a wired charger. In some wired charging implementations, the charging management module 140 may receive charging input from a wired charger via the USB interface 130. In some wireless charging implementations, the charging management module 140 can receive a wireless charging input through a wireless charging coil of the cell phone 100. The charging management module 140 can also supply power to the mobile phone 100 through the power management module 141 while charging the battery 142.

Continuing to refer to fig. 2, the power management module 141 is illustratively coupled to the battery 142, the charge management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and/or the charge management module 140 and provides power to the processor 110, the internal memory 121, the external memory, the display 194, the camera 193, the wireless communication module 160, and the like. The power management module 141 may also be used to monitor parameters such as battery capacity, battery cycle count, battery state of health (leakage, impedance), etc. In other implementations, the power management module 141 may also be disposed in the processor 110. In other implementations, the power management module 141 and the charging management module 140 may also be disposed in the same device.

Continuing to refer to fig. 2, the wireless communication function of the handset 100 can be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor, the baseband processor, and the like.

It should be noted that the antenna 1 and the antenna 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the handset 100 may be used to cover a single or multiple communication bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed as a diversity antenna of a wireless local area network. In other implementations, the antenna may be used in conjunction with a tuning switch.

Continuing to refer to fig. 2, for example, the mobile communication module 150 may provide a solution for wireless communication including 2G/3G/4G/5G, etc. applied to the handset 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a Low Noise Amplifier (LNA), and the like. The mobile communication module 150 may receive the electromagnetic wave from the antenna 1, filter, amplify, etc. the received electromagnetic wave, and transmit the electromagnetic wave to the modem processor for demodulation. The mobile communication module 150 may also amplify the signal modulated by the modem processor, and convert the signal into electromagnetic wave through the antenna 1 to radiate the electromagnetic wave. In some implementations, at least some of the functional modules of the mobile communication module 150 may be provided in the processor 110. In some implementations, at least some of the functional modules of the mobile communication module 150 may be provided in the same device as at least some of the modules of the processor 110.

Further, it should be noted that the modem processor may include a modulator and a demodulator. The modulator is used for modulating a low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then passes the demodulated low frequency baseband signal to a baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.) or displays an image or video through the display screen 194. In some implementations, the modem processor may be a stand-alone device. In other implementations, the modem processor may be provided in the same device as the mobile communication module 150 or other functional modules, independent of the processor 110.

With continued reference to fig. 2, the wireless communication module 160 may provide solutions for wireless communication applied to the mobile phone 100, including Wireless Local Area Networks (WLANs) (e.g., wireless fidelity (Wi-Fi) networks), bluetooth (BT), global Navigation Satellite System (GNSS), frequency Modulation (FM), short-range wireless communication technology (NFC), infrared technology (infrared, IR), and the like. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering on electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, perform frequency modulation and amplification on the signal, and convert the signal into electromagnetic waves through the antenna 2 to radiate the electromagnetic waves.

Specifically, in the technical solution provided in the embodiment of the present application, the mobile phone 100 may communicate with a cloud or other servers through the mobile communication module 150 or the wireless communication module 160. For example, the mobile phone 100 may send a request for obtaining the simplified desktop icon to the cloud through the mobile communication module 150. The cloud may be a server cluster consisting of a plurality of servers.

For example, the simplified desktop icon in this embodiment may be an icon with a background color and a border removed and only a graphic line in the desktop icon is retained. In this way, when the mobile phone 100 subsequently implements the method for displaying the desktop icon provided in the embodiment of the present application, it is not necessary to perform a transparency process on the background color of the desktop icon and to perform an operation of removing a frame.

In addition, it should be noted that the mobile phone 100 implements the display function through the GPU, the display screen 194, and the application processor. The GPU is a microprocessor for image processing, and is connected to the display screen 194 and an application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.

Continuing to refer to FIG. 2, display screen 194 is illustratively used to display images, video, and the like. The display screen 194 includes a display panel. The display panel may adopt a Liquid Crystal Display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (active-matrix organic light-emitting diode, AMOLED), a flexible light-emitting diode (FLED), a miniature, a Micro-oeld, a quantum dot light-emitting diode (QLED), and the like. In some implementations, the cell phone 100 can include 1 or N display screens 194, N being a positive integer greater than 1.

In addition, it should be noted that the mobile phone 100 can implement the shooting function through the ISP, the camera 193, the video codec, the GPU, the display screen 194, the application processor, and the like.

In addition, it should be noted that the ISP is used to process data fed back by the camera 193. For example, when a photo is taken, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing and converting into an image visible to naked eyes. The ISP can also carry out algorithm optimization on noise, brightness and skin color of the image. The ISP can also optimize parameters such as exposure, color temperature and the like of a shooting scene. In some implementations, the ISP may be provided in camera 193.

Further, it is noted that the camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image to the photosensitive element. The photosensitive element may be a Charge Coupled Device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The light sensing element converts the optical signal into an electrical signal, which is then passed to the ISP where it is converted into a digital image signal. And the ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV and other formats. In some implementations, the handset 100 can include 1 or N cameras 193, N being a positive integer greater than 1.

In the technical solution provided in the embodiment of the present application, the wallpaper picture used as the desktop background may be obtained by a user through shooting with the camera 193, for example.

In addition, it should be noted that the digital signal processor is used for processing digital signals, and can also process other digital signals besides digital image signals. For example, when the handset 100 is in frequency bin selection, the digital signal processor is used to perform fourier transform or the like on the frequency bin energy.

In addition, it should be noted that the video codec is used for compressing or decompressing digital video. Handset 100 may support one or more video codecs. Thus, the mobile phone 100 can play or record video in a variety of encoding formats, such as: moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, and the like.

Continuing to refer to fig. 2, for example, the external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to extend the memory capability of the mobile phone 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function. For example, files such as music, video, etc. are saved in an external memory card.

Continuing to refer to FIG. 2, for example, internal memory 121 may be used to store computer-executable program code, which includes instructions. The processor 110 executes various functional applications of the cellular phone 100 and data processing by executing instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area. The storage program area may store an operating system, an application program (such as a sound playing function, an image playing function, and the like) required by at least one function, and the like. The data storage area may store data (e.g., audio data, a phonebook, etc.) created during use of the handset 100, and the like. In addition, the internal memory 121 may include a high-speed random access memory, and may further include a nonvolatile memory, such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (UFS), and the like.

Specifically, in the technical solution provided in this embodiment of the present application, the simplified desktop icons obtained from the cloud or the preset custom desktop icons may be stored in the internal memory 121, so that when the display method of the desktop icons provided in this embodiment of the present application is used, the corresponding desktop icons can be conveniently and quickly obtained from the internal memory 121.

In addition, it should be noted that the mobile phone 100 can implement an audio function through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the earphone interface 170D, and the application processor. Such as music playing, recording, etc.

It should be noted that the audio module 170 is used for converting digital audio information into an analog audio signal and outputting the analog audio signal, and is also used for converting an analog audio input into a digital audio signal. The audio module 170 may also be used to encode and decode audio signals. In some implementations, the audio module 170 may be disposed in the processor 110, or some functional modules of the audio module 170 may be disposed in the processor 110.

With continued reference to fig. 2, exemplary keys 190 include a power on key, a volume key, etc. The keys 190 may be mechanical keys. Or may be touch keys. The cellular phone 100 may receive a key input, and generate a key signal input related to user setting and function control of the cellular phone 100.

Continuing with fig. 2, illustratively, the motor 191 may generate a vibratory cue. The motor 191 may be used for incoming call vibration cues, as well as for touch vibration feedback. For example, touch operations applied to different applications (e.g., photographing, audio playing, etc.) may correspond to different vibration feedback effects. The motor 191 may also respond to different vibration feedback effects for touch operations applied to different areas of the display screen 194. Different application scenes (such as time reminding, receiving information, alarm clock, game and the like) can also correspond to different vibration feedback effects. The touch vibration feedback effect may also support customization.

Continuing to refer to fig. 2, for example, indicator 192 may be an indicator light that may be used to indicate a charge status, a charge change, or a message, missed call, notification, etc.

The hardware architecture of the handset 100 is described herein, it being understood that the handset 100 shown in fig. 2 is merely an example, and in particular implementations, the handset 100 may have more or fewer components than shown, may combine two or more components, or may have a different configuration of components. The various components shown in fig. 2 may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and/or application specific integrated circuits.

In order to better understand the software structure of the mobile phone 100 shown in fig. 2, the following description will be made of the software structure of the mobile phone 100. Before explaining the software structure of the mobile phone 100, first, an architecture that can be adopted by the software system of the mobile phone 100 will be explained.

Specifically, in practical applications, the software system of the mobile phone 100 may adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture.

Furthermore, it is understood that software systems currently used in mainstream electronic devices include, but are not limited to, windows systems, android systems, and iOS systems. For convenience of description, in the embodiment of the present application, an Android system with a layered architecture is taken as an example to exemplarily describe a software structure of the mobile phone 100.

In addition, the desktop icon display scheme provided in the embodiments of the present application is also applicable to other systems in specific implementations.

Referring to fig. 3, a block diagram of a software architecture of the handset 100 is shown.

As shown in fig. 3, the layered architecture of the handset 100 divides the software into several layers, each layer having a clear role and division of labor. The layers communicate with each other through a software interface. In some implementations, the Android system is divided into four layers, which are an application layer, an application framework layer, an Android runtime (Android runtime) and system library, and a kernel layer from top to bottom.

Wherein the application layer may include a series of application packages. As shown in fig. 3, the application package may include applications such as a camera, a calendar, a map, settings, a gallery, music, a desktop icon simplifying module, a desktop Launcher (Launcher), and the like, which are not limited herein.

Understandably, the application programs such as the camera, the calendar, the map, the setting, the gallery, the music and the like have corresponding desktop icons on the desktop of the mobile phone 100, and can be operated and used by the user; while Launcher, which is a User Interface (UI) of the android system, does not have a special desktop icon.

Specifically, in this embodiment, the Launcher is loaded when the mobile phone 100 is started, and then the Launcher loads the desktop icon of the installed application by calling the corresponding programming interface provided in the application framework layer.

For example, the desktop icon loaded by Launcher may be a normal desktop icon (as shown in fig. 1) or a simplified desktop icon merged with the desktop background (as shown in fig. 4 and 5).

For example, launcher loads a normal desktop icon or a simplified desktop icon merged with a desktop background (hereinafter referred to as a simplified desktop icon) by detecting whether the mobile phone 100 is turned on to display the simplified desktop icon.

Accordingly, if the mobile phone 100 opens the function of displaying the simplified desktop icon, launcher calls a corresponding programming interface provided in the application framework layer to implement the method for displaying the desktop icon provided in this embodiment, that is, the desktop icon and the desktop background are displayed in a fused manner.

In addition, it should be noted that, in some implementation manners, if the desktop icon displayed on the desktop of the mobile phone 100 is already a simplified desktop icon processed by using the display method for desktop icons provided in the embodiment of the present application, in this case, if the positions of any several existing desktop icons on the desktop are changed, the Launcher is triggered to call the corresponding programming interfaces provided in the application framework layer to implement the display method for desktop icons provided in the embodiment, and then the desktop icon whose position is changed is fused with the desktop background at the changed position again.

In addition, it should be noted that in other implementation manners, if the desktop icon displayed on the desktop of the mobile phone 100 is already a simplified desktop icon processed by using the display method of the desktop icon provided in the embodiment of the present application, in this case, if a new application is installed by the user, the Launcher is also triggered to call the corresponding programming interface provided in the application framework layer to implement the display method of the desktop icon provided in the embodiment, so as to fuse the desktop icon of the newly installed application with the desktop background.

In addition, it should be further noted that in other implementation manners, if the desktop icon displayed on the desktop of the mobile phone 100 is a simplified desktop icon processed by using the display method for desktop icons provided in the embodiment of the present application, in this case, if the user deletes an application program corresponding to an existing desktop icon, the Launcher will also be triggered to call the corresponding programming interface provided in the application framework layer to implement the display method for desktop icons provided in this embodiment, so that the desktop icon whose position is changed is fused with the desktop background whose position is changed again.

In this embodiment, the desktop icon simplification module may be configured to turn on or turn off a function of displaying the simplified desktop icon. The desktop icon simplification module may be an independent functional module, or may be integrated in a setting application, which is not limited in this embodiment. It can be understood that, in the case that the desktop icon simplification module is an independent functional module, a corresponding desktop icon needs to be provided on the desktop of the mobile phone 100, so that after the user operates the desktop icon corresponding to the desktop icon simplification module, a corresponding page is started, and the user can select to turn on or turn off the function of displaying the simplified desktop icon.

In addition, it should be noted that, in some implementation manners, the simplified desktop icon module may be configured to provide an entry for setting a customized simplified desktop icon in addition to the function of turning on or off the simplified desktop icon, so that a user can set a simplified desktop icon meeting the user demand according to the demand.

In addition, it should be further noted that, in other implementation manners, the desktop icon simplification module may further provide an entry for managing simplified desktop icons stored in the local database, so that a user can conveniently manage, such as delete, simplified desktop icons in the local database according to needs.

In addition, it should be further noted that in other implementations, the function of turning on or turning off the simplified desktop icon may be implemented by a control in a page corresponding to the simplified desktop icon module, or may be determined according to the number of times (for example, 3 times) that the finger joint/finger/stylus pen taps the screen of the mobile phone 100, or the rear shell, or the specified position or any position of the side frame within a set time (for example, 2 s).

In addition, it should be noted that in other implementation manners, the function of displaying the simplified desktop icon may also be determined to be turned on according to a graphic drawn by the finger joint/finger/stylus in any area or a specific area of the screen of the mobile phone 100, for example, a triangle drawn in any area of the screen of the mobile phone 100.

In addition, it should be further noted that in other implementations, the function of displaying the simplified desktop icon may also be determined to be turned on according to the pressing duration of the finger joint/finger/stylus pen in any area or a specific area of the screen of the mobile phone 100, for example, when the designated area of the screen of the mobile phone 100 is pressed for more than 4 seconds.

Correspondingly, when the function of displaying the simplified desktop icon is turned off, the function of displaying the simplified desktop icon may also be turned off according to the number of times (for example, 4 times) that the finger joint/finger/stylus pen taps the screen, or the rear shell, or the designated position or any position of the side frame of the mobile phone 100 within a set time (for example, 2 s); the function of displaying simplified desktop icons can be determined to be closed according to a figure drawn by a finger joint/finger/touch pen in any area or a specific area of the screen of the mobile phone 100, such as a square drawn in any area of the screen of the mobile phone 100; the function of displaying the simplified desktop icon can be determined to be turned off according to the pressing time of the finger joint/finger/stylus pen in any area or a specific area of the screen of the mobile phone 100, for example, when the designated area of the screen of the mobile phone 100 is pressed for more than 5 seconds.

In addition, it should be noted that in other implementations, the manner of turning on or off the function of displaying the simplified desktop icon may also be determined to turn on or off the function of displaying the simplified desktop icon by some mechanical keys of the mobile phone 100, for example, by pressing the volume up key and/or the volume down key for 3 seconds for a long time within 2 seconds, or by pressing the simplified desktop icon several times (for example, 3 times) consecutively within a set time (for example, 3 seconds).

The application framework layer provides an Application Programming Interface (API) and a programming framework for the application program of the application layer.

Wherein the application framework layer comprises a number of predefined functions. As shown in fig. 3, the application framework layer may include a window manager, a notification manager, a content provider, a resource manager, a view system, a data model (hereinafter, referred to as launcher model), a loading module (hereinafter, referred to as loader task), an icon cache update processing module (hereinafter, referred to as IconCacheUpdateHandler), and the like, which are not limited herein.

In this embodiment, the Launcher model provides some list of API interfaces for Launcher calls, such as loadandbindworkbench, which informs LoaderTask to load a workspace and bind with Launcher; notifying the LoaderTask to load all Application programs (APPs), and binding loadAndBindAllapp with Launcher; and an API interface such as IconCacheUpdateHandler, updateicon Icon, and the like, which notifies IconCacheUpdateHandler to update the contents in the Icon cache (Icon cache). Therefore, loading and binding of the working space corresponding to the desktop icon, loading and binding of the application corresponding to the desktop icon, and updating of the content in the icon cache corresponding to the desktop icon are completed in the Launcher.

In this embodiment, the LoaderTask is used to implement loading and binding of a workspace corresponding to a desktop icon and loading and binding of an application corresponding to the desktop icon. Illustratively, the LoaderTask may implement loading of a workspace corresponding to the desktop icon by calling loadWorkspace, implement binding the workspace with the Launcher by calling bindWorkspace, implement loading of an application corresponding to the desktop icon by calling loadAllapp, and implement binding of the loaded application with the Launcher by calling bindAllapp.

It should be understood that the above description is only an example for better understanding of the technical solution of the present embodiment, and is not to be taken as the only limitation of the present embodiment. For the API interface that needs to be called when the Launcher starts to load the desktop icon and the application corresponding to the desktop icon and performs binding, reference may be made to an API document about Launcher in the android system, which is not limited in this embodiment.

In this embodiment, the iconcacheupdatehandle is further configured to update the content in the Icon cache (Icon cache) when the launcher model calls iconcacheupdatehandle. Therefore, after the function of displaying simplified desktop icons is started, the desktop icons and the desktop background can be fused, and the processed desktop icons can shield the wallpaper as little as possible, so that the visual experience effect of a user is improved.

It should be understood that the above naming of the API interfaces is only a specific example and not as the only limitation to the embodiment. In practical applications, the API can be set according to the API document of Launcher, which is not limited in this embodiment.

In addition, it should be further noted that the view system located in the application framework layer includes visual controls, such as a control for displaying text, a control for displaying pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, the display interface including the short message notification icon may include a view for displaying text and a view for displaying pictures. Specifically, in the technical solution provided in the embodiment of the present application, the view system may display a normal desktop icon (as shown in fig. 1) or display a simplified desktop icon fused with a desktop background (as shown in fig. 4 and 5) according to an API called by Launcher when the Launcher starts to display the desktop icon.

In addition, it should be noted that the window manager located in the application framework layer is used for managing the window program. The window manager can obtain the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like.

In addition, it should be noted that the notification manager located in the application framework layer enables the application to display notification information in the status bar, can be used for conveying notification type messages, and can automatically disappear after a short stay without user interaction. Such as a notification manager used to inform download completion, message alerts, etc. The notification manager may also be a notification that appears in the form of a chart or scroll bar text at the top status bar of the system, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, text information is prompted in the status bar, a prompt tone is given, the mobile phone vibrates, and an indicator light flickers.

In addition, it should be noted that the content provider located in the application framework layer is used to store and acquire data and make the data accessible to the application. The data may include video, images, audio, calls made and answered, browsing history and bookmarks, phone books, etc., which are not further listed herein, but are not limited in this application.

In addition, it should be further noted that the resource manager located in the application framework layer provides various resources for the application, such as localized character strings, icons, pictures, layout files, video files, and the like, which are not listed here, and the application is not limited thereto.

The Android Runtime comprises a core library and a virtual machine. The Android Runtime is responsible for scheduling and managing an Android system.

The core library comprises two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.

The application layer and the application framework layer run in a virtual machine. And executing java files of the application program layer and the application program framework layer into a binary file by the virtual machine. The virtual machine is used for performing the functions of object life cycle management, stack management, thread management, safety and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: surface managers (surface managers), media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., openGL ES), 2D graphics engines (e.g., SGL), and the like.

The surface manager is used to manage the display subsystem and provide a fusion of the 2D and 3D layers for multiple applications.

The media library supports a variety of commonly used audio, video format playback and recording, and still image files, among others. The media library may support a variety of audio-video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.

It can be understood that the 2D graphics engine mentioned above is a drawing engine for 2D drawing.

Furthermore, it is understood that the kernel layer in the Android system is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, a sensor driver and the like. For example, the sensor driver may be configured to output a detection signal of the sensor (e.g., a touch sensor), such as a signal for operating a desktop icon in the desktop, to the view system, so that the view system displays an application interface of an application corresponding to the desktop icon in response to the detection signal.

The software structure of the mobile phone 100 is described here, and it is understood that the layers in the software structure shown in fig. 3 and the components included in each layer do not specifically limit the mobile phone 100. In other embodiments of the present application, the handset 100 may include more or fewer layers than those shown, and may include more or fewer components in each layer, which is not limited in this application.

In order to better understand the technical solutions provided by the present application, the following describes usage scenarios of the display schemes of desktop icons provided by the embodiments of the present application by taking an electronic device as a mobile phone as an example in conjunction with fig. 1 and fig. 4 to 6, respectively.

Referring to fig. 1, assuming that the user of the mobile phone desires that the wallpaper 10a be displayed as completely as possible, the user of the mobile phone may operate in any of the above manners to turn on the function of displaying the simplified desktop icon.

Accordingly, the mobile phone determines, in response to an operation behavior of the user, whether the user wants to turn on the function of displaying the simplified desktop icon, and if so, turns on the function of displaying the simplified desktop icon, and obtains application names corresponding to application programs that need to be displayed on the desktop after turning on the function, for example, application names of application programs corresponding to 20 desktop icons, such as "aaa", "bbb", "ccc", etc., of the desktop icon 10b-1 to the desktop icon 10b-20 in fig. 1, which are not listed one by one, and this embodiment is not limited thereto.

Then, the mobile phone searches a desktop icon corresponding to the application name in a local desktop icon database according to the acquired application name.

It should be noted that the desktop icons stored in the local desktop icon database are simplified desktop icons (for example, the background color and the border of the desktop icon are removed, and only the graphic lines are reserved) obtained by simplifying the original desktop icons (provided by the application manufacturer, with regular shape, and background color, etc.) corresponding to the application program.

In addition, the simplified desktop icon stored in the local desktop icon database may be, for example, actively obtained from the cloud desktop icon database, or may be stored locally after the original desktop icon is processed by the mobile phone, which is not limited in this embodiment.

For example, in some implementation manners, after all application names corresponding to application programs that need to be displayed on the desktop are obtained, the operation of searching for corresponding desktop icons in the local desktop icon database according to the application names may be performed.

For example, in another implementation manner, after each application name corresponding to an application program that needs to be displayed on the desktop is obtained, an operation of searching a corresponding desktop icon in the local desktop icon database according to the currently obtained application name may be performed.

Correspondingly, after the above operations are completed, if the corresponding simplified desktop icon is found, the simplified desktop icon is fused with the area content of the wallpaper 10a corresponding to the simplified desktop icon, and the fused desktop icon is reloaded, so that the desktop icon 10b-1 to the desktop icon 10b-20 which blocks the wallpaper 10a in fig. 1 are replaced with the desktop icon 10b-1 'to the desktop icon 10b-20' in fig. 4.

It is easy to find that the line color and the background of each desktop icon in fig. 4 are processed according to the color and the content of the wallpaper 10a corresponding to the location of the desktop icon, so that the line profile of the simplified desktop icon is retained, the line profile can be fused with the wallpaper 10a, the shielding of the wallpaper 10a is reduced, and the user can visually and completely view the wallpaper 10a. Namely, the desktop icon can shield the desktop background as little as possible based on the display method of the desktop icon provided by the embodiment of the application, so that the visual experience effect of a user is improved.

Referring to fig. 5, for example, assuming that the user performs position exchange between the desktop icons 10b-19 'and the desktop icons 10b-15', and the mobile phone detects the operation behavior, the positions of the desktop icons 10b-19 'and 10b-15' are respectively obtained, specifically, the positions of the desktop icons 10b-19 'on the desktop are moved from the position of A1 in fig. 5 to the position of A2 in fig. 5, and the positions of the desktop icons 10b-15' on the desktop are moved from the position of A2 in fig. 5 to the position of A1 in fig. 5, since the content and the color of the wallpaper 10a corresponding to the position of A1 are different from the content and the color of the wallpaper 10a corresponding to the position of A2, therefore, in order to avoid the position changes of the desktop icons 10b-19 'and 10b-15' from affecting the overall effect of the wallpaper 10a, the mobile phone will fuse the desktop icons 10b-19 'with the content and color of the wallpaper 10a corresponding to the position A2, fuse the desktop icons 10b-15' with the content and color of the wallpaper 10a corresponding to the position A1, and reload the fused desktop icons, so that the desktop icons 10b-19 'at the position A1 in FIG. 5 will be replaced by the desktop icons 10b-15 "in FIG. 6, and the desktop icons 10b-15' at the position A2 will be replaced by the desktop icons 10b-19" in FIG. 6.

Therefore, after the function of displaying simplified desktop icons is started, as long as the positions of desktop icons displayed on a desktop are changed, for example, the positions of any two desktop icons are interacted (as shown in fig. 5 and 6), or a certain desktop icon or a plurality of desktop icons are deleted, the desktop icons are rearranged, and then when the positions of the remaining desktop icons are changed, the desktop icons and the changed desktop background are fused, so that the desktop background is reloaded and displayed, and the desktop icons shield the desktop background as little as possible, so that the visual experience effect of a user is improved.

With reference to the display scene of the desktop icon shown in the foregoing embodiment, details of the implementation of the display scheme of the desktop icon provided in the embodiment of the present application are described below. It should be understood that the following are implementation details provided only for ease of understanding and are not necessary to practice the present solution.

Before explaining the details of the display scheme of the desktop icons provided in the present embodiment, the source of the simplified desktop icons as described above will be described with reference to fig. 7.

For example, in some implementation manners, a mobile phone manufacturer or a manufacturer providing the technical solution of this embodiment may process an original desktop icon corresponding to an existing application in the market in advance, such as removing a background color, a border, and a reserved graphic line of the desktop icon, so as to obtain a simplified desktop icon meeting a service requirement; and then uploading the simplified desktop icons to a desktop icon database (hereinafter referred to as a cloud desktop icon database) which is used for specially storing and managing the simplified desktop icons in a cloud corresponding to the technical scheme provided by the embodiment for subsequent use.

Further, if some new applications are generated in the subsequent market, the mobile phone manufacturer or the manufacturer providing the technical solution of this embodiment also needs to process the original desktop icons corresponding to the new applications in time, so as to obtain simplified desktop icons meeting the business requirements, and update the simplified desktop icons to the cloud desktop icon database.

In some implementation manners, in order to cover the application programs on the market as much as possible, the simplified desktop icons corresponding to all the application programs on the market can be stored in the cloud desktop icon database, so that no matter which application programs are downloaded and installed by a user, the corresponding simplified desktop icons can be obtained from the cloud desktop icon database.

In addition, in other implementation manners, in order to take cost into consideration, only simplified desktop icons corresponding to mainstream application programs may be stored in the cloud desktop icon database, so that mobile phone manufacturers or manufacturers providing the technical scheme of the embodiment may also only process original desktop icons corresponding to the mainstream application programs, thereby reducing occupation of cloud storage controls and input labor cost.

It is understood that the determination of the mainstream application may be determined according to factors such as the downloading amount, the user amount, and the use frequency, which is not limited in this embodiment.

Based on the manner, after processing of the original desktop icons of the mainstream application programs or all application programs in the market is completed to obtain the corresponding simplified desktop icons, and the simplified desktop icons are stored in the cloud desktop icon database, the cloud end can actively issue the simplified desktop icons stored in the cloud desktop icon database to the electronic devices implementing the technical scheme provided by this embodiment, such as the mobile phone a, the mobile phone B, the mobile phone C and the like shown in fig. 7, and further store the simplified desktop icons in the local desktop icon database (hereinafter referred to as the local desktop icon database) for storing and associating the simplified desktop icons. Therefore, when the simplified desktop icon display function of the electronic equipment such as the mobile phone A, the mobile phone B, the mobile phone C and the like is started, the corresponding simplified desktop icon can be searched from the local desktop icon database according to the application name of the application program displayed on the desktop.

Understandably, in some implementation manners, the cloud may actively push the simplified desktop icon to the electronic device implementing the technical scheme provided by the embodiment according to a preset period; in other implementation manners, the cloud may also actively push the simplified desktop icon to the electronic device implementing the technical scheme provided by this embodiment when there is a new simplified desktop icon in the cloud desktop icon database, which is not limited in this embodiment.

For example, in some implementation manners, the simplified desktop icons sent by the cloud to the electronic device may be the same, that is, all the simplified desktop icons obtained by the electronic device implementing the technical scheme provided in this embodiment from the cloud are the same.

For example, in other implementation manners, the simplified desktop icons sent by the cloud to the electronic device may be different, that is, the simplified desktop icon acquired by the electronic device according to the technical scheme provided in this embodiment from the cloud may be only for the current electronic device, and if the current electronic device supports installation of which application programs, the simplified desktop icon corresponding to the application program that can be installed is pushed to the electronic device, so that the difference between devices can be realized, and the actual use of the user can be better fitted.

For example, in another implementation manner, each simplified desktop icon acquired from the cloud by the electronic device implementing the technical scheme provided in this embodiment may be specific to a user using the electronic device, and if the user using the electronic device prefers which type of application program to use, the simplified desktop icon corresponding to the application program preferred by the user is pushed to the electronic device, so that the simplified desktop icon can be different from person to person, and thus the simplified desktop icon can better fit the actual use of the user.

In addition, it should be further noted that the simplified desktop icon may also be actively obtained from the cloud by the electronic device implementing the technical scheme provided in this embodiment.

For example, a request for acquiring the simplified desktop icon is periodically sent to the cloud according to a preset period, so that the local desktop icon database can be updated regularly.

For example, when the function of displaying the simplified desktop icon is started, a request for obtaining the simplified desktop icon is sent to the cloud, so that the simplified desktop icon is obtained from the cloud desktop icon database.

In addition, it should be noted that, for convenience of searching, the simplified desktop icons stored in the cloud desktop icon database or the simplified desktop icons stored in the local desktop icon data may be stored according to the corresponding relationship between the application name and the simplified desktop icons, and the specific form may be as shown in table 1, for example.

TABLE 1 local desktop icon data sheet

Therefore, when the simplified desktop icon is searched for subsequently, the path corresponding to the simplified desktop icon can be located according to the application name and the content recorded in the table 1, and the simplified desktop icon is further acquired from the corresponding path.

It should be understood that table 1 is an example of a local desktop icon data table stored in a local desktop icon database, which is only an example listed for better understanding of the technical solution of the present embodiment, and is not limited to the present embodiment.

Thus, the preparation work for realizing the display method of the desktop icon provided in the present embodiment is completed. The preparation standard of the simplified desktop icons may be determined according to business requirements, and this embodiment does not limit this, and in addition, the simplified desktop icons that are issued from the cloud desktop icon database to the local desktop icon database may be, for example, a specific number of simplified desktop icons each time, or all of the simplified desktop icons, or simplified desktop icons corresponding to a specific application program each time, and this embodiment does not limit this.

The following describes a method for displaying a desktop icon according to this embodiment in detail.

Referring to fig. 8, an exemplary display method for a desktop icon provided in this embodiment specifically includes:

and S101, responding to the operation behavior of starting the function of displaying the simplified desktop icon by the user.

For example, the operation behavior of the user for opening the function of displaying the simplified desktop icon depends on the manner of opening the function of displaying the simplified desktop icon in the foregoing embodiment, and specific details may be referred to above, and are not described herein again.

S102, whether the function of displaying the simplified desktop icon is started or not is judged.

Specifically, when the user triggers an operation behavior of opening the function of displaying the simplified desktop icon in any of the above manners, the electronic device, in response to the operation behavior, first determines whether the current electronic device has already opened the function of displaying the simplified desktop icon, that is, whether the current electronic device is already in a mode corresponding to the function.

Accordingly, if the function is not turned on, the function of displaying the simplified desktop icon is turned on in response to the operation behavior, and the application name of the application program to be displayed on the desktop is acquired after the function is turned on, that is, step S103 is performed.

Accordingly, if the function is turned on, in a possible implementation, it may be further determined whether there is a newly installed application, i.e., step S104 is performed. In this way, if there is a newly installed application program on the desktop, the steps S105 to S109 may be performed on the original desktop icon corresponding to the newly installed application program under the condition that the desktop icon displayed on the desktop is the desktop icon processed by using the desktop icon display method provided in this embodiment, so that the desktop icon of the newly installed application program can be fused with the current desktop background, and the visual experience effect of the user is ensured.

S103, starting a function of displaying simplified desktop icons, and acquiring application names of application programs needing to be displayed on the desktop.

According to the contents recorded in the cloud desktop icon database and the local desktop icon database, the application name and the simplified desktop icon have a corresponding relation, so that when the simplified desktop icon corresponding to the application program to be displayed is obtained, the simplified desktop icon corresponding to the application program to be displayed is searched according to the application name of the application program, and after the function of displaying the simplified desktop icon is started, the application name of the application program to be displayed on a desktop is required to be obtained.

Similarly, when there is a newly installed application program, the application name of the newly installed application program also needs to be acquired, so as to search the corresponding simplified desktop icon from the local desktop icon database or the cloud desktop icon database.

It should be understood that the above description is only an example for better understanding of the technical solution of the present embodiment, and is not intended to limit the present embodiment. In practical application, a corresponding relationship between the simplified desktop icon and the simplified desktop icon may also be established according to the application identification number ID, that is, the uniqueness of the simplified desktop icon may be arbitrarily identified, which is not limited in this embodiment.

And S104, judging whether the newly installed application program exists or not.

Specifically, if there is a newly installed application, after the function of displaying the simplified desktop icon is started and the simplified desktop icon corresponding to the installed application is fused with the desktop background, it is detected that the electronic device installs an original desktop icon that is not subjected to the processing operation of the display method for desktop icons provided in this embodiment, and it is determined that the application is newly installed in the electronic device; otherwise, it is determined that there is no newly installed application, in which case, it is not necessary to perform steps S105 to S109.

In addition, it should be noted that, after it is determined that the electronic device does not have a newly installed application program, it may be further monitored whether a position corresponding to an adaptive desktop icon displayed in the desktop and processed in steps S106 to S109 changes, for example, the user interchanges positions of any two adaptive desktop icons, or deletes one adaptive desktop icon and rearranges the desktop, so that positions of other adaptive desktop icons change.

Correspondingly, if it is monitored that the position corresponding to the adaptive desktop icon changes, the application name of the application program corresponding to the adaptive desktop icon with the changed position can be acquired, and the operations from step S106 to step S109 are performed again on the adaptive desktop icon with the changed position.

And S105, acquiring the application name of the newly installed application program.

For example, in some implementations, the installation packages of the application programs are named by application names, so that the application names of the application programs needing to be displayed on the desktop can be determined by acquiring the name of each installation package.

For example, in other implementations, each application's installation package may have corresponding description information indicating the version, application name, size, etc. of the application. The application name can be acquired from the description information of each application program.

Based on the above description, the manner of acquiring the application name of the application program in step S103 or step S105 can be implemented in the above manner. In practical application, if the corresponding relationship is established based on the other unique identifiers and the simplified desktop icon, the application name of the application program required to be displayed on the desktop can be determined according to the other unique identifiers capable of identifying the application program.

S106, searching whether the simplified desktop icon corresponding to the application name exists in the local desktop icon database or not.

For example, whether the same application name exists in the local desktop icon database may be first searched according to the obtained application name. Correspondingly, when the same application name exists, the corresponding simplified desktop icon can be obtained from the path according to the path of the simplified desktop icon corresponding to the application name recorded in the local desktop icon database.

It can be understood that, in order to reduce the memory occupation of the local, the simplified desktop icons stored in the local desktop icon database are not simplified desktop icons of all applications in the market generally, for example, the simplified desktop icons are only simplified desktop icons of current mainstream applications. Thus. If the same application name does not exist in the local desktop icon database, it indicates that the corresponding simplified desktop icon does not exist in the local desktop icon database, at this time, step S107 shown in fig. 8 may be executed, and the cloud desktop icon database may also be accessed, that is, according to the obtained application name, whether the simplified desktop icon corresponding to the application name exists in the cloud desktop icon database is searched for.

Correspondingly, if the simplified desktop icon corresponding to the application name exists in the cloud desktop icon database, the simplified desktop icon corresponding to the application name stored in the cloud desktop icon database is acquired to the local desktop icon database for storage, and the processing of the step S108 is carried out according to the simplified desktop icon; otherwise, if the simplified desktop icon corresponding to the application name does not exist in the cloud desktop icon database, step S107 is performed.

It should be understood that the above description is only an example for better understanding of the technical solution of the present embodiment, and is not to be taken as the only limitation of the present embodiment. In practical application, a specific query processing logic may be set according to an actual service requirement, which is not limited in this embodiment.

And S107, acquiring the customized simplified desktop icon.

For example, in some implementation manners, the customized simplified desktop icon may be preset locally by, for example, an electronic device manufacturer, or preset locally by a manufacturer that provides the technical solution of the present embodiment. In this way, when the simplified desktop icon corresponding to the acquired application name does not exist in the local desktop icon database and the cloud desktop icon database, a user-defined simplified desktop icon can be acquired locally as the simplified desktop icon corresponding to the application program corresponding to the application name, so that the execution of steps S108 and S109 can be ensured.

For example, in other implementation manners, a user-defined simplified desktop icon provided by an electronic device manufacturer or a manufacturer providing the technical solution of the embodiment may also be preset in the cloud. In this way, when the simplified desktop icon corresponding to the acquired application name does not exist in the local desktop icon database and the cloud desktop icon database, a user-defined simplified desktop icon can be acquired from the cloud and used as the simplified desktop icon corresponding to the application program corresponding to the application name, so that the execution of steps S108 and S109 can be ensured.

For example, in other implementations, the customized simplified desktop icon may be set by the user through a user portal provided in the desktop icon simplification module described above, for example.

And S108, fusing the simplified desktop icon with the desktop background to obtain the self-adaptive desktop icon.

In this embodiment, the simplified desktop icon is fused with the desktop background, specifically, the simplified desktop icon is changed in brightness and darkness in a self-adaptive manner along with the color depth of the wallpaper area of the desktop background corresponding to the position of the simplified desktop icon, so that the self-adaptive desktop icon obtained after processing can be fused with the desktop background, that is, the wallpaper.

Further, in this embodiment, the adaptive brightness change according to the color depth of the wallpaper area is specifically implemented based on the corresponding gray value of the wallpaper area.

Based on this, in this embodiment, the simplified desktop icon is fused with the desktop background, which may include several important steps, such as gray value extraction, gray value blurring processing, and gray value overlap fitting.

In addition, it can be understood that the desktop background, such as the wallpaper 10a in fig. 1, 4 to 6, or the desktop icon displayed on the desktop, is composed of pixel points. Each pixel point corresponds to a gray value, and the distribution range of the gray value is 0 to 255, as shown in fig. 9, wherein "0" corresponds to black, and "255" corresponds to white, and the smaller the number is, the darker the corresponding color is.

Based on this distribution trend, in order to implement the fuzzification processing on the gray-scale values, that is, to perform the fuzzification processing on the gray-scale values within a certain range into the same gray-scale value, in this embodiment, the distribution range of the gray-scale values shown in fig. 10 is divided into N groups, for example, N =5 is taken as an example, and the distribution range of the divided 5 groups of gray-scale values may be, for example, 0 to 49, 50 to 99, 100 to 149, 150 to 199, and 200 to 255.

Then, the value of the middle area is taken as the fuzzified gray value (hereinafter referred to as fuzzy gray value) for each set of gray values, the fuzzy gray value corresponding to the set of gray values from 0 to 49 may be, for example, 25, the fuzzy gray value corresponding to the set of gray values from 50 to 99 may be, for example, 75, the fuzzy gray value corresponding to the set of gray values from 100 to 149 may be, for example, 125, the fuzzy gray value corresponding to the set of gray values from 150 to 199 may be, for example, 175, and the fuzzy gray value corresponding to the set of gray values from 200 to 255 may be, for example, 225.

That is, the fuzzification processing of the gray values in this embodiment is to fuzzify the gray values in the same group into the same gray value, so that the gray values included in the simplified desktop icon and the desktop background can be reduced.

Exemplarily, the division of the gray-scale values may be as shown in table 2.

TABLE 2 data table with gray value distribution range divided into 5 groups

It should be understood that the above description is only an example for better understanding of the technical solution of the present embodiment, and is not intended to limit the present embodiment.

The specific implementation of step S108 is specifically described below with reference to fig. 10.

Referring to fig. 10, the operation of fusing the simplified desktop icon with the desktop background to obtain the adaptive desktop icon specifically includes:

s1081, determining position information of the simplified desktop icon on the desktop.

It can be understood that the position information of the simplified desktop icon on the desktop is essentially the position information of the corresponding original desktop icon on the desktop. Therefore, the position information of the original desktop icon on the desktop, such as the specific coordinate relative to the desktop, can be directly obtained.

Referring to fig. 11, assuming that the original desktop icons corresponding to the simplified desktop icons are the positions of the desktop icons 10b-16 in fig. 11, the corresponding position information may be directly determined according to the information such as the shapes and sizes of the desktop icons 10 b-16.

S1082, obtaining a desktop background area corresponding to the position information.

It can be understood that the desktop background area mentioned in the present embodiment specifically refers to a wallpaper area at the position of the original desktop icon. For convenience of description, in this embodiment, a desktop background region corresponding to the position information is represented as area, and a region corresponding to the original desktop Icon is represented as Icon, that is, a region to be processed by the simplified desktop Icon is represented as Icon.

In addition, it should be noted that, in this embodiment, the area and the Icon have the same size, that is, the number of included pixels and the position of each pixel are the same, as shown in fig. 11, the area and the Icon are two regions of n × m, that is, n × m small squares are included, where each small square is, for example, a pixel to be provided.

S1083, extracting the gray value of the desktop background area.

Referring to fig. 12a, for example, if the area is as shown in (1) of fig. 12a, it is necessary to perform gray value extraction on the area shown in (1) of fig. 12a first, so as to obtain the area' shown in (2) of fig. 12 a. That is, area' is a picture after area gradation processing.

As can be seen from fig. 12a, the area 'shown in (2) of fig. 12a obtained by performing gray-scale value extraction on the area shown in (1) of fig. 12a specifically includes the gray-scale values corresponding to 112, 145, 163, 192, 230, and 250, that is, the area' includes 5 gray-scale values.

S1084, performing fuzzification processing on the gray value of the desktop background area to obtain a fuzzy gray value of the desktop background area.

Referring to fig. 12b, for example, in order to make the line in the area 'shown in (1) in fig. 12b clearer, in this embodiment, it is necessary to perform blurring processing on the area' shown in (1) in fig. 12b, for example, processing is performed according to 5 groups of gray values divided as described above, where 112 and 145 belong to the group of 100 to 149, so after performing blurring processing on the gray values corresponding to 112 and 145, the corresponding blurred gray values become 125, 163 and 192 belong to the group of 150 to 199, so after performing blurring processing on the gray values corresponding to 163 and 192, the corresponding blurred gray values become 175, 230 and 250 belong to the group of 200 to 255, and thus after performing blurring processing on the gray values corresponding to 230 and 250, the corresponding blurred gray values become 225, thereby obtaining the area shown in (2) in fig. 12 b. That is, area "is a picture after the area' gray value blurring process.

S1085, extracting the gray value of the simplified desktop icon.

And S1086, fuzzifying the gray value of the simplified desktop icon to obtain a fuzzy gray value of the simplified desktop icon.

Regarding the simplified desktop Icon, that is, the manner of extracting the grayscale value of Icon and the way of blurring the grayscale value are similar to those of area, and the specific details may be referred to step S1083 and step S1084, which are not described herein again.

For example, taking the outline of the simplified desktop Icon as the letter "a", the Icon ' may be obtained by extracting the grayscale of the Icon in step S1085, and the Icon ' may be obtained by blurring the Icon ' in step S1086.

Regarding the finally obtained Icon ", for example, as shown in fig. 13, the Icon" includes two kinds of blur gradation values, for example, 125 and 175.

S1087, performing overlapping fitting on the fuzzy gray value of the desktop background area and the fuzzy gray value of the simplified desktop icon to obtain the self-adaptive desktop icon.

In this embodiment, the operation of performing overlap fitting on the blurred grayscale value of the desktop background area and the blurred grayscale value of the simplified desktop icon may be implemented based on the following formula (1):

（1）

wherein the content of the first and second substances,

coordinates of pixel points representing the same position in area "and Icon",

in expression area

The pixel points of the location correspond to the blurred grey value,

in representation of Icon

The blurred gray values corresponding to the pixel points of the location,

in expression area

Pixel point correspondence of location in blurred grayscale value and Icon ″

And (4) carrying out gray value fitting on the fuzzy gray value corresponding to the pixel point at the position.

That is, the gradation value of each pixel of area' shown in (2) in FIG. 12b

Gray value of pixel point corresponding to Icon' shown in fig. 13

By overlap-fitting in equation (1).

It can be understood that, taking the simplified desktop Icon "without background color and frame as an example, by performing overlap fitting in formula (1), specifically, finding out the portion overlapping with Icon" shown in fig. 13 in area "shown in (2) in fig. 12b, and then performing overlap fitting on the blurred grayscale values of the overlapping portion to obtain Icon'" shown in fig. 14, that is, (1) in fig. 14 is performed to perform overlap fitting with (2) in fig. 14 to obtain (3) in fig. 14.

Referring to fig. 14, exemplary, the overlapped fit Icon' "includes three

gray values

125, 175 and 225, and the distribution of the respective gray values is merged with the area" shown in (2) of fig. 12 b.

Note that the "a" line 20 in fig. 14 (3) is drawn for convenience of drawing only, and in actual application, the fuzzy gray values of area "and Icon" are subjected to overlap fitting, and the obtained Icon' "does not have this line.

Therefore, the self-adaptive simplified desktop icons can be obtained, and the desktop icons displayed in this way can be attached to the desktop background, namely can be blended into the desktop background and cannot be obtrusive.

It should be understood that the above description is only an example for better understanding of the technical solution of the present embodiment, and is not to be taken as the only limitation of the present embodiment. In practical applications, the simplified desktop icon is not limited to the letter "a", and the letter "a" is taken as an example in this embodiment, and is only for convenience of description of the solution.

And S109, displaying the self-adaptive desktop icon on the desktop.

For example, if the desktop background of the desktop is the wallpaper 10a shown in fig. 1 and the original desktop icons displayed on the desktop are the desktop icons 10b-1 to 10b-20 shown in fig. 1 before the steps S101 to S108 are performed, the wallpaper 10a shown in fig. 4 is finally displayed on the desktop and the adaptive desktop icons displayed on the desktop are the desktop icons 10b-1 'to 10b-20' shown in fig. 4 after the steps S101 to S109 are performed.

Therefore, according to the display method of the desktop icon provided by the embodiment, the simplified desktop icon corresponding to each application program to be displayed on the desktop is obtained, so that the desktop icon finally displayed on the desktop is simpler; through will simplifying the desktop icon and fusing with current desktop background, realize simplifying the self-adaptation change of desktop icon to make the desktop icon can be called as a whole with the better integration of desktop background together, make the desktop icon that finally shows on the desktop can shelter from the desktop background as far as possible like this, make the desktop seem cleaner and tidier, thereby promote user's visual experience effect.

It is obvious from the above description that the method for displaying a desktop icon provided in this embodiment is mainly implemented by launchers and calling corresponding API interfaces and a local desktop icon DataBase when loading and displaying desktop contents, and for better understanding of the method for displaying a desktop icon provided in this embodiment, a specific description is made below with reference to fig. 15, starting from the interaction perspective of launchers, called APIs thereof, such as launchemodel, loaderTask, iconCacheUpdateHandler, and accessed local desktop icon DataBase.

Specifically, the present embodiment takes an example in which the electronic device is started, and the adaptive desktop icon is loaded and displayed by using the desktop icon display method provided in the present embodiment.

In addition, it should be noted that since launchers inherit from Activity (one of the four major components of Android, which is an active application), launchers also have Activity-like life cycles, such as onCreate, onRestart, onStart, onResume, onPause, onStop, and onDestroy.

Wherein onCreate represents that Activity is being created, which is also the first method of the Activity lifecycle; onRestart indicates that Activity is restarting, and this lifecycle is only called if both onPause and onStop have executed; onStart indicates that Activity is being launched, i.e., is about to begin, at which time Activity is already visible but has not yet appeared in the foreground and cannot yet interact (hereinafter referred to as the launch phase); onResume indicates that Activity is already visible and appears in the foreground to interact with the user (hereinafter referred to as the visible and interactable phase); onPause indicates that Activity is stopping; onStop represents that Activity stops and is not visible; onDestroy indicates that Activity is about to be destroyed, which is the last callback of Activity.

For convenience of description, the present embodiment takes as an example that the electronic device is normally started, the Launcher does not execute onPause and onStop, that is, the Launcher does not execute onStop, and only executes onCreate, onStart and onResume in sequence.

Referring to fig. 15, the method for displaying a desktop icon provided in this embodiment specifically includes:

the electronic device is started, and the Launcher calls a creation method (such as an onCreate method for creating Launcher provided in an android API) to realize creation of the Launcher.

It should be noted that, in practical applications, a Launcher state is instantiated in the onCreate mode, and then the Launcher model is acquired according to the Launcher state, that is, a corresponding API can be subsequently called through the Launcher model, and then the loader task and the IconCacheUpdateHandler are triggered to complete corresponding operations, such as loading and binding of a space, loading and binding of an application program, updating of an icon cache, and the like.

2, after the Launcher is created, the Launcher calls an add callback and loading method (such as an addCallbackksAndLoad method), adds the Launcher to a callback list, and thus, the Launcher model calls a startLoader method to start a LoadeTask to execute a corresponding task, and calls back a processing result to the Launcher.

3, the launcher model calls the Start load method (e.g., startLoader method) to start the LoaderTask.

4, after the Launcher model calls the startLoader method to start the loadTask, a load and bind workspace method (e.g., loadAndBindWorkSpace method) is called, a load workspace (workspace) is issued to the loadTask, and the loadAndWordWordWorkSpace instruction is used to bind the workspace with the Launcher, so that the loadTask executes the load workspace method (e.g., loadWorksspace method) and the bind workspace method (e.g., bindWorkWorksspace method).

And 5, calling a loadWorkspace method to load a workpace according to a loadAndBindWorkSpace instruction issued by Launcher Mode.

6, after the loadertask is loaded with the workspace, the bindWorkspace method is called to bind the workspace and the Launcher.

7,launchermadel calls load and bind all Application methods (e.g., loadAndBindAllapp method), issues a LoaderTask instruction to load all applications (Application, app), and binds app to Launcher, so that the LoaderTask executes load all Application methods (e.g., loadAllapp method) and bind all Application methods (e.g., bindAllapp method).

It is understood that in practical applications, after the LoaderTask completes step 7, a callback message is returned to the launcher model to inform the launcher model that the operations of step 5 and step 6 are completed, so that the launcher model can execute step 7 (the callback step is not shown in fig. 15).

In addition, it should be understood that, in practical applications, if either step 5 or step 6 fails, the LoaderTask also returns a callback message to the launcher model to inform the launcher model of which step failed, so that the launcher model can re-execute step 4 (the callback step is not shown in fig. 15).

And 8, the LoaderTask calls a loadAllapp method to load all apps according to a loadAndBindAllapp instruction issued by Launcher Mode.

9,LoaderTask calls the bindAllapp method after all apps have been loaded, binding all apps to launchers.

Similarly, after the LoaderTask completes step 9, a callback message is returned to the launcher model to inform the launcher model that the operations of step 8 and step 9 are completed, so that the launcher model can execute step 10 (the callback step is not shown in fig. 15).

Furthermore, it should be understood that, in practical applications, if either step 8 or step 9 fails, the loader task will also return a callback message to the launcher model to inform the launcher model which step failed, so that the launcher model can perform step 7 again (the callback step is not shown in fig. 15).

10, the launcher model calls an update icon method (e.g., the IconCacheUpdateHandler. Updateicon method) to cause the IconCacheUpdateHandler to update the contents of the IconCache (not shown in fig. 15).

Similarly, after the IconCacheUpdateHandler updates the content in the IconCache, callback information is also returned to the launcher model to inform the launcher model of the update result, such as success of the update, failure of the update, and the like.

Correspondingly, if the returned callback information is update failure, the launcher model executes step 10 again; otherwise, step 11 is executed.

11, the Launcher model calls a loading and binding shortcut method (such as loadAndBindDeepShortcuts method), issues a loading shortcut to the LoaderTask, and binds the shortcut with the Launcher with a loadandbinddeepcuts instruction, so that the LoaderTask executes the loading shortcut method (such as loadDeepShortcuts method) and the binding shortcut method (such as bindDeepShortcuts method).

And 12, calling a loadDeepShortcuts method to load shortcuts by the LoaderTask according to a loadAndBindDeepShortcuts instruction issued by the launcher mode.

And 13, after the loadertask loads the shortcut, calling a bindDeepShortcuts method to bind the shortcut with the Launcher.

Similarly, after the LoaderTask completes step 13, a callback message is returned to the launcher model to inform the launcher model that the operations of step 12 and step 13 are completed, so that the launcher model can execute step 14 (the callback step is not shown in fig. 15).

In addition, it should be understood that, in practical applications, if either step 12 or step 13 fails, the LoaderTask also returns a callback message to the launcher model to inform the launcher model of which step failed, so that the launcher model can re-execute step 11 (the callback step is not shown in fig. 15).

14,launchermadel calls an update icon method (e.g., iconCacheUpdateHandler. Updateicon method) to cause IconCacheUpdateHandler to update the contents in IconCache (not shown in fig. 15).

15, the Launcher model calls a method for loading and binding each component (e.g., loadandbinddeep widgets method), issues a loaderTask with a loadandBindedwidgets instruction for loading each component, and binding each component with the Launcher, so that the loaderTask executes the method for loading each component (e.g., loadWidgets method) and the method for binding each component (e.g., bindWidgets method).

And 16, calling a loadWidgets method to load each component by the loadTask according to a loadAndBindWidgets instruction issued by the launcher mode.

17, after loading each component, the loadertask calls a bindWidgets method to bind each component with the Launcher.

Similarly, after the LoaderTask completes step 17, a callback message is returned to the launcher model to inform the launcher model that the operations of step 16 and step 17 are completed, so that the launcher model can execute step 18 (the callback step is not shown in fig. 15).

Furthermore, it should be understood that, in practical applications, if either step 16 or step 17 fails, the loader task will also return a callback message to the launcher model to inform the launcher model which step failed, so that the launcher model can perform step 15 again (the callback step is not shown in fig. 15).

18,launchermadel calls an update icon method (e.g., iconcacheupdatehandle. Updateicon method) to cause iconcacheupdatehandle to update the contents of IconCache (not shown in fig. 15).

It can be understood that, since the content loaded each time is different, in order to ensure that the content in the IconCache can be matched with the content finally displayed on the desktop, the content in the IconCache needs to be updated once in time each time some content is loaded, so that the launcher model calls the iconcacheupdatehandle.

19,launchermadel calls an extract gray value and blurring method (e.g., the dowyvalueblur method) to make the LoaderTask extract the gray value of the simplified desktop icon and blur it, and extracts the gray value of the desktop background area where the simplified desktop icon is located and blur it (not shown in fig. 15).

For details of the step 19, reference may be made to the contents of the step S1081 to the step S1086 in the foregoing embodiment, and details are not described herein again.

Similarly, after the LoaderTask pair completes the above operation, it also returns a callback message to the launcher model to inform the launcher model of the processing result, such as success or failure.

Accordingly, if the returned callback information is a failure, the launcher model re-executes step 19; otherwise, step 20 is executed.

20,launchermadel calls a gray value overlap fitting method (e.g., doOverLapFit method) to make LoaderTask perform gray value overlap fitting on the blurred gray values of the desktop background region and the blurred gray values of the simplified desktop icon, thereby obtaining an adaptive desktop icon (not shown in fig. 15).

Accordingly, if the returned callback information is a failure, the launcher model re-executes step 20; otherwise, step 21 is executed.

21, the launcher model calls a method (e.g., the upatelconconfromdb method) for updating the icon to the DataBase, and stores the adaptive desktop icon into the DataBase, specifically, the local desktop icon DataBase.

In this way, in a scene that the user uses the wallpaper corresponding to the current desktop, if the user does not adjust the position of the desktop icon, nor delete or add a desktop icon, the electronic device may directly obtain the adaptive desktop icon suitable for the wallpaper corresponding to the current desktop from the local desktop icon database every time the electronic device is started, that is, step 19 to step 20 do not need to be executed every time, and step 22 is directly executed after step 18 is executed.

Furthermore, it is understood that in some implementations, after step 21 is executed, a corresponding instruction may be issued by the launcher model to the loadtask to cause the loadtask to execute step 22; in other implementations, it may also be configured that, after adding the adaptive desktop icon, the DataBase returns callback information to the LoaderTask, so that the LoaderTask performs step 22.

Furthermore, it should be noted that, in a possible implementation manner, simplified desktop icons corresponding to all mainstream applications and adaptive desktop icons corresponding to all wallpapers used by the electronic device may be stored in the local desktop icon database. In this way, when the user switches back to the wallpaper used before, the adaptive desktop icon matching the corresponding desktop background area can be directly acquired without performing steps 19 to 21 again.

In another possible implementation manner, simplified desktop icons corresponding to all mainstream applications and adaptive desktop icons corresponding to wallpaper currently used by the electronic device may be stored in the local desktop icon database. Therefore, the user can be ensured to acquire the self-adaptive desktop icon matched with the corresponding desktop background area no matter whether the electronic equipment is restarted or not in the scene that the user uses the current wallpaper, the steps 19 to 21 do not need to be executed again, and the occupation of the equipment memory can be reduced.

It should be understood that the above description is only an example for better understanding of the technical solution of the present embodiment, and is not intended to limit the present embodiment. In practical applications, the storage standard may be set according to specific service needs, which is not limited in this embodiment.

22, the loadertask calls an icon update completion method (for example, iconCacheUpdateHandler. Finish method), so that IconCacheUpdateHandler updates the content in the IconCache (not shown in fig. 15), and the operation flow of this time is completed.

Continuing with fig. 15, for example, in some implementations, steps 2 and 3 may be implemented in onCreate, steps 4 through 20 may be implemented in onStart, and step 22 may be implemented in onsesume. However, this is only a specific example, in an actual application, the steps 3 to 22 may also be implemented at any stage of onCreate, onStart, and onResume according to a business requirement, and this embodiment does not limit this.

Therefore, the desktop icon displayed on the current desktop can be updated to be the self-adaptive desktop icon, so that the desktop icon can be better integrated with the desktop background to form a whole, the desktop background can be shielded as less as possible by the desktop icon finally displayed on the desktop, the desktop looks cleaner and tidier, and the visual experience effect of a user is improved.

Furthermore, it is understood that the electronic device comprises corresponding hardware and/or software modules for performing the respective functions in order to implement the above-described functions. The present application is capable of being implemented in hardware or a combination of hardware and computer software in conjunction with the exemplary algorithm steps described in connection with the embodiments disclosed herein. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, with the embodiment described in connection with the particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In addition, it should be noted that, in an actual application scenario, the method for displaying the desktop icon provided in the foregoing embodiments implemented by the electronic device may also be executed by a chip system included in the electronic device, where the chip system may include a processor. The system-on-chip may be coupled to the memory, such that the computer program stored in the memory is called when the system-on-chip is run to implement the steps performed by the electronic device. The processor in the system on chip may be an application processor or a processor other than an application processor.

In addition, an embodiment of the present application further provides a computer-readable storage medium, where a computer instruction is stored in the computer storage medium, and when the computer instruction runs on an electronic device, the electronic device is caused to execute the above-mentioned related method steps to implement the method for displaying the desktop icon in the above-mentioned embodiment.

In addition, an embodiment of the present application further provides a computer program product, which when running on an electronic device, causes the electronic device to execute the above related steps, so as to implement the method for displaying a desktop icon in the above embodiment.

In addition, embodiments of the present application also provide a chip (which may also be a component or a module), which may include one or more processing circuits and one or more transceiver pins; the receiving pin and the processing circuit are communicated with each other through an internal connection path, and the processing circuit executes the related method steps to realize the display method of the desktop icon in the embodiment, so as to control the receiving pin to receive the signal and control the sending pin to send the signal.

In addition, as can be seen from the foregoing description, the electronic device, the computer readable storage medium, the computer program product, or the chip provided in the embodiments of the present application are all configured to execute the corresponding methods provided above, and therefore, the beneficial effects achieved by the electronic device, the computer readable storage medium, the computer program product, or the chip may refer to the beneficial effects in the corresponding methods provided above, which are not described herein again.

The above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for displaying desktop icons, the method comprising:

displaying a first interface, wherein a first background and a first desktop icon are displayed in the first interface, and the first desktop icon is located at a first position and blocks a first area of the first background at the first position;

and responding to a first operation, replacing the first desktop icon at the first position with a second desktop icon, and performing overlapping fitting on the second desktop icon according to the fuzzy gray value of the first area and the fuzzy gray value of the simplified desktop icon corresponding to the first desktop icon to obtain the second desktop icon and the content of the first area, so that the second desktop icon is fused with the content of the first area.

2. The method of claim 1, wherein prior to said replacing said first desktop icon at said first location with a second desktop icon, said method further comprises:

acquiring an application name of an application program corresponding to the first desktop icon;

searching a simplified desktop icon corresponding to the application name in a local desktop icon database, wherein the simplified desktop icon is a simplified desktop icon based on the first desktop icon;

if the simplified desktop icon corresponding to the application name is found in the local desktop icon database, fusing the simplified desktop icon with the content of the first area to obtain a second desktop icon;

if the simplified desktop icon corresponding to the application name is not found in the local desktop icon database, obtaining a user-defined simplified desktop icon;

and fusing the user-defined simplified desktop icon with the content of the first area to obtain the second desktop icon.

3. The method of claim 2, wherein fusing the simplified desktop icon with the content of the first region to obtain the second desktop icon comprises:

extracting a gray value of the first region, and performing fuzzification processing on the gray value of the first region to obtain a fuzzy gray value of the first region;

extracting the gray value of the simplified desktop icon, and performing fuzzification processing on the gray value of the simplified desktop icon to obtain a fuzzy gray value of the simplified desktop icon;

and performing overlapping fitting on the fuzzy gray value of the first area and the fuzzy gray value of the simplified desktop icon to obtain the second desktop icon.

4. The method of claim 3, wherein the blurred grayscale value of the first region and the blurred grayscale value of the simplified desktop icon are overlap fit based on the following formula:

wherein the content of the first and second substances,

coordinates of pixel points representing a same location in the first region and the simplified desktop icon,

in the first area

The blurred gray values corresponding to the pixel points of the location,

in the icon representing the simplified desktop

The blurred gray values corresponding to the pixel points of the location,

representing the gray values after gray value fitting.

5. The method of claim 2, wherein obtaining the customized simplified desktop icon comprises:

in response to a second operation, displaying a second interface, wherein the second interface comprises a simplified desktop icon drawing area;

and responding to a third operation, acquiring the desktop icon drawn in the simplified desktop icon drawing area, and taking the desktop icon as the self-defined simplified desktop icon.

6. The method of any of claims 1-5, wherein after said replacing said first desktop icon at said first location with a second desktop icon, said method further comprises:

in response to a fourth operation, replacing the second desktop icon at the first location with a first desktop icon.

7. The method of any of claims 1-5, wherein after said replacing the first desktop icon at the first location with a second desktop icon, the method further comprises:

in response to a fifth operation, replacing the first background with a second background, the second desktop icon obstructing a second area of the second background at the first location;

replacing the second desktop icon at the first position with a third desktop icon, the third desktop icon being fused with the content of the second region.

8. The method of any of claims 1-5, wherein after said replacing said first desktop icon at said first location with a second desktop icon, said method further comprises:

responding to a sixth operation, installing an application program, and displaying a fourth desktop icon in the first interface after the application program is successfully installed, wherein the fourth desktop icon is a desktop icon of the application program, is located at a second position, and covers a third area of the first background at the second position;

and replacing the fourth desktop icon at the second position with a fifth desktop icon, wherein the fifth desktop icon is fused with the content of the third area.

9. The method of claim 8, wherein after the replacing the first desktop icon at the first location with a second desktop icon, the method further comprises:

in response to a seventh operation, interchanging the positions of the second desktop icon at the first position and the fifth desktop icon at the second position;

replacing the fifth desktop icon at the second position with a sixth desktop icon, replacing the second desktop icon at the first position with a seventh desktop icon, wherein the sixth desktop icon is fused with the content of the first area, and the seventh desktop icon is fused with the content of the third area.

10. The method of claim 8, wherein after the replacing the first desktop icon at the first location with a second desktop icon, the method further comprises:

in response to an eighth operation, deleting the second desktop icon at the first position;

moving the fifth desktop icon at the second location to the first location;

replacing the fifth desktop icon at the first position with a sixth desktop icon, the sixth desktop icon being fused with the content of the first region.

11. An electronic device, characterized in that the electronic device comprises: a memory and a processor, the memory and the processor coupled; the memory stores program instructions that, when executed by the processor, cause the electronic device to perform the method of displaying a desktop icon according to any one of claims 1 to 10.

12. A computer-readable storage medium characterized by comprising a computer program that, when run on an electronic device, causes the electronic device to execute the method of displaying a desktop icon according to any one of claims 1 to 10.