JPWO2010090286A1 - Information processing system, information processing apparatus, and information processing method - Google Patents

Abstract

The information processing system includes a plurality of information processing devices (CL) connected to each other so as to be able to perform data communication, and provides a virtual work space accessible by a plurality of users. Each information processing apparatus includes holding means (114), first display means (104, 106), second display means (104, 108), and synchronization means (116). The holding unit holds first information defining the virtual work space and the first object included in the virtual work space. Here, the first information is synchronized with other information processing apparatuses. The first display means displays part or all of the contents of the virtual work space to the user based on the first information. The second display means displays a second object that is associated with the first object included in the virtual work space and can be changed independently of the first object in response to a user operation. The synchronization unit synchronizes and holds the second information defining the instructed second object in response to an instruction to share the information processing apparatuses.

Description

  The present invention relates to an information processing system, an information processing apparatus, and an information processing method that provide a virtual work space in which a plurality of users can work interactively.

  In recent years, virtual work spaces (hereinafter also referred to as “work spaces”) have been proposed to support intellectual creation work by a plurality of users (for example, Japanese Patent Laid-Open Nos. 10-051581 and 10-126758). Issue gazette).

  This workspace is a virtual whiteboard-like space, and the user can interactively input materials such as handwritten characters, images, and photographs (hereinafter also referred to as “objects”) in this space. Can be operated. Such a workspace facilitates intellectual creation work (thinking and communicating with other members) within an individual or group.

  By the way, in the work space, unlike a physical whiteboard or memo pad, it is possible to provide a work space in a wider range than the range actually viewed by the user. Note that the range browsed by the user can be freely expanded or reduced as necessary, so that writing or the like can be performed even in a narrow area. Therefore, even in a vast range of work space, the user can work without stress.

  As a specific usage scene of such intellectual creation work, the subject matter that the user has conceived is input as objects one after another, and these inputted many objects are classified (categorized) or associated with each other. Thus, there are cases where information is organized and connected to new ideas (typically KJ method). More specifically, in order to categorize, the user brings objects that are considered to belong to the same category close together or adds the same display attribute to each object (typically the same color To trim each object. Further, in order to associate the objects, a group consisting of a plurality of objects belonging to the same category and an object considered to belong to the category are connected with a line.

JP-A-10-051581 JP-A-10-126758

  By the way, considering the usage of actual workspaces, workspaces are used by various users to write around a vast space, so it is efficient and appropriate for one person to organize information. It may not be possible. Therefore, there is a need to share information among a plurality of members and utilize the knowledge of each member to organize information.

  This sort of information is done by actually checking or editing the objects placed on the workspace (typically tagging objects, changing colors, grouping, etc.) By doing work, it can be made more efficient.

  If an operation such as editing is directly performed on the object arranged on the workspace from the beginning of the information organization work, the work of other members may be hindered.

  On the other hand, ultimately, there is a need to share the results of information organization with other members.

No workspace satisfying such needs has been proposed in the prior art.
Accordingly, the present invention has been made to solve such a problem, and its purpose is to organize information while reducing the influence of each user on the work of other users with respect to objects on the workspace. By providing an information processing system, an information processing apparatus, and an information processing method that can easily share the work results finally obtained by the work of organizing information with other users is there.

  An information processing system according to an aspect of the present invention provides a virtual work space accessible by a plurality of users. This information processing system includes a plurality of information processing devices connected to each other so as to be capable of data communication. Each of the plurality of information processing apparatuses includes a holding unit, a first display unit, a second display unit, and a synchronization unit. The holding unit holds first information defining the virtual work space and the first object included in the virtual work space. Here, the first information is synchronized with another information processing apparatus. The first display means displays part or all of the contents of the virtual work space to the user based on the first information. In response to a user operation, the second display means displays a second object that is associated with the first object included in the virtual work space and can be changed independently of the first object. The synchronization unit synchronizes and holds the second information defining the instructed second object in response to an instruction to share the information processing apparatuses.

  Preferably, the first display means includes a first area for the second object that should be shared among the plurality of information processing apparatuses, and a second area for the second object that should not be shared among the plurality of information processing apparatuses. The area is displayed separately from the display of part or all of the contents of the virtual work space. The synchronization means holds the second information corresponding to the second object displayed in the first area in synchronization, and does not synchronize the second information corresponding to the second object displayed in the second area.

  Alternatively, preferably, each of the plurality of information processing devices is either a first mode shared between the plurality of information processing devices or a second mode not shared between the plurality of information processing devices for each second object. It further includes mode setting means for receiving the setting. The synchronization unit synchronously holds the second information corresponding to the second object set in the first mode, and does not synchronize the second information corresponding to the second object set in the second mode.

  Alternatively, preferably, each of the plurality of information processing apparatuses further includes an authentication unit that authenticates a user who uses the information processing apparatus, and a sharing destination setting unit that receives a setting of a user who permits sharing for each second object. Including. The synchronization means holds the second information corresponding to the second object in synchronization with the information processing apparatus used by the user who is set to permit sharing of the second object.

  Preferably, the first information includes identification information associated with the first object and a description defining the substance of the first object. The second display means includes means for holding identification information for specifying the first object in association with the second object.

  Preferably, the second display means further includes means for changing the display position of the second object independently of the first object in response to a user operation.

  Preferably, the second display means further includes means for changing a display mode of the second object independently of the first object in response to a user operation.

  Preferably, the second display means can display a plurality of second objects side by side. The second display means further includes means for adding an object that associates the second objects with each other in response to a user operation.

  Preferably, at least one of the plurality of information processing apparatuses further includes a reflection unit that reflects changes made to the second object in the first object in response to a user operation.

  An information processing apparatus according to another aspect of the present invention provides a virtual work space. The information processing apparatus includes a holding unit, a first display unit, a second display unit, and a synchronization unit. The holding unit holds first information defining the virtual work space and the first object included in the virtual work space. Here, the first information is synchronized with another information processing apparatus. The first display means displays part or all of the contents of the virtual work space to the user based on the first information. In response to a user operation, the second display means displays a second object that is associated with the first object included in the virtual work space and can be changed independently of the first object. In response to an instruction to share with other information processing apparatuses, the synchronization unit holds second information defining the instructed second object in synchronization with the other information processing apparatuses.

  An information processing method according to yet another aspect of the present invention provides a virtual work space accessible by a plurality of users, using a plurality of information processing apparatuses connected to each other so as to be capable of data communication. In this information processing method, each of a plurality of information processing devices holds a first information defining a virtual work space and a first object included in the virtual work space, and each of the plurality of information processing devices holds Synchronizing the first information to be performed, and one information processing device among the plurality of information processing devices displaying a part or all of the contents of the virtual workspace to the user based on the first information; The information processing apparatus displaying a second object associated with the first object included in the virtual work space and changeable independently of the first object in response to a user operation; In response to an instruction that the processing device should be shared among a plurality of information processing devices, the second information defining the designated second object is synchronized with other information processing devices. That and a step.

  According to the present invention, by using the second display means for displaying the second object (in accordance with a typical embodiment, a shared tray), each user can perform other operations on the object on the workspace. The work of organizing information can be performed while reducing the influence on the work of the user, and the work result finally obtained by the work of organizing information can be easily shared with other users.

It is a schematic block diagram of the information processing system for providing the work space according to Embodiment 1 of this invention. It is a schematic diagram which shows the schematic hardware constitutions of the personal computer which is a typical example of the information processing apparatus according to Embodiment 1 of this invention. It is a figure which shows typically an example of the work space according to Embodiment 1 of this invention. It is a figure which shows an example of the content of the work space (WS) information corresponding to the work space shown in FIG. It is a figure for demonstrating the initial operation on the client apparatus according to Embodiment 1 of this invention. It is a figure which shows an example of the user interface on the client apparatus according to Embodiment 1 of this invention. It is FIG. (1) for demonstrating edit operation on the client apparatus according to Embodiment 1 of this invention. It is FIG. (2) for demonstrating edit operation on the client apparatus according to Embodiment 1 of this invention. It is a figure which shows typically an example of the workspace in the scene used as the object of description of the tray function according to Embodiment 1 of this invention. It is a figure for demonstrating starting operation of the tray function on the client apparatus according to Embodiment 1 of this invention. It is FIG. (1) for demonstrating operation in the tray function on the client apparatus according to Embodiment 1 of this invention. It is FIG. (2) for demonstrating operation in the tray function on the client apparatus according to Embodiment 1 of this invention. It is a figure for demonstrating an example of the intelligent creation work using the tray function according to Embodiment 1 of this invention. It is FIG. (3) for demonstrating operation in the tray function on client apparatus CL according to Embodiment 1 of this invention. It is FIG. (1) for demonstrating operation in the tray function on client apparatus CL according to Embodiment 1 of this invention. It is FIG. (2) for demonstrating operation in the tray function on client apparatus CL according to Embodiment 1 of this invention. It is the schematic which shows the control structure implement | achieved with the client apparatus CL according to Embodiment 1 of this invention. It is the schematic which shows the control structure implement | achieved by the server apparatus SRV according to Embodiment 1 of this invention. It is a schematic diagram which shows the exchange of data in Embodiment 1 of this invention. It is a figure which shows an example of the content of the tray information according to Embodiment 1 of this invention. It is a figure which shows an example of the content of WS information 114a in which the content of the tray information shown in FIG.20 (b) was reflected. It is a figure which shows the example of description of the tray information according to Embodiment 1 of this invention. It is a flowchart (the 1) which shows the process sequence which concerns on provision of the work space according to Embodiment 1 of this invention. It is a flowchart (the 2) which shows the process sequence which concerns on provision of the work space according to Embodiment 1 of this invention. It is a flowchart (the 3) which shows the process sequence which concerns on provision of the work space according to Embodiment 1 of this invention. It is a sequence diagram (the 1) which shows the process sequence which concerns on provision of the work space according to Embodiment 1 of this invention. It is a sequence diagram (the 2) which shows the process sequence which concerns on provision of the work space according to Embodiment 1 of this invention. It is a sequence diagram (the 3) which shows the process sequence which concerns on provision of the work space according to Embodiment 1 of this invention. It is a schematic block diagram of the information processing system for providing the work space according to Embodiment 2 of this invention. It is a schematic diagram which shows the exchange of data in Embodiment 2 of this invention. It is the schematic which shows the control structure implement | achieved with the client apparatus CL according to Embodiment 3 of this invention. It is a figure for demonstrating operation in the tray function on the client apparatus CL according to Embodiment 3 of this invention. It is a figure which shows an example of the content of the tray information corresponding to FIG. It is a sequence diagram which shows the process sequence which concerns on the tray function according to Embodiment 3 of this invention. It is the schematic which shows the control structure implement | achieved by the client apparatus CL according to Embodiment 4 of this invention. It is a figure for demonstrating operation in the tray function on the client apparatuses CL1-CL3 according to Embodiment 4 of this invention. It is a figure which shows an example of the content of the tray information corresponding to FIG.

  Embodiments of the present invention will be described in detail with reference to the drawings. Note that the same or corresponding parts in the drawings are denoted by the same reference numerals and description thereof will not be repeated.

[the term]
In this specification, the “work space” means a virtual work space provided on the information processing apparatus to which a visible object can be added or edited. Such a workspace allows a user to organize information and share information with other users. As a form (device) for providing the workspace, an information processing apparatus that executes a program (application), an electronic whiteboard in which the function is incorporated in advance, a mobile phone, a tablet PC, and the like are conceivable.

  In this specification, “object” means general data that can be added to a workspace. This object is the unit of operation target of the user. Examples of this object include graphics, text documents, worksheet cells, images, audio, logs, tags, bookmarks, annotations, user information, and the like. In addition, all data added on a “selection tray” to be described later is also referred to as “object”. Therefore, when it is necessary to distinguish between them, an object on the workspace is referred to as an “entity object”, and an object on the selection tray is also referred to as an “alias object”. The “substance object” is an object to be operated to achieve the original purpose of using the workspace, and the “alias object” is an object that refers to the entity object in order to use the tray function.

[Overview]
The present invention provides an environment in which intelligent creation work can be efficiently performed by selectively collecting objects that are considered necessary by a user among objects (substance objects) scattered on a workspace. More specifically, in this environment, the user can freely place alias objects associated with the entity objects in a display area that is distinct from the workspace, and these alias objects can be placed on the workspace. Various editing operations can be freely performed independently of the entity object. In this specification, these functions are also referred to as “tray functions”.

  Furthermore, the present invention provides a tray function that allows a user to arbitrarily select one of the arranged alias objects and share it among a plurality of users (actually, information processing devices used by each user). . By using such a function, work in the case of performing collaborative work in a group of a plurality of members is made efficient.

[Embodiment 1]
<Overall configuration>
FIG. 1 is a schematic configuration diagram of an information processing system for providing a work space according to the first embodiment of the present invention.

  Referring to FIG. 1, the information processing system according to the present embodiment includes a plurality of client devices CL1 to CLN (hereinafter referred to as “a plurality of information processing devices” connected to each other via a network NW so that data communication is possible. Client device CL ”) and server device SRV. That is, in the present embodiment, a so-called server client configuration is illustrated. As will be described later, a so-called peer-to-peer configuration can also be adopted.

  Each of the client devices CL1 to CLN holds information (workspace (WS) information described later) for providing a work space in common via the server device SRV, so that the client devices CL1 to CLN. A workspace is provided to users who use each of the above. That is, when a user adds an object on a workspace on any client device CL, the added object is reflected on the workspace displayed on the other client device CL. In this way, information can be shared between users. Note that the tray function according to the present invention can also be applied to a workspace provided by a single client device CL. That is, the present invention is not necessarily limited to a workspace that can be accessed simultaneously by a plurality of users.

  Server SRV mainly controls data sharing among client apparatuses CL1 to CLN.

<Hardware configuration>
FIG. 2 is a schematic diagram showing a schematic hardware configuration of a personal computer which is a representative example of the information processing apparatus according to the first embodiment of the present invention.

  Referring to FIG. 2, client device CL, which is an information processing device according to the present embodiment, temporarily stores CPU 2 that executes various programs including an operating system, and data necessary for the execution of the program by CPU 2. And a hard disk (HDD) 12 that stores a program executed by the CPU 2 in a nonvolatile manner. Such a program is read from a CD-ROM 16a or a flexible disk 18a by a CD-ROM (Compact Disk-Read Only Memory) drive 16 or a flexible disk (FD) drive 18, respectively.

  The CPU 2 receives a user operation request via the input device 10 including a keyboard, mouse, tablet, and the like, and outputs a screen output generated by executing the program to the output device 6.

  The output device 6 is a device for displaying the state of the workspace to the user, and typically includes a monitor or a projector.

  In addition, the CPU 2 performs data communication with other client devices CL and the server device SRV via the communication interface 8 including a LAN card. These parts are connected to each other via the internal bus 4.

  Server apparatus SRV according to the present embodiment is also an information processing apparatus, and the hardware configuration thereof is the same as the hardware configuration of client apparatus CL shown in FIG. 2, and therefore detailed description will not be repeated.

<Workspace>
Next, with reference to FIGS. 3 to 8, an example of operation of the workspace according to the present embodiment will be described. FIG. 3 is a diagram schematically showing an example of a workspace according to the first embodiment of the present invention. FIG. 4 is a diagram showing an example of the contents of the work space (WS) information corresponding to the work space shown in FIG. FIG. 5 is a diagram for describing an initial operation on client device CL according to the first embodiment of the present invention. FIG. 6 shows an example of a user interface on client device CL according to the first embodiment of the present invention. FIG. 7 is a diagram (part 1) for describing an editing operation on client device CL according to the first embodiment of the present invention. FIG. 8 is a diagram (No. 2) for describing an editing operation on client device CL according to the first embodiment of the present invention.

  Various objects can be added to the workspace according to the present embodiment, and the added objects can be edited or deleted. FIG. 3 shows a workspace in which objects OBJ1 to OBJ9 have already been created as an example. In FIG. 3, an object OBJ1 is an “image object”, objects OBJ2 and OBJ4 to OBJ9 are “text objects”, and object OBJ3 is a “line object”. As described above, the type of object is not particularly limited as long as it is data that can be handled electronically, but as an example, in addition to external files such as images and documents, vector data such as figures and lines, and free by handwriting Can accept input.

  Note that the workspace shown in FIG. 3 is conceptually expressed. In practice, the contents included in the range (view range) corresponding to the user operation are displayed on each client device CL ( Rendered). That is, part or all of the contents of the workspace are displayed for the user.

  These objects OBJ1 to OBJ9 and the view range are defined as WS information as shown in FIG. WS information for defining a workspace and objects included in the workspace according to the present embodiment is typically described in a markup language such as XML. By adopting such a markup language, tags (attributes given to characters surrounded by <> and </>) can be freely set, so that the expandability of the system can be improved.

  Referring to FIG. 4, WS information includes a workspace tag 302 for specifying a workspace, a description 304 for specifying a view range, and descriptions 311 to 315 for defining objects OBJ1 to OBJ5, respectively. .

  The workspace tag 302 typically stores information such as a workspace identification number (workspace id) and the creator of the workspace (Author). The workspace tag 302 may include a character encoding attribute.

  The description 304 stores information for specifying the view range. More specifically, the center coordinates of the view range are specified by the <object> tag, the </ object> tag, and the <point x = y = /> tag. Further, the display magnification (ratio of the display range to the default display range) is specified by the <zoom_scale> tag and the </ zoom_scale> tag.

  Each object is defined by a description that begins with an <object> tag and ends with a </ object> tag. Each of these descriptions 311 to 315 includes an identification number (objectid) of each object, an attribute according to the type of each object (image: image object, text: text object, line: line object, etc.), each object or each The coordinate position (x =, y =) on the workspace for the elements constituting the object, the link address (src) of the external file, the enlargement / reduction ratio (scale), and the like are included. That is, each of the descriptions 311 to 315 defines identification information associated with the object and the substance of the object.

  More specifically, an identification number that uniquely identifies each object is defined in the <object id> tag. In the <point> tag, the coordinate position on the workspace for each object or an element constituting each object is defined. In the <src> tag, a link address of the associated external file is defined.

  For example, in the description 311 corresponding to the object OBJ1, it is defined that the identification number is “1” in the <object id> tag and the image object is defined in the <image> tag. Furthermore, it is defined in the attribute in the <image> tag that the x-coordinate is “60” and the y-coordinate is “180”, and the <src> tag specifies an external file “ fuji.jpg ”is defined, and the <scale> tag defines that the display magnification of the object OBJ1 is“ 0.25 ”.

  For image objects and the like, an external file (reference destination file) is prepared separately from the description in the WS information. The contents of such an image object can be referred to and displayed on the workspace WS.

  In FIG. 4, an example of configuring a workspace using one WS information is illustrated, but equivalent information may be defined using a plurality of files. For example, a configuration in which files in which each object is defined is associated with each other using a relational database or the like can be employed. In other words, any data structure that can be handled in units of objects is not limited to the data structure shown in FIG. 4, and any data structure can be adopted. Based on the contents of the WS information, drawing of the workspace and external output are performed.

  Also, the content of the description 304 shown in FIG. 4 is updated at any time as the user changes the view range such as enlargement / reduction or scrolling on any of the client devices CL.

  Furthermore, a user can perform operations on the client device CL to create a new workspace, write the created workspace, read an already created workspace, and the like.

  Referring to FIG. 5, as a typical operation example, display window 150 that provides a work space according to the present embodiment is initially displayed on output device 6 of client device CL. In the display window 150, in addition to an area 158 for displaying a workspace, a “file” button 152, an “operation” button 154, and a “display” button 156 are displayed at the top. When the user selects this “file” button 152 with a mouse or the like, a dialog for operating the WS information is displayed. When “Open new WS” is selected in this dialog, a new workspace is created. When “Save WS” is selected, the currently created workspace is saved as WS information. When “Open WS” is selected, the saved WS information that has been saved is selectively read to display the workspace. 6 to 8 show operation examples in a state where the workspace is read and displayed.

  Referring to FIG. 6, when the workspace is displayed on output device 6 of client device CL, display window 160 indicating the position of the view range on the workspace is displayed in addition to display window 150. The display window 160 schematically shows the relative relationship between the entire workspace and the view range VIEW. When the user moves or deforms (resizes) the view range VIEW on the display window 160 with a mouse or the like, the range of the workspace displayed in the area 158 is changed accordingly.

  FIG. 6A shows a display example when the range VIEW1 shown in FIG. 3 is set as the view range, and FIG. 6B shows the case where the range VIEW2 shown in FIG. 3 is set as the view range. A display example is shown.

  Comparing FIG. 6A and FIG. 6B, since the region 158 on the output device 6 of the client device CL is the same, the smaller the view range set on the workspace, the smaller the view range. The contents of the workspace are enlarged and displayed. Therefore, for example, when an overview of the entire workspace is desired, a wider range is set as the view range, and when a specific object is desired to be focused, a narrower range is set as the view range.

  When a user performs an editing or deleting operation on an object placed on the workspace, typically, an object to be operated is selected and then the processing content is instructed. As a method for selecting this object, there are a method for directly selecting a target object and a method for selecting an object existing in the range by designating a desired range. Moreover, you may enable it to select (add) an object over multiple times continuously. FIG. 7 shows an operation example when the target object is directly selected, and FIG. 8 shows an operation example when the target object is indirectly selected by specifying a range.

  As an example, the operation when the user moves the object OBJ2 arranged on the workspace is illustrated. As shown in FIG. 7A, the user places a cursor CRS to be displayed on the target object (object OBJ2) and then performs a click operation (typically left click) on the mouse. The object OBJ2 is directly selected. Alternatively, as shown in FIG. 7B, the user places a cursor CRS to be displayed on the target object (object OBJ2) and then performs a click operation (typically right click) on the mouse. A dialog showing a list of operation commands is displayed, and by designating “select” on this dialog, the object OBJ2 is directly selected.

  In the state where the object OBJ2 is selected in this way, as shown in FIG. 7C, the user can move the object OBJ2 by performing a drag operation, a cursor operation, or the like.

  On the other hand, as shown in FIG. 8, a desired range is specified by dragging a range including the object OBJ2 while the user continues a click operation (typically a left click) on the mouse. . Objects included in the specified range are selected. In this way, the user can select an object within the specified range without directly selecting the target object.

  As a matter of course, various operations can be performed in addition to the object movement operations shown in FIGS. For example, the color, shape, and contents of the object can be changed. In addition, connection of objects and attribute settings such as a link and a tag may be employed.

<Tray function>
Next, a tray function according to the present embodiment will be described with reference to FIGS. As described above, personal use and shared use are prepared as the tray function according to the present embodiment. In the following description, the basic contents of the tray function according to the present embodiment will be described first. Then, the functional difference between the tray function (individual) and the tray function (shared) will be described.

  FIG. 9 is a diagram schematically showing an example of a workspace in a scene which is a target for explanation of the tray function according to the first embodiment of the present invention. FIG. 10 is a diagram for illustrating a tray function activation operation on the client device CL according to the first embodiment of the present invention. FIG. 11 is a diagram (No. 1) for explaining the operation in the tray function on client device CL according to the first embodiment of the invention. FIG. 12 is a diagram (No. 2) for explaining the operation in the tray function on client device CL according to the first embodiment of the invention. FIG. 13 is a diagram for explaining an example of the intelligent creation work using the tray function according to the first embodiment of the present invention. FIG. 14 is a diagram (No. 3) for explaining the operation in the tray function on client device CL according to the first embodiment of the invention.

  As a premise of the following description, consider a workspace as shown in FIG. The workspace shown in FIG. 9 is different from the workspace shown in FIG. 3 only in the position of the view range VIEW. Note that the objects OBJ4 to OBJ9 include solutions A to F for a certain problem, for example. Then, it is determined which one of the solutions A to F is optimal, extracts a part of the solutions A to F, or creates a new solution based on them. Think about the case.

  Referring to FIG. 10, when starting the tray function according to the present embodiment, the user selects “display” button 156 displayed at the top of display window 150 with cursor CRS or the like. Then, a dialog 156a for performing an operation related to display is displayed. In this dialog 156a, a plurality of items including a “personal tray display” for activating a personal tray function and a “shared tray display” for activating a shared tray function can be selected and displayed. Is done. Here, when the user selects “personal tray display”, a display window 170 indicating the selected tray (individual) is newly generated. When the user selects “shared tray display”, a display window indicating the selected tray (shared) is displayed. 180 is newly generated. Note that when the display window 180 is newly generated in any one of the client devices CL, the display window 180 may be automatically generated in the other client devices CL. Alternatively, it is searched whether or not the display window 180 has been generated in another client device CL, and if there is a client device CL that has generated the display window 180, the display window 180 is also generated in the own device. You may do it.

  In the following description, when the common functions of the selection tray (individual) and the selection tray (shared) are described, both are simply referred to as “selection tray”.

  As shown in FIG. 11, a display window 150 that provides a workspace, a display window 170 that indicates a selection tray (individual), and / or a display window 180 that indicates a selection tray (shared) are displayed. Drags and drops any object on the workspace to the display window 170 (or the display window 180), so that the selected alias object ALS1 appears on the selection tray. As a method of adding to the selection tray, in addition to the above-mentioned drag and drop, the object on the workspace is selected, the object is stored by the pull-down menu, and the drop destination is specified with the destination to be dropped. Another method such as specifying a command may be used. In other words, any method may be employed as long as an object on the designated workspace can be dropped at a designated position on the selection tray. In addition, it is preferable that the method of selecting objects on the workspace as the selection tray (individual) and the selection tray (shared) is a common operation.

  In this way, the alias object associated with the entity object is displayed in a display area that is distinct from the display of the contents of part or all of the workspace.

  With the addition of the alias object ALS1 to the selected tray, tray information for defining an object on the selected tray is newly generated. As will be described later, this tray information is described in a markup language such as XML, like the WS information described above.

  The object (alias object) on the selection tray exists independently of the object (substance object) on the workspace. That is, in principle, even if the user performs an operation such as moving, editing, or deleting an alias object on the selection tray, the actual object on the workspace is not affected. That is, as shown in FIG. 12, for the alias object ALS1 displayed in the display window 170, operations such as movement, editing, and deletion can be performed independently of the associated entity object on the workspace. Is possible.

  Note that operations such as moving, editing, and deleting an alias object on the selection tray can be reflected on an associated entity object on the workspace according to a user operation.

  At the same time, the object (alias object) on the selection tray is displayed in a display mode based on the display mode of the associated entity object so that the user can recognize the association with the entity object. For example, when the entity object has a rectangular shape, the alias object is also displayed as a rectangle.

  The number of alias objects that can be added to the selection tray is not particularly limited, and the user can create an alias object by dragging and dropping an entity object on the workspace. A part of the alias objects added to the selection tray in this way can also be selected. In other words, among the alias objects added to the selection tray, it is possible to extract a more important one or the like that reflects some change to the actual object on the workspace.

  In FIG. 11, the display windows 170 and 180 indicating the selection tray are illustrated as being displayed separately from the display window 150 that provides the work space. A form may be adopted in which a part of is used as a selection tray.

  By providing such a user interface, the user can perform an intelligent creation work independently of the actual object on the workspace. With reference to FIG. 13, an example of the intellectual creation work by the user will be described.

  First, as shown in FIG. 13A, the user adds an object considered necessary on the workspace to the selection tray by a drag-and-drop operation, but determines that the object added to the selection tray is unnecessary. Deleted objects can be deleted from the selection tray. At this time, even if the user moves the alias object on the selection tray, the actual object on the workspace is not affected.

  For example, as shown in FIG. 13 (a), the user can think of a state where three alias objects have been added to the selection tray and appropriately change the position of the alias object on the selection tray. In such a thinking process, a user thinks that the alias object ALS2 is unnecessary and deletes it from the selection tray, and instead, it is better to add new alias objects ALS4 and ALS5 to the selection tray. The added state is shown in FIG.

  In the state shown in FIG. 13B, the alias objects ALS1 and ALS3 associated with the entity objects OBJ4 and OBJ8 on the workspace are arranged close to each other, and the entity objects OBJ7 and OBJ6 on the workspace are arranged. Alias objects ALS4 and ALS5 respectively associated with each other are arranged close to each other. In this way, the user can arrange the entity objects arranged separately on the workspace at positions close to each other on the selection tray. Thereby, it is possible to visually collect objects that the user thinks that the contents are similar and should be classified into the same category.

  If the user continues to think, and if the alias objects ALS1 and ALS3 are considered superior to the alias objects ALS4 and ALS5, the respective background color is changed in order to visually represent it. can do. More specifically, as shown in FIG. 13C, the user performs a drag operation while continuing a click operation (typically, left click) on the mouse, whereby the alias object ALS1 on the selection tray is displayed. And selection range DA1 is specified to include ALS3. Subsequently, the user selects an “operation” button 172 displayed on the left side of the display window 170 (or 180) with the cursor CRS or the like. Then, a dialog (not shown) for performing various operations is displayed. By selecting a “color edit” button for changing the color attribute of the selected object on this dialog, the background colors of the alias objects ALS4 and ALS5 are changed (for example, white to yellow). The initial background color of the alias objects ALS1 and ALS3 on the selection tray is set to the same background color as the associated entity object on the workspace.

  Further, when the alias objects ALS4 and ALS5 are considered to be superior to the alias objects ALS1 and ALS3, in order to visually express them, the same procedure as in FIG. The background color can also be changed. That is, as shown in FIG. 13D, the user includes the alias objects ALS4 and ALS5 on the selection tray by performing a drag operation while continuing a click operation (typically a left click) on the mouse. Thus, the selection range DA2 is designated. Subsequently, the user selects an “operation” button 172 displayed on the left side of the display window 170 (or 180) with the cursor CRS or the like. Then, a dialog (not shown) for performing various operations is displayed. By selecting a “color edit” button for changing the color attribute of the selected object on this dialog, the background colors of the alias objects ALS1 and ALS3 are changed (for example, from white to red).

  From another point of view, if the user thinks that the alias object ALS1 and the alias object ALS5 are classified into different categories but are related to each other, the shape of the alias objects ALS1 and ALS5 is changed. By changing it, it can be expressed that it is classified into the same category in another sense. More specifically, as shown in FIG. 13E, the user performs a drag operation while continuing a click operation (typically a left click) on the mouse, whereby an alias object ALS1 on the selection tray is displayed. And selection range DA3 is specified to include ALS4. Subsequently, the user selects an “operation” button 172 displayed on the left side of the display window 170 (or 180) with the cursor CRS or the like. Then, a dialog (not shown) for performing various operations is displayed. By selecting a “shape edit” button for changing the shape of the selected object on this dialog, the shapes of the alias objects ALS1 and ALS4 are changed from a square to an ellipse. The changed shape can be arbitrarily selected.

  Alternatively, referring to FIG. 13 (f), the user places a cursor CRS to be displayed on the first alias object (alias object ALS1) on the selection tray, and then performs a click operation on the mouse (typically Right click), and then, after placing the cursor CRS on the second alias object (alias object ALS4) and performing a click operation (typically right click) on the mouse. , A linking LNK that visually represents that both alias objects are associated is added.

  In this way, the user places the alias objects in a certain position, selects the alias objects that are to be operated at once by a simple selection range specification operation, and changes the color of the alias objects belonging to the same category. , You can easily perform complex and complex operations such as changing the shape of the alias object that has been re-selected at a different point, and connecting the alias objects that you want to emphasize that are related to each other with a line . Note that these operation contents can be reflected in the associated entity objects on the workspace.

  Next, with reference to FIG. 14, a description will be given of a preview function that is effective when an operation on an alias object on the selection tray is reflected on a real object on the workspace.

  As shown in FIG. 14A, when the alias object ALS1 is selected on the selection tray, it is assumed that some change operation is performed on the alias object ALS1. The alias object ALS1 is assumed to be associated with the entity object OBJ4 on the workspace in the display window 150.

  FIG. 14B shows a case where an operation for increasing the thickness of the outer peripheral frame is performed on the alias object ALS1. After performing such an operation, the user selects a “preview” button 174 displayed on the left portion of the display window 170 (or 180) with the cursor CRS or the like. Then, the display of the associated entity object OBJ4 on the workspace in the display window 150 is changed to a state in which the changed shape of the alias object ALS1 is reflected. That is, a preview display of the state when the change made to the alias object ALS1 is reflected on the associated entity object. With this preview display, the user can visually determine in advance whether or not the change made to the alias object may be reflected on the associated entity object.

  In the above description, the operation when an alias object is added to the display window 170 indicating the selected tray (individual) is described as an example. However, when an alias object is added to the display window 180 indicating the selected tray (shared). The same operation can be performed for.

<Selection tray (individual) and selection tray (shared)>
Next, with reference to FIGS. 15 and 16, the functional difference between the tray function (individual) and the tray function (shared) will be described. FIG. 15 is a diagram (No. 1) for explaining the operation in the tray function on client device CL according to the first embodiment of the invention. FIG. 16 is a diagram (No. 2) for explaining the operation in the tray function on client device CL according to the first embodiment of the invention.

  First, the selection tray (sharing) will be described with reference to FIG. FIG. 15A shows a display example in the client device CL1, and FIG. 15B shows a display example in the other client devices CL2 to CLN.

  As shown in FIG. 15A, the user of the client device CL1 drags and drops an arbitrary object on the workspace to the display window 180 (selection tray (shared)), thereby selecting the selected tray (shared). It is assumed that a new alias object ALS1 is added above. With the addition of the alias object to the selected tray (shared), the shared tray information 114c held by the client device CL1 is changed, and the changed content of the shared tray information 114c is the shared tray information held by the server device SRV. Reflected in 214c. Further, the changed contents are reflected from the server SRV to the shared tray information 114c held by each of the other client apparatuses CL2 to CLN.

  As a result, the selected tray (shared) in each of the other client devices CL2 to CLN is synchronized with the alias object added to the selected tray (shared) of the client device CL1, as shown in FIG. Is displayed.

  Next, the selection tray (individual) will be described with reference to FIG. FIG. 16A shows a display example in the client device CL1, and FIG. 16B shows a display example in the other client devices CL2 to CLN.

  As shown in FIG. 16A, the user of the client device CL1 drags and drops an arbitrary object on the workspace to the display window 170 (selection tray (individual)), thereby selecting the selection tray (individual). It is assumed that a new alias object ALS1 is added above. As the alias object is added to the selected tray (individual), the personal tray information 114b held by the client device CL1 is changed. However, the changed contents of the personal tray information 114b are not synchronized with the other client devices CL and the server device SRV.

  As a result, the alias objects added to the selection tray (individual) of the client device CL1 are displayed on the selection tray (individual) in each of the other client devices CL2 to CLN, as shown in FIG. Not. That is, each selected tray (individual) of the client device CL is handled independently of the other client devices CL.

  It should be noted that the timing of data transmission between the client device CL and the server device SRV, the client device CL to be transmitted, the transmission direction, the transmission content (whether or not all transmission is performed), etc. It can be arbitrarily set according to the system configuration and performance.

  By using the sharing tray function described above, a group of a plurality of members can jointly advance an intellectual creation work. Referring to FIG. 13 again, an example of intellectual creation work by a group of a plurality of members will be described.

  For example, each user using the client devices CL1 to CL3 simultaneously shares and adds the entity object that is considered most appropriate to the display window 180 indicating the selection tray (shared), and then the client device CL1 is added. After the user who has used the idea moves while moving the alias object on the selection tray (shared), one more object is added. FIG. 13B shows a state after these series of operations are performed. Furthermore, the background color of two (alias objects ALS1 and ALS3) of the four alias objects added to the selection tray (shared) by the user using the client device CL2 as shown in FIG. The user using the client device CL3 changes two of the four alias objects added to the selection tray (shared) as shown in FIG. Change the background color of ALS4 and ALS5). Further, the user who uses the client device CL4 visually represents that the two alias objects are associated with the alias object ALS1 and the alias object ALS4 as shown in FIG. Add LNK.

