Display method, electronic equipment and computer readable storage medium

Abstract

The invention provides a display method, electronic equipment and a computer readable storage medium. In some embodiments of the application, the electronic device can create and display the 3D component based on the attribute information of the 3D component provided by the three-party application, the 3D component is used for displaying complex animation content or complex pictures, and the diversity of the display component of the electronic device is expanded. In other embodiments of the present application, when the electronic device creates the 3D component based on the attribute information of the 3D component provided by the first application (three-party application or non-three-party application), the electronic device can create the common component and the extended component of the 3D component at the same time, and after the 3D component is displayed, the electronic device can control the 3D component to switch different display states, so that the 3D component display efficiency is improved. And the display effect of the 3D component in the electronic equipment is improved.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to a display method, electronic device and computer-readable storage medium. Background Technology

[0002] With the popularization of smart electronic devices and the development of Internet technology, smartphones, laptops, tablets and other electronic devices have become indispensable products in people's daily lives.

[0003] Electronic devices are equipped with increasingly diverse functions, and operating systems support the development of components to provide users with richer functionalities and user experiences. For example, electronic devices can display key information and help users quickly access corresponding functions by showing display cards and widgets. For instance, an electronic device can display a weather card to show users weather information, or a navigation card to show users route navigation information.

[0004] However, the current components display limited content, failing to provide users with a richer interactive experience. Further research is needed to improve the display effect of the components. Summary of the Invention

[0005] This application provides a display method, an electronic device, and a computer-readable storage medium. In some embodiments of this application, the electronic device can create and display 3D components based on attribute information of 3D components provided by a third-party application. These 3D components are used to display complex animation content or complex images, expanding the diversity of display components available on the electronic device. In other embodiments of this application, when the electronic device creates a 3D component based on attribute information of a 3D component provided by a first application (either a third-party application or a non-third-party application), the electronic device can simultaneously create both ordinary and extended components of the 3D component. After displaying the 3D component, the electronic device can control the 3D component to switch between different display states, improving the display effect of the 3D component in the electronic device.

[0006] In a first aspect, this application provides a display method applied to an electronic device, the electronic device including a first application, the first application being a third-party application; the electronic device acquires attribute information of a first component, the attribute information including attribute information of a regular component and attribute information of an extended component, the first component being a component in the first application. The electronic device receives and responds to a first operation, adding the first component to a first interface based on the attribute information of the first component.

[0007] Optionally, the first component can be a 3D component or a non-3D component. The electronic device 100 can determine whether the first component is a 3D component or a non-3D component based on its attribute information. If the electronic device 100 determines that the first component is a 3D component based on its attribute information, then the electronic device 100 can create the first component, which includes a regular component and an extended component, and display the regular component while hiding the extended component. The electronic device 100 can also display the content of the regular component within the regular component. If the electronic device 100 determines that the first component is a non-3D component based on its attribute information, then the electronic device 100 can create the first component, which includes a regular component, and display the regular component. The electronic device 100 can also display the content of the regular component within the regular component.

[0008] For example, a 3D component may include a fun interactive component or a scene animation component. If the first component is a 3D component, its attribute information may include the attribute information of a regular component and the attribute information of an extended component. If the first component is a non-3D component, its attribute information may include the attribute information of a regular component. The attribute information of a regular component includes any one or more of the following: size, shape, color, and transparency. When the type of the first component is a fun interactive component, the attribute information of the extended component includes any one or more of the following: the first extended component type (e.g., a fun interactive component), the name of the dynamic component extension module that the extended component depends on, the name of the installation package of the application to which the extended component belongs, and the timeout pause duration. When the type of the first component is a scene animation component, the attribute information of the extended component includes any one or more of the following: the second extended component type (e.g., a scene animation component), the name of the dynamic component extension module that the extended component depends on, whether the extended component can remain active, and the types of gestures disabled when displaying the extended component.

[0009] By implementing this method, the electronic device can receive attribute information of the first component provided by the third-party application, and create and display the first component provided by the third-party application based on the attribute information of the first component, thereby increasing the diversity of components displayed by the electronic device 100 and improving the display effect of the components.

[0010] In one possible implementation, the first component includes a regular component and an extended component; the method further includes: in response to a component content switching message, the electronic device displays the first content of the regular component and hides the second content of the extended component, or the electronic device displays the second content of the extended component and hides the first content of the regular component. By implementing this method, the electronic device can switch between different display states of the 3D component, improving the display effect of the component.

[0011] In one possible implementation, the electronic device obtains the first data of the first component, specifically including: when the electronic device installs the first application, the electronic device obtains the attribute information of the first component; or, after the first application is installed, the electronic device obtains the attribute information of the first component.

[0012] In one possible implementation, the electronic device includes a component management service; when the electronic device displays the first content of a common component, the electronic device displays the common component and hides or destroys the extended component through the component management service; when the electronic device displays the second content of the extended component, the electronic device displays the extended component and hides the common component through the component management service.

[0013] Both extended components and regular components are child components of the first component. Implementing this method, after the component user creates the first component, the user doesn't need to worry about receiving component content switching messages, nor do they need to control the display state switching of the first component. The electronic device can confirm whether it has received the component content switching message through the framework layer (e.g., a component rendering service or a component management service). After confirming that the component content switching message has been received, the electronic device can control the display state switching of the first component through the component management service in the framework layer. In other words, the component user does not need to participate in controlling the component's display state switching, and the component user does not need to adapt, reducing the workload of developers.

[0014] For example, a component user can call the Formkit interface provided by Formkit, and a component provider can also call the Formkit interface provided by Formkit. The Formkit interface called by the component user is different from the Formkit interface called by the component provider.

[0015] Formkit provides a Live Form Extension Ability, which component providers can use to develop 3D components. When an electronic device displays the content of an extended component, the framework layer (such as a card management service and / or a card rendering service) can invoke the Live Form Extension Ability in the first application process through the Formkit interface to display the extended component and hide the regular component. The Live Form Extension Ability in the first application process can display the extended component content within the extended component based on the extended component data provided by the Live Form Extension Ability.

[0016] When the electronic device displays the first content of a regular component, the framework layer (such as the card management service and / or card rendering service) can use the Formkit interface to pause or destroy the Live Form Extension Ability in the application process, hide or destroy the extension component, and display the regular component. The framework layer (such as the card management service and / or card rendering service) can obtain the regular component data from the first application through the Formkit interface and display the regular component content in the regular component based on the regular component data.

[0017] By implementing this method, electronic devices can control the switching of the display state of the first component through the component management service in the framework layer. The component user does not need to control the switching of the display state of the first component. The component user does not need to adapt or monitor whether the message of the first component switching from the inactive state to the active state is obtained, which reduces the workload of developers.

[0018] In one possible implementation, the electronic device displays the first content of a general component, specifically including: the electronic device obtaining first data of the general component from a first application; and the electronic device displaying the first content of the general component in the general component based on the first data of the general component.

[0019] For example, an electronic device may include a component rendering service. The electronic device can obtain first data of a common component from a first application through the component rendering service; the component rendering service renders the first data of the common component to obtain the first content of the common component, and displays the first content of the common component in the common component.

[0020] Optionally, when the first component is inactive or paused, the electronic device can display the first content of the ordinary component in the ordinary component.

[0021] In one possible implementation, the first application includes a first interface; the electronic device obtains first data of a common component from the first application, specifically including: the electronic device obtains the first data of the common component from the first application through the first interface. Thus, when the first application is a third-party application, the electronic device can obtain the first data of the common component provided by the first application through the first interface and display the first content of the common component of the third-party application.

[0022] In one possible implementation, the electronic device displays the second content of the extended component, specifically including: the electronic device sending a first message to a first application; in response to the first message, the first application obtaining second data of the extended component; and the first application displaying the second content of the extended component in the extended component based on the second data of the extended component. Implementing this method, the second content of the extended component is relatively complex, and the electronic device can render the second content of the extended component using the second data of the extended component provided by the first application.

[0023] For example, an electronic device may include a component rendering service. The electronic device may send a first message to a first application through the component rendering service, the first message instructing the first application to render a second content of the extended component based on the second data of the extended component.

[0024] Optionally, when the first component is in a paused state, the electronic device may display the second content of the extended component in the extended component.

[0025] Optionally, the first application includes a dynamic component extension module. The first application displays the second content of the extension component in the extension component based on the second data of the extension component. Specifically, the first application renders the second data of the extension component through the dynamic component extension module and displays the second content of the extension component in the extension component.

[0026] For example, a dynamic component extension module may include a rendering engine and second data for the extension component. A first application can render the second data of the extension component using the rendering engine provided by the dynamic component extension module to obtain the second content of the extension component. By implementing this method, third-party applications can develop the resources required for 3D components, such as the rendering engine and the second data of the extension component, using the dynamic component extension module provided by the framework layer, enabling electronic devices to display the 3D components of the third-party applications.

[0027] In one possible implementation, the electronic device includes a component management service; the component management service is used to store attribute information of a first component. By implementing this method, the electronic device can store the attribute information of the first component provided by a third-party application in the component management service.

[0028] In some embodiments, the component management service can also send the attribute information of the first component to the component user. The component user can then create the first component based on the attribute information of the first component.

[0029] In some embodiments, the response to the component content switching message includes any one or more of the following: a message that the first component switches from an active state to a paused state, a message that the first component switches from a paused state to an inactive state, a message that the first component switches from an active state to an inactive state, a message that the first component switches from an inactive state to an active state, and a message that the first component switches from a paused state to an active state.

[0030] In one possible implementation, the response to the component content switching message includes any one or more of the following: a message that the first component switches from an active state to a paused state, a message that the first component switches from a paused state to an inactive state, a message that the first component switches from an active state to an inactive state, a message that the first component switches from an inactive state to an active state, and a message that the first component switches from a paused state to an active state.

[0031] Wherein, if the type of the first component is the first type (e.g., a fun interactive component), the event that the first component switches from the active state to the paused state includes any one or more of the following: a touch operation on the first component, the user's gaze being directed at an area other than the first component, the first interface being invisible, an operation performed on an area other than the display area where the first component is located, and the continuous display duration of the second content of the extended component exceeding the second duration.

[0032] The event in which the first component switches from the paused state to the inactive state includes any one of the following: the process of the first application is closed, the second component enters the active state, and the second component and the first component are different components.

[0033] The event in which the first component switches from the active state to the inactive state includes any one or more of the following: the process of the first application is closed, or the second component enters the active state.

[0034] The event that switches the first component from an inactive state to an active state includes any one or more of the following: a touch operation on the first component, or the user's gaze on the first component.

[0035] The event that allows the first component to switch from a paused state to an active state includes any one or more of the following: a touch operation on the first component, or the user's gaze on the first component.

[0036] In one possible implementation, when the first component switches from an active state to a paused state, or from a paused state to an inactive state, or from an active state to an inactive state, the electronic device displays the first content of the ordinary component and hides the second content of the extended component; when the first component switches from an inactive state to an active state, or when the first component switches from a paused state to an active state, the electronic device displays the second content of the extended component and hides the first content of the ordinary component.

[0037] If the first component is of type two (e.g., scene animation component), the event that the first component switches from active state to inactive state includes any one or more of the following: the cumulative display duration of the first content of the ordinary component exceeds the first duration, the process of the first application is closed, the second component enters the active state, and the second component and the first component belong to different components.

[0038] The event in which the first component switches from an inactive state to an active state includes any one or more of the following: receiving a first request sent by the first application.

[0039] In one possible implementation, when the first component switches from an active state to an inactive state, the electronic device displays the first content of the ordinary component and hides the second content of the extended component; when the first component switches from an inactive state to an active state, the electronic device displays the second content of the extended component and hides the first content of the ordinary component.

[0040] In one possible implementation, if the event in which the first component switches from an inactive state to an active state includes receiving a first request sent by the first application, the method further includes: the electronic device obtaining a first duration from the first application, the first duration being used to instruct the electronic device to stop displaying the second content of the extended component after detecting that the continuous display duration of the second content of the extended component exceeds the first duration.

[0041] Optionally, the electronic device may also include a component management service, to which the first application may send a first duration. The component management service may, upon detecting that the continuous display duration of the second content of the extended component exceeds the first duration, destroy or hide the extended component. The electronic device may then stop displaying the second content of the extended component and display the normal component, allowing the electronic device to begin displaying the content of the normal component.

[0042] In one possible implementation, the method further includes: the electronic device obtaining a first overflow area from a first application; the electronic device determining a first display area of ​​a second component based on the first overflow area, the first display area of ​​the second component being used to indicate an area for the first application to display the second content of the extended component. Implementing this method, the first application can also request an overflow area from the electronic device, which can allocate a display area for the first application, allowing the first application to display the second content of the extended component within the allocated display area, thus improving the display effect of the second content of the extended component.

[0043] Optionally, the electronic device may also include a component management service and a component rendering service. The first application can send the first overflow area to the component management service. The component management service then sends the first overflow area to the component rendering service. The component rendering service can allocate a display area based on the first overflow area, and then send the display area information to the first application. The first application can display the second content of the extended component in the display area allocated by the component rendering service.

[0044] In one possible implementation, the first application includes a second interface; the electronic device obtains a first duration from the first application, specifically including: the electronic device obtaining the first duration from the first application through the second interface; and / or, the electronic device obtaining a first overflow area from the first application through the second interface. The second interface and the first interface may be the same or different.

[0045] Secondly, this application provides a display method applied to an electronic device, the electronic device including a first application; the method includes: the electronic device acquiring attribute information of a first component, the attribute information including attribute information of a regular component and attribute information of an extended component, the first component being a component in the first application. The electronic device receives and responds to a first operation, adding the first component to a first interface based on the attribute information of the first component, the first component including a regular component and an extended component. In response to a component content switching message, the electronic device displays the first content of the regular component and hides the second content of the extended component, or the electronic device displays the second content of the extended component and hides the first content of the regular component.

[0046] By implementing this method, the electronic device can receive attribute information of 3D components provided by a first application (a third-party application or a non-third-party application). When the electronic device creates 3D components based on the attribute information of the 3D components provided by the first application, the electronic device can simultaneously create ordinary components and extended components of the 3D components. After displaying the 3D components, the electronic device can control the 3D to switch between different display states, thereby improving the display effect of the 3D components in the electronic device.

[0047] It should be noted that one or more possible implementations shown in the first aspect can also be applied to a display method provided in the second aspect. Refer to the description of one or more possible implementations in the first aspect, which will not be repeated here.

[0048] Thirdly, this application provides an electronic device, which includes a memory and a processor; wherein the memory and the processor are coupled, the memory is used to store a computer program, and when the processor executes and calls the computer program, the electronic device performs a display method provided in any possible implementation of the first aspect above.

[0049] Fourthly, this application provides a computer-readable storage medium including instructions that, when executed on an electronic device, cause the electronic device to perform a display method provided in any possible implementation of the first aspect above.

[0050] Fifthly, this application provides a computer program product containing instructions, including a computer program that, when executed by a processor, implements a display method provided in any possible implementation of the first aspect above.

[0051] In a sixth aspect, this application provides a chip system, which includes a processing circuit and an interface circuit. The chip system is characterized in that it includes a processing circuit and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processing circuit, and the processing circuit is used to execute the code instructions to perform a display method provided in any possible implementation of the first aspect above.

[0052] For a description of the beneficial effects of the second to sixth aspects, please refer to the description of the beneficial effects in the first aspect; this application will not repeat it here. Attached Figure Description

[0053] Figure 1 A schematic diagram is shown of an electronic device 100 displaying the content of a common component based on the common component data within the common component;

[0054] Figure 2A A schematic diagram of the hardware structure of an electronic device 100 is shown;

