CN116974429A

CN116974429A - Document processing method, device, terminal, medium and program product

Info

Publication number: CN116974429A
Application number: CN202211632678.2A
Authority: CN
Inventors: 李森; 许杞蕴; 梁丽; 郭林烁; 邱凯捷; 许海浩; 杨颢
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2022-12-19
Filing date: 2022-12-19
Publication date: 2023-10-31

Abstract

The embodiment of the application provides a document processing method, a device, a terminal, a medium and a program product, wherein the method comprises the following steps: displaying an editing interface of a second sub-document in the target document; in the editing interface of the second sub-document, the content data in the first sub-document is displayed in canvas form. The embodiment of the application can realize the data interconnection and intercommunication of different types of sub-documents in the target document.

Description

Document processing method, device, terminal, medium and program product

Technical Field

The present application relates to the field of computer technology, and in particular, to the field of document processing, and more particularly, to a document processing method, a document processing apparatus, a terminal, a computer readable storage medium, and a computer program product.

Background

The category fusion refers to the process of associating different category data so as to realize interconnection and intercommunication of the different category data.

At present, the class fusion strategy provided by the document application program is simple, and only shallow data fusion can be realized. For example, the document application supports inserting a link to a textual product document (e.g., doc document) into a tabular product document (e.g., sheet document) such that a jump from the tabular product document to the textual product document may be made in the tabular product document by triggering the link. The existing simple class fusion mode does not realize deep interconnection of classes, and cannot meet the class data fusion requirements of users in various application scenes.

Disclosure of Invention

The embodiment of the application provides a document processing method, a device, a terminal, a medium and a program product, which can realize the data interconnection and intercommunication of different types of sub-documents in a target document.

In one aspect, an embodiment of the present application provides a document processing method, including:

displaying an editing interface of a second sub-document in the target document, wherein the target document comprises a first sub-document and a second sub-document, the first sub-document belongs to a first document class, and the second sub-document belongs to a second document class;

in the editing interface of the second sub-document, the content data in the first sub-document is displayed in canvas form, and the content data is kept updated synchronously in the first sub-document and the second sub-document.

In another aspect, an embodiment of the present application provides a document processing apparatus, including:

the display unit is used for displaying an editing interface of a second sub-document in the target document, wherein the target document comprises a first sub-document and a second sub-document, the first sub-document belongs to a first document class, and the second sub-document belongs to a second document class;

and the processing unit is used for displaying the content data in the first sub-document in the form of canvas in the editing interface of the second sub-document, and the content data is synchronously updated in the first sub-document and the second sub-document.

In one implementation, the processing unit is configured to, when displaying the editing interface of the second sub-document in the target document, specifically:

receiving a sub-document creation operation aiming at a target document, and displaying an editing interface of a created second sub-document;

wherein the sub-document creation operation includes at least one of: a referencing operation for content data in the first sub-document; aiming at the triggering operation of the sub-document creating control, the sub-document creating control is displayed in a toolbar of the target document, or the sub-document creating control is displayed in an option window; gesture operations in the target document or in the editing interface of the first sub-document; a voice input operation in the target document or in the editing interface of the first sub-document; or a shortcut key input operation.

In one implementation, if the sub-document creation operation includes any of the following: aiming at the triggering operation of the sub-document creating control, the gesture operation in the target document or the editing interface of the first sub-document, the voice input operation in the target document or the editing interface of the first sub-document, or the shortcut key input operation, the editing interface of the second sub-document is created as a blank interface;

If the sub-document creation operation includes: and (3) carrying out reference operation on the content data in the first sub-document, and automatically filling the content data which is referenced in the editing interface of the first sub-document in the editing interface of the created second sub-document.

In one implementation, the first document class is a form class, the content data contained in the editing interface of the first sub-document is form data, and the second document class is a canvas class;

the editing interface of the second sub-document automatically populates the referenced content data in the manner of: automatically populating in the first component the form data referenced in the first sub-document; the first component is a default component or a component selected from the component panels in a self-defining way, the component type of the first component is a chart type, and the first component belonging to the chart type comprises any one of the following components: list components, sector diagram components, polyline components, circle components, and column diagram components.

In one implementation, the processing unit is further configured to:

in response to a component creation operation for the second sub-document, displaying a component panel, the component panel containing a type identification of at least one component type;

and displaying a second component under the target component type corresponding to the selected target type identifier in a second sub-document interface according to the identifier selection operation.

In one implementation, the component creation operation includes any of the following: an input operation of a shortcut key, a trigger operation of creating an option for a component, or a gesture operation in an editing interface of a second sub-document;

the display mode of the component panel comprises the following steps: displaying the second sub-document on the editing interface of the second sub-document in a floating layer window mode or displaying the second sub-document in a target area in the editing interface of the second sub-document;

the identification selection operation includes: triggering operation aiming at the target type identifier or dragging operation for moving the target type identifier from the component panel to the editing interface of the second sub-document.

In one implementation, the editing interface of the second sub-document includes a target component, where the target component is the first component or the second component; the processing unit is further used for:

when the target component is triggered, a component configuration menu is displayed, wherein the component configuration menu contains data source configuration options;

when the data source configuration option is triggered, displaying data source identifications of one or more candidate data sources; the candidate data sources include at least one of: a first sub-document in the target document, independent of the reference document of the target document, or independent of a sub-document in the reference document of the target document;

Content data in the first sub-document is displayed in the target component in response to a triggering operation for the data source identification of the first sub-document.

In one implementation, the processing unit is further configured to:

and if the content data in the first sub-document is updated, synchronously displaying the updated content data in the first sub-document in the target component.

In one implementation, the processing unit is further configured to:

outputting data update prompt information, wherein the data update prompt information is used for indicating: the content data in the first sub-document changes;

when a confirmation operation for the data update prompt information exists, triggering and executing the step of synchronously displaying the content data in the updated first sub-document in the target component.

In one implementation, the processing unit is further configured to:

when the operation aiming at the data updating prompt information is a newly-built component, a third component is created, and content data in the updated first sub-document is displayed in the third component;

the third component and the target component are the same in component type; the third component is displayed in the second sub-document interface, or the third component is displayed in the editing interface of the newly built sub-document belonging to the second document category.

In one implementation, one or more candidate component styles corresponding to the target component are contained in the component configuration menu; the processing unit is further used for:

in response to a selection operation for a target component style of the one or more candidate component styles, in an editing interface of the second sub-document, the component style update of the target component is displayed as the target component style.

In one implementation, the processing unit is further configured to:

switching display from the editing interface of the second sub-document to the editing interface of the first sub-document according to the data source viewing operation for the target component;

in the editing interface of the first sub-document, the content data referenced in the first sub-document is highlighted.

In one implementation, the processing unit is further configured to:

executing drag operation on the target component in the editing interface of the second sub-document;

controlling the target component to move in the editing interface of the second sub-document according to the dragging operation;

wherein the layout style of the plurality of components in the second sub-document comprises: displaying in parallel along the horizontal direction of the editing interface of the second sub-document; or, displaying the second sub-document side by side along the vertical direction of the editing interface of the second sub-document; or, along a diagonal direction of the editing interface of the second sub-document.

In one implementation, the first sub-document is any one of at least one sub-document belonging to a first document class in the target document and the second sub-document is any one of at least one sub-document belonging to a second document class in the target document.

In one implementation, the process of creating the second sub-document in the target document includes:

generating a software development kit based on the document data stream of the second sub-document;

integrating the software development kit into a target document;

a second sub-document is created in the target document that integrates the software development kit.

In one implementation, the processing unit is configured to, when displaying the content data in the first sub-document in canvas form in the editing interface of the second sub-document, specifically configured to:

storing the document identification of the first sub-document into a document data stream of the second sub-document;

the second sub-document invokes content data in the first sub-document based on the document identification of the first sub-document.

In another aspect, an embodiment of the present application provides a terminal, including:

a processor adapted to execute a computer program;

a computer readable storage medium having a computer program stored therein, which when executed by a processor, implements a document processing method as described above.

In another aspect, embodiments of the present application provide a computer readable storage medium storing computer instructions adapted to be loaded by a processor and to perform a document processing method as described above.

In another aspect, embodiments of the present application provide a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the terminal reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions so that the terminal performs the document processing method described above.

In the embodiment of the application, on one hand, the sub-documents of different document classes are supported to be created in the same target document, for example, the target document can comprise a first created sub-document and a second created sub-document, the first sub-document belongs to the first document class, the second sub-document belongs to the second document class, and the first document class is different from the second document class; by adding the sub-documents of different document classes into the same target document, the integration of the sub-documents of different document classes can be realized, and the document application forms of the document application programs are enriched. On the other hand, interconnection and intercommunication among the sub-document data of different document categories are also supported, for example, a first document category is a table category, a second document category is a canvas category, by inserting an intelligent document of the canvas category into an intelligent table of the table category and associating the intelligent table with the intelligent document, visual display and application display of content data in the intelligent table can be realized through the intelligent document on the basis of taking the intelligent table as a database, a brand-new application form is provided for interconnection and intercommunication of the data of different document categories, data editing and data consumption can be realized more efficiently by helping a user to use the same target document (or the same document application program), and user viscosity is improved.

Drawings

In order to more clearly illustrate the embodiments of the application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1a is a schematic diagram of an interface for a smart form provided in accordance with an exemplary embodiment of the present application;

FIG. 1b is a schematic diagram of an interface for an intelligent document according to one exemplary embodiment of the present application;

FIG. 2 is a schematic diagram of the architecture of a document processing system provided in accordance with an exemplary embodiment of the present application;

FIG. 3 is a flow chart of a method of document processing provided in an exemplary embodiment of the application;

FIG. 4a is a schematic diagram of a second sub-document creating a blank in a target document provided by an exemplary embodiment of the present application;

FIG. 4b is a schematic diagram of another second sub-document creating a blank in a target document provided by an exemplary embodiment of the present application;

FIG. 4c is a schematic diagram of yet another second sub-document creating a blank in a target document provided by an exemplary embodiment of the present application;

FIG. 5a is a schematic diagram of creating a non-blank second sub-document in a target document according to an exemplary embodiment of the present application;

FIG. 5b is a schematic diagram of another creation of a non-blank second sub-document in a target document provided by an exemplary embodiment of the present application;

FIG. 5c is a schematic illustration of yet another creation of a non-blank second sub-document in a target document provided by an exemplary embodiment of the present application;

FIG. 6 is a schematic diagram of inserting a created intelligent document into a target document, provided by an exemplary embodiment of the present application;