<Functional configuration>
Next, a control structure for providing a work space according to the present embodiment will be described with reference to FIGS. FIG. 17 is a schematic diagram showing a control structure realized by client device CL according to the first embodiment of the present invention. FIG. 18 is a schematic diagram showing a control structure realized by server SRV according to the first embodiment of the present invention. FIG. 19 is a schematic diagram showing data exchange according to the first embodiment of the present invention.

  Referring to FIG. 17, client device CL includes an input device 10, an output device 6, a processing unit 100, a WS storage unit 120, and an input / output control unit 130 as a control structure. Typically, the processing unit 100 and the input / output control unit 130 are provided by the CPU 2 executing a program stored in advance in the hard disk 12 after the CPU 2 develops the program in the memory 14. The WS storage unit 120 is provided as a part of the HDD 12.

  The input device 10, the output device 6, the processing unit 100, the WS storage unit 120, and the input / output control unit 130 are not necessarily provided in the same client device CL, and may be provided separately in separate devices. Good. Further, the input / output control unit 130 may be provided inside the input device 10 or the output device 6. Further, other information such as between the input device 10 and the output device 6 and the input / output control unit 130, between the input / output control unit 130 and the processing unit 100, and between the processing unit 100 and the WS storage unit 120, etc. You may comprise in the form which mediates a processing apparatus, a control part, etc.

  The input / output control unit 130 interprets the content of the input signal received by the input device 10 and outputs a corresponding command to the processing unit 100. That is, the input / output control unit 130 determines what kind of operation the user has performed on the input device 10. As a more specific example, the input / output control unit 130 determines which object on the workspace has been selected, which button has been pressed, click operation, and drag operation by clicking or dragging the mouse. Interpret the contents such as.

  Further, the input / output control unit 130 generates an output signal based on the information from the processing unit 100 and sends it to the output device 6. As a more specific example, the input / output control unit 130 performs what kind of display on any part of the displayed screen in accordance with an object operation or a view change operation performed by the user on the workspace. Determine whether it is okay and generate (render) the output signal.

  Processing unit 100 governs the entire process of providing a work space according to the present embodiment. The processing unit 100 is synchronized with the operation management unit 102, the view management unit 104, the object management unit 106, the tray management unit 108, the WS space management unit 110, the WS input / output unit 112, and the WS work memory 114. And a management unit 116.

  The operation management unit 102 determines the requested processing content based on the information sent from the input / output control unit 130, and in accordance with the determination result, the view management unit 104, the object management unit 106, the tray management unit 108, A command is given to corresponding parts of the WS space management unit 110, the WS input / output unit 112, and the synchronization management unit 116. More specifically, when the received operation content is creation of a new workspace, reset of a workspace, deletion of a workspace, etc., the operation management unit 102 issues an instruction to the WS space management unit 110 and sets the WS. Processing is executed in the space management unit 110. In addition, when the received operation content is editing such as movement, content change, decoration change, etc., creation of a new object, or deletion of an object, the operation management unit 102 issues an instruction to the object management unit 106, and the object management unit Processing is performed at 106. Further, when the received operation content is a view change, the operation management unit 102 issues an instruction to the view management unit 104, and the view management unit executes the process. Further, when the received operation content is reading or writing of a workspace, the operation management unit 102 issues an instruction to the WS input / output unit 112 and the WS input / output unit 112 executes processing. In addition, the operation management unit 102 displays the selected operation, such as displaying a selected tray, adding an object to the selected tray, editing an object on the selected tray such as movement, content change, decoration change, and the like. In the case of deletion, an instruction is issued to the tray management unit 108 and processing is executed by the tray management unit 108.

  The WS work memory 114 stores WS information 114a for providing a work space, personal tray information 114b for providing a personal tray function, and shared tray information 114c for providing a tray function for sharing. Is done. The WS information 114a, personal tray information 114b, and shared tray information 114c are updated as needed in accordance with user operations and processing in each unit.

  The WS space management unit 110 manages new creation and deletion of the WS information 114 a in the WS work memory 114 in accordance with an instruction from the operation management unit 102.

  The object management unit 106 updates the content (description) of the WS information 114 a stored in the WS work memory 114 in accordance with an instruction from the operation management unit 102. Here, the synchronization management unit 116 communicates with other client devices CL periodically or whenever some event occurs, and updates (synchronizes) the WS information 114a in the WS work memory 114.

  The view management unit 104 is based on information included in the view range specified by the user among the information defined in the WS information 114a stored in the WS work memory 114 in accordance with an instruction from the operation management unit 102. Then, drawing processing (rendering processing) is performed. It should be noted that a common view range may be displayed between the client devices CL sharing the same WS information 114a. In this case, it is preferable that the view management units 104 of the client device CL communicate with each other and also hold information indicating the view range in synchronization.

  The WS input / output unit 112 reads the WS information 120a stored in the WS storage unit 120 in accordance with an instruction from the operation management unit 102, or stores the WS information 114a stored in the WS work memory 114 in the WS storage unit 120. The stored WS information 120a is updated. The WS storage unit 120 stores the WS information 120a in a nonvolatile manner, and continuously holds the WS information 120a even after an application that provides a work space is shut down.

  The tray management unit 108 creates personal tray information 114b in the WS work memory 114 in accordance with an instruction from the operation management unit 102, and further updates the contents of the personal tray information 114b as appropriate. Further, the tray management unit 108 creates the shared tray information 114c in the WS work memory 114 in accordance with the instruction from the operation management unit 102, and further updates the contents of the shared tray information 114c as appropriate.

  Referring to FIG. 18, server SRV according to the present embodiment includes WS work memory 214 and synchronization management unit 216 as its control structure. The WS work memory 214 stores WS information 214a for providing a work space and shared tray information 214c for providing a tray function. The WS information 214a and the shared tray information 214c are synchronized with the WS information 114a and the shared tray information 114c shown in FIG.

  The synchronization management unit 216 mediates synchronization processing between the client devices CL. More specifically, the synchronization management unit 216 stores the change in the WS work memory 214 when any of the WS information 114a and the shared tray information 114c is changed in any of the client devices CL. Is reflected in the current WS information 214a and the shared tray information 214c. Further, the synchronization manager 216 distributes the changed WS information 214a and shared tray information 214c to the other client devices CL, respectively. By this series of processing, synchronization processing between the client devices CL is realized.

  Referring to FIG. 19, as an overview of the synchronization processing described above, synchronization is established between WS information 114a held by each of client devices CL1 to CLN and WS information 214a held by server device SRV, Synchronization is taken between the shared tray information 114c held by each of the client devices CL1 to CLN and the shared tray information 214c held by the server device SRV. On the other hand, the personal tray information 114b held by each of the client devices CL1 to CLN is not synchronized with any of the other client devices CL and the server device SRV.

  That is, the personal tray information 114b is used exclusively for the user who uses the client device CL, and the shared tray information 114c is common to all the client devices CL and the server device SRV that constitute the information processing system. Used for.

  Thus, by providing two types of tray functions having different properties, the user can perform an intelligent creation work according to the situation. More specifically, by using the tray function provided based on the personal tray information 114b, the user can use his / her own mind and use the tray function provided based on the shared tray information 114c. As a result, users who use a plurality of client devices CL can collaborate on ideas.

