JPH01114948A - File edition supporting method - Google Patents

Abstract

PURPOSE:To easily and efficiently execute reedition even if file edition is frequently executed by storing an edition history file for an updated file, a backup file and an edition history file for the backup file every updating a file. CONSTITUTION:When a command for starting editing operation and a file name for specifying a file 9 in a file storing part 1 are inputted from an input part 3, a file control part 2 loads the specified file 9 to an edition storing part 5. An edition history file forming part 6 forms a new edition history file in an edition history storing part 7. Then, an edition processing part 4 executes the edition processing of the file in the storing part 5 in accordance with an edition command and edition information inputted from the input part 3. Every execution of each edition processing, the screen display of a display part 8 is also updated. The editing operation and edited contents are successively recorded in the edition history file in the storing part 7.

Description

[Detailed Description of the Invention] Industrial Application Field The present invention is a file editing support method for supporting the editing and management of files such as source program files in a general-purpose data processing device or a dedicated file creation and editing device. Regarding.

BACKGROUND ART Source program files are generally created and edited on a computer using a program called an editor.

Many of these editors have a function that saves a copy of the unedited file as a backup file every time the file is updated. This file backup function allows you to check the editing process by comparing the updated file and the backup file when it is necessary to check the edited content or re-edit the updated file (file after editing). Also, if you need to make a major modification to the updated file, you can rename the backup file as the original file instead of the updated file and edit it to get the desired file. This is useful as a support function for file editing.

Regarding the editing support function for document files, there is a known word processor that saves editing history information and the unedited file when a file (document file) is edited (Japanese Patent Laid-Open No. 60-16486
No. 3).

Problems to be Solved by the Invention However, even if the editing process can be checked by comparing and contrasting the update file and the back-amp file with the file/banokatsu function of the editor mentioned above, the comparison and comparison work is quite troublesome. There is also the problem that it is easy to overlook the editing content.

In this regard, file comparison work can be facilitated by frequently updating files each time a certain amount of editing operations are performed, rather than performing many edits at once. However, each time a file is updated, the backup file is also updated, and the contents of previous edits to the backup file are unknown, so if you update the file too frequently, you should check the flow of file editing carefully. Another problem arises in that it is no longer possible to edit the data, and it is not possible to effectively re-edit using the backup file.

On the other hand, in the word processor, editing contents can be directly confirmed from recorded editing history information. However, since the edit history that can be checked is limited to the edit history from the backup file to the updated file, there is a problem similar to the above-mentioned editor when files are frequently updated.

The present invention has been made in view of the above-mentioned problems, and allows editing history to be directly checked, sufficient editing history information can be obtained even when files are frequently updated, and back-up The purpose of the present invention is to provide a file editing support method that makes it easy to re-edit files based on files.

Means for Solving the Problems In order to solve the above-mentioned problems, the present invention creates an editing history file that records editing operations and editing contents while editing a file, and edits the updated file every time the file is updated. The configuration is such that the history file is saved, and the original file of the updated file (pre-edited file) and a similar edit history file for this file are also saved.

Effect of the Invention With the above-described configuration, the present invention allows editing history to be checked directly from the editing history file without comparing and contrasting the updated file with the unedited file, making editing process management and re-editing more efficient. It can be done in a
You can check not only the editing operations and contents performed to create the updated file, but also the editing operations and contents performed to create the unedited file, so even if the file is frequently updated. , it is possible to fully check the editing process, and re-editing based on backup files can be done effectively and easily.

EXAMPLE An example of the present invention will be described below with reference to the drawings.

FIG. 1 is a functional block diagram of a file editing device to which the file editing support method according to the present invention is applied, and FIG. 2 is a practical block diagram of the same file editing device.

First, explanation will be given with reference to FIG. 1 is a file storage section, 2 is a file control section that controls file storage, reading, updating, etc., 3 is an input section for inputting editing commands, etc., and 4 is an insertion, deletion, and modification section for files. 5 is an editing storage section in which the file being edited is temporarily stored. Reference numeral 6 denotes an editing history file creation section that creates an editing history file during editing processing, 7 an editing history storage section in which the editing history file is temporarily stored, and 8 a display section for displaying files and the like.

