JP6805096B2 - File generator, file generator, and file generator - Google Patents

Description

The present invention relates to a file generation device, a file generation method, and a technique of a file generation program.

JSON (JavaScript (registered trademark) Object Notation), which is a lightweight data exchange format, has been adopted as a standard format by standardization organizations such as the Open API Initiative as a data format that enables flexible data description. Compared to the list format, which groups multiple data in order, and the data table format, which stores multiple data in cells of m rows and n columns, JSON files include the parent object and are further contained within the parent object. Complex descriptions that include child objects are also possible.

On the site of Non-Patent Document 1, an editor on the web that can add objects and the like is published so that a programmer can easily edit a JSON file that is a text file. In this editor, the readability of the JSON file is improved by coloring the value contained in the object and adding the line number to each line of the text file.

"JSON Editor Online", [online], [Searched on July 26, 2017], Internet <URL: http://jsoneditoronline.org/>

Programmers may want to do transcription-type coding that cuts out part of the source code of an existing program and pastes it into new source code. At that time, a part of the existing file is referred to as the material. Below, consider the case of reusing a JSON file as a material.

Since the JSON file is a text file, the programmer reads the contents of the JSON file line by line from the beginning and posts only the necessary parts to the new file. However, the JSON file is a complicated data structure including the hierarchical relationship (parent-child relationship) of objects as described above. Therefore, no matter how easy it is to read on the screen with the editor of Non-Patent Document 1, the work of manually transcribing takes a long time and tends to cause work mistakes.

FIG. 14 is an explanatory diagram showing a specific example of a process of manually creating a new JSON file of the transfer destination from the material JSON file of the transfer source. Since the JSON file is a text file, a line ID (A01, A02, A03 ...) is added to the left side of each line of the text file for easy explanation in this specification.
In the material JSON file, as reusable parts, "Posting source A03 line to A06 line → Posting destination B03 line to B06 line" and "Posting source A07 line, A08 line → Posting destination B13 line, B14 line" , "Posting source A15 line to A20 line → Posting destination B19 line to B24 line".
However, as a work mistake, for example, only the first half (A03 line, A04 line) of the object may be cut out and the second half (A05 line, A06 line) may be forgotten. At that time, the new JSON file contains insufficient objects (objects without B05 and B06 lines) only in the first half.

Therefore, a main object of the present invention is to provide an editing support means for efficiently reusing a material file having a complicated data structure.

In order to solve the above problems, the file generator of the present invention has the following features.
The present invention includes a material database in which material objects used as part of a newly generated file are stored.
The new intermediate data in which the identification information of the material object is described as a link is read at the position where the description content of the material object is inserted, and the identification information of the material object read from the link in the new intermediate data is used as a search key to read the material. database to get the description content of the material object from, by inserting replace the description contents of the acquired material object to the link of the new intermediate data, have a, and the new file creating unit that creates the new generation file ,
The icon for each material object registered in the material database is displayed on the screen, and the operation of dragging and dropping the icon to a predetermined position in the new intermediate data is accepted.
It has a file editing unit that creates the new intermediate data to be input to the new file creation unit by adding a link of the material object corresponding to the dragged icon to the dropped predetermined position.
The file editing unit is characterized in that an object similar to the material object corresponding to the dragged icon is read from the material database and presented as an input candidate .
Further, the file editing unit is characterized in that links of similar objects presented as input candidates are collectively input to the new intermediate data.
Further, the file editing unit is characterized in that meta information given to the similar object, which is an input candidate, is displayed for each icon.
Further, when the duplicate object exists in the set of material objects corresponding to the dragged icon, the file editing unit activates one material object in the set of duplicate material objects. However, it is characterized in that other material objects are invalidated.

As a result, a material file having a complicated data structure can be efficiently created by a mechanism in which the description content of the material object is reused only by embedding one link. Furthermore, the editing work of embedding a link in new intermediate data can be realized intuitively and efficiently.

The present invention has a material registration unit that extracts a material object from an input material file and registers the material object of the extraction result in the material database.
The material registration unit extracts the objects described in the material file one by one as separate material objects.

As a result, the objects listed in the material file can be automatically extracted one by one as separate material objects.

The present invention is characterized in that the material registration unit extracts an object included in the material object described in the material file as yet another material object.

As a result, not only the parent object but also the child objects included in the parent object can be automatically extracted as a new material object.