<Detailed operation in the tray management unit>
Next, details of processing in the tray management unit 108 of the client device CL will be described with reference to FIGS. 20 and 21.

  FIG. 20 shows an example of the contents of the tray information according to the first embodiment of the present invention. FIG. 21 is a diagram showing an example of the contents of the WS information 114a reflecting the contents of the tray information shown in FIG.

  As shown in FIG. 11, when the user drags and drops an arbitrary object on the workspace to the display window 170, personal tray information 114b as shown in FIG. 20A is generated.

  Referring to FIG. 20A, personal tray information 114b is recorded in a state in which the display position on the selected tray is associated with information that uniquely identifies the entity object that is the reference destination of the alias object. More specifically, information for uniquely specifying an alias object on the selected tray is described by a <select_object id => tag and a </ select_object> tag (reference numeral 350). In addition, the <text id = x = y => tag and </ text> (reference numeral 351) identify the entity object on the workspace that is referred to the associated alias object, and the alias object on the selection area. A position is specified.

  That is, in the example shown in FIG. 20A, since “text id = 4” is defined, it is interpreted that the object OBJ4 is the reference destination among the entity objects defined in the WS information 114a shown in FIG. Is done. That is, in the description 314 of the WS information 114a shown in FIG. 4, it is defined that the identification number is “4” in the <object id> tag, and “text id = 4” defined in the personal tray information 114b. ".

  In this way, the personal tray information 114b holds identification information for specifying the entity object in association with the alias object.

  As shown in FIG. 20 (a), for the alias object added to the selection tray, basically only the entity object of the reference destination is specified. Therefore, the tray management unit 108 refers to the WS information 114a when referring to the WS information 114a when displaying the contents on the selected tray in order to notify the user of the state of the reference destination entity object. Get the attributes about. Then, the alias object is displayed according to the acquired attribute. Also, the tray management unit 108 refers to the WS information 114a periodically or every time an event occurs, and if the attribute of the reference object is changed, the display of the alias object is changed. Update the display according to. By adopting such a display method, the user can easily recognize which entity object on the workspace is associated with each alias object selected on the selection tray. In addition, when an instruction is given to reflect any changes made to the selected alias object on the selection tray, whether or not the reflection processing has been executed correctly and which change contents are on the workspace. It can be easily confirmed whether it is reflected.

  As a display method of the alias object, the display mode including the size of the actual object on the workspace may be applied as it is, or the size may be changed at a predetermined enlargement / reduction ratio or set to a predetermined fixed size. The size may be changed so that Alternatively, if it can be determined that the entity object on the workspace can be identified and the status can be confirmed based on the shape and decoration alone, only the shape and decoration of the alias object can be displayed or displayed on the workspace. The alias object on the selection tray is limited to some attributes so that the decoration and the pattern, image, etc. that are the contents of the entity object do not correspond (for example, the interior of the alias is filled). You may make it express. How to display the alias object may be set in advance by the tray management unit 108 or may be set each time according to the user's designation.

  The tray management unit 108 updates the personal tray information 114b according to the content of the user performing a change operation on the alias object on the selected tray. For example, in FIG. 13F described above, the background color of the alias object ALS1 is changed to “yellow” and the shape thereof is changed to “ellipse”. The contents of the personal tray information 114b corresponding to the alias object ALS1 are shown in FIG.

  20A and 20B are compared, it can be seen that descriptions 352, 353, and 354 are added to the personal tray information 114b. The description 352 specifies the background color when the corresponding alias object ALS1 is displayed. That is, the background color ("yellow" indicating yellow in the case of FIG. 20B) is specified by the <bg_color> tag and the </ bg_color> tag. The description 353 specifies the shape when the corresponding alias object ALS1 is displayed. That is, the shape (“ellipse” indicating an ellipse in the case of FIG. 20B) is specified by the <shape> tag and the </ shape> tag.

  Next, when the user performs an operation of reflecting the change contents for the alias object on the selected tray on the associated entity object on the workspace, the tray management unit 108 manages the change contents in the personal tray information 114b. The data is output to the object management unit 106 via the unit 102. That is, the tray management unit 108 outputs the contents of the descriptions 352 and 353 shown in FIG. 20B together with the identification number (id) of the reference destination entity object to the object management unit 106. The object management unit 106 updates the description of the entity object having the specified identification number among the contents included in the WS information 114a in accordance with the change contents received from the tray management part 108. FIG. 21 shows an example of the WS information 114a reflecting the change contents shown in FIG.

  Comparing FIG. 4 with FIG. 21, it can be seen that the content of the description 314 defining the entity object OBJ4 is updated to the description 314A. In the description 314A, a definition substantially the same as the contents of the descriptions 352 and 353 defined in FIG. 20B is added. By updating the WS information 114a, changes made to the alias object on the selected tray are reflected in the associated entity object. Note that after the changed content is reflected on the entity object, the tray management unit 108 updates the content of the personal tray information 114b to the content shown in FIG. That is, since the change content is reflected in the entity object that is the reference destination of the alias object, it is only necessary to display the alias object with reference to the entity object in which the change content is reflected.

  Furthermore, in addition to the description example of the personal tray information 114b shown in FIG. 20B, various displays and decorations as shown below can be given to the alias object.