[0055] Figure 2B A schematic diagram of the software structure of an electronic device 100 is shown;

[0056] Figure 3A A schematic diagram of software interaction is shown for an electronic device 100 to acquire and save attribute information of a first component provided by a first application;

[0057] Figure 3B A flowchart illustrating a method for an electronic device 100 to acquire and save attribute information of a first component provided by a first application is shown.

[0058] Figure 3C A schematic diagram of the software interaction of another electronic device 100 acquiring and saving attribute information of a first component is shown;

[0059] Figure 3D A flowchart illustrating a method for another electronic device 100 to acquire and save attribute information of a first component is shown.

[0060] Figures 4A-4F This diagram illustrates an electronic device 100 receiving a user operation and adding a first component to the desktop.

[0061] Figure 5A A schematic diagram of software interaction is shown for an electronic device 100 displaying the contents of a common component of a first component;

[0062] Figure 5B A flowchart illustrating a method for an electronic device 100 to display the contents of a common component of a first component is shown.

[0063] Figure 5C Several examples are shown of the first component switching between different display states;

[0064] Figures 6A-6E A schematic diagram is shown showing a set of events that detect the first component switching from an inactive state to an active state, and the electronic device 100 displays the data of the extended component in the extended component;

[0065] Figures 7A-7C Another set of diagrams shows the electronic device 100 displaying extended component data in the extended component after detecting an event that the first component switches from an inactive state to an active state;

[0066] Figure 8A A schematic diagram of a software interaction is shown in which an electronic device 100 displays data of an extended component in an extended component after detecting an event that the first component switches from an inactive state to an active state.

[0067] Figure 8B A flowchart illustrating a method for an electronic device 100 to display extended component data in an extended component after detecting an event that switches from an inactive state to an active state;

[0068] Figures 9A-9B A schematic diagram is shown showing a group of electronic devices 100 receiving an operation applied to the display area where a first component is located, causing the first component to switch from an active state to a paused state;

[0069] Figures 9C-9D A schematic diagram is shown showing a group of electronic devices 100 receiving a user operation that makes the interface where the first component is located invisible, causing the first component to switch from an active state to a paused state;

[0070] Figure 10A The diagram illustrates a software interaction where, upon detecting an event that the first component switches from an active state to a paused state, the electronic device 100 displays the content of a normal component in a normal component.

[0071] Figure 10B The diagram illustrates a method flow diagram of an electronic device 100 displaying the content of a normal component in a normal component when an event is detected in which the first component switches from an active state to a paused state.

[0072] Figure 11AThis diagram illustrates a software interaction in which an electronic device 100 displays data from an extension component when a cancellation event is detected, indicating a switch from an active state to an inactive state.

[0073] Figure 11B A flowchart illustrating a method for an electronic device 100 to display extended component data in an extended component after detecting an event that switches from an active state to an inactive state;

[0074] Figure 12 Several examples of another first component switching between different display states are shown;

[0075] Figures 13A-13D This diagram illustrates another set of scenarios where, after detecting an event that the first component switches from an inactive state to an active state, the electronic device 100 displays extended component data in the extended component.

[0076] Figures 14A-14C This diagram illustrates another instance where, after detecting an event that the first component switches from an inactive state to an active state, the electronic device 100 displays extended component data in the extended component.

[0077] Figure 15A This diagram illustrates another software interaction whereby the electronic device 100 displays extension component data in the extension component after detecting an event that switches from an inactive state to an active state.

[0078] Figure 15B A flowchart illustrating another method by which electronic device 100 displays extended component data in an extended component after detecting an event that switches from an inactive state to an active state;

[0079] Figures 16A-16C The diagram illustrates how, after the fifth group detects an event where the first component switches from an inactive state to an active state, the electronic device 100 displays extended component data in the extended component.

[0080] Figure 17A This illustrates another software interaction diagram in which the electronic device 100 displays data of the extended component in the extended component after detecting an event that the first component switches from an inactive state to an active state;

[0081] Figure 17B This diagram illustrates a method for an electronic device 100 to display extended component data in an extended component after detecting an event that the first component has switched from an inactive state to an active state.

[0082] Figures 18A-18C A schematic diagram is shown showing how, after detecting an event that the first component switches from an active state to an inactive state, the electronic device 100 displays ordinary component data in the ordinary component;

[0083] Figure 19A This diagram illustrates another software interaction whereby the electronic device 100 displays extension component data in the extension component after detecting an event that switches from an active state to an inactive state.

[0084] Figure 19B A flowchart illustrating another method by which electronic device 100 displays extended component data in an extended component after detecting an event that switches from an active state to an inactive state;

[0085] Figure 20 A flowchart illustrating a display method provided in this application is shown;

[0086] Figure 21 A flowchart illustrating another display method provided in this application is shown. Detailed Implementation

[0087] The technical solutions in the embodiments of this application will be clearly and thoroughly described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B; the word "and / or" in the text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0088] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying or suggesting relative importance or implicitly indicating the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature, and in the description of the embodiments of this application, unless otherwise stated, "multiple" means two or more.

[0089] First, this application will introduce the components, component providers, component users, and component data involved.

[0090] 1. Components (Application Widget, App Widget)

[0091] A component, also known as a card, service card, service widget, application widget, or application component, is a small window or widget provided by an application on the interface of an electronic device. It presents key information to the user and helps the user quickly enable the corresponding function, so as to achieve the purpose of direct access to services and reduce hierarchical jumps.

[0092] In some embodiments, components can also be described as objects, elements, etc., which are simple encapsulations of data and methods, possessing their own properties and methods. In some examples, applications with different functionalities can generate different components to help users achieve different functionalities. Optionally, components include, for example, user interface components, software development windows, text boxes, buttons, chart components, etc. For instance, a card is one type of component.

[0093] 2. Component providers and component users

[0094] The provider of component data can be called the component provider, and the user who displays component content based on component data can be called the component user.

[0095] In some embodiments, the applications installed on an electronic device may be referred to as component users. For example, component users may include, but are not limited to, desktop applications, voice assistant applications, etc. For instance, a voice assistant application may be the Xiaoyi voice assistant application.

[0096] In some embodiments, the always-on display can be provided by an always-on display app, the lock screen can be provided by a lock screen app, and the pull-down and pull-up notification bar interfaces can be provided by a settings app. The always-on display app, lock screen app, and settings app can be independent apps, and therefore, the component users can also include the always-on display app, lock screen app, and settings app. In other embodiments, the always-on display, lock screen, pull-down notification bar, and pull-up notification bar interfaces can also be provided by a desktop app.

[0097] In some embodiments, the component provider may also be an application installed on the electronic device. For example, the component user may include, but is not limited to, weather apps, game apps, etc.

[0098] 3. Component Data

[0099] In the embodiments of this application, the type of component may include ordinary components and extended components. Component data may include ordinary component data and extended component data.

[0100] Regular components can display simple animated content or simple images. For example, simple animated content can include 2D animations with a duration shorter than a first duration (e.g., 1 second), and simple images can be 2D images. Component providers can provide regular component data. Electronic devices can display regular component content based on regular component data; the content of regular components can be 2D animated content. Regular components run in the component rendering service within the framework layer of the electronic device.

[0101] Extended components can display complex animations or images. For example, complex animations may include 3D animations with a duration longer than a primary duration (e.g., 1 second), and complex images may be 3D images. The component provider can provide extended component data. Electronic devices can display extended component content based on the extended component data, which can be 3D animations. Extended components run within the application layer of the electronic device, within the process of the component provider.

[0102] In some embodiments, because the complex animation content displayed in the extended component is intricate and lengthy, it requires a rendering engine with stronger rendering capabilities. Therefore, the component provider can provide a rendering engine. Before displaying the extended component content, the electronic device can activate the component provider's rendering engine to render the extended component data, obtain the extended component content, and then display the extended component content within the extended component.

[0103] Optionally, the rendering engine and extended component data can be provided by the component provider, and the rendering engine can be implemented through a Live Form Extension Ability. In some embodiments, the extended component data can also be implemented through a Live Form Extension Ability. In other embodiments, the component provider can periodically / irregularly obtain extended component data from the content provider.

[0104] For example, the rendering engine could be a UIExtension process.

[0105] Figure 1 A schematic diagram is shown of an electronic device 100 displaying the content of a common component based on the common component data within the common component.

[0106] like Figure 1 As shown, the electronic device 100 includes an application layer and an application framework layer. The application layer includes component users and component providers. The application framework layer includes component management services and component rendering services.

[0107] The method by which electronic device 100 displays the content of a common component based on the common component within the common component includes, but is not limited to, the following steps:

[0108] 1. The user of the component creates a regular component.

[0109] 2. The component uses the component management service to send messages 11.

[0110] 3. The component management service sends message 12 to the component rendering service.

[0111] 4. In response to message 12, the component rendering service obtains the ordinary component data from the component provider.

[0112] 5. The component rendering service renders the data of ordinary components and displays the content of ordinary components within them.

[0113] from Figure 1 It can be seen that the electronic device 100 can only display the content of the Euro-connected components based on the most basic components. It cannot provide rich and diverse component content, resulting in a poor user experience.

[0114] Electronic device 100 can be a mobile phone, tablet computer, personal computer (PC), ultra-mobile personal computer (UMPC), netbook, personal digital assistant (PDA), wearable device, artificial intelligence (AI) device, or other terminal device. Electronic device 100 can also be an in-vehicle device. Electronic device 100 can also be other types, and this application does not limit it in this regard.

[0115] See below. Figure 2A The structure of the electronic device to which the method provided in the embodiments of this application is applicable will be described.

[0116] like Figure 2A As shown, the electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a USB interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a sensor module 180, a display screen 194, and a SIM card interface 195, etc.

[0117] The sensor module 180 may include a gyroscope sensor 180B, a magnetic sensor 180D, an accelerometer sensor 180E, a proximity sensor 180F, a touch sensor 180K, etc. The sensor module 180 may also include a temperature sensor, a pressure sensor, a proximity sensor, a fingerprint sensor, an ambient light sensor, a barometric pressure sensor, a bone conduction sensor, etc.

[0118] Understandable, Figure 2A The electronic device 100 shown is merely an example and does not constitute a limitation on the electronic device. The electronic device may have more or fewer components than those shown in the figure, may combine two or more components, or may have different component configurations. Figure 2A The various components shown can be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application-specific integrated circuits.

[0119] Processor 110 may include one or more processing units, such as application processors (APs), modem processors, graphics processing units (GPUs), image signal processors (ISPs), controllers, memory, video codecs, digital signal processors (DSPs), baseband processors, and / or neural network processing units (NPUs). Different processing units may be independent devices or integrated into one or more processors. The controller may serve as the central nervous system and command center of the electronic device 100. The controller can generate operation control signals based on instruction opcodes and timing signals to control instruction fetching and execution.

[0120] The processor 110 may also include a memory for storing instructions and data.

[0121] The execution of the display method provided in this application embodiment can be controlled by the processor 110 or by calling other components. For example, it can call the processing program of this application embodiment stored in the internal memory 121, or call the processing program of this application embodiment stored in a third-party device through the external memory interface 120 to control the wireless communication module 160 to perform data communication with other devices, thereby improving the intelligence and convenience of the electronic device 100 and enhancing the user experience. The processor 110 may include different devices. For example, when integrating a CPU and a GPU, the CPU and GPU can cooperate to execute the display method provided in this application embodiment. For example, some algorithms in the display method can be executed by the CPU, and other algorithms can be executed by the GPU to achieve faster processing efficiency.

[0122] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. Display screen 194 can be used to display information input by the user or information provided to the user, as well as various graphical user interfaces (GUIs). For example, display screen 194 can display various interfaces from the embodiments of this application.

[0123] In this embodiment of the application, the display screen 194 can be a single flexible display screen, or it can be a splicing display screen composed of two rigid screens and a flexible screen located between the two rigid screens.

[0124] The electronic device 100 may also include a camera (a front-facing camera or a rear-facing camera, or a camera that can function as both a front-facing and a rear-facing camera), which is used to capture still images or videos.

[0125] Internal memory 121 can be used to store computer executable program code, which includes instructions. Processor 110 executes various functional applications and data processing of electronic device 100 by running the instructions stored in internal memory 121.

[0126] The internal memory 121 may also store one or more computer programs corresponding to the algorithm of this application. The one or more computer programs are stored in the internal memory 121 and configured to be executed by one or more processors 110. The one or more computer programs include instructions that can be used to perform the various steps in the following embodiments.

[0127] Of course, the algorithm code of the embodiment of this application can also be stored in external memory. In this case, the processor 110 can run the algorithm code of the embodiment of this application stored in external memory through the external memory interface 120.

[0128] A touch sensor, also known as a "touch panel". The touch sensor can be set on the display screen 194, and the touch sensor and the display screen 194 together form a touch display screen, also known as a "touch screen".

[0129] For example, the display screen 194 of the electronic device 100 can display a desktop, on which components of one or more applications can be displayed.

[0130] The wireless communication function of electronic device 100 can be realized through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor, etc.

[0131] The mobile communication module 150 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the electronic 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 via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a 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 for radiation via antenna 1.