In such a configuration, the '
When a command and a file name specifying a file 9 (for example, a source program file) in the file storage section 1 are input from the input section 3, the file control section 2 loads the specified file 9 into the editing storage section 5. do. This file is also displayed on the display section 8. At this point, it is assumed that the file 90 edit history file 10, the backup file 11 of the file 9, and its edit history file 12 are stored in the file storage unit 1. Further, the editing history file creation section 6 generates a new editing history file (empty file) in the editing history storage section 7.

Thereafter, the editing processing section 4 performs editing processing on the file in the editing storage section 5 according to the editing command and editing information inputted from the input section 3. Every time the editing process is performed, the 8-screen display on the display section is also updated.

Further, the editing operations and editing contents are sequentially recorded in the editing history file in the editing history storage section 7 by the editing history file creation section 6.

File editing and editing history file creation are performed in this way, but when the end command is input to the input section 3, the file control section 2 deletes the backup file 11 and re-banks the copy of the file 9. The edit history file 12 is deleted, and a copy of the edit history file 10 is stored again as the edit history file 12 of the backup file. Next, the files in the editing storage unit 5 are used in the file storage unit 1
The edit history file f1 of the updated file is updated using the edit history file in the edit history storage section 7.
Update 0.

In this way, each time a file is updated, the original file and its editing history file are backed up, and the editing history file of the updated file is updated.

Note that the input section 3 inputs the update file 9 or the backup file 11, or the edit history file 10 or 1.
2 is input, the file control section 2 transfers the specified file to the display section 8,
Display.

Next, the practical configuration of the file editing device will be explained with reference to FIG. 14 is a central processing unit, 15 is a main memory 16
is a hard disk device, 17 is a disk control device, 18
1 is a display device with a keyboard 19 attached, 21 is a display control device, and 21 is a bus.

The hard disk device 16 is the file storage section 1 shown in FIG.
(including the operating system) are also stored there.

Necessary programs in this program group are loaded into a specific area of the main memory 15 when the device is powered on, and can be executed by the central processing unit 14. The disk controller 17 cooperates with the central processing unit 14 (program) to implement the file controller 2 shown in FIG.

The display device 18 and the attached keyboard 19, together with the display control device, implement the display section 8 and input section 3 in FIG. 1, respectively.

The editing storage section 5 and editing history storage section 7 in FIG. 1 are realized as an editing storage area and an editing history storage area on the main memory 15. Further, the editing processing section 4 and the editing history file creation section 6 shown in FIG. 1 are realized by the central processing unit 14 according to a program loaded onto the main memory 15.

The operation of the file editing device configured as described above will be described below. Figure 3 is a flowchart. For convenience of explanation, it is assumed that files 9, 10, 11, and 12 similar to those shown in FIG. 1 are stored in the node disk storage device 16, and that file 9 is to be edited.

In step 1, an edit start command and a file name (here, the file name of file 9) are input using the keyboard 19.

Then, in step 2, the specified file 9 is loaded into the editing storage area on the main memory 15. The contents of this file are also displayed on the display device 18. In the next step 3, create a new edit history file (
At this point, an empty file) is generated in the edit history storage area on the main memory 15. Then, in step 4, each file is opened. This completes the preparation process for file editing.

In step 4, when a command is input from the keyboard 19, the input command is analyzed in steps 6 to 11. That is, whether it is a display instruction command for the history file 10 (step 6) or a display instruction command for the backup file 11 (step 7).
), whether it is a display instruction command for the edit history file 12 of the edit history file 11 (step 8), whether it is an edit end command (step 9), whether it is an edit stop (edit cancel) command (step 10), and whether it is an actual command. It is sequentially checked whether the command is for editing (step 11).

If it is determined in step 11 that the command is an editing command such as deletion, insertion, or modification, specific editing information is input from the keyboard 19 in step 12. According to this input information, in step 13, editing processing (deletion, insertion, modification, etc.) of the file in the editing storage area on the main memory 15 is executed.

When this editing process is completed, in step 14, the command (editing operation) input in step 5 is
The contents of the editing process performed in step 13 (in the case of deletion, the deleted contents, in the case of modification, the contents before and after the modification,
In the case of insertion, the inserted contents) are written to the editing history storage area on the main memory 15.

After that, return to step 5.