FIG. 22 is a diagram showing a description example of tray information according to the first embodiment of the present invention.
As shown in FIG. 13 (f) described above, when displaying an association LNK that visually represents that alias objects are associated with each other, the contents as shown in FIG. 22 (a) are added. . That is, on the selected tray, the linking LNK itself is newly generated as a new object. In the example shown in FIG. 22A, the <object id> tag defines a new object having an identification number “5”. As the definition contents of this object, the line type used for the linking LNK (in the case of FIG. 22A, “arrow” indicating a unidirectional arrow) is defined by the <type> tag and the </ type> tag. It is specified. Further, the <connect_obj1_id = /> tag specifies an alias object for starting the association LNK (in the case of FIG. 22A, the alias object ALS2 having id = 2). At the same time, the <connect_obj2_id = /> tag specifies an alias object (in the case of FIG. 22A, the alias object ALS4 having id = 4) that ends the association LNK. In this way, an object that associates alias objects is added.

  FIG. 22B shows a description example in which the character “ABC” added on the selection tray is blinked as another decoration form. That is, in the example shown in FIG. 22B, characters to be blinked are designated in the <blink> tag and the </ blink> tag.

  In WS information 114a, personal tray information 114b, and shared tray information 114c according to the present embodiment, tags that are standardized as HTML format can be used in addition to tags that are arbitrarily defined according to the XML format. .

  In the above description, the case where the appearance of display or decoration (blinking, bordering, color conversion, thickening, etc.) is defined as a tag is exemplified. However, for example, a “user intention” such as a <warning> tag is used. Or “effect” may be defined as a tag. By using such a tag, for example, one user may imagine "blinking" as "warning", while another user has a feeling of warning when "thickening" rather than blinking, “Blinking” takes into consideration that there may be an image of “recommended”. In this case, you may make it change the display content allocated to the same tag for every client apparatus CL which each user uses. In this case, each user can freely select a display method that he / she feels, for example, “warning”. As a result, even if the same tag is used to define the client devices CL that share the workspace, each client device CL can be used for the feeling of the user who uses the client device CL. It will be displayed with a combined decoration, which is preferable.

  Next, the preview function will be described with reference to FIGS. 20 (b) and 20 (c). The personal tray information 114b shown in FIG. 20B includes a description 354 for providing a preview function. In the <preview> tag and the </ preview> tag in the description 354, “NULL” which means that no operation is performed is described as an initial value.

  Next, as shown in FIG. 14B described above, after the user performs some change operation on the alias object on the selection tray, a “preview” button 174 displayed on the left side of the display window 170. Is selected, the tray management unit 108 inputs a command line describing the contents to be previewed in the <preview> tag and the </ preview> tag shown in FIG. FIG. 20C shows a state in which this command line has been input. It can be seen that FIG. 20C includes a description 354A in which a command line corresponding to the descriptions 352 and 353 in FIG. 20B is inserted. In the description 354A, a command is described such as “command” + “id of the target entity object” + “attribute value after change”. That is, in the example shown in FIG. 20C, “change_bg_color” is a command for changing the background color, “4” is an identification number (id) that identifies the target entity object, and “yellow” is The background color after the change.

  Subsequently, the tray management unit 108 notifies the view management unit 104 that the preview function has been designated. Then, the view management unit 104 refers to the WS information 114a, changes the display attribute in accordance with the command line, and renders it. Note that the view management unit 104 only displays a change according to the command line, and the actual WS information 114a is not changed until the change is instructed by the user.

  In the above description, the contents of the personal tray information 114b have been mainly described. However, the basic data structure of the shared tray information 114c is the same, and therefore detailed description will not be repeated.