FIG. 7a is a schematic diagram of a second component disposed in an editing interface of a second sub-document according to an exemplary embodiment of the present application;

FIG. 7b is a schematic illustration of a component panel provided in accordance with an exemplary embodiment of the present application;

FIG. 7c is a schematic diagram of a display component hint provided by an exemplary embodiment of the present application;

FIG. 7d is a schematic illustration of an insert component in an editing interface of a second sub-document provided in accordance with an exemplary embodiment of the present application;

FIG. 8 is a schematic diagram of a configuration data source for a target component provided in accordance with an exemplary embodiment of the present application;

FIG. 9 is a schematic diagram of content data to be referenced in a smart form provided in accordance with an exemplary embodiment of the present application;

FIG. 10 is a schematic diagram of configuring multiple data sources for a target component in accordance with an exemplary embodiment of the present application;

FIG. 11 is a flowchart of another document processing method provided by an exemplary embodiment of the present application;

FIG. 12a is a schematic background flow diagram of creating a second sub-document in a target document according to an exemplary embodiment of the present application;

FIG. 12b is a schematic diagram of another background flow for creating a second sub-document in a target document provided by an exemplary embodiment of the present application;

FIG. 13 is a background flow diagram of cross-class fusion provided by an exemplary embodiment of the present application;

FIG. 14a is a schematic diagram of implementing data synchronization in an editing interface of a second sub-document according to an exemplary embodiment of the present application;

FIG. 14b is a schematic diagram of a new third component based on updated content data in the first sub-document according to an exemplary embodiment of the present application;

FIG. 15 is a schematic diagram of component style configuration for a target component provided in accordance with an exemplary embodiment of the present application;

FIG. 16 is a schematic illustration of a replacement target assembly provided in accordance with an exemplary embodiment of the present application;

FIG. 17 is a schematic diagram of a data source for viewing a target component provided by an exemplary embodiment of the present application;

FIG. 18 is a background flow diagram of a data synchronization provided by an exemplary embodiment of the present application;

FIG. 19 is a schematic diagram of a document processing apparatus according to an exemplary embodiment of the present application;

fig. 20 is a schematic structural view of a terminal according to an exemplary embodiment of the present application.

Detailed Description

The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

The embodiment of the application relates to a document application program, which refers to an application program with a document editing function (such as a function of creating or editing a document), for example, the document application program is an online document tool supporting multi-person collaboration created and edited anytime and anywhere. Document applications often support creating documents of different categories; the categories to which the documents belong may include, but are not limited to: electronic forms (or simply form categories Excel Spreadsheet, xls), text (documents), presentations (PowerPoint, ppt), portable documents (pdf), and the like.

Wherein, the portable document is a file format for presenting the document in a manner independent of the application, hardware, and operating system. The pdf document class supports storing document content contained in a document (if the document content is text, font type, font size, color, and display position information of the text are supported to be stored); this makes the document content contained in the pdf format target document unchanged, facilitating network transmission or office printing, etc. A text category is a file format that supports editing of document content. doc document class supports formatting, document embedding, etc. of a target document by a target object. A presentation class is a file format that supports presentation in the form of a presentation on a projector or computer. The form class is a file format presented in a tabular form; the xls documents support storing data of form types, and also support ordering, grouping, automatic calculation, applying formulas, etc. of form data.

The embodiment of the application provides two brand new document categories based on the document application program, namely a first document category and a second document category. Wherein:

(1) The first document class is specifically a form document class (or referred to as a form class), and documents belonging to the form document class may be referred to as smart forms (or as smart multidimensional forms); a schematic diagram of an exemplary smart form editing interface may be seen in fig. 1a. Unlike the aforementioned electronic forms under the traditional electronic form category, the intelligent form belonging to the form document category is a relational database electronic form; and the data format of each column in the intelligent table is controlled through the field, each row in the intelligent table is used as a data record, and homologous data can be converted into different view types based on the data structure with regular rows and columns, so that a richer table view is provided for a user.

(2) The second document class is specifically an intelligent document class, and documents belonging to the intelligent document class may be referred to as intelligent documents (or as intelligent multidimensional documents); a schematic diagram of an exemplary intelligent document editing interface can be seen in fig. 1b. The intelligent document is a document class with light editing; the editing interface of the intelligent document is carried and provided by the canvas, so that the second document class can also be called as the canvas class; and supporting the high-level drag component on the canvas, and making the application program document with high fusion degree and no class difference. Wherein the canvas mentioned above is a carrier for rendering components and supporting the composition editing of the components into a scenerising solution. The above mentioned components (components), or edit components, controls, parts, etc., components are simple packages of data and methods; the data and methods are built into blocks by componentizing (i.e., encapsulating) editing capabilities already owned by a document application (e.g., an online document tool) or developed entirely new, such that invocation of encapsulated data and methods is accomplished by invoking components.

The embodiment of the application provides a document processing scheme based on the brand new first document class and the second document class. The document processing scheme supports creation of sub-documents of different document categories in the same target document, particularly supports insertion of a second sub-document belonging to a second document category when the target document contains a first sub-document belonging to a first document category, can integrate documents of different document categories, enriches document application forms of document application programs, and improves overall ecology of the document application programs. Furthermore, the document processing scheme also supports class fusion of different document classes; the category fusion can be used for carrying out data interconnection and intercommunication on sub-documents of different document categories, and particularly, the editing components in the intelligent documents and the content data in the intelligent tables are associated, so that data linkage across categories is realized. For example, in the case where the intelligent form and the intelligent document implement class fusion, an editing component that supports the introduction of form data in the intelligent form into the intelligent document; similar to the database taking the intelligent table as an editing component in the intelligent document, ensuring that table data in the intelligent table, which is referenced to the intelligent document, can be synchronously updated in the intelligent document and the intelligent table, and if the table data in the intelligent table changes, displaying the updated table data in the intelligent document in real time; the method not only realizes the data linkage of the cross-class through an editing component (such as a chart component or a chart block), but also more intuitively passes the table data in the intelligent table through the editing component in the intelligent document, realizes the visualization and the application presentation or display, and improves the readability and the intelligibility of the table data in the intelligent table.

In summary, the embodiment of the application provides a scheme for building an application document (the application document may refer to a document after cross-class fusion in a target document) through cross-class fusion. On the other hand, the linkage between the sub-document data of different document categories is supported, for example, the linkage between the editing component in the intelligent document and the table data in the intelligent table can realize the more visual and applied presentation of the table data in the intelligent table through the editing component in the intelligent document, and the category fusion mode accords with the document editing habit of a user and has low use threshold; and the cross-class fusion provides a brand-new application form for the interconnection of two document classes, solves the problem of separation of the current data editing scene and the data consumption scene, ensures that the target object can use the same document application program and even the same document from the data editing scene and the data consumption scene, and realizes the efficient collaboration of the documents under different document classes. In another aspect, the foregoing description indicates that the editing interface of the intelligent document is carried and provided by the canvas, so that the user can customize the layout editing component to become a scene solution according to the creation requirement in the canvas, and a creative tool is created for the user; therefore, after users encounter data consumption problems in different data editing scenes, on the basis of taking the intelligent table as a database, the intelligent table can help the target object to solve the information processing problems encountered in the scenes by the music height editing of the components and the adjustment of the overall layout in the intelligent document, and the user experience of the target object in the data consumption scenes is improved.

To facilitate a better understanding of the document processing scheme proposed by the embodiment of the present application, an exemplary document processing scenario is presented in connection with fig. 2. Referring now to FIG. 2, FIG. 2 illustrates a schematic architecture of a document processing system according to one exemplary embodiment of the present application; as shown in fig. 2, the document processing system includes a terminal 201 and a server 202, and the number, kind and naming of the terminal 201 and the server 202 are not limited in the embodiment of the present application. Wherein:

1) Terminal 201 may refer to: a terminal device for use with a target object (i.e., any user) that performs category fusion requirements in a document application. The terminal device may include, but is not limited to: smart phones (such as Android mobile phones, iOS mobile phones, etc.), tablet computers, portable personal computers, mobile internet devices (MID for short), smart televisions, vehicle-mounted devices, head-mounted devices, etc. smart devices capable of performing touch screens, and the embodiment of the application does not limit the types of terminal devices; the terminal device includes a display screen, which may be a physical screen, a touch screen, etc., which may be referred to as a terminal screen, a display screen, etc.

The terminal 201 runs a document application program having the above-mentioned category fusion function. Where a document application refers to an application that may refer to a computer program that performs some particular task or tasks. Classifying the document application programs according to different dimensions (such as the running mode, the function and the like of the application programs), and obtaining the types of the same document application program under different dimensions, wherein: (1) classified by how the document application operates, the document application may include, but is not limited to: a client installed in a terminal, an applet that can be used without downloading an installation, a web application opened through a browser, and the like. (2) Applications may include, but are not limited to, by functional type of application: IM (instant messaging) applications, content interaction applications, and the like. Wherein, the instant messaging application program refers to an application program of instant messaging and social interaction based on internet, and the instant messaging application program can include but is not limited to: social applications including communication functionality, map applications including social interaction functionality, gaming applications, and the like. The content interaction application is an application capable of realizing content interaction, and may be, for example, an application such as internet banking, a sharing platform, personal space, news, and the like.

The document application program according to the embodiment of the present application is not limited to the above-described type of application program, and is specifically described herein.

2) Server 202 may be a background server of terminal 201 for interacting with terminal 201 to provide computing and application service support for terminal 301. In detail, the server 202 is a background server of the document application running in the terminal 201, so that the background server is used to provide computing and application service support for the document application running in the terminal 201. In more detail, the server 202 may include different servers corresponding to different document categories in the document application program, such as a background server corresponding to a smart form included in the server 202, the background server being configured to provide computing and application service support for the smart form, and a background server corresponding to an intelligent document included in the server 202, the background server being configured to provide computing and application server support for the intelligent document. The server 202 may be a stand-alone physical server, or may be a server cluster or a distributed system formed by a plurality of physical servers; in a cloud game scenario, server 202 may also be a cloud server. The terminal 201 and the server 202 may be directly or indirectly connected in a communication manner through a wired or wireless manner, and the connection manner between the target terminal and the server is not limited in the embodiment of the present application.

The document processing scheme provided by the embodiment of the application can be jointly executed by the terminal 201 and the server 202 in the document processing system; or, the document application program running in the terminal 201 and the server 202 are executed together; the embodiment of the application is not limited to the specific mode for executing the document processing scheme provided by the embodiment of the application.

