WO2017113317A1 - Procédé d'édition de fichier et éditeur de fichier - Google Patents

Procédé d'édition de fichier et éditeur de fichier Download PDF

Info

Publication number
WO2017113317A1
WO2017113317A1 PCT/CN2015/100168 CN2015100168W WO2017113317A1 WO 2017113317 A1 WO2017113317 A1 WO 2017113317A1 CN 2015100168 W CN2015100168 W CN 2015100168W WO 2017113317 A1 WO2017113317 A1 WO 2017113317A1
Authority
WO
WIPO (PCT)
Prior art keywords
file
data unit
editor
basic data
block
Prior art date
Application number
PCT/CN2015/100168
Other languages
English (en)
Chinese (zh)
Inventor
裴廷斌
Original Assignee
深圳配天智能技术研究院有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 深圳配天智能技术研究院有限公司 filed Critical 深圳配天智能技术研究院有限公司
Priority to PCT/CN2015/100168 priority Critical patent/WO2017113317A1/fr
Priority to CN201580080837.4A priority patent/CN107924397B/zh
Publication of WO2017113317A1 publication Critical patent/WO2017113317A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor

Definitions

  • the embodiment of the present application relates to the field of file processing, and in particular, to a file editing method and a file editor.
  • Editing the contents of a file by the file editor needs to be based on loading the contents of the file into memory.
  • the file editor needs to load all the contents of the file into the memory first.
  • the file editor records the modified file content and the position of the modified file in the file to generate the basic data unit. Then, the content of the file that has been loaded into the memory can be restored and undone according to the basic data unit.
  • An aspect of the embodiments of the present invention provides a file editing method, including:
  • the file editor performs target modification on the first file block of the processed file, and records the target modified information and the position information of the first file block to obtain the target basic data unit, and the target modified information includes the target modified content and the target modified content. Location information in the first file block;
  • the file editor stores the target basic data unit in the data link table behind the first basic data unit pointed to by the current modification identifier, and points the current modification identifier to the target basic data unit;
  • the file editor receives a resume or undo instruction
  • the file editor determines, according to the current modification identifier, that the basic data unit corresponding to the recovery or revocation instruction is the target basic data unit;
  • the file editor reads the first file block from the external memory according to the location information of the first file block;
  • the file editor restores or revokes the first file block based on the information modified by the target.
  • the file editor receives the save instruction; the file editor saves the first file block and points the save modification identifier to the second base
  • the basic data unit, the second basic data unit is the basic data unit pointed to by the current modification identifier.
  • the file editor processes the first file in an order from the start point to the end point of the target base data unit segment of the data link table.
  • the block is restored or revoked, and the starting point of the basic data unit segment is the second basic data unit pointed to by the save modification identifier, and the end point of the basic data unit segment is the third basic data unit pointed to by the current modification identifier.
  • the first The location information of the file block includes at least two of a start position of the first file block in the full text of the file, an end position, and a length of the first file block.
  • the location information of the first file block is a storage location of the first file block in the external memory.
  • the file editor receives the save instruction; the location of the first file block in the target base data unit by the file editor The information is updated.
  • the file editor deletes the first file block from the memory and from the external memory.
  • the second file block in which the file to be processed is read and displayed.
  • the file editor is The location information of the first file block stores the first file block.
  • the file editor determines whether the second file block and the first file block are the same file. Piece;
  • the file editor directs the current modification identifier to the target base data unit.
  • the file editor directs the current modification identifier to the first base data unit.
  • the first possible implementation of the first aspect, the second possible implementation of the first aspect, the third possible implementation of the first aspect, the fourth possible aspect of the first aspect The implementation manner, the fifth possible implementation manner of the first aspect, the sixth possible implementation manner of the first aspect, the seventh possible implementation manner of the first aspect, and the eighth possible implementation manner of the first aspect Any one of the ninth possible implementation of the first aspect and the tenth possible implementation of the first aspect.
  • the target modification includes Deleted file content and/or added file content.
  • a second aspect of the embodiments of the present invention provides a file editor, including:
  • a recording module configured to record the information of the target modification and the location information of the first file block to obtain the target basic data unit, where the target modified information includes the content of the target modification and the location information of the content of the target modification in the first file block;
  • a first storage module configured to store the target basic data unit behind the first basic data unit pointed to by the current modification identifier in the data link table
  • a first pointing module configured to point the current modified identifier to the target basic data unit
  • a first receiving module configured to receive a resume or revocation instruction
  • a determining module configured to determine, according to the current modification identifier, that the basic data unit corresponding to the recovery or revocation instruction is the target basic data unit;
  • a first reading module configured to read the first file block from the external memory according to the location information of the first file block
  • a first recovery module configured to recover the first file block according to the information modified by the target
  • the first undo module is configured to cancel the first file block according to the information modified by the target.
  • the file editor further includes:
  • a second receiving module configured to receive a save instruction
  • the second pointing module is configured to point the save modification identifier to the second basic data unit, where the second basic data unit is the basic data unit pointed to by the current modification identifier.
  • the file editor further includes:
  • a second recovery module configured to recover the first file block in an order from a start point to an end point of the target basic data unit segment of the data link table
  • a second revocation module configured to revoke the first file block in an order from a start point to an end point of the target basic data unit segment of the data link table
  • the starting point of the basic data unit segment is the second basic data unit pointed to by the save modification identifier, and the end point of the basic data unit segment is the third basic data unit pointed to by the current modification identifier.
  • the first possible implementation manner of the second aspect, and the second possible implementation manner of the second aspect in a third possible implementation manner of the second aspect, the first The location information of the file block includes at least two of a start position of the first file block in the full text of the file, an end position, and a length of the first file block.
  • the location information of the first file block is a storage location of the first file block in the external memory.
  • the file editor further includes:
  • a third receiving module configured to receive a save instruction
  • an update module configured to update location information of the first file block in the target basic data unit.
  • the file editor further includes:
  • a second reading module configured to read a second file block of the file to be processed from the external memory
  • a display module for displaying a second file block of the file to be processed.
  • the file editor further includes a second storage module, configured to perform, according to the location information of the first file block, the first File blocks are stored.
  • the file editor further includes:
  • a determining module configured to determine whether the second file block and the first file block are the same file block
  • a first triggering module configured to: when the second file block and the first file block are the same file block, trigger an operation of restoring or revoking the first file block according to the information modified by the target;
  • the second triggering module is configured to trigger an operation of reading the first file block from the external memory according to the location information of the first file block when the second file block and the first file block are not the same file block.
  • the file editor further includes a third pointing module, configured to point the current modified identifier to the target basic data unit.
  • the file editor further includes a fourth pointing module, configured to point the current modified identifier to An underlying data unit.
  • the file editor performs editing on the file based on the file content being loaded into the memory, and the file editor only reads and displays one file block at a time.
  • the file block can be read and restored or undone by the file block location information in the underlying data unit. Since the file editor restores or undoes the contents of the file, it is not necessary to load all the contents of the file into memory, thereby avoiding affecting system performance.
  • FIG. 1 is a schematic diagram of an embodiment of a file editing method of the present invention
  • FIG. 2 is a schematic diagram of another embodiment of a file editing method of the present invention.
  • FIG. 3 is a schematic diagram of another embodiment of a file editing method of the present invention.
  • FIG. 4 is a schematic diagram of an embodiment of a file editor of the present invention.
  • Figure 5 is a schematic view of another embodiment of the file editor of the present invention.
  • Figure 6 is a schematic illustration of another embodiment of the file editor of the present invention.
  • the embodiment of the invention provides a file editing method, which is used for restoring or revoking the file content, and does not need to load all the file contents into the memory, thereby avoiding affecting system performance.
  • an embodiment of the file editing method in the embodiment of the present invention includes:
  • the file editor performs a target modification on the first file block of the processed file
  • the file editor reads and displays the first file block of the file to be processed from the external memory, and then the target file block can be modified.
  • the file editor records the target modified information and the location information of the first file block to obtain the target basic data unit.
  • Each base data unit represents an undo/redo operation step and is the smallest unit of execution for the undo/redo operation.
  • the file editor stores the target basic data unit after the first basic data unit in the data link table, where the first basic data unit is a basic data unit pointed to by the current modification identifier;
  • the recovery or undo operation information recorded in the basic data unit is uniformly included in the basic data unit data link table.
  • the data link table refers to the basic data unit data link table.
  • the file editor points the current modification identifier to the target basic data unit
  • the file editor After the file editor stores the target base data unit in the data link table, the file editor points the current modification identifier to the target base data unit, indicating that the target base data unit represents the current modification status of the file to be processed.
  • the file editor receives a resume or revocation instruction
  • the file editor can receive recovery or undo instructions after modifying the file to be processed.
  • the file editor determines, according to the current modification identifier, that the basic data unit corresponding to the recovery or revocation instruction is the target basic data unit;
  • the file editor may determine, in the data link table, the basic data unit corresponding to the recovery or revocation instruction as the target basic data unit according to the basic data unit pointed to by the current modification identifier.
  • the file editor reads the first file block from the external memory according to the location information of the first file block.
  • the file editor reads the target basic data unit, acquires location information of the first file block, and reads the first file block from the external memory according to the location information of the first file block.
  • the file editor restores or revokes the first file block according to the information modified by the target.
  • the first file block After the file editor reads the first file block, the first file block can be restored or revoked according to the information modified by the target in the target basic data unit.
  • the modified file block may be automatically saved to the external memory, or may be saved to the save command when the save command is received.
  • the external memory the following are explained separately:
  • the file editor saves the modified file block to the external memory when receiving the save instruction:
  • Another embodiment of the file editing method of the present invention includes:
  • the file editor receives the save instruction.
  • the file editor After the user modifies the first file block of the file to be processed by the file editor, the file editor records the modified information and the location information of the first file block, generates and stores the second basic data unit in the data link table, and The current modification identifier points to the second base data unit. If the user needs to save the file content of the first file block to the external memory, the user can input a save instruction to the file editor, and the file editor can receive the save instruction input by the user.
  • the file editor saves the first file block.
  • the first file block may be saved, and the file content changed by the first file block is saved to the external memory.
  • the file editor points the save modification identifier to the second basic data unit.
  • the file editor may point the save modification identifier to the second basic data unit, where the second basic data unit is the basic data unit pointed to by the current modification identifier.
  • This step may be performed before step 202, or may be performed after step 202, and may also be performed simultaneously with step 202, which is not specifically limited herein.
  • the base data unit contains the modified information and the location information of the modified file block.
  • the location information of the file block may include at least two of a start position, a termination position, and a length of the file block of the file block in the full text of the file.
  • the starting position of the file block in the full text of the file can be the offset generated by the file pointer moving from the beginning position of the file to the beginning position of the file block.
  • the end position of the file block in the full text of the file can be the file pointer from the file.
  • the offset from the start position of the file block to the end position of the file block may also be used to indicate the start and end positions of the file block in the full text of the file, which is not specifically limited herein.
  • the file editor When the file editor receives the save instruction, the file editor will write the modification to the modified file before receiving the save instruction to the file to be modified in the external memory, which may result in the start position and the end position of the file block in the full text of the file. And the length of the file block changes, so the location information of the file block of the underlying data unit in the data link table needs to be updated.
  • the location information of the file block includes the starting position and the ending position of the file block in the full text of the file, and the basic data unit in the data link table may be corrected one by one from the beginning of the chain.
  • the specific method may be:
  • the basic data unit currently being corrected is Ix, wherein the starting position and the ending position of the recorded file block are respectively recorded as P 1 and P 2 , and the data link table is traversed to determine the basic data of all the recorded modified positions before P 1 .
  • the elements, such as I 1 , I 2 , I 3 , and I 4 are modified to produce a character offset of ⁇ 1 , ⁇ 2 , ⁇ 3 , and ⁇ 4 , respectively .
  • the character offset ⁇ caused by the modification is -3 characters.
  • Adding ⁇ 1 , ⁇ 2 , ⁇ 3 , ⁇ 4 , and P 1 yields I 1 corrected P 1 .
  • the method of correcting P 2 of Ix is similar to the above method of correcting P 1 and will not be described herein.
  • the location information of the file block of the basic data unit in the data link table may be updated by other methods, which are not specifically limited herein.
  • the file block may be distributedly stored in different external memory areas, for example, the first file block may be stored.
  • the first storage area is large enough to store the modified first file block
  • the location information of the first file block is the first storage area.
  • file blocks can also be stored in other ways. As long as you can avoid saving the impact of the modification on the location of the file block. It can be seen that in this case, the file editor does not need to update the location information of the file block in the underlying data unit when receiving the save instruction.
  • Steps 204 to 207 in this embodiment are the same as steps 101 to 104 in the embodiment shown in FIG. 1, and details are not described herein again.
  • the file editor reads the second file block from the external memory.
  • the file editor reads the second file block from the external memory.
  • the file editor deletes the first file block from the memory
  • the file editor can delete the first file block from the memory to load the second file block into the file editor. It should be noted that the execution order of the steps 208 and 209 can be interchanged, that is, the file editor first deletes the first file block from the memory, and then reads the second file block from the external memory, which is not specifically limited herein.
  • the file editor displays a second file block of the file to be processed.
  • the second file block of the file to be processed can be displayed to the user.
  • Steps 208 to 210 are used to describe the case where the file block corresponding to the recovery or undo operation is not the currently displayed file block when the file editor receives the recovery or revocation instruction. In actual use, steps 208 to 210 may also be used. Does not occur, that is, the file block corresponding to the recovery or undo operation is the currently displayed file block.
  • the file editor receives a resume or revocation instruction
  • the user can input a recovery instruction to the file editor to restore the previously revoked modification operation, the file editor can receive the recovery instruction, and the user can also input a revocation instruction to the file editor to cancel the previous modification operation, the file editor. Can receive an undo command.
  • the file editor determines, according to the current modification identifier, that the basic data unit corresponding to the recovery or revocation instruction is the target basic data unit;
  • the file editor determines the basic data unit pointed to by the current modification identifier. If the current modification identifier points to the first basic data unit, the file editor may determine the corresponding recovery instruction in the data link table.
  • the underlying data unit is the target underlying data unit.
  • the file editor will determine what the current modification identifier points to.
  • the basic data unit if the current modification identifier points to the target basic data unit, the file editor may determine, in the data link table, that the basic data unit corresponding to the revocation instruction is the target basic data unit.
  • Step 213 in this embodiment is the same as step 107 in the embodiment shown in FIG. 1, and details are not described herein again.
  • the file editor restores or revokes the first file block according to an order from a start point to an end point of the target basic data unit segment of the data link table.
  • the file editor restores the first file block according to the order from the start point to the end point of the target data unit segment of the data link table, and obtains the first file block in the current modified state, and the starting point of the basic data unit segment is pointed to by the save modification identifier.
  • the second basic data unit, the end point of the basic data unit segment is the third basic data unit pointed to by the current modification identifier. If the file editor receives the resume instruction, the third base data unit is the first base data unit, and if the undo command is received, the third base data unit is the target base data unit.
  • Steps 201 to 203 mainly explain the specific operations performed by the file editor when receiving the save instruction.
  • steps 201 to 203 may not occur, and even the file editor may not receive the save instruction before receiving the resume instruction.
  • the file editor restores the first file block in the order from the beginning of the data link table to the third basic data unit pointed to by the current modification identifier.
  • the save modification identifier may point to the basic data unit behind the first basic data unit in the data link table, and then the file editor undoes the first file block in the order from the start point to the end point of the target base data unit segment of the data link table.
  • steps 213 and 214 may not be performed.
  • the file editor restores or revokes the first file block according to the information modified by the target.
  • the converted first file block After the file editor converts the read first file block from the modified state at the time of the last save to the current modified state, the converted first file block can be restored or revoked according to the information modified by the target.
  • the file editor may point the current modification identifier to the target basic data unit.
  • the file editor may point the current modification identifier to the first basic data unit.
  • the modified first file block may be automatically saved to the external memory to back up the first file block in the current modified state.
  • FIG. 3 another embodiment of the file editing method of the present invention includes:
  • Steps 301 to 304 in this embodiment are the same as steps 101 to 104 in the embodiment shown in FIG. 1, and details are not described herein again.
  • the file editor saves the first file block that has been modified by the target to the external storage.
  • the modified first file block can be saved to the external memory. Saving the modified first file block to the external memory, by writing the entire file block to the external memory and deleting the original file block, or by writing the modified content to the original file block in the external memory, Other methods, as long as the first file block saved in the external memory can be updated to the current modified state.
  • the timing between step 305 and step 302 to step 304 is not specifically limited, as long as the file editor has the first modified state before the first file block is deleted from the memory.
  • the file block can be saved to the external memory.
  • the steps 306 to 311 in the embodiment are the same as the steps 208 to 213 in the embodiment shown in FIG. 2, and the step 312 in this embodiment is the same as the step 215 in the embodiment shown in FIG. Narration.
  • an embodiment of the file editor 400 in the embodiment of the present invention includes:
  • the modifying module 401 is configured to perform target modification on the first file block of the file to be processed
  • the recording module 402 is configured to record the target modified information and the location information of the first file block to obtain the target basic data unit, where the target modified information includes the target modified content and the location information of the target modified content in the first file block;
  • a first storage module 403 configured to store the target basic data unit after the first basic data unit in the data link table, where the first basic data unit is a basic data unit pointed to by the current modification identifier;
  • a first pointing module 404 configured to point the current modification identifier to the target basic data unit
  • a first receiving module 405, configured to receive a resume or revocation instruction
  • a determining module 406 configured to determine, according to the current modification identifier, a base number corresponding to the recovery or revocation instruction According to the unit as the target data unit;
  • the first reading module 407 is configured to read the first file block from the external memory according to the location information of the first file block;
  • the first recovery module 408 is configured to recover the first file block according to the information modified by the target;
  • the first revocation module 409 is configured to rectify the first file block according to the information modified by the target.
  • the modified file block may be automatically saved to the external memory, or may be saved to the save command when the save command is received.
  • the external memory the following are explained separately:
  • the file editor saves the modified file block to the external memory when receiving the save instruction:
  • the modified file block is saved to the external memory only when the file editor receives the save instruction, as shown in FIG. 5 .
  • Another embodiment of the file editor 500 of the present invention includes:
  • the second receiving module 501 is configured to receive a save instruction.
  • a saving module 502 configured to save the first file block
  • a second pointing module 503, configured to point the save modification identifier to the second basic data unit
  • module 504 in this embodiment and the module 401, the module 505 and the module 402, the module 506 and the module 403, the module 507 and the module 404 in the embodiment shown in FIG. 4 are respectively the same, and are not described herein again.
  • a second reading module 508, configured to read a second file block from the external memory
  • a deleting module 509 configured to delete the first file block from the memory
  • a display module 510 configured to display a second file block of the file to be processed
  • the first receiving module 511 is configured to receive a resume or revocation instruction
  • the determining module 512 is configured to determine, according to the current modification identifier, that the basic data unit corresponding to the recovery or revocation instruction is the target basic data unit;
  • the module 513 in this embodiment performs the same function as the module 407 in the embodiment shown in FIG. 4, and details are not described herein again.
  • a second recovery module 514 configured to follow a starting point from a target base data unit segment of the data linked list The order of the end points restores the first file block;
  • a second revocation module 515 configured to revoke the first file block in an order from a start point to an end point of the target basic data unit segment of the data link table;
  • the first recovery module 516 is configured to recover the first file block according to the information modified by the target;
  • the first revocation module 517 is configured to rectify the first file block according to the information modified by the target.
  • the modified first file block may be automatically saved to the external memory to back up the first file block in the current modified state.
  • the file editor 600 of the present invention includes:
  • Steps 601 to 604 in this embodiment are the same as steps 401 to 404 in the embodiment shown in FIG. 1, and details are not described herein again.
  • a second storage module 605, configured to store the first file block that has been modified by the target into an external memory
  • the module 606 in this embodiment and the module 508 in the embodiment shown in FIG. 5, the module 607 and the module 509, the module 608 and the module 510, the module 609 and the module 511, the module 610 and the module 512, the module 611 and the module 513, the module 612 and module 516, module 613 and module 517 perform the same functions, and are not described herein again.
  • the disclosed system, apparatus, and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of cells is only a logical function division.
  • multiple units or components may be combined or integrated. Go to another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated as a unit
  • the displayed components may or may not be physical units, ie may be located in one place, or may be distributed over multiple network elements. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • An integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, can be stored in a computer readable storage medium.
  • the technical solution of the present invention which is essential or contributes to the prior art, or all or part of the technical solution, may be embodied in the form of a software product stored in a storage medium.
  • a number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the various embodiments of the present invention.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