<Processing procedure>
Next, with reference to FIG. 23A to FIG. 23C, a processing procedure related to providing a work space according to the present embodiment will be described.

  FIG. 23A to FIG. 23C are flowcharts showing a processing procedure related to providing a work space according to the first embodiment of the present invention. Each step shown in FIGS. 23A to 23C is typically performed by the CPU 2 executing a program. That is, it is executed by functions corresponding to the respective units shown in FIG. It is assumed that the workspace has already been created.

  With reference to FIG. 17 and FIGS. 23A to 23C, the synchronization management unit 116 receives the WS information 114 a stored in the WS work memory 114 of the own device from the server SRV (or another client device CL). It is determined whether or not the WS information 114a newer than the last update time has been received (step S100). If the WS information 114a newer than the last update time has not been received (NO in step S100), the process proceeds to step S108.

  On the other hand, when the WS information 114a newer than the last update time is received (YES in step S100), the synchronization management unit 116 overwrites the received WS information 114a in the WS work memory 114 of the own device (step S102). ). Subsequently, the view management unit 104 updates the contents of the workspace to be displayed based on the updated WS information 114a (step S104). That is, the display of the display window 150 is updated. At the same time, the tray management unit 108 updates the contents of the selected tray (individual) and the selected tray (shared) to be displayed (step S106). That is, the display of display window 170 and display window 180 is updated. Then, the process proceeds to step S108.

  In step S108, the synchronization management unit 116 transmits the shared tray information that is newer than the last update time of the shared tray information 114c stored in the WS work memory 114 of the own device from the server SRV (or another client device CL). It is determined whether or not 114c is received. If shared tray information 114c that is newer than the last update time has not been received (NO in step S108), the process proceeds to step S114.

  On the other hand, when the shared tray information 114c that is newer than the last update time is received (YES in step S108), the synchronization management unit 116 overwrites the received shared tray information 114c in the WS work memory 114 of the own device ( Step S110). Subsequently, the tray management unit 108 updates the contents of the selected tray (shared) to be displayed (step S112). That is, the display of the display window 180 is updated. Then, the process proceeds to step S114.

  In step S114, the operation management unit 102 determines whether a new creation / change / deletion of an entity object has been operated by the user. If new creation / change / deletion of the entity object has not been operated by the user (NO in step S114), the process proceeds to step S120.

  On the other hand, when a new creation / change / deletion of a real object is operated by the user (YES in step S114), the operation management unit 102 gives an instruction corresponding to the user operation to the object management unit 106. In response to this instruction, the object management unit 106 changes the WS information 114a stored in the WS work memory 114 (step S116). Subsequently, the synchronization management unit 116 transmits the updated WS information 114a of the own device to the server device SRV (or another client device CL) (step S118). Then, the process proceeds to step S120.

  In step S <b> 120, the operation management unit 102 determines whether a view change has been operated by the user. If the view change has not been operated by the user (NO in step S120), the process proceeds to step S124.

  On the other hand, when the view change is operated by the user (YES in step S120), the operation management unit 102 gives an instruction corresponding to the user operation to the view management unit 104. In response to this instruction, the view management unit 104 displays information based on information included in the view range specified by the user among the information defined in the WS information 114a stored in the WS work memory 114. The contents of the workspace to be updated are updated (step S122). That is, the display of the display window 150 is updated. Then, the process proceeds to step S124.

  In step S124, the operation management unit 102 determines whether or not the user has operated the tray function activation. If validation of the tray function has not been operated by the user (NO in step S124), the process proceeds to step S128.

  On the other hand, when the activation of the tray function is operated by the user (YES in step S124), the operation management unit 102 gives an instruction corresponding to the user operation to the tray management unit 108. In response to this instruction, the tray management unit 108 displays the selected tray (individual) or the selected tray (shared) (step S126). That is, the display window 170 or the display window 180 is newly generated. Then, the process proceeds to step S128.

  In step S128, the operation management unit 102 determines whether or not an operation of dropping any entity object on the workspace onto the selection tray (individual) has been performed. If any entity object on the workspace has not been dropped onto the selected tray (individual) (NO in step S128), the process proceeds to step S134.

  On the other hand, when an operation of dropping any entity object on the workspace onto the selected tray (individual) is performed (YES in step S124), the operation management unit 102 instructs the tray management unit 108 to perform a user operation. Give instructions accordingly. In response to this instruction, the tray management unit 108 adds the contents associated with the dropped entity object among the contents described in the WS information 114a to the personal tray information 114b (step S130). At this time, if the personal tray information 114b is not yet stored in the WS work memory 114, the tray management unit 108 newly creates the personal tray information 114b. Subsequently, the tray management unit 108 updates the contents of the selected tray (individual) to be displayed (step S132). That is, the display of the display window 170 is updated. Then, the process proceeds to step S130.

  In step S <b> 134, the operation management unit 102 determines whether an operation of dropping any entity object on the workspace onto the selection tray (shared) has been performed. If any entity object on the workspace has not been dropped onto the selected tray (shared) (NO in step S134), the process proceeds to step S142.

  On the other hand, when an operation of dropping any entity object on the workspace onto the selected tray (shared) is performed (YES in step S134), the operation management unit 102 instructs the tray management unit 108 to perform a user operation. Give instructions accordingly. In response to this instruction, the tray management unit 108 adds the contents associated with the dropped entity object among the contents described in the WS information 114a to the shared tray information 114c (step S136). At this time, if the shared tray information 114c is not yet stored in the WS work memory 114, the tray management unit 108 newly creates the shared tray information 114c. Subsequently, the tray management unit 108 updates the contents of the selected tray (shared) to be displayed (step S138). That is, the display of the display window 170 is updated. Further, the synchronization management unit 116 transmits the updated shared tray information 114c of the own device to the server device SRV (or another client device CL) (step S140). Then, the process proceeds to step S142.

  In step S <b> 142, the operation management unit 102 determines whether or not the user has changed or deleted the alias object on the selection tray (individual). If the change / deletion of the alias object on the selection tray (individual) has not been operated by the user (NO in step S142), the process proceeds to step S148.

  On the other hand, when a change or deletion of an alias object on the selected tray (individual) is operated by the user (YES in step S142), the operation management unit 102 causes the tray management unit 108 to respond to the user operation. Give instructions. In response to this instruction, the tray management unit 108 changes the personal tray information 114b stored in the WS work memory 114 (step S144). Subsequently, the tray management unit 108 updates the contents of the selected tray (individual) to be displayed (step S146). That is, the display of the display window 170 is updated. Then, the process proceeds to step S148.

  In step S <b> 148, the operation management unit 102 determines whether or not the user has changed or deleted an alias object on the selected tray (shared). If the alias object on the selected tray (shared tray) has not been changed or deleted by the user (NO in step S148), the process proceeds to step S156.

  On the other hand, when the change / deletion of the alias object on the selected tray (shared) is operated by the user (YES in step S148), the operation management unit 102 causes the tray management unit 108 to respond to the user operation. Give instructions. In response to this instruction, the tray management unit 108 changes the shared tray information 114c stored in the WS work memory 114 (step S150). Subsequently, the tray management unit 108 updates the contents of the selected tray (shared) to be displayed (step S152). That is, the display of the display window 180 is updated. Furthermore, the synchronization management unit 116 transmits the updated shared tray information 114c of the own device to the server device SRV (or another client device CL) (step S154). Then, the process proceeds to step S156.

  In step S156, the operation management unit 102 determines whether the preview of the alias object on the selection tray (individual) has been operated by the user. If the preview of the alias object on the selection tray (individual) has not been operated by the user (NO in step S156), the process proceeds to step S162.

  On the other hand, when the preview of the alias object on the selected tray (individual) is operated by the user (YES in step S156), the operation management unit 102 gives an instruction corresponding to the user operation to the tray management unit 108. . In response to this instruction, the tray management unit 108 changes the content of the <preview> tag of the personal tray information 114b stored in the WS work memory 114 (step S158). Then, the tray management unit 108 notifies the view management unit 104 of the content change of the <preview> tag of the personal tray information 114b. In response to this notification, the view management unit 104 refers to the WS information 114a, changes the display attribute according to the content of the <preview> tag of the personal tray information 114b, and then displays the content of the workspace to be displayed. Update (step S160). That is, the display of the display window 150 is updated. Then, the process proceeds to step S162.

  In step S162, the operation management unit 102 determines whether the preview of the alias object on the selection tray (shared) has been operated by the user. If the preview of the alias object on the selection tray (share) is not operated by the user (NO in step S162), the process proceeds to step S170.

  On the other hand, when the preview of the alias object on the selected tray (shared) is operated by the user (YES in step S162), the operation management unit 102 gives an instruction corresponding to the user operation to the tray management unit 108. . In response to this instruction, the tray management unit 108 changes the contents of the <preview> tag of the shared tray information 114c stored in the WS work memory 114 (step S164). Then, the tray management unit 108 notifies the view management unit 104 of the content change of the <preview> tag of the shared tray information 114c. In response to this notification, the view management unit 104 refers to the WS information 114a, changes the display attribute according to the content of the <preview> tag of the shared tray information 114c, and then displays the content of the workspace to be displayed. Update (step S166). That is, the display of the display window 150 is updated. Further, the synchronization management unit 116 transmits the updated shared tray information 114c of the own device to the server device SRV (or another client device CL) (step S168). Then, the process proceeds to step S170.

  In step S <b> 170, it is determined whether or not the reflection of the change contents for the alias object on the selection tray (individual) on the entity object is operated by the user. If the change content for the alias object on the selection tray (individual) is not reflected on the entity object by the user (NO in step S170), the process proceeds to step S184.

  On the other hand, when the user has manipulated the change contents for the alias object on the selected tray (individual) to reflect on the actual object (YES in step S170), the operation management unit 102 notifies the tray management unit 108 to the user. Give instructions according to the operation. In response to this instruction, the tray management unit 108 outputs the changed contents in the personal tray information 114b stored in the WS work memory 114 to the object management unit 106 (step S172). In response to the output of the change content, the object management unit 106 updates the description of the entity object having the specified identification number among the content included in the WS information 114a (step S174). Subsequently, the view management unit 104 cancels the change of the display attribute accompanying the preview instruction, and updates the contents of the workspace to be displayed based on the updated WS information 114a (step S176). That is, the display of the display window 150 is updated. At the same time, the tray management unit 108 resets the contents of the <preview> tag of the personal tray information 114b stored in the WS work memory 114 (step S178) and updates the contents of the selected tray (individual) to be displayed ( Step S180). That is, the display of the display window 170 is updated. Further, the synchronization management unit 116 transmits the updated WS information 114a of the own device to the server device SRV (or another client device CL) (step S182). Then, the process proceeds to step S184.

  In step S 184, it is determined whether or not the user has operated the reflection of the change contents for the alias object on the selected tray (shared) on the entity object. If the user has not manipulated the change contents of the alias object on the selection tray (shared) to reflect the actual object (NO in step S184), the process returns.

  On the other hand, when the user has performed an operation to reflect the change contents for the alias object on the selected tray (shared) to the actual object (YES in step S184), the operation management unit 102 notifies the tray management unit 108 to the user. Give instructions according to the operation. In response to this instruction, the tray management unit 108 outputs the changed contents in the shared tray information 114c stored in the WS work memory 114 to the object management unit 106 (step S186). In response to the output of the change content, the object management unit 106 updates the description of the entity object having the specified identification number among the content included in the WS information 114a (step S188). Subsequently, the view management unit 104 cancels the display attribute change accompanying the preview instruction, and then updates the contents of the workspace to be displayed based on the updated WS information 114a (step S190). That is, the display of the display window 150 is updated. At the same time, the tray management unit 108 resets the contents of the <preview> tag of the shared tray information 114c stored in the WS work memory 114 (step S192) and updates the contents of the selected tray (shared) to be displayed (step S192). Step S194). That is, the display of the display window 170 is updated. Furthermore, the synchronization management unit 116 transmits the updated WS information 114a and shared tray information 114c of the own device to the server device SRV (or another client device CL) (step S196). Then, the process returns.

