Collaborative editing method, apparatus and device, and storage medium
By storing collaborative documents on a cloud server and using a cloud client for collaborative editing, the problem of traditional file editors being unable to support multi-person collaboration and management is solved, thus improving user experience and ease of use.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-11-13
- Publication Date
- 2026-04-10
AI Technical Summary
Current file editors only save documents locally, making it impossible to enable multi-user collaboration and file management.
Collaborative documents are stored on a cloud server and edited collaboratively via a cloud client, including document retrieval, display, and processing of collaborative editing instructions.
It enables collaborative editing and file management by multiple users, improving user experience and ease of use.
Smart Images
Figure CN121833636A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of computer, and particularly relates to a collaborative editing method and device, equipment and a storage medium. BACKGROUND
[0002] At present, the traditional file editor only saves the document locally, cannot collaborate with multiple people, and cannot manage the document. SUMMARY
[0003] The main purpose of the present application is to provide a collaborative editing method, device, equipment and a storage medium, which aims to solve the technical problem that the prior art only saves the document locally, cannot collaborate with multiple people, and cannot manage the file.
[0004] To achieve the above purpose, the present application provides a collaborative editing method, which is applied to a cloud client corresponding to a cloud server, and the collaborative editing method comprises the following steps of:
[0005] When receiving a collaborative editing request, a collaborative document is acquired from a cloud storage space corresponding to the cloud server according to the collaborative editing request;
[0006] The collaborative document is displayed.
[0007] The collaborative document is collaboratively edited according to a collaborative editing instruction, and the collaborative editing instruction is an operation instruction fed back based on the collaborative document.
[0008] Optionally, the collaborative editing of the collaborative document according to the collaborative editing instruction comprises the following steps of:
[0009] When the collaborative editing instruction is to insert a cloud file, the authority of a user inputting the collaborative editing instruction is verified.
[0010] The cloud file is filtered according to the verification result, and the filtered cloud file is displayed.
[0011] A cloud file selection instruction fed back based on the filtered cloud file is received.
[0012] A target cloud file is selected from the filtered cloud file according to the cloud file selection instruction and inserted into the collaborative document.
[0013] Optionally, the collaborative editing of the collaborative document according to the collaborative editing instruction comprises the following steps of:
[0014] When the collaborative editing instruction is to insert a template, a recommended template is displayed.
[0015] A template selection instruction fed back based on the recommended template is received.
[0016] According to the template selection instruction, a target template is selected from the recommended templates and inserted into the collaborative document.
[0017] Optionally, the collaborative editing of the collaborative document according to the collaborative editing instruction comprises:
[0018] Upon receiving the member collaboration instruction, a collaboration member and a to-do item are determined according to the member collaboration instruction;
[0019] Upon saving the collaborative document, the to-do item is sent to a cloud client corresponding to the collaboration member.
[0020] Optionally, the sending of the to-do item to the cloud client corresponding to the collaboration member upon saving the collaborative document comprises:
[0021] Upon saving the collaborative document, a notification mark corresponding to the to-do item is obtained;
[0022] According to the notification mark, it is verified whether the to-do item has been sent to the cloud client corresponding to the collaboration member;
[0023] If not, the to-do item is sent to the cloud client corresponding to the collaboration member.
[0024] Optionally, the obtaining of the collaborative document from the cloud storage space corresponding to the cloud server upon receiving the collaborative editing request comprises:
[0025] Upon receiving the collaborative editing request, the collaborative editing request is authenticated;
[0026] Upon passing the authentication, the collaborative document is obtained from the cloud storage space corresponding to the cloud server according to the collaborative editing request.
[0027] Optionally, the collaborative editing of the collaborative document according to the collaborative editing instruction comprises:
[0028] The collaborative editing instruction is parsed by a rich text editor to obtain a rich text element;
[0029] The collaborative document is collaboratively edited according to the rich text element.
[0030] Optionally, the collaborative document is stored in the cloud storage space in a pre-specified block level data.
[0031] Optionally, the displaying of the collaborative document comprises:
[0032] The collaborative document is parsed to obtain a token sequence;
[0033] An element tree is generated based on the calibration sequence, and the element tree is displayed.
[0034] Optionally, displaying the collaborative document includes:
[0035] Obtain the collaboration status information of the collaborative document;
[0036] The collaborative document is displayed, along with the collaboration status information.
[0037] Optionally, after performing collaborative editing of the collaborative document according to collaborative editing instructions, wherein the collaborative editing instructions are operation instructions based on feedback from the collaborative document, the process further includes:
[0038] The collaborative document is updated in real time after collaborative editing is completed;
[0039] And / or, send update reminders and update operation entry points to the user currently viewing the collaborative document.
[0040] Optionally, the collaborative document is displayed in the cloud folder list in the form of a folder dashboard to preview the content of the collaborative document in the cloud folder list.
[0041] Furthermore, to achieve the above objectives, the present invention also proposes a collaborative editing device, which is applied to a cloud client corresponding to a cloud server. The collaborative editing device includes:
[0042] The document retrieval module is used to retrieve the collaborative document from the cloud storage space corresponding to the cloud server when a collaborative editing request is received.
[0043] The document display module is used to display the collaborative documents;
[0044] The collaborative editing module is used to collaboratively edit the collaborative document according to collaborative editing instructions, which are operation instructions based on feedback from the collaborative document.
[0045] Optionally, the collaborative editing module is further configured to: verify the user's permissions when the collaborative editing instruction is to insert a cloud file; filter the cloud files according to the verification result and display the filtered cloud files; receive a cloud file selection instruction based on the filtered cloud files; and select a target cloud file from the filtered cloud files and insert it into the collaborative document according to the cloud file selection instruction.
[0046] Optionally, the collaborative editing module is further configured to display recommended templates when the collaborative editing instruction is to insert a template; receive a template selection instruction based on the recommended templates; and select a target template from the recommended templates and insert it into the collaborative document according to the template selection instruction.
[0047] Optionally, the collaborative editing device further includes:
[0048] The member collaboration module is used to determine the collaborating members and to-do items according to the member collaboration instruction when a member collaboration instruction is received; and to send the to-do items to the cloud client corresponding to the collaborating member when the collaborative document is saved.
[0049] Optionally, the member collaboration module is further configured to, when saving the collaboration document, obtain the notification tag corresponding to the to-do item; verify whether the to-do item has been sent to the cloud client corresponding to the collaboration member based on the notification tag; if not, send the to-do item to the cloud client corresponding to the collaboration member.
[0050] Optionally, the document acquisition module is further configured to authenticate the collaborative editing request upon receiving it; and after successful authentication, retrieve the collaborative document from the cloud storage space corresponding to the cloud server according to the collaborative editing request.
[0051] Furthermore, to achieve the above objectives, the present invention also proposes a collaborative editing device, which includes a memory, a processor, and a collaborative editing program stored in the memory and executable on the processor, the collaborative editing program being configured to implement the collaborative editing method as described above.
[0052] Furthermore, to achieve the above objectives, the present invention also proposes a storage medium storing a collaborative editing program, which, when executed by a processor, implements the collaborative editing method as described above.
[0053] This invention discloses a method for retrieving a collaborative document from the cloud storage space corresponding to the cloud server upon receiving a collaborative editing request, displaying the collaborative document, receiving collaborative editing instructions based on the collaborative document, and collaboratively editing the collaborative document according to the collaborative editing instructions. Since this invention is applied to the cloud client corresponding to the cloud server, storing the collaborative document on the cloud server and accessing the cloud server through the cloud client to collaboratively edit the collaborative document, it solves the technical problems of existing technologies that only save documents locally, cannot support multi-person collaboration, and cannot perform file management, thereby improving user experience and ease of operation. Attached Figure Description
[0054] Figure 1 This is a schematic diagram of the structure of a collaborative editing device in the hardware operating environment involved in the embodiments of the present invention;
[0055] Figure 2 This is a flowchart illustrating the first embodiment of the collaborative editing method of the present invention;
[0056] Figure 3 This is a flowchart illustrating the second embodiment of the collaborative editing method of the present invention;
[0057] Figure 4 This is a flowchart illustrating the third embodiment of the collaborative editing method of the present invention;
[0058] Figure 5 This is a flowchart illustrating the fourth embodiment of the collaborative editing method of the present invention;
[0059] Figure 6 This is a flowchart illustrating the fifth embodiment of the collaborative editing method of the present invention;
[0060] Figure 7 This is a schematic diagram of the collaborative document functional structure according to an embodiment of the collaborative editing method of the present invention;
[0061] Figure 8 This is a structural block diagram of the first embodiment of the collaborative editing device of the present invention.
[0062] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation
[0063] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
[0064] Reference Figure 1 , Figure 1 This is a schematic diagram of the collaborative editing device structure of the hardware operating environment involved in the embodiments of the present invention.
[0065] like Figure 1As shown, the collaborative editing device may include: a processor 1001, such as a central processing unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. The communication bus 1002 is used to enable communication between these components. The user interface 1003 may include a display screen, and optionally, it may also include a standard wired interface or a wireless interface. In this invention, the wired interface of the user interface 1003 may be a USB interface. The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a Wireless-Fidelity (Wi-Fi) interface). The memory 1005 may be high-speed random access memory (RAM) or non-volatile memory (NVM), such as a disk storage device. The memory 1005 may also optionally be a storage device independent of the aforementioned processor 1001.
[0066] Those skilled in the art will understand that Figure 1 The structure shown does not constitute a limitation on collaborative editing devices and may include more or fewer components than shown, or combine certain components, or have different component arrangements.
[0067] like Figure 1 As shown, the memory 1005, which is identified as a computer storage medium, may include an operating system, a network communication module, a user interface module, and a collaborative editing program.
[0068] exist Figure 1 In the collaborative editing device shown, the network interface 1004 is mainly used to connect to the backend server and communicate data with the backend server; the user interface 1003 is mainly used to connect to the user device; the collaborative editing device calls the collaborative editing program stored in the memory 1005 through the processor 1001 and executes the collaborative editing method provided in the embodiment of the present invention.
[0069] Based on the above hardware structure, an embodiment of the collaborative editing method of the present invention is proposed.
[0070] Reference Figure 2 , Figure 2 This is a flowchart illustrating the first embodiment of the collaborative editing method of the present invention, which presents the first embodiment of the collaborative editing method of the present invention.
[0071] It should be understood that in modern internet applications, more and more people use browsers to access and use applications. Therefore, there is an urgent need for a way to edit and manage text data in the browser. However, browsers themselves do not provide native text editing functions, so users need to download and install traditional text editors. However, traditional text editors cannot be stored in the cloud, thus they have technical problems such as only saving documents locally, not being able to collaborate with multiple users, and not being able to manage files.
[0072] To overcome the above-mentioned shortcomings, this embodiment is applied to the cloud client corresponding to the cloud server. The collaborative document is stored on the cloud server, and the collaborative document is collaboratively edited by accessing the cloud server through the cloud client. This solves the technical problems of the prior art, which only saves documents locally, cannot enable multi-person collaboration, and cannot perform file management. This improves the user experience and ease of operation. The cloud client can be a web client of a cloud application (e.g., cloud storage) on a browser.
[0073] Of course, the collaborative editing method of the present invention can be applied to other scenarios besides the example scenarios mentioned above. In other scenarios, the cloud client can be the application client of the cloud application, and this embodiment does not limit this.
[0074] In the first embodiment, the collaborative editing method is applied to a cloud client corresponding to a cloud server, and the collaborative editing method includes:
[0075] Step S10: Upon receiving a collaborative editing request, retrieve the collaborative document from the cloud storage space corresponding to the cloud server according to the collaborative editing request.
[0076] It is understood that the execution subject of this embodiment can be a collaborative editing device with data processing, network communication and program running functions, such as a computer, mobile device, or other electronic devices that can achieve the same or similar functions. This embodiment does not limit this.
[0077] It should be noted that collaborative editing requests can be initiated manually by the user who created the collaborative document or by the collaborating user, or they can be automatically initiated by the cloud client according to actual needs. This embodiment does not impose any restrictions on this. The user who creates the collaborative document can be the user who creates the collaborative document, and the collaborating user can be specified by the user who creates the collaborative document.
[0078] It should be understood that retrieving a collaborative document from the corresponding cloud storage space on the cloud server based on a collaborative editing request can involve sending the collaborative editing request to the cloud server, the cloud server searching for the corresponding collaborative document in the cloud storage space, and then sending the collaborative document to the cloud client. The collaborative document in the cloud storage space can be uploaded by the cloud client when a user creates the collaborative document, thus achieving cloud storage for the collaborative document. In specific implementations, the collaborative document can be an XMD file.
[0079] Furthermore, to enhance security, the collaborative documents are stored in the cloud storage space in a pre-specified block-level data format.
[0080] It should be understood that many websites and applications in the prior art store document content through HTML nodes, which is vulnerable to malicious code injection or cross-site scripting (XSS) attacks, thus posing security risks. Therefore, to overcome the above-mentioned shortcomings, this embodiment uses pre-specified block-level data instead of HTML nodes for storage to prevent malicious code injection and cross-site scripting attacks, thereby enhancing security.
[0081] Using pre-defined block-level data instead of HTML nodes enhances security because: 1. It prevents HTML injection attacks: If user input is directly embedded in HTML code, attackers may insert malicious tags or code, corrupting the page structure or performing unwanted operations. Separating user-provided data from HTML code effectively reduces the risk of HTML injection attacks. 2. It prevents cross-site scripting (XSS) attacks: Separating user input data from HTML code ensures that user input is not interpreted as code, thus preventing malicious script injection into the webpage. This helps prevent XSS attacks, where attackers attempt to execute malicious scripts in the user's browser.
[0082] Furthermore, to facilitate viewing the content of collaborative documents in the cloud folder list, the collaborative documents are displayed in the cloud folder list in the form of a folder dashboard, so as to preview the content of the collaborative documents in the cloud folder list.
[0083] It should be understood that, in order to facilitate viewing the content of collaborative documents in the cloud folder list, in this embodiment, collaborative documents are displayed in the cloud folder list in the form of a folder dashboard. The folder dashboard form means that when collaborative documents are displayed in the cloud folder list, the content of the collaborative documents can be previewed in the cloud folder list.
[0084] Step S20: Display the collaborative document.
[0085] It is understood that displaying collaborative documents can specifically refer to displaying an online preview interface or an online editing interface for the collaborative documents, and this embodiment does not limit this.
[0086] Furthermore, to facilitate users' viewing of collaborative documents, step S20 includes: performing syntactic analysis on the collaborative document to obtain a calibration sequence; generating an element tree based on the calibration sequence; and displaying the element tree.
[0087] It should be understood that performing syntactic analysis on collaborative documents to obtain the tag sequence can be achieved by using a lexical analyzer to segment the text content of the collaborative document into a list of file elements, such as text paragraphs, headings, images, links, styles, etc., to obtain the tag sequence.
[0088] Understandably, an element tree can be constructed using the calibration sequence. Once the element tree is constructed, it is displayed to the user, who can then perform collaborative editing operations such as adding, deleting, and viewing the text content of the collaborative document.
[0089] Step S30: Collaboratively edit the collaborative document according to the collaborative editing instructions, wherein the collaborative editing instructions are operation instructions based on the feedback from the collaborative document.
[0090] It should be understood that collaborative documents provide a text editor for users to operate. After viewing the collaborative document, users can initiate collaborative editing commands through the text editor. The cloud client will then collaboratively edit the collaborative document according to the collaborative editing commands. These collaborative editing commands include, but are not limited to, operations such as adding, deleting, and viewing.
[0091] Of course, to facilitate user editing of collaborative documents, this embodiment can also provide a rich text editor for users to operate.
[0092] It is understandable that when users collaboratively edit a document, the cloud client will automatically save the document (saving every 5 minutes). Of course, users can also manually save and publish to complete the file editing, and this embodiment does not restrict this.
[0093] In this embodiment, upon receiving a collaborative editing request, the system retrieves the collaborative document from the cloud storage space corresponding to the cloud server, displays the collaborative document, receives collaborative editing instructions based on the collaborative document, and performs collaborative editing on the collaborative document according to the instructions. Since this embodiment is applied to the cloud client corresponding to the cloud server, the collaborative document is stored on the cloud server, and the collaborative document is collaboratively edited by accessing the cloud server through the cloud client. This solves the technical problems of existing technologies that only save documents locally, cannot support multi-person collaboration, and cannot perform file management, thereby improving user experience and ease of operation.
[0094] Reference Figure 3 , Figure 3 This is a flowchart illustrating the second embodiment of the collaborative editing method of the present invention, based on the above. Figure 2 The first embodiment shown presents a second embodiment of the collaborative editing method of the present invention.
[0095] In the second embodiment, step S30 includes:
[0096] Step S301': When the collaborative editing instruction is to insert a cloud file, verify the permissions of the user who entered the collaborative editing instruction.
[0097] It should be understood that, in order to improve the association between collaborative editing and existing files, in this embodiment, the collaborative editing instruction can also be to insert cloud files (e.g., cloud drive files).
[0098] Step S302': Filter the cloud files based on the verification results and display the filtered cloud files.
[0099] Understandably, in order to improve the security of cloud files, in this embodiment, before displaying cloud files for users to select, the cloud files will be filtered according to the permissions of the user who inputs the collaborative editing instructions, and the filtered cloud files will be displayed.
[0100] Step S303': Receive the cloud file selection instruction based on the cloud file feedback after filtering.
[0101] Step S304': Select the target cloud file from the filtered cloud files according to the cloud file selection instruction and insert it into the collaborative document.
[0102] For ease of understanding, the following example is provided, but it does not limit the invention. In one example, a user clicks the "Insert - Cloud Drive File" function. The cloud drive client opens a file / folder selector, which verifies user permissions and filters files / folders for the user to choose from. After the user completes the selection, the cloud drive client generates a specified text content and merges it into the collaborative document. Specifically, the specified text content can be divided into file list elements, such as text paragraphs, titles, images, links, styles, etc., to obtain an annotation sequence. The annotation sequence can be used to construct an element tree. After the element tree is constructed, it is displayed to the user, who can then perform collaborative editing operations such as adding, deleting, and viewing the specified text content.
[0103] In this embodiment, the collaborative editing command can also insert cloud files, thereby improving the association between collaborative editing and existing files, making it easier for users to perform collaborative editing.
[0104] Reference Figure 4 , Figure 4This is a flowchart illustrating the third embodiment of the collaborative editing method of the present invention, based on the above. Figure 2 The first embodiment shown presents a third embodiment of the collaborative editing method of the present invention.
[0105] In the third embodiment, step S30 includes:
[0106] Step S301: When the collaborative editing command is to insert a template, display the recommended template.
[0107] Understandably, in order to facilitate collaborative editing by users, this embodiment may also display preset templates for users to select from.
[0108] It should be noted that the recommended templates can contain diverse template data. Recommended templates include, but are not limited to, meeting collaboration templates, team project management templates, and other templates with the file extension .xmd. This embodiment does not impose any restrictions on this.
[0109] Step S302: Receive template selection instructions based on the feedback from the recommended template.
[0110] Step S303: Select a target template from the recommended templates and insert it into the collaborative document according to the template selection instruction.
[0111] For ease of understanding, the following examples are provided, but are not intended to limit the invention. In one example, the right side of the online editing interface for collaborative documents provides templates with the file extension .xmd, such as meeting collaboration templates and team project management templates, which can be clicked to quickly use or create template files.
[0112] In another example, clicking the blue template button in a blank collaborative document will bring up meeting collaboration templates and team project management templates. Clicking "use" will quickly insert the corresponding content into the file for use.
[0113] In another example, clicking on a recommended template opens the template interface. The template interface manages the backend data embedding and online / offline status. Clicking to use the template automatically writes content into the collaborative document. During the writing process, the following steps are performed: 1. Lexical analysis; 2. Generating an element tree; 3. Element processing: rendering and editing; 4. Event handling.
[0114] In this embodiment, when the collaborative editing command is to insert a template, a preset template is displayed for the user to select, thereby facilitating collaborative editing and improving the user experience.
[0115] Reference Figure 5 , Figure 5 This is a flowchart illustrating the fourth embodiment of the collaborative editing method of the present invention, based on the above. Figure 2The first embodiment shown presents a fourth embodiment of the collaborative editing method of the present invention.
[0116] In the fourth embodiment, step S30 includes:
[0117] Step S301": Upon receiving a member collaboration instruction, determine the collaboration members and pending tasks based on the member collaboration instruction.
[0118] It should be understood that, in order to promptly notify collaborating members of pending tasks, in this embodiment, upon receiving a member's collaboration instruction, the collaborating member and the pending task are determined based on the member's collaboration instruction, and when saving the collaborative document, the pending task is sent to the cloud client corresponding to the collaborating member.
[0119] In practice, users can @specified collaborators within the collaboration file to notify them of pending tasks.
[0120] Step S302": When saving the collaborative document, the to-do items are sent to the cloud client corresponding to the collaborative member.
[0121] Furthermore, in order to avoid the problem of duplicate message notifications, step S302" includes: when saving the collaborative document, obtaining the notification tag corresponding to the to-do item; verifying whether the to-do item has been sent to the cloud client corresponding to the collaborative member based on the notification tag; if not, sending the to-do item to the cloud client corresponding to the collaborative member.
[0122] For ease of understanding, the following example illustrates the concept but does not limit the scope of the invention. In one example, inviting members to collaborate within a cloud drive involves accessing a document and using shortcuts to mention members (@). When the file is saved, the file data is queried to find the mentioned members. Upon saving, the server is informed of the list of members mentioned in the @ notification. After completion, a message is sent to the members within the cloud drive. To avoid duplicate message notifications, the document is marked upon opening. The mark made by the member when mentioning them verifies the conditions, and then the message is sent.
[0123] In this embodiment, upon receiving a member collaboration instruction, the collaborating members and pending tasks are determined based on the instruction. When saving the collaborative document, the pending tasks are sent to the cloud client corresponding to the collaborating member, thereby enabling timely notification of pending tasks to the collaborating member and improving the user experience.
[0124] Reference Figure 6 , Figure 6 This is a flowchart illustrating the fifth embodiment of the collaborative editing method of the present invention. Based on the above embodiments, the fifth embodiment of the collaborative editing method of the present invention is proposed.
[0125] In the fifth embodiment, step S10 includes:
[0126] Step S101: Upon receiving a collaborative editing request, authenticate the collaborative editing request.
[0127] It should be understood that, in order to solve the problem of user login security and improve the security of collaborative documents, in this embodiment, when a collaborative editing request is received, the collaborative editing request is authenticated. After the authentication is successful, the collaborative document is retrieved from the cloud storage space corresponding to the cloud server according to the collaborative editing request.
[0128] It is understood that authenticating collaborative editing requests can involve obtaining the current user identifier from the collaborative editing request, matching the current user identifier with the authorized user identifier corresponding to the collaborative document, and authenticating the collaborative editing request based on the matching result. Here, the identifier can be a token, and the authorized user identifier includes, but is not limited to, the creator user identifier and the collaborating user identifier. The authorized user identifier can be entered by the creator user, or it can be automatically entered by the cloud client when the creator user specifies the collaborating user. This embodiment does not impose any restrictions on this.
[0129] Step S102: After authentication is successful, retrieve the collaborative document from the cloud storage space corresponding to the cloud server according to the collaborative editing request.
[0130] It should be understood that successful authentication indicates the user initiating the collaborative editing request has the right to access the collaborative document. Therefore, the collaborative document can be retrieved from the corresponding cloud storage space on the cloud server based on the collaborative editing request.
[0131] In this embodiment, upon receiving a collaborative editing request, the request is authenticated. After successful authentication, the collaborative document is retrieved from the cloud storage space corresponding to the cloud server, thereby resolving the user's secure login issue and improving the security of the collaborative document.
[0132] In the fifth embodiment, step S20 includes:
[0133] Step S201: Obtain the collaboration status information of the collaborative document.
[0134] It should be understood that, in order to help users understand the current status of collaborative documents when they view them, this embodiment displays the collaborative document and its collaborative status information at the same time.
[0135] It should be noted that the collaboration status information includes, but is not limited to, the number of people currently viewing the content, the number of people currently editing the content, the information of the person currently editing the content, and the editing status information. This embodiment does not impose any restrictions on this.
[0136] Step S202: Display the collaborative document and simultaneously display the collaborative status information.
[0137] It is understood that displaying a collaborative document and simultaneously displaying collaboration status information could mean displaying the collaborative document and showing the collaboration status information in the corresponding prompt area of the collaborative document. For example, displaying the collaboration status information on the right side of the online editing interface of the collaborative document; this embodiment does not limit this to that.
[0138] This embodiment displays the collaborative document and its collaboration status information simultaneously, making it easy for users to understand the current status of the collaborative document when they view it.
[0139] In the fifth embodiment, step S30 includes:
[0140] Step S301: Parse the collaborative editing instructions using a rich text editor to obtain rich text elements.
[0141] It should be understood that, to facilitate user editing of collaborative documents, a rich text editor can also be provided for user operation. Accordingly, in this embodiment, the collaborative editing instructions are parsed through a rich text editor. The rich text editor allows users to easily apply text formatting, such as bold, italics, underline, font color, font size, etc., to improve the readability and visual appeal of the document. The rich text editor also allows users to create hyperlinks to other web pages, documents, or resources to provide more information or guide users. The rich text editor also supports multi-device compatibility, allowing users to seamlessly edit text content on desktops, tablets, and mobile devices, improving user convenience and satisfaction.
[0142] Step S302: Collaboratively edit the collaborative document based on the rich text elements.
[0143] It is understood that rich text elements include, but are not limited to, elements such as paragraphs, headings, images, links, and styles. This embodiment does not limit these elements. Collaborative editing of a collaborative document based on rich text elements can mean editing the content of the collaborative document based on the rich text elements.
[0144] For ease of understanding, please refer to Figure 7 This explanation does not limit the scope of this solution. Figure 7 This is a schematic diagram of the collaborative document functional structure of an embodiment of the collaborative editing method of the present invention. In the figure, the basic rich text editing function corresponds to steps S301 to S302, the cloud disk file management function corresponds to steps S301' to S304', the file template function corresponds to steps S301" to S303", and the task notification function corresponds to steps S301"' to S302"'.
[0145] This embodiment uses a rich text editor to parse the document creation information and uses the rich text elements obtained from the parsing to collaboratively edit the collaborative document, thereby making it easier for users to edit the collaborative document and improving the user experience.
[0146] In the fifth embodiment, after step S30, the method further includes:
[0147] Step S40: After collaborative editing is completed, update the collaborative document in real time, and / or send an update reminder message and update operation entry to the user currently viewing the collaborative document.
[0148] It should be understood that, in order to update the latest version in a timely manner or to notify the user currently viewing the collaborative document in a timely manner after the collaborative editing is completed, in this embodiment, the collaborative document is updated in real time after the collaborative editing is completed, and / or, update reminder information and update operation entry are sent to the user currently viewing the collaborative document. Here, sending update reminder information is to remind the user currently viewing the collaborative document, and sending update operation entry is to provide the user with an update method when the user wants to update to the latest version.
[0149] It should be noted that collaborative editing ends specifically after the current editing user clicks the save button.
[0150] In this embodiment, after collaborative editing is completed, the collaborative document is updated in real time, and / or, update reminders and update operation entry points are sent to the user currently viewing the collaborative document, thereby enabling timely updates to the latest version or timely notification to the user currently viewing the collaborative document.
[0151] In addition, refer to Figure 8 Furthermore, this invention also proposes a collaborative editing device.
[0152] It should be understood that in modern internet applications, more and more people use browsers to access and use applications. Therefore, there is an urgent need for a way to edit and manage text data in the browser. However, browsers themselves do not provide native text editing functions, so users need to download and install traditional text editors. However, traditional text editors cannot be stored in the cloud, thus they have technical problems such as only saving documents locally, not being able to collaborate with multiple users, and not being able to manage files.
[0153] To overcome the above-mentioned shortcomings, this embodiment is applied to the cloud client corresponding to the cloud server. The collaborative document is stored on the cloud server, and the collaborative document is collaboratively edited by accessing the cloud server through the cloud client. This solves the technical problems of the prior art, which only saves documents locally, cannot enable multi-person collaboration, and cannot perform file management. This improves the user experience and ease of operation. The cloud client can be a web client of a cloud application (e.g., cloud storage) on a browser.
[0154] Of course, in addition to the above-described example scenarios, the collaborative editing device of the present invention can also be applied to other scenarios. In other scenarios, the cloud client can be the application client of a cloud application, and this embodiment does not limit this.
[0155] In this embodiment, the collaborative editing device is applied to a cloud client corresponding to a cloud server, and the collaborative editing device includes:
[0156] The document acquisition module 10 is used to acquire collaborative documents from the cloud storage space corresponding to the cloud server when a collaborative editing request is received.
[0157] It should be noted that collaborative editing requests can be initiated manually by the user who created the collaborative document or by the collaborating user, or they can be automatically initiated by the cloud client according to actual needs. This embodiment does not impose any restrictions on this. The user who creates the collaborative document can be the user who creates the collaborative document, and the collaborating user can be specified by the user who creates the collaborative document.
[0158] It should be understood that retrieving a collaborative document from the corresponding cloud storage space on the cloud server based on a collaborative editing request can involve sending the collaborative editing request to the cloud server, the cloud server searching for the corresponding collaborative document in the cloud storage space, and then sending the collaborative document to the cloud client. The collaborative document in the cloud storage space can be uploaded by the cloud client when a user creates the collaborative document, thus achieving cloud storage for the collaborative document. In specific implementations, the collaborative document can be an XMD file.
[0159] Furthermore, to enhance security, the collaborative documents are stored in the cloud storage space in a pre-specified block-level data format.
[0160] It should be understood that many websites and applications in the prior art store document content through HTML nodes, which is vulnerable to malicious code injection or cross-site scripting (XSS) attacks, thus posing security risks. Therefore, to overcome the above-mentioned shortcomings, this embodiment uses pre-specified block-level data instead of HTML nodes for storage to prevent malicious code injection and cross-site scripting attacks, thereby enhancing security.
[0161] Using pre-defined block-level data instead of HTML nodes enhances security because: 1. It prevents HTML injection attacks: If user input is directly embedded in HTML code, attackers may insert malicious tags or code, corrupting the page structure or performing unwanted operations. Separating user-provided data from HTML code effectively reduces the risk of HTML injection attacks. 2. It prevents cross-site scripting (XSS) attacks: Separating user input data from HTML code ensures that user input is not interpreted as code, thus preventing malicious script injection into the webpage. This helps prevent XSS attacks, where attackers attempt to execute malicious scripts in the user's browser.
[0162] Furthermore, to facilitate viewing the content of collaborative documents in the cloud folder list, the collaborative documents are displayed in the cloud folder list in the form of a folder dashboard, so as to preview the content of the collaborative documents in the cloud folder list.
[0163] It should be understood that, in order to facilitate viewing the content of collaborative documents in the cloud folder list, in this embodiment, collaborative documents are displayed in the cloud folder list in the form of a folder dashboard. The folder dashboard form means that when collaborative documents are displayed in the cloud folder list, the content of the collaborative documents can be previewed in the cloud folder list.
[0164] The document display module 20 is used to display the collaborative document.
[0165] It is understood that displaying collaborative documents can specifically refer to displaying an online preview interface or an online editing interface for the collaborative documents, and this embodiment does not limit this.
[0166] Furthermore, to facilitate users' viewing of collaborative documents, the document display module 20 is also used to perform syntactic analysis on the collaborative document to obtain a calibration sequence; generate an element tree based on the calibration sequence, and display the element tree.
[0167] It should be understood that the syntax analysis of the collaborative document to obtain the label sequence can be achieved by using a lexical analyzer to segment the text content of the collaborative document into a list of file elements, such as text paragraphs, headings, images, links, styles, etc., to obtain the label sequence.
[0168] Understandably, an element tree can be constructed using the calibration sequence. Once the element tree is constructed, it is displayed to the user, who can then perform collaborative editing operations such as adding, deleting, and viewing the text content of the collaborative document.
[0169] The collaborative editing module 30 is used to collaboratively edit the collaborative document according to collaborative editing instructions, which are operation instructions based on feedback from the collaborative document.
[0170] It should be understood that collaborative documents provide a text editor for users to operate. After viewing the collaborative document, users can initiate collaborative editing commands through the text editor. The cloud client will then collaboratively edit the collaborative document according to the collaborative editing commands. These collaborative editing commands include, but are not limited to, operations such as adding, deleting, and viewing.
[0171] Of course, to facilitate user editing of collaborative documents, this embodiment can also provide a rich text editor for users to operate.
[0172] It is understandable that when users collaboratively edit a document, the cloud client will automatically save the document (saving every 5 minutes). Of course, users can also manually save and publish to complete the file editing, and this embodiment does not restrict this.
[0173] In this embodiment, upon receiving a collaborative editing request, the system retrieves the collaborative document from the cloud storage space corresponding to the cloud server, displays the collaborative document, receives collaborative editing instructions based on the collaborative document, and performs collaborative editing on the collaborative document according to the instructions. Since this embodiment is applied to the cloud client corresponding to the cloud server, the collaborative document is stored on the cloud server, and the collaborative document is collaboratively edited by accessing the cloud server through the cloud client. This solves the technical problems of existing technologies that only save documents locally, cannot support multi-person collaboration, and cannot perform file management, thereby improving user experience and ease of operation.
[0174] Other embodiments or specific implementations of the collaborative editing device described in this invention can be found in the above-described method embodiments, and will not be repeated here.
[0175] Furthermore, this embodiment of the invention also proposes a storage medium storing a collaborative editing program, which, when executed by a processor, implements the collaborative editing method described above.
[0176] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.
[0177] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.
[0178] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as a read-only memory image (ROM) / random access memory (RAM), magnetic disk, optical disk), and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present invention.
[0179] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.
[0180] This invention discloses A1, a collaborative editing method, which is applied to a cloud client corresponding to a cloud server. The collaborative editing method includes:
[0181] Upon receiving a collaborative editing request, the collaborative document is retrieved from the cloud storage space corresponding to the cloud server according to the collaborative editing request;
[0182] Display the collaborative document;
[0183] The collaborative document is collaboratively edited according to the collaborative editing instructions, which are operation instructions based on feedback from the collaborative document.
[0184] A2. The collaborative editing method as described in A1, wherein the collaborative editing of the collaborative document according to the collaborative editing instructions includes:
[0185] When the collaborative editing command is to insert a cloud file, verify the permissions of the user who entered the collaborative editing command;
[0186] The cloud files are filtered based on the verification results, and the filtered cloud files are displayed.
[0187] Receive cloud file selection instructions based on the cloud files after filtering;
[0188] According to the cloud file selection instruction, a target cloud file is selected from the filtered cloud files and inserted into the collaborative document.
[0189] A3. The collaborative editing method as described in A1, wherein the collaborative editing of the collaborative document according to the collaborative editing instructions includes:
[0190] When the collaborative editing command is to insert a template, a recommended template will be displayed;
[0191] Receive template selection instructions based on the recommended template;
[0192] According to the template selection instruction, a target template is selected from the recommended templates and inserted into the collaborative document.
[0193] A4. The collaborative editing method as described in A1, wherein the collaborative editing of the collaborative document according to the collaborative editing instructions includes:
[0194] Upon receiving a member collaboration instruction, the collaboration members and pending tasks are determined based on the member collaboration instruction;
[0195] When the collaborative document is saved, the to-do items are sent to the cloud clients corresponding to the collaborative members.
[0196] A5. The collaborative editing method as described in A4, wherein when saving the collaborative document, sending the to-do items to the cloud client corresponding to the collaborative member includes:
[0197] When saving the collaborative document, obtain the notification tag corresponding to the to-do item;
[0198] Verify whether the to-do item has been sent to the cloud client corresponding to the collaborating member based on the notification tag;
[0199] If not, the to-do item will be sent to the cloud client corresponding to the collaborating member.
[0200] A6. The collaborative editing method as described in any one of A1 to A5, wherein upon receiving a collaborative editing request, retrieving the collaborative document from the cloud storage space corresponding to the cloud server according to the collaborative editing request includes:
[0201] Upon receiving a collaborative editing request, the collaborative editing request is authenticated.
[0202] After successful authentication, the collaborative document is retrieved from the cloud storage space corresponding to the cloud server according to the collaborative editing request.
[0203] A7. The collaborative editing method as described in any one of A1 to A5, wherein the collaborative editing of the collaborative document according to the collaborative editing instructions includes:
[0204] The collaborative editing instructions are parsed using a rich text editor to obtain rich text elements;
[0205] Collaborative editing of the collaborative document based on the rich text elements.
[0206] A8. The collaborative editing method as described in any one of A1 to A5, wherein the collaborative document is stored in the cloud storage space in a pre-specified block-level data format.
[0207] A9. The collaborative editing method as described in any one of A1 to A5, wherein displaying the collaborative document includes:
[0208] Perform syntactic analysis on the collaborative document to obtain the calibration sequence;
[0209] Generate an element tree based on the calibration sequence, and display the element tree.
[0210] A10. The collaborative editing method as described in any one of A1 to A5, wherein displaying the collaborative document includes:
[0211] Obtain the collaboration status information of the collaborative document;
[0212] Display the collaborative document and simultaneously display the collaboration status information.
[0213] A11. The collaborative editing method as described in any one of A1 to A5, wherein after collaboratively editing the collaborative document according to collaborative editing instructions, the collaborative editing instructions being operation instructions based on feedback from the collaborative document, further includes:
[0214] The collaborative document is updated in real time after collaborative editing is completed;
[0215] And / or, send update notifications and update access points to the user currently viewing the collaborative document.
[0216] A12. The collaborative editing method as described in any one of A1 to A5, wherein the collaborative document is displayed in a cloud folder list in the form of a folder dashboard, so as to preview the content of the collaborative document in the cloud folder list.
[0217] The present invention also discloses B13, a collaborative editing device, wherein the collaborative editing device is applied to a cloud client corresponding to a cloud server, and the collaborative editing device includes:
[0218] The document retrieval module is used to retrieve the collaborative document from the cloud storage space corresponding to the cloud server when a collaborative editing request is received.
[0219] The document display module is used to display the collaborative documents;
[0220] The collaborative editing module is used to collaboratively edit the collaborative document according to collaborative editing instructions, which are operation instructions based on feedback from the collaborative document.
[0221] B14. In the collaborative editing device described in B13, the collaborative editing module is further configured to: verify the user's permissions when the collaborative editing instruction is to insert a cloud file; filter the cloud files according to the verification result and display the filtered cloud files; receive a cloud file selection instruction based on the filtered cloud files; and select a target cloud file from the filtered cloud files and insert it into the collaborative document according to the cloud file selection instruction.
[0222] B15. The collaborative editing device as described in B13, wherein the collaborative editing module is further configured to: display recommended templates when the collaborative editing instruction is to insert a template; receive a template selection instruction based on the recommended templates; and select a target template from the recommended templates and insert it into the collaborative document according to the template selection instruction.
[0223] B16. The collaborative editing device as described in B13, further comprising:
[0224] The member collaboration module is used to determine the collaborating members and to-do items based on the member collaboration instruction when a member collaboration instruction is received; and to send the to-do items to the cloud client corresponding to the collaborating member when the collaborative document is saved.
[0225] B17. In the collaborative editing device as described in B16, the member collaboration module is further configured to, when saving the collaborative document, obtain a notification tag corresponding to the to-do item; verify whether the to-do item has been sent to the cloud client corresponding to the collaborative member based on the notification tag; if not, send the to-do item to the cloud client corresponding to the collaborative member.
[0226] B18. The collaborative editing apparatus as described in any one of B13 to B17, wherein the document acquisition module is further configured to authenticate the collaborative editing request upon receiving it; and, after successful authentication, acquire the collaborative document from the cloud storage space corresponding to the cloud server according to the collaborative editing request.
[0227] The present invention also discloses C19, a collaborative editing device, the collaborative editing device comprising: a memory, a processor, and a collaborative editing program stored in the memory and executable on the processor, wherein the collaborative editing program, when executed by the processor, implements the collaborative editing method as described above.
[0228] The present invention also discloses D20 and a storage medium storing a collaborative editing program, which, when executed by a processor, implements the collaborative editing method described above.
Claims
1. A collaborative editing method, characterized in that, The collaborative editing method is applied to the cloud client corresponding to the cloud server. The collaborative editing method includes: Upon receiving a collaborative editing request, the collaborative document is retrieved from the cloud storage space corresponding to the cloud server according to the collaborative editing request; Display the collaborative document; The collaborative document is collaboratively edited according to the collaborative editing instructions, which are operation instructions based on feedback from the collaborative document.
2. The collaborative editing method as described in claim 1, characterized in that, The step of collaboratively editing the collaborative document according to collaborative editing instructions includes: When the collaborative editing command is to insert a cloud file, verify the permissions of the user who entered the collaborative editing command; The cloud files are filtered based on the verification results, and the filtered cloud files are displayed. Receive cloud file selection instructions based on the cloud files after filtering; According to the cloud file selection instructions, the target cloud file is selected from the filtered cloud files and inserted into the collaborative document.
3. The collaborative editing method as described in claim 1, characterized in that, The step of collaboratively editing the collaborative document according to collaborative editing instructions includes: When the collaborative editing command is to insert a template, a recommended template will be displayed; Receive template selection instructions based on the recommended template; The target template is selected from the recommended templates and inserted into the collaborative document according to the template selection instructions.
4. The collaborative editing method as described in claim 1, characterized in that, The step of collaboratively editing the collaborative document according to collaborative editing instructions includes: Upon receiving a member collaboration instruction, the collaboration members and pending tasks are determined based on the member collaboration instruction; When the collaborative document is saved, the to-do items are sent to the cloud client corresponding to the collaborative member.
5. The collaborative editing method as described in claim 4, characterized in that, The step of sending the to-do items to the cloud clients corresponding to the collaborating members when saving the collaborative document includes: When saving the collaborative document, obtain the notification tag corresponding to the to-do item; Verify whether the to-do item has been sent to the cloud client corresponding to the collaborating member based on the notification tag; If not, the to-do item will be sent to the cloud client corresponding to the collaborating member.
6. The collaborative editing method as described in any one of claims 1 to 5, characterized in that, Upon receiving a collaborative editing request, retrieving the collaborative document from the corresponding cloud storage space on the cloud server according to the collaborative editing request includes: Upon receiving a collaborative editing request, the collaborative editing request is authenticated. After authentication is successful, the collaborative document is retrieved from the cloud storage space corresponding to the cloud server according to the collaborative editing request.
7. The collaborative editing method as described in any one of claims 1 to 5, characterized in that, The step of collaboratively editing the collaborative document according to collaborative editing instructions includes: The collaborative editing instructions are parsed using a rich text editor to obtain rich text elements; Collaborative editing of the collaborative document is performed based on the rich text elements.
8. A collaborative editing device, characterized in that, The collaborative editing device is applied to a cloud client corresponding to the cloud server. The collaborative editing device includes: The document retrieval module is used to retrieve the collaborative document from the cloud storage space corresponding to the cloud server when a collaborative editing request is received. The document display module is used to display the collaborative documents; The collaborative editing module is used to collaboratively edit the collaborative document according to collaborative editing instructions, which are operation instructions based on feedback from the collaborative document.
9. A collaborative editing device, characterized in that, The collaborative editing device includes: a memory, a processor, and a collaborative editing program stored in the memory and executable on the processor, wherein the collaborative editing program, when executed by the processor, implements the collaborative editing method as described in any one of claims 1 to 7.
10. A storage medium, characterized in that, The storage medium stores a collaborative editing program, which, when executed by a processor, implements the collaborative editing method as described in any one of claims 1 to 7.