JP3294646B2 - Data processing system - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a data processing system which employs a configuration for managing an object and executes data processing by manipulating the object, and more particularly to a data processing system capable of efficiently executing data processing. To a data processing system.

2. Description of the Related Art A data processing system that manages an object such as a Japanese document, a graph, or a diagram, and executes data processing such as document creation by manipulating the object is becoming widespread. In order to make such a data processing system practical, it is necessary to construct a configuration that can efficiently execute data processing.

[0003]

2. Description of the Related Art Conventionally, in a data processing system that performs data processing by operating an object by adopting a configuration for managing an object, a parent-child relationship in which an object expands another object. , Each object manages its parent-child relationship. For example, when a Japanese document develops an image, the Japanese document itself manages the parent-child relationship by pointing to the image.

Conventionally, the relationship between objects other than the parent-child relationship has not been managed by the system itself, but has been left to the user's memory. For example, when a report is composed of a plurality of objects, the user needs to remember the combination of the objects.

[0005] Conventionally, when an operation is performed on an object, a method has been adopted in which an object to be operated is individually specified. For example, when performing an operation of copying a Japanese document when the image is expanded in a Japanese document, specify the Japanese document and also specify the image to be expanded in the Japanese document. It was a structure that would do it.

[0006]

However, if each object is configured to manage its own parent-child relationship, the program load on the application program increases, and processing with a unified interface becomes impossible. There is a problem.

[0007] If an object operation is executed by individually designating the object to be operated, there is a problem that the operation on the object cannot be executed at high speed.

The present invention has been made in view of such circumstances, and has a data processing system that performs data processing by manipulating the object by adopting a configuration for managing the object. It is an object of the present invention to provide a new data processing system that enables data processing to be executed.

[0009]

FIG. 1 shows the principle configuration of the present invention. In the figure, 1 is a data processing system configured according to the present invention, and 2 is a terminal provided in the data processing system 1.

[0010] The data processing system 1, the input-output control means 10, the object management unit 11, a data operation unit 13, a management unit 14, a registration unit 15, an identifying unit 16, the display control unit 17 And

The input / output control means 10 executes an interface process with the terminal 2. Object management means 1
1, to manage the objects to be deployed in the data processing system 1 110-i (i = 1~n ). Data operation means 1
3 is the object 110-i according to the instruction from the terminal 2.
Perform data processing by performing operations on.

[0012] The management means 14 is provided in a form independent of the object, and allows one or more objects to be linked to the link source object while permitting the link destination object to be the link source object. It manages information as to whether the object is an object and information as to whether the link relationship is linked as a child object or as a parent object.
More specifically, this management means 14
First management means / second pipe provided for each directory
Management means / third management means. This first management
The means is a parent for each object under the directory.
Information indicating whether the child is a child or child
And information indicating whether or not the information is to be managed. Also, the second management
In the means, objects under the directory are stored
Manage locations. In addition, the third management means is a link destination.
Allow objects to be linked objects
While linking to the link source object or
Which objects are multiple objects?
Information and its link relationship are recalled as child objects.
Link or link as parent object
And manage the information. The registration unit 15 registers data of a hierarchical link relationship established between objects in the management unit 14 by interacting with the terminal 2.

When the object 110-i is specified from the terminal 2 via the data operating means 13, the specifying means 16
By searching the data to manage the management unit 14, to identify the O Bed <br/> object 110-i communicating with the hierarchical form of the child in its <br/> object 110-i.

The display control means 17 is provided at the top of the link relationship.
To view a list of the object name only to be located in the display screen of the terminal 2.

[0015]