<Sequence>
Sequence diagrams corresponding to the steps shown in FIGS. 23A to 23C are as shown in FIGS. 24A to 24C.

  24A to 24C are sequence diagrams showing a processing procedure related to provision of a work space according to the first embodiment of the present invention. In the sequence diagrams shown in FIGS. 24A to 24C, as a method for ensuring the consistency of data (information) between the client device CL and the server device SRV, a partner to which a device in which some change has occurred should be notified. Although the configuration in which the notification is actively made first is employed, the server device SRV may periodically check for updates.

  In the sequence diagrams shown in FIGS. 24A to 24C, when the display in the workspace and / or the selection tray is updated in any of the client devices CL, the WS information 114a for performing these displays, and The configuration for sharing the personal tray information 114b and the shared tray information 114c will be exemplified, but only a command indicating that an event has occurred (information such as which attribute value has been changed) is exchanged, and The display may be updated based on the difference.

<Operation / Effects of First Embodiment>
According to the first embodiment of the present invention, it is possible to selectively handle only necessary objects without affecting objects already created on the workspace.

  Further, according to the first embodiment of the present invention, the contents and display state of the actual object associated with the alias object can be visually recognized even during the selection operation of the alias object or in the selected state. Typically, in a scene where documents or images are edited, multiple locations are selected simultaneously, batch conversion, an overview of the selected location and the overall positional relationship, and status confirmation after editing for the selected location Can be facilitated.

  As a result, the meaning of the target object can always be understood, and as a result, an extra operation such as confirming the meaning of the target object is not necessary, so that the work can be continued without interrupting thinking.

  Further, according to the first embodiment of the present invention, only the alias object added to the selection tray (shared) is shared with the other client device CL (user), and the alias object added to the selection tray (individual). Is displayed only on the client device CL used by the user. Therefore, when working in a group of a plurality of members, only necessary alias objects can be arbitrarily shared according to the work process and situation, the type of target entity object, and the like.

  In the editing work for documents and images described above, there are cases where objects created and edited by each member are scattered on the same workspace. Considering a scene in which these objects are aggregated, according to Embodiment 1 of the present invention, it is not necessary for one user to select all objects, so even if the workspace is too large, When a plurality of users share and select an object, it is possible to suppress the occurrence of problems such as omissions in selection targets and the time required for selection.

  In addition, there are many cases where the contents created by other members cannot be understood at a glance, but multiple users can share and select objects to select the target object properly without omission. it can.

  In addition, it is possible to select an object based on specialized skills and expertise possessed by a specific member, and to perform a task such as a chairman or other representative member freely determining the processing for the selected object at its discretion. it can.

  In addition, according to the first embodiment of the present invention, work such as arranging closely related objects close to each other on the selection tray or arranging them with the same display size is arranged in the workspace. This can be done without affecting the upper entity object. At the same time, such a work result on the selection tray can be used as it is, and a target object and edit contents can be subsequently determined and operated. Furthermore, the editing content for such an alias object can be easily reflected in the associated entity object.

  Further, according to the first embodiment of the present invention, the operation for further narrowing down the alias objects is performed after checking the selection state and arrangement state of the plurality of alias objects existing on the selection tray, and the necessary aliases are also displayed. An operation for categorizing (classifying) objects can be easily performed. For example, when there are four alias objects A, B, C, and D on the selection tray, the display mode of the alias object A is set to border / bold / enlarged, and the alias object B is set to The display mode can be set to border / enlarge, the display mode can be set to bold / enlarge for the alias object C, and the display mode can be set to bold only for the alias object D. Further, in order to instruct such a complex operation, the alias objects A and B are selected to indicate “Bordering”, and then the alias objects A and C are selected to indicate “Bold”. Further, all the alias objects A to D are selected and “enlargement” is instructed, for example, a total of three operations are sufficient. Therefore, even when a complex operation is instructed, it can be performed efficiently.

[Embodiment 2]
In the above-described first embodiment, a system having a so-called server client configuration has been illustrated. In contrast, in the second embodiment, a so-called peer-to-peer system will be described.

<Overall configuration>
FIG. 25 is a schematic configuration diagram of an information processing system for providing a work space according to the second embodiment of the present invention.

  Referring to FIG. 25, the information processing system according to the present embodiment includes a plurality of client devices CL1 to CLN that are a plurality of information processing devices connected to each other via a network NW so as to be able to perform data communication. That is, in the information processing system according to the present embodiment, there is no server device, and each client device CL exchanges data directly with all other client devices CL to perform synchronization processing, etc. To complete. Since other configurations are the same as those in the first embodiment, detailed description will not be repeated.

  FIG. 26 is a schematic diagram showing data exchange in the second embodiment of the present invention. Referring to FIG. 26, the outline of the synchronization processing according to the present embodiment is as follows: WS information 114a held by each of client devices CL1 to CLN and WS information 114a held by another client device CL. In addition, there is direct synchronization between the shared tray information 114c held by each of the client devices CL1 to CLN and the shared tray information 114c held by another client device CL. It is done.

  Note that the timing of data transmission between client devices CL, other client devices CL to be transmitted, transmission direction, transmission contents (whether or not all transmissions are transmitted), information processing system configuration and performance It can be arbitrarily set according to the above.

  Since other configurations are the same as those in the first embodiment, detailed description will not be repeated.

<Operation / Effect of Embodiment 2>
According to Embodiment 2 of the present invention, in addition to the operations and effects in Embodiment 1 described above, the following operations and effects can be obtained. That is, according to the second embodiment of the present invention, since a peer-to-peer configuration is adopted, even in a place where a server cannot be connected, such as outside the company, only the terminals of members who need to share work are connected. Can work together.

[Embodiment 3]
In the first embodiment described above, each of the client device CL and the server device SRV has personal tray information for providing a personal tray function, and shared tray information for providing a shared tray function. An example of a configuration in which each of them is held separately is illustrated. On the other hand, the third embodiment exemplifies a configuration that defines whether the object is for personal use or shared for each alias object described in the tray information.

  FIG. 27 is a schematic diagram showing a control structure realized by the client device CL according to the third embodiment of the present invention. The control structure shown in FIG. 27 is a control structure realized by the client device CL according to the first embodiment shown in FIG. 17 and is replaced with a form in which the personal work tray information 114b and the shared tray information 114c are held in the WS work memory 114. The tray information 114d is retained. Others are the same as in FIG. 17, and thus detailed description will not be repeated.