The present invention extracts a part of the description including a plurality of elements selected by the range specification from the input material file, and in addition to the material object containing the extraction result, the part of the range specified. It is characterized by having a material registration unit for registering a material object including another extraction result extracted according to the same extraction rule as the description in the material database.

As a result, even when a part of the object is reused, only the reused part can be extracted as a material object.

According to the present invention, when the file editing unit displays an icon for each material object on the screen, when the second material object is included inside the first material object, the icon of the first material object is displayed. Is displayed on the screen, and when the icon of the first material object is double-clicked, the icon of the second material object displayed as a tree from the icon of the first material object is also displayed on the screen. To do.

As a result, by displaying a set of objects having a parent-child relationship at once, a desired material object can be efficiently found even when a large number of material objects are registered in the material database.

According to the present invention, it is possible to provide an editing support means for efficiently reusing a material file having a complicated data structure.

It is explanatory drawing which shows the process of extracting the material object from the material JSON file which concerns on this embodiment. It is explanatory drawing which shows the process of creating a new JSON file from the material object and the new JSON template which concerns on this Embodiment. It is explanatory drawing which shows the specific example of the process of extracting the material object from the material JSON file shown in FIG. 1 which concerns on this Embodiment. It is explanatory drawing which shows the specific example different from FIG. 3 which concerns on this Embodiment. It is explanatory drawing which shows the specific example of the process of creating a new JSON file from the material object and the new JSON template which concerns on this Embodiment. It is a block diagram of the file generation apparatus which concerns on this embodiment. It is a data table which shows an example of the material database which concerns on this embodiment. It is a screen view of the portal screen presented to the user in the process of inputting a new JSON template by the file editing department related to this embodiment. It is a screen view after the drag-and-drop operation is performed from the portal screen of FIG. 8 which concerns on this embodiment. This is the main routine of the new file creation unit related to this embodiment. This is a subroutine of the file editing unit related to this embodiment. It is explanatory drawing which shows the specific example of the object X and the object Y which have a similar relationship explained with FIG. 11 which concerns on this Embodiment. It is explanatory drawing which shows the result of generating a new JSON file based on the object X and the object Y which are the similar relations related to this embodiment. It is explanatory drawing which shows the specific example of the process of manually creating a new JSON file of a transfer destination from a material JSON file of a transfer source.

Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. First, the outline of the processing of the present embodiment will be described with reference to FIGS. 1 to 5. Each of these processes is executed by each processing unit of the file generation device 1 shown in FIG.

FIG. 1 is an explanatory diagram showing a process of extracting a material object 92 from a material JSON file 91 (material file).
As the material JSON file 91, a first file containing three objects "Obj1, Obj2, Obj3" and a second file containing three objects "Obj4, Obj5, Obj6" are exemplified.
Each object is independently extracted as a material object 92 that will be reused in the future. For example, "Obj1, Obj2" is extracted from the first file, and "Obj4, Obj5" is extracted from the second file. On the other hand, the remaining objects "Obj3, Obj6" were not extracted due to their low reusability.

FIG. 2 is an explanatory diagram showing a process of creating a new JSON file 94 (newly generated file) from the material object 92 and the new JSON template 93 (new intermediate data).
As the material object 92, four objects "Obj1, Obj2, Obj4, Obj5" extracted in FIG. 1 are registered.
The new JSON template 93 is data that serves as a mount for generating a new JSON file 94, and in addition to elements of the JSON file such as an object, a link to the material object 92 can be described. Here, as the new JSON template 93, in addition to the three newly described objects "Obj7, Obj8, Obj9", the links "Obj1, Obj4" to the material object 92 are described.

When the description of the new JSON template 93 is completed, the new JSON file 94 is created by expanding (replacing) the links "Obj1, Obj4" to the material object 92 in the new JSON template to the description contents of the material object 92. To. In other words, three objects "Obj7, Obj8, Obj9" in the new JSON file 94 are manually generated, and two objects "Obj1, Obj4" in the new JSON file 94 are automatically generated.

FIG. 3 is an explanatory diagram showing a specific example of the process of extracting the material object 92 from the material JSON file 91 shown in FIG.
First, since the material JSON file 91, the material object 92, and the like are text files, a line ID (A01, A02, A03 ...) Is added to the left side of each line of the text file for easy explanation in the present specification.
In the material JSON file 91, three objects "object1 starting from line A02, object2 starting from line A12, and object3 starting from line A22" are described in order from the top. These three objects can be extracted as separate material objects 92-1, 92-2, and 92-3 by parsing one by one in the order of scanning.

