JPH05298163A - Data processor - Google Patents

Abstract

PURPOSE:To provide a data processor capable of copying by fetching data whose applications are different by a simple operation. CONSTITUTION:Floppy disk control information is composed of a name 101, a detection method 102 for deciding a floppy disk and a converter 103 for converting the data form of the floppy disk to the data form under a cabinet, 16. When a floppy disk 17 is opened, the data control information of the floppy disk is converted into the data control information of the cabinet, 16 when the detection method 102 is fit for the disk. In the case of a copy, the substance of data is converted by the converter 103 and it is copied to a copy destination.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a data processing apparatus in which any user can operate any data in a plurality of computer systems used by a plurality of users.

[0002]

2. Description of the Related Art Conventionally, in a plurality of computer systems used by a plurality of users, user data is generated in various formats, that is, data formats, for each computer system, and this data is stored in, for example, a floppy disk, an optical disk, or the like. , Is stored on a magneto-optical disk or hard disk. Therefore, in order for a user to capture, copy, and use different data in another computer system, for example, the application must perform an operation of converting the data format so as to be suitable for the application.

[0003]

However, in the above-mentioned conventional computer system, when the application captures, copies, and uses different data, the user has to perform the conversion operation of the data format, so that the work efficiency is high. There is a problem that it is bad.

In view of the above-mentioned conventional problems, an object of the present invention is to provide a data processing device capable of taking in and copying data of different applications by a simple operation.

[0005]

In order to achieve the above object, the present invention provides a data processing apparatus having a plurality of applications for generating or editing data by a plurality of users' operations in a plurality of computer systems,
A plurality of data management means for managing the data by the plurality of applications, a determination means for determining the format of the data generated or edited by the plurality of applications, and a data for the second application for the data by the plurality of applications. A conversion means for converting the data format of the second application discriminated by the discrimination means into a data format suitable for the processing of the first application when copying into the data management means. To do.

[0006]

According to the present invention, when the data generated or edited by the second application in another computer system is taken into the own computer and copied, the format of the data is discriminated and the first of the present invention is realized. Is converted to fit the application data format.
Therefore, there is no need for the user to perform a data format conversion operation, and therefore data different in application can be captured and copied by a simple operation.

[0007]

Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 is a block diagram showing a schematic configuration of an embodiment of a data processing device according to the present invention. The CRT 1 is used to display a document being edited, various messages, menus, etc., and the image data displayed on the screen of the CRT 1 is expanded on the video RAM (VRAM) 2. The bit move unit (BMU) 3 controls data transfer between memories and between the memory and each device. The keyboard 4 is provided with various keys for editing a document and the like, and the pointing device (PD) 5 is used for pointing an icon or the like on the screen of the CRT 1.

A central processing unit (CPU) 6 controls the entire apparatus, and in particular, as will be described later, document editing, data copying of a floppy disk having different applications, and
Execute programs such as data destruction and error handling programs. The program of the CPU 6 is stored in the read-only memory (ROM) 7, and the random access memory (RAM) 8 has a work area when the CPU 6 executes the program, a temporary save area for error processing, and the like. Hard disk drive (HD
D) 9 and floppy disk drive device (FDD) 10
Is used to store application programs and data as described below. The network interface (Net-I / F) 11 performs data control and diagnosis on the network in order to transfer data with another data processing device via the network. Further, these members 2 to 11 are connected to each other via an address bus and an input / output (I / O bus) 12 composed of a data bus and a control bus.

In this embodiment, a program for managing data and giving a user an operating environment for referring to, updating, saving, and executing the data is called a "desktop". As an actual display example, a plurality of windows 1 are displayed on the window system as shown in FIG.
Built in 5, 16, 22-24, this window 1
Data of 5, 16, 22 to 24 are operated via input means such as the keyboard 4 and the pointing device 5.

Next, various concepts of the desktop will be described with reference to FIG.
Is the user's data environment. The room 13 shows a space that provides an environment owned by one user, and also shows a window as a user interface which is an entry for the user to use the desktop. The office 14 is a space formed by a set of local rooms 13.

In addition, a plurality of offices 1 can be used without exchanging data due to the difference in architecture from the domain.
4 shows a set of offices 14 capable of moving, copying, executing, etc. of data across four areas. For example, with a physical file system of one computer as one office 14, there are a plurality of rooms 13 for each office 14 distributed to a plurality of computers connected via a network.

One user has his / her room 13 in an appropriate office 14, enjoys a desktop service in the room 13, and operates an operation object described later to start an application and process data. It can be performed. In addition, the user can access the room 13 of another user in the same office 14 other than his / her room 13 or the room 13 of another office 14, and within the permitted range, his / her room 1
The same operation as in the case of 3 can be performed. further,
If the rooms 13 are in the same domain, it is possible to move, copy, or execute data across a plurality of rooms 13.

Here, the operation object refers to data and a set of data represented as an icon on the desktop in order to provide access means for the user's desktop management system.

FIG. 3 is a screen showing the room 13 of the user, and operation objects are displayed in the room 13. The desktop 15 is used to manage registration and activation of an application, which is one of the functions of the desktop, and an operation of opening the desktop 15 causes a window including an object in the desktop 15 to be described later to be displayed.