<Tray function>
Next, a tray function according to the present embodiment will be described with reference to FIGS. As described above, the tray function according to the present embodiment is intended to be used by each individual member in alias object units, or to be shared by members belonging to the same group. Can be set.

  FIG. 28 is a diagram for illustrating an operation in the tray function on the client device CL according to the third embodiment of the present invention. FIG. 29 is a diagram showing an example of the contents of the tray information corresponding to FIG.

  The tray function according to the present embodiment is activated when the user selects a “display” button displayed at the top of the display window 150 with the cursor CRS or the like, as in the procedure shown in FIG. By such an operation, a display window 170A indicating the selected tray is newly generated. The selection tray that appears as the display window 170A serves both for personal use and for sharing.

  As shown in FIG. 28A, in a state in which a display window 150 that provides a workspace and a display window 170A that indicates a selection tray are displayed, for example, the user of the client device CL1 moves an arbitrary object on the workspace. Consider adding to the selection tray. That is, when the user of the client device CL1 drags and drops the objects OBJ4, OBJ5, OBJ8 on the display window 150 to the display window 170, the corresponding alias objects ALS1, ALS2, ALS3 are displayed on the selected tray. Each appears. As a method of adding to the selection tray, in addition to the above-mentioned drag and drop, the object on the workspace is selected, the object is stored by the pull-down menu, and the drop destination is specified with the destination to be dropped. Another method such as specifying a command may be used. In other words, any method may be employed as long as an object on the designated workspace can be dropped at a designated position on the selection tray.

The essence of these alias objects is the same as that in the first embodiment. That is, the alias object on the selection tray exists independently of the entity object on the workspace. Therefore, in principle, even if the user performs an operation such as moving, editing, or deleting an alias object on the selection tray, the actual object on the workspace is not affected. Since the other points are the same as in the first embodiment, detailed description will not be repeated. In the selection tray according to the present embodiment, as an example, the generated alias object has a personal mode (non- Shared mode). Then, the user of the client device CL can selectively set the alias object that should be shared to the sharing mode.

  As a specific example, as shown in FIG. 28A, the user of the client device CL1 arranges the displayed cursor CRS on the alias object ALS2 on the selection tray, and then performs a click operation (typically) In particular, when right-clicking), a dialog 190 for switching between the shared mode and the non-shared mode is displayed. In this dialog 190, when the user designates “selection is shared”, the designated alias object ALS2 is switched from “non-shared mode” to “shared mode”.

  By this operation, as will be described later, information in which the alias object ALS2 is arranged on the selection tray is transmitted to the other client devices CL2 to CLN. As a result, as shown in FIG. 28B, the alias object ALS2 set to the “shared mode” is displayed on the selection tray in each of the other client devices CL2 to CLN.

  On the other hand, the alias objects ALS1 and ALS3 that are maintained in the “non-shared mode” are not displayed on the selection tray in each of the other client devices CL2 to CLN.

  Such a function is similarly provided in the operation on the selection tray of any client device CL. Therefore, each user who uses the client device CL can realize an intellectual creation work by a plurality of users by setting an alias object that he / she thinks should be shared in a group of a plurality of members to “shared mode”. .

  Next, data processing for realizing the operation as shown in FIG. 28 will be described with reference to FIG. Alias objects ALS1, ALS2, and ALS3 as shown in FIG. 28A are defined by tray information as shown in FIG. That is, descriptions 321, 322, and 323 correspond to alias objects ALS1, ALS2, and ALS3, respectively. Descriptions 321 and 323 that define the alias objects ALS1 and ALS3 maintained in the “non-shared mode” are basically the same as the contents of the tray information in the first embodiment. However, in the description 322 that defines the alias object ALS2 set to “shared mode”, a <share_mode> tag and a </ share_mode> tag indicating the “shared mode” are embedded. That is, the value of “ON” is defined by being surrounded by these <share_mode> tags and </ share_mode> tags, so that the corresponding alias object is interpreted as being in “shared mode”.

  Therefore, when the user sets any alias object to “shared mode”, the tray management unit 108 (FIG. 27) of each client device CL describes “<share_mode> ON </ share_mode>” in the corresponding description. On the other hand, when the user sets any alias object to the “non-shared mode”, the description “<share_mode> ON </ share_mode>” is deleted from the corresponding description. Note that a <share_mode> tag and a </ share_mode> tag are embedded in the description corresponding to each alias object, and the value is set to “ON” in accordance with the designation of “shared mode” or “non-shared mode”. Alternatively, it may be rewritten as “OFF”.

  Further, only the description of the alias object set in the sharing mode is shared among the client devices CL. That is, only the description 322 corresponding to the alias object ALS2 set to the shared mode among the descriptions shown in FIG. 29A is transmitted to the other client devices CL2 to CLN. In this way, the processing time and the amount of communication data can be reduced by transmitting and receiving only the description set to the shared mode.

<Sequence>
A synchronization process associated with switching between the shared mode and the non-shared mode in units of alias objects as described above will be described with reference to FIG.

  FIG. 30 is a sequence diagram showing a processing procedure related to the tray function according to the third embodiment of the present invention. Each process shown in FIG. 30 is typically performed by the CPU 2 executing a program. That is, it is executed by functions corresponding to the respective units shown in FIG.

  Referring to FIG. 30, first, when an operation of dropping any entity object on the workspace onto the selected tray is performed (sequence SQ200), operation management unit 102 causes tray management unit 108 to respond to the user operation. Give instructions. In response to this instruction, the tray management unit 108 adds contents associated with the dropped entity object among the contents described in the WS information 114a to the tray information 114d (sequence SQ202). At this time, if the tray information 114d is not yet stored in the WS work memory 114, the tray management unit 108 newly creates the tray information 114d. Subsequently, the tray management unit 108 updates the contents of the selected tray to be displayed (sequence SQ204).

  Next, when an operation to change the alias object of the selected tray to the shared mode is performed (sequence SQ206), the operation management unit 102 gives an instruction according to the user operation to the tray management unit 108. In response to this instruction, the tray management unit 108 updates the tray information 114d corresponding to the designated alias object on the selected tray. That is, the tray management unit 108 adds or deletes the description <share_mode> ON </ share_mode> as shown in FIG.

  Subsequently, the synchronization management unit 116 transmits the tray information changed to the shared mode among the descriptions of the alias objects defined in the updated tray information 114d of the own device to the server SRV (sequence SQ210). That is, not all the contents of the tray information 114d but only information defining the alias object set to the sharing mode is transmitted.

  On the other hand, when receiving the tray information from the client device CL, the synchronization management unit 216 (FIG. 18) of the server device SRV updates the tray information stored in the WS work memory 214 of the own device (sequence). SQ212). Furthermore, synchronization management section 216 (FIG. 18) of server SRV transmits the tray information stored in WS work memory 214 of the own apparatus to other client apparatuses CL2 to CLN (sequence SQ214).

  Subsequently, when receiving the tray information from the server apparatus SRV, the synchronization management unit 116 of the client apparatuses CL2 to CLN updates the tray information stored in the WS work memory 214 of the own apparatus (sequence SQ216). At this time, if the tray information 114d is not yet stored in the WS work memory 114, the tray management unit 108 newly creates the tray information 114d. Subsequently, the tray management unit 108 updates the contents of the selected tray to be displayed (sequence SQ218).

  By such a series of sequences, the alias object set in the sharing mode in any one of the client devices CL is shared with the other client devices CL2 to CLN.

Other configurations and processes are the same as those in the first or second embodiment described above, and thus detailed description thereof will not be repeated. <Operation and effect of the third embodiment>
According to Embodiment 3 of the present invention, in addition to the operations and effects in Embodiment 1 described above, the following operations and effects can be obtained. That is, according to the third embodiment of the present invention, the “shared mode” and the “non-shared mode” can be set on a per-alias object basis, so that it is necessary to change from the “shared mode” to the “non-shared mode”. In some cases, or when it is necessary to change from the “non-shared mode” to the “shared mode”, these changes can be performed with a simpler operation.

  Further, according to the third embodiment of the present invention, since only data corresponding to the alias object set to the shared mode is transmitted and received between the client device CL and the server device SRV, the processing time and The amount of communication data can be reduced.

[Embodiment 4]
In the above-described third embodiment, the configuration that can set whether to share for each object (alias object) on the selection tray has been exemplified. On the other hand, in the fourth embodiment, for each alias object, in addition to whether to share, in the case of sharing, a configuration that can specify which user to share is exemplified.

  FIG. 31 is a schematic diagram showing a control structure realized by the client device CL according to the fourth embodiment of the present invention. The control structure shown in FIG. 31 is the same as the control structure realized by the client device CL according to the first embodiment shown in FIG. 17, but the user authentication unit 134 and the user management unit 132 are added, and the WS work memory 114 is personalized. Instead of the form for holding the tray information 114b and the shared tray information 114c, a form for holding the tray information 114e is adopted.

  The user authentication unit 134 authenticates a user who uses the workspace according to the present embodiment in the corresponding client device CL. Specifically, the user authentication unit 134 prompts the user who requests use of the workspace to input an ID and a password. When the user inputs an ID and password, user authentication is performed with reference to a predetermined database. If the user authentication is successful, the user is allowed to use the workspace and holds the user name (user ID) currently in use (logged in). The configuration for performing user authentication is a well-known technique and will not be described in further detail. In the present embodiment, it is only necessary that the user who uses each client device CL can be specified, and therefore authentication using a password is not necessarily required.

  The user management unit 132 manages, for example, a user who created each object (alias object) on the selection tray and a user who is allowed to share each alias object based on the authentication result in the user authentication unit 134.