FIG. 4 is an explanatory diagram showing a specific example different from that of FIG. The details of the extraction method of the three extracted material objects 92 will be described in order.
In the material object 92-4 "object1 ref", the part of the material JSON file 91 whose range is specified by the user is newly extracted as one material object 92.
The material registration unit 12 (FIG. 6) inputs from the user the range specification data of lines A07 and A08 in the material JSON file 91 and the name data "object1 ref" of the material object 92 to be named in the range specification data. Accept. Then, the material registration unit 12 converts the range designation data part (A07 line, A08 line) into the JSON object format. In this conversion process, the part (a01 line to a03 line, a04 line to a06 line) enclosed as an object before and after the range specified part (A07 line, A08 line) is complemented, and the name "object1" entered in the result is completed. Assign "ref".

The material object 92-5 "object2-1" is an object of lines A15 to A20 included as a part of "object2" described in lines A12 to A21 of the material JSON file 91. The material object "object2-1" is extracted as a child object for the parent object "object2" and as one object separately from object2.
In this way, not only the parent object (first layer) included in the material JSON file 91, but also the child object (second layer) included in the parent object, the grandchild object (third layer) included in the child object, and the like. , Objects of a plurality of layers may be separately extracted as material objects 92.

The material object 92-6 "object3 ref" is extracted by assuming that the range is specified in a place (A27 line, A28 line) different from the range specified part (A07 line, A08 line). ..
First, the key (here, key1-1 and key1-2 in that order) of the location (A07 line, A08 line) specified as the material object "object1 ref" is registered as an extraction rule. Then, the extraction rule of the specified range (A07 line, A08 line) is applied to another similar part (A27 line, A28 line).
Here, the key (in the order of key1-1, key1-2) is different from the specified range (A07 line, A08 line) and another part (A27 line, A28 line), although the object values are different from each other. Since they are the same as each other, they meet the extraction rules. Therefore, it is possible to propose in advance the material objectization of similar parts without taking the trouble of specifying the range.

FIG. 5 is an explanatory diagram showing a specific example of a process of creating a new JSON file 94 from the material object 92 and the new JSON template 93.
As the new JSON template 93, the newly described element is indicated by the line ID starting from B like B01 and B02, and the line where the link to the material object 92 is described is indicated by the line ID starting from L (meaning Link). .. That is, three links (object1-1 on the L01 line, object1-ref on the L02 line, and object2-1 on the L03 line) are embedded in the illustrated new JSON template 93. In this specification, for the sake of explanation regardless of the JSON file standard, the link line is distinguished from other lines by enclosing the object name with a special symbol (%%). It was to be.

Next, the link line L01 is expanded to the description contents of the material object 92 (lines B03 to B06) by the process of expanding the link line of the new JSON template 93 to the description contents of the material object 92 which is the link source. The object. Similarly, the link line L02 is expanded to the description contents of the material object 92 (B11 to B15 lines), and the link line L03 is expanded to the description contents of the material object 92 (B19 to B24 lines).
As a result, one new JSON file 94 is generated by reusing the three material objects 92. That is, for the same new JSON file 94 as in FIG. 14, the new JSON file 94 can be efficiently and automatically generated without actually having the user perform the JSON file transcription work.

FIG. 6 is a configuration diagram of the file generation device 1.
The file generation device 1 is configured as a computer having a CPU (Central Processing Unit), a memory, a storage means (storage unit) such as a hard disk, and a network interface.
In this computer, the CPU operates a control unit (control means) composed of each processing unit by executing a program (also called an application or an abbreviation thereof) read in the memory. That is, in the present invention, the hardware resources of a general computer can be realized by a file generation program that operates as each means of the file generation device 1. Further, this program can be distributed via a communication line, or can be recorded and distributed on a recording medium such as a CD-ROM.

The file generation device 1 has a file editing unit 11, a material registration unit 12, a material database 13, a material presentation unit 14, and a new file creation unit 15.
Hereinafter, the details of each component will be described with reference to the steps (S11 to S25 in FIG. 6) showing the signal flow between the components of the file generation device 1.

