Methods, apparatuses, devices, media, and program products for user interface interaction

By establishing a stable correspondence between structured declarations and authoritative document nodes in the interface interaction, the problem of full-page reconstruction caused by partial editing is solved, improving presentation efficiency and storage efficiency.

CN123114465APending Publication Date: 2026-11-17BEIJING ZITIAO NETWORK TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611329363.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-08-28
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In existing technologies, partial editing during interface presentation can easily lead to the reconstruction of the entire page, resulting in inconsistencies between stored information and what the user sees, and the running state is difficult to maintain.

Method used

By establishing a stable correspondence between structured declarations and authoritative document nodes, only the nodes of the target element are updated, while the state of other nodes is preserved, reducing the difficulty of rebuilding the entire page and storing mixed runtime states.

Benefits of technology

It shortens the processing time for page re-rendering, reduces the scope of data updates, and lowers storage overhead.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123114465A_ABST
    Figure CN123114465A_ABST
Patent Text Reader

Abstract

Methods, apparatuses, devices, media, and program products for interface interaction are provided. The method includes: presenting, on an editing interface, first content rendered from a structured declaration created by an intelligent system, the first content including multiple elements; receiving an editing operation on the first element among the multiple elements; and presenting second content based on first persistent information, the first persistent information obtained by editing a first node associated with the first element in the second persistent information derived from the structured declaration.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The examples in this article generally relate to the field of computer science, and in particular to methods, apparatuses, devices, media, and program products for user interface interaction. Background Technology

[0002] When presenting generative content in an interface, solutions may use page-level images to represent the results, or directly use pages with a runtime shell and temporary state as the objects to be edited and saved. Page-level images primarily retain pixel-level results. Summary of the Invention

[0003] In a first aspect of this paper, a method for interface interaction is provided. The method includes: in an editing interface, presenting first content, the first content being presented through a structured declaration, the first content comprising multiple elements, the structured declaration being created by an intelligent system; receiving an editing operation, the editing operation targeting a first element among the multiple elements; and presenting second content, the second content being presented based on first persistent information, the first persistent information being obtained by editing a first node of the second persistent information based on the editing operation, the second persistent information originating from the structured declaration, the first node being associated with the first element.

[0004] In a second aspect of this document, an apparatus for interface interaction is provided. The apparatus includes: a first presentation module configured to present first content on an editing interface, the first content being presented through a structured declaration, the first content comprising multiple elements, the structured declaration being created by an intelligent system; a receiving module configured to receive an editing operation on the first element among the multiple elements; and a second presentation module configured to present second content formed based on first persistent information, the first persistent information being obtained by editing a first node associated with the first element in the second persistent information derived from the structured declaration.

[0005] In a third aspect of this document, an electronic device is provided. The electronic device includes at least one processor; and at least one memory coupled to the at least one processor and storing instructions for execution by the at least one processor, the instructions causing the electronic device to perform the method of the first aspect when executed by the at least one processor.

[0006] In a fourth aspect of this document, a computer-readable storage medium is provided. The computer-readable storage medium stores computer-executable instructions that can be executed by a processor to implement the method of the first aspect.

[0007] In a fifth aspect of this document, a computer program product is provided. This computer program product is tangibly stored in a computer storage medium and includes computer-executable instructions that, when executed by a device, cause the device to perform the method of the first aspect.

[0008] In this way, a stable correspondence is established between structured declarations, elements, and authoritative document nodes. Edits to the first element can be converted into updates to associated nodes, while preserving other nodes. This process reduces the scope of data updates during re-rendering, minimizing processing time and storage overhead caused by full-page reconstruction.

[0009] It should be understood that the content described in this section is not intended to limit the key or important features of the examples in this article, nor is it intended to restrict the scope of the solution. Other features will become readily apparent from the following description. Attached Figure Description

[0010] The above and other features, advantages, and aspects of the various examples herein will become more apparent when taken in conjunction with the accompanying drawings and the following detailed description. In the accompanying drawings, the same or similar reference numerals denote the same or similar elements, wherein: Figure 1 A schematic diagram of the example environment is shown; Figure 2A and Figure 2B Example interfaces before and after editing are shown in some scenarios; Figure 3 The diagram illustrates a layered operational architecture for user interface interaction in several scenarios. Figure 4 The diagram illustrates authoritative documents, derived document models, live documents, and editing and saving paths in several scenarios. Figure 5 The diagram illustrates the bridging communication process between the host and the embedded framework runtime in some scenarios. Figure 6 The diagram illustrates the editing, re-presentation, and persistence loop in some scenarios; Figure 7 Flowcharts illustrating example processes for interface interaction in several scenarios are shown; Figure 8 Block diagrams of devices for interface interaction in several scenarios are shown; and Figure 9 A block diagram of an electronic device capable of implementing multiple illustrative scenarios is shown. Detailed Implementation

[0011] The examples in this document will now be described in more detail with reference to the accompanying drawings. While some examples are shown in the drawings, it should be understood that solutions can be implemented in various forms and should not be construed as limited to the examples presented herein. Rather, these examples are provided to provide a more thorough and complete understanding of the solutions. It should be understood that the drawings and examples in this document are for illustrative purposes only and are not intended to limit the scope of protection of the solutions.

[0012] It should be noted that the headings of any section / subsection provided herein are not restrictive. Various examples are described throughout this document, and examples of any type may be included under any section / subsection. Furthermore, examples described in any section / subsection may be combined in any way with any other examples described in the same section / subsection and / or different sections / subsections.

[0013] In the description of the examples in this document, the term "including" and similar terms should be understood as open inclusion, i.e., "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "an example" or "the example" should be understood as "at least one example". The term "some examples" should be understood as "at least some examples". Other explicit and implicit definitions may also be included below. The terms "first", "second", etc., may refer to different or the same objects. Other explicit and implicit definitions may also be included below.

[0014] The examples in this document may involve user data, data acquisition, and / or use. All of these aspects comply with relevant laws, regulations, and rules. In the examples, all data collection, acquisition, processing, manipulation, forwarding, and use are conducted with the user's knowledge and confirmation. Accordingly, when implementing each example, the type, scope of use, and usage scenarios of any data or information that may be involved should be communicated to the user and their authorization obtained through appropriate means, in accordance with relevant laws and regulations. The specific methods of notification and / or authorization can vary depending on the actual situation and application scenario; the scope of the solution is not limited in this regard.

[0015] The solutions and examples described in this article, if involving the processing of personal information, will all be processed under the premise of a legal basis (such as obtaining the consent of the personal information subject, or being necessary for the performance of a contract), and will only be processed within the scope stipulated or agreed upon. A user's refusal to process personal information beyond what is necessary for basic functions will not affect the user's use of basic functions.

[0016] As used in this article, the term "structured declaration" refers to a declarative document, which can include a machine-parseable document used to declare content, hierarchical structure, page units, element attributes, styles, resource references, entry points, and interactive metadata. In this article, "structured declaration" and "declarative document" may refer to the same document representation.