The cabinet 16 indicates a top-level entry of a mechanism for managing the data created by the application in a hierarchical structure.
The open operation of the cabinet 1 as described later
A window containing the objects in 6 is displayed. The public shelf 22 indicates an object that manages the publication of data of other users or user groups (described later), and the trash box 2
Reference numeral 3 denotes an object that manages the discarding of data. The exit 24 indicates an object used as a means of accessing another user's room 13 or office 14, and an opening operation of this exit 24 causes the exit 24 to be described later.
A window containing the objects in is displayed.

As shown in FIG. 3, in addition to the operation objects 15, 16, 22 to 24, a title 25 indicating the name of the user and the title of the window being displayed.
And operation buttons 2 for instructing operations in the window
6, a help button 27 for instructing the help content of the operation, and a scroll bar 28 for scrolling the icon outside the window are displayed.

FIG. 4 shows objects in the desktop 15, which are displayed as objects for the application 29 to operate (start) the application.
Each operation of the application 29 will be described later. Figure 5
Indicates an object in the cabinet 16, and a binder 20 and data 18 are displayed. The binder 20 indicates a node under the cabinet 16 that manages data in a hierarchical structure, and when the binder 20 is opened, a window including the binder 20 and the data 18 in the binder 20 is displayed. The data 18 is an object that represents data created by an application and is used to manipulate the content of the data. In addition, this data 1
The operation of 8 will be described later. Further, the screen showing the windows in the binder 20 has the same contents as in the case shown in FIG.

FIG. 6 shows the objects in the open shelf 22. The disclosure tray 33 is used when the user performs a disclosure operation.
Other users to be published or a set of users (hereinafter,
User group. ), And a window including the public object 34 as shown in FIG. 7 is displayed by the opening operation of the public tray 33. The public object 34 shown in FIG. 7 indicates the object of the binder 20 and the data 18 of the user who has performed the public operation, and the object of publicizing the public object 34 according to the attribute of the public tray 33 in which the public object 34 exists. The users or user groups that are to be determined. Although not shown, the public object 34 includes the cabinet 16.

FIG. 8 shows an operation object in the exit 24, which includes the door 35, the office 14 and the floppy disk 17.
Objects are displayed. The door 35 is an object indicating an entry of another user into the room 13, and a user name is displayed. By this opening operation of the door 35, the room 13 of the user indicated by the door 35 is displayed, and the cabinet 16 in which the user of the room 13 has performed the public operation for the user or the user group including the user, the binder 20, and the data. 18 is displayed. Then, the user can access the data of the user by manipulating the published object.

The office 14 shown in FIG. 8 is an object indicating an entry to another office 14, and the office name is displayed. Then, by the opening operation of this office 14, an object indicating the entry to the room 13 included in the office 14, that is, the door 35.
Is displayed. The operation on the door 35 is as described above. Further, the floppy disk 17 shown in FIG.
This is an object that manages a floppy disk, and an object 19 included in the floppy disk 17 is displayed as shown in FIG. 9 by the opening operation of the floppy disk 17.

Next, the management information necessary for the desktop to operate will be described. The desktop management information includes data information 36, application information 42, and user information 54 as shown in FIGS. 10 to 14, respectively. , Office information 58 and group information 65. FIG. 10 shows data information 3 of this desktop management information.
6 is used to register and manage the format and type of the data 18 created by the application 29 shown in FIG. 4, and the following information 37 to 37 for each data format is used. 40. The data format ID 37 is an independent number assigned to each data format, and the extension 38 is information of three characters added to the end of the file name when creating a file of the data 18 of that data format. Is. The icon file name 39 is used when displaying the data 18 in the binder 20, and a plurality of icon file names 39 are registered depending on the display format.

FIG. 11 shows application information 42 regarding the application 29 managed by the desktop. Based on the application information 42, the object of the application 29 is displayed in the window of the desktop 15 which will be described later, and is composed of the following information 43 to 49 for each registered application 29. The application ID 43 is an independent number assigned to each application 29, and the execution module name 44 is a program name used when executing the application 29. The application name 45 is the name of the application 29, and the icon file name 46 is used when displaying the application 29 as an icon.

The processing list 47 is the data 18 that can be processed.
Format ID 37 (FIG. 10) and a processing list thereof, in which a processing code and a name for displaying the processing are one item. The processing list 47 is
It is blank if the application 29 does not create the data 18. Information 48 in processing list 47
Is the top entry of the processing list 47 for each format ID 37, and indicates the default processing of the application 29. This entry 48 is used by the application 29 without specifying the data 18 to be processed.
Shows the process when is started, and the format ID 37
And its processing list. The information 49 is data 18 to be processed when the processing in the processing list 47 is performed.
Indicates that the data 18 is required when it is “◯”, unnecessary when it is “×”, and either is not necessary when it is blank.

FIG. 12 shows a table of user information 54 for managing users of the system in which one desktop operates. This user information 54 is the following information 55-57.
It is composed by. The user ID 55 is an independent number given to each user, and the user information 56 in a narrow sense is arbitrary information about the user such as the name of the user.
The user's room directory 57 is the user's room 13
Is the location (directory path).

FIG. 13 shows a table of office information 58 for managing the office 14 in which another desktop connected via a network or the like is operating.
Each of the four items is composed of the following information 60 to 63. The office ID 60 is an independent number assigned to each office 14, and the host name 61 is the host name where the office 14 is located. The office name 62 is the name of the office 14 existing in the host, and the domain 63
Is the domain of the host to which the office 14 belongs.