L'invention concerne un procédé d'édition de fichier et un éditeur de fichier (400, 500 et 600). Le procédé comprend les opérations suivantes : l'éditeur de fichier (400, 500 et 600) réalise une modification cible sur un premier bloc de fichier d'un fichier à traiter (101, 204 et 301), l'éditeur de fichier (400, 500 et 600) enregistre des informations de la modification cible et des informations d'emplacement du premier bloc de fichier (102, 205 et 302) pour produire des unités de données de base cibles ; l'éditeur de fichier (400, 500 et 600) reçoit une instruction de restauration ou de révocation (105, 211 et 309), l'éditeur de fichier (400, 500 et 600) détermine une unité de données de base correspondant à l'instruction de restauration ou de révocation comme étant une unité de données de base cible (106, 212 et 310), l'éditeur de fichier (400, 500 et 600) lit le premier bloc de fichier à partir d'un disque dur sur la base des informations d'emplacement du premier bloc de fichier (107, 213 et 311), et l'éditeur de fichier (400, 500 et 600) soit restaure, soit révoque le premier bloc de fichier sur la base des informations de la modification cible (108, 215 et 312). En raison du fait qu'un chargement en mémoire du contenu entier du fichier n'est plus nécessaire lorsque l'éditeur de fichier (400, 500 et 600) restaure ou révoque le contenu du fichier, un impact sur les performances du système est évité.
PCT/CN2015/100168 2015-12-31 2015-12-31 Procédé d'édition de fichier et éditeur de fichier WO2017113317A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2015/100168 WO2017113317A1 (fr) 2015-12-31 2015-12-31 Procédé d'édition de fichier et éditeur de fichier
CN201580080837.4A CN107924397B (zh) 2015-12-31 2015-12-31 一种文件编辑方法和文件编辑器

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/100168 WO2017113317A1 (fr) 2015-12-31 2015-12-31 Procédé d'édition de fichier et éditeur de fichier