The following is a brief description of a technical process related to the document processing scheme for creating a second sub-document in a target document and fusing a first sub-document and a second sub-document, taking the document processing scheme provided by the terminal 201 and the server 202 together as an example in connection with fig. 2, where:

the technical process of creating the second sub-document in the target document may include: first, after the target object opens and displays the target document using the document application program running in the terminal 201, an editing interface of the first sub-document in the target document, such as a form editing interface for displaying a smart form included in the target document, may be displayed. Then, if the target object has a need to insert an intelligent document in the target document, then the support target object performs a sub-document creation operation (e.g., a creation operation indicating creation of a second sub-document belonging to a second document class) in the target document, at which point the terminal 201 may generate a sub-document creation request according to the sub-document creation operation, which may be used to request creation of the second sub-document belonging to the second document class in the target document. The terminal sends the sub-document creation request to the server 202. Second, the server 202 generates a software development kit based on the document data stream of the second sub-document in response to the received sub-document creation request; then, integrating the software development kit corresponding to the second sub-document into the target document, specifically into the data package of the target document, so that the second sub-document can be created in the target document integrated with the software development kit. Finally, after receiving the data packet of the first sub-document of the software development kit integrated with the second sub-document returned by the server 202, the terminal 201 may render and display the editing interface of the second sub-document in the terminal screen according to the data packet.

Further, the technical process of fusing the first sub-document and the second sub-document may include: if the target object has the requirement of category fusion of the first sub-document and the second sub-document, the target object may also perform data source configuration on the editing component in the editing interface of the second sub-document, where the data source configuration may refer to configuring a database for the editing component. When the database configured for the editing component is the first sub-document, the terminal 201 may send a data storage request to the server 202, where the server 202 may store the document identification (e.g., a flag for uniquely identifying the first sub-document, such as a document number, a document name, or a document ID, etc.) of the first sub-document into the document data stream (e.g., a data stream composed of a large amount of data included in the editing interface of the second sub-document) of the second sub-document according to the data storage request, so that the second sub-document can call the content data (e.g., table data) in the first sub-document based on the document identification of the first sub-document. The server 202 returns the associated content data in the first sub-document to the terminal 201 in order to display the content data in the first sub-document in the editing component in the second sub-document to enable a data visual presentation of the content data.

Through the implementation process, the sub-documents of different document classes can be created in the same target document in a mode of integrating the target document by packing the document data of the intelligent document into a software development kit, so that the document application forms supported by the document application program are enriched; and the document identification of the first sub-document can be stored in the document data stream of the second sub-document, so that the data interconnection and intercommunication among the sub-documents of different document classes can be realized.

It should be noted that, when the embodiment of the present application is applied to a specific product or technology, for example, when the target object opens the target document, permission or consent of the creator who creates the target document needs to be obtained; and the collection, use and processing of the relevant data is required to comply with relevant laws and regulations of the relevant country and region, such as the specific content of the document content contained in the target document is required to comply with relevant laws and regulations of the relevant country and region.

Based on the above-described document processing scheme, the embodiment of the present application proposes a more detailed document processing method, and the document processing method proposed by the embodiment of the present application will be described in detail below with reference to the accompanying drawings.

FIG. 3 illustrates a flow diagram of a document processing method provided by an exemplary embodiment of the present application; the document processing method may be performed by the terminal 201 in the system shown in fig. 2, and may include, but is not limited to, steps S301 to S302:

s301: and displaying an editing interface of the second sub-document in the target document.

As described above, the target document may include sub-documents of different document classes, such as a first sub-document and a second sub-document included in the target document; the first sub-document belongs to a first document class, for example, the first document class is a form class, and the second sub-document belongs to a second document class, for example, the second document class is a canvas class. In practical applications, the number of sub-documents belonging to the same document class in the target document may be more than one, and the first sub-document as mentioned above may be any one of at least one sub-document belonging to the first document class in the target document; similarly, the second sub-document may be any one of at least one sub-document belonging to the second document category in the target document. For ease of explanation, embodiments of the present application will be described with reference to a first sub-document belonging to a first document category and a second sub-document belonging to a second document category.

In the case that the target document already contains a second sub-document belonging to the second document category, if the target object has a need to view the second sub-document in the target document, the target object may open the target document by a document application deployed in the terminal to trigger an editing interface displaying the second sub-document in the target document. In the specific implementation, when a target document is opened through a document application program deployed in a terminal, a service interface of the target document is output in a terminal screen of the terminal; the service interface of the target document herein may refer to: a document interface of the target document (e.g., a document-level interface, rather than a sub-document interface in the target document), or an editing interface (otherwise known as a sub-document interface) of any sub-document in the target document. The manner in which the editing interface of the second sub-document in the target document is displayed varies depending on the service interface of the target document. Alternatively, if the interface displayed by default or last time the target document was closed is: and if the target object opens the target document, the service interface of the displayed target document is the editing interface of the second sub-document. Alternatively, if the interface displayed by default or last time the target document was closed is: if the target object opens the target document, the service interface of the displayed target document is the other interface, and then the document identification (which can be used for uniquely identifying the second sub-document, such as the document name, the document ID, the document number or the document storage path, etc.) of the second sub-document needs to be triggered in the target document, and then the sub-document interface displayed to the second sub-document is switched from the other interface.

In the case that the target document does not contain the second sub-document, the second sub-document needs to be created in the target document first, and the editing interface for displaying the second sub-document in the target document can be triggered after the second sub-document is created. The specific implementation process of creating the second sub-document in the target document and displaying the editing interface of the second sub-document may include: and if the terminal receives the sub-document creation operation executed by the target object aiming at the target document, displaying an editing interface of the created second sub-document in a terminal screen. Wherein the sub-document creation operation for the target document may include at least one of:

(1) for the referencing operation of the content data in the first sub-document in the target document, if the first sub-document is a smart table, the content data contained in the smart table may include all or part of the table data in the smart table. (2) Trigger operation of a control (or component, option, button, etc.) is created for the sub-document. (3) A gesture operation in the target document or in the editing interface of the first sub-document, the gesture operation having a function of triggering creation of the second sub-document; the gesture operation may include: a double click operation, a long press operation, or a three-finger operation, or a movement operation of a preset trajectory (e.g., an "S" shaped trajectory or an "L" shaped trajectory, etc.) is performed, etc. (4) The voice input operation in the target document or the editing interface of the first sub-document may specifically be that the microphone of the terminal obtains the audio in the physical environment where the target object is located, and analyzes the obtained audio by using a voice signal, and if the voice signal indicates that the second sub-document needs to be created in the target document, the operation of creating the second sub-document is automatically performed. Or, (5) a shortcut key input operation, in particular by entering a shortcut key (e.g. a single key or a combination of keys) in the virtual input device or the physical input device, to trigger the creation of a second sub-document in the target document.

It should be noted that, the above is only an exemplary sub-document creation operation given in the embodiment of the present application, and the specific implementation process of the sub-document creation operation may vary in the actual sub-document creation process.

It should be noted that, according to the difference of the sub-document creation operation, the second sub-document created in the target document is not the same. Taking several sub-document creation operations as examples given above, if the sub-document creation operation performed for the target sub-document includes any one of the following: aiming at the triggering operation of the sub-document creation control, the gesture operation in the target document or the editing interface of the first sub-document, the voice input operation in the target document or the editing interface of the first sub-document, or the shortcut key input operation, the second sub-document created in the target document is a blank intelligent document, namely the editing interface of the second sub-document is a blank interface. If the sub-document creation operation performed on the target document includes: and (3) carrying out reference operation on the content data in the first sub-document, wherein the second sub-document created in the target document is a non-blank document, and the content data referenced in the editing interface of the first sub-document is automatically filled in the editing interface of the second sub-document by default. The specific creation modes of the two second sub-documents given above are described in detail below with reference to the accompanying drawings, wherein:

(1) A blank second sub-document is created in the target document.

In a specific implementation, if the target object has a requirement of creating a blank second sub-document in the target document, the target object may execute a sub-document creation operation for the target document; the terminal responds to the sub-document creation operation executed by the target object for the target document, and can create and display an editing interface of the second sub-document, wherein the editing interface of the second sub-document is a blank interface. As described above, the sub-document creation operation for creating the blank second sub-document may include various kinds such as a trigger operation for a sub-document creation control, a gesture operation, a voice input operation, or a shortcut key input operation, and the like.

A schematic flow chart of performing an exemplary sub-document creation operation in a terminal screen to create a blank second sub-document is given below with reference to the accompanying drawings, wherein:

an exemplary sub-document creation operation is a trigger operation for a sub-document creation control, and a schematic diagram of creating a second sub-document in a target document can be seen in fig. 4a and 4b. A service interface of the target document is displayed in a terminal screen of the terminal, and at this time, the service interface is an editing interface 401 of a first sub-document in the target document, and the editing interface 401 includes a toolbar 402. Alternatively, the sub-document creation control 403 for triggering creation of the second sub-document may be displayed directly in the target document, such as in the toolbar 402 of the target document (an area containing multiple tools for document editing (e.g., editing of font settings or formatting) of the target document), as shown in FIG. 4 a; thus, the target object can be conveniently and directly arranged on the service interface of the target document, and the editing interface 406 of the second sub-document can be quickly created and displayed by triggering the sub-document creation control 403 in the toolbar 402, so that the sub-document creation speed and efficiency can be improved to a certain extent. Optionally, the child document creation control 403 may also be displayed in the options window 404, as shown in FIG. 4 b; the options window 404 is hidden and only when the options window 404 needs to be used, the options window 404 and thus the child document creation control 403 are presented; the manner of triggering the display of the options window 404 may include, but is not limited to: the gesture operation (such as a long press operation shown in fig. 4b, for example, the action position of the long press operation is the bottom area of the editing interface) or the trigger operation for the new option 405 is not limited thereto.

An exemplary sub-document creation operation is a gesture operation, and when the gesture operation is an operation in which a movement track is "S" shape, a schematic diagram of creating a second sub-document in a target document may be referred to in fig. 4c. A service interface of the target document is displayed in the terminal screen of the terminal, and at this time, the service interface is an editing interface 401 of the first sub-document in the target document. If there is an operation that the movement track is in an S shape in the editing interface 401 of the first sub-document, which indicates that the target object wants to create a new blank second sub-document in the target document, the editing interface 406 of the second sub-document is automatically created and displayed, or the option window 404 is triggered to be displayed so as to create the blank second sub-document through the option window 404. The method for automatically creating the second sub-document through gesture operation or rapidly calling the option window can improve the creation speed and efficiency of the second sub-document and the intelligence of the document application program.