FIG. 14 shows a table of group information 65 for managing a group of a plurality of users in order to represent the range of users who restrict the reference and update of the data 18, and the following information 66 for each group, It is composed of 67. The group ID 66 is an independent number assigned to each group, and the user ID 67 includes the user IDs 55 of one or more users who belong to the group.

Next, the cabinet management information will be described. FIG. 15 shows a table of the data management information 68, and this data management information 68 is a file for managing the individual data 18 in the binder 20 shown in FIG. This data management information 68 also exists for each binder 20 below the cabinet 16 (including the trash box 23).
It has the following information 69-88 for one data. The object type 69 indicates the type of data (binder 20, data 18, open shelf 22, open tray 33), and the file name 70 indicates the content of the data. Format ID 7
1 is a data format ID 37, and creator ID 72 is an application 29 that created the data.
Application ID 43 of.

The kanji name 73 is the kanji name of the data, and the size 74 is the size of the data in byte units, and is the total size of the data when the data is composed of a plurality of files. The registration date 75 is the date when the data was newly created, the update date 76 is the date when the data was last modified, and the reference date 77 is the date when the data was last referenced. Owner user I
D78 is the user ID 55 indicating the owner of the data,
The owner group ID 79 is a group ID 66 indicating the owner of the data. The reference user ID 80 is the user ID 55 that last referred to the data, and the updated user ID 81
Is the user ID 55 that last updated the data.

At the accelerator level 82, reference to data and permission / non-permission of update operation are set separately for the owner user ID 78 of the data, the group ID 66 and other users. The domain 83 is the domain of the office 14 in which the data was created or updated.

The disclosure destination user ID 84 is the user ID 55 to be disclosed when the data is the disclosure tray 33 where the data is disclosed to other users, and the disclosure destination group I
D85 is the group ID of the disclosure target when the data is the disclosure tray 33 where the data is disclosed to other groups.
66. When the data is the public object 34, the public copy deadline 86 is a setting content that restricts the copying operation of the data to the user of the publication destination, and the public deadline 87 is the public object when the data is the public object 34. The publication operation of 34 is a valid time limit. Further, as shown in FIG. 46, the data discard deadline 88 is a deadline for automatically discarding data in the trash box 23 after a certain period of time has passed.

FIG. 16 shows a table of the open data management information 90 showing the states of the binder 20 and the data 18 which are currently opened in the room 13 of each user. There is one open data management information 90 for each room 13 and is composed of the following information 91 to 94. The file name 91 is the file name of the data,
The user ID 92 is the user ID 55 of the user who is currently opening the data. The access level 93 is a flag indicating whether the data is opened at the reference-only accelerator level 82 or the update accelerator level 82, and the date 94 indicates the date and time when the data was opened.

FIG. 17 shows the floppy disk management information. This floppy disk management information is included in the floppy disk registration file, and is composed of the following information 101 to 103 for each floppy disk. Name 1
01 is the name of the floppy disk, and as an example, the name 104 shows the floppy disk information of Microsoft MS-DOS, and the name 105 shows the floppy disk information of the word processor.

The detection method 102 is, for example, a process name or a function name for determining the floppy disk. The data converter 103 is, for example, a process name or a function name for converting the data format of the floppy disk into the data format under the cabinet 16 or converting the data format under the cabinet 16 into the data format of the floppy disk. Whether to convert the direction is given by a parameter.

FIG. 18 shows the data management information of the floppy disk, which is composed of the following information 106 to 112 for each binder 20 of each floppy disk. File type 106 indicates the type of data, file name 1
07 shows the content of the data. Also, like the data management information 68 shown in FIG. 15, the Chinese character name 108 is the Chinese character name of the data, and the size 109 indicates the size of the data in bytes.

The registration date 110 is the date when the data is newly created, the update date 111 is the date when the data was last changed, and the accelerator level 112 refers to the data and permits or prohibits the update operation. The non-permission is set separately for the data owner user ID 78, the group ID 66, and the other users.

FIG. 19 shows the binder 2 in the cabinet 16.
An operation screen for opening 0 is shown, on which a cursor 96 designated by the pointing device 5 is displayed.
A mark 97 indicating a button operation of the pointing device 5 is displayed for the purpose of explaining the operation. In this mark 97, "★" indicates one click of the button, and "★"
"★" indicates two clicks of the button, "☆" indicates that the button was pressed, and "☆☆" indicates that the button was released. The opening operation of the binder 20 will be described. When the cursor 96 is moved to the icon of the binder 20 and the button is clipped by two, a window showing the contents of the binder 20 is displayed. This open operation is common to all operation objects.

Next, the open process of the binder 20 will be described with reference to FIG. First, in step S1, the data management information 6 of the binder 20 whose button is clicked 2 times 6
8, the icon file is read from the format ID 37 and the data information 36 of the data management information 68 in the subsequent step S2, and the icon is displayed on the window in step S3. In steps S1 to S4, these processes are performed for all the entries of the data management information 68, and the process ends. It should be noted that this process is common to the cabinet 16 and the open shelf 22, and the desktop 1
5 and the opening process of the exit 24 will be described later.