The file editing unit 11 provides the user with a portal screen for generating a new JSON file 94. The file editing unit 11 receives the input of the material JSON file 91 shown in FIG. 1 from the user via the portal screen (S11). Further, upon input by the user, the file editing unit 11 accepts additional input for extracting the material object 92 from the material JSON file 91. The additional input is, for example, input of information for designating the material object 92 to be extracted, or input of information for specifying a part of the material JSON file 91 to be the material object 92 to be extracted.

The material registration unit 12 reads the material JSON file 91 input in S11 (S12), extracts the material object 92 from the material JSON file 91, and registers the extraction result in the material database 13 (S13). The extraction target of the material object 92 by the material registration unit 12 is classified as shown below, for example.
(Extraction target 1) An object originally defined as an object. For example, the objects "object1, object2, object3" in FIG.
(Extraction target 2) Object in the object. For example, the object "object2-1" in the object "object2" in FIG.
(Extraction target 3) An object in which a part of the description content in the object is extracted. For example, the range-specified object "object1 ref" in FIG. 4 and the "object3 ref" to which the range-specified extraction rule is applied.

FIG. 7 is a data table showing an example of the material database 13.
In the material database 13, the description contents of the material object 92 are registered for each object name of the material object 92. The material object 92 is an associative array format in which one or more combinations of an item name (key) and its item value (value) are registered as specified in the JSON file format. Further, as shown by the object name "3-1-1", the material object 92 is described in a list format including other material objects {1-1-1} and {2-1-1}. May be good.

Returning to FIG. 6, the material presentation unit 14 reads the material object 92 registered in the material database 13 (S14) and presents it to the user as a reusable icon via the file editing unit 11 (portal screen). (S15).
The file editing unit 11 causes the user to select (drag) the icon of the material object 92 and insert (drop) it in the new JSON template to link to the material object 92 (link lines L01, L02, L03 in FIG. 5). ) Is described in the new JSON template 93 (left side of FIG. 5) (S21).
The new file creation unit 15 acquires the object name corresponding to the link included in the input new JSON template 93 from the material presentation unit 14 (S23), and reads the description content corresponding to the object name from the material database 13 ( S24). Then, the new file creation unit 15 creates a new JSON file 94 by expanding the description content of the read material object 92 at the link position of the new JSON template 93 (S25).

FIG. 8 is a screen view of the portal screen presented to the user in the input process (S21) of the new JSON template 93 by the file editing unit 11.
The icons (drag sources) of the material object 92 are listed on the left side of the portal screen. If there is a parent-child relationship (hierarchical relationship) between the material objects, double-clicking the parent object (3-1-1) will display the child objects (1-1-1,2-1-1) in a tree. .. That is, in the tree display, it is possible to switch between the collapsed state in which only the parent object is displayed and the expanded state in which both the parent and child objects are displayed by double-clicking.
On the right side of the portal screen, the description content (drop destination) of the new JSON template 93 being edited and the file creation button for creating a new JSON file 94 from the new JSON template 93 after the editing is completed are displayed. In the new JSON template 93, an object area R1 for roughly determining the editing position is defined, and objects (2-1-2, 3-1-2) can be arranged in the area R1.

FIG. 9 is a screen view after the drag and drop operation is performed from the portal screen of FIG.
First, the user creates a new object area R2 in the new JSON template.
Next, the user drags the icon (1-1-1) of the material object 92 and drops it as it is into the area R2 (shown by the arrow). As a result, a link to the material object 92 (1-1-1) is embedded in the area R2 of the new JSON template 93 (shown by enclosing 1-1-1 with a broken line to indicate the link).
Similarly, the user adds a link to the material object 92 (1-1-2) in the area R2 of the new JSON template 93.

FIG. 10 is the main routine of the new file creation unit 15. This main routine is executed when the file creation button is pressed from the portal screen of FIG.
As S101 to S107, the new file creation unit 15 executes a loop for sequentially selecting the object areas included in the new JSON template 93 (R2 → R1 in FIG. 9).
As S102, the file editing unit 11 executes a subroutine (FIG. 11) for adding an icon in the area selected by the loop.
In S103 to S106, the new file creation unit 15 executes a loop of sequentially selecting the icons in the area added in S102 (1-1-1 → 1-1-2 in FIG. 9).
As S104, the new file creation unit 15 acquires the object name corresponding to the icon selected in the loop from the material presentation unit 14.
As S105, the new file creation unit 15 acquires the description content of the material object 92 corresponding to the object name acquired in S104 from the material database 13, and adds the acquired description content to the new JSON file 94.
As S108, the new file creation unit 15 outputs the addition result of S105 repeatedly implemented in the loop as a new JSON file 94.