It should be noted that the foregoing is merely illustrative of several examples of the embodiments of the present application, and the specific implementation process of creating the blank second sub-document through the sub-document creation operation is not limited to the embodiments of the present application.

(2) A non-blank second sub-document is created in the target document based on the content data of the first sub-document.

In a specific implementation, if the target object has a requirement of taking the first sub-document in the target document as a database and creating the second sub-document, the target object may execute a sub-document creation operation in an editing interface of the first sub-document, specifically may execute a reference operation on content data to be referenced in the first sub-document, so that the terminal automatically creates the second sub-document in response to the reference operation, and visually displays the referenced content data in the editing interface of the second sub-document.

A flow diagram of performing a referencing operation on content data to be referenced in a first sub-document to create a non-blank second sub-document and visually displaying the referenced content data in an editing interface of the second sub-document is given below in conjunction with the accompanying drawings, wherein:

in one implementation manner, the embodiment of the application supports that content data to be referred is selected in an editing interface of a first sub-document; then, a new option is selected from the output option window, so that the second sub-document can be automatically created based on the content data selected in the first sub-document, and the content data referenced by the visual display is defaulted in the editing interface of the second sub-document. As shown in fig. 5a, assuming that the first document class is a table class, the first sub-document is a smart table, content data to be referenced contained in an editing interface of the first sub-document is table data, and the second document class is a canvas class, the second sub-document is an intelligent document, and the editing interface of the second sub-document is carried by the canvas. When the target object selects the column 5011 of the date and the column 5012 of the number in the editing interface 501 of the smart table, the option window 502 is output (or after the column 5011 of the date and the column 5012 of the number are selected, a right button is input (such as a mouse) to trigger to display the option window), and the option window 502 includes the new option 5021. In response to the triggering operation for the new option 5021, which indicates that the target object has a need to create an intelligent document based on the two data, the editing interface 503 of the second sub-document is created and displayed. The editing interface 503 of the second sub-document is automatically populated with the referenced form data (i.e., the date column 5011 and the number column 5012). In more detail, the editing interface of the second sub-document automatically populates the referenced content data in the manner of: the first component is automatically populated with the referenced form data in the first sub-document, that is, the referenced form data is visually presented in component form.

The first component displayed in the editing interface of the second sub-document is a default component, if the first component is determined according to the document class of the first sub-document, if the document class of the first sub-document is a table document class, the component type of the first component created in the second sub-document by default is a chart type. Further, the first component belonging to the chart type includes any one of the following: list components, fan-shaped components, circle components, polyline components, bar graph components, etc., any edit component belonging to the icon type may be inserted by default or randomly in the edit interface of the second sub-document, as in the schematic diagram shown in fig. 5a, the first component 504 is a bar graph component. Of course, the first component may also be a component of which the target object is custom selected from the component panel. As shown in fig. 5b, after the target object triggers the new option 5021 in the option window 502, the output component panel 504 is further supported, where the component panel 504 includes type identifiers of multiple component types (may further include one or more components under different component types, so as to directly and custom select a component from the component panel 504 to insert into the editing interface of the second sub-document), such as a type identifier 5041 of a chart type; in response to a triggering operation for this type identification 5041, indicating that the target object wants to visually present the referenced form data in the first sub-document in a chart style, the referenced form data is visually presented in the editing interface 503 of the second sub-document in the form of a chart component (e.g., a default bar chart component, or a component selected by the target object in a component panel).

In other embodiments, the first component belonging to the chart type may further include any one of the following: catalog component, scatter component, map component, curve component, funnel component and combination component.

With continued reference to FIG. 5b, the components under each component type in the component panel 504 may be displayed in a categorized fashion, as the corresponding components under the base block component type may include: text component and title component, etc., components under chart component types may include: the column diagram component, the sector diagram component and the like are beneficial to the target object to search the required components according to the component type classification, and help the target object to quickly position the components. In addition, a shortcut creation manner corresponding to each component is also displayed in the component panel 504, for example, when the shortcut key corresponding to the bar graph component is "/a", which indicates that the target object inputs "/a" through the virtual input setting or the physical input device (such as a solid keyboard), the bar graph component corresponding to the shortcut key "/a" can be quickly inserted into the editing interface of the second sub-document, so as to improve the component insertion efficiency. Further, considering that the display area of the component panel 504 is limited, and the types of components provided by the second sub-document and components belonging to different component types are numerous, this makes it impossible for the component types and components to be displayed in the component panel 504 all at once; thus, embodiments of the present application support sliding display of component types and components in component panel 504 to enable the appearance of hidden component types and components following the sliding operation, thereby providing rich components for the target object. The sliding operation herein may include, but is not limited to: the operation of moving the slide shaft 5041 or the operation of pressing and moving any position of the assembly panel 504 is not limited thereto.

In other implementations, the embodiments of the present application support starting a sub-document creation function of inserting a second sub-document into a target document, and then selecting content data to be referenced from an editing interface of a first sub-document, so as to automatically create the second sub-document based on the selected content data to be referenced. In the specific implementation, a second sub-document creation function of the target document is supported to be started firstly, specifically, a document creation control is triggered to enable a first sub-document in the target document to be in a content citation state; the document creation control may be displayed in a toolbar of the first sub-document or in an options window as shown in fig. 5c, where the triggering display manner of the options window may include, but is not limited to: a gesture operation, a trigger operation of creating a control for a sub-document (as shown in fig. 4a described above), a voice input operation, or the like. And, after the document creation control is triggered, the output state prompt information 505 is also supported (such as continuously displayed in the terminal screen for a period of time, or continuously displayed until the second sub-document is successfully created), so that the target object timely senses that the first sub-document is in a state of supporting the selection of the content data to be referenced. Then, the target object may perform a selection operation of the content data in the first sub-document, and an editing interface of the second sub-document may be automatically created and displayed in response to the selection operation. At this point, the referenced content data is visually presented in the editing interface of the second sub-document. It will be appreciated that the manner in which the referenced content data is visually displayed in the editing interface of the second sub-document is similar to that described in connection with fig. 5a and 5b, and is not described in detail herein.

In summary, the embodiment of the application supports the target object to self-define and create the blank or non-blank second sub-document according to the requirement, meets the personalized creation requirement of the target object on the second sub-document, not only enriches the functions of the document application program, but also improves the intelligent document creation experience of the target object.

Notably, in addition to supporting creation of a blank in the target document or a second sub-document based on the first sub-document, embodiments of the present application also support insertion of the created intelligent document in the target document as a second sub-document. In other words, if there is a created intelligent document (created by the target object, or received by the target object created by another object) and the target object wants to introduce the created intelligent document in the target document, the insertion of the created intelligent document in the target document is supported, i.e. the created intelligent document is regarded as the second sub-document in the target document. Thus, if the target object wants to utilize the content data of the created intelligent document in the target document, the target object can directly insert the created intelligent document into the target document as the second sub-document without creating a blank intelligent document first and then executing subsequent operations such as data association, component addition and the like, so that the construction efficiency of the second sub-document is greatly improved, and the functions of the document application program are enriched.

An exemplary schematic of inserting a created intelligent document into a target document can be seen in FIG. 6; as shown in FIG. 6, in response to a selected operation for a sub-document insertion option 601 (e.g., located in an options window or directly displayed in a service interface of a target document), a document options window 602 may be output; and selecting the created intelligent document in the document option window 602; in this way, the intelligent document can be inserted into the target document to realize the intelligent document as a second sub-document of the target document.

S302: in the editing interface of the second sub-document, the content data in the first sub-document is displayed in canvas form.

After inserting the second sub-document belonging to the second document class into the target document based on the aforementioned step S301, the embodiment of the present application further supports class fusion of the first sub-document belonging to the first document class in the target document and the second sub-document belonging to the second document class; class fusion may refer to: and associating the content data in the first sub-document with the second sub-document. Thus, in one aspect, the second sub-document can display content data in the first sub-document in canvas form in an editing interface of the second sub-document with the first sub-document as a database; on the other hand, ensuring that the content data is kept updated synchronously in the first sub-document and the second sub-document; the readability of the content data in the first sub-document is improved, and the target object is convenient to consume the content data in the first sub-document.

As described above, the canvas is a carrier supporting the combined editing of components into a scenerized solution, and thus a process of displaying content data in the form of canvas in the editing interface of the second sub-document, specifically, a process of displaying content data through a target component in the editing interface of the second sub-document. The target component herein may refer to any component displayed in the editing interface of the second sub-document; for example, in the case where the second sub-document is constructed by using the first sub-document as a database, the target component may refer to the first component; for another example, if after the second sub-document is created in the target document, the target object inserts a new second component in the editing interface of the second sub-document, then the target component may be referred to as a second component; the specific source of the target component in the second sub-document for association with the content data in the first sub-document is not limited in this embodiment of the present application and is described herein.

As can be seen from the above description, after inserting the second sub-document into the target object, the document processing method provided by the embodiment of the present application further relates to: inserting a second component in the editing interface of the second sub-document, and associating the target component in the second sub-document with the content data in the first sub-document. The following describes the specific implementation process of the two parts of content, wherein:

1. Inserting a second component in the editing interface of the second sub-document.

Specifically, if the target object has a need to perform page editing on the second sub-document (e.g., inserting a component in an editing interface of the second sub-document) after inserting the second sub-document in the target document, the target object may perform a component creation operation for the second sub-document, at which time the terminal may display a component panel including a type identifier of at least one component type in response to the component creation operation. If the target object executes the identification selection operation in the component panel, a second component under the target component type corresponding to the selected target type identification can be displayed in the second sub-document according to the identification selection operation. That is, when the target object has a need to insert a component in the editing interface of the second sub-document, the component panel of the second sub-document may be evoked and the desired target component may be selected for the second sub-document through the component panel.

Wherein the above-mentioned component creation operations for the second sub-document may include, but are not limited to: input operation of inputting a shortcut key through a virtual input device or a physical input device (e.g., when inputting a shortcut key "/" in a physical keyboard, a component panel of a second sub-document may be quickly evoked, or a certain component in the component panel may be directly evoked and inserted (e.g., a bar graph component is directly inserted when inputting a shortcut key "/a" as shown in fig. 5 b) previously); a triggering operation to create an option for a component, or a gesture operation in an editing interface of a second sub-document, etc.