FIG. 21 shows the cabinet 16 and the binder 20.
A copy operation screen of the data 18 during the period is shown. This copy operation is performed by moving the cursor 96 to the icon of the data 18 at the desired copy source, moving to the window of the desired copy destination cabinet 16 or binder 20 while pressing the button, and releasing the button. Be seen.

Next, referring to FIG. 22, the cabinet 1
The copy processing of the data 18 in 6 is performed. First step S
When the button is pressed on the copy source icon in 5, the data management information 68 of the data 18 is obtained from the binder 20 in which the copy source data 18 exists. Then, in step S6, if the copy source data 18 is the public object 34 and the public copy restriction 86 is set from the data management information 68, the copy prohibition is displayed in step S7, and the process is stopped. To do.

On the other hand, if the above conditions are not satisfied, the process proceeds to step S8, and if the button is released at the copy destination, the process proceeds to step S9. In step S9, it is checked whether or not copying is possible by checking the disk capacity and the like. If copying is not possible, step S9
An error (copy not possible) is displayed in 10 and the processing is stopped.

On the other hand, if copying is possible, the data management information 6 obtained in advance with respect to the data management information 68 of the binder 20 of the copy destination in step S11.
8 entries are added, and in the subsequent step S12, the file which is the content of the data 18 is copied, and the process is ended.

FIG. 23 shows an operation screen for opening the floppy disk 17 in the cabinet 16. This is almost the same as the operation screen for opening the binder 20 in the cabinet 16 described above (FIG. 19), and the open processing is shown in FIG. That is, step S2
The registration file of the floppy disk 17 whose button is double-clicked in 1 is read to obtain the floppy disk management information as shown in FIG. 17, and in the following step 22, a method 102 for detecting one floppy disk management information is obtained.

Next, in step S23, if the detection method 102 is successfully adapted to the data format of the floppy disk in the FDD 10, step S26.
Go to step S24 if not successful. In steps S22 to S24, the detection method 102 is checked for all entries of the floppy disk management information, and if none of the detection methods 102 is successfully matched, it is determined that there is no floppy disk 17 that can be handled. After displaying (step S25), this open processing is terminated.

On the other hand, in step S26, the data management information of the root directory of the floppy disk 17 (see FIG.
8) is obtained, and in the subsequent step S27, this data management information is converted into the data management information 68 of the cabinet 16 as shown in FIG. Then, in step S28, the format ID 37 of the obtained data management information 68 is
Then, the icon file is read from the data information 36, a window is generated in step S29, and the icon is displayed. In addition, this processing is performed for all the entries of the data management information 68 in the loop of steps S28 to S30, and the processing ends. The process for opening the binder 20 of the floppy disk 17 is the same as the case shown in steps S26 to S30.

FIG. 25 shows an operation screen for copying the data on the floppy disk 17 to the binder 20, which is almost the same as the screen (FIG. 21) described above. FIG. 26
Indicates the copy processing, and when the button is released and the copy destination is determined in step S31,
In step S32, the disk capacity and the like are checked to determine whether copying is possible. If copying is not possible, a message to that effect is displayed in step S33, and this copying process ends.

If copying is possible, the conversion method (converter 103) is obtained from the floppy disk management information in step S34, and the copy source file name is obtained from the floppy disk management information in step S35 to convert the substance of the data. To do. Then, step S36
Data management information 68 of the binder 20 of the copy destination
On the other hand, the entry of the data management information 68 obtained in advance is added, and the conversion data is copied in step S37, thereby ending this processing. It should be noted that substantially the same processing is performed when copying the data under the cabinet 16 to the floppy disk.

Next, the activation of the application will be described. When the user operates the application 29 or the data 18 managed on the desktop, the application is activated. This application is started by executing the application execution module name 44
(FIG. 11), followed by the file name 70 of the data 18 to be processed, the format ID 37, and the character string designating the processing method in the processing list 47, which is executed (for example, / usr / local / bin / ezps / ezps-f 012
-me).

First, when the desktop 15 in the room 13 is clicked twice, the desktop 15 is opened and the application 29 already installed is displayed.
Is displayed. The open process of the desktop 15 is completed by reading the icon file after obtaining the application information 42 and displaying the icon on the window. When the data 18 is opened by the application, the entry of the opened data 18 is added to the open data management information 90 of the room 13 in which the data 18 exists. Further, when the data 18 is closed by the application, the entry of the opened data 18 in the above-mentioned open data management information 90 is deleted.

Next, with reference to FIGS. 27 to 38, the process of starting an application on the desktop will be described for each user operation. In FIG. 28, the application 29 in the desktop 15 is displayed in the operation screen shown in FIG.
The start processing when clicked is shown. Step S41
In step S42, the application information 42 of the application 29 clicked on in step S42 is obtained, and the format ID at the head of this application information 42 is obtained.
37 and the processing code of the default processing 48 are passed to the application 29, and the application 29 is activated.

FIG. 30 shows a starting process when the application 29 in the desktop 15 is selected on the operation screen shown in FIG. 29 and various open processes in the list 98 are selected. If the "operation" button 26 is not selected in step S51, another process is performed in step S52, and if the "operation" button 26 is selected, the process proceeds to step S53 and thereafter. When the application 29 is selected in step S53, step S5
In 4, the application information 42 of this application 29 is obtained.