[0017] In one context, an intelligent system is an information processing system. This intelligent system uses at least one or more models to process one or more inputs. The intelligent system may include the one or more models as components, or it may use models external to the system for processing. Those skilled in the art will recognize that there are various implementations of intelligent systems in the industry, including but not limited to agents, artificial intelligence (AI) assistants, AI workers, copilot systems, and chatbots. The inputs include data in one or more modalities. The modal data includes, but is not limited to, text, audio, images, video, application-specific data, or scientific computing data. The models include, but are not limited to, one or more combinations of the following: large-scale parametric models, deep learning models, neural network models, machine learning models, statistical models, rule-based models, or other models capable of processing the inputs. The specific implementation of the models can employ various existing or improved models. The intelligent system may involve one or more of the following operations: receiving single-round or multi-round input; recognizing and / or understanding the input; generating answers, decisions, or processing results using one or more models; invoking one or more external tools, interfaces, knowledge bases, or other systems to obtain information or perform operations; processing in a self-decision-making or human-machine collaborative manner, or transferring tasks to human or other systems for processing. Self-decision-making refers to execution without human intervention. Human-machine collaboration refers to partial human participation or confirmation. The above explanation of "intelligent system" is illustrative, and each description is an example, not necessarily necessary, and does not constitute an exhaustive list.

[0018] The term "editing interface" as used in this article refers to an interface that can present content to be edited and receive editing operations, which may include the main display area, thumbnail area, notes area, tool area or other areas suitable for interface interaction.

[0019] As used in this article, the term "content" refers to generated content presented in the editing interface. For example, generated content can include various types of media content, such as presentations, web pages, etc.

[0020] As used in this article, the term "element" refers to a content object that can form a perceptible presentation in an interface, which may include text, graphics, images, containers, media, controls, or combinations thereof.

[0021] As used in this article, "persistent information" refers to a Canonical Document, which is an authoritative representation of declarative document content that can be saved, reloaded, and edited. Persistent information, Canonical Document, and authoritative document can all refer to the same type of document representation in this article.

[0022] As used in this article, the term "node" refers to a data structure in an authoritative document that can express a document, page unit, element, or element attribute. Nodes can have parent-child relationships, sequential relationships, referencing relationships, or other relationships suitable for expressing the document structure.

[0023] As used in this article, a "page unit" refers to a child node under the declarative document root node that represents a renderable page. A page unit can include multiple elements, page-level attributes, notes, animation information, and identification information.

[0024] The term "identification information" as used in this article refers to information that enables the location of page units or elements during rendering, editing, history recovery, or persistence. Identification information can be provided by the author or temporarily completed by runtime according to deterministic rules.

[0025] As used in this article, the term "editable attribute" refers to an attribute that indicates whether a node or its descendants are eligible for editing. Editable attributes can be explicitly given by a declarative document or determined at runtime if editing is not prohibited and the element has a stable identifier.

[0026] The term “presentation effect” as used in this article refers to the visual or interactive result of an element in an interface, which may include content, shape, position, size, style, hierarchy, animation state, or interactive state.

[0027] As used in this document, "runtime information" refers to the information that enables a declarative document to render, communicate, edit, or animate, and may include the base runtime, formatting runtime, styles, scripts, temporary categories, or states. Runtime information does not necessarily need to be included in the authoritative document.

[0028] The term “animation style” as used in this article refers to information used to define how an animation target changes, which may include keyframes, duration, delay, easing, or activation categories.

[0029] The term "channel" as used in this article refers to the logical communication scope corresponding to a single declarative document rendering instance. Different channels can isolate messages from different embedded frame instances.

[0030] The term “endpoint” as used in this article refers to the message sender or receiver in bridged communication, which may have an endpoint identifier, source window information, and source address information.

[0031] The term "handshake message" as used in this document refers to the message used to initiate endpoint association. The term "response message" as used in this document refers to the association message returned by the receiving end in response to a handshake message or request message.

[0032] The term “allowed address set” as used in this article refers to one or more source addresses that are configured to be allowed into the bridging protocol processing path.

[0033] The term “derived document model” as used in this article refers to a read-only model obtained from parsing authoritative documents for querying and rendering acceleration, which may include page mapping, page proportions, rendered content, content summary, notes, editable areas, and animation targets.

[0034] The term "real-time document" as used in this article refers to a runtime document that serves visual presentation and interaction. A real-time document may include a Document Object Model (DOM), an interface shell, a presentation surface, an editing overlay, and a temporary state, but is not a persistent source.

[0035] As used in this article, the term "runtime" refers to a collection of software components that provide communication, state, rendering, editing, animation, or formatting capabilities for declarative documents. A runtime may include a base runtime and one or more format runtimes.

[0036] The term "edit surface" as used in this article refers to the range of content that the editor kernel can currently read and submit, which may include surface identifiers, content, size, mounted elements, and resource base addresses.

[0037] The term "adapter" as used in this article refers to a software component that maps a page or author subject of a specific document format to an editing surface and writes a snapshot of the editing surface back to the corresponding node of the authoritative document.

[0038] The term "revision identifier" as used in this document refers to information used to identify a runtime document state and verify the consistency of the presentation task. Revision identifiers are used for runtime consistency control and do not necessarily represent multiple saved versions of a persistent document.

[0039] As mentioned above, when related solutions present results using page-level images, page elements are merged into pixel-level results, making it difficult to address text, graphics, containers, and layout relationships. If related solutions directly use the real-time document after loading runtime information as the object of editing and saving, the interface shell, temporary styles, and interactive states may end up in the stored information.

[0040] In partial editing scenarios, the aforementioned difficulties further manifest as follows: a change to one element may trigger a complete page regeneration, and the identity and resource loading state of unchanged elements are difficult to maintain. Stored information and the content currently seen by the user may come from different data copies. Therefore, a stable correspondence needs to be established between structured declarations, authoritative document nodes, derived models, and live-rendered elements.

[0041] A scheme for interface interaction is proposed. According to this scheme, the intelligent system creates a structured declaration, and the electronic device 110 presents first content including multiple elements by loading runtime information. Before presenting the first content, it clones the authoritative document before editing from the structured declaration. The electronic device 110 receives an editing operation on the first element, locates the first node associated with the first element in the authoritative document before editing, updates the first node based on the editing operation, and retains other nodes in the authoritative document, thereby obtaining the authoritative document after editing and presenting the second content.

[0042] In one context, an intelligent system is an information processing system. This intelligent system uses at least one or more models to process one or more inputs. The intelligent system may include the one or more models as components, or it may use models external to the system for processing. Those skilled in the art will recognize that there are various implementations of intelligent systems in the industry, including but not limited to agents, artificial intelligence (AI) assistants, AI workers, copilot systems, and chatbots. The inputs include data in one or more modalities. The modal data includes, but is not limited to, text, audio, images, video, application-specific data, or scientific computing data. The models include, but are not limited to, one or more combinations of the following: large-scale parametric models, deep learning models, neural network models, machine learning models, statistical models, rule-based models, or other models capable of processing the inputs. The specific implementation of the models can employ various existing or improved models. The intelligent system may involve one or more of the following operations: receiving single or multiple rounds of input; recognizing and / or understanding the input; generating answers, decisions, or processing results using one or more models; invoking one or more external tools, interfaces, knowledge bases, or other systems to obtain information or perform operations; processing in a self-decision-making or human-machine collaborative manner, or transferring tasks to human or other systems for processing. Self-decision-making refers to execution without human intervention. Human-machine collaboration refers to partial human participation or confirmation. The above explanation of "intelligent system" is illustrative, and each description is an example, not necessarily necessary, and does not constitute an exhaustive list.