FIG. 11 is a subroutine of the file editing unit 11. This subroutine is called from S102 for each object area currently selected in the loop from S101.
As S201, the new file creation unit 15 determines whether or not an object similar to the object included in the selected object area exists in the material object 92 registered in the material database 13. A similar object means that when the object X and the object Y include the same set of keys in common, the object X and the object Y have a similar relationship. If Yes in S201, proceed to S202, and if No, proceed to S203.
As S202, the file editing unit 11 presents the icon of the material object 92 before input to the new JSON template 93 as an input candidate, which is similar to the object already input to the new JSON template 93. As a result, the user can input similar objects at once, and can prevent forgetting to input similar objects.
As S203, the file editing unit 11 adds an icon to the selected object area for the object already input to the new JSON template 93, as illustrated in the area R2 of FIG.

As S204, the file editing unit 11 determines whether or not there are duplicate objects in the object set included in the selected object area. The overlapping object means that the object X and the object Y are the same (overlapping relationship) when the object X and the object Y include a set of the same key and the same value in common. In other words, unlike similar relationships, not only the key but also the value is the same among multiple objects. If Yes in S204, proceed to S205, and if No, proceed to S206.
As S205, the file editing unit 11 invalidates the operation of the icon for the duplicate object detected in S204. That is, since it is useless if the objects X and the objects Y having the same relationship exist in the same one area, one object X is enabled and the other object Y is invalidated. Since the object Y has been invalidated, it is not subject to the subsequent link expansion processing of S104 and S105.

As S206, the file editing unit 11 determines whether or not the object X and the object Y having a similar relationship defined in S201 are registered in the same one area. If Yes in S206, proceed to S207, and if No, proceed to S208.
As S207, the file editing unit 11 assigns meta information indicating the similarity to each of the plurality of objects having a similarity relationship registered in the same area. Note that, unlike the overlapping relationship in S204, objects having a plurality of similar relationships in the same area are both valid.

As S208, the file editing unit 11 displays the icon added to the selected object area on the portal screen. Here, by displaying the meta information given in S207 for each icon, the user can easily grasp that a set of objects having a similar relationship has been input collectively.
As S209, the file editing unit 11 determines whether or not there is an object to be added to the selected object area. If Yes in S209, the process returns to S201. If No, the subroutine of FIG. 11 (S102) is terminated, and the process proceeds to the main routine (S103) of FIG.

FIG. 12 shows objects X (upper side of FIG. 12, material object 92-7 starting from line C01) and object Y (lower side of FIG. 12, material object 92-8 starting from line D01) having a similar relationship described with reference to FIG. It is explanatory drawing which shows a specific example. The key set included in this object X is "description, href, id, isRoot, lastUpdate, lifecycleStatus, name, version, validFor, endDateTime, startDateTime" in order from the top.
Also, the key set included in object Y is "description, href, id, isRoot, lastUpdate, lifecycleStatus, name, version, validFor, endDateTime, startDateTime" in order from the top, which is the same as the key set included in object X. is there. However, the value corresponding to each key is different between the object X and the object Y.

FIG. 13 is an explanatory diagram showing the result of generating a new JSON file 94 based on the objects X and Y that have a similar relationship. From line E04, the key "href, id, name, version" of a part of object X (material object 92-71) shown in FIG. 12 is linked and expanded, and from line E10, a part of object Y (material object 92-71) is expanded. The key "href, id, name, version" of the material object 92-81) is linked and expanded. In this way, the new JSON file 94 can be efficiently created by inputting similar material objects 92 into the new JSON template 93 at once.

In the present embodiment described above, the file generation device 1 that accepts a simple editing operation of newly dragging and dropping the material object 92 registered in the material database 13 into the new JSON template has been described. As a result, a new JSON file 94 including the description contents of the material object 92 can be efficiently created from the link generated by the editing operation.

As a comparative example, a system that converts a conversion source file described in a data format different from the JSON file into a JSON file can be considered. The conversion source file is, for example, a graphic file including an icon of the object A, an icon of the object B, and an arrow connecting the objects. However, in this comparative example, since the mechanism for reusing the description contents of the material object 92 is not provided, the editing work of the new JSON file 94 cannot be made more efficient.