A specific implementation of configuring the second sub-document with the second component from the component panel when the component creation operation includes a trigger operation for the component creation option is given below in connection with fig. 7 a. First, a component creation option 701 is displayed in the editing interface of the second sub-document, and the specific display position of the component creation option 701 in the editing interface of the second sub-document is not limited in the embodiment of the present application, for example, the component creation option 701 is displayed at each line of input positions in the editing interface of the second sub-document, or the component creation option 701 is displayed at the bottom area of the editing interface of the second sub-document, or the like. Second, when the component creation option 701 is triggered, indicating that the target object has a need to call up the component panel of the second sub-document, the component panel 702 of the second sub-document is output. The component panel 702 includes a category identifier (e.g., an identifier in the form of an icon or text, etc.) for at least one component type. The component types herein may include, but are not limited to: chart type, text type, drawing type, etc.; each component type, in turn, contains one or more components, and the various components contained in the chart types as mentioned above may include: sector assemblies, circle assemblies, column assemblies, and the like; the various components contained by the text types may include: text component, title component or list component, etc.; the components contained in the diagram types may include animation components of different content.

Finally, the target object may perform an identifier selection operation in the component panel 702, where a component under a target component type corresponding to the selected target type identifier may be inserted as a second component into the editing interface of the second sub-document according to the identifier selection operation; alternatively, the second component is represented by an integrally selectable region. Wherein, according to the difference of the display positions of the component creation options 701, the insertion positions of the selected second components are also different; for example: the component creation option 701 is displayed at an input position, and after a second component to be inserted is selected, the second component is inserted into the input position; and the following steps: when the component creation option 701 is displayed in the bottom area of the editing interface of the second sub-document, after the second component to be inserted is selected, the second component is inserted into a specific position (specified by the target object user definition or set by the developer) in the editing interface.

Based on the above description of the embodiment shown in fig. 7a, the following points are also described:

1) The content contained in the component panel is not limited to the type identifier of the component type shown in fig. 7 a; as previously described with respect to fig. 7a, if only a category identification of at least one component type (e.g., basic block component type and chart component type, etc., as shown in fig. 7 a) may be included in the component panel; in this implementation manner, if the target object performs an identifier selection operation (such as a trigger operation) for a target type identifier (such as a type identifier of any component type), one or any component of the target component type corresponding to the target type identifier is inserted as a second component into the editing interface of the second sub-document by default.

Optionally, only the component identifications of each component of at least one component type (e.g., the component identifications of the bar graph component and the fan graph component of the chart component type (e.g., the component style thumbnail)) may be included in the component panel; in the implementation manner, if the target object performs an identification selection operation on a target component identification (such as a component identification of any component), a component corresponding to the triggered target component identification is used as a second component and is inserted into an editing interface of a second sub-document; the target object may thus select the second component to be inserted directly from the component panel. Optionally, the type identifier of at least one component type and the component identifier of each component under each component type may also be contained in the component panel, as shown in fig. 7 b; therefore, the target object can select the second component according to self-requirement in a self-defined manner, the component selection modes are enriched, and the component configuration experience of the target object is improved to a certain extent.

In addition, the display style of the component panel 703 evoked by the execution of the component creation operation for the second sub-document is similar to the display style of the component panel 504 evoked before the creation of the second sub-document mentioned in the foregoing fig. 5 a; the component panel 703 also includes a sliding shaft to slide and display the hidden component type or component, which is not described herein.

2) The component panel evoked for the second sub-document is displayed as shown in FIG. 7a in the following manner: displaying the first sub-document on an editing interface of the second sub-document in a floating layer window mode; however, in practical applications, the component panel may also be displayed in other display manners, which are not limited in the embodiments of the present application. For example, the component panel is directly displayed in a target area in the editing interface of the second sub-document, which may refer to any area in the editing interface of the second sub-document (e.g., the right area or the bottom area of the interface). For another example, the component panels may also be displayed in a separate interface format. The display mode of the component panel is not limited in the embodiment of the application.

3) In the editing interface of the second sub-document, component prompt 703 (as shown in fig. 7 c) may also be displayed, where the component prompt 703 is used to remind the component of the function of creating the option 701; this may help the target object to learn the functionality of the component creation option 701 in time, thereby enabling insertion of the second component in the editing interface of the second sub-document. The component prompt 703 may be displayed in a region adjacent to the component creation option 701, so that the target object perceives the association between the component prompt 703 and the component creation option 701. In addition, the component prompt 703 may be continuously displayed in the editing interface of the second sub-document, for example, continuously displayed in the editing interface from the triggering display of the editing interface of the second sub-document; alternatively, the component prompt 703 may be displayed in the editing interface only when a viewing operation for the component creation option 701 is detected, and the component prompt 703 may be hidden when the viewing operation is canceled; among other things, the view operation for component creation option 701 may include: the dwell time of the cursor (e.g., the mapped position of the external mouse in the terminal screen) on the component creation option 701 exceeds a duration threshold (e.g., 0.5 seconds), etc.; the embodiment of the application does not limit the specific operation process of the checking operation.

4) As depicted in fig. 7a, the identification selection operation in component panel 702 is: triggering operation aiming at target type identification; in practical applications, however, the implementation of the identifier selection operation is not limited to the triggering operation shown in fig. 7 a. For example, the identification selection operation may further include: a drag operation of moving the object type identifier in the component panel from the component panel to the editing interface of the second sub-document; as shown in fig. 7d, if the target object wants to insert a bar graph component as a second component in the editing interface of the second sub-document, the target object may press the bar graph component long, at which time the bar graph component is activated, then continuously press the bar graph component and drag the bar graph component from the component panel to the editing interface of the second sub-document; further, when the pressing against the bar graph component is released in the editing interface of the second sub-document, the bar graph component is inserted at the release position.

In summary, the inserting of the second component into the editing interface of the second sub-document may be achieved through the above-mentioned related description; the second sub-document may be a blank document created, or may be a non-blank document created when the first sub-document is used as a database. That is, regardless of the manner in which the second sub-document is created in the foregoing description, embodiments of the present application support the insertion of a second component in the second sub-document, as described herein.

2. And associating the target component in the second sub-document with the content data in the first sub-document to realize data linkage between the first sub-document and the second sub-document.

In a specific implementation, the editing interface of the second sub-document includes a target component, where the target component may be the first component or the second component mentioned above, and this is not limited. When a target component is triggered, indicating that the target object has a need for data source association with the target component, then a component configuration menu associated with the target component may be displayed, the component configuration menu containing data source configuration options. Then, when a data source configuration option in the component configuration menu is triggered, the data source identification of one or more candidate data sources (a flag that may be used to uniquely identify the data source, such as in the form of an icon or text, etc.) may be displayed. Wherein the candidate data sources may include at least one of: a first sub-document in the target document, independent of the reference document of the target document, or independent of a sub-document in the reference document of the target document; that is, the embodiment of the application supports the second sub-document to reference the sub-document in the target document as an internal data source, and also supports the second sub-document to reference the external intelligent document independent of the target document as an external data source, so that the target object can freely select the data to be referenced according to the data reference requirement of the target object, and the selection path of the data source is enriched.

Further, the target object may perform data source selection on one or more candidate data sources to be output, where the terminal determines that the target object wants to refer to the content data of the first sub-document as a database in response to a triggering operation of the target object for a data source identifier (may be a document identifier) of the first sub-document, and triggers and executes a step of displaying the content data in the first sub-document in a canvas form in an editing interface of the second sub-document, specifically displaying the content data in the first sub-document in a target component in an editing interface of the second sub-document; in this way, the content data of the first sub-document can be displayed in the form of the target component in the editing interface of the second sub-document, so that the visual display of the content data of the first sub-document is realized.

An exemplary schematic diagram of data source association for implementing a target component through a component configuration menu can be seen in FIG. 8; as shown in fig. 8, when a target component (e.g., the target component is a bar graph component) in the editing interface of the second sub-document is triggered, the triggering operation for the target component herein may include: a long-press operation, a click operation, a trigger operation for a "deselect" option in the area where the target component is located, or an operation that a cursor falls onto the target component, etc., which indicate that the target object has a requirement for configuring the target component, the component configuration menu 803 may be directly output in the editing interface of the second sub-document; alternatively, the configuration window 801 is output first, where the configuration window 801 includes an association option 802, and the component configuration window 803 may be triggered to be displayed in the editing interface of the second sub-document by triggering the association option 802. The component configuration menu 803 may be displayed as an area in the editing interface of the second sub-document, which is not limited to this, and of course, the component configuration menu may also support displaying in a floating layer window form or a separate interface form.

Further, a data source configuration option 804 is included in the component configuration menu 803; then in response to a triggering operation for this data source configuration option 804, the data source identification of one or more candidate data sources may be displayed, see the relevant description above regarding the source of the candidate data source. The target object may select one or more candidate data sources to be output, and when the target object selects the first sub-document from the one or more candidate data sources, it is determined that the content data of the first sub-document is used as a data source of the target component, and at this time, the target component in the editing interface of the second sub-document is updated, specifically, the target component is filled with the content data of the first sub-document, so that the filled target component can reflect the data rule of the content data of the first sub-document.

In summary, the embodiment of the application supports the realization of data association between the first sub-document and the second sub-document through the target component in the editing interface of the second sub-document, thereby achieving inter-class data interconnection, enriching the data consumption scene, helping the target object obtain good experience in the data consumption scene, and solving the information processing problem encountered in the data consumption scene.

It should be noted that, the content data included in the first sub-document is often more, and in the actual data consumption scenario, the target object may only want to reference part of the content data in the content data included in the first sub-document; if the first sub-document is a smart table, the smart table contains 7 rows and 6 columns of table data as shown in fig. 9, but the target object only wants to refer to the table data of the column where the date is located and the column where the number is located. Based on the above, the embodiment of the application also supports the selection of the content data to be referenced from the content data contained in the first sub-document; specifically, after the data source identifier of the first sub-document is selected in the component configuration menu, supporting to jump from the editing interface of the second sub-document to the editing interface of the first sub-document, and performing content data selection operation on the editing interface of the first sub-document by the target object; when the operation of finishing the selection of the content data is detected, returning to the editing interface of the second sub-document from the editing interface of the first sub-document, and filling a target component with the content data to be referenced in the editing interface of the second sub-document, so as to realize the visual display of the content data referenced in the first sub-document through the target component. Of course, the implementation procedure of selecting the content data to be referred to from the first sub-document is not limited to the above-mentioned implementation procedure; for example, after the data source identifier of the first sub-document is selected in the component configuration menu, the thumbnail of the editing interface of the first sub-document can be directly output in the component configuration menu, so that the target object can directly select content data from the thumbnail without interface skip, and the data selection efficiency can be improved to a certain extent.