[0043] In one implementation, the intelligent system, authoritative document, and runtime can all reside on electronic device 110, with electronic device 110 handling generation, presentation, and node updates unilaterally. In another implementation, server 130 can create and maintain authoritative documents, electronic device 110 retrieves and presents the corresponding content, and editing operations are applied to associated nodes by server 130. In yet another implementation, server 130 creates an initial declarative document, electronic device 110 presents and performs partial editing locally, and then sends the node update results to server 130 to form a joint processing path.

[0044] Through the above scheme, the stable correspondence between structured declarations and authoritative document nodes enables electronic device 110 to update only the data range associated with the target element, thereby solving the difficulties of rebuilding the entire page during partial editing and the easy mixing of stored information into the runtime state. Since other nodes continue to reuse existing content and resources, the number of page parsing operations, layout calculations, and cache writes of electronic device 110 can be reduced, and the processing time required for re-presentation is also shortened accordingly.

[0045] The following describes various examples of this scheme in further detail with reference to the accompanying drawings.

[0046] Figure 1 A schematic diagram of example environment 100 is shown. (e.g.) Figure 1 As shown, example environment 100 may include electronic device 110.

[0047] In this example environment 100, electronic device 110 can run application 120 that supports user interface interaction. User 140 can interact with application 120 via electronic device 110 and / or attached devices of electronic device 110. Electronic device 110 can present interface 150 for supporting user interface interaction through application 120.

[0048] In some scenarios, application 120 can create an embedded frame within the host page and load a declarative document created by the intelligent system through that frame. The host page and the declarative document within the embedded frame are isolated from each other at the operational boundary and exchange messages for loading, editing, saving, or closing via bridged communication.

[0049] In some cases, electronic device 110 communicates with server 130 to provide services to application 120. Electronic device 110 can be any type of mobile terminal, fixed terminal, or portable terminal, including mobile phones, desktop computers, laptop computers, notebook computers, netbook computers, tablet computers, media computers, multimedia tablets, handheld computers, portable gaming terminals, virtual reality (VR) / augmented reality (AR) devices, personal communication system (PCS) devices, personal navigation devices, personal digital assistants (PDAs), audio / video players, digital cameras / camcorders, positioning devices, television receivers, radio receivers, e-book devices, gaming devices, or any combination of the foregoing, including accessories and peripherals of these devices or any combination thereof. In some cases, electronic device 110 can also support any type of user-facing interface (such as "wearable" circuitry).

[0050] Server 130 can be a single physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks, and artificial intelligence platforms. Server 130 may include, for example, computing systems / servers such as mainframes, edge computing nodes, computing devices in a cloud environment, etc. Server 130 can provide backend services for applications 120 that support user interface interaction in electronic devices 110.

[0051] A communication connection can be established between server 130 and electronic device 110. This communication connection can be established via wired or wireless means. The communication connection can include, but is not limited to, Bluetooth, mobile network, Universal Serial Bus (USB), and Wireless Fidelity (WiFi) connections. In some cases, server 130 and electronic device 110 can exchange signaling information through their communication connection.

[0052] It should be understood that the structure and function of the various elements in environment 100 are described for illustrative purposes only and do not imply any limitation on the scope of the scheme.

[0053] The following description of the example will continue with reference to the accompanying drawings.

[0054] The examples described herein can be implemented on electronic device 110. It should be noted that the operations described relative to electronic device 110 can be performed by a related application 120 running on electronic device 110. The interface described relative to electronic device 110 can be provided by application 120; for example, electronic device 110 presents the corresponding interface by running application 120. Furthermore, some operations described relative to electronic device 110 may require the assistance of server 130 to complete.

[0055] Figure 2A and Figure 2B Schematic diagrams of example interfaces 200A and 200B for user interface interaction are shown, based on some scenarios. Example interfaces 200A and 200B can, for example, be derived from... Figure 1 The electronic device 110 shown is provided via application 120. Example interface 200A represents the interface state before the editing operation, and example interface 200B represents the interface state after the editing operation.

[0056] like Figure 2AAs shown, the electronic device 110 presents first content 202 in the example interface 200A. The first content 202 includes a main presentation area 210 and a thumbnail area 220. The main presentation area 210 is used to present the page content of the current page, and the thumbnail area 220 is used to present thumbnail representations of multiple page units. The first content 202 may also include a notes area 230, which is used to present or receive notes information for the current page.

[0057] In the main presentation area 210, the electronic device 110 presents a first element 212 and another element 214. The first element 212 may be, for example, an editable graphic formed by one or more graphic nodes, and the other element 214 may be, for example, a page background, text, a container, or other page object. The first element 212 is associated with a first node in the authoritative document before editing (also referred to below as the second persistent information), and the other element 214 is associated with another node in that authoritative document.

[0058] In some cases, the structured declaration indicates that the first element 212 has editable attributes that allow editing. In response to the user 140 selecting the first element 212 in the main presentation area 210, the electronic device 110 can provide the editor kernel with the element identifier of the first element 212 and the surface identifier of the current page unit, and set the first element 212 as the target of the editing operation.

[0059] In response to receiving an edit operation for the first element 212, the electronic device 110 converts the edit operation into a node update for the first node via an adapter. For example, the edit operation can adjust the single flower shape graphic represented by the first element 212 into a combined graphic including multiple flower shapes. The electronic device 110 does not need to add the node corresponding to the other element 214 to the update scope.

[0060] Electronic device 110 first locates the first node in the authoritative document before editing, and replaces or updates the attributes of the first node with the editing result, thereby obtaining the authoritative document after editing (hereinafter also referred to as the first persistent information). The authoritative document after editing still retains at least one node other than the first node in the authoritative document before editing. Electronic device 110 then refreshes the derived document model according to the authoritative document after editing, and updates the real-time document according to the refreshed derived document model.

[0061] like Figure 2B As shown, the electronic device 110 presents second content 204 based on the edited authoritative document. The second content 204 includes the main presentation area 210 and the thumbnail area 220 in the example interface 200B. The editing result corresponding to the first element 212 can be represented as element 222, which is presented as an edited composite graphic in the main presentation area 210.

[0062] Besides the first element 212, the other element 214 has the same presentation effect in the second content as its corresponding element in the first content. The thumbnail representation in the thumbnail area 220 corresponding to the current page can reflect the update of element 222, while the thumbnail representations of other page units can continue to use the original node data and loaded resources.