Then, in step S55, the format I of the top entry of the application information 42 is set.
D37 is selected as the default, and the process name of the process list 47 of this format ID 37 is displayed as the pull-down list 98. In this list 98, "processing data required" 49 shown in FIG. 11 is not checked and displayed for functions that require already created data, such as printing functions. When one item in the list 98 is selected in step S56, step S57.
In step 1, the already-selected format ID 37 and the processing code corresponding to the selected item are passed, and the already-selected application 29 is activated.

FIG. 31 shows an operation of dragging the application 29 in the desktop 15 and dropping it in the cabinet 16 (or the binder 20). In this case, similar to the processing shown in FIG. 28, the application information 42 of the dragged / dropped application 29 is obtained, and the format I at the beginning of the application information 42 is obtained.
D37 and the processing code of the processing list of the default processing 48 are passed to the application 29 and activated.

FIG. 32 shows an operation of double-clicking the data 18 in the cabinet 16 (or the binder 20).
FIG. 33 shows an application starting process by the operation. Data 1 clicked two times in step S61
The creator ID 72 and the format ID 37 of the data are obtained from the data management information 68 of No. 8. Next, in step S62, the application information 4 having the same application ID 43 as this format ID 37
In step S63, the format ID 37, the process code of the default process 48 of the format ID 37 of the application information 42, and the file name 70 of the data 18 are passed to the application 29 and activated.

FIG. 34 shows an operation of selecting the data 18 in the cabinet 16 (or the binder 20) and selecting various open processes from the list 98, and FIG. 35 shows an application starting process by the operation. Step S
If the "operation" button 26 on the window is not selected in 71, another process is performed in step S72, and if the "operation" button 26 is selected, the process proceeds to step S73 and the subsequent steps. When the data 18 to be processed is selected in step S73, the format ID 37 and creator ID of this data 18 are selected in step S74.
72 is obtained from the data management information 68, and an entry having the same application ID 43 as this creator ID 72 is obtained from the application information 42.

Then, in step S75, the name of the processing list 47 corresponding to the format ID 37 obtained from the entry of the application ID 43 is displayed as a pull-down list 98. Next, when one item of the list 98 is selected in step S76, the file name 7 of the data 18 is selected in step S77.
0, format ID 37 already obtained, and list 9
The processing code corresponding to the item selected from 8 is passed to the application 29 and activated.

FIG. 36 shows an operation of dragging one data 18 in the cabinet 16 (or the binder 20) and dropping it on the application 29 in the desktop 15, and FIG. 37 shows an application starting process by the operation. When the data 18 is dragged, the file name 70 and the format ID 37 of this data 18 are obtained from the data management information 68 in step S81. Then, if the dragged data 18 is located in the application 29 of the desktop 15 in step S82, the process proceeds to step S83 and thereafter, and if not, the process directly proceeds to step S86.

In step S83, the application information 42 of the located application 29 is obtained, and in the following step S84, the format ID 3 of the data 18 to which the application 29 is dragged is obtained.
If No. 7 can be processed, the process proceeds to step S85, and if not, the process directly proceeds to step S86. Step S8
In 5, the display method is changed by, for example, highlighting the icon display of the application 29 to inform the user that the application 29 can process the dragged data 18.

Then, when the dragged data 18 is dropped in step S86, step S86 is executed.
Go to 87 or below, and if not dropped, step S
Return to 82. In step S87, it is checked whether or not the data 18 is dropped on the processable application 29. If it is dropped, the process proceeds to step S88, and if it is not dropped, the process ends. In step S88, the format ID 37 corresponding to the application ID 43 and the processing code of the default processing 48 are obtained from the application information 42, and the format I
The D37, the processing code, and the file name 70 of the data 18 are passed to the application 29 and activated.

FIG. 38 shows an operation of dragging a plurality of data 18 in the cabinet 16 (or the binder 20) and dropping them on the application 29 in the desktop 15. In the process in this case, the format ID 37 of each dragged data 18 is obtained as in the process shown in FIG. And the dragged data 18
Is located in the application 29 of the desktop 15, the application information 42 is searched, and when the application 29 can process the format ID 37 of the dragged data 18, the application 2 is searched.
The display method is changed by, for example, highlighting the icon display of 9 to notify the user that this application 29 can process the dragged data 18.

Then, a plurality of data 18 dragged onto the highlighted application 29 is displayed.
Is dropped, the application ID 43 of the application 29 and the format ID 37 of the data 18
The application information 42 is searched from the execution information 44, the execution module 44 corresponding to the application ID 43, the format ID 37, the processing code of the default processing 48, and the file names 70 of the plurality of data 18 are passed to the application 29 and activated.

Next, the operation and the processing when the "publication operation" is performed will be described with reference to FIGS. here,
In this embodiment, the cabinet 16 in the user's room 13, the binder 20 and the data 18 are not normally permitted to be referred to or updated by other users. And
An operation that allows a user to refer to or update the cabinet 16 owned by the user, the binder 20 and the data 18 to another user is called a “public operation”, and this “public operation” is performed. The cabinet 16 that has been viewed or performed, the binder 20 and the data 18 are referred to as a public object 34.