Publications (1)

Publication Number Publication Date
WO2017113317A1 true WO2017113317A1 (fr) 2017-07-06

Family

ID=59224207

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/100168 WO2017113317A1 (fr) 2015-12-31 2015-12-31 Procédé d'édition de fichier et éditeur de fichier

Country Status (2)

Country Link
CN (1) CN107924397B (fr)
WO (1) WO2017113317A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111352909A (zh) * 2019-05-07 2020-06-30 鸿合科技股份有限公司 一种文件保存及加载方法、设备、电子设备及存储介质
CN112416325A (zh) * 2019-08-22 2021-02-26 福建天泉教育科技有限公司 一种Unity中构建ab包的方法及终端
CN113312212A (zh) * 2021-06-02 2021-08-27 广联达科技股份有限公司 保护模型构件参数的方法、装置、设备和可读存储介质

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110389796A (zh) * 2019-07-01 2019-10-29 北京字节跳动网络技术有限公司 编辑操作处理方法、装置及电子设备
CN112363708B (zh) * 2020-12-04 2023-03-10 中信银行股份有限公司 一种支持Eclipse工具下的上下文保护方法及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070204126A1 (en) * 2006-02-24 2007-08-30 Bangalore Kiran K Reclaim algorithm for fast edits in a nonvolatile file system
CN101551793A (zh) * 2008-04-03 2009-10-07 鸿富锦精密工业（深圳）有限公司 文件保存及编辑方法
CN103440181A (zh) * 2013-09-06 2013-12-11 珠海金山网络游戏科技有限公司 一种文件修改的方法及系统
CN104092780A (zh) * 2014-07-29 2014-10-08 中国联合网络通信集团有限公司 基于文件分块的文件修改方法、单文件同步方法及装置
CN104199856A (zh) * 2014-08-13 2014-12-10 北京配天技术有限公司 呈现文件的方法和文件呈现装置

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7464116B2 (en) * 2005-12-28 2008-12-09 Network Appliance, Inc. Method and apparatus for cloning filesystems across computing systems
TWI425375B (zh) * 2010-01-20 2014-02-01 Inventec Corp 伺服器檔案管理之方法
CN101751478A (zh) * 2010-02-20 2010-06-23 浪潮(北京)电子信息产业有限公司 一种文件备份方法及系统
CN102737032B (zh) * 2011-04-06 2016-06-08 腾讯科技（深圳）有限公司 文件恢复的方法及装置
US9411687B2 (en) * 2011-06-03 2016-08-09 Apple Inc. Methods and apparatus for interface in multi-phase restore
JP5831235B2 (ja) * 2012-01-06 2015-12-09 ティアック株式会社 ファイル編集装置
JP5876592B2 (ja) * 2012-04-25 2016-03-02 株式会社日立製作所 ファイルストレージシステムとファイルクローニング方法
US9348840B2 (en) * 2012-12-14 2016-05-24 Intel Corporation Adaptive data striping and replication across multiple storage clouds for high availability and performance
CN103294957B (zh) * 2013-05-06 2015-10-28 北京赛思信安技术有限公司 支持重复数据删除文件系统中数据更新时的数据保护方法
CN104199967A (zh) * 2014-09-22 2014-12-10 广东欧珀移动通信有限公司 一种手机文件的恢复方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070204126A1 (en) * 2006-02-24 2007-08-30 Bangalore Kiran K Reclaim algorithm for fast edits in a nonvolatile file system
CN101551793A (zh) * 2008-04-03 2009-10-07 鸿富锦精密工业（深圳）有限公司 文件保存及编辑方法
CN103440181A (zh) * 2013-09-06 2013-12-11 珠海金山网络游戏科技有限公司 一种文件修改的方法及系统
CN104092780A (zh) * 2014-07-29 2014-10-08 中国联合网络通信集团有限公司 基于文件分块的文件修改方法、单文件同步方法及装置
CN104199856A (zh) * 2014-08-13 2014-12-10 北京配天技术有限公司 呈现文件的方法和文件呈现装置

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111352909A (zh) * 2019-05-07 2020-06-30 鸿合科技股份有限公司 一种文件保存及加载方法、设备、电子设备及存储介质
CN112416325A (zh) * 2019-08-22 2021-02-26 福建天泉教育科技有限公司 一种Unity中构建ab包的方法及终端
CN113312212A (zh) * 2021-06-02 2021-08-27 广联达科技股份有限公司 保护模型构件参数的方法、装置、设备和可读存储介质
CN113312212B (zh) * 2021-06-02 2024-05-07 广联达科技股份有限公司 保护模型构件参数的方法、装置、设备和可读存储介质