[0063] Through the above solution, user 140 can perform partial editing on the first element 212 in the editing interface, while electronic device 110 only updates the first node associated with that element, thus solving the difficulty of rebuilding the entire page due to local changes within the page. Since other nodes, layouts, and resources continue to be reused, the derived model and real-time document only process the affected data range. Therefore, the amount of node parsing, layout calculation, and cache writing by electronic device 110 is reduced, and the processing time required for the main rendering area 210 and thumbnail area 220 to be rendered again is correspondingly shortened.

[0064] Figure 3 A schematic diagram of a layered runtime architecture 300 for user interface interaction is shown, depending on several scenarios. The layered runtime architecture 300 may include an intelligent system generation layer 310, a host control layer 320, a runtime installation layer 330, a unified document and editing layer 340, and a deterministic presentation and output layer 350.

[0065] In the intelligent system generation layer 310, the intelligent system plans content and interaction according to the declarative document protocol, and writes assets, scripts, and styles into a complete declarative document in an isolated execution environment. The complete declarative document simultaneously carries content, structure, and runtime entry point, thus enabling it to be recognized and presented by the runtime.

[0066] In some cases, declarative documents (such as the structured declarations mentioned above) can include a variety of information and attributes to express the presentation agreement. For example, a declarative document can indicate the document root node, which can be considered a direct child node under the body, and include the document type, agreement version, active page, and global canvas scale.

[0067] In some cases, declarative documents can also specify multiple page units and page identification information. Each page unit is a direct child node of a corresponding root node, used to declare page order and page-level content. Page identification information is a unique identifier for a page within the document scope, which can be used to locate pages, restore history, write back nodes, and establish rendering units.

[0068] In some cases, declarative documentation can also indicate page scale and page notes. Page scale can be used, for example, to derive canvas height from a reference width. Page notes include optional strings that are persisted as pages are sorted, edited, and fully serialized.

[0069] In some cases, declarative documents can also indicate editable properties. These editable properties correspond to nodes or elements presented on the page, indicating whether the node or element is editable, and can be inherited by parent nodes to control whether nodes and their descendants are considered for editing.

[0070] In some cases, declarative documentation can also specify animation categories, animation steps, and wait information. Animation categories indicate the animation target and the category to be activated, used to load the corresponding animation style at the start of the animation step. Animation steps constrain the behavior of multiple animations; for example, animations belonging to the same step are rendered in parallel, while animations belonging to different steps are executed sequentially. Wait information determines whether the current animation blocks subsequent steps, thus defining when the corresponding animation should be rendered.

[0071] For example, in some cases, one of multiple page units includes a second element and a third element. The declarative document can indicate a first value for the second element and a second value for the third element, which are associated with the rendering order of a first animation corresponding to the second element and a second animation corresponding to the third element. In this case, the first and second animations can be rendered according to the rendering order corresponding to the first and second values. For example, the first and second values ​​can be non-negative integers. If the first and second values ​​correspond to the same animation execution step, the first and second animations can be rendered simultaneously.

[0072] In some cases, the declarative document can also specify a first animation style for the second element and a second animation style for the third element. In this case, a first animation corresponding to the second element can be rendered based on the first animation style, and a second animation corresponding to the third element can be rendered based on the second animation style.

[0073] In some cases, the declarative document may also indicate a wait message associated with the second element. If the wait message indicates no waiting, the second animation is presented before the first animation ends.

[0074] The host control layer 320 may include a host application and a type-safe bridging component. The host application performs loading, control, event reception, and lifecycle management through the bridging component, which restricts messages to corresponding declarative document rendering instances through handshakes, origins, channels, endpoints, and revision information. The process of performing loading, control, event reception, and lifecycle management through the bridging component will be discussed in detail below. Figure 5 A detailed description is required, so it will not be elaborated here.

[0075] The runtime installation layer 330 may include a base runtime, a format recognition and installation component, and one or more format runtimes. The base runtime provides bridging communication, status, editing, and common capabilities. The format recognition and installation component verifies the root structure, page units, and protocol attributes of declarative documents and assembles a presentation runtime or a web page runtime according to the document type.

[0076] The presentation runtime and the web runtime can share bridging, editor kernel, resource caching, and rendering control capabilities. The presentation runtime provides thumbnails, a main stage, page transitions, annotations, and animation capabilities, while the web runtime provides fluid page and webpage interaction capabilities. Other document formats can also be integrated into this layered architecture by adding corresponding authoritative document parsing methods, adapters, and runtime entry points.

[0077] Each runtime format can generate deployable runtime artifacts, and protocol mismatches can be avoided by using runtime version and deployment environment information. Declarative documents can load the base runtime and the target format runtime on demand, reducing runtime resources unrelated to the current document format.

[0078] For example, in some cases, Figure 2A The first content 202 shown may be presented by loading runtime information into a declarative document. This runtime information may include, for example, the basic runtime information already mentioned above, as well as presentation runtime and webpage runtime information.

[0079] The unified document and editing layer 340 may include authoritative documents (such as the persistent information mentioned above), derived document models, live documents, editor kernels, and format adapters. In some cases, authoritative documents maintain writable author semantics, derived document models provide read-only queries, live documents are used for service rendering, editor kernels handle general editing tables, and format adapters are responsible for conversion between editing surfaces and authoritative document nodes.

[0080] For example, in some cases, the second persistent information mentioned above is presented... Figure 2A The first content 202 shown was previously obtained by cloning a declarative document (i.e., a structured declaration). In some cases, the first storage information can be obtained based on the second persistent information. For example, the storage information may be a snapshot corresponding to the persistent information.

[0081] In some cases, second stored information can be obtained based on the first persistent information. The first persistent information is persistent information used to present the second content 204. In some cases, the second stored information can directly overwrite the first stored information.

[0082] The deterministic rendering and output layer 350 maps each page to a stable rendering unit and generates a revision identifier for the current document state. After rendering preparation, resource readiness, and output data formation, the electronic device 110 verifies the expected revision identifier. If the authoritative document changes during processing, the electronic device 110 rejects the rendering task for the old state. Off-screen rendering can wait for font and image resources to be ready, for multiple rendering frames to stabilize, and for animation states to converge; in case of anomalies or cancellations, the electronic device 110 releases off-screen nodes and resource leases.

[0083] Through the above scheme, the layered operation architecture 300 assigns generation, communication, format rendering, editing and writing back, and persistence processing to components with clearly defined responsibilities, thereby solving the difficulties of repeated implementation of common capabilities and unclear operational boundaries when different document formats are accessed. Shared basic capabilities reduce repeated initialization and resource loading, and the format runtime only processes content related to the target format. As a result, the number of running components and resource consumption of the electronic device 110 can be reduced, and the protocol processing path remains consistent when different formats are extended.

[0084] Figure 4 The diagram illustrates authoritative documents, derived document models, real-time documents, and an editing and saving path 400, depending on various scenarios. The processing path 400 may include an authoritative document layer 410, a format recognition and derived model layer 420, a format runtime layer 430, a real-world rendering pipeline 440, a non-persistence branch 450, a saving branch 460, and an editing feedback loop 470.