First, the disclosure tray 33 is created on the disclosure shelf 22 for each user or group to be disclosed. As shown in FIG. 39, this specific creation method is performed by the user selecting the new creation button 26a on the window on the public shelf 22 and displaying the name or the name of the user or group to be published in the inquiry input window 99. User ID
55 or a group ID 66 is input. Next, as shown in FIG. 40, the public tray 33 of the user or group to be published is opened, and like the copy operation of the data 18 between the binders 20, the icon of the public object 34 to be published is dragged to open the public tray 33. Drop it on. The public object 34 dropped by this operation is displayed on the public tray 33, thus indicating that the “public operation” has been performed.

In this embodiment, the public object 3
It is possible to set a setting for restricting copy operations of other users to 4, and a time limit for permitting disclosure. This specific setting method is as shown in FIG. 40. When the user presses the operation button 26 of the public tray 33 and then clicks the public object 34 to be set, the inquiry input window 100 is displayed. 10
The setting is completed by inputting the public copy restriction 86 and the public time limit 87 for 0. If the setting has already been completed, the setting content is displayed in the setting item column of the input window 100.

FIG. 41 shows the process of creating the open tray 33 on the desktop 15. When the new creation button 26a on the window is selected, the input window 100 for inputting the disclosure target is created and displayed in step S91, and the user waits for input (step S92). When the user name is input, the user information 54 is searched from this user name and the user ID 5
5 (steps S93, S94), user ID
When 55 is input, the user information 54 is searched from this user ID 55 to check whether this user ID 55 exists (steps S95, S96).

When the group name is input, the group information 65 is retrieved from this group name to obtain the group ID 66 (steps S97 and S98). When the group ID 66 is input, the group information 66 is converted from the group information 65. Is checked to see if this group ID 66 exists (steps S99 and S10).
0).

In step S101, the user ID 55 is set.
Alternatively, if the group ID 66 exists, step S1
If it does not exist, the process is stopped.
In step S102, the data management information 68 of the open shelf 22 is displayed.
A new entry for the publication tray 33 is created, and the user ID 55 or the group ID 66 is substituted for the publication destination user ID 84 or the publication destination group ID 85. Then, in the subsequent step S103, the newly created public tray 33 is displayed, and the process ends.

FIG. 42 shows the "publication operation" processing on the desktop 15. When the public object 34 to be published is dragged, the data management information 68 of the dragged public object 34 is dragged in step S111.
To get If the dragged public object 34 is dropped on the public tray 33 in step S112, the process proceeds to step S113 and subsequent steps, and if not dropped, the process branches to step S115 to perform other processing.

In step S113, a new public object 34 is added to the data management information 68 of the public tray 33.
And the data management information 68 obtained as described above.
Is substituted, and in the subsequent step S114, the dragged public object 34 is displayed on the window of the public tray 33, and the processing is ended.

FIG. 43 shows a process of setting a public copy restriction and a public deadline for the desktop 15. Step S1
If the operation button 26 on the window is selected in step 21, the process proceeds to step S123 and thereafter, and if not selected, the process branches to step S112 to perform another process. In step S123, selection input of the public object 34 is waited, and when the public object 34 is selected, step S1
At 24, the data management information 68 of the selected public object 34 is obtained.

Then, in step S125, the inquiry input window 100 is created and displayed, and the public copy restriction 86 and the publication deadline 87 are displayed in the input field by the data management information 68 obtained as described above, and step S126.
Wait for the input at. Then, in step S127, the input public copy restriction 86 and the public deadline 87 are substituted into the data management information 68, and the data management information 68 for which this setting has been completed is transferred to the data management information 6 in the publication tray 33.
Then, this process is terminated.

Next, with reference to FIG. 44, an operation and a process when a user accesses data of another user will be described. In this case, first, when the user opens the exit 24 in his / her room 13 as shown in FIG. 3, another user's room 1 in his / her office 14 as shown in FIG.
A door 35 representing 3 and another office 14 are displayed. When another office 14 is opened in this display state, the user's door 3 of the opened office 14 is opened.
5 is displayed again. Then, the desired user's door 3
Room 5 opened when 5 is opened
The public object 34 that the user has performed the public operation for is displayed.

The public object 34 can be operated by the same operation as that for the object in the user's room 13. However, when the public copy restriction 86 is set for the public object 34, the operation of copying the content of the public object 34 is prohibited, and the public deadline 87 is set for the public object 34. In some cases the publication deadline is 87
The published object 34 whose time has passed is not displayed on the window.

FIG. 44 shows the exit 2 on the desktop 15.
4 shows the open process. When the exit 24 is opened, the names of other users and the office 14 are obtained from the user information 54 and the office information 59 in step S131, and the door 35 is displayed on the window based on the user information 54 and the office information 59 in step S132. The office 14 icon is displayed, and the input is awaited in step S133. When the open operation is performed on the office 14, the process branches from step S124 to step 135, and when the open operation is performed on the door 35, the steps S136 to S13.
Branch to 7 or less. If the open operation is not performed for either of these, this processing is ended.

When the open operation is performed on the office 14, the host name 62 is obtained from the office information 59 in step S135, and the user information 54 is requested by requesting the user information 54 from the opened host. Then, the process returns to step S132, the icon of the door 35 is displayed on the window, and the input is awaited in step S133.