According to the present invention, the registering means 15 communicates with the user to control the object
The link relationship you established between the -i to register. Register at this time
In the link relationship, the link destination object 110
-i can be the link source object 110-i
Object 110-i becomes a parent
Sometimes, which child object 110-i is
Not only the child's object
When the parent 110-i becomes the parent, the child
Like parent 110-i, "parent → child →
Grandchild → great-grandchild → ... ”
Wear. In this way, the management means 14 sets the object 1
When managing a hierarchical link relationships between 10-i, the display control unit 17, in response to an instruction from the user, the link relationship
Will be displayed on the display screen of the terminal 2 to the list of object names for only object 110-i that is at the top of the.

Upon receiving a display such as a list of object names located at the highest position in the link relation, the user instructs the data operation means 13 to display the object 11 to be operated.
Specify 0-i to instruct object operation. At this time, the specifying unit 16 refers to the data managed by the management unit 14 to thereby specify the object 110-i to be operated.
The object 110-i, which is hierarchically connected in the form of a child, is specified and notified to the data operation means 13. In response to this notification, the data operation means 13 110-i and the object 110-i specified by the specifying means 16 are read, and data processing is executed by executing an object operation instructed by the user on these objects 110-i. To explain in more detail, the book
The data processing system 1 according to the present invention includes the first management method described above.
Objects that are indicated in the list to be listed
By listing only the objects,
And let the user select one of the
Let the user specify the operation on the object. Soshi
Then, by referring to the first management means described above, the selection is made.
Whether the selected object is a parent object
Is determined, and if the object is a parent object, the third
By referring to the management means of the
Objects that are hierarchically linked to
Identify the selected object and its identification
Perform the specified operation on the specified object
The processing is performed so as to execute the data processing.

[0017]

[0018]

[0019] Thus, in the data processing system 1 of the present invention, since a configuration in which management unit 14 that the system is prepared to manage the hierarchical link relationship of objects 110-i, the program load application program As it decreases, processing on a unified interface becomes possible. When specifying the object 110-i to be operated, to be able to run from that we are automatically applied to the other objects 110-i that the operation is in the hierarchical link relationship, the data processing at high speed become.

[0020]

DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention will be described below in detail with reference to embodiments. As described in FIG. 1, the composed data processing system 1 according to the present invention, in which a configuration for managing a hierarchical link relationship you established between the object 110-i in the system.

[0021] Figure 2 illustrates one embodiment of a management structure to manage the hierarchical link relationship you satisfied <br/> between the object 110-i. Here, “■” in the figure indicates a directory file, and “□” indicates an object 110-i under the directory.

[0022] In the figure, 20 is an object relationship management file is provided in the directory file associated, which the hierarchical link relationship you established between the object 110-i under the directory file, 30 directory Inode provided in association with the file
A block, which points to the object management book 40 / directory block 50 for managing the related information of the object 110-i under the directory file, and 40 is an object management book pointed to by the inode block 30; 50 manages control information of display / non-display in the parent object name list displayed on the screen;
Directory block pointed to by
It manages the file position of the object management book 40 and the information of the relative position indicating which data of which object is managed in which position of the object management book 40.

FIG. 3 shows an embodiment of the management data of the object management book 40 and the directory block 50, FIG.
An example of the management data of the object relation management file 20 is shown in FIG.

As shown in FIG. 3, the object management book 40 stores a parent flag (in the figure) indicating whether the object 110-i is a parent or a child, and the validity of the parent flag. Valid / invalid flag to be displayed (in the figure)
And a list non-display flag (in the figure) for displaying whether or not the parent object name list can be displayed, and a valid / invalid flag (in the figure) for displaying the validity of the list non-display flag. Specifically, in the case of the parent object 110-i, the display enable flag is set in the list non-display flag, and in the case of the child object 110-i, the display non-display flag is set in the list non-display flag. By setting, control information of display / non-display in the parent object name list is managed.

As shown in FIG. 3, the directory block 50 manages the object names in the same order as the object names held in the object management book 40, and also controls the relative positions of the data bodies of these managed object names. by managing the "inode-No" indicating which objects in the object management list 40 throat position
Whether data relating to the defect is managed will be managed.