[0085] The real-time documents in the authoritative document layer 410, derived document model layer 420, and real-time rendering pipeline 440 have interconnected but distinct responsibilities. In some cases, the authoritative document (also referred to as persistent information in the text) may include a complete document type declaration, header and body information, author styles, scripts, resources, and page units as the authoritative source for preservation. Subsequent edits only update the target page nodes or the author body. The derived document model may include a title, resource base address, scale, page mapping, rendered content, content summary, notes, editable areas, and animation targets, which are parsed by the authoritative document and used only for querying and rendering acceleration. After the authoritative document is updated, the derived document model will be re-parsed. Real-time documents may include an interface shell, main stage, thumbnails, notes area, editing canvas, running status, and temporary styles, which are used only for visual and interactive purposes; the complete real-time document is not saved as a result.

[0086] Before running the shell to replace the source node of the declarative document, electronic device 110 clones the complete declarative document to form a pre-edit authoritative document. Electronic device 110 then loads the base runtime and format runtime into the declarative document and renders the first content according to the derived document model. Thus, the pre-edit authoritative document retains the author structure before the runtime information was loaded.

[0087] The format runtime layer 430 can select different real-time rendering methods based on the document type. For presentations, the componentized interface shell manages thumbnails, the main stage, page selection, notes, and presentation status, while the original page content is injected as content islands into the corresponding presentation surfaces. Content summaries and page identifiers are used to maintain page identity, and the main stage, thumbnails, and off-screen surfaces can use the same page content but employ different animation or interaction strategies.

[0088] For web pages, the format runtime layer 430 can perform in-situ coordination on nodes with identification keys in the author body. The electronic device 110 aligns nodes based on the identification information and tries to preserve the identity of unchanged nodes and established event handling relationships.

[0089] When the edited result arrives, the electronic device 110 first submits the local changes to the authoritative document layer 410, then causes the derived document model layer 420 to re-parse the affected pages, and finally the format runtime layer 430 updates the real-world rendering pipeline 440 according to the new derived document model. This sequence advances the persistent state before the real-time state.

[0090] The rendering pipeline 440 may also include resource address resolution and caching. Electronic device 110 can resolve document attributes, candidate source sets, inline styles, or image addresses in style sheets, and reuse resources through memory caching, persistent caching, or object address leases. Caching can employ appropriate expiration periods, capacity limits, and least recently used cleanup strategies. At the end of rendering or editing, electronic device 110 restores the original resource addresses provided by the author; authoritative documents do not save runtime object addresses.

[0091] For elements that lack an author identifier but are editable, electronic device 110 can generate a temporary identifier based on the node path, content summary, or other deterministic information. The temporary identifier is used for selection, positioning, and partial updates, and is deleted when the author document of branch 460 is serialized; the original author identifier is retained.

[0092] The "Disallow Persistence" branch 450 indicates that neither live documents nor user-visible pixels are used as sources for storage. The "Save" branch 460 generates storage information only from cloned copies of authoritative documents, restoring author resource addresses, cleaning up ephemeral nodes, ephemeral identifiers, run categories, and ephemeral topic information before serialization.

[0093] When saving, the host requests and calls the document retrieval interface of the format runtime to obtain the serialized content of the complete authoritative document. The host does not directly read the complete structure of the componentized interface shell, editor canvas, or live document.

[0094] The edit feedback loop 470 can be executed in the following order: user editing, editing surface snapshot, adapter serial commit, partial update of authoritative document, advancement of runtime revision flag, re-parsing of derived model, and refreshing of live document. The runtime revision flag is used to verify the consistency of the current round of derived model and rendering task; it does not indicate that the persistent system has stored multiple document versions.

[0095] Through the above scheme, the authoritative document is always updated before the derived document model and the real-time document, and the saved branch only reads the authoritative document, thus solving the problem of the running shell or temporary state potentially entering the stored information. The real-time document can continue to retain unchanged nodes and loaded resources, and the derived model only needs to reparse the affected data range. As a result, the number of node reconstructions, resource decodings, and memory writes of the electronic device 110 can be reduced, and the content obtained after reloading is consistent with the edited authoritative state.

[0096] Figure 5 A schematic diagram of a bridging communication flow 500 between the host and the embedded framework runtime is shown, depending on certain scenarios. The bridging communication flow 500 may include handshake 510, binding 520, request 530, response 540, cancellation 550, and disconnection 560.

[0097] Bridged communication uses message envelopes to separate service-specific information from routing, versioning, association, and endpoint information. Example field groups and their uses in the message envelope are shown in the table below.

[0098]

[0099] In handshake 510, the host bridge generates a first identifier and sends a handshake message (also referred to as the first message in this document) containing the first identifier and channel information of the first channel to the first window. If a handshake response is not received, the host bridge can resend the handshake message at a set interval to accommodate differences in the initialization order between the host and the embedded frame.

[0100] Upon receiving the handshake message, the embedded framework runtime verifies the message's source window, source address, protocol flag, protocol version, and channel information. If the verification passes, the embedded framework runtime saves the source endpoint information and returns a response message including association information, first source endpoint information, and channel information. After the host bridge determines that the association information matches the first identifier, it saves the first source endpoint information as the peer information, thus completing the peer binding.

[0101] In request 530, the host bridge or embedded frame runtime can obtain a second message including edit operation instruction information, source address, second source endpoint information, and target endpoint information. Electronic device 110 only delivers the second message to the protocol processor and presents the second content based on the instruction information if the second message originates from the first window, the source address belongs to the allowed address set, the target endpoint information matches the local endpoint information, and the second source endpoint information matches the bound peer information. If any condition is not met, electronic device 110 discards the second message.

[0102] Request messages can be added to the processing queue using a message identifier. After the embedded framework completes the request, it returns a response message with corresponding association information in response 540. The host bridge matches pending requests based on the association information and removes the corresponding pending item after a successful result or a structured error.

[0103] In Cancel 550, when a request times out or the host receives an abort signal, the host bridge can remove the pending item and send a cancellation message associated with the request identifier. The embedded frame runtime stops the corresponding task based on this association information. In Disconnect 560, when a window is destroyed, a channel is closed, or the peer changes, the bridge component rejects pending requests and cleans up message processing relationships.

[0104] In some cases, the bridging component uses the precise target source address and configures the set of allowed addresses. For embedded frames where the source address cannot be directly represented, the bridging component can use a target address setting appropriate for the operating environment, provided that the set of allowed addresses is explicitly configured.

[0105] Through the above scheme, the bridging component jointly verifies the window, source address, channel, and endpoint before the message enters the editing or rendering process, thereby solving the problem that messages may mistakenly enter other instances or untrusted messages may reach the processor when multiple rendering instances coexist. Invalid messages are discarded at the inbound security gate, and the electronic device 110 does not need to create an editing transaction or rendering task for them. As a result, the number of invalid items in the pending queue and the computational overhead caused by error messages can be reduced, and the communication range between the host and the embedded frame is stably constrained.