When the opening operation is performed on the door 35, the data management information 68 of the open shelf 22 of the user of the door 35 opened in step S137 is obtained, and in the following step S138, the user who is operating is opened. It is determined whether or not the open tray 33 exists, and if it exists, the process proceeds to step S139 and thereafter. Step S13
In 9, the data management information 68 of this open tray 33 is obtained,
In the subsequent step S140, only the public object 34 for which the publication time limit 87 has not elapsed is displayed on the window and the process ends. If there is no public tray 33 for the user who is operating in step S138, the process branches to step S141 to display that effect.
The process ends.

Next, the processing for discarding data will be described with reference to FIGS. 45 and 46. In this case, in order to discard the created binder 20 or data 18, the icon of the discarded binder 20 or data 18 is dropped in the window of the trash box 23 as in the copy operation between the binders 20. And data 1
The icon 8 moves to the trash box 23 window. Further, as shown in FIG. 46, the process of monitoring the discarding of this data is constantly operating on the desktop 15, and the moved binder 20 and data 18 are erased after being stored for a certain period of time.

This data discarding process will be described with reference to FIG. 45. When the icon of the data 18 is grabbed in step S151, the data management information 68 of the binder 20 in which the data 18 exists is obtained. When the button is released on the window of the trash box 23 in the following step S152, the process proceeds to step S153 and thereafter.

In step S152, the trash box 2
If the button is released on a window other than the window No. 3, this process ends. In addition, when the update disapproval is set for the data management information 68 in step S153, the discarding impossible is displayed in step S154, and this processing is ended. In addition, if the update disapproval is not set for the data management information 68 in step S153, the open data management information is searched for in step S155, and the data 18 is also discarded if it is open elsewhere. No is displayed and this process ends. In cases other than the above, the data 18 is copied to the trash box 23 in step S156, and when the copy process is normally completed, the process proceeds from step S157 to step S158 and thereafter. If the copy process does not end normally, the message "discard not possible" is displayed in step S154 and the process ends.

In step S158, the entry of the data 18 in the data management information 68 of the binder 20 in which the data 18 exists is deleted, and the file of the data 18 is deleted. Next, when the input window is displayed in step S159 and the time until discarding is input,
The time obtained by adding the time until the discard is added to the current time is substituted for the data discard deadline of the entry of the data 18 added to the data management information 68 of the trash box 23, and this processing is ended.

FIG. 46 shows the processing of the data discard monitoring process. In step S161, the data management information 68 of the trash box 23 is obtained, and the data disposal deadline 88 of one data is acquired.
Take out. Then, only when the data discard deadline 88 has elapsed in steps S162 and S163, the entry of the data is deleted to erase the file, and the trash box 23 is deleted in the loop of steps S162 to S164.
Check the data disposal deadline of each data. Then,
After a predetermined time has elapsed in steps S165 and S166, the process returns to step S161 and the same process is repeated.

The operation of registering the floppy disk 17, that is, adding a new floppy disk 17 to the floppy disk registration file will be described with reference to FIGS. 47 and 48. FIG. 47 shows the operation screen, and FIG. 48 shows the processing. When the "System" operation button 26b is pressed in FIG. 47, the submenu 1
20 is displayed, and "FD registration" of this submenu 120 is displayed.
Is selected, the floppy disk registration window 121 is displayed.

In the display state of the window 121, the floppy disk name 101 as shown in FIG.
Then, when the detection method 102 and the converter 103 are input and the cursor 96 is clicked on the “execute button” of the window 121, this input data is registered. It should be noted that the detection method 102 and the converter 103 are input and registered with either “function (function inside the desktop 15)” or “process (start a process different from the desktop 15)”.

The detailed processing is performed by the floppy disk registration window 121 in step S171 shown in FIG.
Is displayed, and in step S172 the button is pressed, and when the button is pressed, it is determined in step S173 whether the button is the help button 27 or not. If the help button 27 is pressed, the help process is performed in step S174 and the process returns to step S172. If the execute button is pressed without pressing the help button 27, the process proceeds from step S175 to step S176 and the subsequent steps. If any button other than the help button 27 and the execute button is pressed, this registration process ends.

In step S176, the floppy disk registration file is read, and if the name 101 is input in step S177 and this input name 101 does not overlap the registered name, the detection method 102 is input in step S178. Detection method 102
Exists, the converter 103 has been input in step S179, and when this input converter 103 exists, each input data is additionally written to the floppy disk registration file. Note that steps S177-1
If each data is not set in 79 or if the disc names overlap or if the detection or conversion method is an unknown method, a parameter error is displayed in step S150, and the registration process ends.

Therefore, according to the above embodiment, the floppy disk name 101, the detection method 102 and the converter 103 convert the data format of the floppy disk, which has different applications, so as to be adapted to the own application. For example, data of another computer system can be copied.

In the above embodiment, the case where the data on the floppy disk 17 is converted has been described as an example, but the data on a portable device such as an optical disk, a magneto-optical disk or a CD-ROM is converted. It is also possible to convert data of another computer system via a network by preparing and using a dedicated area for a hard disk.

[0087]