It should also be noted that the embodiment of the present application also supports the simultaneous referencing of the target component to at least two data sources; that is, the target component can enable visual presentation of content data in at least two data sources; by adopting the same component to visually present the content data of different data sources, the target object can be helped to perceive the difference or the connection between the content data of different data sources based on the same component, the target object can be helped to better analyze the content data, and the object experience can be improved. As shown in fig. 10, in the process that the target object configures the data sources of the target component through the component configuration menu, a plurality of data sources may be simultaneously selected, and if the first sub-document 1 and the first sub-document 2 in the target document are selected as the data sources, a bar graph of the content data of the first sub-document 1 and a bar graph of the content data of the second sub-document 2 may be simultaneously displayed in the target component; thus, the target object is assisted in data analysis by comparing the bar graphs of different sub-documents in the target component.

It should be noted that, according to the different types of the components of the target component, the content of the target component is different, and further, the setting mode of the content of the target component is also different. Taking the target component as a column diagram component for example, the target component often further comprises an abscissa, an ordinate and a column diagram name; optionally, embodiments of the present application support automatically generating the abscissa, ordinate and histogram name of the target component from the content data referenced in the first sub-document. Optionally, the embodiment of the application further supports the custom setting of the abscissa, the ordinate and the cylindrical chart name of the target component in the editing interface of the second sub-document by the target object; specifically, the custom setting of the abscissa, the ordinate and the column diagram name can be realized through the component configuration menu associated with the target component, or the target component is directly edited in the editing interface of the second sub-document, so that the custom setting of the abscissa, the ordinate and the column diagram name can be realized.

In summary, the embodiment of the application supports creation of the sub-documents of different document classes in the same target document, and can integrate the sub-documents of different document classes and enrich the document application form of the document application program by adding the sub-documents of different document classes to the same target document. On the other hand, the method also supports interconnection and intercommunication among the sub-document data of different document types, can realize visual display and application display of the content data in the intelligent form through the intelligent document on the basis of taking the intelligent form as a database, provides a brand new application form for interconnection and intercommunication of the data of different document types, helps a user to use the same target document (or the same document application program) to more efficiently realize data editing and data consumption, and improves user viscosity.

FIG. 11 is a flow chart illustrating another document processing method provided by an exemplary embodiment of the present application; the document processing method may be performed by the terminal 201 in the embodiment shown in fig. 2, and may include, but is not limited to, steps S1101 to S1103:

s1101: and displaying an editing interface of the second sub-document in the target document.

It should be noted that, the specific implementation process shown in step S1101 may be referred to the description of the specific implementation process shown in step S301 in the embodiment shown in fig. 3, which is not repeated herein. Also, step S301 mainly gives an interface flow of creating the second sub-document in the target document, and a background technical flow of creating the second sub-document in the target document is given below in conjunction with fig. 12 a.

The background technical process of creating the second sub-document in the target document may be performed by the terminal or performed jointly by the terminal and the server (the jointly performed background technical process may be referred to in the foregoing description of the system shown in fig. 2).

Taking the background technical process executed by the terminal as an example; as shown in fig. 12a, when detecting that there is a sub-document creation operation for a target object, the terminal may package a document data stream of a second sub-document according to the sub-document creation operation to generate a software development kit; then, the software development kit is integrated into the target document, in particular into a data packet of the target document, so that the target document can call up the second sub-document through the software development kit, and the function of creating the second sub-document in the target document is realized. Further, it is contemplated that the second sub-document created in the target document may be a blank document, or a non-blank document; therefore, the embodiment of the present application also supports determining whether the second sub-document created according to the sub-document creation operation is a blank document. If the second sub-document is a blank document, ending the creation flow of the second sub-document. Otherwise, if the second sub-document is a non-blank document, the document identification of the referenced first sub-document needs to be stored in the document data stream of the second sub-document, in particular in the software development kit, so that the second sub-document can dynamically acquire the content data in the first sub-document through the stored document identification of the first sub-document. Wherein, the software development kit (SoftwareDevelopmentKit, SDK) refers to a set of development tools when building application software for a specific software package, a software framework, a hardware platform, an operating system and the like, and the set contains related documents, examples and tools for assisting in developing a certain type of software; the SDK includes an application program interface (ApplicationProgrammingInterface, API), and the API refers to a number of predefined functions for data communication. APIs are used to interface the different components in the system. For example, the SDK of the present application contains a call interface for the second sub-document through which the target document can access routines in the second sub-document after obtaining authorization without having to access source code or understand details of the internal operating mechanism.

It should be noted that the background technical flow shown in fig. 12a is only exemplary; for example, the background technical flow of creating a second sub-document in a target document may also be seen in FIG. 12b. Unlike the background technical flow shown in fig. 12a, the embodiment of the present application supports, when a sub-document creation operation is detected, first determining whether a second sub-document created according to the sub-document creation operation is a blank document. If the second sub-document is a blank document, the document data stream of the second sub-document may be packaged in response to the sub-document creation operation to generate a software development kit. Otherwise, if the second sub-document is a non-blank document, the document identification of the referenced first sub-document needs to be stored into the document data stream of the second sub-document; then, a software development kit for the second sub-document is generated based on the document data stream of the second sub-document storing the document identification of the first sub-document. Finally, integrating the software development kit corresponding to the second sub-document into the target document, in particular into the data package of the target document, so that the target document can call up the second sub-document through the software development kit; and ends the sub-document creation flow.

S1102: in the editing interface of the second sub-document, the content data in the first sub-document is displayed in canvas form.

It should be noted that, the specific implementation process shown in steps S1102-S1103 may refer to the specific implementation process shown in steps S302-S302 in the embodiment shown in fig. 3, which is not described herein. And, steps S302-S302 mainly show an interface flow of data-associating the target component in the second sub-document with the content data in the first sub-document. A background technical flow in cross-class data fusion is given below in connection with fig. 13.

The background technical process of cross-class data fusion may be executed by the terminal or jointly executed by the terminal and the server (the jointly executed background technical process may be referred to in the related description of the system shown in fig. 2). Taking the background technical process executed by the terminal as an example; as shown in fig. 13, when there is a component creation operation in the editing interface of the second sub-document, a target component may be inserted in the second sub-document according to the component creation operation. Then, if there is a data source related event for the target component (i.e., an event generated by performing an operation of configuring a data source on the target component), the document identifier of the first sub-document may be stored in the document data stream of the second sub-document, so that the second sub-document can acquire the content data in the first sub-document through the document identifier of the first sub-document, thereby implementing visual display of the content data.

As can be seen from the above description, in the second sub-document, the data source referenced by the target component (i.e., the first sub-document) need not store the complete data into the document data stream of the second sub-document, but rather stores the document identification (e.g., document ID) of the referenced first sub-document; in this way, the second sub-document can dynamically acquire the content data (such as the form data of the intelligent form) in the first sub-document through the document identification of the first sub-document, so that the visual presentation of the content data in the first sub-document is realized, and the data in the second sub-document can be automatically and timely visually presented after the referenced content data in the first sub-document is updated. The above-mentioned process of dynamically acquiring content data in the first sub-document can be simply understood as a process of calling the content data in the first sub-document at a timing or at an irregular timing based on the stored document identification of the first sub-document. For example, the second sub-document may call the content data in the first sub-document based on the document identification timing of the first sub-document (e.g., every 1 hour); if the content data dynamically acquired at this time is different from the content data displayed in the second sub-document, automatically updating the content data originally visually displayed into the content data dynamically acquired at this time; if the content data dynamically acquired at this time is different from the content data displayed in the second sub-document, the above-mentioned update operation is not performed. For another example, the second sub-document may call content data in the first sub-document at intervals based on the document identification of the first sub-document; specifically, when the fact that the referenced content data in the first sub-document is updated is detected, the second sub-document triggers the step of calling the updated content data in the first sub-document based on the document identification of the first sub-document.

Considering that the second sub-document stores the document identification of the first sub-document, the second sub-document can dynamically acquire the content data in the first sub-document, thereby being capable of maintaining consistency of data sources and ensuring that the first sub-document can maintain the characteristic of independent editing. In other words, considering that the document identification of the referenced first sub-document is stored in the second sub-document, the embodiment of the application supports that when the content data referenced by the target component in the first sub-document is updated, the target component is automatically updated in the editing interface of the second sub-document; if the content data in the first sub-document is detected to be updated, synchronously displaying the updated content data in the first sub-document in the target component; so as to realize the data consistency of the content data in the first sub-document and the target component in the second sub-document. Compared with the method that when the content data cited in the first sub-document changes, the target component is manually updated by the target object, the automatic updating mode can also reduce the workload of the target object, ensure the data consistency and promote the intelligence of the document application program.

In order to enrich the data update control capability of the target object on the second sub-document, the embodiment of the application further supports that after detecting the update of the content data referenced in the first sub-document, data update prompt information is output first, and the data update prompt information can be used for indicating: the content data in the first sub-document changes. Then, whether the target component needs to be updated in the editing interface of the second sub-document is customized by the target object. Specifically, if the target object has a need to update the target component, the synchronization operation may be performed with respect to the data update-prompting information, so that when the terminal detects the confirmation operation with respect to the data update-prompting information, the step of performing synchronous display in the target component is triggered, and the content data in the updated first sub-document is performed. An exemplary diagram of content data in the updated first sub-document displayed synchronously in the editing interface of the second sub-document may be seen in fig. 14a; as shown in fig. 14a, when it is detected that the content data referenced in the first sub-document is updated, outputting data update prompt information in a service interface of the target document (such as any interface in the target document), where the data update prompt information includes a synchronization option; when the synchronization option is triggered, it is determined that a synchronization operation for the data update prompt information exists, and then the target component is automatically updated in the second sub-document according to the updated content data in the first sub-document.

Furthermore, in order to facilitate that the updated content of the target object can be intuitively displayed in the updated target component, the embodiment of the application also supports the highlighting of the updated content in the target component, namely, the display of the updated content data which can be visually distinguished from the display of the non-updated content data in the target component; for example, the target component associates the first list of tables and the second list of tables contained in the first sub-document, and if it is detected that the second list of tables is updated and the first list of tables is not updated, the second list of tables may be highlighted in the target component. The method comprises the steps of displaying the updated content in a target component according to the different target components. The target component shown in fig. 14a is a bar graph component, and if the data of 6 months in the first sub-document changes, the update part may be highlighted in the target component in the following manner: displaying the updated data for 6 months with a darker gray scale than the other months; of course, the highlighting manner may be other manners, which are not limited by the embodiments of the present application.