[0106] Figure 6 A schematic diagram of an editing, re-rendering, and persistence loop 600 based on several scenarios is shown. Loop 600 may include an active rendering surface 602, an editor kernel 604, an editor rendering surface snapshot 606, an adapter 608, an authoritative document 610, a derived model and revision state 612, a live document 614, an updated active rendering surface 616, a user interaction history 618, runtime 620, a fully declarative document update 622, and persistence rules 624.

[0107] When the active drawing surface 602 enters the editing state, the editor kernel 604 can first settle the current animation state and prepare the interactive layer. After the user completes text, style, image, or layout operations, the editor kernel 604 generates an editor drawing surface snapshot 606 at the animation frame boundary. During continuous dragging, the commit can be postponed, and the change is treated as an editing transaction when the drag ends.

[0108] Adapter 608 applies editor drawing face snapshot 606 to authoritative document 610 via a serial submission queue. For presentations, adapter 608 locates the current page cell and updates only the first node associated with the first element; for web pages, adapter 608 can update the corresponding node in the author body. Other nodes in authoritative document 610 are preserved.

[0109] After the authoritative document 610 is updated, runtime 620 re-parses and advances the derived model and revision state 612, and then refreshes the affected presentation content of the live document 614. The electronic device 110 forms an updated active drawing surface 616 from the live document 614 and can continue to receive the next editing operation.

[0110] When the intelligent system generates a new, complete declarative document, runtime 620 can first commit the remaining partial edits and synchronize the current historical state. Runtime 620 then captures, verifies, and replaces the complete authoritative document 610. This complete document update can serve as an atomic checkpoint, allowing the most recent complete document update to be completely undone.

[0111] User interaction history 618 can save snapshots of edited surfaces and undo cursors, while document-level history can save complete authoritative document snapshots and active surface identifiers. When restoring history, runtime 620 coordinates attributes, style categories, and text according to page identifiers; unchanged image or media nodes can maintain their identity and loading state. The two types of history for presentations are sequentially linked through commit, synchronization, saving, and applying snapshots, while web pages can use a single edited surface history and optionally support full document checkpoints.

[0112] In some cases, based on the authoritative document prior to editing, electronic device 110 can obtain the first stored information. The first stored information can serve as persistent data for reloading the first content or restoring the state prior to editing.

[0113] In response to an undo operation on an edit, the electronic device 110 can re-present the first content based on the user interaction history 618 and the first stored information. The undo process can be completed locally, without needing to retrieve multiple historical versions from a persistent system.

[0114] Based on the edited authoritative document, electronic device 110 can obtain the second storage information and overwrite the first storage information with a complete document save. The revision identifier during runtime can continue to be used to verify whether the derived model and the rendering task correspond to the same document state, but the persistence system does not need to create multiple saved versions.

[0115] Persistence rule 624 restricts the save process to reading only the authoritative document 610, and not the live document 614 or the active drawing surface 602. The host can request the complete authoritative document content upon save, avoiding the continuous transfer of the complete document during high-frequency partial editing.

[0116] Through the above solution, the editor kernel 604 converges user operations into transactions specific to the editing surface, and the adapter 608 only writes the transactions back to the associated nodes in the authoritative document 610. This resolves the difficulties of unclear data ownership between partial editing and complete saving, as well as the problem of undo paths easily becoming mixed with persistent states. The user interaction history 618 supports undo and redo locally, and the host only obtains the complete authoritative document upon saving. As a result, the number of whole document transfers, the number of reconstructions of unchanged nodes, and the number of media resource reloads during editing can be reduced, and the editing response time and the amount of data communicated between the end and the cloud can be reduced accordingly.

[0117] Figure 7 A flowchart of an example process 700 for interface interaction is shown, based on some scenarios. Process 700 can be implemented at electronic device 110. See below for reference. Figure 7 To describe process 700.

[0118] like Figure 7 As shown in box 710, the electronic device 110 presents the first content in the editing interface. The first content is presented through a structured declaration, which includes multiple elements. The structured declaration is created by the intelligent system. Its interactive presentation can be found above. Figure 2A The example described.

[0119] like Figure 7 As shown, in box 720, electronic device 110 receives an editing operation, which targets the first element among multiple elements. Its interactive presentation can be found above. Figure 2A The example described.

[0120] like Figure 7 As shown, in box 730, the electronic device 110 presents second content. This second content is based on first persistent information, which is obtained by editing the first node of the second persistent information using an edit operation. The second persistent information originates from a structured declaration, and the first node is associated with the first element. Its interactive presentation can be found above. Figure 2B The example described.

[0121] In some cases, besides the first element, other elements among multiple elements can have the same presentation effect in the second content as their corresponding elements in the first content. For specific interactive presentation details, please refer to the above text. Figure 2A and Figure 2B The example described.

[0122] In some cases, the second persistent information also includes at least one node other than the first node, which is retained in the first persistent information.

[0123] In some cases, electronic device 110 can obtain first stored information based on the second persistent information. For specific interaction details, please refer to the above. Figure 6 The example described.

[0124] In some cases, the electronic device 110 can respond to an undo operation on an editing operation and re-present the first content based on the first stored information. For specific interactive presentation details, please refer to the above. Figure 6 The example described.

[0125] In some cases, electronic device 110 can obtain second stored information based on the first persistent information, with the second stored information overwriting the first stored information. For specific interaction details, please refer to the above. Figure 6 The example described.

[0126] In some cases, a structured declaration can have a root node and multiple page units, where each page unit is a child node of the root node. Multiple elements are distributed across these page units. The second persistent information includes multiple nodes, each corresponding to a page unit, and each node must include at least the first node. For specific interactive presentation details, please refer to the above text. Figure 4 The example described.

[0127] In some cases, multiple page units can correspond to multiple identifiers. The first identifier among these identifiers is used to locate the first page unit corresponding to the first element during editing. For specific interactive presentation details, please refer to the above text. Figure 4 The example described.

[0128] In some cases, structured declarations can also indicate that the first element has editable attributes that indicate editability. See above for specific interactive rendering examples. Figure 4 The example described.

[0129] In some cases, one of multiple page units may include a second element and a third element. A structured declaration may indicate a first value for the second element and a second value for the third element. The first and second values ​​may be associated with the presentation order of a first animation corresponding to the second element and a second animation corresponding to the third element. Presenting first content by the electronic device 110 may include presenting the first and second animations based on the presentation order. Specific interactive presentation details can be found above. Figure 4 The example described.

[0130] In some cases, structured declarations can also specify a first animation style for a second element and a second animation style for a third element. The electronic device 110's presentation of the first content may include: presenting a first animation of the second element based on the first animation style; and, after the first animation, presenting a second animation of the third element based on the second animation style. Specific interactive presentations can be found above. Figure 4 The example described.

[0131] In some cases, structured statements can also indicate waiting information associated with the second element. Based on this waiting information, the electronic device 110 indicates not to wait and presents the second animation before the first animation ends. For specific interactive presentation details, please refer to the above. Figure 4 The example described.

[0132] In some cases, the first content can be presented after loading runtime information into the structured declaration, while the second persistent information can be obtained by cloning the structured declaration before presenting the first content. For specific interactive presentation details, please refer to the above text. Figure 4 and Figure 6 The example described.