On the other hand, as shown in FIG. 4, the object relation management file 20 includes a management area, an index area,
It consists of a record area. As shown in this figure, this index area is the object 110-i to be managed.
And the link information indicating where the object 110-i is managed in the record area. On the other hand, the record area is
A management area for managing invalidation, a management area for managing the link destination object name, a management area for managing the logical object name of the link destination object 110-i, and a connection relationship (parent / child) of the link object 110-i ) Management area to manage
And a management area for managing a link pointer to a previous record and a management area for managing a link pointer to a subsequent record.

The link relationship that will be managed in the object relationship management file 20 is for registering by the data registration mechanism the data processing system 1 interacts with a user, for example, the parent object 110-i by the user When it is created, a configuration is used in which a list of object names of the already prepared objects 110-i is displayed, and an object designated by the user is registered as a child object 110-i from among them, and is executed. Will do.

For example, an object 1 as shown in FIG.
When there is a hierarchical link relationship between the 10-i, the data registration mechanism, first of all, as shown in FIG. 6 (a),
Eobj is the parent object 110-i and Goj / Jo
By registering that bj is a child object 110-i in the object relation management file 20, the management data shown in FIG. 7 is registered in the object relation management file 20, and then, as shown in FIG. Thus, Coobj is the parent object 110-i, and Doc / Eobj / Fo
By registering that bj is a child object 110-i in the object relationship management file 20, the management data shown in FIG. in contrast, the floor established between the object 110-i
It is to process to register the layer specific link relationships. This
In the object relation management file 20 shown in FIG.
As a join relationship, manage only if it is a parent or a child
Object that appears to be a child of the C object
There is an E object as an object, and this E object
G objects are objects that are children of
As you can see from the management that
Contains the object "Parent → Child → Grandchild → Great-grandchild → ..."
It manages the hierarchical link relations established between members. Ma
As can be seen from the specific examples shown in FIGS. 7 and 8,
The object relationship management file 20 has a configuration that manages the objects that are the children of the parent object and also manages the parent-child relationship between the objects in two ways, such as managing the objects that are the parents of the child objects. . For example, as shown in FIG. 8, while managing that the D object is a child of the C object in the record with the relative value “5” in the record, the C object is the record with the relative value “8” in the record. In this configuration, the parent-child relationship between objects is managed in both directions, such as managing the parent of the D object. By adopting this management configuration, when an operation is performed on the object 110-i, it is possible to determine whether or not the object 110-i has a parent object 110-i. It is possible to prevent an object operation in a form ignoring the relationship from being performed.

As described above, the object relation management file 20 stores the data between the objects 110-i as shown in FIG.
When there is a hierarchical link relationship as shown in the FIG. 9
In accordance with the management form as (b), the this hierarchical Li
It will manage the link relationship.

Then, in synchronization with the data registration in the object relation management file 20, a hierarchical link relation is established.
If the parent object 110-i is located at the top of the list, "1" is set to the parent flag (of FIG. 3) of the object management book 40 described with reference to FIG. 3) is set to "1" to request display on the parent object name list, while if it is a child object 110-i, its parent flag (FIG. 3) is set to "0". At the same time, the list non-display flag (FIG. 3) is set to "0" to request non-display of the parent object name list.

FIG. 10 shows an embodiment of a processing flow of the display processing executed by the display processing mechanism of the data processing system 1, and FIG. 11 shows an example of a processing flow of the data processing executed by the data processing mechanism of the data processing system 1. An example is illustrated. Next, the operation processing of the present invention will be described in detail according to these processing.

The display processing mechanism of the data processing system 1 is as follows.
Via the terminal 2, at the top of the hierarchical link relationship
When a request to display a list of parent object names
As shown in the processing flow of FIG.
Then, the management information of the object management book 40 under the directory to be displayed in the list is read.
Then, one object management information is selected from the read management information.

