WO2023174200A1 - 界面显示方法及相关装置 - Google Patents

界面显示方法及相关装置 Download PDF

Info

Publication number
WO2023174200A1
WO2023174200A1 PCT/CN2023/081017 CN2023081017W WO2023174200A1 WO 2023174200 A1 WO2023174200 A1 WO 2023174200A1 CN 2023081017 W CN2023081017 W CN 2023081017W WO 2023174200 A1 WO2023174200 A1 WO 2023174200A1
Authority
WO
WIPO (PCT)
Prior art keywords
component
application
page
label
display
Prior art date
Application number
PCT/CN2023/081017
Other languages
English (en)
French (fr)
Inventor
倪银堂
Original Assignee
华为技术有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Priority claimed from CN202210586578.4A external-priority patent/CN116795461A/zh
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023174200A1 publication Critical patent/WO2023174200A1/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/451—Execution arrangements for user interfaces

Definitions

  • the present application relates to the field of electronic technology, and in particular to interface display methods and related devices.
  • the user When the user finishes using an application (for example, Application 1) and exits the application, he or she can switch the application to run in the background and switch the display interface of the mobile phone to the desktop or the interface of other applications.
  • the historical task interface of the mobile phone can display the application identification of each application (such as application 1) running in the background.
  • the application identification of application 1 can include the exit interface of application 1 (That is, the interface snapshot of the user interface displayed by Application 1 when the user exits Application 1); by clicking the application logo of Application 1 in the historical task interface, the phone can quickly switch to the exit interface of Application 1.
  • the exit interface of Application 1 is not necessarily where the user wants Application 1 to be displayed.
  • the user may want to view a specific component in Application 1.
  • the user needs to enter Application 1 and click multiple times to reach this specific component.
  • the exit interface of Application 1 is the chat page with Contact A.
  • the user can switch pages through background tasks to reach the chat page of Contact A, and then perform multiple steps. Only then can you reach the display position of the voting component. This operation is very cumbersome and affects the user experience.
  • This application provides an interface display method and related devices, which can quickly view relevant information of specific components in the application.
  • the above-mentioned relevant information includes the display position and display content of the components, effectively improving the user experience.
  • this application provides an interface display method, applied to an electronic device including a touch display screen.
  • the method includes: displaying a first page of a first application, the content of the first page including one or more components, the The one or more components include a first component; a first operation of receiving input, wherein the first operation includes at least one input operation; in response to the first operation, displaying a second page of the first application or a third page of the second application; Receive a second operation of input; in response to the second operation, display a fourth page, and the fourth page displays at least one component label, and the at least one component label includes the first component label; when receiving the first component label acting on the first component label During the third operation, in response to the third operation, the first application is opened, the first page is displayed, and the first component is displayed on the first page.
  • the component tags associated with each component can be displayed on the fourth page.
  • the component associated with the component tag for example, the first component associated with the first component tag
  • the display position in the application effectively improves the user experience.
  • the first page of the first application is displayed.
  • the content of the first page includes one or more components.
  • the one or more components include the first component, including: displaying the first page of the first application.
  • the first part of the first page, the first page also includes a second part; wherein when the input sliding gesture is detected, the second part of the first page is displayed, the second part is The section includes the first component.
  • the display screen can only display part of the first page (for example, the second part), and the user can view the currently undisplayed part of the first page (for example, the first part) through a sliding gesture.
  • the second part includes the first component, and the first part does not include the first component; even if the first application is switched to running in the background when the display screen displays the first part, through the third operation for the first component label associated with the first component, It is also possible to quickly locate the display position of the first component in the second part of the first page in the first application, and display the second part including the first component, which effectively improves the user experience.
  • the method further includes: the first component is a plug-in component, and when receiving a fourth operation acting on the label of the first component, in response to the fourth operation, opening the first application and displaying the first component The first content page, where the third operation is different from the fourth operation.
  • the user can open the first content page of the first component in the first application by operating (for example, clicking) the first component displayed on the first page of the first application; the above scenario , through the fourth operation on the component tag associated with the first component, the first application can be quickly called to display the first content page of the first component.
  • the method further includes: the first component is a plug-in component, and when receiving a fourth operation acting on the label of the first component, in response to the fourth operation, opening a third application and displaying the first component The second content page, where the third operation is different from the fourth operation.
  • the user can open the second content page related to the first component in the third application by operating (for example, clicking) the first component displayed on the first page of the first application; the above
  • the third application can be quickly called to display the second content page.
  • the first component displayed on the first page provides a first function related to the display content of the first component; the first content page or the second content page provides a third function related to the display content of the first component.
  • First function and second function the first component cannot provide the second function.
  • the first component can only provide some functions related to the display content of the first component. If the user needs to experience more functions related to the display content of the first component, the user can call the first component through the fourth operation.
  • the content page or the second content page, the first content page or the second content page can be understood as a detail page of the display content of the first component, which can provide richer functions.
  • the method further includes: displaying a fifth page, where the fifth page includes an application identification corresponding to the first application; the fifth page further includes: At least one extended control; receiving a fifth operation acting on the extended control; in response to the fifth operation, displaying a fourth page; the above-mentioned application identification may be an application identification of an application that calls the component.
  • the fifth page called up by the user through the second operation displays the application identification of the application that calls the component and the extended controls corresponding to each application identification. The component labels are not displayed; the user can control the application identification corresponding to any one of them.
  • the fourth page further includes a first control and a second control
  • the method further includes: when receiving a touch input acting on the first control, displaying a sixth page, where the sixth page includes at least one user identification and a first component label; when receiving a third operation acting on the first component label on the sixth page; in response to the third operation, displaying the first page and displaying the first component on the first page .
  • the above-mentioned user ID may be the user ID of a user using the component.
  • the terminal device When operating; in response to the third operation, display the first page and display the first component on the first page.
  • the above device identification may be a user identification of the device that calls the component.
  • the terminal device in the fourth page, can adopt a variety of display modes to display the user's Display component labels of components; users can also switch the display mode of component labels according to their own needs.
  • the fourth page displays the application identification of each application that calls the component, and the component label of the component called by the application indicated by any application identification; for example, the fourth page displays the user identification of each user who uses the component, and any The component label of the component used by the user indicated by a user identification; for example, the fourth page displays the device identification of each device that calls the component, and the component label of the component called by the device indicated by any device identification.
  • the fourth page is a historical task interface
  • the display content of the fourth page includes an interface snapshot of the first application.
  • the first component includes: a component called by the first application; or, during the latest running of the first application, a component called by the first application; or, within the first preset time period, the first component The components called by the application; or, within the second preset time period, the preset number of components with the highest usage rate among the components called by the first application.
  • the at least one component label includes at least two component labels, wherein the arrangement order of the two component labels is determined based on the latest usage time and/or frequency of use of the component indicated by the component label.
  • the arrangement order of component labels is based on the last use time and/or frequency of use of the components, which is more suitable for the user's usage needs.
  • the third operation is a click operation on the first component label; the fourth operation is a sliding operation of dragging the first component label to the third control after long-pressing the first component label.
  • the third control displays an application identification of the third application and/or third prompt information, and the third prompt information is used to prompt the third application to display the third component by dragging the first component label to the third control. Content related to a component.
  • the third control is displayed after detecting a long press operation on the first component label.
  • the fourth page includes a fourth control and a fifth control; the third operation includes a sliding operation from the first component label to the fourth control; the fourth operation includes a sliding operation from the first component label to the fifth control. Slide operation.
  • the third operation includes long-pressing the first component label and then dragging the first component label to the sliding operation of the fourth control; the fourth operation includes long-pressing the first component label and then dragging the first component label to The sliding operation of the fifth control.
  • the fourth control and the fifth control are displayed after detecting a long press operation on the first component label.
  • the fourth control displays the application identification and/or the first prompt information of the first application
  • the fifth control displays the application identification and/or the second prompt information of the third application
  • the first prompt information is The second prompt information is used to prompt the component to be located in the application that calls the first component
  • the second prompt information is used to prompt the component to be opened through the application that provides the first component. It can be understood that the third application that provides the first component opens the first component and can display the second content page.
  • the third operation and the fourth operation are one of the following operations: a click operation acting on the first component label; a long press operation acting on the first component label; The sliding operation; the left sliding operation acting on the first component label; the upward sliding operation acting on the first component label; the sliding operation acting on the first component label; the third operation and the fourth operation are different.
  • the method further includes: when receiving a sixth operation acting on the first component label, in response to the sixth operation, displaying one or more of the following on the fourth page: at least one of the following in the first application
  • the user identification of one contact, the application identification of the fourth application, and the page identification of the designated page of the fourth application; the user identification of at least one contact includes The user ID of the first contact, the user ID of the first contact is used to share the first component to the first contact in the first application; the application ID of the fourth application is used to share the first component to the fourth application the contact in; the page identifier of the designated page of the fourth application is used to share the first component to the designated page of the fourth application.
  • the method further includes: when receiving a seventh operation acting on the first component label, the seventh operation is used to preview the first component in the first page, and in response to the seventh operation, according to the seventh operation
  • the original size or enlarged size of a component, and the component snapshot of the first component is displayed on the fourth page.
  • the method further includes: when receiving an eighth operation that acts on the first component label, in response to the eighth operation, stopping displaying the first component label, and moving component labels after the first component label to Displayed one position ahead.
  • the eighth operation acting on the component label of the component the user can delete the component note on the fourth page to view more other component notes, which effectively improves the user experience.
  • the components indicated by the component labels displayed on the fourth page are all components in the component management whitelist; the component management whitelist is set by one or more of the terminal device, the first application, and the user.
  • the component management whitelist can be used to set components that can be managed (such as component positioning) through the fourth page; users can set components in the component management whitelist according to personal needs to achieve personalized component management.
  • the first component is the first page.
  • the first component may be a component inserted or embedded in the first page, or may be the first page itself.
  • the first component tag includes the component identifier of the first component; the first component tag also includes zero, one or more of the following: the page identifier of the page where the first component is located, and provides the application of the first component.
  • the application identifier is the workspace identifier of the workspace where the first component is located; the component identifier includes one or more of the following: component icon, component name and component snapshot, the page identifier includes the page icon and/or page name, the application in the component tag
  • the identification includes the application icon and/or the application name, and the workspace identification includes the workspace icon and/or the workspace name.
  • the user can know the component associated with the component tag; when the component tag includes a page identifier, through the page identifier in the component tag, the user can know the page where the above component is located, and can also distinguish between different pages.
  • the same component inserted when the component label includes the workspace identifier, the user can know the workspace where the above component is located through the workspace identifier in the component label, and can also distinguish the same component inserted in different workspaces; when the component label includes the application identifier , through the application identification in the component tag, the user can know the application that provides the above component.
  • the first component label includes: the component icon or component snapshot of the first component, and the page name of the first page; or, the component icon or component snapshot of the first component, and the workspace where the first page is located. the workspace name; or, the component icon or component snapshot of the first component, and the component name of the first component; or, the page icon of the first page and the component name of the first component; or, the application that provides the first component The application icon and the component name of the first component.
  • the fourth page includes at least one application identifier, and the at least one application identifier includes a first application identifier; the component label display area corresponding to the first application identifier in the fourth page displays the first application identifier. At least one component tag associated with the component called by the indicated application. Implementing the embodiments of this application, the component notes on the fourth page can be classified and displayed based on the application that calls the component, enriching the display method of component labels and improving the user experience.
  • the fourth page includes at least one application identifier, and the at least one application identifier includes a second application identifier; the component label display area corresponding to the second application identifier in the fourth page displays the second application identifier. indicative At least one component tag associated with the component provided by the application.
  • the component notes on the fourth page can be classified and displayed based on the application that provides the component, enriching the display method of component labels and improving the user experience.
  • the fourth page includes at least one device identifier, and the at least one device identifier includes a first device identifier; and the component label display area corresponding to the first device identifier in the fourth page displays the first device identifier.
  • At least one component tag associated with the component called by the indicated device Implementing the embodiments of this application, the component notes on the fourth page can be classified and displayed based on the device that calls the component, enriching the display method of component labels and improving the user experience.
  • the fourth page includes at least one user identification, and the at least one user identification includes a first user identification; and the component label display area corresponding to the first user identification in the fourth page displays the first user identification. Indicates at least one component tag associated with the component used by the user. Implementing the embodiments of this application, the component notes on the fourth page can be classified and displayed based on the users who use the components, enriching the display method of component labels and improving the user experience.
  • the fourth page includes at least one page identifier, and the at least one page identifier includes the first page identifier; the component label display area corresponding to the first page identifier in the fourth page displays the first page identifier. At least one component tag associated with the component called by the indicated page. Implementing the embodiments of this application, the component notes on the fourth page can be classified and displayed based on the page where the component is located, enriching the display method of component labels and improving the user experience.
  • the fourth page includes at least one Widget identifier, and the at least one Widget identifier includes a first Widget identifier; the component label display area corresponding to the first Widget identifier in the fourth page displays: At least one component tag associated with the component added by the Widget indicated by the first Widget identifier.
  • the component notes on the fourth page can be classified and displayed based on the Widget to which the component is added, enriching the display method of component labels and improving the user experience.
  • the component labels on the fourth page can be displayed in a variety of ways; for example, based on the application that calls the component, the application that provides the component, the device that calls the component, the user who uses the component, the page where the component is located, the Widget that adds the component and other classification methods (or display dimensions) for classification display.
  • Such classified display makes the display of component labels clearer, allowing users to quickly locate the component labels they want to operate, enriching the display method of component labels, and improving the user experience.
  • the fourth page includes an application identification of the application that calls the component
  • the fourth page also includes a sixth control and/or a seventh control
  • the method further includes: when receiving a touch that acts on the sixth control When input, an eighth page is displayed, and the eighth page includes an application identification and a first component label of at least one application that provides the component; when receiving a third operation that acts on the first component label on the eighth page; in response to The third operation is to display the first page and display the first component on the first page; when receiving the touch input acting on the seventh control, display the ninth page, and the ninth page includes at least one component added.
  • Widget identification and the first component label of the Widget when receiving the third operation acting on the first component label on the ninth page; in response to the third operation, displaying the first page and displaying the first component on the first page .
  • users can also switch the display mode of component labels according to their own needs. In this way, users' different component label display needs and component label search needs can be met, the convenience of component use can be improved, and the user experience can be effectively improved.
  • the fourth page includes at least two application identifiers corresponding to the application that calls the component, and the at least two application identifiers include a first application identifier and a third application identifier; in the fourth page, at the same time, in the first
  • the component label display area corresponding to the application identification displays the component label associated with the component called by the application indicated by the first application identification
  • the component label display area corresponding to the third application identification displays the component association called by the application indicated by the third application identification.
  • component label can be displayed simultaneously on the fourth page to avoid additional user operations.
  • the at least one component tag further includes a second component tag
  • the second component tag is associated with the first component called on the tenth page of the first application, and the first component tag is different from the second component tag
  • the first component tag includes the page identifier of the first page
  • the second component tag includes the page identifier of the tenth page.
  • the present application provides a terminal device, which may include multiple functional modules or units for correspondingly executing the interface display method provided in the first aspect.
  • a terminal device may include multiple functional modules or units for correspondingly executing the interface display method provided in the first aspect.
  • display unit and receiving unit may include multiple functional modules or units for correspondingly executing the interface display method provided in the first aspect.
  • the display unit is used to display the first page of the first application, the content of the first page includes one or more components, and the one or more components include the first component;
  • a receiving unit configured to receive an input first operation, wherein the first operation includes at least one input operation
  • the display unit is also configured to display the second page of the first application or the third page of the second application in response to the first operation;
  • a receiving unit also configured to receive a second operation of the input
  • the display unit is further configured to display a fourth page in response to the second operation.
  • the fourth page displays at least one component label, and the at least one component label includes the first component label;
  • the display unit is also configured to, when receiving a third operation acting on the first component label, open the first application, display the first page, and display the first component on the first page in response to the third operation.
  • the above-mentioned display unit is specifically used to display the first part of the first page of the first application, and the first page also includes a second part; when an input sliding gesture is detected, the display unit is also used to display The second part of the first page, the second part contains the first component.
  • the first component is a plug-in component.
  • the display unit is further configured to open the first application in response to the fourth operation and display the The first content page of the first component, where the third operation is different from the fourth operation.
  • the method further includes: the first component is a plug-in component, and when the receiving unit receives the fourth operation acting on the first component label, the display unit is further configured to respond to the fourth operation, The third application is opened to display the second content page of the first component, where the third operation is different from the fourth operation.
  • the above-mentioned display unit is also used to display a fifth page.
  • the fifth page includes an application identification corresponding to the first application; the fifth page further includes at least An extended control; the above-mentioned receiving unit is also used to receive the fifth operation that acts on the extended control; the above-mentioned display unit is also used to display a fourth page in response to the fifth operation; the above-mentioned application identifier can be an application that calls the component's application logo.
  • the fourth page also includes a first control and a second control.
  • the above-mentioned display unit is also used to display the sixth page, as shown in the third page.
  • the six pages include at least one user identification and a first component label; when the receiving unit receives a third operation that acts on the first component label on the sixth page, the above-mentioned display unit is also configured to display the first component label in response to the third operation. page, and display the first component on the first page; the user ID may be the user ID of a user who uses the component.
  • the above-mentioned display unit When the receiving unit receives a touch input acting on the second control, the above-mentioned display unit is also used to display a seventh page, where the seventh page includes at least one device identification and a first component label; when the receiving unit receives a touch input acting on the second control, During the third operation of the first component label on the seven pages, the above-mentioned display unit is also used to display the first page in response to the third operation, and display the first component on the first page; the above-mentioned device identification may be a calling component The user ID of the device.
  • the fourth page is a historical task interface
  • the display content of the fourth page includes an interface snapshot of the first application.
  • the first component includes: a component called by the first application; or, the most recent component of the first application. During a run, the components called by the first application; or, within the first preset time period, the components called by the first application; or, within the second preset time period, the preset number of components with the highest usage rate among the components called by the first application s component.
  • the at least one component label includes at least two component labels, wherein the arrangement order of the two component labels is determined based on the latest usage time and/or frequency of use of the component indicated by the component label. .
  • the third operation is a click operation on the first component label; the fourth operation is a sliding operation of dragging the first component label to the third control after long-pressing the first component label.
  • the third control displays an application identification of the third application and/or third prompt information, and the third prompt information is used to prompt the third application to display the third component by dragging the first component label to the third control. Content related to a component.
  • the third control is displayed after detecting a long press operation on the first component label.
  • the fourth page includes a fourth control and a fifth control; the third operation includes a sliding operation from the first component label to the fourth control; the fourth operation includes a sliding operation from the first component label to the fifth control. Slide operation.
  • the third operation includes long-pressing the first component label and then dragging the first component label to the sliding operation of the fourth control; the fourth operation includes long-pressing the first component label and then dragging the first component label to The sliding operation of the fifth control.
  • the fourth control and the fifth control are displayed after detecting a long press operation on the first component label.
  • the fourth control displays the application identification and/or the first prompt information of the first application
  • the fifth control displays the application identification and/or the second prompt information of the third application
  • the first prompt information is The second prompt information is used to prompt the component to be located in the application that calls the first component
  • the second prompt information is used to prompt the component to be opened through the application that provides the first component.
  • the third operation and the fourth operation are one of the following operations: a click operation acting on the first component label; a long press operation acting on the first component label; The sliding operation; the left sliding operation acting on the first component label; the upward sliding operation acting on the first component label; the sliding operation acting on the first component label; the third operation and the fourth operation are different.
  • the display unit is further configured to display one or more of the following on the fourth page in response to the sixth operation: first application The user identification of at least one contact in the application, the application identification of the fourth application, and the page identification of the designated page of the fourth application; the user identification of the at least one contact includes the user identification of the first contact, the user identification of the first contact, and the user identification of the first contact.
  • the user identification is used to share the first component to the first contact in the first application;
  • the application identification of the fourth application is used to share the first component to the contact in the fourth application;
  • the page of the designated page of the fourth application The identifier is used to share the first component to a specified page of the fourth application.
  • the seventh operation is used to preview the first component in the first page
  • the above-mentioned display unit is also used to respond to the seventh operation , display the component snapshot of the first component on the fourth page according to the original size or the enlarged size of the first component.
  • the display unit when the receiving unit receives the eighth operation that acts on the first component label, the display unit is further configured to stop displaying the first component label in response to the eighth operation, and change the first component label after the first component label.
  • the component label is displayed one position forward.
  • the components indicated by the component labels displayed on the fourth page are all components in the component management whitelist; the component management whitelist is set by one or more of the terminal device, the first application, and the user.
  • this application provides a terminal device including one or more processors and one or more memories.
  • the one or more memories are coupled to one or more processors.
  • the one or more memories are used to store computer program codes.
  • the computer program codes include computer instructions.
  • the terminal device executes Interface display method in any possible implementation of any of the above aspects.
  • embodiments of the present application provide a computer storage medium that includes computer instructions.
  • the terminal device When the computer instructions are run on a terminal device, the terminal device causes the terminal device to execute the interface display method in any of the possible implementations of any of the above aspects. .
  • embodiments of the present application provide a computer program product.
  • the computer program product When the computer program product is run on a computer, it causes the computer to execute the interface display method in any of the possible implementations of any of the above aspects.
  • Figure 1 is a schematic structural diagram of a terminal device provided by an embodiment of the present application.
  • Figure 2A is the main interface provided by the embodiment of the present application.
  • Figures 2B to 2C are historical task interfaces provided by embodiments of the present application.
  • Figures 3A to 3D are exemplary interfaces for using the circle of friends page provided by the embodiment of the present application.
  • FIGS. 4A to 4G are exemplary interfaces for using the voting component provided by embodiments of the present application.
  • FIGS. 5A to 5F are exemplary interfaces for using the music playback component provided by embodiments of the present application.
  • Figures 6A to 6E are exemplary interfaces for using collaborative office applications provided by embodiments of the present application.
  • Figures 7A to 7J are historical task interfaces provided by embodiments of the present application.
  • FIGS 8 and 9 are schematic diagrams of component labels provided by embodiments of the present application.
  • Figures 10A to 10I are exemplary interfaces for component positioning provided by embodiments of the present application.
  • Figures 11A to 11H are exemplary interfaces for component positioning provided by embodiments of the present application.
  • Figures 12A to 12K are exemplary interfaces for the function of component tags provided by embodiments of the present application.
  • Figures 13A to 13D are exemplary interfaces for setting component management whitelists provided by embodiments of the present application.
  • Figure 14A and Figure 14B are a display method of component labels provided by the embodiment of the present application.
  • Figures 15A to 15D are another display method of component labels provided by the embodiment of the present application.
  • Figure 16A and Figure 16B are another display method of component labels provided by the embodiment of the present application.
  • Figures 17A to 17C are another display method of component labels provided by the embodiment of the present application.
  • Figure 18 is another display method of component labels provided by the embodiment of the present application.
  • Figure 19A and Figure 19B are another display method of component labels provided by the embodiment of the present application.
  • Figures 20A to 20E are exemplary interfaces for switching the display mode of component labels provided by the embodiment of the present application.
  • Figure 21 is a schematic flowchart of an interface display method provided by an embodiment of the present application.
  • first and second are used for descriptive purposes only and shall not be understood as implying or implying relative importance or implicitly specifying the quantity of indicated technical features. Therefore, the features defined as “first” and “second” may explicitly or implicitly include one or more of the features. In the description of the embodiments of this application, unless otherwise specified, “plurality” The meaning is two or more.
  • the structure of the terminal device 100 involved in the embodiment of the present application is introduced below.
  • the terminal device 100 may be a mobile phone, a tablet computer, a desktop computer, a laptop computer, a handheld computer, a pen Laptops, ultra-mobile personal computers (UMPC), netbooks, and cellular phones, personal digital assistants (PDAs), augmented reality (AR) devices, virtual reality , VR) equipment, artificial intelligence (AI) equipment, wearable equipment, vehicle equipment, smart home equipment and/or smart city equipment.
  • PDAs personal digital assistants
  • AR augmented reality
  • VR virtual reality
  • AI artificial intelligence
  • the terminal device can be equipped with iOS, Android, Microsoft or other operating systems, and there are no specific limitations here.
  • the terminal device 100 may include 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, and a battery 142 , Antenna 1, Antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone interface 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193 , display screen 194, and subscriber identification module (subscriber identification module, SIM) card interface 195, etc.
  • SIM subscriber identification module
  • the sensor module 180 may include a pressure sensor 180A, a gyro sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, and ambient light. Sensor 180L, bone conduction sensor 180M, etc.
  • the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the terminal device 100.
  • the terminal device 100 may include more or less components than shown in the figures, or combine some components, or split some components, or arrange different components.
  • the components illustrated may be implemented in hardware, software, or a combination of software and hardware.
  • the processor 110 may include one or more processing units.
  • the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processing unit (GPU), and an image signal processor. (image signal processor, ISP), controller, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural network processor (neural-network processing unit, NPU), etc.
  • application processor application processor, AP
  • modem processor graphics processing unit
  • GPU graphics processing unit
  • image signal processor image signal processor
  • ISP image signal processor
  • controller video codec
  • digital signal processor digital signal processor
  • DSP digital signal processor
  • baseband processor baseband processor
  • neural network processor neural-network processing unit
  • the controller can generate operation control signals based on the instruction operation code and timing signals to complete the control of fetching and executing instructions.
  • the processor 110 may also be provided with a memory for storing instructions and data.
  • the memory in processor 110 is cache memory. This memory may hold instructions or data that have been recently used or recycled by processor 110 . If the processor 110 needs to use the instructions or data again, it can be called directly from the memory. Repeated access is avoided and the waiting time of the processor 110 is reduced, thus improving the efficiency of the system.
  • processor 110 may include one or more interfaces.
  • Interfaces may include integrated circuit (inter-integrated circuit, I2C) interface, integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, pulse code modulation (pulse code modulation, PCM) interface, universal asynchronous receiver and transmitter (universal asynchronous receiver/transmitter (UART) interface, mobile industry processor interface (MIPI), general-purpose input/output (GPIO) interface, subscriber identity module (SIM) interface, and /or universal serial bus (USB) interface, etc.
  • I2C integrated circuit
  • I2S integrated circuit built-in audio
  • PCM pulse code modulation
  • UART universal asynchronous receiver and transmitter
  • MIPI mobile industry processor interface
  • GPIO general-purpose input/output
  • SIM subscriber identity module
  • USB universal serial bus
  • the charging management module 140 is used to receive charging input from the charger.
  • the charger can be a wireless charger or a wired charger.
  • the charging management module 140 may receive charging input from the wired charger through the USB interface 130 .
  • the charging management module 140 may receive wireless charging input through the wireless charging coil of the terminal device 100 . While charging the battery 142, the charging management module 140 can also The terminal device is powered through the power management module 141 .
  • the power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110.
  • the power management module 141 receives input from the battery 142 and/or the charging management module 140, and supplies power to the processor 110, the internal memory 121, the display screen 194, the camera 193, the wireless communication module 160, and the like.
  • the power management module 141 can also be used to monitor battery capacity, battery cycle times, battery health status (leakage, impedance) and other parameters.
  • the power management module 141 may also be provided in the processor 110 .
  • the power management module 141 and the charging management module 140 may also be provided in the same device.
  • the wireless communication function of the terminal device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.
  • Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals.
  • Each antenna in terminal device 100 may be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example: Antenna 1 can be reused as a diversity antenna for a wireless LAN. In other embodiments, antennas may be used in conjunction with tuning switches.
  • the mobile communication module 150 can provide wireless communication solutions including 2G/3G/4G/5G applied to the terminal device 100.
  • the mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc.
  • the mobile communication module 150 can receive electromagnetic waves through the antenna 1, perform filtering, amplification and other processing on the received electromagnetic waves, and transmit them to the modem processor for demodulation.
  • the mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves through the antenna 1 for radiation.
  • at least part of the functional modules of the mobile communication module 150 may be disposed in the processor 110 .
  • at least part of the functional modules of the mobile communication module 150 and at least part of the modules of the processor 110 may be provided in the same device.
  • a modem processor may include a modulator and a demodulator.
  • the modulator is used to modulate the low-frequency baseband signal to be sent into a medium-high frequency signal.
  • the demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal.
  • the demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing.
  • the application processor outputs sound signals through audio devices (not limited to speaker 170A, receiver 170B, etc.), or displays images or videos through display screen 194.
  • the modem processor may be a stand-alone device.
  • the modem processor may be independent of the processor 110 and may be provided in the same device as the mobile communication module 150 or other functional modules.
  • the wireless communication module 160 can provide applications on the terminal device 100 including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) network), Bluetooth (bluetooth, BT), and global navigation satellites.
  • WLAN wireless local area networks
  • System global navigation satellite system, GNSS
  • frequency modulation frequency modulation, FM
  • near field communication technology near field communication, NFC
  • infrared technology infrared, IR
  • 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 , demodulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110 .
  • the wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves through the antenna 2 for radiation.
  • the antenna 1 of the terminal device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the terminal device 100 can communicate with the network and other devices through wireless communication technology.
  • the wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), broadband Code division multiple access (wideband code division multiple access, WCDMA), time division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution, LTE), BT, GNSS, WLAN, NFC, FM, and/or IR technology, etc.
  • the GNSS may include global positioning system (GPS), global navigation satellite system (GLONASS), Beidou navigation satellite system (BDS), quasi-zenith satellite system (quasi -zenith satellite system (QZSS) and/or satellite based augmentation systems (SBAS).
  • GPS global positioning system
  • GLONASS global navigation satellite system
  • BDS Beidou navigation satellite system
  • QZSS quasi-zenith satellite system
  • SBAS satellite based augmentation systems
  • the terminal device 100 implements display functions through a GPU, a display screen 194, an application processor, and the like.
  • the GPU is an image processing microprocessor and is connected to the display screen 194 and the application processor. GPUs are used to perform mathematical and geometric calculations for graphics rendering.
  • Processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.
  • the display screen 194 is used to display images, videos, etc.
  • Display 194 includes a display panel.
  • the display panel can use a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active matrix organic light emitting diode or an active matrix organic light emitting diode (active-matrix organic light emitting diode).
  • LCD liquid crystal display
  • OLED organic light-emitting diode
  • AMOLED organic light-emitting diode
  • FLED flexible light-emitting diode
  • Miniled MicroLed, Micro-oLed, quantum dot light emitting diode (QLED), etc.
  • the terminal device 100 may include 1 or N display screens 194, where N is a positive integer greater than 1.
  • the terminal device 100 can implement the shooting function through the ISP, camera 193, video codec, GPU, display screen 194, application processor, etc.
  • the ISP is used to process the data fed back by the camera 193. For example, when taking a photo, the shutter is opened, the light is transmitted to the camera sensor through the lens, the optical signal is converted into an electrical signal, and the camera sensor passes the electrical signal to the ISP for processing, and converts it into an image visible to the naked eye. ISP can also perform algorithm optimization on image noise and brightness. ISP can also optimize the exposure, color temperature and other parameters of the shooting scene. In some embodiments, the ISP may be provided in the camera 193.
  • Camera 193 is used to capture still images or video.
  • the object passes through the lens to produce an optical image that is projected onto the photosensitive element.
  • the photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor.
  • CMOS complementary metal-oxide-semiconductor
  • the photosensitive element converts the optical signal into an electrical signal, and then passes the electrical signal to the ISP to convert it into a digital image signal.
  • ISP outputs digital image signals to DSP for processing.
  • DSP converts digital image signals into standard RGB, YUV and other format image signals.
  • the terminal device 100 may include 1 or N cameras 193, where N is a positive integer greater than 1.
  • Digital signal processors are used to process digital signals. In addition to digital image signals, they can also process other digital signals. For example, when the terminal device 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.
  • Video codecs are used to compress or decompress digital video.
  • the terminal device 100 may support one or more video codecs. In this way, the terminal device 100 can play or record videos in multiple encoding formats, such as moving picture experts group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.
  • MPEG moving picture experts group
  • MPEG2 MPEG2, MPEG3, MPEG4, etc.
  • NPU is a neural network (NN) computing processor.
  • NN neural network
  • the NPU can realize intelligent cognitive applications of the terminal device 100, such as image recognition, face recognition, speech recognition, text understanding, etc.
  • the internal memory 121 may include one or more random access memories (RAM) and one or more non-volatile memories (NVM).
  • RAM random access memories
  • NVM non-volatile memories
  • Random access memory can include static random-access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (double data rate synchronous dynamic random access memory, DDR SDRAM, for example, the fifth generation DDR SDRAM is generally called DDR5SDRAM), etc.; non-volatile memory can include disk storage devices and flash memory (flash memory).
  • SRAM static random-access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • DDR SDRAM double data rate synchronous dynamic random access memory
  • non-volatile memory can include disk storage devices and flash memory (flash memory).
  • Flash memory can be divided according to the operating principle to include NOR FLASH, NAND FLASH, 3D NAND FLASH, etc.
  • the storage unit potential level it can include single-level storage cells (single-level cell, SLC), multi-level storage cells (multi-level cell, MLC), third-level storage unit (triple-level cell, TLC), fourth-level storage unit (quad-level cell, QLC), etc., which can include universal flash storage (English: universal flash storage, UFS) according to storage specifications. , embedded multi media card (embedded multi media Card, eMMC), etc.
  • the random access memory can be directly read and written by the processor 110, can be used to store executable programs (such as machine instructions) of the operating system or other running programs, and can also be used to store user and application data, etc.
  • the non-volatile memory can also store executable programs and user and application program data, etc., and can be loaded into the random access memory in advance for direct reading and writing by the processor 110.
  • the external memory interface 120 can be used to connect an external non-volatile memory to expand the storage capacity of the terminal device 100 .
  • the external non-volatile memory communicates with the processor 110 through the external memory interface 120 to implement the data storage function. For example, save music, video and other files in external non-volatile memory.
  • the terminal device 100 can implement audio functions through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone interface 170D, and the application processor. Such as music playback, recording, etc.
  • the audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. Audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be provided in the processor 110 , or some functional modules of the audio module 170 may be provided in the processor 110 .
  • Speaker 170A also called “speaker” is used to convert audio electrical signals into sound signals.
  • Receiver 170B also called “earpiece” is used to convert audio electrical signals into sound signals.
  • Microphone 170C also called “microphone” or “microphone”, is used to convert sound signals into electrical signals.
  • the headphone interface 170D is used to connect wired headphones.
  • the pressure sensor 180A is used to sense pressure signals and can convert the pressure signals into electrical signals.
  • pressure sensor 180A may be disposed on display screen 194 .
  • the gyro sensor 180B may be used to determine the motion posture of the terminal device 100 .
  • the angular velocity of the terminal device 100 about three axes ie, x, y, and z axes
  • the gyro sensor 180B may be determined by the gyro sensor 180B.
  • Air pressure sensor 180C is used to measure air pressure.
  • Magnetic sensor 180D includes a Hall sensor.
  • the acceleration sensor 180E can detect the acceleration of the terminal device 100 in various directions (generally three axes). When the terminal device 100 is stationary, the magnitude and direction of gravity can be detected. It can also be used to identify the gesture of the terminal device.
  • the terminal device 100 can measure distance through infrared or laser.
  • Proximity light sensor 180G may include, for example, a light emitting diode (LED) and a light detector, such as a photodiode.
  • LED light emitting diode
  • a light detector such as a photodiode
  • the ambient light sensor 180L is used to sense ambient light brightness.
  • the terminal device 100 can adaptively adjust the brightness of the display screen 194 according to the perceived ambient light brightness.
  • Fingerprint sensor 180H is used to collect fingerprints.
  • Temperature sensor 180J is used to detect temperature.
  • the terminal device 100 utilizes a temperature sensor 180J Detect the temperature and execute the temperature processing strategy.
  • Touch sensor 180K also known as "touch device”.
  • the touch sensor 180K can be disposed on the display screen 194.
  • the touch sensor 180K and the display screen 194 form a touch screen, which is also called a "touch screen”.
  • the touch sensor 180K is used to detect a touch operation on or near the touch sensor 180K.
  • the touch sensor can pass the detected touch operation to the application processor to determine the touch event type.
  • Visual output related to the touch operation may be provided through display screen 194 .
  • the touch sensor 180K may also be disposed on the surface of the terminal device 100 in a position different from that of the display screen 194 .
  • Bone conduction sensor 180M can acquire vibration signals.
  • the buttons 190 include a power button, a volume button, etc.
  • Key 190 may be a mechanical key. It can also be a touch button.
  • the terminal device 100 may receive key input and generate key signal input related to user settings and function control of the terminal device 100 .
  • GUI graphical user interface
  • FIG. 2A exemplarily shows the main interface 11 for displaying applications installed on the terminal device 100 .
  • the main interface 11 may include: a status bar, a calendar indicator, a weather indicator, a tray with commonly used application icons, a navigation bar 201, and a display area 202 for other application icons. in:
  • the navigation bar 201 may include system navigation keys such as a return key 201A, a home screen key 201B, and a multi-task key 201C.
  • system navigation keys such as a return key 201A, a home screen key 201B, and a multi-task key 201C.
  • the terminal device 100 can display the application identification of each application that the user has recently viewed and is still running in the background on the historical task interface, as shown in Figure 2B; by clicking on one of the historical task interfaces With the application identifier of the application, the terminal device 100 can quickly switch to the exit interface of the application, that is, the user interface displayed by the application when the user exits the application.
  • Each navigation key can also be named by other names, which is not limited by this application.
  • the main interface 11 may not include the navigation bar 201, and each navigation key in the navigation bar 201 may be implemented as a physical key or navigation gesture.
  • the terminal device 100 implements the functions of each navigation key in the navigation bar 201 through the user's designated navigation gesture.
  • the navigation gesture corresponding to the return key 201A includes a gesture of sliding inward from the left edge of the display screen 194 of the terminal device 100
  • the navigation gesture corresponding to the home screen key 201B includes a gesture of sliding inward from the left half of the bottom edge of the display screen 194 of the terminal device 100.
  • the navigation gesture corresponding to the multitasking key 201C includes a sliding upward gesture from the right half of the bottom edge of the display screen 194 of the terminal device 100 .
  • the display area 202 of other application icons can display: instant messaging application icon 202A, collaborative office application album icon 202B, gallery icon, music icon, application mall icon, cloud sharing icon, memo icon, settings icon. Icon 202C.
  • the main interface 11 may also include a page indicator 203 .
  • Other application icons may be distributed on multiple pages, and the page indicator 203 may be used to indicate which application in which page the user is currently viewing. Users can slide the area of other application icons left and right to view application icons in other pages.
  • the terminal device 100 when the user opens a new application, the terminal device 100 can switch the application running in the foreground to the background, add the application window in which the application is running to the multi-task queue, and store the above application program
  • the snapshot of the user interface last displayed in the window is used as the interface snapshot of the application window in the historical task interface.
  • the above snapshot of the user interface can be a screenshot of the user interface.
  • Figure 2B and Figure 2C are two display forms of historical task interfaces provided by embodiments of the present application.
  • the terminal device 100 may receive an input operation (such as a touch operation) acting on the multitasking key 201C.
  • the terminal device 100 may display the display as shown in FIG. 2B or 2C based on the above multitasking queue.
  • the historical task interface 21 is used to display the application identification of each application in the multi-task queue (for example, the application identification 204 of the collaborative office application, the application identification 205 of the instant messaging application).
  • the application identification may include application icons, application names and interface snapshots.
  • the application identification 204 includes an application icon 204A, an application name 204B, and an interface snapshot 204C. Due to the size of the screen, when the terminal device 100 cannot display the application identifiers of all applications in the multi-task queue, the user can view the application identifiers of more applications by sliding left/right on the historical task interface 21 .
  • the application identifiers of each application are displayed in the form of two rows and multiple columns.
  • the application identifiers of each application are arranged from top to bottom and from right to left.
  • the last one in the multi-task queue is switched to
  • the application IDs of background applications are arranged in the first row of the leftmost column.
  • the application identification of each application is displayed in the form of one row and multiple columns.
  • the application identification of each application is arranged from right to left.
  • the logos are arranged in the leftmost column.
  • the interface snapshot in the application identifier 204 is different from the display size of the actual user interface.
  • the terminal device 100 when the terminal device 100 displays the historical task interface, the terminal device 100 reduces the screenshot above at a preset ratio and displays it in the application logo 204 .
  • the display content of the above user interface is re-layout, and the snapshot of the re-layout user interface is used as the interface snapshot in the application identifier 204 .
  • a snapshot of part of the content in the user interface is selected as the interface snapshot in the application identifier 204 .
  • Component It can also be called a functional entity, usually used to implement one or more specific functions. Some components will provide some standard application interfaces, allowing users to set and adjust parameters and properties, and optionally can be assembled by third parties in some cases. Loop components refer to components that can be kept synchronized (that is, kept up-to-date) in different applications.
  • the components involved in the embodiments of this application can include type A components and type B components from the perspective of component expression; type A components refer to components that can be inserted into specific pages, such as list components, table components, document components, and forms. Components (such as voting forms), dialog components for specifying contacts or group chats, etc., or cards suspended on the page; Class B components refer to A specific page is regarded as a page component.
  • the user interface corresponding to an application window of the application is regarded as a page component
  • a page inserted into the workspace of a collaborative office application is regarded as a page component
  • a page of an applet is regarded as a page component. Treated as a page component.
  • the embodiments of this application do not specifically limit component types and functions implemented by the components. Various components will be exemplified in subsequent embodiments and will not be described again here.
  • the above application window can be an Activity window in the Android system, an application window in the IOS system, or an application window in other operating systems, and is not specifically limited here.
  • An application includes multiple application windows, and one application window can correspond to one user interface (ie, one page).
  • Activity in the Android system is the interface for interaction between users and applications.
  • Each Activity component is associated with a Window object, which is used to describe a specific application window (the application window can be referred to as the Activity window).
  • Activity is a highly abstract user interface component. In Android, it represents the user interface and the corresponding business logic centered on the user interface. The controls in the user interface can monitor and process events triggered by the user. It can be understood that in an Android application, an Activity can be represented as a user interface, and an Android application can have multiple Activities.
  • the designated page of Application 1 can be used as a page component for component management (such as component positioning).
  • the above designated page can be set by default by the terminal device 100, can be set by Application 1 by default, or can be the user's set, there is no specific limitation here.
  • the components may include Class C components and Class D components.
  • the user can call at least one component (for example, a C-type component or a D-type component) in the application 1, and the application 1 includes a calling entry point for each component in the above-mentioned at least one component.
  • the C-type component can be a component provided by this application (ie, application 1).
  • Class D components (for example, component 1) may be components provided by other applications (for example, application 2).
  • Component 1 may include a shortcut entry for application 1 to call application 2 or a specific application window of application 2.
  • application 2 With component 1 displayed in application 1, application 2 can be called and a user interface corresponding to the specific application window associated with the display content of component 1 displayed in application 2.
  • the user interface corresponding to a specific application window of application 2 can be displayed in application 1, and the display content of the user interface is associated with the display content of component 1; in this way, there is no need to open application 2, Avoid jumping between applications.
  • the application that provides components may include Word application, Excel application, PPT (Powerpoint) application, database, instant messaging application, video application, music application, web application, quick application, etc. , may also include Microsoft Loop, OneNote, Outlook, Teams and other office software that can enable multi-person collaboration, which is not specifically limited in the embodiment of this application.
  • a Class C component can also be a Class A component or a Class B component
  • a Class D component can also be a Class A component or a Class B component.
  • embodiments of the present application can manage the circle of friends page as a Class B component (i.e., a page component) and a Class C component.
  • Figures 3A to 3D show the user's display in the instant messaging application.
  • User interface diagram of the Moments page component provided by this application.
  • the icon 202A of the instant messaging application can receive a user's input operation (such as a touch operation).
  • the terminal device 100 displays the homepage 12 of the instant messaging application.
  • the homepage 12 includes one or more chat entries, such as a chat entry 301 for a designated group chat (eg, group chat 1), a chat entry 302 for a file transfer assistant, and a chat entry 303 for a designated contact (eg, Henry); the chat entry 301 includes a group chat entry 301.
  • Chat 1 s avatar 301A and group chat 1
  • the group name 301B the chat entry 302 includes the icon 302A of the file transfer assistant and the name 302B of the file transfer assistant
  • the chat entry 303 includes the contact's avatar 303A and the contact's nickname 303B.
  • the home page 12 also includes page options, such as home page options, address book page options, discovery page options 304 and local page options.
  • the discovery page option 304 may receive a user's input operation (eg, a touch operation), and in response to the above input operation, the terminal device 100 displays the discovery page 13 .
  • the discovery page 13 includes a circle of friends entry 305, which includes a circle of friends icon 305A and a circle of friends name 305B.
  • the friend circle entry 305 may receive a user's input operation (eg, touch operation). In response to the above input operation (eg, touch operation), the terminal device 100 displays the friend circle page 14 .
  • the circle of friends entry 305 can be regarded as the calling entrance of the circle of friends page 14 .
  • the home page 12, the discovery page 13, and the circle of friends page 14 are pages corresponding to different application windows (eg, Activity windows).
  • the instant messaging application can call components provided by this application.
  • FIG. 4A to FIG. 4G show a user interface diagram of a user calling the voting component provided by this application in an instant messaging application.
  • the chat entry 301 may receive a user's input operation (eg, a touch operation).
  • the terminal device 100 displays the chat page 15 of the group chat 1 .
  • the chat page 15 displays the real-time chat records of group chat 1; due to the screen size of the terminal device 100, when the terminal device 100 cannot display all the chat records of group chat 1, the user can view the group chat by sliding up/down. More chat history for 1.
  • the chat page 15 also includes an insert control 306; the insert control 306 can receive the user's input operation (such as a touch operation).
  • the terminal device 100 displays the insert option display area 307.
  • the option display area 307 includes icons for a plurality of insertion options of the chat page (eg, photo options, shooting options, video call options, location options, etc.).
  • the insertion option display area 307 can receive the user's sliding operation.
  • the terminal device 100 can display more icons of the insertion options, such as the voting icon 307A of the voting option, the voting icon 307A of the music option.
  • the voting icon 307A may receive a user's input operation (such as a touch operation).
  • the terminal device 100 may display the above-mentioned voting component 308 inserted by the user in the chat history of the chat page 15 .
  • the voting component 308 includes a voting title 308A, at least two voting options (for example, voting option 308B), a voting control corresponding to each voting option (such as a voting control 308C corresponding to voting option 308B), and Add control 308D.
  • Add control 308D is used to add voting options and voting controls corresponding to the voting options.
  • all group members in group chat 1 can edit the voting title and voting options; the terminal device 100 can display the nickname of the group member being edited/or recently edited.
  • group member "Henry” is editing voting option 308B
  • the group member who recently edited voting title 308A is "Leo”.
  • voting control 308C corresponding to voting option 308B can display the number of votes obtained by this voting option.
  • voting components shown in FIGS. 4E to 4G are exemplary voting components provided by the embodiments of the present application and should not limit the embodiments of the present application.
  • the voting component can also be provided by other applications.
  • the instant messaging application can call components provided by other applications (for example, music applications).
  • music applications for example, music applications.
  • FIG. 5A to FIG. 5F show a user interface diagram in which a user calls the music playing component provided by a music application in an instant messaging application.
  • the music option 307B may receive a user's input operation (eg, a touch operation).
  • the terminal device 100 displays a music search area 309 that includes a search input box 309A.
  • the user can enter song keywords in the search input box 309A.
  • the song keywords can include song titles, lyrics and/or singers, such as the song title "AAA"; the terminal device 100 can obtain information related to the above song keywords.
  • At least one song search result for example, song 309B
  • the song 309B and the sending control 309C corresponding to the song are displayed in the music search area 309.
  • the sending control 309C can receive the user's input operation (such as a touch operation).
  • the terminal device 100 can display the corresponding song 309B inserted by the user in the chat record of the chat page 15 music playing component 310.
  • the music playing component 310 includes a playing control 310A, and in response to an input operation for the playing control 310A, the terminal device 100 can play the song 309B.
  • the music playing component 310 can receive a user's input operation (such as a touch operation).
  • the terminal device 100 can display the simple playing interface 16 of the song 309B in the instant messaging application.
  • the simple play interface 16 includes a source control 311, and the display content of the source control 311 may be "from music application". It can be understood that the simple playback interface 16 can be a user interface provided by a music application; when it is detected that the user clicks on the music playback component 310, there is no need to jump to the music application, and the terminal device 100 can directly display the user provided by the music application in the instant messaging application. interface.
  • the simple playback interface 16 may also be a user interface provided by an instant messaging application.
  • the instant messaging application may display the simple playback interface 16 based on the relevant data of the song "AAA" provided by the application server of the music application. It should be understood that after the user clicks on a component, the terminal device 100 can display the first content page corresponding to the component in this application. For example, after the user clicks on the music playing component 310, the terminal device 100 displays the first content page of the music playing component 310, that is, the example simple playing interface 16.
  • the source control 311 can receive the user's input operation (such as a touch operation). In response to the above input operation, the terminal device 100 can open the music application and display the original playback interface 17 of the song 309B in the music application. . It can be understood that the source control 311 can be regarded as a shortcut entry for the instant messaging application to call the original playback interface 17 of the music application.
  • the original playback interface 17 includes more controls 312, which are used to call up more functional controls, for example, controls for adding song 309B to the playlist, controls for viewing the album of song 309B, controls for viewing songs 309B music score controls, etc. It should be understood that upon receiving an input instruction on the first content page (for example, the simple playback interface 16), the terminal device 100 can then call other applications to display the second content page (for example, the original playback interface 17) corresponding to the component.
  • the user can only control the playback and pause of the song 309B; compared to the music playback component 310, through the simple playback interface 16 displayed in the instant messaging application, the user can also control the song 309B’s playback progress, sharing, likes and comments; compared with the simple playback interface 16, through the original playback interface 17 displayed in the music application, users can obtain more information about song 309B and experience more related to song 309B Functions such as downloading, viewing albums, viewing music scores, etc.
  • the source control 311 receives the user's input operation, and sends the information of the song 309B (such as the song name AAA and the singer name xx) to the music application through the instant messaging application; the music application is based on the information of the song 309B. , generate and display the original playback interface 17 of song 309B.
  • the information of the song 309B such as the song name AAA and the singer name xx
  • music playing component 310 is not limited to music applications.
  • the music playing component 310 may also be provided by this application (i.e., instant messaging application), which is not specifically limited here.
  • the instant messaging application can also use the group solitaire component provided by this application, the location component provided by the map application, the live broadcast component provided by the live broadcast application, etc., which are not specifically limited here.
  • a collaborative office application can call components provided by other applications.
  • Figure 6A to Figure 6B show the user calling the Excel application provided by the collaborative office application.
  • the collaborative office application involved in the embodiments of this application may include three elements in some specific implementations: workspace (workspace), page (page) and component (component).
  • Workspace is a project-oriented workspace with multi-person collaboration capabilities.
  • Page can be understood as a page in the workspace (specific work interface), which can be used to insert (or embed) components and elements (such as links, text, pictures, small programs (such as voting), etc.); a workspace can include multiple page.
  • Collaborative office applications integrate the functions of multiple applications into one application in the form of components. Users can use the above specified functions in the form of components in collaborative office applications without opening the application that provides specified functions; different users can use the same page on the same page. Collaborate in real time.
  • the icon 202B of the collaborative office application shown in FIG. 2A may receive a user's input operation (such as a touch operation).
  • the terminal device 100 may display the user interface 18 of the collaborative office application shown in FIG. 6A .
  • the user interface 18 of the collaborative office application includes a navigation area and a workspace display area.
  • the navigation area includes project names of one or more projects (for example, project name 401, that is, “XX3”).
  • the terminal device 100 in response to the input operation 1 (such as a touch operation) for the project name 401 , the terminal device 100 can expand and display the page navigation of the project corresponding to the project name 401 in the navigation area, that is, the page navigation inserted in the project.
  • the page identifier of each page (such as ZZ1 page, ZZ1 page, and ZZ3 page), and the component identifier of the component inserted in the page.
  • the terminal device 100 displays the page identifier 402 of the page in the navigation area.
  • the page identifier 402 may include the page icon 402A and/or the page name 402B (for example, ZZ1); the terminal device 100 also displays the page in the navigation area.
  • the component identification 404 of the Excel component 403 inserted in this page.
  • the component identification 404 may include the component icon 404A and/or the component name 404B of the component.
  • the component name may be the name of the Excel sheet 1 displayed in the Excel component 403, that is, "Project" Schedule".
  • the ZZ1 page, ZZ1 page and ZZ3 page shown in Figure 6A are all pages inserted in the workspace of project XX3 in the collaborative office application. Users can insert new pages into the workspace of the XX3 project, or delete existing pages.
  • a specified page (such as the ZZ3 page) in the collaborative office application can also be used as a page component for component management.
  • the terminal device 100 in response to the input operation 1 for the project name 401, can also display the page content of the ZZ1 page in the workspace display area (for example, the project schedule displayed through the Excel component 403), and the user can move up to /Swipe down to view more content on the ZZ1 page.
  • the workspace display area for example, the project schedule displayed through the Excel component 403
  • the Excel component 403 when it is detected that the Excel component 403 receives the user's input operation 2 (such as a double-click operation), the Excel component can enter the editing state.
  • the user In the editing state, the user can edit the display content of the Excel table 1 displayed by the Excel component 403.
  • different users can edit the display content of the Excel component 403 at the same time; for a cell in the Excel table 1 displayed by the Excel component 403, the terminal device 100 can display the user who is editing the cell in the cell.
  • the user identification of the user (such as the user nickname "Henry” shown in Figure 6B), or the user identification of the user who recently edited the cell (such as the user nickname "Lily” shown in Figure 6B) can also be displayed in this cell. In this way, the user of the terminal device 100 can see in real time which contents of the Excel component 403 are being edited/or have been edited by other users.
  • the terminal device 100 calls the Excel application and displays Excel through the user interface 19 of the Excel application. Table 1.
  • the original file of Excel table 1 displayed in the Excel component 403 is an Excel table stored locally or online, and the Excel component 403 is associated with the storage path of the table (such as a local storage path or an online storage path).
  • URL uniform resource locator, Uniform Resource Locator
  • Detected input for Excel component 403 When entering operation 3, the collaborative office application calls the Excel application and sends the above-mentioned storage path to the Excel application; the Excel application obtains the table data of the above-mentioned original file through the above-mentioned storage path, and displays the Excel table 1 in the Excel application based on the table data.
  • the terminal device 100 can update the table data of the original file of the Excel table 1 based on the above-mentioned update data of the Excel table 1 to ensure that the Excel table 1 and the original file are consistent.
  • Data synchronization; the above update method can be a regular update, or it can be updated when the table data in Excel Table 1 changes.
  • the Excel component 403 can obtain the table data of the original file indicated by the storage path to update the display content of the Excel table 1 in the Excel component 403 to ensure that the data of the Excel table 1 and the original file are synchronized; similarly, the above update method It can be updated regularly or when the table data of the original file changes.
  • the collaborative office application calls the Excel application and directly sends the table data of Excel table 1 to the Excel application; the Excel application displays the table data in the Excel application based on the table data.
  • Excel sheet 1 when input operation 3 for Excel component 403 is detected, the collaborative office application calls the Excel application and directly sends the table data of Excel table 1 to the Excel application; the Excel application displays the table data in the Excel application based on the table data. Excel sheet 1.
  • the embodiment of the present application does not specifically limit the input operation 2 used to trigger the Excel component to enter the editing state and the input operation 3 used to trigger the calling application 2 to display the content of the component.
  • the Excel component in collaborative office applications only provides some functions of Excel applications, such as simple editing operations (such as input, delete, copy or paste); it does not provide adjusting font format, inserting formulas, adjusting table styles, etc. Function; when the user edits the Excel table 1 displayed in the Excel component 403, if he needs to experience more functions, he can call the Excel application and display and edit the Excel table 1 through the Excel application.
  • FIG. 6D and FIG. 6E show a user interface diagram of a user calling a Word document provided by a Word application in a collaborative office application.
  • the page identifier 405 of the ZZ2 page can receive the user's input operation.
  • the terminal device 100 displays the page content of the ZZ2 page in the workspace display area, such as the Excel component 406 and the Word component. 407.
  • the Word component 407 when it is detected that the Word component 407 receives the user's input operation 3 (such as a double-click operation), the Word component can enter the editing state. In the editing state, the user can edit the display content of the Word document displayed by the Word component 407.
  • the terminal device 100 calls the Word application and displays the above-mentioned information through the user interface 20 of the Word application.
  • Word document Specifically, for the implementation of calling the Word application and updating the displayed content of the Word component 407, you may refer to the related description of the Excel component 403 mentioned above, which will not be described again here.
  • the Word component in the collaborative office application only provides some functions of the Word application. If you need to experience more functions, you can call the Word application and display and edit the Word documents in the Word component through the Word application.
  • the display interface is switched to the second page of the first application; then, after the user finishes using the first application, he usually switches the display interface of the terminal device 100 to the second page of the first application. Switch the display interface to The first application can be switched to the background to run on the desktop, historical task interface or other application interface.
  • the user After the user finishes using the first application on the terminal device 100, or when the terminal displays the first page including the first component, the user usually switches the display interface of the terminal device 100 to the desktop or the interface of other applications, or the same application.
  • the first application On the second page, the first application can be switched to the background.
  • existing mainstream operating systems such as Windows, Android, and iOS, often use historical task interfaces to display these applications running in the background.
  • the user By clicking on the application logo of the first application in the historical task interface, the user can enter the location where the application was last displayed (or where the user last operated); this location is not necessarily the location where the user wants the first application to be displayed.
  • the user may Want to see a specific component in this first application.
  • the above-mentioned specific component may be the last component used in the application/a component of a specific type, such as the first component of the first page.
  • the terminal device 100 receives at least one input touch operation and can return to the homepage of the instant messaging application, or after receiving at least one touch input, Display the user interface of the second application, and switch the instant messaging application to run in the background.
  • the interface snapshot in the application identifier 205 of the instant messaging application may be a screenshot of the above homepage (the exit interface of the instant messaging application). After the user clicks on the application logo 205, the terminal device 100 will display the homepage of the instant messaging application.
  • the user can enter the homepage of the instant messaging application by clicking the application logo 205 of the instant messaging application in the historical task interface 21 or the icon 202A of the instant messaging application in the main interface 11, and then click the discovery page option in turn. 304 and Moments entry 305. In this way, the operation is cumbersome and the user experience is poor.
  • the embodiment of the present application provides an interface display method.
  • the component label of component 1 is provided in the component management interface (for example, the aforementioned historical task interface).
  • the preset operation 1 acting on the above component label you can quickly locate the position of component 1 in application 1, or display the component in application 1; for example, component 1 is inserted into a long page, in response to the above preset operation 1 , the position of component 1 in the above long page can be directly positioned; for example, component 1 is a page component, and in response to the above preset operation 1, the page corresponding to the component can be directly displayed.
  • application 2 associated with component 1 can be called, and the content of the component can be displayed in application 2. In this way, components can be quickly positioned, tedious user operations can be avoided, and user experience can be effectively improved.
  • the above component management interface can be a historical task interface or other user interfaces, such as a negative screen, a notification bar drop-down interface, etc.
  • the terminal device 100 displays application 1, receives at least one touch gesture input by the user, and opens a negative screen or a notification bar drop-down interface.
  • subsequent embodiments mainly take the historical task interface as an example for explanation, but do not represent a limitation on the above component management interface.
  • component management for example, component positioning
  • component management whitelist may be the terminal device 100
  • the default setting can also be the default setting of each application, or it can be set by the user. There is no specific limitation here. Subsequent embodiments will specifically introduce how users set component management whitelists, which will not be described again here.
  • FIG. 7A is a historical task interface 21 that can realize the component positioning function provided by the embodiment of the present application.
  • the historical task interface 21 also includes extended controls corresponding to the application identifiers of each application, such as extended controls 501 corresponding to the application identifier 204 of the collaborative office application, and extended controls 502 corresponding to the application identifier 205 of the instant messaging application.
  • the historical task interface 21 may not include the extended control corresponding to the application identification of the application.
  • the extended control 501 of the collaborative office application is used as an example for explanation.
  • the extended control 501 can receive user input operations (such as touch operations).
  • the terminal device 100 can display the collaborative office application in the component label display area 503 of the collaborative office application.
  • the component tag of the component where the component is located for example, component tag 601 to component tag 604.
  • the component labels of each component are displayed in a row and four columns.
  • FIG. 7C and FIG. 7D are two other arrangements provided by embodiments of the present application.
  • the component labels of each component are displayed in an arrangement of two rows and two columns; in Figure 7D, the component labels of each component are displayed in an arrangement of four rows and one column.
  • This embodiment of the present application does not specifically limit the shape of the component labels of each component in the component label display area 503.
  • the component labels in FIGS. 7B and 7C are exemplarily shown as squares; the component labels in FIG. 7D are exemplarily shown as rectangles.
  • components are usually displayed as rectangles, and accordingly, the component labels of components also display rectangles.
  • the terminal device 100 is triggered to display the component labels of components called in the application through the extended control corresponding to the application identifier of the application. Can keep the page tidy.
  • the collaborative office application currently includes M components that can perform component positioning, and M is a positive integer.
  • the component label display area 503 displays component labels of a preset number of components at most. When M exceeds the preset number, the user can view component labels of more components by sliding operations on the component label display area 503 .
  • the above-mentioned preset number is 4, and the number of components that can be positioned exceeds 4; as shown in Figure 7E and Figure 7F, when an upward sliding operation on the component label display area 503 is detected, the terminal device 100
  • the display component label display area 503 displays component labels of more components, such as component labels 605 to 606 .
  • the terminal device 100 may stop displaying the component in the component label display area 503. component label. For example, after the user clicks the extended control 501 shown in Figure 7B, the terminal device 100 displays the historical task interface 21 shown in Figure 7A.
  • the component label display area 503 displayed by the terminal device 100 can cover the second row of application identification (ie, the application identification of the instant messaging application).
  • the component label display area 503 displayed by the terminal device 100 can squeeze the second row of application identification (that is, the application identification of the instant messaging application) to other positions (for example, the next one in the multi-task queue). where the app's app ID appears).
  • the historical task interface 21 called up by the terminal device 100 can directly display the information corresponding to each application identification.
  • the component's component label For example, taking the historical task interface 21 shown in FIG. 7J as an example, there is no need to expand the control.
  • the component label display area (such as the component label display area 503) corresponding to the application identifier of any application in the historical task interface 21, you can Directly displays the component labels of the components currently available for component positioning in the application. It should be noted that when an application (such as a contact application) currently does not have a component that can be located, the historical task interface 21 will not display the component label of the component corresponding to the application.
  • the above M components include: all components in the component management whitelist 1 of the collaborative office application.
  • the above-mentioned M components include: components belonging to component management whitelist 1 that were used by the user during the latest running of the collaborative office application.
  • the above-mentioned M components include: components that belong to the component management whitelist 1 that the user has used within a preset period of time 1 (for example, one day).
  • the above-mentioned M components include: within a preset period of time 2 (for example, one month), the M components with the highest frequency of use among the components belonging to the component management whitelist 1 that have been used by the user.
  • the same component such as component 1
  • only the component 1 last used by the user on the page will be positioned.
  • the arrangement order of the above-mentioned M components is determined based on the latest usage time of the above-mentioned M components and/or the usage frequency of the above-mentioned M components. It can be understood that the component that the user intends to view is more likely to be a "recently used component or a component with a high usage rate"; sorting based on the last use time and/or frequency of use makes it easier for the user to quickly find the component that the user intends to view.
  • the arrangement order of the above-mentioned M components is the reverse order of the most recent use time of the above-mentioned M components, that is, the most recently used component among the above-mentioned M components is ranked first.
  • component label 601, component label 602, component label 603, and component label 604 respectively correspond to component 1, component 2, component 3, and component 4, and the most recent usage time of these four components.
  • the order is component 4, component 3, component 2 and component 1.
  • the arrangement order of the above-mentioned M components is the positive order of the frequency of use of the above-mentioned M components, that is, the component with the highest frequency of use is ranked first.
  • component label 601, component label 602, component label 603 and component label 604 respectively correspond to component 1, component 2, component 3 and component 4.
  • the frequency of use of these four components is high or low.
  • the order is component 1, component 2, component 3 and component 4.
  • the first m components among the above-mentioned M components are the most recently used m components among the above-mentioned M components, and the order of arrangement is the reverse order of the most recent use time of the above-mentioned m components; among the above-mentioned M components
  • the order of the last M-m components is the positive order of the usage frequency of the above-mentioned M-m components.
  • m is 4.
  • the embodiment of the present application does not specifically limit the arrangement order of the above M components.
  • the last use time of the component can refer to the last time to respond to the user's valid operation or exit.
  • the time of editing status For type B page components (for example, Moments page 14), the last time the component was used may refer to users who switched the Moments page to other pages (for example, returned to the discovery page 13, exited to the main interface 11, or switched to other applications). interface) time.
  • component 1 takes component 1 as an example to introduce the display content of the component label of the component.
  • the component tag of component 1 may include the component identifier of component 1; it may also include one or more of the following: the page identifier of the page where component 1 is located (if component 1 is a plug-in component), the Application 2 Application ID, workspace ID of the workspace where component 1 is located.
  • the component identifier includes one or more of the following: component name, component snapshot, and component icon corresponding to the component type; the page identifier includes a page icon and/or page name; the application identifier includes an application icon and/or application Name; the workspace identification includes the workspace icon and/or the workspace name.
  • Component identifiers include:
  • the component name of the circle of friends page 14 can be "Friends Circle”
  • the component name of the voting component 308 can be the voting title of the component "Travel Voting”
  • the component name of the music playing component 310 can be this component.
  • the name of the song played is "AAA”
  • the component name of the Excel component 403 can be the file name of the Excel table displayed by the component "Project Schedule”
  • the component name of the Word component 407 can be the file name of the Word document displayed by the component "Achievements” illustrate”.
  • the component name of the component may also be the component type corresponding to the component.
  • the component type of the music playing component 310 is the music playing component
  • the component type of the voting component 308 is the voting component.
  • the embodiments of this application do not specifically limit the component names of various types of components.
  • Component snapshot When the terminal device 100 determines that the user has stopped using a component, it intercepts the last displayed content of the component as a component snapshot of the component, and stores the component snapshot. It can be understood that each time the user uses a component, the terminal device 100 can update the component snapshot of the component. In one implementation, after the terminal device 100 responds to the user's valid operation on component 1 for the last time, if component 1 does not receive another valid operation from the user within the preset time period 3, the terminal device 100 determines that the user stops using component 1.
  • the component label can have multiple shapes. To adapt to the shape of the component label, the terminal device 100 can capture an image of a preset shape in the snapshot of the component as a component snapshot of the component, The above preset shapes are determined based on the shape of the component label.
  • Component icon When a component does not have a specific component icon, the application icon of the application that provides the component can be used as the component icon; the component icon and the application icon can be the same or different.
  • the component icon of the circle of friends page 14 may be the circle of friends icon 305A shown in FIG. 3D
  • the component icon of the voting component 308 may be the voting icon 307A shown in FIG. 4D
  • the component icon of the music playback component 310 may be as shown in FIG.
  • the component icon of the Excel component 403 may be the application icon of the Excel application
  • the component icon of the Word component 407 may be the application icon of the Word application.
  • the embodiments of this application do not specifically limit the component icons of various types of components.
  • Page identifiers include:
  • Page name For example, in an instant messaging application, the page name of the circle of friends page 14 can be "Friends Circle", and the page name of the chat page 15 of group chat 1 can be the name of the group chat (for example, group chat 1), specifying the contact
  • the page name of the person's chat page can be the nickname or remarks of the above-mentioned contact.
  • the page name of the ZZ1 page can be "ZZ1".
  • the page icon of the circle of friends page 14 can be the circle of friends icon 305A shown in Figure 3D
  • the page icon of the chat page 15 of group chat 1 can be the group chat shown in Figure 3B.
  • Avatar 301A the page icon of the chat page of the specified contact can be the avatar of the above contact.
  • the page icon of the ZZ1 page may be the page icon 402A shown in Figure 6B. It can be understood that the component icon and the page icon of the page component (for example, the circle of friends page 14) can be the same.
  • the same component inserted in different pages can be distinguished through the page identifier (such as page name, page icon) in the component tag; when multiple different components are inserted into the same page, the page identifiers corresponding to the above-mentioned different components are the same .
  • Workspace name For example, in a collaborative office application, with the XX3 project, the workspace name of the XX3 project may be the project name 401 shown in Figure 6A, that is, "XX3". The embodiment of this application does not specifically limit the name of the workspace.
  • the same component inserted in different workspaces can be distinguished through the workspace identification (such as workspace name) in the component label; when multiple different components are inserted into the same workspace, the workspaces corresponding to the above-mentioned different components
  • the logo is the same.
  • the component label of the component includes an icon and/or a name.
  • the above icon includes a component icon, a component snapshot, a page icon of the page where the component is located, an application icon of the application that provides the component, or a workspace icon of the workspace where the component is located.
  • At least one of the above names may include at least one of the component name, the page name of the page where it is located, the application name of the application that provides the component, or the workspace name of the workspace where it is located.
  • the user successively edited the Word component 407 of page ZZ2 and the Excel component 403 of page ZZ1 before exiting the collaborative office application;
  • the historical task interface 21 shown in Figure 8 includes the component label 601 of the Excel component 403 and the Word component.
  • the user before exiting the instant messaging application, the user successively used the music playback component 310 in the chat page 15 of the group chat 1 and browsed the circle of friends page 14; the historical task interface 21 shown in Figure 9 includes the content of the circle of friends page 14.
  • Component tag 611 and component tag 612 of the music playing component 310 are examples of the music playing component 310 .
  • the component label of the component includes a component icon and a page name of the page where the component is located.
  • the component label 601 of the Excel component 403 includes the component icon 601A of the Excel component 403 and the page name "ZZ1" of the ZZ1 page where it is located.
  • the component label 601 of the Word component 407 includes the component icon 602A of the Word component 407 and the page name "ZZ2" of the ZZ2 page where it is located.
  • the component icon of the Excel component and the application icon of the Excel application are the same. This is just an example and should not limit the embodiments of this application.
  • the component icon of the Excel component and the application icon of the Excel application may also be different; similarly, , the same is true for the component icon of the Word component.
  • the component label 611 of the circle of friends page 14 includes a component icon 611A and the page name “circle of friends”.
  • the component label 612 of the music playing component 310 includes a component icon 612A and a page name "Group Chat 1".
  • the music player component and the Moments page component have specific component icons.
  • the page where the component is located is the component itself; if the component (such as the Excel component 403) is a component inserted into page 1, then the page where the component is located is Page 1.
  • the component tag of a component includes a snapshot of the component and the page name of the page where the component is located.
  • the user before exiting the collaborative office application, the user also inserted the Excel component 403 into the ZZ3 page and edited the Excel component 403 of the ZZ3 page.
  • the historical task interface 21 shown in Figure 8 also includes the component label 603 of the Excel component 403 of the ZZ3 page. .
  • the component snapshot 601B in the component label 601 of the Excel component 403 of the ZZ1 page is the same as the component snapshot 603B in the component label 603 of the Excel component 403 of the ZZ3 page.
  • the component label 601 includes the page name "ZZ1"
  • the component label 603 includes the page name "ZZ3”. It can be understood that the same Excel component on different pages can be kept synchronized and the component snapshots are the same; users can distinguish the same Excel component used in different pages through the page name, and the page name allows users to quickly locate the specific component in the target page.
  • the component label of a component includes a component icon and a workspace name of the workspace where the component is located.
  • the component label of the component includes a component icon and a component name.
  • the user also edited the Excel component 406 of the ZZ2 page before exiting the collaborative office application.
  • the historical task interface 21 shown in FIG. 8 also includes the component label 604 of the Excel component 406.
  • the component icons in the component label 601 of the Excel component 403 and the component label 604 of the Excel component 406 are the same.
  • the component label 601 includes the component name "Project Schedule”
  • the component label 604 includes the component name "Project Results”. surface”. It can be understood that components of the same type have the same component icon, and two same types can be distinguished through the component name. s component.
  • the component label 611 of the circle of friends page 14 includes the component name “circle of friends”.
  • the component label 612 of the music playing component 310 includes the component name "AAA" (ie, the song name).
  • the component tag of the component includes a component snapshot and a component name.
  • the component label of a component includes a page icon and component name of the page where the component is located.
  • the component label 601 of the Excel component 403 of the ZZ1 page and the component label 603 of the Excel component 403 of the ZZ3 page include the same component name "Project Schedule", and the component label 601 includes the page icon 601C of the ZZ1 page. , the component label 603 includes the page icon 603C of the ZZ3 page. It is understandable that the same Excel component on different pages has the same component name; users can distinguish the same Excel component used in different pages through page icons, and page icons also facilitate users to quickly locate specific components in the target page.
  • the component label 611 of the circle of friends page 14 includes the page icon 611B of the circle of friends page; the component label 612 of the music playing component 310 includes the page icon 612B of the chat page 15 .
  • the component tag of a component includes an application icon and component name of the application that provides the component.
  • the component label 601 of the Excel component 403 includes an application icon 601D of the Excel application
  • the component label 602 of the Word component 407 includes an application icon 602D of the Word application.
  • the component label 611 of the circle of friends page 14 includes an application icon 611C of the instant messaging application.
  • the component label 612 of the music playing component 310 includes an application icon 612C of the music application.
  • the location of component 1 in application 1 can be quickly located, or the component can be displayed in application 1 .
  • application 2 associated with component 1 in application 1 can be called, and a user interface associated with the content of the component is displayed in application 2 (for example, The second content page in the related description of Figure 5F); or, through the preset operation 2 acting on the above component tag, the user interface of component 1 can be opened in application 1 (for example, the first content page in the related description of Figure 5E ), the display content of the user interface is associated with the content of component 1. In this way, when exiting the above user interface, you can directly return to application 1 without opening application 2, thus avoiding jumps between applications.
  • component 1 is a component provided by this application, that is, component 1 has no associated application 2, then the terminal device 100 may not respond to the preset operation 2 of the component tag of component 1.
  • preset operation 1 is a left-swipe operation acting on the component label of component 1
  • preset operation 2 is a right-swipe operation acting on the component label of component 1.
  • Excel component 403 is used to display the "Project Schedule”.
  • the component label 601 can receive a left swipe operation.
  • the terminal device 100 locates the location of the Excel component 403 in the ZZ1 page of the collaborative Bao Gong application, and displays the collaboration shown in Figure 10B.
  • the user interface 18 shown in FIG. 10B includes the ZZ1 page, and the ZZ1 page includes the Excel component 403 .
  • the component label 601 can receive a right swipe operation.
  • the terminal device 100 calls the Excel application to open the Excel table displayed by the Excel component 403, and displays the user of the Excel application shown in Figure 10D.
  • Interface 19 the user interface 19 is used to display the "project schedule”.
  • the application identification of application 1 and the application identification of application 2 are displayed; the preset operation 1 includes going from the component label of component 1 to the application of application 1 The sliding operation of the logo; the default operation 2 includes the sliding operation from the component label of component 1 to the application logo of application 2. For example, take the component label 601 of the Excel component 403 shown in FIG. 10E as an example.
  • the component label 601 can receive the user's touch operation.
  • the terminal device 100 displays the application identification 621 of the collaborative office application and the application identification 622 of the Excel application.
  • the component label 601 can receive the user's sliding operation from the component label 601 to the application identification 621 .
  • the terminal device 100 locates the location of the Excel component 403 and displays the collaboration shown in FIG. 10B User interface for office applications18.
  • the component label 601 can receive the user's sliding operation from the component label 601 to the application identification 622 .
  • the terminal device 100 calls the Excel application to display the user of the Excel application shown in FIG. 10D Interface 19.
  • the application identification of application 1 and the application identification of application 2 are displayed;
  • the preset operation 1 includes long pressing the component label of component 1 and then the component is The sliding operation of dragging the label to the application logo of Application 1;
  • the default operation 2 includes the sliding operation of long pressing the component label of Component 1 and then dragging the component label to the application logo of Application 1.
  • dragging the component label means that the component label moves following the sliding trajectory of the sliding operation of the user's finger.
  • the terminal device 100 when detecting the above long press operation on the component label of Component 1, can also display other applications that can use Component 1 (for example, Application 3 ) application identifier.
  • Application 3 a preset operation acting on the application identification of application 3 is detected (for example, a sliding operation of dragging the component label to the application identification of application 3), component 1 is shared to application 3.
  • the historical task interface also includes a source positioning control and a page positioning control; preset operation 1 includes a sliding operation from the component label of component 1 to the page positioning control; preset operation 2 includes a sliding operation from the component label of component 1 to The sliding operation of the source positioning control.
  • preset operation 1 includes a sliding operation from the component label of component 1 to the page positioning control; preset operation 2 includes a sliding operation from the component label of component 1 to The sliding operation of the source positioning control.
  • preset operation 1 includes a sliding operation from the component label of component 1 to the page positioning control
  • preset operation 2 includes a sliding operation from the component label of component 1 to The sliding operation of the source positioning control.
  • the historical task interface also includes a page positioning control 631 and a source positioning control 632.
  • the component label 601 can receive the user's sliding operation from the component label 601 to the page positioning control 631.
  • the terminal device 100 locates the position of the Excel component 403 and displays the collaborative office application shown in Figure 10B.
  • User interface 18 As shown in Figure 10I, the component label 601 can receive the user's sliding operation from the component label 601 to the source positioning control 632.
  • the terminal device 100 calls the Excel application and displays the user interface 19 of the Excel application shown in Figure 10D. .
  • the terminal device 100 does not respond to the preset operation 2 of the source positioning control.
  • the terminal device 100 may display the source positioning control in grayscale to indicate that the source positioning control is unavailable. For example, take the component label 611 of the friend circle page 14 shown in FIG. 11A as an example.
  • the terminal device 100 can display the source positioning control 632 in grayscale to indicate that the source positioning control 632 is unavailable, that is, the circle of friends page 14 is not available.
  • the component label 611 can receive the user's sliding operation from the component label 611 to the source positioning control 632.
  • the terminal device 100 locates the position of the circle of friends page 14, in the instant messaging application. Display the circle of friends page 14.
  • preset operation 1 includes long-pressing the component label of component 1 and then dragging the component label to the sliding operation of the page positioning control; preset operation 2 includes long-pressing the component label of component 1 and then dragging the component label to the application.
  • Source of 1 The sliding operation of positioning controls.
  • preset operation 1 includes a click operation acting on the component label of component 1; preset operation 2 includes a long press operation acting on the component label of component 1.
  • preset operation 1 includes a click operation on the component label of component 1; preset operation 2 includes a sliding operation including long pressing the component label of component 1 and then dragging the component label to a preset area.
  • preset area displays the application identification and/or prompt information of Application 2.
  • the prompt information is used to prompt the user to drag the component label of Component 1 to the preset area, which can trigger Application 2 to open Component 1.
  • the terminal device 100 displays the application identification and/or prompt information of Application 2 in the preset area.
  • a long press operation on the component label 612 is detected.
  • the terminal device 100 displays prompt information 641A and music in the preset area 641 (for example, the center area of the display screen).
  • Application identification 641B As shown in Figure 11G and Figure 11H, the sliding operation of dragging the component label 601 to the preset area 641 is detected.
  • the terminal device 100 calls the music application and displays the original playing interface of the song played by the music playing component 310. 17.
  • the preset operation 1 and the preset operation 2 illustrated in FIGS. 10A to 11F can also be other operations, which are not specifically limited here.
  • the following is an exemplary description of how the terminal device 100 locates the position of the component.
  • the user uses component 1 of application 1, and the page where component 1 is located is page 1.
  • the terminal device 100 adds the application window corresponding to page 1 to the task queue 1 located by the component.
  • the task queue The task information of page 1 in 1 includes the page ID and page data of page 1, the component ID of component 1 and the display position of component 1 in page 1.
  • the terminal device 100 detects the preset operation 1 acting on the component tag of component 1, it obtains the task information of page 1 in task queue 1 based on the page identifier of page 1 where component 1 is located; based on the page in the task information of page 1 Data, component identification and display location of component 1, run page 1, display page 1 including component 1.
  • component 1 such as Excel component of application 1 (such as collaborative office application)
  • application 1 such as collaborative office application
  • page 1 such as ZZ1 page
  • component 1 such as the circle of friends page
  • component 1 such as an instant messaging application
  • a task queue for component positioning can be established for each application, or a total task queue for component positioning can be established for all applications, which is not specifically limited here.
  • the terminal device 100 can only display part of the content of the page, and the user needs to slide up, down, left or right to view it.
  • the entire content of the page; in the embodiment of this application, such pages that cannot be fully displayed are referred to as long pages, and pages that can be fully displayed are called non-long pages.
  • the ZZ1 page 18 shown in Figure 10B, the circle of friends page 14 shown in Figure 11D, and the chat page 15 shown in Figure 4G and Figure 5D are all long pages.
  • the task information of page 1 may not include the display position of component 1 in page 1; the terminal device 100 detects the preset operation 1 that acts on the component label of component 1 At this time, based on the page ID of page 1 where component 1 is located, the task information of page 1 in task queue 1 is obtained; based on the page data of page 1, run page 1 to display the complete page 1, which includes component 1.
  • page 1 is a long page that can be slid up and down
  • component 1 such as the Excel component
  • component 1 is a type A plug-in component.
  • the total height that can be displayed on page 1 is H, and the height of page 1 that can be displayed on the display screen of the terminal device 100 is The degree is h, h is less than H; when the user exits component 1, the display position of component 1 in page 1 on the display screen is x to x+s, s is the display height of component 1, and the task information of page 1 in task queue 1 is still
  • the display position of record component 1 is x.
  • the terminal device 100 When the terminal device 100 detects the preset operation 1 that acts on the component label of component 1, it can display part of the page containing component 1 in page 1 based on the page data of page 1 and the display height x of component 1.
  • Component 1 can be located at a designated position on the above-mentioned partial page, such as the top, middle or bottom, which is not specifically limited here.
  • the content of page 1 includes the first part and the second part, and the content displayed in the first part does not include component 1; the user can slide page 1 so that the display screen displays the second part of page 1 that contains component 1; when the user exits component 1 , the display shows the first part of page 1 that does not contain component 1.
  • the terminal device 100 detects the preset operation 1 acting on the component label of component 1, the first part of page 1 containing component 1 can be displayed.
  • component 1 (for example, the circle of friends page) is a type B page component.
  • the total height that can be displayed on page 1 is H
  • the height of page 1 that can be displayed on the display screen of the terminal device 100 is h
  • h is less than H
  • the terminal device 100 detects the preset operation 1 acting on the component label of component 1, it may display the above-mentioned partial page of page 1 based on the page data of page 1 and the display height y of component 1.
  • component label of component 1 can also implement other functions.
  • the following is an exemplary introduction to other functions that component 1 can provide.
  • the component snapshot of component 1 can be previewed through the component label of component 1 .
  • the component label 601 of the Excel component 403 in the historical task interface 21 can receive the user's input operation (such as a double-click operation).
  • the terminal device 100 can perform the historical task in the historical task interface 21 .
  • An enlarged version of the component snapshot of the Excel component 403 is displayed on the interface 21 .
  • component 1 can be removed from the component management whitelist during the current run of application 1 through the component label of component 1, and/or component 1 can be completely removed from the component management whitelist.
  • the component label 611 of the friend circle page 14 in the historical task interface 21 can receive the user's input operation (such as a slide-up operation).
  • the terminal device 100 can During this run of the instant messaging application, the Moments page will be removed from the component management whitelist, the component label 611 will stop displaying, and the component labels of the components ranked after Moments page 14 will be moved one position forward.
  • the display position of component label 612 moves to the original display position of component label 611 ; the display position of component label 613 moves to the original display position of component label 612 .
  • component 1 can be shared through the component tag of component 1 to other applications (such as application 3) that can use component 1, or to contacts in this application.
  • the component label 601 of the Excel component 403 in the historical task interface 21 can receive the user's sharing operation (such as a sliding operation).
  • the terminal device 100 can display the application.
  • the user ID of a contact for example, a colleague who can work together
  • a collaborative office application for example, the user ID of the contact Lily 651
  • the application ID of other applications of component 1 for example, the application ID of an instant messaging application 652
  • you can use the page identifier of the specified page of other applications of component 1 for example, the page identifier 653 of the friend circle page of the instant messaging application.
  • the user identification 651 can receive the user's input operation (such as a touch operation).
  • the terminal device 100 can send component 1 to the terminal device of the contact Lily, and the terminal device of the contact Lily can be displayed in the collaborative office application.
  • Component 1 Component 1.
  • FIGS. 12F to 12I show user interface diagrams of the sharing component 1 through the application identifier 652 of the instant messaging application.
  • the application identifier 652 may receive a user's input operation (such as a touch operation).
  • the terminal device 100 may display the contact selection interface 22 of the instant messaging application.
  • the contact selection interface 22 includes user identifications of multiple contacts in the instant messaging application, such as the user identification 654 of the contact "Anna".
  • the terminal device 100 may display the sharing box 655 of the Excel component 403 of the contact "Anna", the sharing box 655 including the Excel component 403 Component label 655A (such as the component snapshot shown in Figure 12G), and share control 655B.
  • the terminal device 100 in response to an input operation (such as a touch operation) on the sharing control 655B, shares component 1 to the contact "Anna” of the instant messaging application, and displays the user "Anna” in the instant messaging application.
  • Anna"'s chat page 23 displays the Excel component 403 sent by the user of this device on the chat page 23.
  • Figures 12F to 12I show user interface diagrams of the sharing component 1 through the page identification 653 of the circle of friends.
  • the terminal device 100 may display the editing interface 24 of the circle of friends.
  • the editing interface 24 includes the identification of the attachment of the circle of friends (ie, the component identification of the Excel component 403 656), and the publishing control of the circle of friends 657.
  • the terminal device 100 in response to an input operation (for example, a touch operation) on the publishing control 657 , displays the latest published circle of friends on the circle of friends page 14 , and the circle of friends includes the Excel component 403 .
  • the following is an exemplary description of how users set up a component management whitelist.
  • FIG. 13A to FIG. 13D show relevant user interface diagrams for managing the whitelist through the system setting management component.
  • the setting icon 202C shown in FIG. 2A can receive a user's input operation (such as a touch operation).
  • the terminal device 100 can display the system setting interface 31 shown in FIG. 13A .
  • the system setting interface 31 includes component management setting items. 701.
  • the terminal device 100 may display the component management setting interface 32 including a switch control 702 of component management and an application. Management entry 703.
  • the switch control 702 When the switch control 702 is in the ON state, the service of component management (such as component positioning) is enabled; when the switch control 702 is in the OFF state, the service of component management is turned off.
  • the user can switch the state of the switch control 702 through an input operation (such as a touch operation).
  • the terminal device 100 in response to an input operation (such as a touch operation) for the application management entry 703 , the terminal device 100 displays a user interface 33 that includes a setting entry of at least one application that can provide components, such as instant Communication application settings entry 704.
  • the terminal device 100 displays the component setting interface 34 of the instant messaging application.
  • the component setting interface 34 includes at least one page provided by the instant messaging application.
  • the switch control of the component such as the switch control 705 of the friend circle page
  • the switch control of at least one plug-in component such as the switch control 706 of the voting component.
  • Figures 13A to 13D are exemplary setting methods provided by the embodiment of the present application.
  • a setting entry for the component management whitelist can also be added to each application, which is not specifically limited here. It can be understood that by setting the component management whitelist by the user, a personalized component positioning experience can be provided based on the needs of each user.
  • the display mode of the component management interface shown in Figure 7A to Figure 12D (that is, the application using the component is displayed on the component management interface) (application identifier used), the component management is based on the application that uses the component as the dimension; it is not limited to the above display method (or display dimension), the embodiment of the present application can also perform component management in other display methods (or display dimensions).
  • Method 1 Display the application ID of the application that uses the component.
  • FIGS. 7A to 9 take the component management interface as the historical task interface 21 as an example.
  • the components currently capable of component positioning in the terminal device 100 are managed, and each application (for example, The component tags of components used by collaborative office applications are introduced in detail.
  • the historical task interface 21 may include the application identifier of the collaborative office application, and the component label display area corresponding to the application identifier includes the component labels of the components used in the collaborative office application that can currently perform component positioning.
  • the application identifier includes App icon, app name, and interface snapshot.
  • FIG. 14A shows another component management interface 41 with the application using the component as the dimension.
  • the application identification of each application in the component management interface 41 may not include the interface of the application. Snapshot.
  • the component management interface 41 shown in Figure 14A includes extended controls corresponding to the application identifiers of each application.
  • the component management interface 41 may not include extended controls.
  • the preset operation 3 (such as a touch operation) acting on the application identifier of the application can be used to call up the current component positioning parameters used in the application.
  • the component's component label can be used to call up the current component positioning parameters used in the application.
  • Figure 14B shows another component management interface 41.
  • the component management interface 41 can directly display the component labels of the components used by each application in the component label display area corresponding to the application identification of the application. No need to expand controls.
  • the component management interface 41 shown in FIGS. 14A and 14B does not include the application identification of the contact application.
  • the application shown in FIGS. 14A and 14B currently includes at least one component that can perform component location.
  • Method 2 Display the application ID of the application that uses the component and the page ID of the page where the component is located.
  • Method 2 is based on Method 1, and the M components currently available for component positioning used by Application 1 (such as collaborative office applications) are divided again based on the page where they are located.
  • the M components are located in the W components of Application 1.
  • W is a positive integer.
  • the terminal device 100 in response to an input operation (such as a touch operation) of the extended control 502 for the collaborative office application, displays the page identifiers of the above W pages in the component label display area of the collaborative office application ( For example, page icon and/or page name), such as the page identifier of the ZZ1 page, the page identifier 801 of the ZZ2 page, and the page identifier of the ZZ3 page.
  • the page identifier 801 can receive the user's input operation (such as a touch operation).
  • the terminal device 100 displays the components used in the ZZ2 page in the component label display area of the collaborative office application.
  • a component label for example, a component label 802 of the Excel component 406.
  • the component label 802 includes a component identification (such as a component icon, a component snapshot, and/or a component name) of the Excel component 406.
  • the arrangement order of the above-mentioned W pages may be based on the latest usage time of the components used in the above-mentioned W pages, the frequency of use of the components used in the above-mentioned W pages, and the exit time of the above-mentioned W pages. one or more certain ones.
  • the most recent usage time of the components in each page is determined.
  • the arrangement order of the above-mentioned W pages is the reverse order of the most recent use time of the components in the above-mentioned W pages, that is, the most recently used time of the components in the above-mentioned W pages.
  • the page ranks first. In one implementation, the highest frequency of use of components used by each page is determined.
  • the order of the above W pages is the positive order of the highest frequency of use corresponding to the above W pages, that is, the page with the highest frequency of use of the component is ranked The first one.
  • the arrangement order of the above W pages is the order of the above W pages.
  • the reverse order of exit time, that is, the most recently exited page among the above W pages is ranked first.
  • the aforementioned preset operation 1 of component positioning may be a sliding operation from the page identifier 801 of the Excel component 406 to the component label 802; such as As shown in FIG. 15D , the aforementioned preset operation 2 for component positioning may be a click operation acting on the component label 802 .
  • the component management interface may not include extended controls, and the page identifiers of the above W pages may be called out through the preset operation 3 acting on the application identifier of the collaborative office application.
  • the component label of the component can be used to replace the page identifier of the page; there is no need for the user to click on the page identifier to obtain the corresponding information of the page.
  • Component labels for unique components saving user operations.
  • the component management interface may not include extended controls, and the component management interface may directly display the page identifiers of the above W pages.
  • the component label display area displays at most a preset number (for example, 4) of page identifiers. When N exceeds the preset number, the user can view more page identifiers by swiping left or right. Similarly, the same is true for component labels. For details, please refer to the relevant descriptions in Figure 7E and Figure 7F , which will not be described again here.
  • component labels in method two can be referred to the functions of component labels in method one, and will not be described again here.
  • Method 3 Display the application ID of the application that uses the component, and the application ID of the application that provides the component.
  • Method 3 is based on Method 1, and the M components that can be used for component positioning used by Application 1 (such as collaborative office applications) are divided again based on the application providing the components.
  • the M components are provided by F applications.
  • F is a positive integer.
  • the terminal device 100 in response to an input operation (such as a touch operation) of the extended control 502 for the collaborative office application, displays the application identifiers of the above F applications in the component label display area of the collaborative office application ( For example, application icon and/or application name), such as the application identification 803 of the Excel application, the application identification of the Word application, and the application identification of the instant messaging application.
  • the application identification 803 can receive a user's input operation (such as a touch operation).
  • the terminal device 100 displays components provided by the Excel application that can be positioned in the component label display area. Component tag, for example, component tag 804 of Excel component 403.
  • the arrangement order of the above-mentioned F applications may be based on the latest usage time of the components provided by the above-mentioned F applications, the usage frequency of the components provided by the above-mentioned F applications, and the exit time of the above-mentioned F applications.
  • One or more definite ones the most recent usage time of the components provided by each application is determined.
  • the ranking order of the above-mentioned F applications is the reverse order of the most recent usage time of the components provided by the above-mentioned F applications, that is, the ranking of applications that provide the most recently used components. In the first place.
  • the highest usage frequency corresponding to each application is determined to be the highest usage frequency of the components provided by the application.
  • the arrangement order of the above-mentioned F applications is the positive order of the highest usage frequencies corresponding to the above-mentioned F applications, that is, providing The applications of the most frequently used components are ranked first.
  • the order of the above-mentioned F applications is the reverse order of the exit time of the above-mentioned F applications, that is, the most recently exited application among the above-mentioned F applications is ranked first.
  • the component management interface may not include extended controls.
  • the application identifiers of the above F applications can be called up in the component label display area of the collaborative office application.
  • the component label of the component can be used instead of the application identification of the application; there is no need for the user to click on the application identification to obtain the corresponding page.
  • the component label of the only component saving user operations.
  • the component management interface may not include extended controls, and the component management interface may directly display the page identifiers of the above F applications.
  • the component label display area displays at most a preset number (for example, 4) of application identifiers. When F exceeds the preset number, the user can view more application identifiers by swiping left or right. Similarly, the same is true for component labels. For details, please refer to the relevant descriptions in Figure 7E and Figure 7F , which will not be described again here.
  • component labels in method three can also be referred to the functions of component labels in method one, which will not be described again here.
  • Method 4 Display the application ID of the application that provides the component.
  • component management is performed on the components currently capable of component positioning in the terminal device 100 by taking the application that provides the component as a dimension.
  • the components currently capable of component positioning in the terminal device 100 are provided by K applications.
  • FIG. 17A shows a component management interface 41 with the application providing the component as the dimension.
  • the component management interface 41 includes the application identifiers of the K applications, for example, the application identifier 805 of the instant messaging application.
  • the application identification 805 can receive a user's input operation (such as a touch operation).
  • the component label of the component provided by the instant messaging application is displayed in the component label display area corresponding to the application identification 805.
  • the component tag 806 of the friend circle page 14 and the component tag 807 of the music playback component is displayed in the component label display area corresponding to the application identification 805.
  • the component tag 806 of the friend circle page 14 and the component tag 807 of the music playback component for example, the component tag 806 of the friend circle page 14 and the component tag 807 of the music playback component.
  • Figure 17A can only display the application identifiers of some of the K applications, the user can view more application identifiers through a sliding operation (such as a sliding operation).
  • Figure 17C shows another component management interface 41.
  • the component management interface 41 can directly display component labels of components provided by each application that can be used for component positioning.
  • the arrangement order of the K applications may be based on the latest usage time of the components provided by the K applications, the usage frequency of the components provided by the K applications, and the exit time of the K applications.
  • the component label display area can display a preset number (for example, 4) of component labels at most. When the number of components exceeds the preset number, the user can view the component labels of more components through a sliding operation (such as a left sliding operation). .
  • a preset number for example, 4
  • the user can view the component labels of more components through a sliding operation (such as a left sliding operation).
  • component management is not performed in manner 4.
  • the application that provides the component is used as the dimension
  • the superimposed application that uses the component is used as the dimension.
  • Method 5 Display the user ID of the user using the component
  • some components can be used by multiple users.
  • the components in the terminal device 100 that can currently be located are managed from the perspective of users who have used the components.
  • the components currently available for component positioning in the terminal device 100 have been used by D users.
  • Figure 18 shows a component management interface 41 with the application of providing components as the dimension.
  • the component management interface 41 includes the user identifications (such as user avatars and/or user names) of the above D users, such as user " Leo" user identification 808, and the component label display area corresponding to the user identification of each user displays the component label of the component used by the user.
  • the component label display area of the user "Leo” includes: the component label 809 of the voting component 308 and the component label 810 of the Excel component 403 .
  • Figure 18 can only display the user IDs of some of the above D users, the user can view more user IDs through a sliding operation (such as a sliding operation).
  • the arrangement order of the D users may be determined based on the time when the D users recently used the component and/or the frequency of use of the component by the D users.
  • the time when each user recently used the component is determined, and the order of the above-mentioned D users is the reverse order of the time when the above-mentioned D users recently used the component, That is, users who have recently used the component are ranked first.
  • the arrangement order of the above D users is the positive order of component usage frequency of the above D users, that is, the user with the highest usage frequency is ranked first.
  • the component label display area displays a preset number (for example, 3) of component labels at most.
  • a preset number for example, 3
  • the user can view the component labels of more components through a sliding operation (such as a left sliding operation).
  • component management is not performed in manner five.
  • Method 6 Display the device ID of the device using the component.
  • the user's H devices are collaboratively connected.
  • the user can perform component management on the components used in the above H devices in the terminal device 100 from the device dimension.
  • the terminal The device 100 may be one of the H devices mentioned above; H is a positive integer.
  • the above H devices can establish collaborative connections by logging in to the same account, connecting to the same local area network, etc., which are not specifically limited here.
  • FIG. 19A shows a component management interface 41 with the device using the component as the dimension.
  • the component management interface 41 includes the device identifiers (such as device icons and/or device names) of the H devices, such as XX mobile phone.
  • the device identification 811 of each device the component label display area corresponding to the device identification of each device displays the component label of the component used by the device.
  • the component label display area of XX mobile phone includes: the component label 809 of the voting component 308 and the component label 810 of the Excel component 403. It should be noted that when Figure 19A can only display the device identifiers of some of the above H devices, the user can view more device identifiers through a sliding operation (such as a sliding operation).
  • the arrangement order of the H devices may be determined based on the time when the H devices recently used the component and/or the frequency of use of the component by the H devices.
  • the component label display area displays a preset number (for example, 3) of component labels at most.
  • a preset number for example, 3
  • the user can view the component labels of more components through a sliding operation (such as a left sliding operation).
  • component management is not performed in manner six.
  • the user can use component 1 through this device or through other collaboratively connected devices.
  • the user can choose to stream component 1 to a specified device among the above multiple devices for opening in this device.
  • dragging the component label of component 1 used by device 1 onto the device identifier of device 2 can realize the component transfer function.
  • the terminal device 100 is a XX mobile phone, and the Excel component 403 is used to display the Excel table "Project Schedule"; the component label 810 of the Excel component 403 to the device identification of the XX tablet is detected. 812, in response to the above sliding operation, the terminal device 100 sends the relevant data of the Excel component 403 to the XX tablet, and the XX tablet displays the above Excel table based on the above relevant data.
  • the terminal device 100 in response to the above sliding operation, calls the Excel application to display the above Excel table, and sends the projection data of the Excel application to the XX tablet through the screen projection channel; the XX tablet based on the above projection data Display the above Excel table.
  • the terminal device 100 in response to the above sliding operation, sends the table data of the Excel table displayed by the Excel component 403 to the XX tablet; the XX tablet calls the Excel application to display the above Excel table based on the above table data.
  • device 2 for example, XX tablet
  • application 2 for example, Excel application
  • component 1 for example, Excel component 403
  • the display content for example, table data
  • device 2 calls application 2 to display the above display content; if device 2 does not install application 2, it sends the screencast data of application 2 to device 2, and device 2 displays the above display content based on the screencast data.
  • Method 7 Display the event ID of the event corresponding to the component.
  • component 1 is classified as a component that specifies an event based on the keyword of component 1 or the event label of component 1 , and the event label may be manually labeled or automatically labeled.
  • the seventh method components in the terminal device 100 that can currently be located are managed using events corresponding to the components as dimensions.
  • Method 8 Display the identification of the Widget where the component is located.
  • multiple Widgets can be created, and multiple components can be added to a Widget based on a preset theme corresponding to the Widget.
  • the components in the terminal device 100 that can currently be located are managed using the Widget corresponding to the component as the dimension.
  • the terminal device 100 performs component management on a fixed basis based on one or more of the display modes; or, one or more of the display modes are selected based on multiple factors. Component management is performed in various display modes, and this application does not limit this.
  • multiple preset display modes can be switched.
  • the display mode is switched through a switching control.
  • the current display mode of the component management interface 41 is the above-mentioned mode 1, that is, using the application that uses the component as the dimension, displaying the application identification of the application that uses the component.
  • the component management interface 41 also includes a switching control 814 .
  • the switching control 814 can receive a user's input operation (such as a touch operation), and in response to the above input operation, display a switching box, which includes multiple display mode options, for example, the above-mentioned mode one ( That is, the option 815 of the application that uses the component is the dimension) and the option 816 of the above-mentioned method six (that is, the device that provides the component is the dimension).
  • a user's input operation such as a touch operation
  • display a switching box which includes multiple display mode options, for example, the above-mentioned mode one ( That is, the option 815 of the application that uses the component is the dimension) and the option 816 of the above-mentioned method six (that is, the device that provides the component is the dimension).
  • the display mode is switched to option 816, that is, component management is performed with the device using the component as the dimension.
  • the display mode is switched directly through the options of each display mode.
  • the component management interface can directly include options in multiple display modes, such as option 815 and option 816.
  • Option 815 is selected and option 816 is unselected.
  • the status of switching option 815 is an unselected state, and the status of switching option 816 is a selected state, that is, component management is performed with the device using the component as the dimension.
  • the embodiment of the present application provides an interface display method, which is applied to the terminal device 100 including a touch display screen.
  • Figure 21 shows a schematic flowchart of the above interface display method. in,
  • the content of the first page includes one or more components, and the one or more components include the first component.
  • the first component may be the aforementioned component 1.
  • the first component may be a component inserted into a specific page.
  • the first component may also be a page corresponding to an application window of the first application, that is, the first page.
  • the first component may be provided by a first application (for example, the aforementioned application 1), or may be provided by another application (for example, the aforementioned application 2).
  • the first page of the first application may be the circle of friends page 14 of the instant messaging application, and the first component may be the circle of friends page.
  • the first page of the first application may be the chat page 15 of the instant messaging application, and the first component may be the voting component 308 inserted in the chat page 15 .
  • the first page of the first application may be the chat page 15 of the instant messaging application, and the first component may be the music playing component 310 inserted in the chat page 15 .
  • the first page of the first application may be the ZZ1 page of the collaborative office application, and the first component may be the Excel component 403 inserted in the ZZ1 page.
  • the first page of the first application may be the ZZ2 page of the collaborative office application, and the first component may be the Word component 407 inserted in the ZZ1 page.
  • S102 Receive a first operation of input, wherein the first operation includes at least one input operation; in response to the first operation, display the second page of the first application or the third page of the second application.
  • the first operation is used to switch the first page of the first application to another page, that is, the second page of the first application or the third page of the second application.
  • the first page of the first application may be the chat page 15 of the instant messaging application.
  • the chat page 15 can be switched to the homepage 12 of the instant messaging application; when the first operation is used to return to the desktop, in response to the first operation, the chat page 15 can be switched to the homepage 12 of the instant messaging application. 15Switch to or the main interface of the desktop application11.
  • S103 Receive a second input operation; in response to the second operation, display a fourth page, where at least one component label is displayed on the fourth page, and the at least one component label includes the first component label.
  • the fourth page may be the aforementioned component management interface.
  • the component management interface may be a historical task interface, a negative screen or a notification bar interface, or it may be other pages, which are not specifically limited here.
  • the fourth page may be a historical task interface
  • the second operation may be a touch operation on the multi-task key 201C.
  • the historical task interface may display one or more component labels.
  • the third operation may be the aforementioned preset operation 1.
  • the display position of the component in Application 1 can be quickly located by preset operation 1 acting on the component label of Component 1 in the component management interface.
  • the first page of the first application is displayed.
  • the content of the first page includes one or more components.
  • the one or more components include the first component, including: displaying the first page of the first application.
  • a first part of the first page, the first page further includes a second part; wherein when the input sliding gesture is detected, the second part of the first page is displayed, and the second part includes the first component.
  • the first page is a long page
  • the terminal device 100 can only display part of the content of the long page.
  • the user needs to slide up, down, left, or right to view the entire content of the page.
  • the ZZ1 page 18 shown in Figure 10B, the circle of friends page 14 shown in Figure 11D, and the chat page 15 shown in Figure 4G and Figure 5D are all long pages.
  • part of the first page displayed on the display screen may be the first part that does not include the first component; after the first application is switched to the background, through the first component acting on the first component
  • the default operation 1 of the component label can still quickly locate and display the first component on the first page.
  • the method further includes: the first component is a plug-in component, and when receiving an action on the first component During the fourth operation of the label, in response to the fourth operation, the first application is opened and the first content page of the first component is displayed, where the third operation is different from the fourth operation.
  • the method further includes: the first component is a plug-in component, and when receiving a fourth operation acting on the label of the first component, in response to the fourth operation, opening a third application and displaying the first component The second content page, where the third operation is different from the fourth operation.
  • the fourth operation may be the aforementioned default operation 2, and the third application may be the aforementioned application 2.
  • the preset operation 2 acting on the component label of component 1 the user interface associated with the display content of the component can be displayed in application 1, such as the aforementioned first content page.
  • the application 2 that provides the component 1 can be called, and the user interface associated with the display content of the component is displayed in the application 2, such as the aforementioned second content page.
  • the first page of the first application may be the chat page 15 of the instant messaging application, and the first component may be the music playback inserted in the chat page 15 Component 310, the first component label may be the component label 612 of the music playing component 310; through the preset operation 1 acting on the component label 612, the terminal device 100 can display the music playing component 310 on the chat page 15 of the instant messaging application.
  • the first content page may be the aforementioned simple play interface 16; through the preset operation 2 acting on the component tag 612, the terminal device 100 may display the simple play interface 16 of the song played by the music play component 310 in the instant messaging application.
  • the second content page may be the aforementioned original playing interface 17; through the preset operation 2 acting on the component tag 612, the terminal device 100 may call the music application and display the original playing interface 17 of the song played by the music playing component 310 in the music application.
  • the first page of the first application may be the ZZ1 page of the collaborative office application
  • the first component may be the Excel component 403 inserted in the ZZ1 page
  • the first component label may be The component label 601 of the Excel component 403; through the preset operation 1 acting on the component label 601, the terminal device 100 can display the Excel component 403 on the ZZ1 page of the collaborative office application.
  • the second content page may be the user interface 19 of the aforementioned Excel application; through the preset operation 2 acting on the component label 601, the terminal device 100 calls the Excel application to display the user interface 19 in the Excel application, and the user interface 19 is used to display the Excel component. 403's "Project Schedule".
  • the first page of the first application may be the circle of friends page 14 of the instant messaging application
  • the first component may be the circle of friends page
  • the first component label may be the circle of friends.
  • the first component displayed on the first page provides a first function related to the display content of the first component; the first content page or the second content page provides a third function related to the display content of the first component.
  • First function and second function the first component cannot provide the second function. It can be understood that the first component can only provide some functions related to the display content of the first component (such as the first function). If the user needs to experience more functions related to the display content of the first component (such as the second function), The user can call the first content page or the second content page through the fourth operation.
  • the first content page or the second content page can be understood as a detail page of the display content of the first component, which can provide richer functions.
  • the method further includes: displaying a fifth page, where the fifth page includes an application identification corresponding to the first application; the fifth page further includes: At least one extended control; receiving a fifth operation acting on the extended control; in response to the fifth operation, displaying a fourth page; the above-mentioned application identification may be an application identification of an application that calls the component.
  • the fifth page may be the historical task interface 21 shown in FIG. 7A .
  • the historical task interface 21 includes extended controls corresponding to the application identifiers of each application of the calling component, such as collaborative office.
  • application The application identifier 204 corresponds to the extended control 501.
  • the fourth page may be the historical task interface 21 shown in FIG. 7B to FIG. 7D
  • the fifth operation may be a touch operation on the extended control 501 .
  • the terminal device 100 displays the component label display area of the collaborative office application.
  • 503 displays the component labels of the components that can be located in the collaborative office application, such as component labels 601 to 604 .
  • the first component includes: a component called by the first application; or, during the latest running of the first application, a component called by the first application; or, within the first preset time period, the first component The components called by the application; or, within the second preset time period, the preset number of components with the highest usage rate among the components called by the first application.
  • the at least one component label includes at least two component labels, wherein the arrangement order of the two component labels is determined based on the latest usage time and/or frequency of use of the component indicated by the component label.
  • the third operation is a click operation on the first component label; the fourth operation is a sliding operation of dragging the first component label to the third control after long-pressing the first component label.
  • the third control displays an application identification of the third application and/or third prompt information, and the third prompt information is used to prompt the third application to display the third component by dragging the first component label to the third control. Content related to a component.
  • the third control is displayed after detecting a long press operation on the first component label.
  • the third control may be the preset area 641
  • the third application may be a music application
  • the fourth operation may include a long The sliding operation of dragging the component label 601 to the preset area 641.
  • the preset area 641 may be displayed after long pressing the component label 601 .
  • the preset area 641 displays the application identification of the music application and/or third prompt information (for example, the text "Drag here to open the component through the following application").
  • the fourth page includes a fourth control and a fifth control; the third operation includes a sliding operation from the first component label to the fourth control; the fourth operation includes a sliding operation from the first component label to the fifth control. Slide operation.
  • the third operation includes long-pressing the first component label and then dragging the first component label to the sliding operation of the fourth control; the fourth operation includes long-pressing the first component label and then dragging the first component label to The sliding operation of the fifth control.
  • the fourth control and the fifth control are displayed after detecting a long press operation on the first component label.
  • the fourth control displays the application identification and/or the first prompt information of the first application
  • the fifth control displays the application identification and/or the second prompt information of the third application
  • the first prompt information is The second prompt information is used to prompt the component to be located in the application that calls the first component
  • the second prompt information is used to prompt the component to be opened through the application that provides the first component. It can be understood that the third application that provides the first component opens the first component and can display the second content page.
  • the fourth control may be the application identifier 621 of the collaborative office application, and the fifth control may be the application identifier 622 of the Excel application.
  • the third operation includes a sliding operation from the component label 601 to the application identification 621; the fourth operation may include a sliding operation from the component label 601 to the application identification 621.
  • the third operation includes a sliding operation of long pressing the component label 601 and then dragging to the application identification 621; the fourth operation may include a sliding operation of long pressing the component label 601 and then dragging to the application identification 621.
  • the application identification 621 of the collaborative office application and the application identification 622 of the Excel application may be displayed after long pressing the component label 601.
  • the fourth control may be a page positioning control 631 , and the fourth control displays the first prompt information (for example, the text "Page”Positioning"); the fifth control may be the source positioning control 632, and the fifth control displays the second prompt information (for example, the text "Source Positioning”).
  • the third operation includes a sliding operation from the component label 601 to the page positioning control 631; the fourth operation may include a sliding operation from the component label 601 to the page positioning control 631; Sliding operation from component label 601 to source location control 632.
  • the third operation includes a sliding operation of long pressing the component label 601 and then dragging to the page positioning control 631; the fourth operation may include a sliding operation of long pressing the component label 601 and then dragging to the source positioning control 632.
  • the page positioning control 631 and the source positioning control 632 can be displayed after long pressing the component label 601.
  • the third operation and the fourth operation are one of the following operations: a click operation acting on the first component label; a long press operation acting on the first component label; The sliding operation; the left sliding operation acting on the first component label; the upward sliding operation acting on the first component label; the sliding operation acting on the first component label; the third operation and the fourth operation are different.
  • the third operation may be a left sliding operation acting on the component label
  • the fourth operation may be a right sliding operation acting on the component label.
  • the method further includes: when receiving a sixth operation acting on the first component label, in response to the sixth operation, displaying one or more of the following on the fourth page: at least one of the following in the first application
  • the user identification of one contact, the application identification of the fourth application, and the page identification of the designated page of the fourth application includes the user identification of the first contact, and the user identification of the first contact is for sharing the first component to the first contact in the first application
  • the application identification of the fourth application is used for sharing the first component to the contact in the fourth application
  • the page identification of the designated page of the fourth application is used for Share the first component to the specified page of the fourth application.
  • the sixth operation may be a sliding operation on the component label 601
  • the first application is collaborative office.
  • the user identification of the first contact person may be the user identification 651
  • the application identification of the fourth application may be the application identification 652 of the instant messaging application
  • the page identification of the designated page of the fourth application may be the friend circle page 14 of the instant messaging application.
  • the page ID is 653.
  • the Excel component 403 can be shared with contacts of this application through the user identification 651 . Referring to the relevant descriptions of FIGS.
  • the Excel component 403 can be shared with contacts of the instant messaging application through the application identifier 652 . Referring to the related descriptions of FIG. 12J and FIG. 12K , the Excel component 403 can be shared to the circle of friends page 14 through the page identifier 653 .
  • the method further includes: when receiving a seventh operation acting on the first component label, the seventh operation is used to preview the first component in the first page, and in response to the seventh operation, according to the seventh operation The original size or enlarged size of a component, and the component snapshot of the first component is displayed on the fourth page.
  • the seventh operation may be a double-click operation on the component label 601 .
  • double-clicking the component label 601 the user can preview the displayed content of the Excel component 403.
  • the method further includes: when receiving an eighth operation that acts on the first component label, in response to the eighth operation, stopping displaying the first component label, and moving component labels after the first component label to Displayed one position ahead.
  • the seventh operation may be a slide-up operation acting on the component label 611 .
  • the terminal device 100 can stop displaying the component label 611, move the component label of the component ranked after the circle of friends page 14 forward one position, and can also remove the circle of friends page from the component management whitelist. Remove.
  • the components indicated by the component labels displayed on the fourth page are all components in the component management whitelist; the component management whitelist is set by one or more of the terminal device, the first application, and the user.
  • Figures 13A to 13D show relevant user interface diagrams for managing whitelists through the system settings management component, No further details will be given here.
  • the first component tag includes the component identifier of the first component; the first component tag also includes zero, one or more of the following: the page identifier of the page where the first component is located, and provides the application of the first component.
  • the application identifier is the workspace identifier of the workspace where the first component is located; the component identifier includes one or more of the following: component icon, component name and component snapshot, the page identifier includes the page icon and/or page name, the application in the component tag
  • the identification includes the application icon and/or the application name, and the workspace identification includes the workspace icon and/or the workspace name.
  • the first component label includes: the component icon or component snapshot of the first component, and the page name of the first page; or, the component icon or component snapshot of the first component, and the workspace where the first page is located. the workspace name; or, the component icon or component snapshot of the first component, and the component name of the first component; or, the page icon of the first page and the component name of the first component; or, the application that provides the first component The application icon and the component name of the first component.
  • the at least one component tag further includes a second component tag, the second component tag is associated with the first component called on the tenth page of the first application, and the first component tag is different from the second component tag, the first component tag includes the page identifier of the first page, and the second component tag includes the page identifier of the tenth page.
  • the same component that is, the Excel component 403 is called on the ZZ1 page and the ZZ3 page; the component label 601 of the Excel component 403 of the ZZ1 page and the Excel component of the ZZ3 page 403's component tag 603 is different.
  • the component label 601 of the Excel component 403 of the ZZ1 page includes the page identification of the ZZ1 page (for example, the page name "ZZ1"), and the component label 603 of the Excel component 403 of the ZZ3 page includes the page identification of the ZZ3 page (for example, the page name "ZZ3").
  • the component labels in the fourth page can be displayed in a variety of ways; for example, based on the application that calls the component, the application that provides the component, the device that calls the component, the user who uses the component, the page where the component is located, the Widget that adds the component and other classification methods (or display dimensions) for classification display.
  • This classification display makes the display of component labels clearer, allowing users to quickly locate the component labels they want to operate, and enriches the display method of component labels.
  • the fourth page includes at least one application identifier, and the at least one application identifier includes a first application identifier; the component label display area corresponding to the first application identifier in the fourth page displays the first application identifier. At least one component tag associated with the component called by the indicated application.
  • the application indicated by the first application identifier may be a collaborative office application.
  • the terminal device can display the component label associated with the component called by the application in the component label display area 503 corresponding to the application identifier of the collaborative office application in the component management interface 41 (ie, the fourth page).
  • the fourth page includes at least two application identifiers corresponding to the application that calls the component; in the fourth page, each application identifier can be displayed simultaneously in the component label display area corresponding to the at least two application identifiers.
  • the component tag associated with the component called by the indicated application For example, referring to the relevant description of FIG. 14B , the terminal device may simultaneously display component labels associated with components called by each application on the component management interface 41 .
  • the fourth page includes at least one application identifier, and the at least one application identifier includes a second application identifier; the component label display area corresponding to the second application identifier in the fourth page displays the second application identifier. At least one component tag associated with the component provided by the indicated application.
  • the application indicated by the second application identifier may be a collaborative office application.
  • the terminal device may display component labels associated with components provided by the application in the component label display area corresponding to the application identifier of the collaborative office application in the component management interface 41 .
  • the fourth page includes at least one device identifier, and the at least one device identifier includes the first Device identification; the component label display area corresponding to the first device identification on the fourth page displays at least one component label associated with the component called by the device indicated by the first device identification.
  • the device indicated by the first device identification may be the terminal device 100 .
  • the terminal device 100 may display the component tag associated with the component called by the device in the component tag display area corresponding to the device identification of the terminal device 100 in the component management interface 41 .
  • the fourth page includes at least one user identification, and the at least one user identification includes a first user identification; and the component label display area corresponding to the first user identification in the fourth page displays the first user identification. Indicates at least one component tag associated with the component used by the user.
  • the user indicated by the first user identification may be user "Leo".
  • the terminal device 100 may display the component labels associated with the components used by the user in the component label display area corresponding to the user identification of the user "Leo" in the component management interface 41 .
  • the fourth page includes at least one page identifier, and the at least one page identifier includes the first page identifier; the component label display area corresponding to the first page identifier in the fourth page displays the first page identifier. At least one component tag associated with the component called by the indicated page.
  • the fourth page includes at least one Widget identification, and the at least one Widget identification includes a first Widget identification; the component label display area corresponding to the first Widget identification in the fourth page displays the first Widget identification. At least one component tag associated with the component added by the indicated Widget.
  • the terminal device can use multiple display methods to display the component labels of the components to the user, and the user can also switch the display method of the component labels according to their own needs.
  • the fourth page further includes a first control and a second control
  • the method further includes: when receiving a touch input acting on the first control, displaying a sixth page, where the sixth page includes at least one user identification and a first component label; when receiving a third operation acting on the first component label on the sixth page; in response to the third operation, displaying the first page and displaying the first component on the first page .
  • the above-mentioned user ID may be the user ID of a user using the component.
  • a touch input acting on the second control is received, a seventh page is displayed, and the seventh page includes at least one device identification and a first component label; when a third touch input acting on the first component label on the seventh page is received.
  • the above device identification may be a user identification of the device that calls the component.
  • the fourth page includes an application identification of the application that calls the component
  • the fourth page also includes a sixth control and/or a seventh control
  • the method further includes: when receiving a touch that acts on the sixth control When input, an eighth page is displayed, and the eighth page includes an application identification and a first component label of at least one application that provides the component; when receiving a third operation that acts on the first component label on the eighth page; in response to The third operation is to display the first page and display the first component on the first page; when receiving the touch input acting on the seventh control, display the ninth page, and the ninth page includes at least one component added. Widget identification and the first component label of the Widget; when receiving the third operation acting on the first component label on the ninth page; in response to the third operation, displaying the first page and displaying the first component on the first page .
  • the current display mode of the component management interface 41 is classified and displayed based on the application that calls the component.
  • the second control can be the option 816 in the component management interface 41; in response to the option In the input operation 816, the terminal device 100 switches the status of the option 816 to the selected state, that is, classified display is performed based on the device using the component.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software when When implemented using software, it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in this application are generated in whole or in part.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another, e.g., the computer instructions may be transferred from a website, computer, server, or data center Transmission to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line) or wireless (such as infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more available media integrated.
  • the available media may be magnetic media (eg, floppy disk, hard disk, magnetic tape), optical media (eg, DVD), or semiconductor media (eg, solid state disk (SSD)), etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

本申请公开了界面显示方法及相关装置，所述方法中，显示第一应用的第一页面，第一页面的内容包括有一个或多个组件，所述一个或多个组件包括第一组件；接收输入的第一操作，其中第一操作包括至少一个输入操作；响应于第一操作，显示第一应用的第二页面或者第二应用的第三页面；接收输入的第二操作；响应于第二操作，显示第四页面，第四页面显示有至少一个组件标签，所述至少一个组件标签包括第一组件标签；当接收作用于第一组件标签的第三操作时，响应于第三操作，打开第一应用的第一页面，在第一页面上显示第一组件。这样，能够快速查看应用中的特定组件的相关信息，有效提高了用户的使用体验。

Description

界面显示方法及相关装置
本申请要求于2022年3月14日提交中国专利局、申请号为202210248494.X、申请名称为“一种快速定位组件的方法及电子设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。本申请要求于2022年5月27日提交中国专利局、申请号为202210586578.4、申请名称为“界面显示方法及相关装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及电子技术领域，尤其涉及界面显示方法及相关装置。
背景技术
用户使用完一个应用(例如应用1)，退出该应用时，可以将该应用切换至后台运行，将手机的显示界面切换为桌面或其他应用程序的界面。现有的主流操作***(例如Windows、Android、iOS)中，手机的历史任务界面可以显示后台运行的各应用(例如应用1)的应用标识，应用1的应用标识可以包括应用1的退出界面(即用户退出应用1时应用1展示的用户界面)的界面快照；通过点击历史任务界面中应用1的应用标识，手机可以快速切换到应用1的退出界面。
但是，应用1的退出界面并不一定是用户希望应用1展示的位置，用户可能希望查看应用1中的某个特定组件，用户需要进入应用1后通过多次点击后，才能到达这个特定组件。例如，在应用1的群聊页面中有个投票组件，应用1的退出界面是与联系人A的聊天页面，用户可以通过后台任务切换页面，到达联系人A的聊天页面，再多步操作，才可以到达投票组件的显示位置，这样的操作很繁琐，影响用户体验。
发明内容
本申请提供了界面显示方法及相关装置，能够快速查看应用中的特定组件的相关信息，上述相关信息包括组件的显示位置和显示内容，有效提高了用户的使用体验。
第一方面，本申请提供了界面显示方法，应用于包括触控显示屏的电子设备，方法包括：显示第一应用的第一页面，第一页面的内容包括有一个或多个组件，所述一个或多个组件包括第一组件；接收输入的第一操作，其中第一操作包括至少一个输入操作；响应于第一操作，显示第一应用的第二页面或者第二应用的第三页面；接收输入的第二操作；响应于第二操作，显示第四页面，第四页面显示有至少一个组件标签，所述至少一个组件标签包括第一组件标签；当接收作用于第一组件标签的第三操作时，响应于第三操作，打开第一应用，显示第一页面，并在第一页面上显示第一组件。
实施本申请实施例，可以在第四页面显示各组件关联的组件标签，通过针对组件标签的第三操作，能够快速定位该组件标签关联的组件(例如第一组件标签关联的第一组件)在应用中的显示位置，有效提高了用户的使用体验。
在一种实现方式中，所述显示第一应用的第一页面，第一页面的内容包括有一个或多个组件，所述一个或多个组件包括第一组件，包括：显示第一应用的第一页面的第一部分，第一页面还包括第二部分；其中当检测到输入的滑动手势时，显示第一页面的第二部分，第二 部分包括第一组件。实施本申请实施例，在一种场景中，显示屏只能显示第一页面的部分页面(例如第二部分)，用户通过滑动手势可以查看第一页面的当前未显示的部分(例如第一部分)，第二部分包括第一组件，第一部分不包括第一组件；即使显示屏在显示第一部分时第一应用被切换至后台运行，通过针对第一组件关联的第一组件标签的第三操作，也能够快速定位第一组件在第一应用中的显示位置位于第一页面的第二部分，并显示包括第一组件的第二部分，有效提高了用户的使用体验。
在一种实现方式中，所述方法还包括：第一组件为***型组件，当接收作用于第一组件标签的第四操作时，响应于第四操作，打开第一应用，显示第一组件的第一内容页面，其中第三操作与第四操作不同。实施本申请实施例，在一种场景中，用户通过操作(例如点击)第一应用的第一页面显示的第一组件，可以打开第一应用中的第一组件的第一内容页面；上述场景中，通过针对第一组件关联的组件标签的第四操作，能够快速调用第一应用显示第一组件的第一内容页面。
在一种实现方式中，所述方法还包括：第一组件为***型组件，当接收作用于第一组件标签的第四操作时，响应于第四操作，打开第三应用，显示第一组件的第二内容页面，其中第三操作与第四操作不同。实施本申请实施例，在一种场景中，用户通过操作(例如点击)第一应用的第一页面显示的第一组件，可以打开第三应用中与第一组件相关的第二内容页面；上述场景中，通过针对第一组件关联的组件标签的第四操作，能够快速调用第三应用显示第二内容页面。
在一种实现方式中，第一页面显示的第一组件提供与第一组件的显示内容相关的第一功能；第一内容页面或第二内容页面，提供与第一组件的显示内容相关的第一功能和第二功能，第一组件不能提供第二功能。实施本申请实施例，第一组件只能提供与第一组件的显示内容相关的部分功能，若用户需要体验与第一组件的显示内容相关的更多功能，用户可以通过第四操作调用第一内容页面或第二内容页面，第一内容页面或第二内容页面可以理解为第一组件的显示内容的详情页面，可以提供更丰富的功能。
在一种实现方式中，所述响应于第二操作后，显示第四页面前，所述方法还包括：显示第五页面，第五页面包括第一应用对应的应用标识；第五页面还包括至少一个拓展控件；接收作用于拓展控件的第五操作；响应于第五操作，显示第四页面；上述应用标识可以是调用组件的应用的应用标识。实施本申请实施例，用户通过第二操作调出的第五页面显示了调用组件的应用的应用标识和各应用标识对应的拓展控件，未显示组件标签；用户可以控制其中任一个应用标识对应的拓展控件，来显示该应用标识指示的应用调用过的组件的组件标签。这样，避免同时显示所有应用标识对应的组件的组件标签，所导致的页面复杂性和用户的视觉疲劳。
在一种实现方式中，第四页面还包括第一控件和第二控件，所述方法还包括：当接收到作用于第一控件的触摸输入时，显示第六页面，所示第六页面包括至少一个用户标识和第一组件标签；当接收作用于第六页面上的第一组件标签的第三操作时；响应于第三操作，显示第一页面，并在第一页面上显示第一组件。上述用户标识可以是使用组件的用户的用户标识。当接收到作用于第二控件的触摸输入时，显示第七页面，所示第七页面包括至少一个设备标识和第一组件标签；当接收作用于第七页面上的第一组件标签的第三操作时；响应于第三操作，显示第一页面，并在第一页面上显示第一组件。上述设备标识可以是调用组件的设备的用户标识。实施本申请实施例，在第四页面中，终端设备可以采用多种显示方式，对用户展 示组件的组件标签；用户还可以根据自身需求切换组件标签的显示方式。例如，在第四页面显示调用组件的各应用的应用标识，以及任一应用标识指示的应用所调用的组件的组件标签；例如，在第四页面显示使用组件的各用户的用户标识，以及任一用户标识指示的用户所使用的组件的组件标签；例如，在第四页面显示调用组件的各设备的设备标识，以及任一设备标识指示的设备所调用的组件的组件标签。这样，可以满足用户不同的组件标签展示需求和组件标签搜索需求，提高组件的使用便捷性，有效提升用户的使用体验。
在一种实现方式中，第四页面为历史任务界面，第四页面的显示内容包括第一应用的界面快照。实施本申请实施例，可以基于现有的用户熟悉的历史任务界面显示组件标签，符合用户使用习惯。
在一种实现方式中，第一组件，包括：第一应用调用过的组件；或者，第一应用的最近一次运行期间，第一应用调用的组件；或者，第一预设时长内，第一应用调用的组件；或者，第二预设时长内，第一应用调用的组件中使用率最高的预设数量的组件。实施本申请实施例，在第四页面中显示用户近期使用的和/或使用率高度的组件的组件便签，更贴合用户的使用需求，提高了用户的使用体验。
在一种实现方式中，所述至少一个组件标签包括至少两个组件标签，其中两个组件标签的排列顺序，是依据组件标签指示的组件的最近一次使用时间和/或使用频率确定的。实施本申请实施例，组件标签的排列顺序依据组件的最近一次使用时间和/或使用频率，更贴合用户的使用需求。
在一种实现方式中，第三操作为作用于第一组件标签的点击操作；第四操作为长按第一组件标签后将第一组件标签拖曳至第三控件的滑动操作。在一种实现方式中，第三控件显示有第三应用的应用标识和/或第三提示信息，第三提示信息用于提示通过将第一组件标签拖曳至第三控件触发第三应用显示第一组件的相关内容。
在一种实现方式中，第三控件是检测到作用于第一组件标签的长按操作后显示的。
在一种实现方式中，第四页面包括第四控件和第五控件；第三操作包括从第一组件标签至第四控件的滑动操作；第四操作包括从第一组件标签至第五控件的滑动操作。
在一种实现方式中，第三操作包括长按第一组件标签后将第一组件标签拖曳至第四控件的滑动操作；第四操作包括长按第一组件标签后将第一组件标签拖曳至第五控件的滑动操作。
在一种实现方式中，第四控件和第五控件是检测到作用于第一组件标签的长按操作后显示的。
在一种实现方式中，第四控件显示有第一应用的应用标识和/或第一提示信息，第五控件显示有第三应用的应用标识和/或第二提示信息；第一提示信息用于提示在调用第一组件的应用中进行组件定位，第二提示信息用于提示通过提供第一组件的应用打开组件。可以理解，提供第一组件的第三应用打开第一组件，可以显示第二内容页面。
在一种实现方式中，第三操作、第四操作为以下操作中的一个：作用于第一组件标签的点击操作；作用于第一组件标签的长按操作；作用于第一组件标签的右滑操作；作用于第一组件标签的左滑操作；作用于第一组件标签的上滑操作；作用于第一组件标签的下滑操作；第三操作和第四操作不同。
在一种实现方式中，所述方法还包括：当接收作用于第一组件标签的第六操作时，响应于第六操作，在第四页面显示以下一或多个：第一应用中的至少一个联系人的用户标识、第四应用的应用标识、第四应用的指定页面的页面标识；所述至少一个联系人的用户标识包括 第一联系人的用户标识，第一联系人的用户标识用于将第一组件分享给第一应用中的第一联系人；第四应用的应用标识用于将第一组件分享至第四应用中的联系人；第四应用的指定页面的页面标识用于将第一组件分享至第四应用的指定页面。实施本申请实施例，通过作用于组件的组件标签的第六操作，可以将该组件分享至调用组件的应用中的指定联系人、其他应用的指定联系人或其他应用的指定页面，有效提高用户的使用体验。
在一种实现方式中，所述方法还包括：当接收作用于第一组件标签的第七操作时，第七操作用于预览第一页面中的第一组件，响应于第七操作，按照第一组件的原尺寸或放大后的尺寸，在第四页面显示第一组件的组件快照。实施本申请实施例，通过作用于组件的组件标签的第七操作，无需定位到组件的显示位置，即可提前预览组件的显示内容；在一些场景中，用户可以基于预览到的显示内容进一步决定是否定位该组件，有效提高了用户的使用体验。
在一种实现方式中，所述方法还包括：当接收作用于第一组件标签的第八操作时，响应于第八操作，停止显示第一组件标签，将第一组件标签之后的组件标签向前顺延一个位置进行显示。实施本申请实施例，通过作用于组件的组件标签的第八操作，用户在第四页面中可以删除该组件便签，以查看更多其他的组件便签，有效提高了用户的使用体验。
在一种实现方式中，第四页面中显示的组件标签指示的组件均为组件管理白名单中的组件；组件管理白名单是终端设备、第一应用和用户中一或多个设置的。实施本申请实施例，利用组件管理白名单可以设置可通过第四页面进行组件管理(例如组件定位)的组件；用户可以根据个人需求设置组件管理白名单中的组件，实现个性化组件管理。
在一种实现方式中，第一组件为第一页面。实施本申请实施例，第一组件可以为***或嵌入到第一页面中的组件，也可以为第一页面本身。
在一种实现方式中，第一组件标签包括第一组件的组件标识；第一组件标签还包括以下零个、一个或多个：第一组件所在的页面的页面标识，提供第一组件的应用的应用标识，第一组件所在的工作区的工作区标识；组件标识包括以下一或多个：组件图标、组件名称和组件快照，页面标识包括页面图标和/或页面名称，组件标签中的应用标识包括应用图标和/或应用名称，工作区标识包括工作区图标和/或工作区名称。实施本申请实施例，通过组件标签，用户可以获知该组件标签关联的组件；组件标签包括页面标识时，通过组件标签中的页面标识，用户可以获知上述组件所在的页面，还可以区分不同页面中***的同一组件；组件标签包括工作区标识时，通过组件标签中的工作区标识，用户可以获知上述组件所在的工作区，还可以区分不同工作区中***的同一组件；组件标签包括应用标识时，通过组件标签中的应用标识，用户可以获知提供上述组件的应用。
在一种实现方式中，第一组件标签包括：第一组件的组件图标或组件快照，和第一页面的页面名称；或者，第一组件的组件图标或组件快照，和第一页面所在工作区的工作区名称；或者，第一组件的组件图标或组件快照，和第一组件的组件名称；或者，第一页面的页面图标和第一组件的组件名称；或者，提供第一组件的应用的应用图标和第一组件的组件名称。
在一种实现方式中，第四页面包括至少一个应用标识，所述至少一个应用标识包括第一应用标识；第四页面中的第一应用标识对应的组件标签显示区，显示有第一应用标识指示的应用调用的组件所关联的至少一个组件标签。实施本申请实施例，第四页面中组件便签能基于调用组件的应用进行分类显示，丰富组件标签的显示方式，提高用户的使用体验。
在一种实现方式中，第四页面包括至少一个应用标识，所述至少一个应用标识包括第二应用标识；第四页面中的第二应用标识对应的组件标签显示区，显示有第二应用标识指示的 应用提供的组件所关联的至少一个组件标签。实施本申请实施例，第四页面中组件便签能基于提供组件的应用进行分类显示，丰富组件标签的显示方式，提高用户的使用体验。
在一种实现方式中，第四页面包括至少一个设备标识，所述至少一个设备标识包括第一设备标识；第四页面中的第一设备标识对应的组件标签显示区，显示有第一设备标识指示的设备调用的组件所关联的至少一个组件标签。实施本申请实施例，第四页面中组件便签能基于调用组件的设备进行分类显示，丰富组件标签的显示方式，提高用户的使用体验。
在一种实现方式中，第四页面包括至少一个用户标识，所述至少一个用户标识包括第一用户标识；第四页面中的第一用户标识对应的组件标签显示区，显示有第一用户标识指示的用户使用的组件所关联的至少一个组件标签。实施本申请实施例，第四页面中组件便签能基于使用组件的用户进行分类显示，丰富组件标签的显示方式，提高用户的使用体验。
在一种实现方式中，第四页面包括至少一个页面标识，所述至少一个页面标识包括第一页面标识；第四页面中的第一页面标识对应的组件标签显示区，显示有第一页面标识指示的页面调用的组件所关联的至少一个组件标签。实施本申请实施例，第四页面中组件便签能基于组件所在的页面进行分类显示，丰富组件标签的显示方式，提高用户的使用体验。
在一种实现方式中，第四页面包括至少一个Widget(微件)标识，所述至少一个Widget标识包括第一Widget标识；第四页面中的第一Widget标识对应的组件标签显示区，显示有第一Widget标识指示的Widget添加的组件所关联的至少一个组件标签。实施本申请实施例，第四页面中组件便签能基于添加组件的Widget进行分类显示，丰富组件标签的显示方式，提高用户的使用体验。
实施本申请实施例，第四页面中组件标签可以有多种显示方式；例如基于调用组件的应用、提供组件的应用、调用组件的设备、使用组件的用户、组件所在的页面、添加组件的Widget等分类方式(或者显示维度)进行分类显示。这样分类显示，组件标签的显示更加清晰明了，以便于用户快速定位到自己想操作的组件标签，丰富了组件标签的显示方式，提高了用户的使用体验。
在一种实现方式中，第四页面包括调用组件的应用的应用标识，第四页面还包括第六控件和/或第七控件，所述方法还包括：当接收到作用于第六控件的触摸输入时，显示第八页面，所示第八页面包括至少一个提供组件的应用的应用标识和第一组件标签；当接收作用于第八页面上的第一组件标签的第三操作时；响应于第三操作，显示第一页面，并在第一页面上显示第一组件；当接收到作用于第七控件的触摸输入时，显示第九页面，所示第九页面包括至少一个添加了组件的Widget的Widget标识和第一组件标签；当接收作用于第九页面上的第一组件标签的第三操作时；响应于第三操作，显示第一页面，并在第一页面上显示第一组件。实施本申请实施例，用户还可以根据自身需求切换组件标签的显示方式。这样，可以满足用户不同的组件标签展示需求和组件标签搜索需求，提高组件的使用便捷性，有效提升用户的使用体验。
在一种实现方式中，第四页面包括调用组件的应用对应的至少两个应用标识，所述至少两个应用标识包括第一应用标识和第三应用标识；第四页面中，同时在第一应用标识对应的组件标签显示区，显示第一应用标识指示的应用调用的组件关联的组件标签时，在第三应用标识对应的组件标签显示区，显示第三应用标识指示的应用调用的组件关联的组件标签。实施本申请实施例，在第四页面可以同时显示各应用标识对应组件的组件标签，以避免增加用户操作。
在一种实现方式中，所述至少一个组件标签还包括第二组件标签，第二组件标签与在第一应用的第十页面调用的第一组件相关联，第一组件标签不同于第二组件标签，第一组件标签包括第一页面的页面标识，第二组件标签包括第十页面的页面标识。实施本申请实施例，通过组件标签包括的页面标识，可以便于用户区分不同页面中***的同一组件。
第二方面，本申请提供了一种终端设备，该终端设备可包括多个功能模块或单元，用于相应的执行第一方面所提供的界面显示方法。例如，显示单元和接收单元。
显示单元，用于显示第一应用的第一页面，第一页面的内容包括有一个或多个组件，所述一个或多个组件包括第一组件；
接收单元，用于接收输入的第一操作，其中第一操作包括至少一个输入操作；
显示单元，还用于响应于第一操作，显示第一应用的第二页面或者第二应用的第三页面；
接收单元，还用于接收输入的第二操作；
显示单元，还用于响应于第二操作，显示第四页面，第四页面显示有至少一个组件标签，所述至少一个组件标签包括第一组件标签；
显示单元，还用于当接收作用于第一组件标签的第三操作时，响应于第三操作，打开第一应用，显示第一页面，并在第一页面上显示第一组件。
在一种实现方式中，上述显示单元，具体用于显示第一应用的第一页面的第一部分，第一页面还包括第二部分；其中检测到输入的滑动手势时，显示单元还用于显示第一页面的第二部分，第二部分包括第一组件。
在一种实现方式中，第一组件为***型组件，当接收单元接收作用于第一组件标签的第四操作时，上述显示单元，还用于响应于第四操作，打开第一应用，显示第一组件的第一内容页面，其中第三操作与第四操作不同。
在一种实现方式中，所述方法还包括：第一组件为***型组件，当接收单元接收作用于第一组件标签的第四操作时，上述显示单元，还用于响应于第四操作，打开第三应用，显示第一组件的第二内容页面，其中第三操作与第四操作不同。
在一种实现方式中，响应于第二操作后，显示第四页面前，上述显示单元，还用于显示第五页面，第五页面包括第一应用对应的应用标识；第五页面还包括至少一个拓展控件；上述接收单元，还用于接收作用于拓展控件的第五操作；上述显示单元，还用于响应于第五操作，显示第四页面；上述应用标识可以是调用组件的应用的应用标识。
在一种实现方式中，第四页面还包括第一控件和第二控件，当接收单元接收到作用于第一控件的触摸输入时，上述显示单元，还用于显示第六页面，所示第六页面包括至少一个用户标识和第一组件标签；当接收单元接收作用于第六页面上的第一组件标签的第三操作时，上述显示单元，还用于响应于第三操作，显示第一页面，并在第一页面上显示第一组件；上述用户标识可以是使用组件的用户的用户标识。当接收单元接收到作用于第二控件的触摸输入时，上述显示单元，还用于显示第七页面，所示第七页面包括至少一个设备标识和第一组件标签；当接收单元接收作用于第七页面上的第一组件标签的第三操作时，上述显示单元，还用于响应于第三操作，显示第一页面，并在第一页面上显示第一组件；上述设备标识可以是调用组件的设备的用户标识。
在一种实现方式中，第四页面为历史任务界面，第四页面的显示内容包括第一应用的界面快照。
在一种实现方式中，第一组件，包括：第一应用调用过的组件；或者，第一应用的最近 一次运行期间，第一应用调用的组件；或者，第一预设时长内，第一应用调用的组件；或者，第二预设时长内，第一应用调用的组件中使用率最高的预设数量的组件。
在一种实现方式中，所述至少一个组件标签包括至少两个组件标签，其中所述两个组件标签的排列顺序，是依据组件标签指示的组件的最近一次使用时间和/或使用频率确定的。
在一种实现方式中，第三操作为作用于第一组件标签的点击操作；第四操作为长按第一组件标签后将第一组件标签拖曳至第三控件的滑动操作。在一种实现方式中，第三控件显示有第三应用的应用标识和/或第三提示信息，第三提示信息用于提示通过将第一组件标签拖曳至第三控件触发第三应用显示第一组件的相关内容。
在一种实现方式中，第三控件是检测到作用于第一组件标签的长按操作后显示的。
在一种实现方式中，第四页面包括第四控件和第五控件；第三操作包括从第一组件标签至第四控件的滑动操作；第四操作包括从第一组件标签至第五控件的滑动操作。
在一种实现方式中，第三操作包括长按第一组件标签后将第一组件标签拖曳至第四控件的滑动操作；第四操作包括长按第一组件标签后将第一组件标签拖曳至第五控件的滑动操作。
在一种实现方式中，第四控件和第五控件是检测到作用于第一组件标签的长按操作后显示的。
在一种实现方式中，第四控件显示有第一应用的应用标识和/或第一提示信息，第五控件显示有第三应用的应用标识和/或第二提示信息；第一提示信息用于提示在调用第一组件的应用中进行组件定位，第二提示信息用于提示通过提供第一组件的应用打开组件。
在一种实现方式中，第三操作、第四操作为以下操作中的一个：作用于第一组件标签的点击操作；作用于第一组件标签的长按操作；作用于第一组件标签的右滑操作；作用于第一组件标签的左滑操作；作用于第一组件标签的上滑操作；作用于第一组件标签的下滑操作；第三操作和第四操作不同。
在一种实现方式中，当接收单元接收作用于第一组件标签的第六操作时，上述显示单元，还用于响应于第六操作，在第四页面显示以下一或多个：第一应用中的至少一个联系人的用户标识、第四应用的应用标识、第四应用的指定页面的页面标识；所述至少一个联系人的用户标识包括第一联系人的用户标识，第一联系人的用户标识用于将第一组件分享给第一应用中的第一联系人；第四应用的应用标识用于将第一组件分享至第四应用中的联系人；第四应用的指定页面的页面标识用于将第一组件分享至第四应用的指定页面。
在一种实现方式中，当接收单元接收作用于第一组件标签的第七操作时，第七操作用于预览第一页面中的第一组件，上述显示单元，还用于响应于第七操作，按照第一组件的原尺寸或放大后的尺寸，在第四页面显示第一组件的组件快照。
在一种实现方式中，当接收单元接收作用于第一组件标签的第八操作时，上述显示单元，还用于响应于第八操作，停止显示第一组件标签，将第一组件标签之后的组件标签向前顺延一个位置进行显示。
在一种实现方式中，第四页面中显示的组件标签指示的组件均为组件管理白名单中的组件；组件管理白名单是终端设备、第一应用和用户中一或多个设置的。
第三方面，本申请提供了一种终端设备，包括一个或多个处理器和一个或多个存储器。该一个或多个存储器与一个或多个处理器耦合，一个或多个存储器用于存储计算机程序代码，计算机程序代码包括计算机指令，当一个或多个处理器执行计算机指令时，使得终端设备执行上述任一方面任一项可能的实现方式中的界面显示方法。
第四方面，本申请实施例提供了一种计算机存储介质，包括计算机指令，当计算机指令在终端设备上运行时，使得终端设备执行上述任一方面任一项可能的实现方式中的界面显示方法。
第五方面，本申请实施例提供了一种计算机程序产品，当计算机程序产品在计算机上运行时，使得计算机执行上述任一方面任一项可能的实现方式中的界面显示方法。
附图说明
图1为本申请实施例提供的终端设备的结构示意图；
图2A为本申请实施例提供的主界面；
图2B至图2C为本申请实施例提供的历史任务界面；
图3A至图3D为本申请实施例提供的使用朋友圈页面的示例性界面；
图4A至图4G为本申请实施例提供的使用投票组件的示例性界面；
图5A至图5F为本申请实施例提供的使用音乐播放组件的示例性界面；
图6A至图6E为本申请实施例提供的使用协同办公应用的示例性界面；
图7A至图7J为本申请实施例提供的历史任务界面；
图8和图9为本申请实施例提供的组件标签示意图；
图10A至图10I为本申请实施例提供的组件定位的示例性界面；
图11A至图11H为本申请实施例提供的组件定位的示例性界面；
图12A至图12K为本申请实施例提供的组件标签的功能的示例性界面；
图13A至图13D为本申请实施例提供的设置组件管理白名单的示例性界面；
图14A和图14B为本申请实施例提供的一种组件标签的显示方式；
图15A至图15D为本申请实施例提供的另一种组件标签的显示方式；
图16A和图16B为本申请实施例提供的另一种组件标签的显示方式；
图17A至图17C为本申请实施例提供的另一种组件标签的显示方式；
图18为本申请实施例提供的另一种组件标签的显示方式；
图19A和图19B为本申请实施例提供的另一种组件标签的显示方式；
图20A至图20E为本申请实施例提供的切换组件标签的显示方式的示例性界面；
图21为本申请实施例提供的界面显示方法的流程示意图。
具体实施方式
下面将结合附图对本申请实施例中的技术方案进行清楚、详尽地描述。其中，在本申请实施例的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B；文本中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，另外，在本申请实施例的描述中，“多个”是指两个或多于两个。
以下，术语“第一”、“第二”仅用于描述目的，而不能理解为暗示或暗示相对重要性或者隐含指明所指示的技术特征的数量。由此，限定有“第一”、“第二”的特征可以明示或者隐含地包括一个或者更多个该特征，在本申请实施例的描述中，除非另有说明，“多个”的含义是两个或两个以上。
下面介绍本申请实施例涉及的终端设备100的结构。
终端设备100可以是手机、平板电脑、桌面型计算机、膝上型计算机、手持计算机、笔 记本电脑、超级移动个人计算机(ultra-mobile personal computer，UMPC)、上网本，以及蜂窝电话、个人数字助理(personal digital assistant，PDA)、增强现实(augmented reality，AR)设备、虚拟现实(virtual reality，VR)设备、人工智能(artificial intelligence,AI)设备、可穿戴式设备、车载设备、智能家居设备和/或智慧城市设备，本申请实施例对该电子设备的具体类型不作特殊限制。终端设备可以搭载iOS、Android、Microsoft或者其它操作***，此处不作具体限定。
如图1所示，终端设备100可以包括处理器110，外部存储器接口120，内部存储器121，通用串行总线(universal serial bus，USB)接口130，充电管理模块140，电源管理模块141，电池142，天线1，天线2，移动通信模块150，无线通信模块160，音频模块170，扬声器170A，受话器170B，麦克风170C，耳机接口170D，传感器模块180，按键190，马达191，指示器192，摄像头193，显示屏194，以及用户标识模块(subscriber identification module，SIM)卡接口195等。其中传感器模块180可以包括压力传感器180A，陀螺仪传感器180B，气压传感器180C，磁传感器180D，加速度传感器180E，距离传感器180F，接近光传感器180G，指纹传感器180H，温度传感器180J，触摸传感器180K，环境光传感器180L，骨传导传感器180M等。
可以理解的是，本发明实施例示意的结构并不构成对终端设备100的具体限定。在本申请另一些实施例中，终端设备100可以包括比图示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。图示的部件可以以硬件，软件或软件和硬件的组合实现。
处理器110可以包括一个或多个处理单元，例如：处理器110可以包括应用处理器(application processor，AP)，调制解调处理器，图形处理器(graphics processing unit，GPU)，图像信号处理器(image signal processor，ISP)，控制器，视频编解码器，数字信号处理器(digital signal processor，DSP)，基带处理器，和/或神经网络处理器(neural-network processing unit，NPU)等。其中，不同的处理单元可以是独立的器件，也可以集成在一个或多个处理器中。
控制器可以根据指令操作码和时序信号，产生操作控制信号，完成取指令和执行指令的控制。
处理器110中还可以设置存储器，用于存储指令和数据。在一些实施例中，处理器110中的存储器为高速缓冲存储器。该存储器可以保存处理器110刚用过或循环使用的指令或数据。如果处理器110需要再次使用该指令或数据，可从所述存储器中直接调用。避免了重复存取，减少了处理器110的等待时间，因而提高了***的效率。
在一些实施例中，处理器110可以包括一个或多个接口。接口可以包括集成电路(inter-integrated circuit，I2C)接口，集成电路内置音频(inter-integrated circuit sound，I2S)接口，脉冲编码调制(pulse code modulation，PCM)接口，通用异步收发传输器(universal asynchronous receiver/transmitter，UART)接口，移动产业处理器接口(mobile industry processor interface，MIPI)，通用输入输出(general-purpose input/output，GPIO)接口，用户标识模块(subscriber identity module，SIM)接口，和/或通用串行总线(universal serial bus，USB)接口等。
充电管理模块140用于从充电器接收充电输入。其中，充电器可以是无线充电器，也可以是有线充电器。在一些有线充电的实施例中，充电管理模块140可以通过USB接口130接收有线充电器的充电输入。在一些无线充电的实施例中，充电管理模块140可以通过终端设备100的无线充电线圈接收无线充电输入。充电管理模块140为电池142充电的同时，还可 以通过电源管理模块141为终端设备供电。
电源管理模块141用于连接电池142，充电管理模块140与处理器110。电源管理模块141接收电池142和/或充电管理模块140的输入，为处理器110，内部存储器121，显示屏194，摄像头193，和无线通信模块160等供电。电源管理模块141还可以用于监测电池容量，电池循环次数，电池健康状态(漏电，阻抗)等参数。在其他一些实施例中，电源管理模块141也可以设置于处理器110中。在另一些实施例中，电源管理模块141和充电管理模块140也可以设置于同一个器件中。
终端设备100的无线通信功能可以通过天线1，天线2，移动通信模块150，无线通信模块160，调制解调处理器以及基带处理器等实现。
天线1和天线2用于发射和接收电磁波信号。终端设备100中的每个天线可用于覆盖单个或多个通信频带。不同的天线还可以复用，以提高天线的利用率。例如：可以将天线1复用为无线局域网的分集天线。在另外一些实施例中，天线可以和调谐开关结合使用。
移动通信模块150可以提供应用在终端设备100上的包括2G/3G/4G/5G等无线通信的解决方案。移动通信模块150可以包括至少一个滤波器，开关，功率放大器，低噪声放大器(low noise amplifier，LNA)等。移动通信模块150可以由天线1接收电磁波，并对接收的电磁波进行滤波，放大等处理，传送至调制解调处理器进行解调。移动通信模块150还可以对经调制解调处理器调制后的信号放大，经天线1转为电磁波辐射出去。在一些实施例中，移动通信模块150的至少部分功能模块可以被设置于处理器110中。在一些实施例中，移动通信模块150的至少部分功能模块可以与处理器110的至少部分模块被设置在同一个器件中。
调制解调处理器可以包括调制器和解调器。其中，调制器用于将待发送的低频基带信号调制成中高频信号。解调器用于将接收的电磁波信号解调为低频基带信号。随后解调器将解调得到的低频基带信号传送至基带处理器处理。低频基带信号经基带处理器处理后，被传递给应用处理器。应用处理器通过音频设备(不限于扬声器170A，受话器170B等)输出声音信号，或通过显示屏194显示图像或视频。在一些实施例中，调制解调处理器可以是独立的器件。在另一些实施例中，调制解调处理器可以独立于处理器110，与移动通信模块150或其他功能模块设置在同一个器件中。
无线通信模块160可以提供应用在终端设备100上的包括无线局域网(wireless local area networks，WLAN)(如无线保真(wireless fidelity，Wi-Fi)网络)，蓝牙(bluetooth，BT)，全球导航卫星***(global navigation satellite system，GNSS)，调频(frequency modulation，FM)，近距离无线通信技术(near field communication，NFC)，红外技术(infrared，IR)等无线通信的解决方案。无线通信模块160可以是集成至少一个通信处理模块的一个或多个器件。无线通信模块160经由天线2接收电磁波，将电磁波信号解调以及滤波处理，将处理后的信号发送到处理器110。无线通信模块160还可以从处理器110接收待发送的信号，对其进行调频，放大，经天线2转为电磁波辐射出去。
在一些实施例中，终端设备100的天线1和移动通信模块150耦合，天线2和无线通信模块160耦合，使得终端设备100可以通过无线通信技术与网络以及其他设备通信。所述无线通信技术可以包括全球移动通讯***(global system for mobile communications，GSM)，通用分组无线服务(general packet radio service，GPRS)，码分多址接入(code division multiple access，CDMA)，宽带码分多址(wideband code division multiple access，WCDMA)，时分码分多址(time-division code division multiple access，TD-SCDMA)，长期演进(long term evolution， LTE)，BT，GNSS，WLAN，NFC，FM，和/或IR技术等。所述GNSS可以包括全球卫星定位***(global positioning system，GPS)，全球导航卫星***(global navigation satellite system，GLONASS)，北斗卫星导航***(beidou navigation satellite system，BDS)，准天顶卫星***(quasi-zenith satellite system，QZSS)和/或星基增强***(satellite based augmentation systems，SBAS)。
终端设备100通过GPU，显示屏194，以及应用处理器等实现显示功能。GPU为图像处理的微处理器，连接显示屏194和应用处理器。GPU用于执行数学和几何计算，用于图形渲染。处理器110可包括一个或多个GPU，其执行程序指令以生成或改变显示信息。
显示屏194用于显示图像，视频等。显示屏194包括显示面板。显示面板可以采用液晶显示屏(liquid crystal display，LCD)，有机发光二极管(organic light-emitting diode，OLED)，有源矩阵有机发光二极体或主动矩阵有机发光二极体(active-matrix organic light emitting diode的，AMOLED)，柔性发光二极管(flex light-emitting diode，FLED)，Miniled，MicroLed，Micro-oLed，量子点发光二极管(quantum dot light emitting diodes，QLED)等。在一些实施例中，终端设备100可以包括1个或N个显示屏194，N为大于1的正整数。
终端设备100可以通过ISP，摄像头193，视频编解码器，GPU，显示屏194以及应用处理器等实现拍摄功能。
ISP用于处理摄像头193反馈的数据。例如，拍照时，打开快门，光线通过镜头被传递到摄像头感光元件上，光信号转换为电信号，摄像头感光元件将所述电信号传递给ISP处理，转化为肉眼可见的图像。ISP还可以对图像的噪点，亮度进行算法优化。ISP还可以对拍摄场景的曝光，色温等参数优化。在一些实施例中，ISP可以设置在摄像头193中。
摄像头193用于捕获静态图像或视频。物体通过镜头生成光学图像投射到感光元件。感光元件可以是电荷耦合器件(charge coupled device，CCD)或互补金属氧化物半导体(complementary metal-oxide-semiconductor，CMOS)光电晶体管。感光元件把光信号转换成电信号，之后将电信号传递给ISP转换成数字图像信号。ISP将数字图像信号输出到DSP加工处理。DSP将数字图像信号转换成标准的RGB，YUV等格式的图像信号。在一些实施例中，终端设备100可以包括1个或N个摄像头193，N为大于1的正整数。
数字信号处理器用于处理数字信号，除了可以处理数字图像信号，还可以处理其他数字信号。例如，当终端设备100在频点选择时，数字信号处理器用于对频点能量进行傅里叶变换等。
视频编解码器用于对数字视频压缩或解压缩。终端设备100可以支持一种或多种视频编解码器。这样，终端设备100可以播放或录制多种编码格式的视频，例如：动态图像专家组(moving picture experts group，MPEG)1，MPEG2，MPEG3，MPEG4等。
NPU为神经网络(neural-network，NN)计算处理器，通过借鉴生物神经网络结构，例如借鉴人脑神经元之间传递模式，对输入信息快速处理，还可以不断的自学习。通过NPU可以实现终端设备100的智能认知等应用，例如：图像识别，人脸识别，语音识别，文本理解等。
内部存储器121可以包括一个或多个随机存取存储器(random access memory，RAM)和一个或多个非易失性存储器(non-volatile memory，NVM)。
随机存取存储器可以包括静态随机存储器(static random-access memory，SRAM)、动态随机存储器(dynamic random access memory，DRAM)、同步动态随机存储器(synchronous dynamic random access memory,SDRAM)、双倍资料率同步动态随机存取存储器(double data  rate synchronous dynamic random access memory,DDR SDRAM，例如第五代DDR SDRAM一般称为DDR5SDRAM)等；非易失性存储器可以包括磁盘存储器件、快闪存储器(flash memory)。
快闪存储器按照运作原理划分可以包括NOR FLASH、NAND FLASH、3D NAND FLASH等，按照存储单元电位阶数划分可以包括单阶存储单元(single-level cell,SLC)、多阶存储单元(multi-level cell,MLC)、三阶储存单元(triple-level cell,TLC)、四阶储存单元(quad-level cell,QLC)等，按照存储规范划分可以包括通用闪存存储(英文：universal flash storage，UFS)、嵌入式多媒体存储卡(embedded multi media Card，eMMC)等。
随机存取存储器可以由处理器110直接进行读写，可以用于存储操作***或其他正在运行中的程序的可执行程序(例如机器指令)，还可以用于存储用户及应用程序的数据等。
非易失性存储器也可以存储可执行程序和存储用户及应用程序的数据等，可以提前加载到随机存取存储器中，用于处理器110直接进行读写。
外部存储器接口120可以用于连接外部的非易失性存储器，实现扩展终端设备100的存储能力。外部的非易失性存储器通过外部存储器接口120与处理器110通信，实现数据存储功能。例如将音乐，视频等文件保存在外部的非易失性存储器中。
终端设备100可以通过音频模块170，扬声器170A，受话器170B，麦克风170C，耳机接口170D，以及应用处理器等实现音频功能。例如音乐播放，录音等。
音频模块170用于将数字音频信息转换成模拟音频信号输出，也用于将模拟音频输入转换为数字音频信号。音频模块170还可以用于对音频信号编码和解码。在一些实施例中，音频模块170可以设置于处理器110中，或将音频模块170的部分功能模块设置于处理器110中。
扬声器170A，也称“喇叭”，用于将音频电信号转换为声音信号。
受话器170B，也称“听筒”，用于将音频电信号转换成声音信号。
麦克风170C，也称“话筒”，“传声器”，用于将声音信号转换为电信号。
耳机接口170D用于连接有线耳机。
压力传感器180A用于感受压力信号，可以将压力信号转换成电信号。在一些实施例中，压力传感器180A可以设置于显示屏194。压力传感器180A的种类很多，如电阻式压力传感器，电感式压力传感器，电容式压力传感器等。
陀螺仪传感器180B可以用于确定终端设备100的运动姿态。在一些实施例中，可以通过陀螺仪传感器180B确定终端设备100围绕三个轴(即，x，y和z轴)的角速度。
气压传感器180C用于测量气压。
磁传感器180D包括霍尔传感器。
加速度传感器180E可检测终端设备100在各个方向上(一般为三轴)加速度的大小。当终端设备100静止时可检测出重力的大小及方向。还可以用于识别终端设备的姿态。
距离传感器180F，用于测量距离。终端设备100可以通过红外或激光测量距离。
接近光传感器180G可以包括例如发光二极管(LED)和光检测器，例如光电二极管。
环境光传感器180L用于感知环境光亮度。终端设备100可以根据感知的环境光亮度自适应调节显示屏194亮度。
指纹传感器180H用于采集指纹。
温度传感器180J用于检测温度。在一些实施例中，终端设备100利用温度传感器180J 检测的温度，执行温度处理策略。
触摸传感器180K，也称“触控器件”。触摸传感器180K可以设置于显示屏194，由触摸传感器180K与显示屏194组成触摸屏，也称“触控屏”。触摸传感器180K用于检测作用于其上或附近的触摸操作。触摸传感器可以将检测到的触摸操作传递给应用处理器，以确定触摸事件类型。可以通过显示屏194提供与触摸操作相关的视觉输出。在另一些实施例中，触摸传感器180K也可以设置于终端设备100的表面，与显示屏194所处的位置不同。
骨传导传感器180M可以获取振动信号。
按键190包括开机键，音量键等。按键190可以是机械按键。也可以是触摸式按键。终端设备100可以接收按键输入，产生与终端设备100的用户设置以及功能控制有关的键信号输入。
本申请以下实施例中的术语“用户界面(user interface，UI)”，是应用程序或操作***与用户之间进行交互和信息交换的接口。用户界面是通过java、可扩展标记语言(extensible markup language，XML)等特定计算机语言编写的源代码，界面源代码在终端设备上经过解析，渲染，最终呈现为用户可以识别的内容。用户界面常用的表现形式是图形用户界面(graphic user interface，GUI)，是指采用图形方式显示的与计算机操作相关的用户界面。它可以是在终端设备的显示屏中显示的文本、图标、按钮、菜单、选项卡、文本框、对话框、状态栏、导航栏、Widget(微件)等可视的界面元素。本申请实施中，“用户界面”也可以简称为“页面”、“界面”。
下面介绍本申请实施例提供的一种在终端设备100上实现的示例性图形用户界面。
图2A示例性示出了用于展示终端设备100安装的应用程序的主界面11。主界面11可以包括：状态栏，日历指示符，天气指示符，具有常用应用程序图标的托盘，导航栏201，以及其他应用程序图标的显示区域202。其中：
导航栏201可包括：返回键201A、主屏幕键201B、多任务键201C等***导航键。当检测到用户点击返回键201A时，终端设备100可显示当前页面的上一个页面。当检测到用户点击主屏幕键201B时，终端设备100可显示主界面。当检测到用户点击多任务键201C时，终端设备100可以在历史任务界面显示用户最近查看的且仍在后台运行的各应用的应用标识，如图2B所示；通过点击历史任务界面中的一个应用的应用标识，终端设备100可以快速切换到该应用的退出界面，即用户退出该应用时该应用展示的用户界面。各导航键的命名还可以为其他，本申请对此不做限制。
不限于虚拟按键，本申请实施例中，主界面11也可以不包括导航栏201，导航栏201中的各导航键可以实现为物理按键或导航手势。在一些实施例中，终端设备100通过用户的指定导航手势实现导航栏201中的各导航键的功能。例如，返回键201A对应的导航手势包括从终端设备100的显示屏194的左边缘向内滑动的手势；主屏幕键201B对应的导航手势包括从终端设备100的显示屏194的底部边缘的左半部分向上滑动的手势；多任务键201C对应的导航手势包括从终端设备100的显示屏194的底部边缘的右半部分向上滑动的手势。
其他应用程序图标的显示区域202可展示：即时通讯应用的图标202A、协同办公应用相册的图标202B、图库的图标、音乐的图标、应用商城的图标、云共享的图标、备忘录的图标、设置的图标202C。主界面11还可包括页面指示符203。其他应用程序图标可分布在多个页面，页面指示符203可用于指示用户当前查看的是哪一个页面中的应用程序。用户可以左右滑动其他应用程序图标的区域，来查看其他页面中的应用程序图标。
下面对本申请实施例涉及的历史任务界面进行示例性说明。
本申请实施例中，当用户打开新的应用时，终端设备100可以将在前台运行的应用切换到后台运行，并将该应用正在运行的应用程序窗口加入多任务队列中，并存储上述应用程序窗口最后显示的用户界面的快照作为该应用程序窗口在历史任务界面的界面快照。可选的，上述用户界面的快照可以为该用户界面的截图。用户可通过指定输入操作调出终端设备100的历史任务界面后，通过历史任务界中各应用的应用标识(例如界面快照)可以对上述多任务队列中的各个应用进行预览、快速切换和关闭后台运行，以及快速清理终端设备100的运行内存。
图2B和图2C是本申请实施例提供的两种历史任务界面的显示形式。
示例性的，用户先后使用联系人应用、图库应用、即时通讯应用、协同办公应用等应用后，联系人、相册、支付应用等应用先后被加入多任务队列。如图2A所示，终端设备100可以接收作用于多任务键201C的输入操作(例如触摸操作)，响应于上述输入操作，终端设备100基于上述多任务队列可以显示如图2B或图2C所示的历史任务界面21。历史任务界面21用于展示多任务队列中各应用的应用标识(例如协同办公应用的应用标识204，即时通讯应用的应用标识205)，应用标识可以包括应用图标、应用名称和界面快照。参见图2C，以协同办公应用的应用标识204为例，应用标识204包括应用图标204A、应用名称204B和界面快照204C。受限于屏幕的尺寸，终端设备100无法显示多任务队列中所有应用的应用标识时，用户可以通过作用于历史任务界面21的向左/向右的滑动操作查看更多应用的应用标识。
图2B所示的历史任务界面中，各应用的应用标识以二行多列的形式进行展示，各应用的应用标识从上至下地、从右至左地排列，多任务队列中最后一个切换至后台的应用的应用标识排列在最左侧一列的第一行。图2C所示的历史任务界面中，各应用的应用标识以一行多列的形式进行展示，各应用的应用标识按从右至左地排列，多任务队列中最后一个切换至后台的应用的应用标识排列在最左侧一列。
由图2B和图2C可知，应用标识204中的界面快照，即协同办公应用最后退出的应用程序窗口对应的用户界面的快照，和实际用户界面的显示尺寸不同。在一些实施例中，当终端设备100显示历史任务界面时，终端设备100以预设比例将上述截图缩小后，显示在应用标识204中。另一些实施例中，对上述用户界面的显示内容进行重新布局，将重新布局后的用户界面的快照作为应用标识204中的界面快照。另一些实施例中，选择上述用户界面中的部分内容的快照作为应用标识204中的界面快照。
需要说明的是，不限于图2B和图2C所示的历史任务界面，本申请实施例提供的界面显示方法也适用于其他显示形式的历史任务界面，此处不做具体限定。后续实施例以图2C所示的历史任务界面为例进行说明。
下面对本申请实施例涉及的组件进行介绍。
组件(component)：也可以被称为功能实体，通常用于实现一或多种特定功能。部分组件会提供一些标准的应用接口，允许使用者设置、调整参数和属性，可选地在一些情况下能够被第三方所组装。循环组件指在不同的应用程序均可以保持同步(即保持最新状态)的组件。
本申请实施例涉及的组件，从组件的表现形式来看，可以包括A类组件和B类组件；A类组件指可***到特定页面中的组件，例如列表组件、表格组件、文档组件、表单组件(例如投票表单)、指定联系人或群聊的对话框组件等等，或者悬浮在页面的卡片；B类组件指将 一个特定页面视为一个页面组件，例如，将应用的一个应用程序窗口对应的用户界面视为一个页面组件，将协同办公应用的工作空间***的一个页面视为一个页面组件、将小程序的页面视为一个页面组件。本申请实施例对组件类型和组件实现的功能不作具体限定。后续实施例会对各类组件进行示例性说明，此处不再赘述。
需要说明的是，上述应用程序窗口可以是Android***中的Activity窗口，还可以是IOS***中的应用程序窗口，还可以是其他操作***中的应用程序窗口，此处不作具体限定。一个应用包括多个应用程序窗口，一个应用程序窗口可以对应一个用户界面(即一个页面)。例如，Android***中Activity是用户和应用程序之间进行交互的接口，每一个Activity组件都关联有一个Window对象，用来描述一个具体的应用程序窗口(该应用程序窗口可以简称为Activity窗口)。由此可知，Activity是一个高度抽象的用户界面组件，在Android中代表了用户界面和以用户界面为中心的相应的业务逻辑，通过用户界面中的控件可以监听并处理用户触发的事件。可以理解，Android应用中，一个Activity可以表现为一个用户界面，一个Android应用可以拥有多个Activity。
本申请实施例中，可以将应用1的指定页面作为页面组件进行组件管理(例如组件定位)，上述指定页面可以是终端设备100默认设置的，也可以是应用1默认设置的，还可以是用户设置的，此处不作具体限定。
本申请实施例中，从组件的来源来看，组件可以包括C类组件和D类组件。用户可以在应用1中调用至少一种组件(例如C类组件或D类组件)，应用1包括上述至少一种组件中每个组件的调用入口。其中，C类组件可以是本应用(即应用1)提供的组件。D类组件(例如组件1)可以是其他应用程序(例如应用2)提供的组件，组件1可以包括应用1调用应用2或应用2的特定应用程序窗口的快捷入口。通过应用1中显示的组件1，可以调用应用2，并在应用2中显示与组件1的显示内容关联的特定应用程序窗口对应的用户界面。或者，通过应用1中显示的组件1，可以在应用1中显示应用2的特定应用程序窗口对应的用户界面，该用户界面的显示内容与组件1的显示内容关联；这样，无需打开应用2，避免了应用之间的跳转。
本申请实施例中，提供组件的应用(即应用1或应用2)可以包括Word应用、Excel应用、PPT(Powerpoint)应用、数据库、即时通讯应用、视频应用、音乐应用、网页应用、快应用等，还可以包括Microsoft Loop、OneNote，Outlook和Teams等可以进行多人协作的办公软件，本申请实施例对此不做具体限定。
可以理解，C类组件同时也可以是A类组件或B类组件，D类组件同时也可以是A类组件或B类组件。
下面结合附图，对本申请涉及的组件类型进行示例性说明。
示例性的，对于即时通信应用，本申请实施例可以将朋友圈页面作为B类组件(即页面组件)和C类组件进行组件管理，图3A至图3D示出了用户在即时通讯应用中显示本应用提供的朋友圈页面组件的用户界面图。
如图3A和图3B所示，即时通讯应用的图标202A可以接收用户的输入操作(例如触摸操作)，响应于上述输入操作，终端设备100显示即时通讯应用的主页12。主页12包括一或多个聊天条目，例如指定群聊(例如群聊1)的聊天条目301、文件传输助手的聊天条目302、指定联系人(例如Henry)的聊天条目303；聊天条目301包括群聊1的头像301A和群聊1 的群名称301B，聊天条目302包括文件传输助手的图标302A和文件传输助手的名称302B，聊天条目303包括联系人的头像303A和联系人的昵称303B。主页12还包括页面选项，例如主页选项、通讯录页面选项、发现页面选项304和本地页面选项。
如图3B和图3C所示，发现页面选项304可以接收用户的输入操作(例如触摸操作)，响应于上述输入操作，终端设备100显示发现页面13。发现页面13包括朋友圈条目305，朋友圈条目305包括朋友圈图标305A和朋友圈名称305B。
如图3C和图3D所示，朋友圈条目305可以接收用户的输入操作(例如触摸操作)，响应于上述输入操作(例如触摸操作)，终端设备100显示朋友圈页面14。朋友圈条目305可以视为朋友圈页面14的调用入口。
可以理解，主页12、发现页面13、朋友圈页面14为不同应用程序窗口(例如Activity窗口)对应的页面。
示例性的，即时通讯应用可以调用本应用提供的组件。以投票组件为例，图4A至图4G示出了用户在即时通讯应用中调用本应用提供的投票组件的用户界面图。
如图4A和图4B所示，聊天条目301可以接收用户的输入操作(例如触摸操作)，响应于上述输入操作，终端设备100显示群聊1的聊天页面15。聊天页面15显示有群聊1的实时聊天记录；受限于终端设备100的屏幕尺寸，终端设备100无法显示群聊1的全部聊天记录时，用户可以通过向上/向下的滑动操作查看群聊1的更多聊天记录。
如图4B和图4C所示，聊天页面15还包括***控件306；***控件306可以接收用户的输入操作(例如触摸操作)，响应于上述输入操作，终端设备100显示***选项显示区307，***选项显示区307包括聊天页面的多个***选项(例如照片选项、拍摄选项、视频通话选项、位置选项等等)的图标。如图4C和图4D所示，***选项显示区307可以接收用户的滑动操作，响应于上述输入操作，终端设备100可以显示更多***选项的图标，例如投票选项的投票图标307A、音乐选项的音乐图标307B、群接龙选项的图标、直播选项的图标等等。
如图4D和图4E所示，投票图标307A可以接收用户的输入操作(例如触摸操作)，响应于上述输入操作，终端设备100可以在聊天页面15的聊天记录中显示上述用户***的投票组件308。示例性的，如图4E所示，投票组件308包括投票标题308A，至少两个投票选项(例如投票选项308B)，各投票选项对应的投票控件(例如投票选项308B对应的投票控件308C)，以及增加控件308D。增加控件308D用于增加投票选项，以及该投票选项对应的投票控件。
在一种实现方式中，群聊1中的所有群成员均可以编辑投票标题和投票选项；终端设备100可以显示正在编辑/或最近编辑的群成员的昵称。示例性的，参见图4F，群成员“Henry”正在编辑投票选项308B，最近编辑投票标题308A的群成员为“Leo”。参见图4G，以投票选项308B为例，投票选项308B对应的投票控件308C上可以显示该投票选项获得的投票数量。
需要说明的是，图4E至图4G所示的投票组件是本申请实施例提供的示例性的投票组件，不应对本申请实施例构成限定。可选地，不限于即时通讯应用，投票组件也可以有由其他应用提供。
示例性的，即时通讯应用可以调用其他应用(例如，音乐应用)提供的组件。以音乐播放组件为例，图5A至图5F示出了用户在即时通讯应用中调用音乐应用提供的音乐播放组件的用户界面图。
如图5A和图5B所示，音乐选项307B可以接收用户的输入操作(例如触摸操作)，响应于上述输入操作，终端设备100显示音乐搜索区309，音乐搜索区309包括搜索输入框309A。 如图5C所示，用户可以在搜索输入框309A输入歌曲关键词，歌曲关键词可以包括歌名、歌词和/或歌手，例如歌名“AAA”；终端设备100可以获取与上述歌曲关键词相关的至少一个歌曲搜索结果(例如歌曲309B)，并在音乐搜索区309显示歌曲309B和该歌曲对应的发送控件309C。
如图5C和图5D所示，发送控件309C可以接收用户的输入操作(例如触摸操作)，响应于上述输入操作，终端设备100可以在聊天页面15的聊天记录中显示上述用户***的歌曲309B对应的音乐播放组件310。音乐播放组件310包括播放控件310A，响应于针对播放控件310A的输入操作，终端设备100可以播放歌曲309B。
如图5D和图5E所示，音乐播放组件310可以接收用户的输入操作(例如触摸操作)，响应于上述输入操作，终端设备100可以在即时通讯应用中显示歌曲309B的简易播放界面16。简易播放界面16包括来源控件311，来源控件311的显示内容可以为“来自音乐应用”。可以理解，简易播放界面16可以是音乐应用提供的用户界面；检测到用户点击音乐播放组件310时，无需跳转至音乐应用，终端设备100可以直接在即时通讯应用中显示音乐应用的提供的用户界面。简易播放界面16也可以是即时通讯应用提供的用户界面，即时通讯应用可以基于音乐应用的应用服务器提供的歌曲“AAA”的相关数据，显示简易播放界面16。应理解，用户点击组件后，终端设备100可以在本应用显示该组件对应的第一内容页面。例如，用户点击音乐播放组件310后，终端设备100显示音乐播放组件310的第一内容页面，即示例的简易播放界面16。
如图5E和图5F所示，来源控件311可以接收用户的输入操作(例如触摸操作)，响应于上述输入操作，终端设备100可以打开音乐应用，在音乐应用中显示歌曲309B的原始播放界面17。可以理解，来源控件311可以视为即时通讯应用调用音乐应用的原始播放界面17的快捷入口。原始播放界面17包括更多控件312，更多控件312用于调出更多功能控件，例如，用于将歌曲309B加入歌单的控件、用于查看歌曲309B的专辑的控件、用于查看歌曲309B的曲谱的控件等等。应理解，在第一内容页面(例如，简易播放界面16)上，接收到输入指令，终端设备100可以再调用其他应用显示该组件对应的第二内容页面(例如，原始播放界面17)。
可以理解，通过即时通讯应用中显示的音乐播放组件310，用户仅能控制歌曲309B的播放和暂停；相比音乐播放组件310，通过即时通讯应用中显示的简易播放界面16，用户还能控制歌曲309B的播放进度、分享、点赞和评论；相比简易播放界面16，通过音乐应用中显示的原始播放界面17，用户可以获取歌曲309B的更多信息，并可以体验与歌曲309B相关的更多功能，例如下载、查看专辑、查看曲谱等。
在一种实现方式中，检测到来源控件311接收到用户的输入操作，通过即时通讯应用向音乐应用发送歌曲309B的信息(例如歌曲名AAA和歌手名xx)；音乐应用基于上述歌曲309B的信息，生成并显示歌曲309B的原始播放界面17。
需要说明的是，不限于音乐应用，音乐播放组件310也可以有由本应用(即即时通讯应用)提供，此处不作具体限定。
本申请实施例中，即时通讯应用还可以使用本应用提供的群接龙组件、地图应用提供的位置组件、直播应用提供的直播组件等，此处也不作具体限定。
示例性的，协同办公应用可以调用其他应用提供的组件。
以Excel组件为例，图6A至图6B示出了用户在协同办公应用中调用Excel应用提供的 Excel组件的用户界面图。
需要说明的，本申请实施例涉及的协同办公应用在一些具体的实施方式中可以包括三种元素：workspace(工作空间)、page(页面)和component(组件)。workspace是一个面向项目(project)且具有多人协作功能的工作空间。page可以理解为workspace里的一个页面(具体的工作界面)，可以用于***(或者嵌入)组件和元素(例如链接、文字、图片、小程序(例如投票)等)；一个workspace可以包括多个页面。协同办公应用将多种应用的功能以组件的形式整合到一个应用中，用户无需打开提供指定功能的应用，即可在协同办公应用中以组件的形式使用上述指定功能；不同用户可以在同一页面上实时地进行协同工作。
图2A所示的协同办公应用的图标202B可以接收用户的输入操作(例如触摸操作)，响应于上述输入操作，终端设备100可以显示图6A所示的协同办公应用的用户界面18。如图6A所示，协同办公应用的用户界面18包括导航区和工作空间显示区，导航区包括一或多个项目的项目名称(例如项目名称401，即“XX3”)。
如图6A和图6B所示，响应于针对项目名称401的输入操作1(例如触摸操作)，终端设备100可以在导航区展开显示项目名称401对应的项目的页面导航，即该项目中***的各页面(例如ZZ1页面、ZZ1页面和ZZ3页面)的页面标识，以及页面中***的组件的组件标识。以ZZ1页面为例，终端设备100在导航区显示该页面的页面标识402，页面标识402可以包括该页面的页面图标402A和/或页面名称402B(例如ZZ1)；终端设备100还在导航区显示该页面中***的Excel组件403的组件标识404，组件标识404可以包括该组件的组件图标404A和/或组件名称404B，组件名称可以为Excel组件403中显示的Excel表格1的名称，即“项目进度表”。
可以理解，图6A所示的ZZ1页面、ZZ1页面和ZZ3页面均为协同办公应用中的项目XX3的工作空间中***的页面。用户可以为XX3项目的工作空间***新的页面，也可以删除已有的页面。示例性的，也可以将协同办公应用中的指定页面(例如ZZ3页面)作为页面组件进行组件管理。
如图6B所示，响应于针对项目名称401的输入操作1，终端设备100还可以在工作空间显示区显示ZZ1页面的页面内容(例如通过Excel组件403展示的项目进度表)，用户可以通过向上/向下的滑动操作查看ZZ1页面的更多内容。
在一些实施例中，检测到Excel组件403接收用户的输入操作2(例如双击操作)时，该Excel组件可以进入编辑状态，编辑状态下用户可以编辑Excel组件403展示的Excel表格1的显示内容。在一种实现方式中，不同用户可以同时编辑Excel组件403的显示内容；针对Excel组件403展示的Excel表格1中的一个单元格，终端设备100可以在该单元格显示正在编辑该单元格的用户的用户标识(例如图6B所示的用户昵称“Henry”)，也可以在该单元格显示最近编辑过该单元格的用户的用户标识(例如图6B所示的用户昵称“Lily”)。这样，终端设备100的用户可以实时看到其他用户正在编辑/或编辑过Excel组件403的哪些内容。
在一些实施例中，如图6B和图6C所示，检测到Excel组件403接收用户的输入操作3(例如长按操作)时，终端设备100调用Excel应用，通过Excel应用的用户界面19显示Excel表格1。
在一种实现方式中，Excel组件403中显示的Excel表格1的原始文件为本地存储或线上存储的Excel表格，Excel组件403关联有该表格的存储路径(例如本地存储路径或线上存储的URL(uniform resource locator，统一资源***)链接)；检测到针对Excel组件403的输 入操作3时，协同办公应用调用Excel应用，并向Excel应用发送上述存储路径；Excel应用通过上述存储路径获取上述原始文件的表格数据，并基于该表格数据在Excel应用显示Excel表格1。可选的，用户编辑Excel组件403中显示的Excel表格1后，终端设备100可以基于上述Excel表格1的更新数据，更新Excel表格1的原始文件的表格数据，以保证Excel表格1和原始文件的数据同步；上述更新方式可以是定时更新，也可以是在Excel表格1的表格数据发生变化时更新。可选的，Excel组件403可以获取存储路径指示的原始文件的表格数据，来更新Excel组件403中Excel表格1的显示内容，以保证Excel表格1和原始文件的数据同步；类似的，上述更新方式可以是定时更新，也可以是在原始文件的表格数据发生变化时更新。
可以理解，用户可以在不同页面***同一组件(例如Excel组件403)，不同用户可以在不同页面编辑Excel组件403中显示的Excel表格1，为保证不同页面的Excel组件403的显示内容的同步，需要及时更新Excel表格1和原始文件的表格数据。
在另一种实现方式中，检测到针对Excel组件403的输入操作3时，协同办公应用调用Excel应用，并直接向Excel应用发送Excel表格1的表格数据；Excel应用基于该表格数据在Excel应用显示Excel表格1。
本申请实施例对上述用于触发Excel组件进入编辑状态的输入操作2和用于触发调用应用2展示组件内容的输入操作3不做具体限定。
可以理解，通常，协同办公应用中Excel组件仅提供了Excel应用的部分功能，例如简单的编辑操作(例如输入、删除、复制或粘贴)；未提供调节字体格式、***公式、调整表格样式等等功能；用户编辑Excel组件403中显示的Excel表格1时，若需要体验更多功能，可以调用Excel应用，通过Excel应用显示和编辑Excel表格1。
以Word组件为例，图6D和图6E示出了用户在协同办公应用中调用Word应用提供的Word文档的用户界面图。
如图6B和图6D所示，ZZ2页面的页面标识405可以接收用户的输入操作，响应于上述输入操作，终端设备100在工作空间显示区显示ZZ2页面的页面内容，例如Excel组件406和Word组件407。
在一些实施例中，检测到Word组件407接收用户的输入操作3(例如双击操作)时，该Word组件可以进入编辑状态，编辑状态下用户可以编辑Word组件407展示的Word文档的显示内容。
在一些实施例中，如图6D和图6E所示，检测到Word组件407接收用户的输入操作4(例如长按操作)时，终端设备100调用Word应用，通过Word应用的用户界面20显示上述Word文档。具体的，调用Word应用、更新Word组件407的显示内容的实现方式，可以参考前述Excel组件403的相关描述，此处不再赘述。
类似的，协同办公应用中Word组件仅提供了Word应用的部分功能，若需要体验更多功能，可以调用Word应用，通过Word应用显示和编辑Word组件中的Word文档。
综上可知，用户在应用1中使用应用2提供的组件时，该组件通常仅能提供应用2的部分功能；用户可以通过该组件调用应用2，在应用2中显示上述组件的相关内容，进而体验应用2的更多功能。
终端设备100显示第一应用的包括有第一组件的第一页面时，将显示界面切换至第一应用的第二页面；然后，用户在使用完第一应用后，通常会将终端设备100的显示界面切换到 桌面、历史任务界面或其他应用的界面，第一应用则可以切换至后台运行。
用户在使用完终端设备100上的第一应用后，或者终端显示完包括有第一组件的第一页面时候，通常会将终端设备100的显示界面切换到桌面或其他应用的界面，或者同一应用的第二页面，第一应用则可以切换至后台运行。参考图2B和图2C，现有的主流操作***，例如Windows、Android、iOS，往往会使用历史任务界面展示这些在后台运行的应用。用户通过点击历史任务界面中的第一应用的应用标识，可以进入到该应用最后展示的(或用户最后操作的)的位置；该位置并不一定是用户希望第一应用展示的位置，用户可能希望查看该第一应用中的特定组件。可选的，上述特定组件可以为在该应用中最后一次使用的组件/特定类型的组件，例如第一页面的第一组件。
示例性的，参考图3A至图3D，用户在即时通讯应用使用了朋友圈页面后，终端设备100接收输入的至少一个触摸操作，可以返回即时通讯应用的主页，或者接收至少一个触摸输入后，显示第二应用的用户界面，并将即时通讯应用切换至后台运行。参考图2C，用户调出的历史任务界面21中，即时通讯应用的应用标识205中的界面快照可以为上述主页(即时通讯应用的退出界面)的截图。用户点击应用标识205后，终端设备100将显示即时通讯应用的主页。若用户意图再次查看朋友圈页面，则用户可以通过点击历史任务界面21中即时通讯应用的应用标识205或主界面11中即时通讯应用的图标202A进入即时通讯应用的主页，再依次点击发现页面选项304和朋友圈条目305。这样，操作繁琐，用户体验差。
可以理解，上述主流操作***在管理后台应用，并通过历史任务界面展示后台应用时，是以应用的维度进行管理，一个应用对应一个应用标识；终端设备100无法通过历史任务界面快速定位应用中特定组件的位置；用户通过点击历史任务界面中的应用标识进入应用1后，仍然需要在应用1的多个页面间、以及单个页面中通过翻页、滑动、搜索等多个操作，才能够找到到用户想要查看的特定组件。这样，操作不便捷，用户使用体验差。
本申请实施例提供了界面显示方法，实施本申请实施例，针对应用1中的特定组件(例如组件1)，在组件管理界面(例如前述历史任务界面)中提供组件1的组件标签。通过作用于上述组件标签的预设操作1，可以快速定位组件1在应用1中的位置，或者在应用1中展示该组件；例如，组件1***在长页面中，响应于上述预设操作1，可以直接定位到组件1在上述长页面中的位置；例如，组件1为页面组件，响应于上述预设操作1，可以直接显示该组件对应的页面。通过作用于上述组件标签的预设操作2，可以调用与组件1关联的应用2，在应用2中展示该组件的内容。这样，可以实现快速定位组件，避免繁琐的用户操作，有效提高用户体验。
需要说明的是，上述组件管理界面可以是历史任务界面，也可以是其他用户界面，例如负一屏、通知栏下拉界面等等。例如，终端设备100显示应用1，接收用户输入的至少一个触摸手势，打开负一屏或者通知栏下拉界面。应理解，后续实施例主要以历史任务界面为例进行说明，但并不代表对上述组件管理界面的限定。
在一些实施例中，为便于各应用的组件管理，仅对各应用(例如应用1)的组件管理白名单中的组件进行组件管理(例如组件定位)，上述组件管理白名单可以是终端设备100默认设置的，也可以是各应用默认设置的，还可以是用户设置的，此处不作具体限定。后续实施例将具体介绍用户如何设置组件管理白名单，此处不再赘述。
下面结合附图，对本申请实施例提供的界面显示方法进行介绍。
示例的，图7A是本申请实施例提供的一种可以实现组件定位功能的历史任务界面21。
如图7A所示，历史任务界面21还包括各应用的应用标识对应的拓展控件，例如协同办公应用的应用标识204对应的拓展控件501，即时通讯应用的应用标识205对应的拓展控件502。
在一些实施例中，以联系人应用为例，当一个应用中没有可进行组件定位的组件时，历史任务界面21可以不包括该应用的应用标识对应的拓展控件。
示例性的，以协同办公应用的拓展控件501为例进行说明。
如图7A和图7B所示，拓展控件501可以接收用户的输入操作(例如触摸操作)，响应于上述输入操作，终端设备100在协同办公应用的组件标签显示区503显示协同办公应用中可进行组件定位的组件的组件标签，例如组件标签601至组件标签604。参见图7B，各组件的组件标签以一行四列的排列形式进行展示。
本申请实施例对组件标签显示区503中各组件的组件标签的排列方式不做具体限定。示例性的，图7C和图7D是本申请实施例提供的另外两种排列方式。图7C中，各组件的组件标签以两行两列的排列形式进行展示；图7D中，各组件的组件标签以四行一列的排列形式进行展示。
本申请实施例对组件标签显示区503中各组件的组件标签的形状也不做具体限定。示例性的，图7B和图7C中组件标签示例性地展示为方形；图7D中组件标签示例性地展示为长方形。例如，在PC、折叠屏等场景中，组件通常展示为长方形，相应的，组件的组件标签也展示长方形。
可以理解，参考图7A至图7D，相比于直接显示所有应用中调用的组件的组件标签，通过应用的应用标识对应的拓展控件，触发终端设备100显示该应用中调用的组件的组件标签，可以保持页面整洁性。
在一些实施例中，协同办公应用当前包括可进行组件定位的M个组件，M为正整数。组件标签显示区503最多显示预设数量的组件的组件标签。当M超过预设数量时，用户可以通过作用于组件标签显示区503的滑动操作，查看更多组件的组件标签。
示例性的，上述预设数量为4，可进行组件定位的组件数量超过4；如图7E和图7F所示，检测到作用于组件标签显示区503的向上的滑动操作时，终端设备100在显示组件标签显示区503显示更多组件的组件标签，例如组件标签605至组件标签606。
在一些实施例中，终端设备100在组件标签显示区503显示组件的组件标签后，响应于针对拓展控件501的输入操作(例如触摸操作)，终端设备100可以停止在组件标签显示区503显示组件的组件标签。例如，用户点击图7B所示的拓展控件501后，终端设备100显示图7A所示的历史任务界面21。
在一些实施例中，如图7G和图7H所示，针对图示的两行多列的历史任务界面21，响应于针对第一行应用标识(即协同办公应用的应用标识)对应的拓展控件501的输入操作(例如触摸操作)，终端设备100显示的组件标签显示区503可以覆盖第二行应用标识(即即时通讯应用的应用标识)。
在一些实施例中，如图7G和图7I所示，针对图示的两行多列的历史任务界面21，响应于针对第一行应用标识(即协同办公应用的应用标识)对应的拓展控件501的输入操作(例如触摸操作)，终端设备100显示的组件标签显示区503可以将第二行应用标识(即即时通讯应用的应用标识)挤压至其他位置(例如，多任务队列中下一个应用的应用标识显示的位置)。
在一些实施例中，终端设备100调出的历史任务界面21可以直接显示各应用标识对应的 组件的组件标签。示例性的，以图7J所示的历史任务界面21为例，无需拓展控件，在历史任务界面21中的任一个应用的应用标识对应的组件标签显示区(例如组件标签显示区503)，可以直接显示该应用当前可进行组件定位的组件的组件标签。需要说明的是，一个应用(例如联系人应用)当前没有可进行组件定位的组件时，历史任务界面21不会显示该应用对应的组件的组件标签。
下面以协同办公应用为例，对该应用中当前可进行组件定位的M个组件进行介绍。
在一些实施例中，上述M个组件包括：协同办公应用的组件管理白名单1中所有组件。
在一些实施例中，上述M个组件包括：协同办公应用的最近一次运行期间，用户使用过的属于组件管理白名单1的组件。
在一些实施例中，上述M个组件包括：预设时长1内(例如一天)，用户使用过的属于组件管理白名单1的组件。
在一些实施例中，上述M个组件包括：预设时长2内(例如一个月)，用户使用过的属于组件管理白名单1的组件中使用频率最高的M个组件。
在一些实施例中，同一页面多次***的同一组件(例如组件1)，仅对该页面中用户最后使用的组件1进行组件定位。
下面对上述M个组件的排列顺序进行介绍。
在一些实施例中，上述M个组件的排列顺序是依据上述M个组件的最近一次使用时间和/或上述M个组件的使用频率确定的。可以理解，用户意图查看的组件为“最近使用的组件或使用率高的组件”的可能性更大；依据最近一次使用时间和/或使用频率进行排序，便于用户快速找到意图查看的组件。
在一种实现方式中，上述M个组件的排列顺序是上述M个组件的最近一次使用时间的倒序，即上述M个组件中最近使用的组件排在第一位。示例性的，参考图7B至图7D，组件标签601、组件标签602、组件标签603和组件标签604，分别对应组件1、组件2、组件3和组件4，这4个组件的最近一次使用时间的先后顺序为组件4、组件3、组件2和组件1。
在一种实现方式中，上述M个组件的排列顺序是上述M个组件的使用频率的正序，即使用频率最高的组件排在第一位。示例性的，参考图7B至图7D，组件标签601、组件标签602、组件标签603和组件标签604，分别对应组件1、组件2、组件3和组件4，这4个组件的使用频率的高低顺序为组件1、组件2、组件3和组件4。
在一种实现方式中，上述M个组件中的前m个组件为上述M个组件中最近使用的m个组件，排列顺序为上述m个组件的最近一次使用时间的倒序；上述M个组件中的后M-m个组件的排列顺序为，上述M-m个组件的使用频率的正序。例如m为4。本申请实施例对上述M个组件的排列顺序不做具体限定。
需要说明的是，对于A类***型组件(例如投票组件308、音乐播放组件310、Excel组件403、word组件407)，组件的最近一次使用时间可以指最后一次响应用户的有效操作的时间或退出编辑状态的时间。对于B类页面组件(例如朋友圈页面14)，组件的最近一次使用时间可以指将朋友圈页面切换为其他页面(例如，返回发现页面13、退出至主界面11、切换至其他应用程序的用户界面)的时间。
下面以组件1为例，对组件的组件标签的显示内容进行介绍。
本申请实施例中，组件1的组件标签可以包括组件1的组件标识；还可以包括以下一个或多个：组件1所在页面的页面标识(如果组件1是***型组件)、与组件1关联的应用2的 应用标识、组件1所在工作区的工作区标识。其中，组件标识包括以下一或多个：组件名称、组件快照和组件类型对应的组件图标中的一或多个；页面标识包括页面图标和/或页面名称；应用标识包括应用图标和/或应用名称；工作区标识包括工作区图标和/或工作区名称。下面进行分别说明。
组件标识包括：
组件名称：示例性的，朋友圈页面14的组件名称可以为“朋友圈”，投票组件308的组件名称可以为该组件的投票标题“旅游投票”，音乐播放组件310的组件名称可以是该组件播放的歌曲名称“AAA”，Excel组件403的组件名称可以是该组件显示的Excel表格的文件名“项目进度表”，Word组件407的组件名称可以是该组件显示的Word文档的文件名“成果说明”。在一种实现方式中，组件的组件名称还可以是组件对应的组件类型，音乐播放组件310的组件类型就是音乐播放组件，投票组件308的组件类型就是投票组件。本申请实施例对各类型组件的组件名称不做具体限定。
组件快照：终端设备100确定用户停止使用一个组件时，截取该组件的最后显示内容作为该组件的组件快照，并存储上述组件快照。可以理解，用户每次使用一个组件后，终端设备100可以更新该组件的组件快照。在一种实现方式中，终端设备100最后一次响应用户对组件1的有效操作后，若预设时长3内组件1未再接收到用户的有效操作，则终端设备100确定用户停止使用组件1。在一些实施例中，参考图7A至图7D，组件标签可以有多种形状，为适应组件标签的形状，终端设备100可以截取组件的快照中的预设形状的图像作为该组件的组件快照，上述预设形状是基于组件标签的形状确定的。
组件图标：当组件没有特定的组件图标时，可以取提供该组件的应用的应用图标作为组件图标；组件图标和应用图标可以相同，也可以不同。示例性的，朋友圈页面14的组件图标可以为图3D所示的朋友圈图标305A，投票组件308的组件图标可以为图4D所示的投票图标307A，音乐播放组件310的组件图标可以为图4D所示的音乐图标307B，Excel组件403的组件图标可以是Excel应用的应用图标，Word组件407的组件图标可以是Word应用的应用图标。本申请实施例对各类型组件的组件图标不做具体限定。
页面标识包括：
页面名称：示例性的，即时通讯应用中，朋友圈页面14的页面名称可以为“朋友圈”，群聊1的聊天页面15的页面名称可以为群聊名称(例如群聊1)，指定联系人的聊天页面的页面名称可以为上述联系人的昵称或备注。协同办公应用中，以ZZ1页面为例，ZZ1页面的页面名称可以为“ZZ1”。
页面图标：示例性的，即时通讯应用中，朋友圈页面14的页面图标可以为图3D所示的朋友圈图标305A，群聊1的聊天页面15的页面图标可以为图3B所示的群聊头像301A，指定联系人的聊天页面的页面图标可以为上述联系人的头像。协同办公应用中，以ZZ1页面为例，ZZ1页面的页面图标可以为图6B所示的页面图标402A。可以理解，页面组件(例如朋友圈页面14)的组件图标和页面图标可以相同。
需要说明的是，通过组件标签中的页面标识(例如页面名称、页面图标)，可以区分不同页面中***的同一组件；同一页面***多个不同组件时，上述多个不同组件对应的页面标识相同。
工作区名称：示例性的，协同办公应用中，以XX3项目，XX3项目的工作区名称可以为图6A所示的项目名称401，即“XX3”。本申请实施例对工作区名称不做具体限定。
需要说明的是，通过组件标签中的工作区标识(例如工作区名称)，可以区分不同工作区中***的同一组件；同一工作区***多个不同组件时，上述多个不同组件对应的工作区标识相同。
在一些实施例中，组件的组件标签包括图标和/或名称，例如，上述图标包括组件图标、组件快照、所在页面的页面图标、提供组件的应用的应用图标或所在工作区的工作区图标的至少一种，上述名称可以包括组件名称、所在页面的页面名称、提供组件的应用的应用名称或所在工作区的工作区名称的至少一种。
示例性的，参考图8，用户退出协同办公应用前先后编辑了页面ZZ2的Word组件407和页面ZZ1的Excel组件403；图8所示的历史任务界面21包括Excel组件403的组件标签601和Word组件407的组件标签602。参考图9，用户退出即时通讯应用前，先后在群聊1的聊天页面15中使用了音乐播放组件310和浏览了朋友圈页面14；图9所示的历史任务界面21包括朋友圈页面14的组件标签611和音乐播放组件310的组件标签612。
在一种实现方式中，组件的组件标签包括组件图标和该组件所在的页面的页面名称。
参考图8的(a)，Excel组件403的组件标签601包括Excel组件403的组件图标601A，以及所在的ZZ1页面的页面名称“ZZ1”。Word组件407的组件标签601包括Word组件407的组件图标602A，以及所在的ZZ2页面的页面名称“ZZ2”。该示例中，Excel组件的组件图标和Excel应用的应用图标相同，这仅仅是一个示例，不应对本申请实施例构成限定，Excel组件的组件图标和Excel应用的应用图标也可以不相同；同理，Word组件的组件图标也是如此。
参考图9的(a)，朋友圈页面14的组件标签611包括组件图标611A和页面名称“朋友圈”。音乐播放组件310的组件标签612包括组件图标612A和页面名称“群聊1”。该示例中音乐播放组件和朋友圈页面组件有特定的组件图标。
可以理解，若组件(例如朋友圈页面14)为页面组件，则组件所在的页面即为组件本身；若组件(例如Excel组件403)为***到页面1内的组件，则组件所在的页面即为页面1。
在一种实现方式中，组件的组件标签包括组件快照和该组件所在的页面的页面名称。
示例性的，用户退出协同办公应用前还将Excel组件403***ZZ3页面，并编辑了ZZ3页面的Excel组件403，图8所示的历史任务界面21还包括ZZ3页面的Excel组件403的组件标签603。
参考图8的(b)，ZZ1页面的Excel组件403的组件标签601中的组件快照601B和ZZ3页面的Excel组件403的组件标签603中的组件快照603B相同，组件标签601包括页面名称“ZZ1”，组件标签603包括页面名称“ZZ3”。可以理解，不同页面的同一Excel组件可以保持同步，组件快照相同；用户通过页面名称可以区分在不同页面中使用的同一Excel组件，页面名称便于用户快速定位到目标页面中的特定组件。
在一种实现方式中，组件的组件标签包括组件图标和该组件所在工作区的工作区名称。
在一种实现方式中，组件的组件标签包括组件图标和组件名称。
示例性的，用户退出协同办公应用前还编辑了ZZ2页面的Excel组件406，图8所示的历史任务界面21还包括Excel组件406的组件标签604。
参考图8的(c)，Excel组件403的组件标签601和Excel组件406的组件标签604中的组件图标相同，组件标签601包括组件名称“项目进度表”，组件标签604包括组件名称“项目成果表”。可以理解，同一类型的组件的组件图标相同，通过组件名称可以区分两个相同类型 的组件。
参考图9的(b)，朋友圈页面14的组件标签611包括组件名称“朋友圈”。音乐播放组件310的组件标签612包括组件名称“AAA”(即歌曲名称)。
在一种实现方式中，组件的组件标签包括组件快照和组件名称。
在一种实现方式中，组件的组件标签包括该组件所在页面的页面图标和组件名称。
参考图8的(d)，ZZ1页面的Excel组件403的组件标签601和ZZ3页面的Excel组件403的组件标签603包括相同的组件名称“项目进度表”，组件标签601包括ZZ1页面的页面图标601C，组件标签603包括ZZ3页面的页面图标603C。可以理解，不同页面的同一Excel组件的组件名称相同；用户通过页面图标可以区分在不同页面中使用的同一Excel组件，页面图标也便于用户快速定位到目标页面中的特定组件。
参考图9的(c)，朋友圈页面14的组件标签611包括朋友圈页面的页面图标611B；音乐播放组件310的组件标签612包括聊天页面15的页面图标612B。
在一种实现方式中，组件的组件标签包括提供该组件的应用的应用图标和组件名称。
示例性的，参考图8的(e)，Excel组件403的组件标签601包括Excel应用的应用图标601D，Word组件407的组件标签602包括Word应用的应用图标602D。
参考图9的(d)，朋友圈页面14的组件标签611包括即时通讯应用的应用图标611C。音乐播放组件310的组件标签612包括音乐应用的应用图标612C。
在一些实施例中，针对在应用1中使用的组件1，通过作用于组件1的组件标签的预设操作1，可以快速定位组件1在应用1中的位置，或者在应用1中展示该组件。在一些实施例中，通过作用于上述组件标签的预设操作2，可以调用与应用1中的组件1关联的应用2，在应用2中展示与该组件的内容相关联的用户界面(例如，图5F相关描述中的第二内容页面)；或者，通过作用于上述组件标签的预设操作2，可以在应用1中打开组件1的用户界面(例如，图5E相关描述中的第一内容页面)，该用户界面的显示内容与组件1的内容相关联。这样，退出上述用户界面时，可以直接返回应用1，无需打开应用2，避免了应用之间的跳转。
可以理解，用户在应用1中打开组件1的用户界面时，该用户界面通常仅能提供应用2的部分功能；用户意图体验应用2的更多功能时，可以通过该组件调用应用2，在应用2中显示的用户界面上编辑上述组件的相关内容。
需要说明的是，若组件1是本应用提供的组件，即组件1没有关联的应用2，则终端设备100可以不响应针对组件1的组件标签的预设操作2。
下面结合图10A至图10I对上述预设操作1和预设操作2如何开启页面进行示例性说明。
在一些实施例中，预设操作1为作用于组件1的组件标签的左滑操作，预设操作2为作用于组件1的组件标签的右滑操作。示例性，以图10A所示的Excel组件403的组件标签601为例。Excel组件403用于显示“项目进度表”。
如图10A和图10B所示，组件标签601可以接收左滑操作，响应于上述左滑操作，终端设备100定位Excel组件403的位置在协同包公应用的ZZ1页面中，显示图10B所示的协同办公应用的用户界面18，图10B所示的用户界面18包括ZZ1页面，ZZ1页面包括Excel组件403。
如图10C和图10D所示，组件标签601可以接收右滑操作，响应于上述右滑操作，终端设备100调用Excel应用打开Excel组件403显示的Excel表格，显示图10D所示的Excel应用的用户界面19，用户界面19用于显示“项目进度表”。
在一些实施例中，检测到用户作用于组件1的组件标签的触摸操作时，显示应用1的应用标识和应用2的应用标识；预设操作1包括从组件1的组件标签至应用1的应用标识的滑动操作；预设操作2包括从组件1的组件标签至应用2的应用标识的滑动操作。示例性，以图10E所示的Excel组件403的组件标签601为例。
如图10E和图10F(或图10G)所示，组件标签601可以接收用户的触摸操作，响应于上述触摸操作，终端设备100显示协同办公应用的应用标识621和Excel应用的应用标识622。
如图10E和图10F所示，组件标签601可以接收用户从组件标签601至应用标识621的滑动操作，响应于上述滑动操作，终端设备100定位Excel组件403的位置，显示图10B所示的协同办公应用的用户界面18。如图10E和图10G所示，组件标签601可以接收用户从组件标签601至应用标识622的滑动操作，响应于上述滑动操作，终端设备100调用Excel应用，显示图10D所示的Excel应用的用户界面19。
在一些实施例中，检测到用户作用于组件1的组件标签的长按操作时，显示应用1的应用标识和应用2的应用标识；预设操作1包括长按组件1的组件标签后将组件标签拖曳至应用1的应用标识的滑动操作；预设操作2包括长按组件1的组件标签后将组件标签拖曳至应用1的应用标识的滑动操作。
可以理解，拖曳组件标签指组件标签跟随用户手指的滑动操作的滑动轨迹移动。
在一些实施例中，不限于应用1和应用2的应用标识，检测到上述作用于组件1的组件标签的长按操作时，终端设备100还可以显示可以使用组件1的其他应用(例如应用3)的应用标识。检测到作用于应用3的应用标识的预设操作时(例如将组件标签拖曳至应用3的应用标识的滑动操作)时，将组件1分享至应用3。
在一些实施例中，历史任务界面还包括来源定位控件和页面定位控件；预设操作1包括从组件1的组件标签至页面定位控件的滑动操作；预设操作2包括从组件1的组件标签至来源定位控件的滑动操作。示例性，以图10H所示的Excel组件403的组件标签601为例。
如图10H和图10I所示，历史任务界面还包括页面定位控件631和来源定位控件632。
如图10H所示，组件标签601可以接收用户从组件标签601至页面定位控件631的滑动操作，响应于上述滑动操作，终端设备100定位Excel组件403的位置，显示图10B所示的协同办公应用的用户界面18。如图10I所示，组件标签601可以接收用户从组件标签601至来源定位控件632的滑动操作，响应于上述滑动操作，终端设备100调用Excel应用，显示图10D所示的Excel应用的用户界面19。
在一些实施例中，若组件1是本应用提供的组件，终端设备100不响应对来源定位控件的预设操作2。在一种实现方式中，检测到作用于组件1的组件标签的触摸操作时，终端设备100可以将来源定位控件进行灰度显示，以指示来源定位控件不可用。示例性，以图11A所示的朋友圈页面14的组件标签611为例。
如图11A和图11B所示，检测到作用于组件标签611的触摸操作时，终端设备100可以将来源定位控件632进行灰度显示，以指示来源定位控件632不可用，即朋友圈页面14没有关联的其他应用。如图11C和图11D所示，组件标签611可以接收用户从组件标签611至来源定位控件632的滑动操作，响应于上述滑动操作，终端设备100定位朋友圈页面14的位置，在即时通讯应用中显示朋友圈页面14。
在一些实施例中，预设操作1包括长按组件1的组件标签后将组件标签拖曳至页面定位控件的滑动操作；预设操作2包括长按组件1的组件标签后将组件标签拖曳至应用1的来源 定位控件的滑动操作。
在一些实施例中，预设操作1包括作用于组件1的组件标签的点击操作；预设操作2包括包括作用于组件1的组件标签的长按操作。
在一些实施例中，预设操作1包括作用于组件1的组件标签的点击操作；预设操作2包括包括长按组件1的组件标签后将组件标签拖曳至预设区域的滑动操作。在一种实现方式中，上述预设区域显示有应用2的应用标识和/或提示信息，提示信息用于提示用户将组件1的组件标签拖曳至预设区域，可以触发应用2打开组件1。在一种实现方式中，检测到用户的长按操作时，终端设备100在预设区域显示应用2的应用标识和/或提示信息。
示例性的，以图11E所示的音乐播放组件310的组件标签612为例。
如图11E和图11F所示，检测到作用于组件标签612的长按操作，响应于上述长按操作，终端设备100在预设区域641(例如显示屏的中心区域)显示提示信息641A和音乐应用的标识641B。如图11G和图11H所示，检测到将组件标签601拖曳至预设区域641的滑动操作，响应于上述滑动操作，终端设备100调用音乐应用，显示音乐播放组件310播放的歌曲的原始播放界面17。
不限于图10A至图11F说明的预设操作1和预设操作2，预设操作1和预设操作2还可以是其他操作，此处不作具体限定。
下面对终端设备100如何定位组件的位置进行示例性说明。
在一些实施例中，用户使用应用1的组件1，组件1所在页面为页面1，确定用户退出组件1时，终端设备100将页面1对应的应用程序窗口加入组件定位的任务队列1，任务队列1中页面1的任务信息包括页面1的页面标识和页面数据，组件1的组件标识和组件1在页面1中的显示位置。终端设备100检测到作用于组件1的组件标签的预设操作1时，基于组件1所在的页面1的页面标识，获取任务队列1中页面1的任务信息；基于页面1的任务信息中的页面数据，组件1的组件标识和显示位置，运行页面1，显示包括组件1的页面1。
例如，应用1(例如协同办公应用)的组件1(例如Excel组件)为A类***型组件时，用户在页面1(例如ZZ1页面)使用组件1，组件1所在的页面为ZZ1页面。例如，应用1(例如即时通讯应用)的组件1(例如朋友圈页面)为B类页面组件，组件1本身即为组件1所在页面。
本申请实施例中，可以分别针对每个应用分别建立一个组件定位的任务队列，也可以针对所有应用建立一个组件定位的总任务队列，此处不做具体限定。
需要说明的是，受限于终端设备100的显示屏的尺寸，对于部分页面，终端设备100只能显示该页面的部分内容，需要用户通过上滑、下滑、左滑或右滑操作，才能查看该页面的全部内容；本申请实施例将这类不能完全显示的页面简称为长页面，将可以完全显示的页面称为非长页面。示例性的，图10B所示的ZZ1页面18、图11D所示的朋友圈页面14，图4G和图5D所示的聊天页面15均为长页面。
在一种实现方式中，若页面1为非长页面，页面1的任务信息可以不包括组件1在页面1中的显示位置；终端设备100检测到作用于组件1的组件标签的预设操作1时，基于组件1所在的页面1的页面标识，获取任务队列1中页面1的任务信息；基于页面1的页面数据，运行页面1，显示完整的页面1，页面1包括组件1。
在一种实现方式中，页面1是可以上下滑动的长页面，组件1(例如Excel组件)为A类***型组件。页面1可显示的总高度为H，终端设备100的显示屏可以显示的页面1的高 度为h，h小于H；用户退出组件1时，页面1中组件1在显示屏的显示位置为x至x+s，s为组件1的显示高度，任务队列1中页面1的任务信息还记录组件1的显示位置为x。终端设备100检测到作用于组件1的组件标签的预设操作1时，可以基于页面1的页面数据以及组件1的显示高度x，显示页面1中包含组件1的部分页面。组件1可以位于上述部分页面的指定位置，例如顶部，中部或底部，此处不作具体限定。或者，页面1的内容包括第一部分和第二部分，第一部分显示的内容不包括组件1；用户可以滑动页面1，使得显示屏显示页面1中包含组件1的第二部分；用户退出组件1时，显示屏显示的是页面1中不包含组件1的第一部分。终端设备100检测到作用于组件1的组件标签的预设操作1时，可以显示页面1中包含组件1的第一部分。
在一种实现方式中，若页面1是可以上下滑动的长页面，组件1(例如朋友圈页面)为B类页面组件。页面1可显示的总高度为H，终端设备100的显示屏可以显示的页面1的高度为h，h小于H；用户退出组件1时，页面1显示高度y至y+h的部分页面，任务队列1中页面1的任务信息还记录组件1的显示位置为y。终端设备100检测到作用于组件1的组件标签的预设操作1时，可以基于页面1的页面数据以及组件1的显示高度y，显示页面1的上述部分页面。
除了用于实现组件定位，组件1的组件标签还可以实现其他功能，下面对组件1能提供的其他功能进行示例性介绍。
在一些实施例中，通过组件1的组件标签可以预览组件1的组件快照。
示例性的，如图12A和图12B所示，历史任务界面21中Excel组件403的组件标签601可以接收用户的输入操作(例如双击操作)，响应于上述输入操作，终端设备100可以在历史任务界面21上显示Excel组件403的放大版的组件快照。
在一些实施例中，通过组件1的组件标签可以在应用1的本次运行期间将组件1从组件管理白名单中移除，和/或将组件1从组件管理白名单中彻底移除。
示例性的，如图12C和图12D所示，历史任务界面21中朋友圈页面14的组件标签611可以接收用户的输入操作(例如上滑操作)，响应于上述输入操作，终端设备100可以在即时通讯应用的本次运行期间将朋友圈页面从组件管理白名单中移除，停止显示组件标签611，并将排在朋友圈页面14之后的组件的组件标签向前顺移一位。如图12D所示，组件标签612的显示位置移动至组件标签611的原显示位置；组件标签613的显示位置移动至组件标签612的原显示位置。
在一些实施例中，通过组件1的组件标签可以将组件1分享给可以使用组件1的其他应用(例如应用3)，或本应用中的联系人。
示例性的，如图12E和图12F所示，历史任务界面21中Excel组件403的组件标签601可以接收用户的分享操作(例如下滑操作)，响应于上述分享操作，终端设备100可以显示本应用(即协同办公应用)中的联系人(例如可以协同办公的同事)的用户标识(例如联系人Lily的用户标识651)，可以使用组件1的其他应用的应用标识(例如即时通讯应用的应用标识652)，可以使用组件1的其他应用的指定页面的页面标识(例如即时通讯应用的朋友圈页面的页面标识653)。
用户标识651可以接收用户的输入操作(例如触摸操作)，响应于上述输入操作，终端设备100可以将组件1发送给联系人Lily的终端设备，联系人Lily的终端设备可以在协同办公应用中显示组件1。
示例性的，图12F至图12I示出了通过即时通讯应用的应用标识652分享组件1的用户界面图。
如图12F和图12G所示，应用标识652可以接收用户的输入操作(例如触摸操作)，响应于上述输入操作，终端设备100可以显示即时通讯应用的联系人选择界面22。联系人选择界面22包括即时通讯应用中的多个联系人的用户标识，例如联系人“Anna”的用户标识654。
如图12G和图12H所示，响应于针对用户标识654的输入操作(例如触摸操作)，终端设备100可以显示联系人“Anna”的Excel组件403的分享框655，分享框655包括Excel组件403的组件标签655A(例如图12G所示的组件快照)，以及分享控件655B。
如图12H和图12I所示，响应于针对分享控件655B的输入操作(例如触摸操作)，终端设备100将组件1分享给即时通讯应用的联系人“Anna”，在即时通讯应用中显示用户“Anna”的聊天页面23，在聊天页面23显示本设备的用户发送的Excel组件403。
示例性的，图12F至图12I示出了通过朋友圈的页面标识653分享组件1的用户界面图。
如图12J所示，响应于针对页面标识653的输入操作(例如触摸操作)，终端设备100可以显示朋友圈的编辑界面24，编辑界面24包括朋友圈附件的标识(即Excel组件403的组件标识656)，以及朋友圈的发表控件657。
如图12I和图12J所示，响应于针对发表控件657的输入操作(例如触摸操作)，终端设备100在朋友圈页面14显示最新发表的朋友圈，该朋友圈包括Excel组件403。
下面对用户如何设置组件管理白名单进行示例性说明。
示例性的，图13A至图13D示出了通过***设置管理组件管理白名单的相关用户界面图。
图2A所示的设置图标202C可以接收用户的输入操作(例如触摸操作)，响应于上述输入操作，终端设备100可以显示图13A所示的***设置界面31，***设置界面31包括组件管理设置条目701。
如图13A和图13B所示，响应于针对组件管理设置条目701的输入操作(例如触摸操作)，终端设备100可以显示组件管理设置界面32，管理设置界面32包括组件管理的开关控件702和应用管理条目703。其中，开关控件702处于打开(ON)状态时，开启组件管理(例如组件定位)的服务；开关控件702处于关闭(OFF)状态时，关闭组件管理的服务。用户可以通过输入操作(例如触摸操作)切换开关控件702的状态。
如图13B和图13C所示，响应于针对应用管理条目703的输入操作(例如触摸操作)，终端设备100显示用户界面33，用户界面33包括可提供组件的至少一个应用的设置条目，例如即时通讯应用的设置条目704。
如图13C和图13D所示，响应于针对设置条目704的输入操作(例如触摸操作)，终端设备100显示即时通讯应用的组件设置界面34，组件设置界面34包括即时通讯应用提供的至少一个页面组件的开关控件(例如朋友圈页面的开关控件705)，以及至少一个***型组件的开关控件(例如投票组件的开关控件706)。组件的开关控件处于打开(ON)状态时，该组件被加入组件管理白名单；组件的开关控件处于关闭(OFF)状态时，该组件未被加入组件管理白名单。用户可以通过输入操作(例如触摸操作)切换组件的开关控件的状态。
图13A至图13D是本申请实施例提供的示例性的设置方式，本申请实施例中，也可以在各应用中加入组件管理白名单的设置入口，此处不做具体限定。可以理解，通过用户设置组件管理白名单，可以基于各用户的需求，提供个性化的组件定位体验。
图7A至图12D所示的组件管理界面的显示方式(即在组件管理界面显示使用组件的应 用的应用标识)，是以使用组件的应用为维度进行组件管理；不限于上述显示方式(或者显示维度)，本申请实施例还能以其他显示方式(或者显示维度)进行组件管理。
下面对本申请实施例涉及的多种显示方式(或者显示维度)进行说明。
方式一：显示使用组件的应用的应用标识。
示例性的，图7A至图9以组件管理界面是历史任务界面21为例，以使用组件的应用为维度，对终端设备100中当前可进行组件定位的组件进行管理，并对各应用(例如协同办公应用)使用的组件的组件标签进行了详细介绍。以协同办公应用为例，历史任务界面21可以包括协同办公应用的应用标识，该应用标识对应的组件标签显示区包括协同办公应用中使用的当前可进行组件定位的组件的组件标签，应用标识包括应用图标、应用名称和界面快照。
示例性的，图14A示出了另一种以使用组件的应用为维度的组件管理界面41，不同于历史任务界面21的是，组件管理界面41中各应用的应用标识可以不包括应用的界面快照。类似于图7A和图7B，图14A所示的组件管理界面41包括各应用的应用标识对应的拓展控件。在一种实现方式中，组件管理界面41也可以不包括拓展控件，可以通过作用于应用的应用标识的预设操作3(例如触摸操作)，调出该应用中使用的当前可进行组件定位的组件的组件标签。
示例性的，类似于图7J，图14B示出了另一种组件管理界面41，组件管理界面41可以直接在各应用的应用标识对应的组件标签显示区显示该应用使用的组件的组件标签，无需拓展控件。
相比于图7A，图14A和图14B所示的组件管理界面41不包括联系人应用的应用标识，图14A和图14B中显示的应用当前包括至少一个可进行组件定位的组件。
方式一中，查看组件标签、组件的排序、组件标签的显示内容、组件标签的功能等可以参考前述图7A至图12D的相关描述，此处不再赘述。
方式二：显示使用组件的应用的应用标识和组件所在页面的页面标识。
方式二在方式一的基础上，对应用1(例如协同办公应用)使用的当前可进行组件定位的M个组件，以所在页面为维度再次进行划分，所述M个组件在应用1的W个页面中，W为正整数。示例性的，以组件管理界面是图15A所示的历史任务界面21为例。
如图15A和图15B所示，响应于针对协同办公应用的拓展控件502的输入操作(例如触摸操作)，终端设备100在协同办公应用的组件标签显示区，显示上述W个页面的页面标识(例如页面图标和/或页面名称)，例如ZZ1页面的页面标识、ZZ2页面的页面标识801、ZZ3页面的页面标识。如图15B和图15C所示，页面标识801可以接收用户的输入操作(例如触摸操作)，响应于上述输入操作，终端设备100在协同办公应用的组件标签显示区，显示ZZ2页面中使用的组件的组件标签，例如，Excel组件406的组件标签802，组件标签802包括Excel组件406的组件标识(例如组件图标、组件快照和/或组件名称)。
在一些实施例中，上述W个页面的排列顺序，可以是依据上述W个页面中使用的组件的最近一次使用时间、上述W个页面中使用的组件的使用频率和上述W个页面的退出时间中的一或多个确定的。在一种实现方式中，确定每个页面中组件的最近使用时间，上述W个页面的排列顺序是上述W个页面中的组件的最近使用时间的倒序，即上述W个页面中最近使用组件的页面排在第一位。在一种实现方式中，确定每个页面使用的组件的最高使用频率，上述W个页面的排列顺序是上述W个页面对应的最高使用频率的正序，即组件的使用频率最高的页面排在第一位。在一种实现方式中，上述W个页面的排列顺序是上述W个页面的 退出时间的倒序，即上述W个页面中最近退出的页面排在第一位。
在一些实施例中，以Excel组件406的组件标签802为例，如图15C所示，前述组件定位的预设操作1可以为从Excel组件406的页面标识801至组件标签802的滑动操作；如图15D所示，前述组件定位的预设操作2可以为作用于组件标签802的单击操作。
在一些实施例中，组件管理界面可以不包括拓展控件，可以通过作用于协同办公应用的应用标识的预设操作3调出上述W个页面的页面标识。
在一些实施例中，方式二中，若一个页面中仅有一个可进行组件定位的组件，则可以用该组件的组件标签替代该页面的页面标识；无需用户通过点击页面标识获取该页面对应的唯一组件的组件标签，节省用户操作。
在一些实施例中，类似于图7J，组件管理界面可以不包括拓展控件，组件管理界面可以直接显示上述W个页面的页面标识。
在一些实施例中，组件标签显示区最多显示预设数量(例如4)的页面标识，N超过预设数量时，用户可以通过左滑操作或右滑操作，查看更多页面标识。类似的，组件标签也是如此，具体的，可以参考图7E和图7F的相关描述，此处不再赘述。
方式二中组件标签的功能可以参考方式一中组件标签的功能，此处不再赘述。
方式三：显示使用组件的应用的应用标识，和提供组件的应用的应用标识。
方式三在方式一的基础上，对应用1(例如协同办公应用)使用的可进行组件定位的M个组件，以提供组件的应用为维度再次进行划分，所述M个组件由F个应用提供，F为正整数。示例性的，以组件管理界面是图15A所示的历史任务界面21为例。
如图15A和图16A所示，响应于针对协同办公应用的拓展控件502的输入操作(例如触摸操作)，终端设备100在协同办公应用的组件标签显示区，显示上述F个应用的应用标识(例如应用图标和/或应用名称)，例如Excel应用的应用标识803、Word应用的应用标识、即时通讯应用的应用标识。如图16A和图16B所示，应用标识803可以接收用户的输入操作(例如触摸操作)，响应于上述输入操作，终端设备100在上述组件标签显示区显示Excel应用提供的可进行组件定位的组件的组件标签，例如，Excel组件403的组件标签804。
在一些实施例中，上述F个应用的排列顺序，可以是依据上述F个应用提供的组件的最近一次使用时间、上述F个应用提供的组件的使用频率和上述F个应用的退出时间中的一或多个确定的。在一种实现方式中，确定每个应用提供的组件的最近使用时间，上述F个应用的排列顺序是上述F个应用提供的组件的最近使用时间的倒序，即提供最近使用的组件的应用排在第一位。在一种实现方式中，确定每个应用对应的最高使用频率为该应用提供的组件的最高使用频率，上述F个应用的排列顺序是上述F个应用对应的最高使用频率的正序，即提供最高使用频率的组件的应用排在第一位。在一种实现方式中，上述F个应用的排列顺序是上述F个应用的退出时间的倒序，即上述F个应用中最近退出的应用排在第一位。
在一些实施例中，组件管理界面可以不包括拓展控件，通过作用于协同办公应用的应用标识的预设操作3，可以在协同办公应用的组件标签显示区调出上述F个应用的应用标识。
在一些实施例中，方式三中，若一个应用中仅提供了一个可进行组件定位的组件，则可以用该组件的组件标签替代该应用的应用标识；无需用户通过点击应用标识获取该页面对应的唯一组件的组件标签，节省用户操作。
在一些实施例中，类似于图7J，组件管理界面可以不包括拓展控件，组件管理界面可以直接显示上述F个应用的页面标识。
在一些实施例中，组件标签显示区最多显示预设数量(例如4)的应用标识，F超过预设数量时，用户可以通过左滑操作或右滑操作，查看更多应用标识。类似的，组件标签也是如此，具体的，可以参考图7E和图7F的相关描述，此处不再赘述。
方式三中组件标签的功能也可以参考方式一中组件标签的功能，此处不再赘述。
方式四：显示提供组件的应用的应用标识。
方式四中，以提供组件的应用为维度，对终端设备100中当前可进行组件定位的组件进行组件管理。终端设备100中当前可进行组件定位的组件由K个应用提供。
示例性的，图17A示出了一种以提供组件的应用为维度的组件管理界面41，组件管理界面41包括上述K个应用的应用标识，例如即时通讯应用的应用标识805。如图17A和图17B所示，应用标识805可以接收用户的输入操作(例如触摸操作)，响应于上述输入操作，在应用标识805对应的组件标签显示区显示即时通讯应用提供的组件的组件标签，例如，朋友圈页面14的组件标签806、音乐播放组件的组件标签807。需要说明的是，图17A只能显示K个应用中的部分应用的应用标识时，用户可以通过滑动操作(例如下滑操作)，查看更多应用标识。
示例性的，类似于图7J，图17C示出了另一种组件管理界面41，组件管理界面41可以直接显示各应用提供的可进行组件定位的组件的组件标签。
在一些实施例中，上述K个应用的排列顺序，可以是依据上述K个应用提供的组件的最近一次使用时间、上述K个应用提供的组件的使用频率和上述K个应用的退出时间中的一或多个确定的。
在一些实施例中，组件标签显示区最多显示预设数量(例如4)的组件标签，组件数量超过预设数量时，用户可以通过滑动操作(例如左滑操作)，查看更多组件的组件标签。具体的，可以参考图7E和图7F的相关描述，此处不再赘述。
方式四中组件标签的显示内容和功能等可以参考方式一中的相关描述，此处不再赘述。
在一些实施例中，当小于2个应用提供组件时(即K小于2)时，不以方式四进行组件管理。
在一些实施例中，以提供组件的应用为维度，叠加以使用组件的应用为维度；具体的可以参考方式三，此处不再赘述。
方式五：显示使用组件的用户的用户标识
本申请实施例中，部分组件(例如协同办公应用中Excel组件)可以由多个用户共同使用。方式五中，对终端设备100中当前可进行组件定位的组件，以使用过组件的用户为维度进行组件管理。终端设备100中当前可进行组件定位的组件由D个用户使用过。
示例性的，图18示出了一种以提供组件的应用为维度的组件管理界面41，组件管理界面41包括上述D个用户的用户标识(例如用户头像和/或用户名称)，例如用户“Leo”的用户标识808，各用户的用户标识对应的组件标签显示区显示有该用户使用的组件的组件标签。例如用户“Leo”的组件标签显示区包括：投票组件308的组件标签809和Excel组件403的组件标签810。需要说明的是，图18只能显示上述D个用户中的部分用户的用户标识时，用户可以通过滑动操作(例如下滑操作)，查看更多用户标识。
在一些实施例中，上述D个用户的排列顺序，可以是依据上述D个用户最近使用组件的时间，和/或上述D个用户使用组件的使用频率确定的。在一种实现方式中，确定每个用户最近使用组件的时间，上述D个用户的排列顺序是上述D个用户最近使用组件的时间的倒序， 即最近使用组件的用户排在第一位。在一种实现方式中，上述D个用户的排列顺序是上述D个用户的组件使用频率的正序，即最高使用频率的用户排在第一位。
在一些实施例中，组件标签显示区最多显示预设数量(例如3)的组件标签，组件数量超过预设数量时，用户可以通过滑动操作(例如左滑操作)，查看更多组件的组件标签。具体的，可以参考图7E和图7F的相关描述，此处不再赘述。
方式五中组件标签的显示内容和功能等可以参考方式一中的相关描述，此处不再赘述。
在一些实施例中，当小于2个用户使用组件时(即D小于2)时，不以方式五进行组件管理。
方式六：显示使用组件的设备的设备标识。
在一些实施例，用户的H个设备(例如手机、平板、电脑等)进行了协同连接，用户可以在终端设备100中以设备为维度对在上述H个设备中使用的组件进行组件管理，终端设备100可以是上述H个设备中的一个设备；H为正整数。本申请实施例中，上述H个设备可以通过登录同一账号、连接同一局域网等方式建立协同连接，此处不做具体限定。
示例性的，图19A示出了一种以使用组件的设备为维度的组件管理界面41，组件管理界面41包括上述H个设备的设备标识(例如设备图标和/或设备名称)，例如XX手机的设备标识811，各设备的设备标识对应的组件标签显示区显示有该设备使用的组件的组件标签。例如XX手机的组件标签显示区包括：投票组件308的组件标签809和Excel组件403的组件标签810。需要说明的是，图19A只能显示上述H个设备中的部分设备的设备标识时，用户可以通过滑动操作(例如下滑操作)，查看更多设备标识。
在一些实施例中，上述H个设备的排列顺序，可以是依据上述H个设备最近使用组件的时间，和/或上述H个设备使用组件的使用频率确定的。
在一些实施例中，组件标签显示区最多显示预设数量(例如3)的组件标签，组件数量超过预设数量时，用户可以通过滑动操作(例如左滑操作)，查看更多组件的组件标签。具体的，可以参考图7E和图7F的相关描述，此处不再赘述。
方式六中组件标签的显示内容和功能等可以参考方式一中的相关描述，此处不再赘述。
在一些实施例中，当小于2个协同连接的设备使用组件时(即H小于2)时，不以方式六进行组件管理。
在一些实施例中，上述多个设备建立协同连接后，用户可以通过本设备使用组件1，也可以通过协同连接的其他设备使用组件1。在一种实现方式中，用户可以在本设备中选择将组件1流转到上述多个设备中的指定设备中打开。
在一些实施例中，将设备1使用的组件1的组件标签拖拽到设备2的设备标识上，可以实现组件流转的功能。示例性的，如图19A和图19B所示，终端设备100为XX手机，Excel组件403用于显示Excel表格“项目进度表”；检测到从Excel组件403的组件标签810至XX平板的设备标识812的滑动操作，响应于上述滑动操作，终端设备100向XX平板发送Excel组件403的相关数据，XX平板基于上述相关数据显示上述Excel表格。
具体的，在一种实现方式中，响应于上述滑动操作，终端设备100调用Excel应用显示上述Excel表格，并通过投屏通道向XX平板发送Excel应用的投屏数据；XX平板基于上述投屏数据显示上述Excel表格。在另一种实现方式中，响应于上述滑动操作，终端设备100向XX平板发送Excel组件403显示的Excel表格的表格数据；XX平板调用Excel应用基于上述表格数据显示上述Excel表格。
在一种实现方式中，若设备2(例如XX平板)安装有提供组件1(例如Excel组件403)的应用2(例如Excel应用)，则向设备2发送组件1的显示内容(例如表格数据)，设备2调用应用2显示上述显示内容；若设备2未安装应用2，则向设备2发送应用2的投屏数据，设备2基于投屏数据显示上述显示内容。
方式七：显示组件对应的事件的事件标识。
在一些实施例中，基于组件1的关键词或组件1的事件标签，将组件1归类为指定事件的组件，事件标签可以是手动标注的或自动标注的。方式七中，对终端设备100中当前可进行组件定位的组件，以组件对应的事件为维度进行组件管理。
方式八：显示组件所在的Widget的标识。
在一些实施例中，可以建立多个Widget，基于一个Widget对应的预设主题可以将多个组件添加到该Widget中。方式八中，对终端设备100中当前可进行组件定位的组件，以组件对应的Widget为维度进行组件管理。
以上八种显示方式(或者显示维度)只是一个示例，在一些实施例中，终端设备100固定地基于其中的一或多种显示方式进行组件管理；或者，根据多个因素选择其中的一或多种显示方式进行组件管理，本申请对此均不做限定。
在一些实施例中，可以对多种预设的显示方式进行切换。
在一种实现方式中，通过切换控件实现显示方式的切换。示例性的，如图20A，组件管理界面41当前的显示方式是上述方式一，即以使用组件的应用为维度，显示使用组件的应用的应用标识，组件管理界面41还包括切换控件814。
如图20A和图20B所示，切换控件814可以接收用户的输入操作(例如触摸操作)，响应于上述输入操作，显示切换框，切换框包括多种显示方式的选项，例如，上述方式一(即以使用组件的应用为维度)的选项815和上述方式六(即以提供组件的设备为维度)的选项816。
如图20B和图20C所示，响应于针对选项816的输入操作，切换显示方式为选项816，即以使用组件的设备为维度进行组件管理。
在一种实现方式中，直接通过各显示方式的选项实现显示方式的切换。如图20D所示，组件管理界面可以直接包括多种显示方式的选项，例如选项815和选项816，选项815处于选中状态，选项816处于未选中状态。如图20D和图20E所示，响应于针对选项816的输入操作，切换选项815的状态为未选中状态，切换选项816的状态为选中状态，即以使用组件的设备为维度进行组件管理。
可以理解，采用多种显示方式(或者显示维度)对用户展示组件，可以满足用户不同的组件展示和组件搜索需求，提高组件的使用便捷性。
本申请实施例提供了界面显示方法，应用于包括触控显示屏的终端设备100。图21示出了上述界面显示方法的流程示意图。其中，
S101、显示第一应用的第一页面，第一页面的内容包括有一个或多个组件，所述一个或多个组件包括第一组件。
本申请实施例中，第一组件可以为前述组件1。
可选的，第一组件可以是***到特定页面中的组件。可选的，第一组件也可以是第一应用的一个应用程序窗口对应的页面，即第一页面。可选的，第一组件可以是第一应用(例如前述应用1)提供的，也可以是其他应用(例如前述应用2)提供的。
示例性的，参考图3A至图3D的相关描述，第一应用的第一页面可以为即时通讯应用的朋友圈页面14，第一组件可以为该朋友圈页面。示例性的，参考图4A至图4G的相关描述，第一应用的第一页面可以为即时通讯应用的聊天页面15，第一组件可以为聊天页面15中***的投票组件308。示例性的，参考图5A至图5F的相关描述，第一应用的第一页面可以为即时通讯应用的聊天页面15，第一组件可以为聊天页面15中***的音乐播放组件310。
示例性的，参考图6A至图6C的相关描述，第一应用的第一页面可以为协同办公应用的ZZ1页面，第一组件可以为ZZ1页面中***的Excel组件403。示例性的，参考图6C和图6D的相关描述，第一应用的第一页面可以为协同办公应用的ZZ2页面，第一组件可以为ZZ1页面中***的Word组件407。
S102、接收输入的第一操作，其中第一操作包括至少一个输入操作；响应于第一操作，显示第一应用的第二页面或者第二应用的第三页面。
其中，第一操作用于将第一应用的第一页面切换至其他页面，即第一应用的第二页面或者第二应用的第三页面。
示例性的，参考图4A至图4G的相关描述，第一应用的第一页面可以为即时通讯应用的聊天页面15。第一操作用于返回上一页时，响应于第一操作，可以将聊天页面15切换为即时通讯应用的主页12；第一操作用于返回桌面时，响应于第一操作，可以将聊天页面15切换为或者桌面应用的主界面11。
S103、接收输入的第二操作；响应于第二操作，显示第四页面，第四页面显示有至少一个组件标签，所述至少一个组件标签包括第一组件标签。
本申请实施例，第四页面可以是前述组件管理界面，组件管理界面可以是历史任务界面、负一屏或通知栏界面，还可以是其他页面，此处不做具体限定。
示例性的，参考图2A至图2C和图7A至图7J的相关描述，第四页面可以是历史任务界面，第二操作可以是作用于多任务键201C的触摸操作。参考图7B至图7J的相关描述，历史任务界面可以显示一或多个组件标签。
S104、当接收作用于第一组件标签的第三操作时，响应于第三操作，打开第一应用，显示第一页面，并在第一页面上显示第一组件。
本申请实施例中，第三操作可以为前述预设操作1。参考图10A至图11H的相关描述，应用1调用组件1后，通过作用于组件管理界面中的组件1的组件标签的预设操作1，可以快速定位该组件在应用1中的显示位置。
在一种实现方式中，所述显示第一应用的第一页面，第一页面的内容包括有一个或多个组件，所述一个或多个组件包括第一组件，包括：显示第一应用的第一页面的第一部分，第一页面还包括第二部分；其中当检测到输入的滑动手势时，显示第一页面的第二部分，第二部分包括第一组件。
示例性的，第一页面为长页面，终端设备100只能显示长页面的部分内容，需要用户通过上滑、下滑、左滑或右滑操作，才能查看该页面的全部内容。示例性的，图10B所示的ZZ1页面18、图11D所示的朋友圈页面14，图4G和图5D所示的聊天页面15均为长页面。第一应用被切换至后台运行时，显示屏显示的第一页面的部分页面可以是不包含第一组件的第一部分；第一应用被切换至后台运行后，通过作用于第一组件的第一组件标签的预设操作1，依旧可以快速定位并显示第一页面中的第一组件。
在一种实现方式中，所述方法还包括：第一组件为***型组件，当接收作用于第一组件 标签的第四操作时，响应于第四操作，打开第一应用，显示第一组件的第一内容页面，其中第三操作与第四操作不同。
在一种实现方式中，所述方法还包括：第一组件为***型组件，当接收作用于第一组件标签的第四操作时，响应于第四操作，打开第三应用，显示第一组件的第二内容页面，其中第三操作与第四操作不同。
本申请实施例中，第四操作可以是前述预设操作2，第三应用可以为前述应用2。通过作用于组件1的组件标签的预设操作2，可以在应用1中显示与该组件的显示内容相关联的用户界面，例如前述第一内容页面。或者，通过作用于组件1的组件标签的预设操作2，可以调用提供组件1的应用2，在应用2中展示与该组件的显示内容相关联的用户界面，例如前述第二内容页面。
示例性的，参考图5A至图5F和图11E至图11H的相关描述，第一应用的第一页面可以为即时通讯应用的聊天页面15，第一组件可以为聊天页面15中***的音乐播放组件310，第一组件标签可以为音乐播放组件310的组件标签612；通过作用于组件标签612的预设操作1，终端设备100可以在即时通讯应用的聊天页面15显示音乐播放组件310。第一内容页面可以为前述简易播放界面16；通过作用于组件标签612的预设操作2，终端设备100可以在即时通讯应用中显示音乐播放组件310播放的歌曲的简易播放界面16。第二内容页面可以为前述原始播放界面17；通过作用于组件标签612的预设操作2，终端设备100可以调用音乐应用，在音乐应用中显示音乐播放组件310播放的歌曲的原始播放界面17。
示例性的，参考图10A至图10I的相关描述，第一应用的第一页面可以为协同办公应用的ZZ1页面，第一组件可以为ZZ1页面中***的Excel组件403，第一组件标签可以为Excel组件403的组件标签601；通过作用于组件标签601的预设操作1，终端设备100可以在协同办公应用的ZZ1页面显示Excel组件403。第二内容页面可以为前述Excel应用的用户界面19；通过作用于组件标签601的预设操作2，终端设备100调用Excel应用，在Excel应用中显示用户界面19，用户界面19用于显示Excel组件403的“项目进度表”。
示例性的，参考图11A至图11D的相关描述，第一应用的第一页面可以为即时通讯应用的朋友圈页面14，第一组件可以为该朋友圈页面，第一组件标签可以为朋友圈页面14的组件标签611；通过作用于组件标签611的预设操作1，终端设备100可以在即时通讯应用中显示朋友圈页面14。
在一种实现方式中，第一页面显示的第一组件提供与第一组件的显示内容相关的第一功能；第一内容页面或第二内容页面，提供与第一组件的显示内容相关的第一功能和第二功能，第一组件不能提供第二功能。可以理解，第一组件只能提供与第一组件的显示内容相关的部分功能(例如第一功能)，若用户需要体验与第一组件的显示内容相关的更多功能(例如第二功能)，用户可以通过第四操作调用第一内容页面或第二内容页面，第一内容页面或第二内容页面可以理解为第一组件的显示内容的详情页面，可以提供更丰富的功能。
在一种实现方式中，所述响应于第二操作后，显示第四页面前，所述方法还包括：显示第五页面，第五页面包括第一应用对应的应用标识；第五页面还包括至少一个拓展控件；接收作用于拓展控件的第五操作；响应于第五操作，显示第四页面；上述应用标识可以是调用组件的应用的应用标识。
示例性的，参考图7A至图7I的相关描述，第五页面可以是图7A所示的历史任务界面21，历史任务界面21包括调用组件的各应用的应用标识对应的拓展控件，例如协同办公应用 的应用标识204对应的拓展控件501。第四页面可以是图7B至图7D所示的历史任务界面21，第五操作可以是作用于拓展控件501的触摸操作，响应于上述输入操作，终端设备100在协同办公应用的组件标签显示区503显示协同办公应用中可进行组件定位的组件的组件标签，例如组件标签601至组件标签604。
在一种实现方式中，第一组件，包括：第一应用调用过的组件；或者，第一应用的最近一次运行期间，第一应用调用的组件；或者，第一预设时长内，第一应用调用的组件；或者，第二预设时长内，第一应用调用的组件中使用率最高的预设数量的组件。
在一种实现方式中，所述至少一个组件标签包括至少两个组件标签，其中两个组件标签的排列顺序，是依据组件标签指示的组件的最近一次使用时间和/或使用频率确定的。
在一种实现方式中，第三操作为作用于第一组件标签的点击操作；第四操作为长按第一组件标签后将第一组件标签拖曳至第三控件的滑动操作。在一种实现方式中，第三控件显示有第三应用的应用标识和/或第三提示信息，第三提示信息用于提示通过将第一组件标签拖曳至第三控件触发第三应用显示第一组件的相关内容。在一种实现方式中，第三控件是检测到作用于第一组件标签的长按操作后显示的。
示例性的，参考图11E和图11F的相关描述，以第一组件标签是组件标签612为例，第三控件可以是预设区域641，第三应用可以是音乐应用；第四操作可以包括长按组件标签601拖曳至预设区域641的滑动操作。可选的，预设区域641可以是长按组件标签601后显示的。可选的，预设区域641显示有音乐应用的应用标识和/或第三提示信息(例如文字“拖到此处通过如下应用打开组件”)。
在一种实现方式中，第四页面包括第四控件和第五控件；第三操作包括从第一组件标签至第四控件的滑动操作；第四操作包括从第一组件标签至第五控件的滑动操作。
在一种实现方式中，第三操作包括长按第一组件标签后将第一组件标签拖曳至第四控件的滑动操作；第四操作包括长按第一组件标签后将第一组件标签拖曳至第五控件的滑动操作。
在一种实现方式中，第四控件和第五控件是检测到作用于第一组件标签的长按操作后显示的。
在一种实现方式中，第四控件显示有第一应用的应用标识和/或第一提示信息，第五控件显示有第三应用的应用标识和/或第二提示信息；第一提示信息用于提示在调用第一组件的应用中进行组件定位，第二提示信息用于提示通过提供第一组件的应用打开组件。可以理解，提供第一组件的第三应用打开第一组件，可以显示第二内容页面。
示例性的，参考图10E和图10F的相关描述，以第一组件标签是组件标签601为例，第四控件可以为协同办公应用的应用标识621，第五控件可以为Excel应用的应用标识622。可选的，第三操作包括从组件标签601至应用标识621的滑动操作；第四操作可以包括从组件标签601至应用标识621的滑动操作。可选的，第三操作包括长按组件标签601后拖曳至应用标识621的滑动操作；第四操作可以包括长按组件标签601后拖曳至应用标识621的滑动操作。可选的，协同办公应用的应用标识621和Excel应用的应用标识622，可以是长按组件标签601后显示的。
示例性的，参考图10H和图10I的相关描述，以第一组件标签是组件标签601为例；第四控件可以为页面定位控件631，第四控件显示有第一提示信息(例如文字“页面定位”)；第五控件可以为来源定位控件632，第五控件显示有第二提示信息(例如文字“来源定位”)。可选的，第三操作包括从组件标签601至页面定位控件631的滑动操作；第四操作可以包括从 组件标签601至来源定位控件632的滑动操作。可选的，第三操作包括长按组件标签601后拖曳至页面定位控件631的滑动操作；第四操作可以包括长按组件标签601后拖曳至来源定位控件632的滑动操作。可选的，页面定位控件631和来源定位控件632，可以是长按组件标签601后显示的。
在一种实现方式中，第三操作、第四操作为以下操作中的一个：作用于第一组件标签的点击操作；作用于第一组件标签的长按操作；作用于第一组件标签的右滑操作；作用于第一组件标签的左滑操作；作用于第一组件标签的上滑操作；作用于第一组件标签的下滑操作；第三操作和第四操作不同。
示例性的，参考图10A至图10B的相关描述，第三操作可以是作用于组件标签的左滑操作，第四操作可以为作用于组件标签的右滑操作。
在一种实现方式中，所述方法还包括：当接收作用于第一组件标签的第六操作时，响应于第六操作，在第四页面显示以下一或多个：第一应用中的至少一个联系人的用户标识、第四应用的应用标识、第四应用的指定页面的页面标识；所述至少一个联系人的用户标识包括第一联系人的用户标识，第一联系人的用户标识用于将第一组件分享给第一应用中的第一联系人；第四应用的应用标识用于将第一组件分享至第四应用中的联系人；第四应用的指定页面的页面标识用于将第一组件分享至第四应用的指定页面。
示例性的，参考图12E至图12K的相关描述，以第一组件标签是Excel组件403的组件标签601为例，第六操作可以是作用于组件标签601的下滑操作，第一应用为协同办公应用，第一联系人的用户标识可以是用户标识651，第四应用的应用标识可以为即时通讯应用的应用标识652，第四应用的指定页面的页面标识可以为即时通讯应用的朋友圈页面14的页面标识653。参考图12E和图12F的相关描述，通过用户标识651可以将Excel组件403分享给本应用的联系人。参考图12G至图12I的相关描述，通过应用标识652可以将Excel组件403分享给即时通讯应用的联系人。参考图12J和图12K的相关描述，通过页面标识653可以将Excel组件403分享至朋友圈页面14。
在一种实现方式中，所述方法还包括：当接收作用于第一组件标签的第七操作时，第七操作用于预览第一页面中的第一组件，响应于第七操作，按照第一组件的原尺寸或放大后的尺寸，在第四页面显示第一组件的组件快照。
示例性的，参考图12A和图12B的相关描述，以第一组件标签是Excel组件403的组件标签601为例，第七操作可以是作用于组件标签601的双击操作。通过双击组件标签601，用户可以预览Excel组件403的显示内容。
在一种实现方式中，所述方法还包括：当接收作用于第一组件标签的第八操作时，响应于第八操作，停止显示第一组件标签，将第一组件标签之后的组件标签向前顺延一个位置进行显示。
示例性的，参考图12C和图12D的相关描述，以第一组件标签是朋友圈页面14的组件标签611为例，第七操作可以是作用于组件标签611的上滑操作。响应于上述上滑操作，终端设备100可以停止显示组件标签611，并将排在朋友圈页面14之后的组件的组件标签向前顺移一位，还可以将朋友圈页面从组件管理白名单中移除。
在一种实现方式中，第四页面中显示的组件标签指示的组件均为组件管理白名单中的组件；组件管理白名单是终端设备、第一应用和用户中一或多个设置的。
示例性的，图13A至图13D示出了通过***设置管理组件管理白名单的相关用户界面图， 此处不再赘述。
在一种实现方式中，第一组件标签包括第一组件的组件标识；第一组件标签还包括以下零个、一个或多个：第一组件所在的页面的页面标识，提供第一组件的应用的应用标识，第一组件所在的工作区的工作区标识；组件标识包括以下一或多个：组件图标、组件名称和组件快照，页面标识包括页面图标和/或页面名称，组件标签中的应用标识包括应用图标和/或应用名称，工作区标识包括工作区图标和/或工作区名称。
在一种实现方式中，第一组件标签包括：第一组件的组件图标或组件快照，和第一页面的页面名称；或者，第一组件的组件图标或组件快照，和第一页面所在工作区的工作区名称；或者，第一组件的组件图标或组件快照，和第一组件的组件名称；或者，第一页面的页面图标和第一组件的组件名称；或者，提供第一组件的应用的应用图标和第一组件的组件名称。
示例性的，组件标签可以参考图8和图9的相关描述，此处不再赘述。
在一种实现方式中，所述至少一个组件标签还包括第二组件标签，第二组件标签与在第一应用的第十页面调用的第一组件相关联，第一组件标签不同于第二组件标签，第一组件标签包括第一页面的页面标识，第二组件标签包括第十页面的页面标识。
示例性的，参考图8的(b)和(d)的相关描述，在ZZ1页面和ZZ3页面调用同一组件，即Excel组件403；ZZ1页面的Excel组件403的组件标签601和ZZ3页面的Excel组件403的组件标签603不同。ZZ1页面的Excel组件403的组件标签601包括ZZ1页面的页面标识(例如页面名称“ZZ1”)，ZZ3页面的Excel组件403的组件标签603包括ZZ3页面的页面标识(例如页面名称“ZZ3”)。
本申请实施例中，第四页面中组件标签可以有多种显示方式；例如基于调用组件的应用、提供组件的应用、调用组件的设备、使用组件的用户、组件所在的页面、添加组件的Widget等分类方式(或者显示维度)进行分类显示。这样分类显示，组件标签的显示更加清晰明了，以便于用户快速定位到自己想操作的组件标签，丰富了组件标签的显示方式。
在一种实现方式中，第四页面包括至少一个应用标识，所述至少一个应用标识包括第一应用标识；第四页面中的第一应用标识对应的组件标签显示区，显示有第一应用标识指示的应用调用的组件所关联的至少一个组件标签。
示例性的，参考图7A至图7J以及图14A至图14B的相关描述，第一应用标识指示的应用可以为协同办公应用。终端设备可以在组件管理界面41(即第四页面)中的协同办公应用的应用标识对应的组件标签显示区503，显示该应用调用的组件关联的组件标签。
在一种实现方式中，第四页面包括调用组件的应用对应的至少两个应用标识；第四页面中，可以同时在上述至少两个应用标识各自对应的组件标签显示区，分别显示各应用标识指示的应用调用的组件关联的组件标签。示例性的，参考图14B的相关描述，终端设备可以在组件管理界面41同时显示各应用调用的组件关联的组件标签。
在一种实现方式中，第四页面包括至少一个应用标识，所述至少一个应用标识包括第二应用标识；第四页面中的第二应用标识对应的组件标签显示区，显示有第二应用标识指示的应用提供的组件所关联的至少一个组件标签。
示例性的，参考图17A至图17C的相关描述，第二应用标识指示的应用可以为协同办公应用。终端设备可以在组件管理界面41中的协同办公应用的应用标识对应的组件标签显示区，显示该应用提供的组件关联的组件标签。
在一种实现方式中，第四页面包括至少一个设备标识，所述至少一个设备标识包括第一 设备标识；第四页面中的第一设备标识对应的组件标签显示区，显示有第一设备标识指示的设备调用的组件所关联的至少一个组件标签。
示例性的，参考图19A的相关描述，第一设备标识指示的设备可以为终端设备100。终端设备100可以在组件管理界面41中的终端设备100的设备标识对应的组件标签显示区，显示该设备调用的组件关联的组件标签。
在一种实现方式中，第四页面包括至少一个用户标识，所述至少一个用户标识包括第一用户标识；第四页面中的第一用户标识对应的组件标签显示区，显示有第一用户标识指示的用户使用的组件所关联的至少一个组件标签。
示例性的，参考图18的相关描述，第一用户标识指示的用户可以为用户“Leo”。终端设备100可以在组件管理界面41中的用户“Leo”的用户标识对应的组件标签显示区，显示该用户使用的组件关联的组件标签。
在一种实现方式中，第四页面包括至少一个页面标识，所述至少一个页面标识包括第一页面标识；第四页面中的第一页面标识对应的组件标签显示区，显示有第一页面标识指示的页面调用的组件所关联的至少一个组件标签。
在一种实现方式中，第四页面包括至少一个Widget标识，所述至少一个Widget标识包括第一Widget标识；第四页面中的第一Widget标识对应的组件标签显示区，显示有第一Widget标识指示的Widget添加的组件所关联的至少一个组件标签。
本申请实施例中，在第四页面中，终端设备可以采用多种显示方式对用户展示组件的组件标签，用户还可以根据自身需求切换组件标签的显示方式。
在一种实现方式中，第四页面还包括第一控件和第二控件，所述方法还包括：当接收到作用于第一控件的触摸输入时，显示第六页面，所示第六页面包括至少一个用户标识和第一组件标签；当接收作用于第六页面上的第一组件标签的第三操作时；响应于第三操作，显示第一页面，并在第一页面上显示第一组件。上述用户标识可以是使用组件的用户的用户标识。当接收到作用于第二控件的触摸输入时，显示第七页面，所示第七页面包括至少一个设备标识和第一组件标签；当接收作用于第七页面上的第一组件标签的第三操作时；响应于第三操作，显示第一页面，并在第一页面上显示第一组件。上述设备标识可以是调用组件的设备的用户标识。
在一种实现方式中，第四页面包括调用组件的应用的应用标识，第四页面还包括第六控件和/或第七控件，所述方法还包括：当接收到作用于第六控件的触摸输入时，显示第八页面，所示第八页面包括至少一个提供组件的应用的应用标识和第一组件标签；当接收作用于第八页面上的第一组件标签的第三操作时；响应于第三操作，显示第一页面，并在第一页面上显示第一组件；当接收到作用于第七控件的触摸输入时，显示第九页面，所示第九页面包括至少一个添加了组件的Widget的Widget标识和第一组件标签；当接收作用于第九页面上的第一组件标签的第三操作时；响应于第三操作，显示第一页面，并在第一页面上显示第一组件。
示例性的，参考图20A至图20E的相关描述，组件管理界面41当前显示方式是基于调用组件的应用进行分类显示的，第二控件可以为组件管理界面41中的选项816；响应于针对选项816的输入操作，终端设备100切换选项816的状态为选中状态，即基于使用组件的设备进行分类显示。
本申请的各实施方式可以任意进行组合，以实现不同的技术效果。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当 使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线)或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，该流程可以由计算机程序来指令相关的硬件完成，该程序可存储于计算机可读取存储介质中，该程序在执行时，可包括如上述各方法实施例的流程。而前述的存储介质包括：ROM或随机存储记忆体RAM、磁碟或者光盘等各种可存储程序代码的介质。
总之，以上所述仅为本发明技术方案的实施例而已，并非用于限定本发明的保护范围。凡根据本发明的揭露，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (22)

  1. 一种界面显示方法，应用于包括触控显示屏的电子设备，其特征在于，所述方法包括：
    显示第一应用的第一页面，所述第一页面的内容包括有一个或多个组件，所述一个或多个组件包括第一组件；
    接收输入的第一操作，其中所述第一操作包括至少一个输入操作；
    响应于所述第一操作，显示所述第一应用的第二页面或者第二应用的第三页面；
    接收输入的第二操作；
    响应于所述第二操作，显示第四页面，所述第四页面显示有至少一个组件标签，所述至少一个组件标签包括第一组件标签；
    当接收作用于所述第一组件标签的第三操作时，
    响应于所述第三操作，打开所述第一应用，显示所述第一页面，并在所述第一页面上显示所述第一组件。
  2. 根据权利要求1所述的方法，其特征在于，所述显示第一应用的第一页面，所述第一页面的内容包括有一个或多个组件，所述一个或多个组件包括第一组件，包括：
    显示所述第一应用的所述第一页面的所述第一部分，所述第一页面还包括第二部分；
    其中当检测到输入的滑动手势时，显示所述第一页面的所述第二部分，所述第二部分包括所述第一组件。
  3. 根据权利要求1-2任一项所述的方法，其特征在于，所述方法还包括：
    所述第一组件为***型组件，
    当接收作用于所述第一组件标签的第四操作时，
    响应于所述第四操作，打开所述第一应用，显示所述第一组件的第一内容页面，其中所述第三操作与所述第四操作不同。
  4. 根据权利要求1-2任一项所述的方法，其特征在于，所述方法还包括：
    所述第一组件为***型组件，
    当接收作用于所述第一组件标签的第四操作时，
    响应于所述第四操作，打开第三应用，显示所述第一组件的第二内容页面，其中所述第三操作与所述第四操作不同。
  5. 根据权利要求1所述的方法，其特征在于，所述响应于所述第二操作后，显示第四页面前，所述方法还包括：
    显示第五页面，所述第五页面包括所述第一应用对应的应用标识；
    所述第五页面还包括至少一个拓展控件；
    接收作用于所述拓展控件的第五操作；
    响应于所述第五操作，显示所述第四页面。
  6. 根据权利要求1所述的方法，其特征在于，所述第四页面还包括第一控件和第二控件， 所述方法还包括：
    当接收到作用于所述第一控件的触摸输入时，显示第六页面，所示第六页面包括至少一个用户标识和所述第一组件标签；
    当接收作用于所述第六页面上的所述第一组件标签的所述第三操作时，
    响应于所述第三操作，显示所述第一页面，并在所述第一页面上显示所述第一组件；
    当接收到作用于所述第二控件的触摸输入时，显示第七页面，所示第七页面包括至少一个设备标识和所述第一组件标签；
    当接收作用于所述第七页面上的所述第一组件标签的所述第三操作时；
    响应于所述第三操作，显示所述第一页面，并在所述第一页面上显示所述第一组件。
  7. 根据权利要求1-6任一项所述的方法，其特征在于，所述第四页面为历史任务界面，所述第四页面的显示内容包括所述第一应用的界面快照。
  8. 根据权利要求7所述的方法，其特征在于，所述第一组件，包括：
    所述第一应用调用过的组件；
    或者，所述第一应用的最近一次运行期间，所述第一应用调用的组件；
    或者，第一预设时长内，所述第一应用调用的组件；
    或者，第二预设时长内，所述第一应用调用的组件中使用率最高的预设数量的组件。
  9. 根据权利要求1所述的方法，其特征在于，所述至少一个组件标签包括至少两个组件标签，其中所述两个组件标签的排列顺序，是依据组件标签指示的组件的最近一次使用时间和/或使用频率确定的。
  10. 根据权利要求3-6任一项所述的方法，其特征在于，所述第三操作为作用于所述第一组件标签的点击操作；
    所述第四操作为长按所述第一组件标签后将所述第一组件标签拖曳至第三控件的滑动操作。
  11. 根据权利要求10所述的方法，其特征在于，所述第三控件是检测到作用于所述第一组件标签的长按操作后显示的。
  12. 根据权利要求3-6任一项所述的方法，其特征在于，所述第四页面还包括第四控件和第五控件；
    所述第三操作包括从所述第一组件标签至所述第四控件的滑动操作；
    所述第四操作包括从所述第一组件标签至所述第五控件的滑动操作。
  13. 根据权利要求12所述的方法，其特征在于，
    所述第三操作包括长按所述第一组件标签后将所述第一组件标签拖曳至所述第四控件的滑动操作；
    所述第四操作包括长按所述第一组件标签后将所述第一组件标签拖曳至所述第五控件的 滑动操作。
  14. 根据权利要求12所述的方法，其特征在于，所述第四控件和所述第五控件是检测到作用于所述第一组件标签的长按操作后显示的。
  15. 根据权利要求12-14任一项所述的方法，其特征在于，所述第四控件显示有所述第一应用的应用标识和/或第一提示信息，所述第五控件显示有所述第三应用的应用标识和/或第二提示信息；所述第一提示信息用于提示在调用第一组件的应用中进行组件定位，所述第二提示信息用于提示通过提供第一组件的应用打开组件。
  16. 根据权利要求3-6任一项所述的方法，其特征在于，所述第三操作、所述第四操作为以下操作中的一个：
    作用于所述第一组件标签的点击操作；
    作用于所述第一组件标签的长按操作；
    作用于所述第一组件标签的右滑操作；
    作用于所述第一组件标签的左滑操作；
    作用于所述第一组件标签的上滑操作；
    作用于所述第一组件标签的下滑操作；
    所述第三操作和所述第四操作不同。
  17. 根据权利要求1-7任一项所述的方法，其特征在于，所述方法还包括：
    当接收作用于所述第一组件标签的第六操作时，
    响应于所述第六操作，在所述第四页面显示以下一或多个：所述第一应用中的至少一个联系人的用户标识、第四应用的应用标识、所述第四应用的指定页面的页面标识；
    所述至少一个联系人的用户标识包括第一联系人的用户标识，所述第一联系人的用户标识用于将所述第一组件分享给所述第一应用中的所述第一联系人；
    所述第四应用的应用标识用于将所述第一组件分享至所述第四应用中的联系人；
    所述第四应用的指定页面的页面标识用于将所述第一组件分享至所述第四应用的指定页面。
  18. 根据权利要求1-7任一项所述的方法，其特征在于，所述方法还包括：
    当接收作用于所述第一组件标签的第七操作时，所述第七操作用于预览所述第一页面中的所述第一组件，
    响应于所述第七操作，按照所述第一组件的原尺寸或放大后的尺寸，在所述第四页面显示所述第一组件的组件快照。
  19. 根据权利要求1-7任一项所述的方法，其特征在于，所述方法还包括：
    当接收作用于所述第一组件标签的第八操作时，
    响应于所述第八操作，停止显示所述第一组件标签，将所述第一组件标签之后的组件标签向前顺延一个位置进行显示。
  20. 根据权利要求1-7任一项所述的方法，其特征在于，所述第四页面中显示的组件标签指示的组件均为组件管理白名单中的组件；所述组件管理白名单是终端设备、第一应用和用户中一或多个设置的。
  21. 一种终端设备，其特征在于，包括存储器和处理器，所述存储器和所述处理器电偶合，所述存储器用于存储程序指令，所述处理器被配置用于调用所述存储器存储的全部或部分程序指令，以使得所述终端设备执行如权利要求1-20任一项所述的方法。
  22. 一种计算机存储介质，其特征在于，包括计算机指令，当所述计算机指令在终端设备上运行时，使得所述终端设备执行如权利要求1-20任一项所述的方法。
PCT/CN2023/081017 2022-03-14 2023-03-13 界面显示方法及相关装置 WO2023174200A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202210248494.X 2022-03-14
CN202210248494 2022-03-14
CN202210586578.4A CN116795461A (zh) 2022-03-14 2022-05-27 界面显示方法及相关装置
CN202210586578.4 2022-05-27

Publications (1)

Publication Number Publication Date
WO2023174200A1 true WO2023174200A1 (zh) 2023-09-21

Family

ID=88022236

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/081017 WO2023174200A1 (zh) 2022-03-14 2023-03-13 界面显示方法及相关装置

Country Status (1)

Country Link
WO (1) WO2023174200A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105930073A (zh) * 2015-02-27 2016-09-07 三星电子株式会社 用于支持电子设备中的通信的方法和装置
CN106105182A (zh) * 2014-03-12 2016-11-09 谷歌公司 在应用后台化后在窗口小部件中继续回放的***和方法
CN110174982A (zh) * 2017-05-16 2019-08-27 苹果公司 用于在用户界面之间导航的设备、方法和图形用户界面
WO2019236217A1 (en) * 2018-06-03 2019-12-12 Apple Inc. Accelerated task performance
US20210286509A1 (en) * 2020-03-10 2021-09-16 Apple Inc. Devices, Methods, and Graphical User Interfaces for Interacting with User Interface Objects Corresponding to Applications

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106105182A (zh) * 2014-03-12 2016-11-09 谷歌公司 在应用后台化后在窗口小部件中继续回放的***和方法
CN105930073A (zh) * 2015-02-27 2016-09-07 三星电子株式会社 用于支持电子设备中的通信的方法和装置
CN110174982A (zh) * 2017-05-16 2019-08-27 苹果公司 用于在用户界面之间导航的设备、方法和图形用户界面
WO2019236217A1 (en) * 2018-06-03 2019-12-12 Apple Inc. Accelerated task performance
US20210286509A1 (en) * 2020-03-10 2021-09-16 Apple Inc. Devices, Methods, and Graphical User Interfaces for Interacting with User Interface Objects Corresponding to Applications

Similar Documents

Publication Publication Date Title
WO2020238356A1 (zh) 界面显示方法、装置、终端及存储介质
WO2021013158A1 (zh) 显示方法及相关装置
WO2021103981A1 (zh) 分屏显示的处理方法、装置及电子设备
CN110119296B (zh) 切换父页面和子页面的方法、相关装置
EP3979100A1 (en) Image display method and electronic device
WO2021000881A1 (zh) 一种分屏方法及电子设备
WO2021088881A1 (zh) 一种选择图片的方法和电子设备
WO2021082835A1 (zh) 启动功能的方法及电子设备
WO2021000841A1 (zh) 一种生成用户头像的方法及电子设备
WO2021008334A1 (zh) 小程序的数据绑定方法、装置、设备及存储介质
US20220358089A1 (en) Learning-Based Keyword Search Method and Electronic Device
WO2022152024A1 (zh) 一种微件的显示方法与电子设备
WO2022057852A1 (zh) 一种多应用程序之间的交互方法
KR20210105938A (ko) 이미지 분류 방법 및 전자 디바이스
WO2020073317A1 (zh) 文件管理方法及电子设备
WO2023138305A9 (zh) 卡片显示方法、电子设备及计算机可读存储介质
WO2023083184A1 (zh) 桌面管理方法、图形用户界面及电子设备
EP4336357A1 (en) Message processing method and related apparatus
CN113448658A (zh) 截屏处理的方法、图形用户接口及终端
WO2023174200A1 (zh) 界面显示方法及相关装置
CN112711636B (zh) 数据同步方法、装置、设备及介质
CN116795461A (zh) 界面显示方法及相关装置
WO2023246666A1 (zh) 一种搜索方法及电子设备
WO2023160455A1 (zh) 删除对象的方法及电子设备
KR102264428B1 (ko) 전자 장치의 동작 방법 및 장치

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23769703

Country of ref document: EP

Kind code of ref document: A1