[0133] In some scenarios, the first channel may correspond to a single presentation of the first content. The electronic device 110 may also send a second message to the first window, the second message containing a first identifier and channel information of the first channel; obtain a response message, the response message including association information, first source endpoint information, and channel information; and, based on the consistency between the association information and the first identifier, save the first source endpoint information as peer information. For specific interactive presentation details, please refer to the above. Figure 5 The example described.

[0134] In some scenarios, electronic device 110 can acquire a second message, which includes instructions for editing operations, a source address, second source endpoint information, and target endpoint information, wherein the instructions indicate the first element; and based on the following conditions being met, presenting second content based on the instructions; or based on at least one of the following conditions being unmet, discarding the second message: the second message originates from the first window, the source address belongs to the allowed address set, the target endpoint information is consistent with the local endpoint information, and the second source endpoint information is consistent with the peer information. For specific interactive presentation details, please refer to the above. Figure 5 The example described.

[0135] Through the above scheme, the electronic device 110 presents the first content as input using a declarative document within the same editing interface, and positions the editing operation on the first element to the associated node in the authoritative document, thus addressing the difficulty of continuing to address and partially modify page elements after presentation. Node-level write-back allows the editing results to be passed to the main presentation area 210 and the thumbnail area 220 via the authoritative document, derived document model, and real-time document, while retaining unchanged nodes, thereby reducing full-page reconstruction and media resource reloading. As a result, the electronic device 110 can shorten the interface refresh time after editing, reduce the amount of computation and end-to-cloud communication data during editing, and provide users with consistent editing feedback in the main presentation area 210 and the thumbnail area 220.

[0136] A corresponding apparatus for implementing the above methods or processes is also provided.

[0137] Figure 8 Block diagrams of a device 800 for user interface interaction are shown in some scenarios. Device 800 can be implemented as or included in electronic device 110. Various modules or components in device 800 can be implemented by hardware, software, firmware, or any combination thereof.

[0138] like Figure 8 As shown, the device 800 includes a first presentation module 810 configured to present first content in an editing interface. The first content is presented through a structured declaration, which includes multiple elements. The structured declaration is created by an intelligent system. A receiving module 820 is configured to receive an editing operation targeting the first element among the multiple elements. A second presentation module 830 is configured to present second content based on first persistent information. The first persistent information is obtained by editing the first node of the second persistent information based on the editing operation. The second persistent information originates from the structured declaration, and the first node is associated with the first element.

[0139] In some cases, other elements among multiple elements, besides the first element, can have the same presentation effect in the second content as their corresponding elements in the first content.

[0140] In some cases, the second persistent information also includes at least one node other than the first node, which is retained in the first persistent information.

[0141] In some cases, the first presentation module 810 can also be configured to obtain the first stored information based on the second persistent information. In some cases, the first presentation module 810 can also be configured to re-present the first content based on the first stored information in response to an undo operation on an edit operation.

[0142] In some cases, the second presentation module 830 can also be configured to obtain second storage information based on the first persistent information, with the second storage information overwriting the first storage information.

[0143] In some cases, a structured declaration may have a root node and multiple page units, with the multiple page units being child nodes of the root node. Multiple elements are distributed across the multiple page units. The second persistent information includes multiple nodes, which correspond to the multiple page units, and the multiple nodes include at least the first node.

[0144] In some cases, multiple page units can correspond to multiple identification information, and the first identification information among the multiple identification information is used to locate the first page unit corresponding to the first element in the editing operation.

[0145] In some cases, a structured declaration can also indicate that the first element has editable attributes that indicate that editing is allowed.

[0146] In some cases, the first presentation module 810 may also be configured to present first content according to the following page information: one of the multiple page units includes a second element and a third element, a structured declaration may indicate a first value of the second element and a second value of the third element, the first value and the second value may be associated with the presentation order of a first animation corresponding to the second element and a second animation corresponding to the third element, and the first presentation module 810 may present the first animation and the second animation based on the presentation order.

[0147] In some cases, the first presentation module 810 may also be configured to present the first content according to the following animation information: the structured declaration also indicates the first animation style of the second element and the second animation style of the third element, and presenting the first content includes: presenting the first animation of the second element based on the first animation style; and presenting the second animation of the third element based on the second animation style after the first animation.

[0148] In some cases, the first presentation module 810 may also be configured to present the animation according to the following waiting information: the structured declaration also indicates waiting information associated with the second element, based on which the waiting information indicates not to wait and to present the second animation before the first animation ends.

[0149] In some cases, the first presentation module 810 may also be configured to form content for presentation in the following sequence: the first content is presented after loading runtime information into the structured declaration, and the second persistent information is obtained by cloning the structured declaration before presenting the first content.

[0150] In some cases, the first channel may correspond to a single presentation of the first content, and the receiving module 820 may also be configured to send a second message to the first window, the second message having a first identifier and channel information of the first channel; obtain a response message, the response message including association information, first source endpoint information and channel information; and based on the consistency between the association information and the first identifier, save the first source endpoint information as peer information.

[0151] In some cases, the receiving module 820 may also be configured to acquire a second message, the second message including instructions for editing operations, a source address, second source endpoint information, and target endpoint information, the instructions indicating the first element; and the second presentation module 830 may also be configured to present the second content based on the instructions, provided that all of the following are true; or the receiving module 820 may also be configured to discard the second message if at least one of the following is false: the second message comes from the first window, the source address belongs to the set of allowed addresses, the target endpoint information is consistent with the local endpoint information, and the second source endpoint information is consistent with the peer information.

[0152] The modules included in device 800 can be implemented in various ways, including software, hardware, firmware, or any combination thereof. In some cases, one or more modules can be implemented using software and / or firmware, such as machine-executable instructions stored on a storage medium. In addition to or as an alternative to machine-executable instructions, some or all of the units in device 800 can be implemented at least partially by one or more hardware logic components. By way of example, and not limitation, exemplary types of hardware logic components that can be used include field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard parts (ASSPs), systems on a chip (SOCs), complex programmable logic devices (CPLDs), and so on.

[0153] Figure 9 A block diagram of an electronic device 900 in which one or more examples may be implemented is shown. It should be understood that... Figure 9 The electronic device 900 shown is merely exemplary and should not be construed as limiting the functionality and scope of the examples described herein. Figure 9 The electronic device 900 shown can be used to implement the electronic device 110 discussed above.

[0154] like Figure 9 As shown, electronic device 900 is in the form of a general-purpose electronic device. Components of electronic device 900 may include, but are not limited to, one or more processing units or processors 910, memory 920, storage devices 930, one or more communication units 940, one or more input devices 950, and one or more output devices 960. Processor 910 may be a physical or virtual processor and is capable of performing various processes according to programs stored in memory 920. In a multiprocessor system, multiple processors execute computer-executable instructions in parallel to improve the parallel processing capability of electronic device 900.