FIG. 4 is an explanatory diagram of the editing history file. As shown in the figure, the editing history file is composed of an operation number recording area n, a command recording area n, and an editing content recording area. In the operation number recording area n, a consecutive number indicating the order of editing operations is recorded, and in the command recording area B, commands actually input for editing are recorded. Note that the example shown here assumes editing on a line-by-line basis. As described above, the edited content recording area records the deleted content, inserted content, and content before and after modification.

Now, as described above, file editing is executed on the main memory 15 and an editing history file is created, but at the start of editing or in the middle of editing, it is necessary to check the file update process up to that point. If the need arises, you can input the command from the keyboard 19.
The contents of the desired file can be displayed on the display device 18. .

For example, when a command to display the edit history file 10 of file 9 is input, the process proceeds from step 6 to step 15, and the contents of the edit history file 10 are displayed on the screen. When a command to display the backup file 11 is input, the process advances from step 7 to step 16, and the contents of the backup file 11 are displayed on the screen. Similarly, when a command to display the edit history file 12 of the backup file 11 is input, step 8 moves to step 1.
7, the contents of the edit history file 12 are displayed on the screen.

If it is determined in step 11 that the input command is not directly related to editing, then in step 18 the process corresponding to the command is executed.

For example, with the edit history file 10.12 and the backup file 11 displayed on the screen, returning to the screen display of the file being edited, scrolling the screen, etc. are executed according to input commands in this step.

To finish the necessary editing and update the file, input the editing end command. When this editing end command is input, the process advances from step 9 to step 19. In this step, the backup file 11 and its editing history file 12 in the hard disk 16 are deleted, and copies of the file 9 and its editing history file 10 are stored anew as the backup file 11 and editing history file 12. In the next step, the file 9 in the hard disk drive 16 is updated with the contents of the file in the edit memory on the main memory 15, and the edit history file lO is updated with the contents of the file in the edit history memory on the main memory 15. Updated by the contents of the history file. Then, in step 21, each file is closed, and the process ends.

In this way, each time a file is updated, the edit history file 10 of the updated file 9 is saved, and the backup file 11 and its edit history file 12 are also saved. The contents of the edits made to create the update file 9 can be directly confirmed. Furthermore, edit history file 12
Since you can also check the contents of the edits made to create the backup file 11 from can be easily re-edited, and files based on bank-up files can also be easily re-edited.

To cancel editing and cancel the editing operations up to that point, input a cancel command from the keyboard 19. If this cancel command is input, the process advances from step 10 to step 21, each file is closed, and the process ends. In this case, each file 9.10.11.12 in the hard disk device 16 will be saved as is.

Note that a plurality of windows may be set on the screen of the display device 18, and different contents may be displayed on each window at the same time. In this way, the contents of two or more of the file currently being edited, the edit history file 101, the backup file 11, and the edit history file 12 can be displayed simultaneously, and they can be compared easily.

Further, it may be possible to display the file 9 on the screen during editing.

Effects of the Invention As is clear from the above description, the present invention saves the edit history file, backup file, and edit history file each time a file is updated, so even if the file is edited frequently, , the editing process can be directly confirmed, and file editing management and re-editing of updated files or backup files can be easily and efficiently performed.

[Brief explanation of the drawing]

FIG. 1 is a functional configuration diagram of a file editing device according to an embodiment of the present invention, FIG. 2 is a practical configuration diagram of the file editing device, FIG. 3 is a flowchart of the operation of the file editing device, and FIG. The figure is an explanatory diagram of the contents of the edit history file. 1...File storage unit, 2...File control unit, 3
. . . Input section, 4. Edit processing section, 5. Edit storage section, 6. Edit history file creation section, 7. Edit history origin, 8. Display section, 9. ...File, 10...
- Edit history file of file 9, 11... Backup file of file 9, 12... Edit history file of backup file 11, 14... Central processing unit, 15... Main memory, 16... Hard disk Device, 18... Display device, 19... Keyboard. Name of agent: Patent attorney Toshio Nakao and 1 other person11
v1j jl12 Figure 3

Claims (1)

[Claims] The present invention is characterized in that an editing history file is created that records editing operations and editing contents while editing a file, and each time a file is updated, the editing history file of the updated file, the file before editing, and its editing history file are respectively saved. File editing support method.