In addition, the data update prompt information also comprises a cancel option; when the cancel option is triggered, the target component in the second sub-document is not updated. In addition, the data update prompt message also includes a new option, as shown in fig. 14 b; when the new option is triggered, determining that the operation aiming at the data update prompt information is a new component, indicating that the target object wants to newly build a component for display according to the updated content data in the first sub-document, thus a third component (the third component is the same as the component of the target component) can be created, the content data in the updated first sub-document is displayed in the third component, and the target component in the second sub-document is kept unchanged. The creation position of the third component is not limited, and may be specifically set by the target object in a user-defined manner according to the requirement of the target object; for example, the third component is displayed in the second sub-document interface, or the third component is displayed in the edit interface of the newly created sub-document belonging to the second document class (i.e., a sub-document belonging to the second document class is newly created in the target document to store the third component).

S1103: and carrying out component configuration on the target component in the editing interface of the second sub-document to generate the application document.

After the second sub-document is created in the target document based on the foregoing steps, the embodiment of the present application further supports operations such as content editing and layout adjustment in an editing interface of the second sub-document; content editing and layout adjustment performed in the editing interface of the second sub-document are specifically performed by performing component editing on components in the second sub-document. Wherein component editing performed in the editing interface of the second sub-document may include, but is not limited to: component configuration, component layout, etc.; the component layout may refer to adding, deleting, or style updating components in the editing interface of the second sub-document, and the component configuration may include, but is not limited to: data source configuration (data source configuration for a target component as described in the embodiment of fig. 3 above) or style configuration (e.g., changing component style of a target component), etc.

The specific implementation process of editing the components executed in the editing interface of the second sub-document into the data source configuration may be referred to the foregoing related description, which is not repeated herein. The following description will mainly be made of specific implementation procedures of the style configuration and the component layout included in the component configuration.

The embodiment of the application supports component style configuration of the target component in the editing interface of the second sub-document. In a specific implementation, the component configuration menu associated with the target component (for an implementation manner of triggering and displaying the component configuration menu associated with the target component, see the related description) includes: one or more candidate component styles corresponding to the target component. In this way, when the target object has a need to change the component style of the target component, the target object may directly select a desired component style in the component configuration menu, at which time the terminal updates and displays the component style of the target component as the target component style in the editing interface of the second sub-document in response to a selection operation for the target component style of the one or more candidate component styles. The component styles of the target component are enriched, so that the requirements of the target object on different component styles are met.

As shown in fig. 15, the component type of the target component displayed in the editing interface of the second sub-document is a chart type, specifically a bar chart component, and the component configuration menu associated with the target component includes one or more candidate component styles corresponding to the target component, such as candidate component style 1501, candidate component style 1502, candidate component style 1503, and the like; when the target object wants the component style of the target component to be displayed as a candidate component style 1502, the candidate component style 1502 may be triggered, at which time the original component style update of the target component is displayed as a candidate component style 1502 in the editing interface of the second sub-document. In addition, considering that the display area of the component configuration menu is limited and the number of candidate component styles may be large, it is supported to hide part of the candidate component styles in the component configuration menu; and by performing a switching operation (such as a sliding operation or a triggering operation for the switching key 1504) in the component configuration menu, the hidden candidate component patterns are displayed in a sliding manner.

In addition to supporting style configuration for a target component in a component configuration menu, the embodiment of the application also supports updating the target component to other types of components in a chart type in the component configuration menu, if the target component is a bar chart component, the bar chart component can be updated to be a fan-shaped component, namely, at the moment, the content data presented by the original bar chart component is visually presented in a fan-shaped diagram form. As shown in fig. 16, a type switching option 1601 is included in the component configuration menu, and when the type switching option 1601 is triggered, a plurality of candidate type components under the chart type are output to facilitate target object selection.

In addition, the intelligent document (namely the second sub-document) provided by the embodiment of the application also supports music editing and overall layout. As described above, the editing interface of the intelligent document is carried and provided by the canvas, thus supporting the realization of component stacking or arbitrary layout in the editing interface, and meeting the requirements of creatively setting layout of target objects, thereby enabling the intelligent document to be used in various data consumption scenes. The implementation process for realizing the overall layout in the editing interface of the intelligent document can comprise the following steps: when the target object has a need to adjust the display position of the target component in the editing interface, the target object may perform a drag operation on the target component in the editing interface of the second sub-document; then the target component can be controlled to move in the editing interface of the second sub-document in real time according to the drag operation; and displaying the target component at the released position of the drag operation. In the case that the second sub-document includes a plurality of components, after the target object drags the plurality of components, the layout styles of the plurality of components in the second sub-document may include, but are not limited to: the plurality of components are displayed in parallel along the horizontal direction of the editing interface of the second sub-document; or, a plurality of editing interfaces of the second sub-document are displayed side by side along the vertical direction; or, a plurality of the editing interfaces are displayed along the diagonal direction of the editing interface of the second sub-document; etc. Of course, the manner of the layout of the second sub-document on the component supports, in addition to the dragging of the component described above, the realization of the layout of the component (such as the stacking of the components) by setting a layer in the component configuration menu associated with the component, and the like; the embodiment of the application does not limit the specific implementation process of the component layout in the editing interface of the second sub-document.

In addition, the embodiment of the application also supports the jump from the second sub-document to the editing interface of the data source associated with the target component, so that the target object can be rapidly positioned to the data source. In a specific implementation, if the target object has a requirement for viewing a data source of a target component in the editing interface of the second sub-document, the target object may perform a data source viewing operation for the target component; specifically, the editing interface of the second sub-document includes a data source viewing option (such as viewing option 1701 shown in fig. 17). Then when the data source view option is triggered, it is determined that there is a data source view operation for the target component, at which time the display is switched from the editing interface of the second sub-document to the editing interface of the first sub-document in accordance with the data source view operation for the target component. Furthermore, in order to facilitate that the target object can intuitively perceive the referenced content data from the editing interface of the first sub-document, the embodiment of the application further supports that the referenced content data in the first sub-document is highlighted in the editing interface of the first sub-document; the embodiment of the application does not limit the specific display mode of the highlighting.

In summary, creating sub-documents of different document categories in the target document may be achieved by the above-mentioned related description, e.g. in case the target document contains a first sub-document belonging to a first document category, enabling to create a second sub-document belonging to a second document category in the target document; and cross-class fusion of sub-documents of different document classes is supported, for example, a target component in a second sub-document refers to content data in a first sub-document, so that interconnection and interworking between the content data in the first sub-document and the target component in the second sub-document are realized. For convenience of description, the document obtained by cross-class fusion is supported to be called an application document, namely the application document is a document created by a target object according to personalized scene requirements.

In the data consumption scene, specific data consumption requirements obtained by personalized editing can be checked from an editing interface of a second sub-document in the application document by sharing the created application document, for example, the approximate fluctuation condition of data along with the date is known through a bar graph in the editing interface of the second sub-document. A background technical flow for acquiring the interface content of the editing interface of the second sub-document and rendering and displaying the interface content when the editing interface of the second sub-document is opened and displayed through the application document is provided below in connection with FIG. 18. As shown in fig. 18, after a second sub-document (i.e., an intelligent document) in the application document is opened by the terminal, a document data request may be generated; the terminal sends the document data request to a server, specifically to a background server corresponding to the second sub-document, and then the background server corresponding to the second sub-document responds to the document data request to return the document data of the second sub-document, wherein the document data can comprise component information (or component data such as component type, component style or component display position, etc.) of each component contained in an editing interface of the second sub-document. Further, for the component rendering, after receiving the component information, the terminal may further parse the component information of the component to parse the data source information referenced by the component. And then, the terminal can generate a content data acquisition request according to the data source information, and send the content data acquisition request to a background server corresponding to the data source through the document identification of the first sub-document, if the data source of the target component is the first sub-document, the background server corresponding to the data source is determined to be the background server corresponding to the first sub-document. In this way, the background server corresponding to the data source can respond to the content data acquisition request to return the content data referenced by the target component in the second sub-document to the terminal. And finally, the terminal performs rendering display of the target component based on the received content data referenced by the target component so as to realize visual presentation of the content data referenced in the first sub-document.

In summary, the embodiment of the application supports creation of sub-documents of different document classes in the same target document, and enriches the forms of document applications supported by document application programs. And the linkage between the sub-document data of different document categories is supported, for example, the linkage between the editing component in the intelligent document and the table data in the intelligent table can realize the more visual and application presentation of the table data in the intelligent table through the editing component in the intelligent document, and the category fusion mode accords with the document editing habit of a user and has low use threshold. In addition, the editing interface of the intelligent document is carried and provided by the canvas, so that a user can self-define and layout the intelligent document in the canvas according to the creation requirement, and a creative tool is created for the user; therefore, after encountering data consumption problems under different data editing scenes, a user can use the intelligent form as a database, and the requirements of data consumption scenes are met through the music height editing of the components and the adjustment of the overall layout in the intelligent document.

The foregoing details of the method of the present application and, in order to facilitate better practice of the method of the present application, a device of the present application is provided below.

Fig. 19 is a schematic view showing a structure of a document processing apparatus according to an exemplary embodiment of the present application, which may be a computer program (including program code) running in a terminal; the document processing device may be used to perform some or all of the steps in the method embodiments shown in fig. 3 and 11; the device comprises the following units:

a display unit 1901 for displaying an editing interface of a second sub-document in a target document, the target document including a first sub-document and a second sub-document, the first sub-document belonging to a first document category and the second sub-document belonging to a second document category;

and a processing unit 1902, configured to display, in the editing interface of the second sub-document, the content data in the first sub-document in the form of canvas, where the content data is kept updated synchronously in the first sub-document and the second sub-document.

In one implementation, the processing unit 1902 is configured to, when displaying the editing interface of the second sub-document in the target document, specifically:

In one implementation, the processing unit 1902 is further configured to:

In one implementation, the editing interface of the second sub-document includes a target component, where the target component is the first component or the second component; the processing unit 1902 is further configured to:

In one implementation, the processing unit 1902 is further configured to:

In one implementation, one or more candidate component styles corresponding to the target component are contained in the component configuration menu; the processing unit 1902 is further configured to:

In one implementation, the processing unit 1902 is further configured to:

integrating the software development kit into a target document;