Others are the same as in FIG. 17, and thus detailed description will not be repeated.
<Tray function>
Next, a tray function according to the present embodiment will be described with reference to FIG. As described above, the tray function according to the present embodiment is intended to be used by each individual user on an alias object basis, or to be shared with other users. Can be set. Furthermore, with respect to an alias object intended to be shared with other users, it can be specified with which user the alias object is shared.

  FIG. 32 is a diagram for describing an operation in the tray function on the client devices CL1 to CL3 according to the fourth embodiment of the present invention. FIG. 32A shows an example of a display window 170B that is a selection tray in the client device CL1. Here, it is assumed that the user (ID is “tanaka”) authenticated by the user authentication unit 134 is logged in to the client device CL1. FIG. 32B shows an example of a display window 170B which is a selection tray in the client device CL2. Here, it is assumed that the user authenticated by the user authentication unit 134 (ID is “hayashi”) is logged in to the client device CL2. FIG. 32 (c) shows an example of a display window 170B which is a selection tray in the client device CL3. Here, it is assumed that the user (ID is “suzuki”) authenticated by the user authentication unit 134 is logged in to the client device CL3.

  Note that the tray function according to the present embodiment is activated when the user selects a “display” button displayed at the top of the display window 150 with the cursor CRS or the like, as in the procedure shown in FIG. By such an operation, a display window 170B indicating the selected tray is newly generated. The selection tray that appears as the display window 170B serves both for personal use and for sharing.

  As in the other embodiments described above, each user who has logged in to the client device CL drags and drops an arbitrary real object on the workspace to the display window 170B, so that it is displayed on the selection tray. Any alias object can be added to. As a method of adding to the selection tray, in addition to the above-mentioned drag and drop, the object on the workspace is selected, the object is stored by the pull-down menu, and the drop destination is specified with the destination to be dropped. Another method such as specifying a command may be used. In other words, any method may be employed as long as an object on the designated workspace can be dropped at a designated position on the selection tray. The essence of the added alias object is the same as that in the first embodiment.

  Further, it is assumed that the alias object added in this way is set to the personal mode, that is, sharing with other users is disabled as an initial value.

  First, as shown in FIG. 32A, it is assumed that “tanaka”, who is a user who has logged in to the client device CL1, has added the alias object ALS1 to the selection tray of the client device CL1. Further, as shown in FIG. 32C, it is assumed that “suzuki” who is a user logged in to the client device CL3 adds the alias objects ALS2 and ALS3 to the selection tray of the client device CL3.

  Subsequently, as shown in FIG. 32A, a case where the user “tanaka” desires to share the alias object ALS1 with the other two users (“hayashi” and “suzuki”). Think. In such a case, the user “tanaka” places a cursor CRS to be displayed on the alias object ALS1 on the selection tray and then performs a click operation (typically right click) on the mouse. Then, a dialog 196A for designating a public permission destination is displayed. This dialog 196A designates another user who should share the target alias object. More specifically, this dialog 196A displays a list of users who are logged in to the other client devices CL2 to CLN. The user can arbitrarily select a partner with whom the alias object should be shared among the displayed users.

  In FIG. 32A, it is assumed that the other two users (“hayashi” and “suzuki”) are both designated. Then, as shown in FIGS. 32 (b) and 32 (c), the target alias object ALS1 is the client device CL2 to which “hayashi” and “suzuki” designated as public permission destinations are respectively logged in. And displayed on the selection tray of CL3.

  Further, as shown in FIG. 32C, a case where the user “suzuki” desires to share the alias object ALS2 only with the user “tanaka” is considered. In such a case, the user “suzuki” places a cursor CRS to be displayed on the alias object ALS2 on the selection tray and then performs a click operation (typically right click) on the mouse. Then, as described above, a dialog 196B for designating a public permission destination is displayed. Then, only “tanaka” is designated as a public permission destination for the alias object ALS2 targeted for the user “suzuki”. Then, as shown in FIG. 32A, the target alias object ALS2 is displayed in the selection tray of the client device CL1 that is the login destination of “tanaka” designated as the public permission destination. . However, as shown in FIG. 32B, it is not displayed in the selection tray of the client device CL2 that is the login destination of “hayashi” that is not designated as the public permission destination.

  Further, as shown in FIG. 32C, consider a case where the user “suzuki” wants to use the alias object ALS3 for his / her own examination. In such a case, the user “suzuki” does not perform any operation on the alias object ALS3 on the selection tray. Then, as shown in FIGS. 32A and 32B, for this alias object ALS3, the selection of other client devices CL excluding the client device CL3 that is the login destination of the user “suzuki” It is not displayed on the tray.

  Next, data processing for realizing the operation shown in FIG. 32 will be described with reference to FIG. FIG. 33 is a diagram showing an example of the contents of the tray information corresponding to FIG. FIG. 33A shows an example of tray information held in the client device CL1 that is the login destination of the user “tanaka”. FIG. 33B shows an example of tray information held in the client device CL2 that is the login destination of the user “hayashi”. FIG. 33C shows an example of tray information held by the client device CL3 that is the login destination of the user “suzuki”.

  The alias objects ALS1, ALS2, and ALS3 shown in FIG. 32 are defined by tray information as shown in FIG. More specifically, the alias object ALS1 is defined by a description 331 that exists in common in FIGS. 33 (a) to 33 (c). This description 331 is basically the same as the contents of the tray information in the first embodiment, but particularly for the alias object according to the present embodiment, for specifying the user who added (created) the alias object. Information (ID) is added. That is, the description 331 includes a <user id => tag and a </ user> tag that specify the user who added (created) the corresponding alias object. Note that the <user id => tag and the </ user> tag that specify the user who added (created) the corresponding alias object are added to any alias object (see FIG. 33C).

  Furthermore, for the alias object ALS1, the user “hayashi” and the user “suzuki” are designated as public permission destinations, so the description 331 includes definitions of these designations. That is, the description 331 includes an <access_flag => tag and a </ access_flag> tag that specify a public permission destination (user) of the corresponding alias object. As shown in FIG. 33 (b), when a plurality of users are designated, they are described using a logical symbol “|”. In the description 331 shown in FIG. 33B, “hayashi” and “suzuki” are defined by being surrounded by an <access_flag => tag and a </ access_flag> tag in accordance with a user operation.

  The alias object ALS2 is defined by a description 332 that exists in common in FIGS. 33 (a) and 33 (c). The contents of the description 332 are the same as the contents of the description 331 corresponding to the alias object ALS1 described above. The description 332 defines “tanaka”, which is specified as the only public permission destination surrounded by the <access_flag => tag and the </ access_flag> tag.

  On the other hand, the alias object ALS3 that is not shared with any other user is defined by the description 333 existing in FIG. In this description 333, “NULL” is defined, which is surrounded by the <access_flag => tag and the </ access_flag> tag, which means that there is no public permission destination.

  As described above, the tray management unit 108 (FIG. 31) of each client device CL can specify the public permission destination when the user sets to share any alias object with a specific user. The corresponding descriptions are updated sequentially.

<Sequence>
Since synchronization processing related to the sharing mode and the non-sharing mode in units of alias objects according to the present embodiment as described above is similar to the sequence diagram shown in FIG. 30 described above, detailed description will not be repeated.

Other configurations and processes are the same as in the first to third embodiments described above, and thus the detailed description will not be repeated. <Operation and effect of the fourth embodiment>
According to Embodiment 4 of the present invention, in addition to the operations and effects in Embodiments 1 and 3 described above, the following operations and effects can be obtained. That is, according to the fourth embodiment of the present invention, whether or not to share in alias object units can be set, and for the alias object set to be shared, the sharing destination (partner to be shared) is designated. Can do. As a result, for example, when a plurality of subgroups are provided in the same group consisting of a plurality of members, an alias object is shared only among members belonging to the corresponding subgroup. Can be adopted. Alternatively, the present invention can be applied to a usage pattern in which a final decision is made between leaders of a plurality of subgroups.

[Other embodiments]
The program according to the present invention may be a program module that is provided as a part of a computer operating system (OS) and that calls necessary modules in a predetermined arrangement at a predetermined timing to execute processing. . In that case, the program itself does not include the module, and the process is executed in cooperation with the OS. A program that does not include such a module can also be included in the program according to the present invention.

  Furthermore, the program according to the present invention may be provided by being incorporated in a part of another program. Even in this case, the program itself does not include the module included in the other program, and the process is executed in cooperation with the other program. Such a program incorporated in another program can also be included in the program according to the present invention.

  The provided program product is installed in a program storage unit such as a hard disk and executed. Note that the program product includes the program itself and a storage medium in which the program is stored.

  Furthermore, part or all of the functions realized by the program according to the present invention may be configured by dedicated hardware.

  The embodiment disclosed this time should be considered as illustrative in all points and not restrictive. The scope of the present invention is defined by the terms of the claims, rather than the description above, and is intended to include any modifications within the scope and meaning equivalent to the terms of the claims.

  2 CPU, 4 internal bus, 6 output device, 8 communication interface, 10 input device, 12 hard disk (HDD), 14 memory, 16 CD-ROM drive, 16a CD-ROM, 18 flexible disk (FD) drive, 18a flexible disk , 100 processing unit, 102 operation management unit, 104 view management unit, 106 object management unit, 108 tray management unit, 110 WS space management unit, 112 input / output unit, 114, 214 work memory, 114a, 214a WS information, 114b personal Tray information, 114c, 214c Shared tray information, 114d, 114e Tray information, 116, 216 Synchronization management unit, 120 WS storage unit, 130 Input / output control unit, 132 User management unit, 134 User authentication unit, CL, CL1-C N client device, NW network, SRV server device.

Claims (11)

An information processing system providing a virtual work space accessible by a plurality of users,
A plurality of information processing devices (CL) connected to each other so as to be able to perform data communication,
Each of the plurality of information processing devices
And holding means (114) for holding first information defining the virtual work space and a first object included in the virtual work space, wherein the first information is exchanged with another information processing apparatus. Is synchronized,
First display means (104, 106) for displaying part or all of the contents of the virtual work space to the user based on the first information;
In response to a user operation, second display means (104, 108) for displaying a second object that is associated with the first object included in the virtual work space and that can be changed independently of the first object. )When,
Information including synchronization means (116) for synchronizing and holding second information defining the instructed second object in response to an instruction to be shared among the plurality of information processing devices Processing system. The first display means includes a first area for a second object that should be shared among the plurality of information processing devices, and a second area for a second object that should not be shared between the plurality of information processing devices. Display the area separately from the display of the contents of part or all of the virtual workspace,
The synchronization means synchronously holds the second information corresponding to the second object displayed in the first area, and stores the second information corresponding to the second object displayed in the second area. The information processing system according to claim 1, which is not synchronized. Each of the plurality of information processing devices is either a first mode shared among the plurality of information processing devices or a second mode not shared between the plurality of information processing devices for each second object. Further includes mode setting means for accepting the setting of
The synchronization means synchronously holds the second information corresponding to the second object set in the first mode, and stores the second information corresponding to the second object set in the second mode. The information processing system according to claim 1, which is not synchronized. Each of the plurality of information processing devices
Authentication means for authenticating a user who uses the information processing apparatus;
A sharing destination setting means for accepting a setting of a user permitted to share for each second object;
The synchronization means holds the second information corresponding to the second object in synchronization with an information processing apparatus used by a user who is set to allow the sharing of the second object. The information processing system according to claim 1. The first information is:
Including identification information associated with the first object and a description defining the entity of the first object;
The second display means includes
The information processing system according to claim 1, further comprising means for holding the identification information for specifying the first object in association with the second object. The second display means includes
The information processing system according to claim 1, further comprising means for changing a display position of the second object independently of the first object in response to a user operation. The second display means includes
The information processing system according to claim 1, further comprising means for changing a display mode of the second object independently of the first object in response to a user operation. The second display means can display a plurality of the second objects side by side,
The second display means includes
The information processing system according to claim 1, further comprising means for adding an object that associates the second objects with each other in response to a user operation. At least one of the plurality of information processing apparatuses is
The information processing system according to claim 1, further comprising a reflecting unit that reflects changes made to the second object in the first object in response to a user operation. An information processing device (CL) that provides a virtual work space,
And holding means (114) for holding first information defining the virtual work space and a first object included in the virtual work space, wherein the first information is exchanged with another information processing apparatus. Is synchronized,
First display means (104, 106) for displaying part or all of the contents of the virtual work space to the user based on the first information;
In response to a user operation, second display means (104, 108) for displaying a second object that is associated with the first object included in the virtual work space and that can be changed independently of the first object. )When,
Synchronizing means (116) for holding the second information defining the instructed second object in synchronization with the other information processing apparatus in response to the instruction to share with the other information processing apparatuses An information processing apparatus comprising: An information processing method for providing a virtual work space accessible by a plurality of users using a plurality of information processing apparatuses connected to each other so as to be capable of data communication,
Each of the plurality of information processing devices holds first information defining the virtual work space and a first object included in the virtual work space (S102);
Synchronizing the first information held by each of the plurality of information processing devices (S116, S118);
A step (S104) in which one information processing device of the plurality of information processing devices displays part or all of the contents of the virtual work space to the user based on the first information;
The information processing apparatus displays a second object associated with the first object included in the virtual work space and changeable independently of the first object in response to a user operation (S110, S112; S136, S138; S150, S152);
In response to the instruction that the information processing apparatus should be shared among the plurality of information processing apparatuses, the second information defining the instructed second object is synchronized with the other information processing apparatuses. An information processing method comprising: step (S140; S154).