Subsequently, in step 3, it is determined whether the list non-display flag of the object management information selected in step 2 indicates "1" or "0". If so, the process proceeds to step 4 to identify the object name. If it indicates "0", the process proceeds to step 5 to delete the object management information selected in step 2.

When the processing in step 4 / step 5 is performed, the process proceeds to step 6, where it is determined whether or not all the management information of the object management book 40 read in step 1 has been processed. If not, the process returns to step 2; if all have been processed, the process proceeds to step 7, where a list of the object names specified in step 4 is displayed.

As described above, when there is a hierarchical link relationship between the objects 110-i as shown in FIG. 12A, the list is not displayed according to the processing flow of FIG.
Display a list of object names with the display flag "1".
By displaying on the play screen, for example, FIG.
The list of object names of only the parent object 110-i located at the top of the hierarchical link relationship as shown in FIG.

When the list of parent object names is displayed on the display screen, the user designates the parent object 110-i to be operated and performs object operation ( object operation ).
Move, copy, delete, update, etc.) . Upon receiving this object operation instruction, the data processing mechanism of the data processing system 1 firstly starts, in step 1, the object management book 40 that manages the operation-specified object 110-i, as shown in the processing flow of FIG. Then, in step 2, by referring to the read object management book 40, it is determined whether or not the parent-child relationship is registered in the operation-designated object 110-i.

If it is determined in step 2 that the parent-child relationship has been registered, the process proceeds to step 3, and
Read an object relationship management file 20, by looking up the read object relationship management file 20, in the form of a child object 110 -i of the operation target
Object 110-i (object to be operated continuous
If 110-i is the parent, the child object
110-i, its grandchild object 110-i, ...
・) Is specified, and following the specified result, the following step 4 is performed.
In the object 110-i of the operation target, and the particular
Against the object 110-i, the process ends by performing the specified object operations. On the other hand, if it is determined in step 2 that the parent-child relationship is not registered, the process proceeds to step 5 and the operation target object 11
The designated object operation is performed only for 0-i, and the process is terminated.

As described above, the data processing mechanism of the data processing system 1 according to the present invention, together with the object 110-i to be operated by the user,
10 even for objects 110-i continuing in the form of a child -i, it is to process to continue to perform the specified object operations.

[0039] In the embodiments described above has been dealt with hierarchical link relationship of objects 110-i, it is also possible to handle the group relationship of objects 110-i. That is, as shown in FIG. 13A, the data registration mechanism of the data processing system 1 receives designation of grouping of the plurality of objects 110-i displayed on the display screen by interacting with the user. ,
As shown in FIG. 13B, the received group information is registered in the object management book 40. For example, upon receiving a designation indicating that the object A, the object B, and the object C are to be treated as the same group, an ID indicating that they are the same group is registered in the group ID column of the object management book 40.

When registered as the same group of objects 110-i in this manner, the display processing mechanism of the data processing system 1 has the same configuration as shown in FIG.
Clip the object 110-i of the group
In accordance with format as in this displaying as if binding that will be displayed on the terminal 2 the display screen, and displays that these objects 110-i are treated as the same group, is clicked with the mouse And the object 110-i displayed in the foreground is sequentially changed. That is, a configuration is adopted in which objects 110-i belonging to the same group are displayed as if they were bound with a clip, and an object 110-i belonging to the same group can be processed as if the user were turning over paper. .

When the object management book 40 manages the group relation defined between the objects 110-i, the data processing mechanism of the data processing system 1 specifies the object 110-i to be operated by the user. By referring to the object management book 40,
The object 110-i belonging to the same group as the operation-designated object 110-i is specified, and the object 110-i belonging to the same group is specified together with the designated operation target object 110-i. That is, processing is performed to execute the object operation.

[0042]

As described in the foregoing, in the data processing system of the present invention, rather than the object itself, since a configuration of managing hierarchical link relationship system is established between objects, application programs along with the program the burden of decreases, the processing of a unified interface becomes possible. When an object to be operated is specified, the operation is performed on the floor.
Since we are automatically applied to the other objects in the layer specific link relationship, the ability to perform data processing at high speed. Further, in realizing this processing, by managing the parent-child relationship between the objects in both directions, it is possible to prevent an object operation in a form ignoring the parent-child relationship.