On the other hand, the file generation device 1 of the present embodiment, which efficiently and automatically generates the text content of the new JSON file 94 in this way, edits the new JSON file 94 by a mechanism for reusing the description content of the material object 92. It helps to improve efficiency.

1 File generator 11 File editing department 12 Material registration department 13 Material database 14 Material presentation department 15 New file creation department 91 Material JSON file 92 Material object 93 New JSON template 94 New JSON file

Claims (10)

A material database that stores material objects used as part of the newly generated file,
The new intermediate data in which the identification information of the material object is described as a link is read at the position where the description content of the material object is inserted, and the identification information of the material object read from the link in the new intermediate data is used as a search key to read the material. database to get the description content of the material object from, by inserting replace the description contents of the acquired material object to the link of the new intermediate data, have a, and the new file creating unit that creates the new generation file ,
The icon for each material object registered in the material database is displayed on the screen, and the operation of dragging and dropping the icon to a predetermined position in the new intermediate data is accepted.
It has a file editing unit that creates the new intermediate data to be input to the new file creation unit by adding a link of the material object corresponding to the dragged icon to the dropped predetermined position.
The file editing unit is a file generation device characterized in that an object similar to the material object corresponding to the dragged icon is read from the material database and presented as an input candidate . The file editing unit is characterized in that links of similar objects presented as input candidates are collectively input to the new intermediate data.
The file generator according to claim 1. The file editing unit is characterized in that meta information given to the similar object, which is an input candidate, is displayed for each icon.
The file generator according to claim 1. If there are duplicate objects in the set of material objects corresponding to the dragged icon, the file editorial unit enables one material object in the set of duplicate material objects while enabling it. Characterized by disabling other material objects
The file generator according to claim 1. Extract a part of the description including multiple elements selected by the range specification from the input material file, and in addition to the material object containing the extraction result, the same extraction as the part of the description specified in the range The file generation device according to claim 1, further comprising a material registration unit for registering a material object including another extraction result extracted according to a rule in the material database. It has a material registration unit that extracts material objects from the input material file and registers the material objects of the extraction results in the material database.
The file generation device according to claim 1, wherein the material registration unit extracts the objects described in the material file one by one as separate material objects. The material registration unit is characterized in that an object included in the material object described in the material file is extracted as yet another material object.
The file generator according to claim 6 . When the icon for each material object is displayed on the screen, the file editing unit displays the icon of the first material object on the screen when the second material object is included inside the first material object. At the same time, when the icon of the first material object is double-clicked, the icon of the second material object displayed as a tree from the icon of the first material object is also displayed on the screen.
The file generator according to claim 1 . The file generation device has a material database, a new file creation unit, and a file editing unit .
The material database stores material objects used as part of the newly generated file.
The new file creation unit reads new intermediate data in which the identification information of the material object is described as a link at a position where the description content of the material object is inserted, and the identification information of the material object read from the link in the new intermediate data. Is used as a search key, the description content of the material object is acquired from the material database, and the description content of the acquired material object is replaced with the link of the new intermediate data and inserted to create the newly generated file .
The file editorial department
The icon for each material object registered in the material database is displayed on the screen, and the operation of dragging and dropping the icon to a predetermined position in the new intermediate data is accepted.
By adding the link of the material object corresponding to the dragged icon to the dropped predetermined position, the new intermediate data to be input to the new file creation unit is created.
A file generation method characterized in that an object similar to the material object corresponding to the dragged icon is read from the material database and presented as an input candidate . A computer as a file generator that stores a material database that stores material objects used as part of a newly generated file.
The new intermediate data in which the identification information of the material object is described as a link is read at the position where the description content of the material object is inserted, and the identification information of the material object read from the link in the new intermediate data is used as a search key to read the material. A new file creation means for creating the newly generated file by acquiring the description content of the material object from the database and replacing the acquired description content of the material object with the link of the new intermediate data and inserting it .
The icon for each material object registered in the material database is displayed on the screen, and the operation of dragging and dropping the icon to a predetermined position in the new intermediate data is accepted.
By adding the link of the material object corresponding to the dragged icon to the dropped predetermined position, the new intermediate data to be input to the new file creation means is created.
A file generation program for reading an object similar to the material object corresponding to the dragged icon from the material database and making it function as a file editing means presented as an input candidate .

Images