CN102646054B - Terminal assembly management method and terminal - Google Patents
Terminal assembly management method and terminal Download PDFInfo
- Publication number
- CN102646054B CN102646054B CN201210045916.XA CN201210045916A CN102646054B CN 102646054 B CN102646054 B CN 102646054B CN 201210045916 A CN201210045916 A CN 201210045916A CN 102646054 B CN102646054 B CN 102646054B
- Authority
- CN
- China
- Prior art keywords
- state
- component
- container
- terminal
- manageable
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000007726 management method Methods 0.000 title abstract description 93
- 238000000034 method Methods 0.000 claims abstract description 16
- 230000000712 assembly Effects 0.000 abstract 5
- 238000000429 assembly Methods 0.000 abstract 5
- 238000009434 installation Methods 0.000 description 16
- 238000010586 diagram Methods 0.000 description 3
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the invention discloses a terminal assembly management method and a terminal and is used for carrying out the unified management on assemblies in an operating system (OS). The method provided by the embodiment of the invention comprises the following steps that: the terminal comprises at least two containers, and the containers are display regions of the assemblies; the containers at least comprise an assembly management container used for displaying the current manageable state of the assemblies, and in addition, the containers at least comprise a desktop container used for displaying a desktop assembly of the terminal; when the terminal receives instructions entering the assembly management container, the terminal sends refreshing requirements to a server; and the terminal receives the refreshing data sent by the server and displays the current manageable state of the assemblies according to the refreshing data. Through the implementation of the scheme, the unified management on the assemblies in the OS can be realized, so the assembly management difficulty is reduced, the assembly management efficiency is improved, and meanwhile, the operation experience of users is improved.
Description
Technical Field
The present invention relates to the field of terminal technologies, and in particular, to a terminal and a method for managing a component of the terminal.
Background
At present, intelligent terminals are popular, and the intelligent terminals adopt Operating Systems (OS). Common OSs include microsoft Windows Mobile and Mobile Phone Windows Phone, saiban Sybiam from nokia, Android from Google, and iOS from apple. The user can customize the installation component in the OS to expand the functions of the mobile terminal and meet the use requirements of the user. A component refers to an application or data that can perform a certain function. Such as input methods, web browsers, drawing applications, image editing tools, and mail clients, among others. During the use of the components, the user also needs to manage many components in the OS, including installation, update, and normal operations, including starting, deleting, and browsing component information.
At present, an OS includes a container, which is a display area of a component and can also be used to place icons of the component, and the component is generally placed in a desktop container after being installed so as to be displayed in a unified manner. The main management method of the components in the OS comprises the following steps: and all the components are placed by using the desktop container, and a user can perform normal operations such as starting, deleting and browsing component information on all the components on the desktop container. Referring to fig. 1, a user can launch a corresponding component by simply touching the component icon 102 on the desktop container 101. The desktop container may include a plurality of pages, the first page is displayed when entering the desktop container, the first page of the desktop container is also called the 1 st page of the desktop container or the homepage of the desktop container, and others are arranged in sequence as the 2 nd page, the 3 rd page, etc., and the next page of the desktop is entered by a touch operation, for example, the next page is entered by sliding left on the touch screen as is common in the prior art, for example, the desktop container 101 includes 4 pages, represented by 4 circles of the paging device 103, when the first page is used, the 1 st circle of the paging device 103 is darkened, when the 2 nd page is used, the 2 nd circle of the paging device 103 is darkened, and so on. A series of commonly used components are pre-installed when the mobile terminal leaves a factory, and then a user can upgrade the components to the latest version or install other new components through an installation source; finally, the user can also launch components and browse component information in an efficient manner using third party management components.
However, in the above management method, the desktop container, the installation source, and the third-party management component are used to perform joint management on the components, and a user needs to perform frequent switching on multiple interfaces to effectively manage a plurality of components, thereby increasing the difficulty of component management, reducing the efficiency of component management, and reducing the operation experience of the user.
Disclosure of Invention
In order to solve the above problems, the present invention provides a terminal component management method and a related terminal thereof, which are used for performing unified management on components in an OS.
A method for managing components of a terminal includes:
the terminal comprises at least two containers, wherein the containers are display areas of the components; the container at least comprises a component management container used for displaying the current manageable state of the component, and the container at least comprises a desktop container used for displaying the desktop component of the terminal;
when the terminal receives an instruction of entering the component management container, the terminal sends a refreshing request to a server;
and the terminal receives the refreshing data sent by the server and displays the current manageable state of the component according to the refreshing data.
A terminal, comprising:
at least two containers, the containers being display areas of the assembly; the container at least comprises a component management container used for displaying the current manageable state of the component, and the container at least comprises a desktop container used for displaying the desktop component of the terminal
A refresh request sending unit, configured to send a refresh request to a server when the terminal receives an instruction to enter the component management container;
the refreshing data receiving unit is used for receiving refreshing data sent by the server;
and the manageable state display unit is used for displaying the current manageable state of the component according to the refreshing data.
According to the technical scheme, the embodiment of the invention has the following advantages:
and setting an assembly management container, when entering the assembly management container, sending a refreshing request to a server by a terminal to request for refreshing data, and displaying the current manageable state of the assembly according to the refreshing data. The components in the OS are managed in a unified mode through the component management container, so that the difficulty of component management is reduced, the efficiency of component management is improved, and the operation experience of a user is improved.
Drawings
Fig. 1 is a diagram illustrating a component management method of a terminal in the prior art;
FIG. 2 is a flowchart of a method for managing components of a terminal according to a first embodiment of the present invention;
FIG. 3 is a flowchart of a component management method of a terminal according to a second embodiment of the present invention;
FIG. 4 is a schematic view of a state corner mark of the present invention;
fig. 5 is a structural diagram of a terminal according to a third embodiment of the present invention;
fig. 6 is a structural diagram of a terminal according to a fourth embodiment of the present invention.
Detailed Description
The technical solutions in the present invention will be described clearly and completely with reference to the accompanying drawings in the specification of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, not all of the embodiments. 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 invention.
The embodiment of the invention provides a terminal component management method, which is used for uniformly managing components in an OS (operating system). The embodiment of the invention also provides a terminal for implementing the method, which is respectively described in detail below.
A first embodiment of the present invention will describe a method for managing a terminal component in detail, where a specific flow of the method for managing a terminal component is shown in fig. 2, and the method includes the following steps:
201. when a terminal receives an instruction of entering a component management container, the terminal sends a refresh request to a server.
The terminal comprises at least two containers, wherein the containers are display areas of the assembly. The at least two containers at least comprise one component management container used for displaying the current manageable state of the components, and the container at least comprises one desktop container used for displaying the desktop components of the terminal.
In order to uniformly manage the components in the OS, the present invention sets at least one component management container in the at least two containers, which is not specifically limited in this embodiment. The component management container is used for displaying the current manageable state of the component. In the background, it has been mentioned that the management of a component by a user includes installation, update and normal operations, where the normal operations include starting, deleting and browsing component information, and correspondingly, the manageable state of the component may include: the component information may be, for example, to be installed, to be updated, to be operated, and the like, and the component information may be, for example and without specific limitation, to be started, to be deleted, and browsed.
And when the terminal receives an instruction of entering the component management container, triggering the terminal to send a refresh request to the server. The refresh request is used to request the server for refresh data, where the refresh request should further include state information of a component in the current desktop container of the terminal, so that the server sends corresponding refresh data to the terminal according to the state information of the component, for example, a list of currently installed components and a version number thereof, which is not specifically limited herein.
In addition, the server may be a data server or an application server, and this embodiment is not particularly limited.
202. And the terminal receives the refreshing data sent by the server and displays the current manageable state of the component according to the refreshing data.
When the server receives the refresh request sent by the terminal in step 201, the server sends corresponding refresh data to the terminal according to the state information of the component contained in the refresh request, and at this time, the terminal receives the refresh data sent by the server and displays the current manageable state of the component according to the refresh data.
Wherein the refresh data is determined from state information of the component. For example, if the version number of the component a in the current terminal is 1.0 and the version number of the component a in the server is 2.0, the refresh data will include information that the component a is to be updated, and the subsequent steps will prompt the user to: component a may be updated from version 1.0 to version 2.0. For another example, the state information of the component included in the refresh request sent by the current terminal does not include a component B, and the server includes an installation source of the component B, and the following steps will prompt the user to: component B may be selected for installation.
In this embodiment, a component management container is set, and when entering the component management container, a terminal sends a refresh request to a server to request for refreshing data, and displays the current manageable state of the component according to the refresh data. The components in the OS are managed in a unified mode through the component management container, so that the difficulty of component management is reduced, the efficiency of component management is improved, and the operation experience of a user is improved.
A second embodiment of the present invention optimizes and supplements the component management method of the terminal described in the first embodiment, and a specific flow of the management method described in this embodiment refers to fig. 3, which includes the following steps:
301. and receiving touch operation of entering the component management container when the home page of the desktop container is displayed on the current screen.
The touch operation direction is opposite to the touch operation direction of the next page entering the desktop container. The terminal comprises at least two containers, wherein the containers are display areas of the assembly. The at least two containers at least comprise one component management container used for displaying the current manageable state of the components, and the container at least comprises one desktop container used for displaying the desktop components of the terminal.
In order to uniformly manage the components in the OS, the invention sets a component management container in the container. The component management container is used for displaying manageable states of components. In the background, it has been mentioned that the management of a component by a user includes installation, update and normal operations, where the normal operations include starting, deleting and browsing component information, and correspondingly, the manageable state of the component may include: to be installed, to be updated, to be operated, etc., which may include to be started, to be deleted, browsable component information, etc. The second embodiment of the present invention will be described by taking the manageable states of the components as three types, i.e., to-be-installed, to-be-updated, and to-be-operated.
Preferably, when a user wants to enter the component management container, a touch operation is sent to the terminal, and in this step, when a desktop container home page is displayed, the touch operation entering the desktop container is received. The touch operation direction is opposite to the touch operation direction of the next page entering the desktop container. Since the desktop is usually slid leftwards to enter the next page of the desktop in the prior art, the scheme here can receive the right sliding touch operation for the terminal.
Currently, all components in an OS are placed in desktop containers, which is a very popular way to facilitate user startup and deletion of components. The desktop container is seamlessly connected with the user operation interface, and is more convenient and visual than a third-party component. As mentioned in the background art, the desktop container may include a plurality of pages, when entering the desktop container, the first page is displayed first, the first page of the desktop container is also called as the 1 st page of the desktop container or the homepage of the desktop container, and the other pages are arranged in sequence as the 2 nd page, the 3 rd page, etc., in the prior art, the next page is usually entered by sliding left on the touch screen.
In the preferred embodiment, the component management container can be set as a related page of the desktop container. In addition, in order to not change the operation habits of the user, the serial number of the component management container is set as page 0, when the terminal displays page 1 of the desktop container, the user can enter the component management container by sliding the touch screen in the opposite direction of the next page, and the component management container slides rightwards on the premise that the user usually slides leftwards to enter the next page in the prior art, so that the seamless connection with the desktop container is realized.
302. And when the terminal receives an instruction of entering the component management container, the terminal sends a refresh request to a server.
And when the terminal receives an instruction of entering the component management container, triggering the terminal to send a refresh request to a server. The refresh request is used to request for refresh data from a server, where the refresh request includes state information of a component included in the current desktop container of the terminal, so that the server sends corresponding refresh data to the terminal according to the state information of the component, for example, a list of currently installed components and a version number thereof, which is not specifically limited herein.
Preferably, according to the example in step 301 above, the manageable states of the components include: at least one of a to-be-installed state, a to-be-updated state, and a to-be-operated state.
The to-be-installed state is used for indicating that the component is to be installed, the to-be-updated state is used for indicating that the component is to be updated, and the to-be-operated state is used for indicating that the component is installed and does not need to be updated.
In addition, the server may be a data server or an application server, and this embodiment is not particularly limited.
303. And the terminal receives the refreshing data sent by the server and displays the state icon of the component according to the refreshing data.
After the server receives the refresh request sent by the terminal in step 302, the server sends corresponding refresh data to the terminal according to the state information of the component included in the refresh request, and at this time, the terminal receives the refresh data sent by the server.
Wherein the refresh data is determined from state information of the component. For example, if the version number of the component a in the current terminal is 1.0 and the version number of the component a in the server is 2.0, the refresh data will include information that the component a is to be updated, and the subsequent steps will prompt the user to: component a may be updated from version 1.0 to version 2.0. For another example, the state information of the component included in the refresh request sent by the current terminal does not include a component B, and the server includes an installation source of the component B, and the following steps will prompt the user to: component B may be selected for installation.
And after receiving the refreshing data, the terminal displays the state icon of the component in the component management container according to the refreshing data. Preferably, the status icon of the component is a status corner mark added to the original icon of the component for indicating the manageable status of the component. According to the example in step 301 above, the manageable states of the components include: at least one of the to-be-installed state, the to-be-updated state and the to-be-operated state, and correspondingly, the state corner mark may include at least one of the to-be-installed corner mark, the to-be-updated corner mark and the to-be-operated corner mark. The form of the state angle scale is shown in fig. 4, and the three state angle scales are an angle scale to be installed 401, an angle scale to be updated 402 and an angle scale to be operated 403. It should be noted that fig. 4 is only an example according to the embodiment of the present invention, and other manners may be used to display the status icons of the components. In addition, the state icon added with the to-be-operated corner mark may be an original icon of the component, which is not limited in the embodiment of the present invention.
The to-be-installed corner mark is used for indicating that the manageable state of the component is the to-be-installed state, the to-be-updated corner mark is used for indicating that the manageable state of the component is the to-be-updated state, and the to-be-operated corner mark is used for indicating that the manageable state of the component is the to-be-operated state.
As described above, the step of displaying the status icon of the component specifically includes:
if the refresh data indicates that the component is installed and does not need to be updated, namely the manageable state of the component is a to-be-operated state, displaying a corresponding state corner mark as the to-be-operated corner mark;
if the refresh data indicates that the component is to be installed, namely the manageable state of the component is the state to be installed, displaying the corresponding state corner mark as the corner mark to be installed;
and if the refreshing data indicates that the component is to be updated, namely the manageable state of the component is the state to be updated, displaying the corresponding state corner mark as the corner mark to be updated.
In this embodiment, a component management container is set, and when entering the component management container, a terminal sends a refresh request to a server to request for refreshing data, and displays a status icon of the component according to the refresh data, where the status icon of the component is used to indicate a manageable status of the component. The components in the OS are managed in a unified mode through the component management container, so that the difficulty of component management is reduced, the efficiency of component management is improved, and the operation experience of a user is improved.
A third embodiment of the present invention will be described in detail for a terminal comprising one or more units for implementing one or more steps of the aforementioned method. Therefore, the description of the steps in the foregoing method is applicable to the corresponding units in the terminal. Referring to fig. 5, a specific structure of the terminal described in this embodiment includes:
at least two containers, the containers being display areas of the assembly. The at least two containers at least comprise one component management container used for displaying the current manageable state of the components, and the container at least comprises one desktop container used for displaying the desktop components of the terminal.
In order to uniformly manage the components in the OS, the present invention sets a component management container in the container, where a specific implementation manner of the set component management container may be a special page in a desktop container, and this embodiment is not particularly limited thereto. The component management container is used for displaying the current manageable state of the component.
A refresh request sending unit 501, configured to send a refresh request to the server when the terminal receives an instruction to enter the component management container.
In the background, it has been mentioned that the management of a component by a user includes installation, update and normal operations, where the normal operations include starting, deleting and browsing component information, and correspondingly, the manageable state of the component may include: the component information may be, for example, to be installed, to be updated, to be operated, and the like, and the component information may be, for example and without specific limitation, to be started, to be deleted, and browsed.
When the terminal receives an instruction to enter the component management container, the terminal triggers the refresh request sending unit 501 to send a refresh request to the server. The refresh request is used to request the server for refresh data, where the refresh request should further include state information of a component in the current desktop container of the terminal, so that the server sends corresponding refresh data to the terminal according to the state information of the component, for example, a list of currently installed components and a version number thereof, which is not specifically limited herein.
In addition, the server may be a data server or an application server, and this embodiment is not particularly limited.
The refresh request sending unit 501 and the refresh data receiving unit 502 are communicably connected.
A refresh data receiving unit 502, configured to receive refresh data sent by a server.
When the server receives the refresh request sent by the refresh request sending unit 501, the server sends corresponding refresh data to the terminal according to the state information of the component included in the refresh request, and at this time, the refresh data receiving unit 502 receives the refresh data sent by the server.
Wherein the refresh data is determined from state information of the component. For example, if the version number of the component a in the current terminal is 1.0 and the version number of the component a in the server is 2.0, the refresh data will include information that the component a is to be updated, and the subsequent steps will prompt the user to: component a may be updated from version 1.0 to version 2.0. For another example, the state information of the component included in the refresh request sent by the current terminal does not include a component B, and the server includes an installation source of the component B, and the following steps will prompt the user to: component B may be selected for installation.
The refresh data receiving unit 502 and the manageable state display unit 503 are connected in a communication mode.
A manageable state display unit 503, configured to display the current manageable state of the component according to the refresh data.
After the refresh data receiving unit 502 receives the refresh data, the manageable state displaying unit 503 displays the manageable states of the components in the component management container according to the refresh data. As already mentioned, the manageable states of a component may include: the component information may be, for example, to be installed, to be updated, to be operated, and the like, and the component information may be, for example and without specific limitation, to be started, to be deleted, and browsed.
In this embodiment, a component management container is set, when entering the component management container, the refresh request sending unit 501 sends a refresh request to the server to request refresh data, and the manageable state display unit 503 displays the manageable state of the component according to the refresh data. The components in the OS are managed in a unified mode through the component management container, so that the difficulty of component management is reduced, the efficiency of component management is improved, and the operation experience of a user is improved.
A fourth embodiment of the present invention will additionally describe the terminal according to the third embodiment, wherein the terminal comprises one or more units for implementing one or more steps of the foregoing method. Therefore, the description of the steps in the foregoing method is applicable to the corresponding units in the terminal. Referring to fig. 6, a specific structure of the terminal described in this embodiment includes:
at least two containers, the containers being display areas of the assembly. The at least two containers at least comprise one component management container used for displaying the current manageable state of the components, and the container at least comprises one desktop container used for displaying the desktop components of the terminal.
In order to uniformly manage the components in the OS, the invention sets a component management container in the container. The component management container is used for displaying manageable states of components. In the background, it has been mentioned that the management of a component by a user includes installation, update and normal operation, where the normal operation includes starting, deleting and browsing component information, and correspondingly, the manageable state of the component may include: to be installed, to be updated, to be operated, etc., which may include to be started, to be deleted, browsable component information, etc. The fourth embodiment of the present invention will be described by taking the manageable states of the components as three types, i.e., to-be-installed, to-be-updated, and to-be-operated.
A touch operation receiving unit 601, configured to receive a touch operation entering the component management container.
Currently, all components in an OS are placed in desktop containers, which is a very popular way to facilitate user startup and deletion of components. The desktop container is seamlessly connected with the user operation interface, and is more convenient and visual than a third-party component. As mentioned in the background art, the desktop container may include a plurality of pages, when entering the desktop container, the first page is displayed first, the first page of the desktop container is also called as the 1 st page of the desktop container or the homepage of the desktop container, and the other pages are arranged in sequence as the 2 nd page, the 3 rd page, etc., in the prior art, the next page is usually entered by sliding left on the touch screen.
Preferably, when the user wants to enter the component management container, a touch operation is issued to the terminal. When the desktop container home page is displayed, the touch operation receiving unit 601 receives a touch operation into the desktop container. The touch operation direction is opposite to the touch operation direction of the next page entering the desktop container. Since the desktop is usually slid leftwards to enter the next page of the desktop in the prior art, the scheme here can receive the right sliding touch operation for the terminal.
Therefore, preferably, the touch operation receiving unit includes a touch operation receiving subunit, and the touch operation receiving subunit is configured to receive a touch operation entering the component management container when the current screen displays the top page of the desktop container, where a direction of the touch operation is opposite to a direction of a touch operation entering a next page of the desktop container. In the preferred embodiment, the component management container can be set as a related page of the desktop container. And in order not to change the operation habit of the user, the serial number of the component management container is set as page 0, when the terminal displays page 1 of the desktop container, the user slides to the opposite direction of the next page on the touch screen to enter the component management container, and slides to the right on the premise that the user slides to the next page in the prior art, so that the seamless connection with the desktop container is realized.
The touch operation receiving unit 601 is communicably connected to the subsequent refresh request transmitting unit 602.
A refresh request sending unit 602, configured to send a refresh request to a server when the terminal receives an instruction to enter the component management container.
When the terminal receives an instruction to enter the component management container, a refresh request sending unit 602 is triggered to send a refresh request to the server. The refresh request is used to request for refresh data from a server, where the refresh request includes state information of a component included in the current desktop container of the terminal, so that the server sends corresponding refresh data to the terminal according to the state information of the component, for example, a list of currently installed components and a version number thereof, which is not specifically limited herein.
Preferably, according to the exemplary discussion of embodiment 4 of the present invention, the manageable states of the components include: at least one of a to-be-installed state, a to-be-updated state, and a to-be-operated state.
The to-be-installed state is used for indicating that the component is to be installed, the to-be-updated state is used for indicating that the component is to be updated, and the to-be-operated state is used for indicating that the component is installed and does not need to be updated.
In addition, the server may be a data server or an application server, and this embodiment is not particularly limited.
The refresh request transmission unit 602 and the refresh data reception unit 603 are communicably connected.
A refresh data receiving unit 603, configured to receive refresh data sent by the server.
When the server receives the refresh request sent by the refresh request sending unit 602, the server sends corresponding refresh data to the terminal according to the state information of the component included in the refresh request, and at this time, the refresh data receiving unit 603 receives the refresh data sent by the server.
Wherein the refresh data is determined from state information of the component. For example, if the version number of the component a in the current terminal is 1.0 and the version number of the component a in the server is 2.0, the refresh data will include information that the component a is to be updated, and the subsequent steps will prompt the user to: component a may be updated from version 1.0 to version 2.0. For another example, the state information of the component included in the refresh request sent by the current terminal does not include a component B, and the server includes an installation source of the component B, and the following steps will prompt the user to: component B may be selected for installation.
A status icon display unit 604, configured to display a status icon of the component according to the refresh data.
The manageable state display unit 503 in the third embodiment of the present invention is specifically the state icon display unit 604 in this embodiment.
After the refresh data receiving unit 603 receives the refresh data, the state icon displaying unit 604 displays the state icons of the components in the component management container according to the refresh data. Preferably, the status icon of the component is a status corner mark added to the original icon of the component for indicating the manageable status of the component. The foregoing preferred examples have mentioned that the manageable states of the components include: at least one of the to-be-installed state, the to-be-updated state and the to-be-operated state, and correspondingly, the state corner mark may include at least one of the to-be-installed corner mark, the to-be-updated corner mark and the to-be-operated corner mark. The form of the state angle scale is shown in fig. 4, and the three state angle scales are an angle scale to be installed 401, an angle scale to be updated 402 and an angle scale to be operated 403. It should be noted that fig. 4 is only an example according to the embodiment of the present invention, and other manners may be used to display the status icons of the components. In addition, the state icon added with the to-be-operated corner mark may be an original icon of the component, which is not limited in the embodiment of the present invention.
The to-be-installed corner mark is used for indicating that the manageable state of the component is the to-be-installed state, the to-be-updated corner mark is used for indicating that the manageable state of the component is the to-be-updated state, and the to-be-operated corner mark is used for indicating that the manageable state of the component is the to-be-operated state.
As described above, the step of displaying the status icon of the component by the status icon display unit 604 specifically includes:
if the refresh data indicates that the component is installed and does not need to be updated, that is, the manageable state of the component is a to-be-operated state, the state icon display unit 604 displays the corresponding state corner mark as the to-be-operated corner mark;
if the refresh data indicates that the component is to be installed, that is, the manageable state of the component is the to-be-installed state, the state icon display unit 604 displays the corresponding state corner mark as the to-be-installed corner mark;
if the refresh data indicates that the component is to be updated, that is, the manageable state of the component is the state to be updated, the state icon display unit 604 displays the corresponding state corner mark as the corner mark to be updated.
In this embodiment, a component management container is provided, when entering the component management container, the refresh request sending unit 602 sends a refresh request to the server to request for refreshing data, and the status icon display unit 604 displays a status icon of the component according to the refresh data, where the status icon of the component is used to indicate a manageable status of the component. The components in the OS are managed in a unified mode through the component management container, so that the difficulty of component management is reduced, the efficiency of component management is improved, and the operation experience of a user is improved.
It will be understood by those skilled in the art that all or part of the steps in the method for implementing the above embodiments may be implemented by hardware that is instructed to implement by a program, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
While the above-mentioned detailed description of the component management method for a terminal and the related terminal provided by the present invention have been described, for those skilled in the art, there may be variations in the specific implementation and application scope according to the concepts of the embodiments of the present invention, and in summary, the content of the present description should not be construed as limiting the present invention.
Claims (2)
1. A method for managing components of a terminal, comprising:
the terminal comprises at least two containers, wherein the containers are display areas of the components; the container at least comprises a component management container used for displaying the current manageable state of the component, and the container at least comprises a desktop container used for displaying the desktop component of the terminal; the desktop container comprises a plurality of pages, and the component management container is set as a related page of the desktop container;
when the terminal receives an instruction of entering the component management container, the terminal sends a refreshing request to a server; the refreshing request comprises state information of components in a current desktop container of the terminal;
the terminal receives refreshing data sent by a server and displays the current manageable state of the component in the component management container according to the refreshing data; the refresh data is determined from state information of the component;
the manageable state comprises at least one of a state to be installed, a state to be updated and a state to be operated; wherein,
the to-be-installed state is used for indicating that the component is to be installed;
the to-be-updated state is used for indicating that the component is to be updated;
the to-be-operated state is used for indicating that the component is installed and does not need to be updated; the to-be-operated state comprises information of components to be started, deleted and browsed;
the displaying the current manageable state of the component according to the refresh data comprises:
displaying a state icon of the component according to the refreshing data, wherein the state icon is formed by adding a state corner mark on an original icon of the component and is used for indicating the manageable state of the component, and the state corner mark comprises at least one of a corner mark to be installed, a corner mark to be updated and a corner mark to be operated; wherein,
the to-be-installed corner mark is used for indicating that the manageable state of the component is the to-be-installed state;
the corner mark to be updated is used for indicating that the manageable state of the component is the state to be updated;
the to-be-operated corner mark is used for indicating that the manageable state of the component is the to-be-operated state;
after the terminal receives the instruction to enter the component management container, the method further comprises: receiving a touch operation entering the component management container;
the receiving a touch operation into the component management container comprises: and when the current screen displays the home page of the desktop container, receiving touch operation entering the component management container, wherein the direction of the touch operation is opposite to the direction of the touch operation entering the next page of the desktop container.
2. A terminal, comprising:
at least two containers, the containers being display areas of the assembly; the container at least comprises a component management container used for displaying the current manageable state of the component, and the container at least comprises a desktop container used for displaying the desktop component of the terminal; the desktop container comprises a plurality of pages, and the component management container is set as a related page of the desktop container;
a refresh request sending unit, configured to send a refresh request to a server when the terminal receives an instruction to enter the component management container; the refreshing request comprises state information of components in a current desktop container of the terminal;
the refreshing data receiving unit is used for receiving refreshing data sent by the server; the refresh data is determined from state information of the component;
a manageable state display unit, which is used for displaying the current manageable state of the component in the component management container according to the refreshing data;
the manageable states of the components in the at least two containers comprise at least one of a to-be-installed state, a to-be-updated state and a to-be-operated state; wherein,
the to-be-installed state is used for indicating that the component is to be installed;
the to-be-updated state is used for indicating that the component is to be updated;
the to-be-operated state is used for indicating that the component is installed and does not need to be updated; the to-be-operated state comprises information of components to be started, deleted and browsed;
the manageable state display unit is specifically a state icon display unit and is used for displaying the state icons of the components according to the refreshing data, the state icons are formed by adding state corner marks on original icons of the components and are used for indicating the manageable states of the components, and the state corner marks comprise at least one of corner marks to be installed, corner marks to be updated and corner marks to be operated; wherein,
the to-be-installed corner mark is used for indicating that the manageable state of the component is the to-be-installed state;
the corner mark to be updated is used for indicating that the manageable state of the component is the state to be updated;
the to-be-operated corner mark is used for indicating that the manageable state of the component is the to-be-operated state;
the terminal further comprises: a touch operation receiving unit for receiving a touch operation of entering the component management container;
the touch operation receiving unit receives a touch operation including: and the touch operation receiving subunit is used for receiving the touch operation of entering the component management container when the current screen displays the home page of the desktop container, and the direction of the touch operation is opposite to the direction of the touch operation of entering the next page of the desktop container.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210045916.XA CN102646054B (en) | 2012-02-27 | 2012-02-27 | Terminal assembly management method and terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210045916.XA CN102646054B (en) | 2012-02-27 | 2012-02-27 | Terminal assembly management method and terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102646054A CN102646054A (en) | 2012-08-22 |
| CN102646054B true CN102646054B (en) | 2014-11-05 |
Family
ID=46658883
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210045916.XA Active CN102646054B (en) | 2012-02-27 | 2012-02-27 | Terminal assembly management method and terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102646054B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103019680B (en) * | 2012-11-20 | 2016-01-13 | 东莞宇龙通信科技有限公司 | Mobile terminal and the application icon display packing for mobile terminal |
| CN103605551A (en) * | 2013-11-28 | 2014-02-26 | 金蝶软件（中国）有限公司 | Plugin updating method, system and relevant equipment based on IOS program |
| CN104714815A (en) * | 2013-12-13 | 2015-06-17 | 乐视网信息技术（北京）股份有限公司 | Method for updating application software and device |
| CN105451085A (en) * | 2015-12-16 | 2016-03-30 | 深圳创维数字技术有限公司 | Desktop data background editing method and desktop data editing server side |
| CN113055702B (en) * | 2018-02-08 | 2023-06-27 | 广州虎牙信息科技有限公司 | Method, system and client for displaying business components |
| CN109032464B (en) * | 2018-09-10 | 2020-12-01 | 腾讯科技（深圳）有限公司 | Interface switching method, device, equipment and storage medium in application program |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101636720A (en) * | 2007-03-20 | 2010-01-27 | 株式会社爱可信 | Terminal having application update managing function, and application update managing program and system |
| CN102123385A (en) * | 2011-03-01 | 2011-07-13 | 宇龙计算机通信科技(深圳)有限公司 | Updating prompt method of application programs on terminal and terminal |
| CN102143128A (en) * | 2010-06-30 | 2011-08-03 | 华为技术有限公司 | Method, device and system for updating desktop shortcut of mobile terminal |
-
2012
- 2012-02-27 CN CN201210045916.XA patent/CN102646054B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101636720A (en) * | 2007-03-20 | 2010-01-27 | 株式会社爱可信 | Terminal having application update managing function, and application update managing program and system |
| CN102143128A (en) * | 2010-06-30 | 2011-08-03 | 华为技术有限公司 | Method, device and system for updating desktop shortcut of mobile terminal |
| CN102123385A (en) * | 2011-03-01 | 2011-07-13 | 宇龙计算机通信科技(深圳)有限公司 | Updating prompt method of application programs on terminal and terminal |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102646054A (en) | 2012-08-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10187872B2 (en) | Electronic device and method of providing notification by electronic device | |
| CN114629865B (en) | Instant messaging system for interacting with dynamically expanding applications | |
| CN108874341B (en) | Screen projection method and terminal equipment | |
| CN107748740B (en) | Code-free sharing of spreadsheet objects | |
| CN102646054B (en) | Terminal assembly management method and terminal | |
| KR101379574B1 (en) | Terminal and method for displaying status of application | |
| WO2017032005A1 (en) | Operation menu display method and terminal | |
| EP4246258A1 (en) | Scene establishment method and apparatus, and computer device and computer-readable storage medium | |
| CN103941964B (en) | Information loading method based on desktop components and intelligent terminal | |
| CN105786485A (en) | Mobile terminal and background display method for applications thereof | |
| JP7635925B2 (en) | Electronic document processing method, device, terminal, and storage medium | |
| CN103279540A (en) | Method and device for pushing application | |
| AU2015376591A1 (en) | Desktop sharing method and mobile terminal | |
| CN103019520A (en) | Display method for optional item information of terminal application and terminal | |
| CN108427598A (en) | Message treatment method, device, terminal and storage medium | |
| CN111857453A (en) | Functional interface display method, computer device and storage medium | |
| EP2587356A2 (en) | Controlling method for basic screen and portable device therefore | |
| KR101985990B1 (en) | Information processing terminal, method and storage medium | |
| CN112286554A (en) | Application program updating method, apparatus, electronic device and readable storage medium | |
| EP2933957B1 (en) | Method and mobile terminal for displaying dlna equipment | |
| WO2021142892A1 (en) | Display device, and method for presenting user interface | |
| CN103294351A (en) | Display method and electronic device | |
| WO2022218192A1 (en) | File processing method and apparatus | |
| CN112130734B (en) | Document management method and device based on floating layer technology | |
| CN105279164B (en) | File processing method and device based on IOS (input/output system) |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20171027 Address after: Metro Songshan Lake high tech Industrial Development Zone, Guangdong Province, Dongguan City Road 523808 No. 2 South Factory (1) project B2 -5 production workshop Patentee after: HUAWEI terminal (Dongguan) Co., Ltd. Address before: 518129 Longgang District, Guangdong, Bantian HUAWEI base B District, building 2, building No. Patentee before: Huawei Device Co., Ltd. |
|
| CP01 | Change in the name or title of a patent holder | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 523808 Southern Factory Building (Phase I) Project B2 Production Plant-5, New Town Avenue, Songshan Lake High-tech Industrial Development Zone, Dongguan City, Guangdong Province Patentee after: Huawei Device Co., Ltd. Address before: 523808 Southern Factory Building (Phase I) Project B2 Production Plant-5, New Town Avenue, Songshan Lake High-tech Industrial Development Zone, Dongguan City, Guangdong Province Patentee before: HUAWEI terminal (Dongguan) Co., Ltd. |