[Brief description of the drawings]

FIG. 1 is a principle configuration diagram of the present invention.

FIG. 2 is an example of parent-child relationship management between objects.

FIG. 3 shows an embodiment of management data of an object management book / directory block.

FIG. 4 is an example of management data of an object relation management file.

FIG. 5 is an example of a parent-child relationship between objects.

FIG. 6 is an example of a parent-child relationship between objects.

FIG. 7 is an example of management data of an object relation management file.

FIG. 8 is an example of management data of an object relation management file.

FIG. 9 is an explanatory diagram of a management configuration of a parent-child relationship between objects.

FIG. 10 is an example of a processing flow of a display process of an object name list.

FIG. 11 is an example of a processing flow of an object operation processing.

FIG. 12 is an explanatory diagram of a display process of a parent object name list.

FIG. 13 is another embodiment of the present invention.

[Explanation of symbols]

1 data processing system 2 terminal 10 output control means 11 object management hand stage 1 3 data operation means 14 management unit 15 registers means 16 specifying unit 17 display control unit 110 objects

Continued on the front page (72) Inventor Tetsuya Mukai 98-2 Unoki-nu, Unoki-cho, Hebei-gun, Ishikawa Pref. Inside PFU Co., Ltd. (72) Inventor Yoshitaka Hosai 1015 Kamikodanaka, Nakahara-ku, Kawasaki-shi, Kanagawa Fujitsu Limited (72) Inventor Yoshiaki Tokumoto 98-2 Unoki-nu, Unoki-cho, Kawakita-gun, Ishikawa Pref. (72) Inventor Yumi Fujimoto 98-2 Unoki-nu, Unoki-machi, Unaki-cho, Kawakita-gun, Ishikawa Inside PFU (72) Inventor Mitsuhiro Katsuizumi 98, Unoki-nu, Unoki-cho, Hebei-gun, Ishikawa Pref. Inside PFU Co., Ltd. (72) Inventor Maki Sakuta 1015 Kamiodanaka, Nakahara-ku, Kawasaki City, Kanagawa Prefecture Fujitsu Limited ( 56) References JP-A-3-8076 (JP, A) JP-A-59-60660 (JP, A) SX / G icon desktop manual Edition 16 / 16A 50S P-2302-IB for V16, Fujitsu Limited Published, first edition in January 1992, Pages 180-192 (58) Fields investigated (Int. Cl. ⁷ , DB name) G06F 9/44 530 G06F 9/06 530

Claims (1)

(57) [Claims] 1. According to a hierarchical directory structure
Data processing system for managing a plurality of objects Mudea
Therefore, for each directory, (a) objects independent of the directory
Was provided in the form, the object of the subordinate those of the directory
For each port, information indicating whether it is a parent or child and a list
The first to manage information indicating whether or not to be displayed
And (b) objects under the directory are stored.
Second managing means for managing that location, independent of the underlying object (c) the directory
In provided form, the link destination of the object is the link source
Object of the link source while allowing
One or more objects etc. to link the object
Information about the object and its link
Whether to link as objects of Kakarigako parent of Obuji
Information that is linked as a project
3 management means, and the first management means indicates that the list is to be displayed.
List display means for displaying only the listed objects
And a plurality of objects displayed by the list display means.
Select one of the objects and select the object
By referring to input means for designating an operation for a project and the first management means, the input means
Therefore, the selected object is the parent object
Judge whether the object is a parent object or not.
By referring to the third management means, the selected object
An object that is hierarchically connected to the object in the form of a child
Specifying means for specifying the object, the object selected by the input means,
For the object specified by the specifying means,
By performing the operation specified by the input means, the data
A data operation means for executing data processing.