In one implementation, the processing unit 1902 is configured to, when displaying the content data in the first sub-document in canvas form in the editing interface of the second sub-document, specifically be configured to:

According to an embodiment of the present application, each unit in the document processing apparatus shown in fig. 19 may be constituted by combining one or several other units separately or in total, or some unit(s) thereof may be constituted by splitting into a plurality of units having a smaller function, which can achieve the same operation without affecting the achievement of the technical effects of the embodiment of the present application. The above units are divided based on logic functions, and in practical applications, the functions of one unit may be implemented by a plurality of units, or the functions of a plurality of units may be implemented by one unit. In other embodiments of the present application, the document processing apparatus may also include other units, and in actual practice, these functions may also be implemented with assistance from other units, and may be implemented by cooperation of a plurality of units. According to another embodiment of the present application, a document processing apparatus as shown in fig. 19 may be constructed by running a computer program (including program code) capable of executing the steps involved in the respective methods shown in fig. 3 and 11 on a general-purpose computing device such as a computer including a Central Processing Unit (CPU), an access storage medium (RAM), a read-only storage medium (ROM), and the like processing elements and storage elements, and implementing the document processing method of the embodiment of the present application. The computer program may be recorded on, for example, a computer-readable recording medium, and loaded into and run in the above-described computing device through the computer-readable recording medium.

Fig. 20 is a schematic diagram showing a structure of a terminal according to an exemplary embodiment of the present application. Referring to fig. 20, the terminal includes a processor 2001, a communication interface 2002, and a computer readable storage medium 2003. Wherein the processor 2001, communication interface 2002, and computer-readable storage medium 2003 may be connected by a bus or other means. Wherein the communication interface 2002 is used to receive and transmit data. The computer readable storage medium 2003 may be stored in a memory of the terminal, the computer readable storage medium 2003 for storing a computer program comprising program instructions, the processor 2001 for executing the program instructions stored by the computer readable storage medium 2003. The processor 2001 (or CPU) is a computing core and a control core of the terminal, which are adapted to implement one or more instructions, in particular to load and execute one or more instructions to implement a corresponding method flow or a corresponding function.

The embodiment of the application also provides a computer readable storage medium (Memory), which is a Memory device in the terminal and is used for storing programs and data. It will be appreciated that the computer readable storage medium herein may include both a built-in storage medium in the terminal and an extended storage medium supported by the terminal. The computer readable storage medium provides a storage space that stores a processing system of the terminal. Also stored in this memory space are one or more instructions, which may be one or more computer programs (including program code), adapted to be loaded and executed by the processor 2001. It should be noted that, the computer readable storage medium herein may be a high speed RAM memory or a non-volatile memory (non-volatile memory), such as at least one disk memory; alternatively, it may be at least one computer-readable storage medium located remotely from the aforementioned processor.

In one embodiment, the computer-readable storage medium has one or more instructions stored therein; loading and executing by the processor 2001 one or more instructions stored in a computer-readable storage medium to implement the corresponding steps in the document processing method embodiments described above; in particular implementations, one or more instructions in the computer-readable storage medium are loaded by the processor 2001 and perform the steps of:

In one implementation, one or more instructions in the computer-readable storage medium are loaded by the processor 2001 and upon execution of the editing interface that displays the second sub-document in the target document, the following steps are specifically performed:

In one implementation, one or more instructions in a computer-readable storage medium are loaded by the processor 2001 and further perform the steps of:

In one implementation, the editing interface of the second sub-document includes a target component, where the target component is the first component or the second component; one or more instructions in the computer-readable storage medium are loaded by the processor 2001 and further perform the steps of:

In one implementation, one or more candidate component styles corresponding to the target component are contained in the component configuration menu; one or more instructions in the computer-readable storage medium are loaded by the processor 2001 and further perform the steps of:

integrating the software development kit into a target document;

In one implementation, one or more instructions in the computer-readable storage medium are loaded by the processor 2001 and, when executed in an editing interface of the second sub-document, display the content data in the first sub-document in canvas form, specifically perform the steps of:

Based on the same inventive concept, the principle and beneficial effects of solving the problem of the terminal provided in the embodiments of the present application are similar to those of solving the problem of the method for processing the file in the embodiments of the present application, and may refer to the principle and beneficial effects of implementing the method, which are not described herein for brevity.

Embodiments of the present application also provide a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the terminal reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions so that the terminal performs the above-described document processing method.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable devices. The computer instructions may be stored in or transmitted across a computer-readable storage medium. The computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). Computer readable storage media can be any available media that can be accessed by a computer or data processing device, such as a server, data center, or the like, that contains an integration of one or more of the available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily appreciate variations or alternatives within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A document processing method, comprising:

displaying an editing interface of a second sub-document in a target document, wherein the target document comprises a first sub-document and the second sub-document, the first sub-document belongs to a first document class, and the second sub-document belongs to a second document class;

and displaying the content data in the first sub-document in the form of canvas in an editing interface of the second sub-document, wherein the content data is synchronously updated in the first sub-document and the second sub-document.

2. The method of claim 1, wherein displaying the editing interface of the second sub-document in the target document comprises:

Wherein the sub-document creation operation includes at least one of: a referencing operation for content data in the first sub-document; triggering operation of a sub-document creation control, wherein the sub-document creation control is displayed in a toolbar of the target document or the sub-document creation control is displayed in an option window; gesture operations in the target document or in an editing interface of the first sub-document; a voice input operation in the target document or in an editing interface of the first sub-document; or a shortcut key input operation.

3. The method of claim 2, wherein if the sub-document creation operation includes any of: aiming at triggering operation of a sub-document creation control, gesture operation in the target document or an editing interface of the first sub-document, voice input operation or shortcut key input operation in the target document or the editing interface of the first sub-document, and the created editing interface of the second sub-document is a blank interface;

if the sub-document creation operation includes: and carrying out reference operation on the content data in the first sub-document, and automatically filling the content data referenced in the editing interface of the first sub-document in the editing interface of the second sub-document.

4. The method of claim 3, wherein the first document class is a form class, the content data included in the editing interface of the first sub-document is form data, and the second document class is a canvas class;

the editing interface of the second sub-document automatically fills the referenced content data in the following manner: automatically populating in a first component table data referenced in the first sub-document; the first component is a default component or a component selected from a component panel in a self-defining way, the component type of the first component is a chart type, and the first component belonging to the chart type comprises any one of the following components: list components, sector diagram components, polyline components, circle components, and column diagram components.

5. The method of claim 1, wherein after displaying the editing interface of the second sub-document in the target document, further comprising:

responsive to a component creation operation for the second sub-document, displaying a component panel, the component panel containing a type identification of at least one component type;

and displaying a second component under the target component type corresponding to the selected target type identifier in the second sub-document interface according to the identifier selection operation.

6. The method of claim 5, wherein the component creation operation comprises any of: an input operation of a shortcut key, a trigger operation of creating an option for a component, or a gesture operation in an editing interface of the second sub-document;

the display mode of the assembly panel comprises the following steps: displaying the second sub-document on the editing interface of the second sub-document in a floating layer window mode or displaying the second sub-document in a target area in the editing interface of the second sub-document;

the identification selection operation includes: and triggering the target type identifier, or moving the target type identifier from the component panel to a drag operation of an editing interface of the second sub-document.

7. The method of claim 1, wherein the editing interface of the second sub-document includes a target component, the target component being either a first component or a second component; the displaying the content data in the first sub-document in the canvas form in the editing interface of the second sub-document comprises the following steps:

when the target component is triggered, a component configuration menu is displayed, wherein the component configuration menu comprises data source configuration options;

When the data source configuration option is triggered, displaying data source identifications of one or more candidate data sources; the candidate data sources include at least one of: a first sub-document in the target document, independent of a reference document of the target document, or independent of a sub-document in a reference document of the target document;

content data in a first sub-document is displayed in the target component in response to a triggering operation for a data source identification of the first sub-document.

8. The method of claim 7, wherein the method further comprises:

9. The method of claim 8, wherein the synchronously displaying in the target component, before the updated content data in the first sub-document, further comprises:

and when the confirmation operation aiming at the data updating prompt information exists, triggering and executing the step of synchronously displaying the content data in the updated first sub-document in the target component.

10. The method of claim 9, wherein the method further comprises:

when the operation of the data update prompt information is a new component, a third component is created, and content data in the updated first sub-document is displayed in the third component;

wherein the third component is the same component type as the target component; and the third component is displayed in the second sub-document interface, or the third component is displayed in an editing interface of a newly built sub-document belonging to the second document category.

11. The method of claim 7, wherein the set up configuration menu includes one or more candidate component styles corresponding to the target component; the method further comprises the steps of:

in response to a selection operation for a target component style of the one or more candidate component styles, in an editing interface of the second sub-document, component style updates of the target component are displayed as the target component style.

12. The method of claim 7, wherein the method further comprises:

switching display from the editing interface of the second sub-document to the editing interface of the first sub-document according to a data source viewing operation for the target component;

13. The method of claim 7, wherein the method further comprises:

controlling the target component to move in an editing interface of the second sub-document according to the drag operation;

wherein the layout style of the plurality of components in the second sub-document comprises: displaying the second sub-document in parallel along the horizontal direction of the editing interface of the second sub-document; or displaying the second sub-document side by side along the vertical direction of the editing interface of the second sub-document; or displaying along the diagonal direction of the editing interface of the second sub-document.

14. The method of any of claims 1-13, wherein the first sub-document is any of at least one sub-document belonging to a first document category in the target document and the second sub-document is any of at least one sub-document belonging to a second document category in the target document.

15. The method of claim 1, wherein creating the second sub-document in the target document comprises:

integrating the software development kit into the target document;

the second sub-document is created in the target document that integrates the software development kit.

16. The method of claim 15, wherein displaying the content data in the first sub-document in canvas form in the editing interface of the second sub-document comprises:

storing the document identification of the first sub-document into the document data stream of the second sub-document;

17. A document processing apparatus, comprising:

the display unit is used for displaying an editing interface of a second sub-document in the target document, wherein the target document comprises a first sub-document and the second sub-document, the first sub-document belongs to a first document class, and the second sub-document belongs to a second document class;

18. A terminal, comprising:

a processor adapted to execute a computer program;

a computer readable storage medium having stored therein a computer program which, when executed by the processor, implements the document processing method according to any one of claims 1-16.

19. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program adapted to be loaded by a processor and to perform the document processing method according to any of claims 1-16.

20. A computer program product comprising computer instructions which, when executed by a processor, implement the document processing method of any of claims 1 to 16.