[0155] Electronic device 900 typically includes multiple computer storage media. Such media can be any accessible media that is accessible to electronic device 900, including but not limited to volatile and non-volatile media, removable and non-removable media. Memory 920 can be volatile memory (e.g., registers, cache, random access memory (RAM)), non-volatile memory (e.g., read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof). Storage device 930 can be removable or non-removable media and may include machine-readable media, such as flash drives, disks, or any other media capable of storing information and / or data and accessible within electronic device 900.

[0156] Electronic device 900 may further include additional removable / non-removable, volatile / non-volatile storage media. Although not explicitly stated... Figure 9 As shown, disk drives for reading from or writing to removable, non-volatile disks (e.g., "floppy disks") and optical disk drives for reading from or writing to removable, non-volatile optical disks can be provided. In these cases, each drive can be connected to a bus (not shown) via one or more data media interfaces. Memory 920 may include computer program product 925 having one or more program modules configured to perform various methods or actions of various examples.

[0157] The communication unit 940 enables communication with other electronic devices via a communication medium. Additionally, the functionality of the components of the electronic device 900 can be implemented using a single computing cluster or multiple computing machines capable of communicating via communication connections. Therefore, the electronic device 900 can operate in a networked environment using logical connections to one or more other servers, networked personal computers, or another network node.

[0158] Input device 950 can be one or more input devices, such as a mouse, keyboard, trackball, etc. Output device 960 can be one or more output devices, such as a monitor, speaker, printer, etc. Electronic device 900 can also communicate with one or more external devices (not shown) via communication unit 940 as needed. External devices include storage devices, display devices, etc., and can communicate with one or more devices that enable user interaction with electronic device 900, or with any device that enables electronic device 900 to communicate with one or more other electronic devices (e.g., network card, modem, etc.). Such communication can be performed via input / output (I / O) interface (not shown).

[0159] A computer-readable storage medium is provided that stores computer-executable instructions thereon, wherein the computer-executable instructions are executed by a processor to implement the methods described above. A computer program product is also provided, which is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, which are executed by a processor to implement the methods described above.

[0160] The flowcharts and / or block diagrams of the methods, apparatus, devices, and computer program products referred to herein describe various aspects. It should be understood that each block of the flowcharts and / or block diagrams, as well as combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer-readable program instructions.

[0161] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processor of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner; thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0162] Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions that execute on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0163] The flowcharts and block diagrams in the accompanying figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products under various scenarios. In this respect, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction, which contains one or more executable instructions for implementing the specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than those shown in the figures. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0164] Various examples have been described above. The foregoing descriptions are exemplary and not exhaustive, nor are they limited to the disclosed implementations. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described implementations. The terminology used herein is chosen to best explain the principles, practical applications, or improvements to technology in the market, or to enable others skilled in the art to understand the various implementations described herein.

Claims

1. A method for interface interaction, comprising: In the editing interface, the first content is presented, which is presented through a structured declaration. The first content includes multiple elements, and the structured declaration is created by the intelligent system. Receive an edit operation, wherein the edit operation is applied to a first element among the plurality of elements; as well as The second content is presented based on the first persistent information, which is obtained by editing the first node of the second persistent information based on the editing operation. The second persistent information originates from the structured declaration, and the first node is associated with the first element.

2. The method according to claim 1, wherein, apart from the first element, the other elements among the plurality of elements have the same presentation effect in the second content as the corresponding elements in the first content.

3. The method according to claim 1, further comprising: The first storage information is obtained based on the second persistent information.

4. The method according to claim 3, further comprising: In response to the undo operation of the edit operation, the first content is presented again based on the first stored information.

5. The method according to claim 3, further comprising: The second storage information is obtained based on the first persistent information, and the second storage information overwrites the first storage information.

6. The method according to claim 1, wherein the structured declaration has a root node and a plurality of page units, the plurality of page units being child nodes of the root node, the plurality of elements being distributed in the plurality of page units, the second persistent information including a plurality of nodes, the plurality of nodes corresponding to the plurality of page units, and the plurality of nodes including at least the first node.

7. The method according to claim 6, wherein the plurality of page units correspond to a plurality of identification information, and the first identification information among the plurality of identification information is used to locate the first page unit corresponding to the first element in the editing operation.

8. The method of claim 7, wherein the structured statement further indicates that the first element has an editable attribute indicating that editing is permitted.

9. The method of claim 6, wherein one of the plurality of page units includes a second element and a third element, the structured declaration indicating a first value of the second element and a second value of the third element, the first value and the second value being associated with a presentation order of a first animation corresponding to the second element and a second animation corresponding to the third element, and presenting the first content includes: The first animation and the second animation are presented in the order stated.

10. The method of claim 9, wherein the structured declaration further indicates a first animation style for the second element and a second animation style for the third element, presenting the first content comprising: The first animation of the second element is presented based on the first animation style; as well as The second animation of the third element is presented based on the second animation style.

11. The method of claim 9, wherein the structured statement further indicates waiting information associated with the second element, and based on the waiting information indicates not to wait, and to present the second animation before the first animation ends.

12. The method of claim 1, wherein the first content is presented after loading runtime information into the structured declaration, and the second persistent information is obtained by cloning the structured declaration before presenting the first content.

13. The method of claim 1, wherein the second persistent information further includes at least one node other than the first node, the at least one node being retained in the first persistent information.

14. The method of claim 1, wherein the first channel corresponds to a single presentation of the first content, the method further comprising: Send a first message to the first window, the first message having a first identifier and channel information of the first channel; Obtain a response message, the response message including association information, first source endpoint information, and the channel information; as well as Based on the consistency between the associated information and the first identifier, the first source endpoint information is recorded as peer information.

15. The method of claim 14, further comprising: Obtain a second message, which includes instruction information for the editing operation, source address, second source endpoint information, and target endpoint information, wherein the instruction information indicates the first element; as well as The second content is presented based on the indication information if all of the following conditions are met; or The second message shall be discarded if at least one of the following conditions is not met: The second message comes from the first window. The source address belongs to the allowed address set. The target endpoint information is consistent with the local endpoint information. The second source endpoint information is consistent with the peer endpoint information.

16. A device for interface interaction, comprising: The first presentation module is configured to present first content in the editing interface. The first content is presented through a structured declaration, which includes multiple elements and is created by an intelligent system. A receiving module is configured to receive an editing operation, the editing operation being directed at a first element among the plurality of elements; as well as The second presentation module is configured to present second content based on first persistent information. The first persistent information is obtained by editing the first node of the second persistent information based on the editing operation. The second persistent information originates from the structured declaration, and the first node is associated with the first element.

17. An electronic device comprising: At least one processor; as well as At least one memory coupled to the at least one processor and storing instructions for execution by the at least one processor, the instructions causing the electronic device to perform the method according to any one of claims 1 to 15 when executed by the at least one processor.

18. A computer-readable storage medium having stored thereon computer-executable instructions that can be executed by a processor to implement the method according to any one of claims 1 to 15.

19. A computer program product tangibly stored in a computer storage medium and comprising computer-executable instructions that, when executed by a device, cause the device to perform the method according to any one of claims 1 to 15.