[0132] The wireless communication module 160 can provide solutions for wireless communication applications on the electronic device 100, including wireless local area networks (WLAN) (such as wireless fidelity (WiFi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR) technology, etc.

[0133] In addition, the electronic device 100 can implement audio functions such as music playback and recording through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, and an application processor.

[0134] In some embodiments, the electronic device 100 may further include buttons, motors, indicators, etc. The electronic device 100 can receive button input and generate key signal inputs related to user settings and function control of the electronic device 100. The electronic device 100 can utilize a motor to generate vibration alerts (such as vibration alerts for incoming calls). The indicators in the electronic device 100 may be indicator lights, used to indicate charging status, battery level changes, or to indicate messages, missed calls, notifications, etc.

[0135] The SIM card interface 195 in the electronic device 100 is used to connect a SIM card. The SIM card can be inserted into or removed from the electronic device 100 to achieve contact and separation with the electronic device 100.

[0136] It should be understood that, in practical applications, electronic device 100 may include more than Figure 2AThe number of more or fewer components shown is not limited in the embodiments of this application. The illustrated electronic device 100 is merely an example, and the electronic device 100 may have more or fewer components than shown in the figure, may combine two or more components, or may have different component configurations. The various components shown in the figure may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application-specific integrated circuits.

[0137] Please refer to Figure 2B , Figure 2B An exemplary software structure block diagram of an electronic device 100 is shown.

[0138] The electronic device provided in this application embodiment can run an operating system (OS). This operating system can be various operating systems used in industry, such as operating systems developed based on OpenHarmony, like HarmonyOS; or other operating systems such as Android™, iOS mobile operating systems; it can also be various open-source operating systems or their derivatives, such as Linux OS, and other embedded operating systems; or it can be a future new operating system, such as an AI operating system based on artificial intelligence. An operating system is a set of interconnected system software programs that manage and control the operation of electronic devices, utilize and run hardware and software resources, and provide public services to organize user interaction. In electronic devices, the operating system connects downwards to the physical devices at the hardware layer and provides a runtime environment for application software upwards.

[0139] An operating system typically includes a kernel layer, a middleware layer, and an application layer. The application layer includes applications, which can include system applications and third-party applications. The middleware layer includes a suite of software providing various services to application developers, or frameworks providing services such as databases, multimedia, and graphics, or capabilities such as distributed scheduling and system scaling. For example, the middleware layer may include a framework layer and / or a system service layer. The framework layer provides application programming interfaces (APIs) and programming frameworks for applications in the application layer. The system service layer includes the system's core capabilities, providing services to applications through the framework layer. The kernel layer is the layer between hardware and software. The kernel layer may include hardware drivers and the operating system kernel. In addition to providing hardware drivers, the kernel layer also supports functions such as memory management and system process management.

[0140] The electronic devices we use in our daily lives come in various types and forms, and are applied in a wide range of scenarios. Therefore, based on the different forms and functions of electronic devices, different application scenarios, and different user needs, the operating systems used in these devices may also differ. The basic functions implemented by the electronic device provided in this application can be implemented using a general-purpose operating system or a dedicated operating system. To more clearly illustrate the implementation of the embodiments of this application under a specific operating system, the architecture of HarmonyOS is shown below. Those skilled in the art can deduce the implementation of the embodiments of this application under other specific operating systems, such as Android™.

[0141] like Figure 2B As shown, the software architecture of an electronic device can be divided into several layers. In some embodiments, from bottom to top, these layers are: kernel layer, system service layer, framework layer, and application layer. Layers communicate with each other through software interfaces. System functions can be tailored, added, or combined at the subsystem granularity in different device deployment scenarios, and each subsystem can also be tailored, added, or combined at the functional granularity.

[0142] The Kernel Abstraction Layer (KAL) provides basic kernel capabilities to upper layers by shielding the differences between multiple kernels, including but not limited to process / thread management, memory management, file system, network management, and peripheral device management.

[0143] Kernel Subsystem: Supports the selection of a suitable OS kernel for different resource-constrained devices, including but not limited to Linux kernel, HarmonyOS kernel, LiteOS (Lite Operating System), etc.

[0144] Driver Subsystem: The driver framework is the foundation for the open system hardware ecosystem, providing unified peripheral access capabilities and a framework for driver development and management. The driver framework includes: display drivers, camera drivers, audio drivers, Bluetooth drivers, sensor drivers, etc.

[0145] The system service layer comprises the core capabilities of the system, providing services to applications through the framework layer. This layer includes, but is not limited to, the following subsystems:

[0146] The system's basic capability subsystem set provides fundamental capabilities for the operation, scheduling, and migration of distributed applications across multiple devices. This set may include distributed soft bus, distributed data management, distributed task scheduling, and Ark multi-language runtime; it may also include multi-modal input subsystem, graphics subsystem, security subsystem, and AI sub-business system.

[0147] Basic software service subsystem set: provides public and general software services; the basic software service subsystem set may include event notification subsystem, telephone service subsystem, multimedia subsystem, etc.

[0148] Enhanced software service subsystem suite: Provides differentiated enhanced software services for different devices; the enhanced software service subsystem suite may include smart screen proprietary business subsystem, wearable proprietary business subsystem, IoT proprietary business subsystem, etc.

[0149] Hardware service subsystem set: Provides hardware services; the hardware service subsystem set may include location service subsystem, user IAM (Identity and Access Management) subsystem, wearable proprietary hardware service subsystem, biometric identification, IoT proprietary hardware service subsystem, etc.

[0150] Distributed task scheduling enables distributed service management (discovery, synchronization, registration, and invocation), supporting remote startup, remote invocation, remote connection, and migration of applications across devices.

[0151] Distributed data management enables data synchronization, data storage, data sharing, and data access across all scenarios and devices.

[0152] The distributed soft bus provides communication-related capabilities for seamless interconnection between multiple devices, including: WLAN service capabilities, Bluetooth service capabilities, soft bus, inter-process communication (IPC), and StarFlash communication capabilities.

[0153] Ark Multilingual Runtime is a unified compilation runtime platform designed to support the joint compilation and execution of multiple programming languages ​​and multiple chip platforms.

[0154] The framework layer provides application programming interfaces (APIs) and programming frameworks for applications in the application layer. The framework layer includes: the ArkUI framework (which provides a complete infrastructure for UI development of system applications, including UI functions such as components, layouts, animations, and interactive events, as well as a real-time interface preview tool), the component framework (Form Kit), the component rendering service (Form Render Service), the component management service (FormManager Service), the package management service (Bundle Manager Service), the user application framework, and the Ability framework (an Ability is a lightweight application; the Ability framework schedules and manages the operation and lifecycle of Abilities). Different devices may have different operating systems, and the APIs they support may also differ.

[0155] like Figure 2B As shown, Form Kit also provides a dynamic component extension module (LiveFormExtensionAbility). The operating system of electronic device 100 can also provide interface extension capabilities (UIExtensionAbility) (not shown in the figure), and LiveFormExtensionAbility can be a subclass of UIExtensionAbility. Since UIExtensionAbility is a capability of the operating system of electronic device 100 and cannot be used by applications in the application layer, LiveFormExtensionAbility can inherit from UIExtensionAbility, allowing applications in the application layer to call LiveFormExtensionAbility and develop 3D components based on LiveFormExtensionAbility. In other words, applications in the application layer can call UIExtensionAbility and develop 3D components based on UIExtensionAbility.

[0156] Form Kit can also provide an overflow interface, which allows component users to call to request the extended playback duration of component data from the component management service, or to request the extended playback duration and overflow area of ​​component data, etc.

[0157] Form Kit includes a FormInfo file, which stores the component's attribute information. For example, electronic device 100 can write the attribute information of a first component provided by a first application into the FormInfo file through the component management service. Electronic device 100 can also send the attribute information of the first component to the component user through the component management service. The component user can then create the first component based on the first component's attribute information.

[0158] Optionally, the properties of the first component can also be modified by the developer.

[0159] The component management service is used to store the attribute information of the first component.

[0160] Component management services are used to manage the lifecycle of components. For example, component management services can toggle the display state of components, control the display and hiding of ordinary components, and control the display, hiding, and destruction of extended components.

[0161] The component rendering service is used to render the ordinary component data provided by the component provider, obtain the ordinary component content, and display the ordinary component content in the ordinary component.

[0162] The component rendering service is also used to interact with component providers, enabling them to render the content of extended components based on the extended component data and display the extended component content within the extended component.

[0163] The component rendering service is also used to obtain messages about the switching of the component's display state, and after obtaining such messages, it sends a message to the component management service to instruct the component management service to switch the component's display state.

[0164] The package management service is used to manage the installation and package resource parsing of various applications in the application layer. Optionally, the package management service includes the installation package of the first application, which includes the installation files of the first application and the attribute information of the first component provided by the first application.

[0165] ArkUI includes code files for Form Components, which in turn include code files for regular components (RSSurface Nodes) and extended components (UIExtension Components). The RSSurface Node code files enable users to create regular components to achieve the same display capabilities. The UIExtension Component code files enable users to create extended components to achieve the same display capabilities.

[0166] The HarmonyOS API is a series of open capabilities provided to support HarmonyOS application development. The HarmonyOS API can be set at the framework layer or independently of the framework layer. The HarmonyOS API includes the Audio API (audio service), Push API (push service), and Account API (account service), among others.

[0167] Applications can include component users and component providers. Component users can be system applications of electronic device 100, such as desktop applications, negative one screen applications, etc. Component providers can be applications installed on electronic device 100. Component providers can be third-party applications or non-third-party applications. Among them, third-party applications can refer to applications not developed by the developer of electronic device 100, and non-third-party applications can refer to applications developed by the developer of electronic device 100.

[0168] In some embodiments, the type of the first component may include an interactive component and a scene animation component. An interactive component refers to a first component that requires user input to switch its display state. A scene animation component refers to a first component that can automatically switch its display state without requiring user input. This application will describe the display effects of these two types of components separately.

[0169] I. Fun Interactive Components.

[0170] 1. Electronic device 100 acquires and saves the attribute information of the first component provided by the first application.

[0171] In some embodiments, when the first application is installed on the electronic device 100, if the first application has developed a first component, the electronic device 100 can obtain the installation package of the first application. The installation package of the first application may include the installation file of the first application, ordinary component data, dynamic component extension module and attribute information of the first component.

[0172] Figure 3A A schematic diagram of software interaction is shown for an electronic device 100 that acquires and saves attribute information of a first component provided by a first application.

[0173] like Figure 3A As shown, the electronic device 100 includes an application layer and an application framework layer. The application layer includes component users (e.g., the desktop) and component providers (e.g., the first application). The application framework layer includes a package management service.

[0174] 1. Electronic device 100 can receive and respond to the operation of installing the first application, obtain the installation package of the first application, and install the first application.

[0175] 2. Electronic device 100 stores the installation package of the first application in the package management service.

[0176] 3. The package management service sends the attribute information of the first component to the component management service.

[0177] like Figure 3A As shown, the installation package of the first application may include, but is not limited to, the installation file of the first application and the property information of the first component. The installation file of the first application is used to install the first application and implement its functions. The property information of the first component is used by the component user to create the first component.

[0178] Optionally, the installation package of the first application may also include ordinary component data and dynamic component extension modules (not shown in the figure). The dynamic component extension module may include a rendering engine and extension component data, which is used to render the extension component content. In other embodiments, if the first component is a scene animation component, the dynamic component extension module may only include the rendering engine, and the first application may periodically / irregularly obtain extension component data from the content provider. If the first component is a scene animation component, the dynamic component extension module may also include extension component data, and the first application does not need to obtain the extension component data from the content provider.

[0179] If the first component is a non-3D component, such as a non-scene animation component or a non-fun interactive component, the attribute information of the first component may only include the attribute information of ordinary components.

[0180] If the first component is a 3D component, such as a scene animation component or a fun interactive component, the attribute information of the first component can include the attribute information of the ordinary component and the attribute information of the extended component. The ordinary component information can include, but is not limited to, any one or more of the following: the size, shape, color, transparency of the ordinary component, and information about the application to which the ordinary component belongs (such as the application's identifier).

[0181] The attribute information of the extended component may include, but is not limited to, any one or more of the following: the type of the extended component, the name of the dynamic component extension module that the extended component depends on, the name of the installation package of the application to which the extended component belongs, and the timeout pause duration. The electronic device 100 can obtain the dynamic component extension module based on its name. The electronic device can then render the extended component data using the rendering engine within the dynamic component extension module, obtain the extended component content, and display the extended component content. When the duration for which the extended component content is displayed exceeds the timeout pause duration, the electronic device 100 can stop displaying the extended component content and begin displaying the content of a regular component, thus saving power consumption.

[0182] For example, the installation package of the first application may include a WidgetCard.ets file, a form_config.json file, and a LiveFormExtensionAbility file. The ordinary component data of the first component can be stored in the WidgetCard.ets file. The attribute information of the extended components can be stored in the form_config.json file. Dynamic component extension modules can be implemented through the LiveFormExtensionAbility file.

[0183] For example, when the first component is a fun interactive component, the form_config.json file may include the following fields, with different fields used to indicate different attribute information of the extended components.

[0184] "funInteractionParams":{

[0185] "abilityName":"xxxAbility",

[0186] "targetBundleName":"xxx.xxx.xxx",

[0187] "keepStateDuration":10,

[0188] }

[0189] The `funInteractionParams` field indicates that the first component is a fun interactive component. The `abilityName` field indicates the name of the dynamic component extension module that the extension component depends on. The `targetBundleName` field indicates the name of the installation package of the application to which the extension component belongs. The `keepStateDuration` field indicates the timeout pause duration, for example, the timeout pause duration can be 1 minute.

[0190] Optionally, in addition to the above-mentioned attribute information, the attribute information of extended components may also include other attribute information, such as the size, shape, color, and transparency of the extended component.

[0191] Optionally, the properties of the first component can also be modified by the developer.

[0192] Figure 3B A flowchart illustrating a method for an electronic device 100 to acquire and save attribute information of a first component provided by a first application is shown.

[0193] S301A, Electronic Device 100 receives user operations from the user who has installed the first application.

[0194] S302A, Electronic device 100 sends information about the first application to the content provider.

[0195] S303A, Electronic device 100 receives the installation package of the first application sent by the content provider.

[0196] Electronic device 100 can receive user operations related to installing the first application. In response to these operations, electronic device 100 can send information about the first application to a content provider. This information may include, but is not limited to, the application's identifier and the developer's name. The content provider can then obtain the installation package of the first application based on this information and send it to electronic device 100.

[0197] S304A, Electronic Device 100 saves the installation package of the first application to the package management service.

[0198] S305A, Electronic Device 100 Installation First Application.

[0199] After receiving the installation package of the first application sent by the content provider, the electronic device 100 can install the first application and save the installation package of the first application to the package management service.

[0200] S306A, Package Management Service sends the attribute information of the first component to Component Management Service.

[0201] In some embodiments, after obtaining the installation package of the first application, the electronic device 100 can parse the installation package of the first application to obtain the attribute information of the first component.

[0202] Optionally, the electronic device 100 can parse the installation package of the first application through the package management service to obtain the attribute information of the first component. After obtaining the attribute information of the first component, the package management service can send the attribute information of the first component to the component management service.

[0203] After obtaining the attribute information of the first component, the component management service can write the attribute information of the first component into the FormInfo file in the component management service.

[0204] Optionally, the electronic device 100 can also parse the installation package of the first application through the component management service to obtain the attribute information of the first component.

[0205] Optionally, the component management service can also send the attribute information of the first component to the card user, so that the card user can obtain the attribute information of the first component and create the first component based on the attribute information of the first component.

[0206] Optionally, the component management service can also send the attribute information of the first component to Form Kit, which can then write the attribute information of the first component into the FormInfo file within Form Kit.

[0207] Thus, when the first application is installed on the electronic device 100, the electronic device 100 can... Figure 3A and Figure 3B The method shown retrieves the attribute information of the first component.

[0208] In other embodiments, after the first application is installed on the electronic device 100, if the developer of the first application develops a first component, the electronic device 100 can also obtain the attribute information of the first component.

[0209] Figure 3C A schematic diagram of the software interaction of another electronic device 100 acquiring and saving attribute information of a first component is shown.

[0210] like Figure 3C As shown, the electronic device 100 includes an application layer and an application framework layer. The application layer includes component users (e.g., the desktop) and component providers (e.g., the first application). The application framework layer includes a package management service.

[0211] 1. The first application obtains data on ordinary components, extended components, the rendering engine, and the attribute information of the first component from the content provider.

[0212] 2. The first application stores the attribute information of the first component in the package management service.

[0213] 3. The package management service sends the attribute information of the first component to the component management service.

[0214] Figure 3D A flowchart illustrating a method for another electronic device 100 to acquire and save attribute information of a first component is shown.

[0215] S301B, the first application obtains ordinary component data, extended component data, rendering engine and attribute information of the first component from the content provider.

[0216] S302B, The first application saves the attribute information of the first component to the package management service.

[0217] S303B, Package Management Service sends the attribute information of the first component to Component Management Service.

[0218] It is understandable that the content provider can be a server. After the first application is installed on the electronic device 100, if the developer of the first application develops the first component, the developer can store the ordinary component data, extended component data, rendering engine, and attribute information of the first component in the content provider. The first application can obtain the ordinary component data, extended component data, rendering engine, and attribute information of the first component from the content provider.

[0219] After the first application obtains the data for ordinary components, extended components, the rendering engine, and the attribute information of the first component from the content provider, it can save the attribute information of the first component in the package management service. The package management service then sends the attribute information of the first component to the component management service.

[0220] In this way, after the first application is installed on the electronic device 100, the electronic device 100 can also be accessed via... Figure 3C and Figure 3D The method shown retrieves the attribute information of the first component.

[0221] 2. The electronic device 100 receives the user's operation, adds the first component to the desktop, and displays the normal component content of the first component on the electronic device 100.

[0222] Figures 4A-4F This diagram illustrates an electronic device 100 receiving a user operation and adding a first component to the desktop.

[0223] like Figure 4A As shown, the electronic device 100 displays a desktop, which includes: a status bar 1001, a calendar indicator, a weather indicator, a tray 1004 with icons for frequently used applications, and other application icons 1002. Among them:

[0224] Other application icons 1002 may include email application icons, cloud sharing application icons, memo application icons, settings application icons, etc. Below these application icons, a page indicator 1003 may also be displayed to indicate the positional relationship between the currently displayed page and other pages. Below the page indicator is a tray icon 1004 containing frequently used application icons, which may include camera application icons, contacts application icons, messaging application icons, and dialer application icons. The application icons remain displayed when switching pages.

[0225] Electronic device 100 can detect user actions performed on the gallery application icon, and in response to the action, electronic device 100 can display... Figure 4B The page editing interface shown is illustrated. The electronic device 100 allows users to drag pages and change the hierarchical relationship between multiple pages.

[0226] Figure 4BThe page editing interface shown also includes wallpaper settings option 1005, card settings option 1006, icon settings option 1007, and theme settings option 1008. Users can set the wallpaper for the electronic device 100 using wallpaper settings option 1005. Users can add application-provided cards to the desktop using card settings option 1006. Users can add or remove application icons on various pages using icon settings option 1007. Users can set the theme background for the electronic device 100 using theme settings option 1008.

[0227] like Figure 4B and Figure 4C As shown, the electronic device 100 can receive user input operations for the card setting option 1006, such as a click operation. In response to the user's input operation, the electronic device 100 can display... Figure 4C The card settings interface shown is 1009.

[0228] like Figure 4C As shown, the card settings interface 1009 includes one or more application options. The electronic device 100 can receive user input to add the components provided by the applications corresponding to these one or more application options to the desktop. For example, the one or more application options may include options for Huawei Video, Huawei Music, Weather, Calendar, Mini Games, Health & Fitness, and Xiaoyi (AI) services.

[0229] like Figure 4C and Figure 4D As shown, the electronic device 100 can receive user input operations for the option 1010 of the mini-game application, such as a click operation. In response to the user's input operation, the electronic device 100 can display... Figure 4D The card adding interface shown is 1011.

[0230] like Figure 4D As shown, the card adding interface 1011 includes a card 1012 and an adding option 1013. Card 1012 is used to indicate the display style of the mini-game components provided by the mini-game application. The mini-game components provided by the mini-game application can be added to the desktop via the adding option 1013.

[0231] like Figure 4D and Figure 4E As shown, the electronic device 100 can receive user input for the added option 1013, such as a click operation. In response to the user's input, the electronic device 100 can display... Figure 4E The page editing interface shown. Figure 4E The page editing interface shown and Figure 4B The page editing interfaces shown are similar, the difference being that... Figure 4E The page editing interface shown also includes a display area 1014, which displays the content of ordinary components of the mini-game components provided by the mini-game application. For example, the content of ordinary components may include images containing game characters.

[0232] like Figure 4E and Figure 4F As shown, the electronic device 100 can receive swiping operations from the user on the page editing interface, such as swiping upwards from the bottom of the page editing interface. In response to the user's swiping operation, the electronic device 100 can display... Figure 4F The desktop shown is Figure 4F The desktop shown includes a display area 1015, which displays the normal component content of the mini-game components provided by the mini-game application.

[0233] In some embodiments, the electronic device 100 may receive user input on the display area 1015 and begin displaying extended content of the mini-game component. See also... Figures 6A-6D Description in the embodiments.

[0234] Optionally, the application-provided components can be added not only to the desktop, but also to the display area. This application only uses the desktop as an example and does not constitute a limitation.

[0235] Figure 5A A schematic diagram of software interaction is shown for an electronic device 100 displaying the contents of a common component of a first component.

[0236] like Figure 5A As shown, the electronic device 100 includes an application layer and a framework layer. The application layer includes component users and component providers, and the framework layer includes component management services and component rendering services.

[0237] Figure 5A The software interaction shown may include, but is not limited to, the following steps:

[0238] 1. The component management service sends the attribute information of the first component to the component user.

[0239] 2. The component user receives the user's action of adding the first component to the desktop, hides the regular component, and shows the extended component.

[0240] 3. The component uses the component management service to send messages 16.

[0241] 4. The component management service sends message 17 to the component rendering service.

[0242] 5. The component rendering service obtains the first ordinary component data from the component provider.

[0243] 6. The component rendering service renders the data of the first ordinary component and displays the content of the first ordinary component in the ordinary component.

[0244] In some embodiments, the first general component data or the second general component data (in...) Figure 10A or Figure 10B (As mentioned in the text) can also be referred to as the first data. The first ordinary component content or the second ordinary component content (in...) Figure 10A or Figure 10B (As mentioned in the text) can also be referred to as the first data.

[0245] Figure 5B A flowchart illustrating a method for an electronic device 100 to display the contents of a common component of a first component is shown.

[0246] like Figure 5B As shown, the electronic device 100 includes a component user, a component provider, a component management service, and a component rendering service. Figure 5B The software interaction shown may include, but is not limited to, the following steps:

[0247] S501, The component management service sends the attribute information of the first component to the component user.

[0248] The first component can include regular components and extended components. The attribute information of the first component can include the attribute information of both the regular and extended components. The attribute information of the regular and extended components can be found by referring to... Figure 3A The description in the text.

[0249] Optionally, if the first component is a 3D component, the component user (e.g., the first application) can be a third-party application. The electronic device 100 can also obtain attribute information of the 3D component displayed by the electronic device 100 provided by the third-party application, and create and display the 3D component of the third-party application based on the attribute information of the first component provided by the third-party application. Formkit can provide a Live Form Extension Ability, which the third-party application can call to develop the resources required for the electronic device 100 to display the 3D component. For example, resources may include attribute information and data of ordinary components, attribute information and data of extended components, rendering engines, etc. The electronic device 100 can invoke the Live Form Extension Ability in the third-party application to display the ordinary component content of the 3D component of the third-party application based on the ordinary component data, or to display the extended component content of the 3D component of the third-party application based on the extended component data.

[0250] Formkit provides the Formkit interface, which third-party applications can call to communicate with the framework layer, enabling the framework layer to communicate with third-party applications through the Formkit interface.

[0251] For example, when an electronic device displays the content of an extension component, the framework layer (such as a card management service and / or a card rendering service) can invoke the Live FormExtension Ability in the third-party application process via the Formkit interface to display the extension component and hide the regular component. The Live FormExtension Ability in the third-party application process can display the content of the extension component within the extension component based on the extension component data provided by the Live Form Extension Ability.

[0252] When the electronic device displays the first content of a regular component, the framework layer (such as the card management service and / or card rendering service) can use the Formkit interface to pause or destroy the Live Form Extension Ability in the third-party application process, hide or destroy the extension component, and display the regular component. The framework layer (such as the card management service and / or card rendering service) can obtain the regular component data from the third-party application through the Formkit interface and display the regular component content in the regular component based on the regular component data.

[0253] S502: The component user receives the user's action of adding the first component to the desktop, hides the normal component, and displays the extended component.

[0254] For example, the component user can be the desktop. In response to a user action of adding the first component to the desktop, the desktop displays the normal component content of the first component by default. The desktop can hide the extended component and display the normal component, which is used to display the normal component content.

[0255] For example, the user actions of adding the first component to the desktop can be referred to Figures 4A-4F The introduction in the text.

[0256] In some embodiments, before adding the first component to the desktop, the component user can create the first component based on its attribute information. If the component user confirms that the first component is a 3D component based on its attribute information, the electronic device 100 can create the first component. The first component may include a regular component and an extended component. The regular component can be displayed, and the extended component can be hidden. The electronic device 100 can display the content of the regular component within the regular component. If the component user confirms that the first component is a non-3D component based on its attribute information, the electronic device 100 can create the first component. The first component may include a regular component. The regular component can be displayed, and the electronic device 100 can display the content of the regular component within the regular component.

[0257] For example, before adding the first component to the desktop, the electronic device 100 can display... Figure 4C The card settings interface 1009 is shown. The electronic device 100 can receive user settings... Figure 4C The input operation of option 1010 in the mini-game application shown can, in response to the operation, allow the electronic device 100 to obtain the attribute information of the mini-game component and determine whether the mini-game component belongs to a 3D component (such as a fun interactive component or a scene interactive component) based on the attribute information of the mini-game component.

[0258] If the electronic device 100 confirms that the mini-game component is a 3D component, it can create a first component, which may include a regular component and an extended component. The electronic device 100 can display the regular component and hide the extended component. After obtaining the content of the regular component, the electronic device 100 can display that content within the regular component. For example, the electronic device 100 can display... Figure 4D The card adding interface 1011 shown contains card 1012. Card 1012 can be the content of a regular component corresponding to a regular component.

[0259] If the electronic device 100 determines that the mini-game component is not a 3D component, the electronic device 100 can create a first component, which may include a regular component. The electronic device 100 can display the regular component. After obtaining the content of the regular component, the electronic device 100 can display the content of the regular component within the regular component.

[0260] S503, The component uses the direction of the component management service to send message 16.

[0261] S504, The component management service sends message 17 to the component rendering service.

[0262] S505, The component rendering service obtains the first ordinary component data from the component provider.

[0263] Optionally, the component provider may include a first interface, which can be used for data transfer between the component rendering service and the component provider. For example, the component rendering service can obtain first ordinary component data from the component provider through the first interface. If the component provider is a third-party application, the third-party application can transfer the first ordinary component data to the component rendering service in the framework layer through the first interface, and the electronic device 100 can also display the ordinary component content of the third-party application.

[0264] S506, The component rendering service renders the data of the first ordinary component and displays the content of the first ordinary component in the ordinary component.

[0265] In response to a user action of adding a component of the first application to the desktop, the component user can send message 16 to the component management service, which in turn sends message 17 to the component rendering service. In response to message 17, the component rendering service can obtain the first ordinary component data from the component provider.

[0266] Optionally, messages 16 and 17 may carry information about the first application, such as the identifier of the first application and / or the ID of the first component. The information about the first application is used by the component rendering service to obtain ordinary component data from the component provider (the first application).

[0267] Optionally, message 16 and message 17 can be the same message or different messages.

[0268] After obtaining the data for the first ordinary component, the component rendering service can render the data to obtain the content of the first ordinary component. Then, the component rendering service can display the content of the first ordinary component within the ordinary component.

[0269] pass Figures 5A-5B The method shown allows the electronic device 100 to render first ordinary component data and display the first ordinary component content of the first component via a component rendering service.

[0270] 3. The first component switches between different display states.

[0271] The display state of the first component may include, but is not limited to, inactive, active, and paused states.

[0272] The inactive state indicates that the first component is not activated. While the first component is in the inactive state, the electronic device 100 can display the normal component content of the first component.

[0273] The active state can refer to the first component being activated and in use. While the first component is in the active state, the electronic device 100 can display the extended component content of the first component.

[0274] A paused state can refer to a situation where, while the first component is in an active state, the electronic device detects an event that the first component has been paused, and the first component can enter a paused state. While the first component is in a paused state, the electronic device 100 can then resume displaying the normal component content of the first component.

[0275] Figure 5C Several examples are shown of the first component switching between different display states.

[0276] Example 1: When an event is detected that the first component has entered an inactive state, the electronic device 100 can display the normal component, hide the extended component, and display the normal component data in the normal component.

[0277] Example 2: When an event is detected in which the first component switches from an inactive state to an active state, the electronic device 100 can hide the normal component, display the extended component, and display the extended component data in the extended component.

[0278] Example 3: When an event is detected that the first component has switched from an active state to a paused state, the electronic device 100 can display the normal component, hide the extended component, and display the normal component data in the normal component.

[0279] Example 4: When an event is detected that the first component has switched from a paused state to an active state, the electronic device 100 can hide the normal component, display the extended component, and display the extended component data in the extended component.

[0280] Example 5: When an event is detected in which the first component switches from an active state to an inactive state, the electronic device 100 can display the normal component, destroy the extended component, and display the normal component data in the normal component.

[0281] Example 6: When an event is detected that the first component has switched from a paused state to an inactive state, the electronic device 100 can display the normal component, destroy the extended component, and display the normal component data in the normal component.

[0282] The following will discuss... Figure 5C Each example in the document is explained in detail.

[0283] Example 1: After detecting that the first component has entered the inactive state, the electronic device 100 can display the normal component, hide the extended component, and display the normal component data in the normal component.

[0284] Optionally, the event that the first component enters the inactive state may include, but is not limited to, the event of adding the first component to the display area of ​​the component user.

[0285] After detecting that the first component has entered an inactive state, how the electronic device 100 displays the data of the ordinary component in the ordinary component section can be found in [reference needed]. Figure 5A and Figure 5B The specific embodiments are described in detail herein, and will not be repeated here.

[0286] Example 2: After detecting an event that the first component switches from an inactive state to an active state, the electronic device 100 can hide the normal component, display the extended component, and display the extended component data in the extended component.

[0287] Optionally, the event that causes the first component to switch from an inactive state to an active state may include, but is not limited to: detecting a user's touch operation on the first component, detecting the user's gaze on the first component, etc.

[0288] Figures 6A-6E A schematic diagram is shown showing an electronic device 100 displaying extended component data in an extended component after detecting an event that the first component switches from an inactive state to an active state.

[0289] For example, the first component can be a game component provided by the game application, and the extended component data can be game content.

[0290] like Figures 6A-6B As shown, the first component is in an inactive state, and the electronic device 100 displays the normal component content of the first component in the display area 1015. The electronic device 100 can receive user input operations on the display area 1015, such as a click operation. In response to the user's input operation, the electronic device 100 can switch the first component from an inactive state to an active state.

[0291] After the first component enters the active state, the electronic device 100 can display the content of the extended component in the extended component of the first component. The content of the extended component can be found in [reference]. Figures 6B-6E The data displayed by the electronic device 100.

[0292] like Figure 6B As shown, the display area 1015 displays a progress bar 6002 and a pause / play option 6004. The black area in the progress bar 6002 gradually expands until the progress bar 6002 is completely black, at which point the electronic device 100 can display... Figure 6C The content shown. Figure 6B The pause / on option 6004 is shown as active, indicating that the content displayed in the display area 1015 can be refreshed periodically / irregularly. In some embodiments, the electronic device 100 can receive user input on the pause / on option 6004, such as a click. In response to the user's input, the pause / on option 6004 can be displayed as active, and the electronic device 100 can also switch the first component to a paused state, and the electronic device 100 stops refreshing the content in the display area 1015.

[0293] like Figures 6C-6E As shown, the extended component content can include game characters 6005, game items 6006, game items 6007, game duration 6003, pause / start option 6004, etc. The number displayed in game duration 6003 can increase as time increases; for example, the number displayed in game duration 6003 can be 1, 2, 3, etc.

[0294] from Figures 6B-6E As can be seen, the display positions of game character 6005, game item 6006, and game item 6007 are different at different times.

[0295] For example, such as Figure 6C As shown, the game character 6005 can be positioned above the game item 6007. The game item 6006 can be positioned outside the display area of ​​the display area 1015.

[0296] like Figure 6D As shown, the game character 6005 can bounce upwards, and the game item 6006 can be moved to the display area 1015.

[0297] like Figure 6E As shown, game item 6006 can be stacked on top of game item 6007, and game character 6005 can be positioned on top of game item 6006.

[0298] Similarly, after the first component enters the active state, the electronic device 100 can refresh and display different content.

[0299] Optional, from Figures 6A-6E It can be seen that after the first component enters the active state, the display area of ​​the electronic device 100 displaying the content of the extended component can be different from the display area 1015. For example, the size of the display area of ​​the electronic device 100 displaying the content of the extended component can be larger than the size of the display area 1015. In other words, the content of the extended component can overflow the display area 1015.

[0300] Optionally, after the first component enters the active state, the size of the display area of ​​the electronic device 100 displaying the content of the extended component can also be the same as the size of the display area 1015.

[0301] Figures 7A-7C Another set of diagrams shows the electronic device 100 displaying extended component data in the extended component after detecting an event that the first component switches from an inactive state to an active state.

[0302] For example, the first component could be a theme component provided by a theme application, and the extended component data could be a pet. The electronic device 100 could be a vehicle infotainment system.

[0303] like Figure 7A As shown, the electronic device 100 includes a display area 7001. The first component is inactive. The display area 7001 displays a confirmation option 7002, a pet image 7003, a "switch to previous theme" option 7005, and a "switch to next theme" option 7004. The user can change the theme of the electronic device 100 to the pet theme displayed in the display area 7001 using the confirmation option 7002. The electronic device 100 can receive and respond to the user's input operation for the "switch to previous theme" option 7005, displaying the content of the previous theme in the display area 7001. The electronic device 100 can also receive and respond to the user's input operation for the "switch to next theme" option 7004, displaying the content of the next theme in the display area 7001.

[0304] like Figures 7A-7B As shown, if the user confirms use Figure 7A The electronic device 100 can receive user input for the selection option 7002, such as a click operation. In response to the user's input operation, the electronic device 100 can change the theme of the electronic device 100 to the pet theme displayed in the display area 7001.

[0305] In response to the user's input operation on the selected option 7002, the electronic device 100 can switch the first component from an inactive state to an active state.

[0306] After the first component enters the active state, the electronic device 100 can display the content of the extended component in the extended component of the first component. The content of the extended component can be found in [reference]. Figures 7B-7C The data displayed by the electronic device 100.

[0307] like Figures 7B-7C As shown, the extended component content can include a pet image 7003, and the position of the pet image 7003 displayed is different at different times.

[0308] like Figure 7B As shown, the display area of ​​the extended component content can include Figure 7B The pet image 7003 can be displayed in the shown display area 7006. Figure 7B The location shown.

[0309] like Figure 7C As shown, the display area of ​​the extended component content can include Figure 7C The display area 7007 shown is larger than the display area 7006, and the pet image 7003 can be displayed thereon. Figure 7C The location shown is where pet image 7003 is located. Figure 7C The location and pet image 7003 shown are in Figure 7BThe positions shown are different.

[0310] Optional, from Figures 7A-7C It can be seen that after the first component enters the active state, the display area of ​​the electronic device 100 displaying the content of the extended component can be different from the display area 7001. For example, the size of the display area of ​​the electronic device 100 displaying the content of the extended component can be larger than the size of the display area 7001. In other words, the content of the extended component can overflow the display area 7001.

[0311] Optionally, after the first component enters the active state, the size of the display area of ​​the electronic device 100 displaying the content of the extended component can also be the same as the size of the display area 7001.

[0312] Figure 8A The diagram illustrates a software interaction whereby an electronic device 100 displays data of an extended component in an extended component after detecting an event that the first component has switched from an inactive state to an active state.

[0313] like Figure 8A As shown, the electronic device 100 includes an application layer and a framework layer. The application layer includes component users (e.g., the desktop) and component providers (e.g., the first application). Both the component users and the component providers can call the Formkit interface (application programming interface, API) provided by Formkit. The framework layer includes component management services and component rendering services.

[0314] Optionally, Formkit can provide a Live Form Extension Ability, which component providers can call to develop 3D components. In some embodiments, the operating system of the electronic device 100 can also provide a UI Extension Ability. Since the UI Extension Ability is a capability of the electronic device 100's operating system and cannot be used by applications in the application layer, LiveFormExtensionAbility can inherit from UI ExtensionAbility. In other words, component providers can call UI ExtensionAbility to develop 3D components based on it.

[0315] When an electronic device displays the content of an extension component, the framework layer (such as a card management service and / or a card rendering service) can invoke the Live Form ExtensionAbility in the first application process via the Formkit interface to display the extension component and hide the regular component. The Live Form Extension Ability in the first application process can display the content of the extension component within the extension component based on the extension component data provided by the Live Form Extension Ability.

[0316] When the electronic device displays the first content of a regular component, the framework layer (such as the card management service and / or card rendering service) can use the Formkit interface to pause or destroy the Live Form Extension Ability in the application process, hide or destroy the extension component, and display the regular component. The framework layer (such as the card management service and / or card rendering service) can obtain the regular component data from the first application through the Formkit interface and display the regular component content in the regular component based on the regular component data.

[0317] In some embodiments, the FormComponent (first component) contains a UIExtensionComponent child node, which is used to receive and display the content of the extension component provided by the application through LiveFormExtensionAbility. Various users, such as those using the desktop or the negative one screen, can use the FormComponent to display 3D card effects.

[0318] 1. The component rendering service obtains the message that the first component has switched from an inactive state to an active state.

[0319] 2. The component rendering service sends message 18 to the component management service.

[0320] 3. The component management service hides regular components and displays extended components.

[0321] 4. The component rendering service sends message 19 to the component provider.

[0322] 5. The component provider renders the extended component data based on the rendering engine to obtain the extended component content.

[0323] 6. The component provider displays the extended component content in the extended component.

[0324] In some embodiments, extended component data may also be referred to as second data. Extended component content may also be referred to as second content.

[0325] Figure 8B A flowchart illustrating a method for an electronic device 100 to display extended component data in an extended component after detecting an event that a first component switches from an inactive state to an active state is shown.

[0326] S801, the component rendering service obtains the message that the first component has switched from an inactive state to an active state.

[0327] The electronic device 100 can detect the event of a first component switching from an inactive state to an active state through a multi-modal input module. After detecting the event of the first component switching from an inactive state to an active state, the multi-modal input module can send a message to the component rendering service indicating that the first component has switched from an inactive state to an active state.

[0328] For example, a multi-mode input module may include one or more sensors. The multi-mode input module can use sensor data collected by one or more sensors to determine whether an event has been detected in which the first component switches from an inactive state to an active state.

[0329] For an explanation of the event in which the first component switches from an inactive state to an active state, please refer to the description above; this application will not repeat it here.

[0330] Optionally, S801 can also be executed by the component management service. When the component management service receives a message that the first component has switched from an inactive state to an active state, the component management service can send a message to the component rendering service.

[0331] S802, The component rendering service sends information 18 to the component management service.

[0332] S803, the component management service hides ordinary components and displays extended components.

[0333] When the first component is inactive, the component rendering service can confirm whether it has received a message indicating that the first component has switched from inactive to active. If the component rendering service confirms that it has received a message indicating that the first component has switched from inactive to active, the component rendering service can send message 18 to the component management service. Message 18 is used to instruct the component management service to hide the normal component and show the extended component.

[0334] Hiding a regular component means making it invisible, while showing an extended component means making it visible.

[0335] S804, The component rendering service sends information 19 to the component provider.

[0336] Optionally, S804 and S802 can be executed simultaneously. S804 can also be executed before S802.

[0337] S805: The component provider renders the extended component data based on the rendering engine to obtain the extended component content.

[0338] S806. The component provider displays the content of the extended component in the extended component.

[0339] In response to receiving a message that the first component has switched from an inactive state to an active state, the component rendering service can send information 19 to the component provider.

[0340] As described above, the dynamic component extension module in the component provider includes a rendering engine and extension component data. In response to message 19, the component provider can obtain the extension component data from the dynamic component extension module and render the extension component data based on the rendering engine to obtain the extension component content. Afterwards, the component provider can display the extension component content within the extension component.

[0341] Optionally, the size of the display area for the extended component content displayed by the electronic device 100 may vary at different times.

[0342] Optionally, the display area of ​​the extended component content can be larger than the display area of ​​the regular component content. Alternatively, the display area of ​​the extended component content can be the same size as the display area of ​​the regular component content.

[0343] In some embodiments, after the interactive component enters the active state, the component user can also request the framework layer to extend the overflow area of ​​the component's content, that is, request that the display area of ​​the extended component's content exceed the display area of ​​the extended component. For example, refer to... Figures 17A-17B The descriptions in the document are not repeated here.

[0344] pass Figures 8A-8B The method shown allows the electronic device 100 to confirm whether it has received a message indicating that the first component has switched from an inactive state to an active state through the component rendering service in the framework layer. After confirming that the message has been received, the electronic device 100 can hide the ordinary component and display the extended component through the component management service in the framework layer. In other words, the component user does not need to participate in controlling the display state switching of the first component; the component user does not need to adapt or monitor whether the message indicating that the first component has switched from an inactive state to an active state has been received, thus reducing the workload of developers.

[0345] Example 3: When an event is detected that the first component has switched from an active state to a paused state, the electronic device 100 can display the normal component, hide the extended component, and display the normal component data in the normal component.

[0346] Optionally, the event that causes the first component to switch from an active state to a paused state may include, but is not limited to: the interface where the first component is located is not visible, an operation performed on the first component, the user's gaze being directed at an area outside the first component, an operation performed on an area outside the display area where the first component is located, the duration for which the electronic device 100 displays the content of the extended component in the extended component exceeds the timeout pause duration, and the electronic device 100 does not detect any user operation during the period when the electronic device 100 displays the content of the extended component in the extended component.

[0347] The interface where the first component is located is not visible. It may include the electronic device 100 receiving and responding to user operations and displaying the previous or next page of the interface where the first component is located.

[0348] Operations performed within the display area of ​​the first component may include the electronic device 100 receiving and responding to user input regarding the start / pause option in the first component.

[0349] Operations performed on areas outside the display area where the first component is located may include the electronic device 100 receiving and responding to touch operations performed by the user on areas outside the display area where the first component is located, or may include the user looking at areas outside the display area where the first component is located.

[0350] Figures 9A-9B A schematic diagram is shown showing a group of electronic devices 100 receiving an operation applied to the display area where a first component is located, causing the first component to switch from an active state to a paused state.

[0351] refer to Figures 6A-6E As described in the embodiments, when the first component is in an active state, the electronic device 100 can periodically / irregularly refresh and display the content of the extended component.

[0352] like Figures 9A-9B The electronic device 100 can receive user input for the start / pause option 1016, such as a click. In response to the user's input, the electronic device 100 can switch the first component from an active state to a paused state and display... Figure 9B The interface shown.

[0353] like Figure 9B As shown, the electronic device displays a start / pause option 9002 and a shut-off option 9003 in display area 9001. The start / pause option 9002 is in a paused state, indicating that the first component is in a paused state. The user can use the start / pause option 9002 to reactivate the first component. The user can use the shut-off option 9003 to deactivate the first component.

[0354] Optionally, the size of display area 9001 and the size of display area 1015 can be the same or different.

[0355] Figures 9C-9D A schematic diagram is shown showing a group of electronic devices 100 receiving a user operation that makes the interface where the first component is located invisible, causing the first component to switch from an active state to a paused state.

[0356] like Figures 9C-9D The electronic device 100 can receive a swipe operation from the user on the interface where the first component is located, such as a swipe to the left. In response to the user's swipe operation, the electronic device 100 can display... Figure 9D The interface shown is Figure 9D The interface shown can be the next interface after the interface where the first component is located. Figure 9D The interface shown includes icons for multiple applications, such as a weather app, a clock app, and a calculator app. When the electronic device displays... Figure 9D When the interface shown is displayed, the interface containing the first component is not visible.

[0357] In response to the first component being invisible on the interface, the electronic device 100 can switch the display state of the first component to a paused state. The first component can display something like... Figure 9B The content shown.

[0358] Figure 10A The diagram illustrates a software interaction whereby, after detecting an event that the first component switches from an active state to a paused state, the electronic device 100 displays the content of a normal component in a normal component.

[0359] like Figure 10A As shown, the electronic device 100 includes an application layer and a framework layer. The application layer includes component users (e.g., the desktop) and component providers (e.g., the first application). The framework layer includes component management services and component rendering services.

[0360] 1. The component rendering service receives a message that the first component has switched from the active state to the paused state.

[0361] 2. The component rendering service sends message 20 to the component management service.

[0362] 3. The component management service hides extended components and displays ordinary components.

[0363] 4. The component rendering service sends message 21 to the component provider. Message 21 is used to instruct the component provider to pause the component provider's rendering engine.

[0364] 5. The component rendering service obtains the second ordinary component data from the component provider.

[0365] 6. The component rendering service renders the data of the second ordinary component and displays the content of the second ordinary component in the ordinary component.

[0366] Figure 10B The diagram illustrates a method flow diagram of an electronic device 100 displaying the content of a normal component in a normal component after receiving a message that the first component has switched from an active state to a paused state.

[0367] S1001, The component rendering service receives a message that the first component has switched from the active state to the paused state.

[0368] Optionally, the event of the first component switching from an active state to a paused state can also be detected by the multi-modal input module. See reference... Figure 8B Description in the embodiments.

[0369] For an explanation of the event in which the first component switches from the active state to the paused state, please refer to the description above; this application will not repeat it here.

[0370] S1002, The component rendering service sends information 20 to the component management service.

[0371] S1003, The component management service hides extended components and displays ordinary components.

[0372] When the first component is in an active state, the component rendering service can confirm whether it has received a message indicating that the first component has switched from an active state to a paused state. If the component rendering service confirms that it has received a message indicating that the first component has switched from an active state to a paused state, the component rendering service can send message 20 to the component management service. Message 20 is used to instruct the component management service to hide the extended component and display the normal component. In this way, in response to receiving a message indicating that the first component has switched from an active state to a paused state, on the one hand, the electronic device 100 can hide the extended component. When the first component re-enters the active state, the electronic device 100 can display the extended component again. Compared to creating the extended component, this speeds up the process of the electronic device 100 displaying the extended component data again. On the other hand, after the electronic device 100 hides the extended component, it can stop rendering the extended component data, which also saves the power consumption of the electronic device 100.

[0373] Hiding extended components can refer to setting extended components to an invisible state, while showing normal components can refer to setting normal components to an invisible state.

[0374] S1004. The component rendering service sends message 21 to the component provider. Message 21 is used to instruct the component provider to pause the component provider's rendering engine.

[0375] S1005, The component provider suspends the component provider's rendering engine.

[0376] Optionally, S1004 and S1005 can be omitted. After the component management service hides the extended component, the component provider can automatically pause the component provider's rendering engine.

[0377] S1006, The component rendering service obtains the second ordinary component data from the component provider.

[0378] S1007. The component rendering service renders the data of the second ordinary component and displays the content of the second ordinary component in the ordinary component.

[0379] The component rendering service can obtain the data of the second ordinary component from the component provider, render the data of the second ordinary component, obtain the content of the second ordinary component, and display the content of the second ordinary component in the ordinary component.

[0380] Optionally, the content of the second ordinary component can be the same as or different from the content of the first ordinary component.

[0381] Optionally, the display position of the content of the second ordinary component can be the same as or different from the display position of the content of the first ordinary component.

[0382] Optionally, the size of the display area where the content of the second ordinary component is located can be the same as or different from the size of the display area where the content of the first ordinary component is located.

[0383] Optionally, when the display state of the first component switches from an active state to a paused state, the electronic device 100 may continue to display the content of the second ordinary component in the extended component, not only within the ordinary component. In one possible implementation, the electronic device 100 may display the last frame image displayed by the first component when it was in the active state before the display state of the first component switches to the paused state. In other possible implementations, the electronic device 100 may display a scaled-down image of the last frame image displayed by the first component when it was in the active state. For example, the size of the display area where the scaled-down image is located is the same as the size of the display area where the content of the first ordinary component is located.

[0384] pass Figures 10A-10B The method shown allows the electronic device 100 to confirm whether it has received a message indicating that the first component has switched from an active state to a paused state through the component rendering service in the framework layer. After confirming that the first component has switched from an active state to a paused state, the electronic device 100 can display the regular component and hide the extended component through the component management service in the framework layer. In other words, the component user does not need to participate in controlling the display state switching of the first component; the component user does not need to adapt or monitor whether the message indicating that the first component has switched from an active state to a paused state has been received, thus reducing the workload of developers.

[0385] Example 4: When the event of the first component switching from the paused state to the active state is detected, the electronic device 100 hides the normal component, displays the extended component, and displays the extended component data in the extended component.

[0386] The event that switches the first component from the paused state to the active state may include, but is not limited to, operations that act on the area within the display area where the first component is located.

[0387] The operation performed on the area within the display area where the first component is located may include the electronic device 100 receiving and responding to the user's input operation on the start / pause option in the first component, or it may include the user's gaze being focused on the display area where the first component is located.

[0388] After detecting an event that the first component switches from a paused state to an active state, the electronic device 100 can hide the normal component, display the extended component, and display the extended component data in the extended component.

[0389] Optionally, the electronic device 100 may re-display the first frame image in the extended component data, as well as images after the first frame image.

[0390] Optionally, the electronic device 100 may display content following the last frame of image displayed when the first component is in the active state.

[0391] After detecting an event that the first component switches from a paused state to an active state, the electronic device 100 can refer to the example of how to display the extended component data in the extended component. Figure 8A and Figure 8B The descriptions in the embodiments are not repeated here.

[0392] Example 5: When an event is detected in which the first component switches from an active state to an inactive state, the electronic device 100 displays the normal component, destroys the extended component, and displays the normal component data in the normal component.

[0393] The event that causes the first component to switch from an active state to an inactive state may include, but is not limited to: the shutdown of the first application process, receiving a user operation that causes the second component to enter an active state, etc. The second component and the first component are different components.

[0394] Figure 11A The diagram illustrates a software interaction whereby an electronic device 100 displays data of an extended component in an extended component after detecting an event that the first component has switched from an active state to an inactive state.

[0395] like Figure 11AAs shown, the electronic device 100 includes an application layer and a framework layer. The application layer includes component users (e.g., the desktop) and component providers (e.g., the first application). The framework layer includes component management services and component rendering services.

[0396] 1. The component rendering service receives a message that the first component has switched from an active state to an inactive state.

[0397] 2. The component rendering service sends message 22 to the component management service.

[0398] 3. The component management service displays ordinary components and destroys extended components.

[0399] 4. The component rendering service sends message 23 to the component provider. Message 23 is used to instruct the component provider to destroy the component provider's rendering engine.

[0400] 5. The component rendering service obtains the first ordinary component data from the component provider.

[0401] 6. The component rendering service renders the data of the first ordinary component and displays the content of the first ordinary component in the ordinary component.

[0402] In some embodiments, if the content of the first ordinary component and the content of the second ordinary component are the same, steps 5 and 6 may not be performed.

[0403] Figure 11B A flowchart illustrating a method for an electronic device 100 to display extended component data in an extended component after detecting an event that a first component switches from an active state to an inactive state is shown.

[0404] S1101, The component rendering service receives a message that the first component has switched from an active state to an inactive state.

[0405] Optionally, the event of the first component switching from an active state to a paused state can also be detected by the multi-modal input module. See reference... Figure 8B Description in the embodiments.

[0406] For the event of the first component switching from an active state to an inactive state, please refer to the description above, which will not be repeated here.

[0407] S1102, The component rendering service sends message 22 to the component management service.

[0408] S1103, Component Management Service displays ordinary components and destroys extended components.

[0409] When the first component is in an active state, the component rendering service can confirm whether it has received a message indicating that the first component has switched from an active state to an inactive state. If the component rendering service confirms that it has received a message indicating that the first component has switched from an active state to an inactive state, the component rendering service can send message 22 to the component management service. Message 22 is used to instruct the component management service to display the normal component and destroy the extended component. In this way, in response to detecting an event that switches from an active state to an inactive state, the electronic device 100 can destroy the extended component, saving memory space of the electronic device 100.

[0410] Optionally, in response to detecting an event that switches from an active state to an inactive state, the electronic device 100 may choose not to destroy the extension component, but simply hide it.

[0411] S1104, The component rendering service sends message 23 to the component provider, which instructs the component provider to destroy the rendering engine of the first application.

[0412] S1105, The component provider destroys the rendering engine of the first application.

[0413] Optionally, steps S1104 and S1105 can be omitted. After the component management service destroys the extended component, the component provider can automatically destroy its rendering engine.

[0414] Optionally, S1104 can be executed simultaneously with S1102, or S1104 can be executed before S1102.

[0415] S1106. The component rendering service obtains the first ordinary component data from the component provider.

[0416] S1107. The component rendering service renders the data of the first ordinary component and displays the content of the first ordinary component in the ordinary component.

[0417] pass Figures 11A-11B The method shown allows the electronic device 100 to confirm whether it has received a message indicating that the first component has switched from an active to an inactive state through the component rendering service in the framework layer. After confirming that the first component has switched from an active to an inactive state, the electronic device 100 can display the ordinary component and destroy the extended component through the component management service in the framework layer. In other words, the component user does not need to participate in controlling the display state switching of the first component; the component user does not need to adapt or monitor whether the message indicating that the first component has switched from an active to an inactive state has been received, thus reducing the workload of developers.

[0418] Example 6: When an event is detected that the first component has switched from a paused state to an inactive state, the electronic device 100 displays the normal component, destroys the extended component, and displays the data of the first normal component in the normal component.

[0419] The event that causes the first component to switch from a paused state to an inactive state may include, but is not limited to: the shutdown of the first application process, receiving a user operation that causes the second component to enter an active state, etc.

[0420] After detecting an event that the first component switches from a paused state to an inactive state, the electronic device 100 can refer to the example of how to display the data of the first ordinary component in the ordinary components. Figure 11A and Figure 11B The descriptions in the embodiments are not repeated here.

[0421] In some embodiments, when the first component is in a paused state, the electronic device 100 may display second general component data of the first component. When the first component is in an inactive state, the electronic device 100 may display first general component data of the first component. If the content of the first general component and the content of the second general component are the same, the electronic device 100 may not execute S1106 and S1007.

[0422] II. Scene animation components.

[0423] If the first component is a scene animation component, how does the electronic device 100 obtain the attribute information of the first component? Please refer to [the relevant documentation / reference]. Figures 3A-3D The descriptions in the embodiments are not repeated here.

[0424] The difference between scene animation components and interactive components lies in the type of attribute information of scene animation components and interactive components.

[0425] If the first component is a scene animation component, its attribute information can include the attributes of both regular components and extended components. For an introduction to the attribute information of regular components, please refer to [link / reference needed]. Figure 3A The introduction in the text.

[0426] For example, when the first component is a scene animation component, the form_config.json file may include the following fields, with different fields used to indicate different attribute information of the extended components.

[0427] "sceneAnimationParams":{

[0428] "abilityName":"xxxAbility"

[0429] "isAlwaysActive":false

[0430] "disabledDesktopBehaviors":"SWIPE_DESKTOP|LONG_CLICK|PULL_DOWN_SEARCH"

[0431] }

[0432] The `sceneAnimationParams` field indicates that the first component is a scene animation component. The `abilityName` field indicates the name of the dynamic component extension module that the extension component depends on. The `disabledDesktopBehaviors` field indicates whether the extension component can remain active. If the value of the `disabledDesktopBehaviors` field is not "false", it means that the extension component cannot remain active indefinitely; if the value of the `disabledDesktopBehaviors` field is not "truse", it means that the extension component can remain active indefinitely. The `disabledDesktopBehaviors` field indicates the types of gestures that are disabled: `SWIPE_DESKTOP` indicates a swipe gesture, `LONG_CLICK` indicates a long press gesture, and `PULL_DOWN_SEARCH` indicates a pull-down gesture to display the global search interface.

[0433] Optionally, in addition to the above-mentioned attribute information, the attribute information of extended components may also include other attribute information, such as the size, shape, color, and transparency of the extended component.

[0434] Optionally, the properties of the first component can also be modified by the developer.

[0435] If the first component is a scene animation component, how the electronic device 100 displays the ordinary component content of the first component can be found in the following example. Figures 4A-4F , Figures 5A-5B The descriptions in the embodiments are not repeated here.

[0436] 1. The first component switches between different display states.

[0437] The display state of the first component may include, but is not limited to, inactive and active states.

[0438] When the first component is a scene animation component, the explanation of the display state of the first component can be found in the explanation of the display state of the first component when the first component is a fun interactive component. This application will not repeat it here.

[0439] Figure 12 Several examples of another first component switching between different display states are shown.

[0440] Example 1: When an event is detected that the first component has entered an inactive state, the electronic device 100 can display the normal component, hide the extended component, and display the normal component data in the normal component.

[0441] Example 2: When an event is detected in which the first component switches from an inactive state to an active state, the electronic device 100 can hide the normal component, display the extended component, and display the extended component data in the extended component.

[0442] Example 3: When an event is detected in which the first component switches from an active state to an inactive state, the electronic device 100 can display the normal component, destroy the extended component, and display the normal component data in the normal component.

[0443] The following will discuss... Figure 12 Each example in the document is explained in detail.

[0444] Example 1: When an event is detected that the first component has entered an inactive state, the electronic device 100 can display the normal component, hide the extended component, and display the normal component data in the normal component.

[0445] Optionally, the event that the first component enters the inactive state may include, but is not limited to, the event of adding the first component to the display area of ​​the component user.

[0446] If the event of the first component entering an inactive state is detected, and the electronic device 100 displays the data of a normal component within a normal component, please refer to [the relevant documentation / reference]. Figure 5A and Figure 5B The specific embodiments are described in detail herein, and will not be repeated here.

[0447] Example 2: When an event is detected in which the first component switches from an inactive state to an active state, the electronic device 100 can hide the normal component, display the extended component, and display the extended component data in the extended component.

[0448] Optionally, the event that triggers the first component to switch from an inactive state to an active state may include, but is not limited to, the following: the component user receiving extended component data sent by the content provider.

[0449] In some embodiments, the electronic device 100 may display extension component data in the extension component.

[0450] Figures 13A-13D The diagram illustrates another set of scenarios where, after detecting an event that the first component switches from an inactive state to an active state, the electronic device 100 displays extended component data in the extended component.

[0451] For example, the first component can be a weather component provided by a weather application, and the extended component data can be weather content.

[0452] like Figures 13A-13B As shown, the first component is inactive, and the electronic device 100 displays the normal component content 1302 of the first component in the display area 1301. The normal component content 1302 includes the temperature "15℃-9℃", the weather condition "cloudy turning to light rain" and "northeast wind level 3-4".

[0453] In some embodiments, if the weather conditions are updated, the content provider can obtain the updated weather data and then send it to the component provider. After obtaining the updated weather data, the component provider can activate the first component via electronic device 100 and display the updated weather content based on the updated weather data. The updated weather content can be used for reference. Figures 13B-13D The data displayed by the electronic device 100.

[0454] like Figure 13B As shown, the electronic device 100 can display refreshed weather content 1303 in the display area 1301, and the refreshed weather content 1303 includes cloud animation effects.

[0455] like Figure 13C As shown, the electronic device 100 can display refreshed weather content 1304 in the display area 1301. The refreshed weather content 1304 includes cloud animation and raindrop animation.

[0456] like Figure 13D As shown, the electronic device 100 can display refreshed weather content 1305 in the display area 1301. The refreshed weather content 1305 includes cloud animation, raindrop animation and thunder effect.

[0457] Not limited to Figures 13B-13D The electronic device 100 can display even more refreshed weather information, as shown in the updated weather display. Figures 13B-13D For illustrative purposes only.

[0458] Figures 14A-14C The diagram illustrates another instance where, after detecting an event that the first component switches from an inactive state to an active state, the electronic device 100 displays extended component data in the extended component.

[0459] For example, the first component could be a weather component provided by a weather application, and the extended component data could be weather content. The electronic device 100 could be a vehicle infotainment system.

[0460] like Figure 14AAs shown, the electronic device 100 includes a display area 1401. The first component is in an inactive state, and the display area 1401 displays the general component content 1402 of the first component. The general component content 1402 includes the location "Beijing," the current temperature "23℃," and the temperature and weather conditions corresponding to different times. For example, at 9:00 AM, the weather is "sunny" and the temperature is "5℃." Another example is at 10:00 AM, the weather is "sunny" and the temperature is "6℃." Another example is at 11:00 AM, the weather is "sunny" and the temperature is "7℃." Another example is at 12:00 PM, the weather is "sunny" and the temperature is "8℃." Another example is at 1:00 PM, the weather is "sunny" and the temperature is "8℃."

[0461] refer to Figures 13A-13B As described in the description, if the weather conditions are refreshed, the component provider can activate the first component via electronic device 100 and display the refreshed weather content based on the refreshed weather data. The refreshed weather content can be referenced. Figures 14B-14C The data displayed by the electronic device 100.

[0462] like Figure 14B As shown, the electronic device 100 can display refreshed weather content 1403 in the display area 1401, and the refreshed weather content 1403 includes raindrop animation.

[0463] like Figure 14C As shown, the electronic device 100 can display refreshed weather content 1404 in the display area 1401, and the refreshed weather content 1304 includes lightning effects.

[0464] Not limited to Figure 14B and Figure 14C The electronic device 100 can display even more refreshed weather information, as shown in the updated weather display. Figure 14B and Figure 14C For illustrative purposes only.

[0465] Figure 15A This diagram illustrates another software interaction whereby the electronic device 100 displays data of the extended component in the extended component after detecting an event that the first component has switched from an inactive state to an active state.

[0466] like Figure 15A As shown, the electronic device 100 includes an application layer and a framework layer. The application layer includes component users (e.g., the desktop) and component providers (e.g., the first application). The framework layer includes component management services and component rendering services.

[0467] 1. The component provider receives extended component data and continuous playback duration sent by the content provider.

[0468] 2. The component provides a direction component management service to send the continuous playback duration.

[0469] 3. The component management service hides regular components and displays extended components.

[0470] 4. The component management service sends message 24 to the component rendering service.

[0471] 5. The component rendering service sends message 25 to the component provider.

[0472] 6. The component provider renders the extended component data based on the rendering engine to obtain the extended component content.

[0473] 7. The component provider displays the content of the extended component in the extended component.

[0474] Figure 15B A flowchart illustrating another method by which electronic device 100 displays extension component data in an extension component after detecting an event that switches from an inactive state to an active state.

[0475] S1501, The component provider obtains extended component data and continuous playback duration from the content provider.

[0476] If the electronic device 100 displays the cumulative playback time of the extended component content based on the extended component data and reaches the continuous playback time, the electronic device 100 can stop displaying the extended component content and start displaying the normal component content again.

[0477] In some embodiments, S1501 may not be executed. The extended component data and the continuous playback duration may be preset in the first application. The first application may send the continuous playback duration to the component management service at fixed intervals, based on preset times, at random times, or based on the fulfillment of preset trigger events.

[0478] S1502. The component provider will send the continuous playback duration to the component management service.

[0479] The component management service can monitor whether the cumulative playback duration of the displayed extended component content exceeds the continuous playback duration. If the component management service detects that the cumulative playback duration of the displayed extended component content exceeds the continuous playback duration, the electronic device 100 can stop displaying the extended component content and start displaying the normal component content again. Optionally, the component provider may include a second interface, which can be used for data transmission between the component management service and the component provider. For example, the component provider can send the continuous playback duration to the component management service through the second interface. The second interface and the first interface may be the same or different.

[0480] S1503: The component management service hides ordinary components and displays extended components.

[0481] When the first component is inactive, the component management service can check whether it has received the playback duration sent by the component provider. If the component management service confirms that it has received the playback duration sent by the component provider, it can hide the regular component, show the extended component, and begin displaying the extended component's content.

[0482] In some embodiments, the component management service can also send the continuous playback duration to the component rendering service, which then detects whether the cumulative playback duration of the extended component content exceeds the continuous playback duration. If the component rendering service detects that the cumulative playback duration of the extended component content exceeds the continuous playback duration, the component rendering service can send a message to the component management service, which then hides the regular component and displays the extended component.

[0483] S1504, The component management service sends message 24 to the component rendering service.

[0484] S1505, The component rendering service sends message 25 to the component provider.

[0485] Optionally, S1504 and S1503 can be executed simultaneously. S1504 can also be executed before S1503.

[0486] S1506. The component provider renders the extended component data based on the rendering engine to obtain the extended component content.

[0487] S1507. The component provider displays the content of the extended component in the extended component.

[0488] In response to the duration of continuous playback sent by the component management service, the component management service can send message 24 to the component provider.

[0489] As described above, the dynamic component extension module in the component provider includes a rendering engine and extension component data. In response to message 25, the component provider can obtain the extension component data from the dynamic component extension module and render the extension component data based on the rendering engine to obtain the extension component content. Afterwards, the component provider can display the extension component content within the extension component.

[0490] For a description of S1507, please refer to the introduction in S806; this application will not repeat it here.

[0491] In other embodiments, the electronic device 100 may display extension component data in the extension component and in areas other than the extension component.

[0492] Figures 16A-16CThe diagram illustrates how, after the fifth group detects an event where the first component switches from an inactive state to an active state, the electronic device 100 displays extended component data in the extended component.

[0493] Figures 16A-16C and Figures 13A-13D Similar, the difference lies in, in Figures 16A-16C In this case, the content of the extended components displayed by the electronic device 100 can be displayed in an area outside the display area 1301.

[0494] refer to Figures 13A-13B As described in the description, if the weather conditions are refreshed, the component provider can activate the first component via electronic device 100 and display the refreshed weather content based on the refreshed weather data. The refreshed weather content can be referenced. Figures 16B-16C The data displayed by the electronic device 100.

[0495] like Figure 16B As shown, the electronic device 100 can display refreshed weather content 1602 in the display area 1601. The refreshed weather content 1602 includes cloud animation and raindrop animation. The size of the display area 1601 is larger than the size of the display area 1301.

[0496] like Figure 16C As shown, the electronic device 100 can display refreshed weather content 1604 in the display area 1603. The refreshed weather content 1604 includes lightning effects and raindrop effects. The size of the display area 1603 is larger than the size of the display area 1301.

[0497] Not limited to Figures 16B-16C The electronic device 100 can display even more refreshed weather information, as shown in the updated weather display. Figures 16B-16C For illustrative purposes only.

[0498] Figure 17A This diagram illustrates another software interaction in which the electronic device 100 displays data of the extended component in the extended component after detecting an event that the first component has switched from an inactive state to an active state.

[0499] Figure 17A The software interaction implementation shown and Figure 15A The software interaction implementation shown is similar, the difference being that... Figure 17A In step 1, the component provider can also obtain a first overflow area from the content provider, which is the display area of ​​the extended component content as indicated by the user. Figure 17A In step 2, the component provider also needs to send the first overflow region to the component management service. Figure 17A In step 4, the component management service also needs to send the first overflow area to the component rendering service. Figure 17A In step 5, the component rendering service can determine the first display area of ​​the extended component based on the first overflow area. Figure 17A In step 6, the component rendering service also needs to send the first display area of ​​the extended component to the component provider. Figure 17A In step 8, the component provider can display the extended component content in the first display area of ​​the extended component.

[0500] Figure 17B The diagram illustrates a method flow diagram of an electronic device 100 displaying extended component data in an extended component after detecting an event that the first component has switched from an inactive state to an active state.

[0501] Figure 17B The method flow shown and Figure 15B The methods and processes shown are similar, the difference being that... Figure 17B In S1701, the component provider can also obtain the first overflow area from the content provider. Figure 17B In S1702, the component provider also needs to send the first overflow region to the component management service. Figure 17B In S1704, the component management service also needs to send the first overflow region to the component rendering service. Figure 17B In S1705, the component rendering service can determine the first display area of ​​the extended component based on the first overflow area. Figure 17B In S1706, the component rendering service also needs to send the first display area of ​​the extended component to the component provider. Figure 17B In S1708, the component provider can display the content of the extended component in the first display area of ​​the extended component.

[0502] Optionally, the component rendering service may also choose not to send the first display area of ​​the extended component to the component provider.

[0503] For example, the first display area of ​​the extended component can be Figure 16B The display area 1601 shown and Figure 16C The display area shown is 1603.

[0504] Example 3: After detecting an event that the first component switches from an active state to an inactive state, the electronic device 100 can display the normal component, destroy the extended component, and display the normal component data in the normal component.

[0505] Optionally, the event that triggers the first component to switch from an active state to an inactive state may include, but is not limited to: the cumulative playback duration of the extended component content exceeding the continuous playback duration, the process of the component provider being closed, and the second component entering an active state.

[0506] Figures 18A-18C The diagram illustrates how, after receiving a message that the first component has switched from an active state to an inactive state, the electronic device 100 displays data of the ordinary component in the ordinary component.

[0507] For example, the first component could be a weather component provided by a weather application, and the extended component data could be weather content. The electronic device 100 could be a mobile phone.

[0508] like Figure 18A As shown in (a), when the first component is active, the electronic device 100 can display the refreshed weather content 1305. If the cumulative playback time of the refreshed weather content exceeds the continuous playback time, the electronic device 100 can stop displaying the refreshed weather content and display... Figure 18A The content of the ordinary component 1302 shown in (b) is shown in the figure.

[0509] Again Figure 18B As shown in (a), when the first component is active, the electronic device 100 can display the refreshed weather content 1305. If the cumulative playback time of the refreshed weather content exceeds the continuous playback time, the electronic device 100 can stop displaying the refreshed weather content and display... Figure 18B The content of the ordinary component 1302 shown in (b) is shown in the figure.

[0510] For example, the first component could be a weather component provided by a weather application, and the extended component data could be weather content. The electronic device 100 could be a vehicle infotainment system.

[0511] like Figure 18C As shown in (a), when the first component is active, the electronic device 100 can display the refreshed weather content 1404. If the cumulative playback time of the refreshed weather content exceeds the continuous playback time, the electronic device 100 can stop displaying the refreshed weather content and display... Figure 18C The content of the ordinary component 1402 is shown in (b) of the diagram.

[0512] Figure 19A This diagram illustrates another software interaction whereby the electronic device 100 displays data from an extension component in the extension component after receiving a message indicating a switch from an active state to an inactive state.

[0513] like Figure 19A As shown, the electronic device 100 includes an application layer and a framework layer. The application layer includes component users (e.g., the desktop) and component providers (e.g., the first application). The framework layer includes component management services and component rendering services.

[0514] 1. The component management service detected that the cumulative playback time of the extended component content exceeded the continuous playback time.

[0515] 2. The component management service displays ordinary components and destroys extended components.

[0516] 3. The component management service sends message 26 to the component management service.

[0517] 4. The component management service sends message 27 to the component provider. Message 27 is used to instruct the component provider to destroy the component provider's rendering engine.

[0518] 5. The component rendering service obtains ordinary component data from the component provider.

[0519] 6. The component rendering service renders the data of ordinary components and displays the content of ordinary components within them.

[0520] Figure 19B This diagram illustrates another method for an electronic device 100 to display extended component data in an extended component after receiving a message indicating a switch from an active state to an inactive state.

[0521] S1901, The component management service detected that the cumulative playback duration of the extended component content exceeded the continuous playback duration.

[0522] For the event of the first component switching from an active state to an inactive state, please refer to the description above, which will not be repeated here.

[0523] S1902, The component management service displays ordinary components and destroys extended components.

[0524] With the first component active, the component management service can verify whether the cumulative playback time of the extended component content exceeds the continuous playback time. If the component management service confirms that the cumulative playback time of the extended component content exceeds the continuous playback time, the component management service can display the normal component and destroy the extended component. In this way, the electronic device 100 can destroy the extended component while it stops displaying its content, saving memory space on the electronic device 100.

[0525] Optionally, in response to receiving a message that the first component has switched from an active state to an inactive state, the electronic device 100 may choose not to destroy the extended component, but simply hide it.

[0526] S1903, The component management service sends message 26 to the component rendering service.

[0527] S1904, The component rendering service sends message 27 to the component provider, which instructs the component provider to destroy the rendering engine of the first application.

[0528] S1905, The component provider destroys the rendering engine of the first application.

[0529] In response to the event that the first component switches from an active state to an inactive state, the component rendering service can send message 26 to the component rendering service. The component rendering service then sends message 27 to the component provider, which instructs the component provider to destroy the rendering engine of the first application. In response to message 27, the component provider destroys the rendering engine of the first application.

[0530] Optionally, S1904 and S1905 can be omitted. After the component management service destroys the extended component, the component provider can automatically destroy the component provider's rendering engine.

[0531] S1906, The component rendering service obtains ordinary component data from the component provider.

[0532] S1907, The component rendering service renders the data of ordinary components and displays the content of ordinary components in the ordinary components.

[0533] pass Figures 19A-19B The method shown allows the electronic device 100 to confirm whether the cumulative playback time of the extended component content exceeds the continuous playback time through the component management service in the framework layer. After confirming that the cumulative playback time of the extended component content exceeds the continuous playback time, the electronic device 100 can display the normal component and destroy the extended component through the component management service in the framework layer. In other words, the component user does not need to participate in controlling the display state switching of the first component; the component user does not need to adapt, nor does it need to monitor whether it receives a message indicating that the first component has switched from an active state to an inactive state, thus reducing the workload of developers.

[0534] In some embodiments, Figure 19A and Figure 19B In the process, the component management service can also send a sustained playback duration to the component rendering service, which will then monitor whether the cumulative playback duration of the extended component content exceeds the sustained playback duration. If the component rendering service detects that the cumulative playback duration of the extended component content exceeds the sustained playback duration, it can send a message to the component management service, instructing the component management service to display the regular component and destroy the extended component.

[0535] In other embodiments, if the first component switches from an active state to an inactive state, including when the component provider's process shuts down or the second component enters an active state, the electronic device 100 can also have the component rendering service confirm whether it has received a message that the provider's process has shut down or a message that the second component has entered an active state. If the component rendering service confirms that it has received a message that the provider's process has shut down or a message that the second component has entered an active state, the component rendering service then sends a message to the component management service, and the component management service then displays the normal component, destroys the extended component, and displays the content of the normal component in the normal component. For details, please refer to... Figure 11A and Figure 11B The descriptions in the embodiments are not repeated here.

[0536] Figure 20 A flowchart illustrating a display method provided in this application is shown.

[0537] S2001. The electronic device obtains the attribute information of the first component, which includes the attribute information of the ordinary component and the attribute information of the extended component. The first component is a component in the first application, and the first application is a third-party application.

[0538] S2002, The electronic device receives and responds to the first operation, and adds the first component to the first interface based on the attribute information of the first component.

[0539] Optionally, the first component can be a 3D component or a non-3D component. The electronic device 100 can determine whether the first component is a 3D component or a non-3D component based on its attribute information. If the electronic device 100 determines that the first component is a 3D component based on its attribute information, then the electronic device 100 can create the first component, which includes a regular component and an extended component, and display the regular component while hiding the extended component. The electronic device 100 can also display the content of the regular component within the regular component. If the electronic device 100 determines that the first component is a non-3D component based on its attribute information, then the electronic device 100 can create the first component, which includes a regular component, and display the regular component. The electronic device 100 can also display the content of the regular component within the regular component.

[0540] For example, a 3D component may include a fun interactive component or a scene animation component. If the first component is a 3D component, its attribute information may include the attribute information of a regular component and the attribute information of an extended component. If the first component is a non-3D component, its attribute information may include the attribute information of a regular component. The attribute information of a regular component includes any one or more of the following: size, shape, color, and transparency. When the type of the first component is a fun interactive component, the attribute information of the extended component includes any one or more of the following: the first extended component type (e.g., a fun interactive component), the name of the dynamic component extension module that the extended component depends on, the name of the installation package of the application to which the extended component belongs, and the timeout pause duration. When the type of the first component is a scene animation component, the attribute information of the extended component includes any one or more of the following: the second extended component type (e.g., a scene animation component), the name of the dynamic component extension module that the extended component depends on, whether the extended component can remain active, and the types of gestures disabled when displaying the extended component.

[0541] By implementing this method, the electronic device can receive attribute information of the first component provided by the third-party application, and create and display the first component provided by the third-party application based on the attribute information of the first component, thereby increasing the diversity of components displayed by the electronic device 100 and improving the display effect of the components.

[0542] In one possible implementation, the first component includes a regular component and an extended component; the method further includes: in response to a component content switching message, the electronic device displays the first content of the regular component and hides the second content of the extended component, or the electronic device displays the second content of the extended component and hides the first content of the regular component. By implementing this method, the electronic device can switch between different display states of the 3D component, improving the display effect of the component.

[0543] In one possible implementation, the electronic device obtains the first data of the first component, specifically including: when the electronic device installs the first application, the electronic device obtains the attribute information of the first component; or, after the first application is installed, the electronic device obtains the attribute information of the first component.

[0544] In one possible implementation, the electronic device includes a component management service; when the electronic device displays the first content of a common component, the electronic device displays the common component and hides or destroys the extended component through the component management service; when the electronic device displays the second content of the extended component, the electronic device displays the extended component and hides the common component through the component management service.

[0545] Both extended components and regular components are child components of the first component. Implementing this method, after the component user creates the first component, the user doesn't need to worry about receiving component content switching messages, nor do they need to control the display state switching of the first component. The electronic device can confirm whether it has received the component content switching message through the framework layer (e.g., a component rendering service or a component management service). After confirming that the component content switching message has been received, the electronic device can control the display state switching of the first component through the component management service in the framework layer. In other words, the component user does not need to participate in controlling the component's display state switching, and the component user does not need to adapt, reducing the workload of developers.

[0546] For example, a component user can call the Formkit interface provided by Formkit, and a component provider can also call the Formkit interface provided by Formkit. The Formkit interface called by the component user is different from the Formkit interface called by the component provider.

[0547] Formkit provides a Live Form Extension Ability, which component providers can use to develop 3D components. When an electronic device displays the secondary content of the extended component, the framework layer (such as a card management service and / or a card rendering service) can launch the Live Form Extension Ability in the first application process through the Formkit interface to display the extended component and hide the regular component. The Live Form Extension Ability in the first application process can display the extended component content within the extended component based on the extended component data provided by the Live Form Extension Ability.

[0548] When the electronic device displays the first content of a regular component, the framework layer (such as the card management service and / or card rendering service) can use the Formkit interface to pause or destroy the Live Form Extension Ability in the application process, hide or destroy the extension component, and display the regular component. The framework layer (such as the card management service and / or card rendering service) can obtain the regular component data from the first application through the Formkit interface and display the regular component content in the regular component based on the regular component data.

[0549] In one possible implementation, the electronic device displays the first content of a general component, specifically including: the electronic device obtaining first data of the general component from a first application; and the electronic device displaying the first content of the general component in the general component based on the first data of the general component.

[0550] For example, an electronic device may include a component rendering service. The electronic device can obtain first data of a common component from a first application through the component rendering service; the component rendering service renders the first data of the common component to obtain the first content of the common component, and displays the first content of the common component in the common component.

[0551] Optionally, when the first component is inactive or paused, the electronic device can display the first content of the ordinary component in the ordinary component.

[0552] In one possible implementation, the first application includes a first interface; the electronic device obtains first data of a common component from the first application, specifically including: the electronic device obtains the first data of the common component from the first application through the first interface. Thus, when the first application is a third-party application, the electronic device can obtain the first data of the common component provided by the first application through the first interface and display the first content of the common component of the third-party application.

[0553] In one possible implementation, the electronic device displays the second content of the extended component, specifically including: the electronic device sending a first message to a first application; in response to the first message, the first application obtaining second data of the extended component; and the first application displaying the second content of the extended component in the extended component based on the second data of the extended component. Implementing this method, the second content of the extended component is relatively complex, and the electronic device can render the second content of the extended component using the second data of the extended component provided by the first application.

[0554] For example, an electronic device may include a component rendering service. The electronic device may send a first message to a first application through the component rendering service, the first message instructing the first application to render a second content of the extended component based on the second data of the extended component.

[0555] Optionally, when the first component is in a paused state, the electronic device may display the second content of the extended component in the extended component.

[0556] Optionally, the first application includes a dynamic component extension module. The first application displays the second content of the extension component in the extension component based on the second data of the extension component. Specifically, the first application renders the second data of the extension component through the dynamic component extension module and displays the second content of the extension component in the extension component.

[0557] For example, a dynamic component extension module may include a rendering engine and second data for the extension component. A first application can render the second data of the extension component using the rendering engine provided by the dynamic component extension module to obtain the second content of the extension component. By implementing this method, third-party applications can develop the resources required for 3D components, such as the rendering engine and the second data of the extension component, using the dynamic component extension module provided by the framework layer, enabling electronic devices to display the 3D components of the third-party applications.

[0558] In one possible implementation, the electronic device includes a component management service; the component management service is used to store attribute information of a first component. By implementing this method, the electronic device can store the attribute information of the first component provided by a third-party application in the component management service.

[0559] In some embodiments, the component management service can also send the attribute information of the first component to the component user. The component user can then create the first component based on the attribute information of the first component.

[0560] In some embodiments, the response to the component content switching message includes any one or more of the following: a message that the first component switches from an active state to a paused state, a message that the first component switches from a paused state to an inactive state, a message that the first component switches from an active state to an inactive state, a message that the first component switches from an inactive state to an active state, and a message that the first component switches from a paused state to an active state.

[0561] In one possible implementation, the response to the component content switching message includes any one or more of the following: a message that the first component switches from an active state to a paused state, a message that the first component switches from a paused state to an inactive state, a message that the first component switches from an active state to an inactive state, a message that the first component switches from an inactive state to an active state, and a message that the first component switches from a paused state to an active state.

[0562] Wherein, if the first component is of type one (e.g., a fun interactive component), the event that causes the first component to switch from an active state to a paused state includes any one or more of the following: a touch operation on the first component, the user's gaze being directed at an area outside the first component, the first interface becoming invisible, an operation performed on an area outside the display area where the first component is located, or the continuous display duration of the second content of the extended component exceeding a second duration. For example, refer to the content regarding Example 3 in the fun interactive card; this application will not repeat it here.

[0563] The event that causes the first component to switch from a paused state to an inactive state includes any of the following: the process of the first application is closed, or the second component enters an active state, wherein the second component and the first component are different components. For example, please refer to the content regarding Example 6 in the interactive card section; this application will not repeat it here.

[0564] The event that causes the first component to switch from an active state to an inactive state includes any one or more of the following: the process of the first application is closed, or the second component enters an active state. For example, please refer to the content related to Example 5 in the interactive card; this application will not repeat it here.

[0565] The event that causes the first component to switch from an inactive state to an active state includes any one or more of the following: a touch operation applied to the first component, or the user's gaze on the first component. For example, please refer to the content related to Example 2 in the interactive fun card; this application will not repeat it here.

[0566] The event that causes the first component to switch from a paused state to an active state includes any one or more of the following: a touch operation applied to the first component, or the user's gaze being directed at the first component. For example, please refer to Example 4 in the interactive fun card; this application will not repeat it here.

[0567] In one possible implementation, when the first component switches from an active state to a paused state, or from a paused state to an inactive state, or from an active state to an inactive state, the electronic device displays the first content of the ordinary component and hides the second content of the extended component; when the first component switches from an inactive state to an active state, or when the first component switches from a paused state to an active state, the electronic device displays the second content of the extended component and hides the first content of the ordinary component.

[0568] If the first component is of type two (e.g., a scene animation component), the event that causes the first component to switch from an active state to an inactive state includes any one or more of the following: the cumulative display duration of the first content of the ordinary component exceeds a first duration, the process of the first application is closed, or the second component enters an active state, wherein the second component and the first component are different components. For example, refer to the content related to Example 2 in the scene animation component section; this application will not repeat it here.

[0569] The event that triggers the first component to switch from an inactive state to an active state includes any one or more of the following: receiving a first request sent by the first application. For example, please refer to Example 3 in the scene animation component section; this application will not repeat it here.

[0570] In one possible implementation, when the first component switches from an active state to an inactive state, the electronic device displays the first content of the ordinary component and hides the second content of the extended component; when the first component switches from an inactive state to an active state, the electronic device displays the second content of the extended component and hides the first content of the ordinary component.

[0571] In one possible implementation, the method further includes: the electronic device obtaining a first duration from a first application, the first duration being used to instruct the electronic device to stop displaying the second content of the extension component after detecting that the continuous display duration of the second content of the extension component exceeds the first duration.

[0572] Optionally, the electronic device may also include a component management service, to which the first application can send a first duration. The component management service can, upon detecting that the continuous display duration of the second content of the extended component exceeds the first duration, destroy or hide the extended component. The electronic device can then stop displaying the second content of the extended component and display the normal component. The electronic device can then begin displaying the content of the normal component. For example, refer to... Figures 13A-15B The descriptions in the embodiments are not repeated here.

[0573] In one possible implementation, the method further includes: the electronic device obtaining a first overflow area from a first application; the electronic device determining a first display area of ​​a second component based on the first overflow area, the first display area of ​​the second component being used to indicate an area for the first application to display the second content of the extended component. Implementing this method, the first application can also request an overflow area from the electronic device, which can allocate a display area for the first application, allowing the first application to display the second content of the extended component within the allocated display area, thus improving the display effect of the second content of the extended component.

[0574] Optionally, the electronic device may further include a component management service and a component rendering service. The first application can send a first overflow area to the component management service. The component management service then sends the first overflow area to the component rendering service. The component rendering service can allocate a display area based on the first overflow area, and then send the display area information to the first application. The first application can display the second content of the extended component in the display area allocated by the component rendering service. For example, refer to... Figures 16A-17B The descriptions in the embodiments are not repeated here.

[0575] In one possible implementation, the first application includes a second interface; the electronic device obtains a first duration from the first application, specifically including: the electronic device obtaining the first duration from the first application through the second interface; and / or, the electronic device obtaining a first overflow area from the first application through the second interface. The second interface and the first interface may be the same or different.

[0576] Figure 21 A flowchart illustrating another display method provided in this application is shown.

[0577] S2101. The electronic device obtains attribute information of a first component, including attribute information of a normal component and attribute information of an extended component, wherein the first component is a component in a first application.

[0578] S2102, The electronic device receives and responds to the first operation, and adds the first component to the first interface based on the attribute information of the first component. The first component includes a normal component and an extended component.

[0579] S2103. In response to a component content switching message, the electronic device displays the first content of the normal component and hides the second content of the extended component, or the electronic device displays the second content of the extended component and hides the first content of the normal component.

[0580] By implementing this method, the electronic device can receive attribute information of 3D components provided by a first application (a third-party application or a non-third-party application). When the electronic device creates 3D components based on the attribute information of the 3D components provided by the first application, the electronic device can simultaneously create ordinary components and extended components of the 3D components. After displaying the 3D components, the electronic device can control the 3D to switch between different display states, thereby improving the display effect of the 3D components in the electronic device.

[0581] It should be noted that, Figure 20 One or more possible implementations shown can also be applied to Figure 21 The display method shown can be referenced. Figure 20 The descriptions in the above descriptions will not be repeated here. Embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, can implement the steps in the various method embodiments described above.

[0582] This application also provides a computer program product, including a computing program, which, when run on a computer, enables the computer to perform the steps in the various method embodiments described above.

[0583] This application also provides a chip system, which includes a processing circuit interface circuit. The interface circuit receives code instructions and transmits them to the processing circuit. The processing circuit executes the code instructions to enable the chip system to implement the steps of any method embodiment of this application. The chip system can be a single chip or a chip module composed of multiple chips.

[0584] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A display method, characterized in that, The method is applied to an electronic device, the electronic device including a first application, the first application being a third-party application; the method includes: The electronic device acquires attribute information of a first component, the attribute information including attribute information of a normal component and attribute information of an extended component, the first component being a component in the first application; The electronic device receives and responds to the first operation, and adds the first component to the first interface based on the attribute information of the first component.

2. The method according to claim 1, characterized in that, The first component includes a regular component and an extended component; the method further includes: In response to a component content switching message, the electronic device displays the first content of the normal component and hides the second content of the extended component, or the electronic device displays the second content of the extended component and hides the first content of the normal component.

3. A display method, characterized in that, The method is applied to an electronic device, the electronic device including a first application; the method includes: The electronic device acquires attribute information of a first component, the attribute information including attribute information of a normal component and attribute information of an extended component, the first component being a component in the first application; The electronic device receives and responds to the first operation, and adds the first component to the first interface based on the attribute information of the first component. The first component includes a normal component and an extended component. In response to a component content switching message, the electronic device displays the first content of the normal component and hides the second content of the extended component, or the electronic device displays the second content of the extended component and hides the first content of the normal component.

4. The method according to claim 2 or 3, characterized in that, The electronic device includes a component management service; the method further includes: When the electronic device displays the first content of the ordinary component, the electronic device displays the ordinary component, hides or destroys the extended component through the component management service; When the electronic device displays the second content of the extended component, the electronic device displays the extended component and hides the ordinary component through the component management service.

5. The method according to any one of claims 1-4, characterized in that, The electronic device acquires first data from the first component, specifically including: When the first application is installed on the electronic device, the electronic device obtains the attribute information of the first component; or, After installing the first application, the electronic device obtains the attribute information of the first component.

6. The method according to any one of claims 2-5, characterized in that, The electronic device displays the first content of the ordinary component, specifically including: The electronic device obtains first data of a common component from the first application; The electronic device displays the first content of the general component in the general component based on the first data of the general component.

7. The method according to claim 6, characterized in that, The first application includes a first interface; the electronic device obtains first data of a common component from the first application, specifically including: The electronic device obtains the first data of the common component from the first application through the first interface.

8. The method according to any one of claims 2-7, characterized in that, The electronic device displays the second content of the extended component, specifically including: The electronic device sends a first message to the first application; In response to the first message, the first application obtains the second data from the extended component; The first application displays the second content of the extension component in the extension component based on the second data of the extension component.

9. The method according to claim 8, characterized in that, The first application includes a dynamic component extension module; the first application displays the second content of the extension component in the extension component according to the second data of the extension component, specifically including: The first application renders the second data of the extended component through the dynamic component extension module and displays the second content of the extended component in the extended component.

10. The method according to any one of claims 1-9, characterized in that, The electronic device includes the component management service; the component management service is used to store the attribute information of the first component.

11. The method according to any one of claims 2-10, characterized in that, The response to the component content switching message includes any one or more of the following: the message that the first component switches from an active state to a paused state, the message that the first component switches from a paused state to an inactive state, the message that the first component switches from an active state to an inactive state, the message that the first component switches from an inactive state to an active state, and the message that the first component switches from a paused state to an active state.

12. The method according to claim 11, characterized in that, When the first component is of type 1, the event that the first component switches from active state to paused state includes any one or more of the following: touch operation on the first component, user's gaze is on an area other than the first component, the first interface is not visible, operation on an area other than the display area where the first component is located, and the continuous display duration of the second content of the extended component exceeds the second duration. The event in which the first component switches from the paused state to the inactive state includes any one of the following: the process of the first application is closed, the second component enters the active state, and the second component and the first component are different components; The event in which the first component switches from an active state to an inactive state includes any one or more of the following: the process of the first application is closed, or the second component enters an active state; The event that switches the first component from an inactive state to an active state includes any one or more of the following: a touch operation on the first component, or the user's gaze on the first component; The event that allows the first component to switch from a paused state to an active state includes any one or more of the following: a touch operation on the first component, or the user's gaze on the first component.

13. The method according to claim 11, characterized in that, When the first component switches from an active state to a paused state, or from a paused state to an inactive state, or from an active state to an inactive state, the electronic device displays the first content of the ordinary component and hides the second content of the extended component; When the first component switches from an inactive state to an active state, or when the first component switches from a paused state to an active state, the electronic device displays the second content of the extended component and hides the first content of the ordinary component.

14. The method according to claim 11, characterized in that, When the first component is of type two, the event in which the first component switches from an active state to an inactive state includes any one or more of the following: the cumulative display time of the first content of the ordinary component exceeds a first duration, the process of the first application is closed, the second component enters an active state, and the second component and the first component belong to different components; The event in which the first component switches from an inactive state to an active state includes any one or more of the following: receiving a first request sent by the first application.

15. The method according to claim 14, characterized in that, When the first component switches from an active state to an inactive state, the electronic device displays the first content of the ordinary component and hides the second content of the extended component; When the first component switches from an inactive state to an active state, the electronic device displays the second content of the extended component and hides the first content of the ordinary component.

16. The method according to claim 15, characterized in that, The method further includes: The electronic device obtains a first duration from the first application. The first duration is used to instruct the electronic device to stop displaying the second content of the extension component after detecting that the continuous display duration of the second content of the extension component exceeds the first duration.

17. The method according to claim 16, characterized in that, The method further includes: The electronic device obtains a first overflow area from the first application; The electronic device determines a first display area of ​​the second component based on a first overflow area, and the first display area of ​​the second component is used to indicate the area where the first application displays the second content of the extended component.

18. The method according to claim 17, characterized in that, The first application includes a second interface; the electronic device obtains a first duration from the first application, specifically including: The electronic device obtains the first duration from the first application through the second interface; And / or, The electronic device obtains the first overflow area from the first application through the second interface.

19. The method according to any one of claims 1-18, characterized in that, The attribute information of the first component includes the attribute information of the ordinary component and the attribute information of the extended component; The attribute information of the common component includes any one or more of the following: size, shape, color, transparency, and information about the application to which the common component belongs; The attribute information of the extended component includes any one or more of the following: first type, name of the dynamic component extension module that the extended component depends on, name of the installation package of the application to which the extended component belongs, and timeout pause duration; or, The attribute information of the extended component includes any one or more of the following: second type, the name of the dynamic component extension module that the extended component depends on, whether the extended component can always be active, and the gesture type that is disabled when the extended component is displayed.

20. An electronic device, characterized in that, The electronic device includes a memory and a processor; wherein the memory and the processor are coupled, the memory is used to store a computer program, and when the processor executes the computer program, the electronic device performs the method of any one of claims 1-19.

21. A computer-readable storage medium, characterized in that, Includes instructions that, when executed on an electronic device, cause the electronic device to perform the method of any one of claims 1-19.

22. A computer program product, characterized in that, It includes a computer program that, when executed by a processor, implements the communication method as described in any one of claims 1-19.

23. A chip system, characterized in that, The chip system includes a processing circuit and an interface circuit. A chip system is characterized by including a processing circuit and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processing circuit, and the processing circuit is used to execute the code instructions to perform the method as described in any one of claims 1-19.

Images