As described above, according to the present invention, in a data processing apparatus having a plurality of applications for generating or editing data in a plurality of computer systems by operations of a plurality of users, the data by the plurality of applications is A plurality of data management means for managing the respective data, a determination means for determining the format of the data respectively generated or edited by the plurality of applications, and a copy of the data by the plurality of applications in the data management means of the second application. In this case, the conversion means for converting the data format of the second application discriminated by the discriminating means into a data format suitable for the processing of the first application is included. You don't have to ® emissions can be duplicated capture by a simple operation of different data.

[Brief description of drawings]

FIG. 1 is a block diagram showing a schematic configuration of an embodiment of a data processing device according to the present invention.

FIG. 2 is an explanatory diagram showing the concept of a desktop.

FIG. 3 is an explanatory diagram of a screen showing a user's room.

4 is an explanatory diagram of a screen showing objects in the desktop of FIG. 3. FIG.

FIG. 5 is an explanatory diagram of a screen showing objects in the cabinet of FIG.

6 is an explanatory diagram of a screen showing objects in the open shelf of FIG. 3. FIG.

7 is an explanatory diagram of a screen showing objects in the open tray of FIG. 6. FIG.

FIG. 8 is an explanatory diagram of a screen showing an operation object in the exit of FIG.

9 is an explanatory diagram of a screen showing a floppy disk in the exit of FIG. 8. FIG.

FIG. 10 is an explanatory diagram showing data information of desktop management information.

FIG. 11 is an explanatory diagram showing application information of desktop management information.

FIG. 12 is an explanatory diagram showing user information of desktop management information.

FIG. 13 is an explanatory diagram showing office information of desktop management information.

FIG. 14 is an explanatory diagram showing group management information of cabinet management information.

FIG. 15 is an explanatory diagram showing data management information of cabinet management information.

FIG. 16 is an explanatory diagram showing open data management information of cabinet management information.

FIG. 17 is an explanatory diagram showing floppy disk management information.

FIG. 18 is an explanatory diagram showing data management information of a floppy disk.

FIG. 19 is an explanatory diagram showing an operation screen for opening a binder.

FIG. 20 is a flowchart for explaining binder open processing.

FIG. 21 is an explanatory diagram showing a data copy operation screen between a cabinet and a binder.

FIG. 22 is a flowchart for explaining a data copy process in a cabinet.

FIG. 23 is an explanatory diagram showing an operation screen when the floppy disk is opened.

FIG. 24 is a flowchart for explaining an open process on the operation screen of FIG. 23.

FIG. 25 is an explanatory diagram showing an operation screen when copying the data on the floppy disk to the binder.

FIG. 26 is a flowchart for explaining copy processing on the operation screen of FIG. 25.

FIG. 27 is an explanatory diagram showing an example of an operation screen for application startup processing on the desktop.

FIG. 28 is a flowchart showing a startup process on the operation screen shown in FIG. 27.

FIG. 29 is an explanatory diagram showing another example of the operation screen of the application startup process on the desktop.

FIG. 30 is a flowchart showing a startup process on the operation screen shown in FIG. 29.

FIG. 31 is an explanatory diagram showing another example of the operation screen of the application startup process on the desktop.

FIG. 32 is an explanatory diagram showing another example of the operation screen of the application startup process on the desktop.

FIG. 33 is a flowchart showing application starting processing on the operation screen of FIG. 32.

FIG. 34 is an explanatory diagram showing another example of the operation screen of the application startup process on the desktop.

35 is a flowchart showing an application starting process on the operation screen of FIG. 34. FIG.

FIG. 36 is an explanatory diagram showing another example of the operation screen of the application startup process on the desktop.

FIG. 37 is a flowchart showing application starting processing on the operation screen of FIG. 36.

FIG. 38 is an explanatory diagram showing another example of the operation screen of the application startup process on the desktop.

FIG. 39 is an explanatory diagram showing a method of creating a disclosure tray.

[Fig. 40] Fig. 40 is an explanatory diagram illustrating a method of setting a setting for restricting a copy operation of another user and a time limit for permitting the disclosure of the disclosure object.

FIG. 41 is a flowchart showing a process of creating a disclosure tray on the desktop.

FIG. 42 is a flowchart showing a “publication operation” process on the desktop.

[Fig. 43] Fig. 43 is a flowchart illustrating a process of setting a public copy restriction and a public deadline for a desktop.

FIG. 44 is a flowchart showing an exit opening process on the desktop.

FIG. 45 is a flowchart showing a data discarding process.

FIG. 46 is a flowchart showing processing of a data discard monitoring process.

FIG. 47 is an explanatory diagram showing a new registration screen for a floppy disk.

48 is a flowchart showing a new registration process on the screen in FIG. 47. FIG.

[Explanation of symbols]

 6 CPU 9 HDD 10 FDD 15 Desktop 17 Floppy disk 68 Data management information 101 Floppy disk name 102 Detection method 103 Converter

Claims (2)

[Claims] 1. A data processing apparatus having a plurality of applications for generating or editing data by a plurality of users' operations in a plurality of computer systems, wherein a plurality of data management means manages data by the plurality of applications, respectively. A discriminating means for discriminating the format of data generated or edited by each of the plurality of applications, and discriminating means for discriminating the data by the plurality of applications into the data management means of the second application. And a conversion unit that converts the data format of the generated second application into a data format suitable for the processing of the first application. 2. The data processing apparatus according to claim 1, further comprising registration means for registering a data format of the plurality of applications determined by the determination means and a data conversion method by the conversion means.