Also Published As

Publication number Publication date
CN107924397B (zh) 2021-12-03
CN107924397A (zh) 2018-04-17

Similar Documents

Publication Publication Date Title
WO2017113317A1 (fr) Procédé d'édition de fichier et éditeur de fichier
CN103235685B (zh) 一种设置终端操作系统桌面内容的方法和装置
EP3564844B1 (fr) Procédé et appareil de déduplication de données
KR20190095066A (ko) 정보 처리 방법, 장치, 서버 및 컴퓨터 판독 가능 매체
TWI502384B (zh) 檔案追蹤方法及其所適用之網路通訊裝置
US10860447B2 (en) Database cluster architecture based on dual port solid state disk
CN106951521B (zh) 日志文件的读写方法、装置及系统
CN110998537B (zh) 一种过期备份处理方法及备份服务器
JP2008217209A (ja) 差分スナップショット管理方法、計算機システム及びｎａｓ計算機
US20160314048A1 (en) Backup and related operations
US20150012846A1 (en) Method, System and Mobile Terminal for Deleting Chat Record
WO2017045481A1 (fr) Procédé et système de sélection de données dans des pages web
CN104166605A (zh) 基于增量数据文件的数据备份方法及系统
WO2010145269A1 (fr) Procédé et dispositif pour restaurer une opération de terminal et des données
CN103942126A (zh) 电子设备及其数据备份方法
CN107770207A (zh) 多终端设备间数据同步的方法
EP3286665B1 (fr) Régénération de pièces jointes riches
US20120185440A1 (en) Method and apparatus for providing address book restoration
CN103037076A (zh) 一种移动终端的状态备份还原方法及装置
WO2017067397A1 (fr) Procédé et dispositif de récupération de données
JP2010282586A (ja) ファイル管理装置、ファイル管理方法、ファイル管理プログラム及び情報システム
CN103995706A (zh) 一种图片缩略图显示方法及装置
US11550665B2 (en) Techniques for preserving clone relationships between files
US20150347008A1 (en) Method for controlling virtual keyboard and electronic device implementing the same
CN110795389B (zh) 基于存储快照的拷贝方法、用户设备、存储介质及装置

Legal Events

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

Ref document number: 15911943

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15911943

Country of ref document: EP

Kind code of ref document: A1