JP7051057B2 - Content sharing system - Google Patents

Description

The present invention relates to a system for jointly editing contents such as figures by a plurality of users.

A system has been proposed in which a plurality of terminal devices are connected to a server device, and a plurality of users can jointly edit and view a figure or the like (for example, Patent Document 1). As a method for performing joint editing in this way, a differential update method and a total update method are mainly used.

In the whole update method, even if only a part of the object is edited in each terminal device, all the information including other objects is transmitted to the server device, and this is transmitted from the server device to the other terminal device. do. The terminal device updates the information of all objects based on the received information.

In the difference update method, only the information of the object edited in each terminal device is transmitted to the server device, and this is transmitted from the server device to another terminal device. The terminal device updates only the information of the object based on the received information.

JP-A-2010-278656

The above-mentioned overall update method has an advantage that it is easy to maintain the same state between the terminal devices because all the objects are rewritten by the received information in each terminal device. However, on the other hand, since the data of all the objects is transmitted, the amount of transmitted data is large, and there is a problem that the immediacy to the change of the object is low. Further, when a plurality of users edit at the same time, there is a problem that only one of the edits is selected and the other edit is invalid even if the edits are compatible with each other.

The difference update method has an advantage that the amount of transmitted data is small, the immediacy can be improved, and both can be effective when a plurality of users perform compatible editing.

However, in the differential update method, if the same object is edited on multiple terminal devices at the same time, there is a problem that the editing result becomes unexpected, or the objects on each terminal device are in the same state. There was a problem that it was difficult to keep.

The explanation of this problem is as follows. As shown in FIG. 32, terminal devices T1 and T2 are connected to the server device S. It is assumed that both the terminal devices T1 and T2 are in the state where the object is displayed in the upper left (see (a) and (b)). From this state, it is assumed that the object is moved to the right by 50 in the terminal device T1 (see (c)). At about the same time, it is assumed that the object is moved down by 20 in the terminal device T2 (see (d)).

The terminal device T1 transmits the operation content that the object has moved 50 to the right to the server device S, and the server device S transmits this operation content to the terminal device T2. In response to this, the terminal device T2 moves the object that was moving to the lower left by 50 to the right (see (f)).

On the other hand, the terminal device T2 transmits the operation content that the object has moved down by 20 to the server device S, and the server device S transmits this operation content to the terminal device T1. In response to this, the terminal device T1 moves the object that had been moved to the upper right by 20 downward (see (e)).

As described above, the user of the terminal device T1 tried to move the object to the upper right, but the result was to move the object to the lower right, and the user of the terminal device T2 tried to move the object to the lower left. Nevertheless, it results in moving to the lower right.

The problem here is that the object moves to a lower right position that was not intended by any user. That is, there is a problem that the operation result of the object cannot be predicted by any user, and the operation result that is not intended by any user is generated.

In order to solve such a problem, a method of transmitting the operation result can be considered. FIG. 33 describes a problem in transmitting the operation result. It is assumed that both the terminal devices T1 and T2 are in the state where the object is displayed in the upper left (see (a) and (b)). From this state, it is assumed that the object is moved to the right by 50 in the terminal device T1 and as a result, the object is moved to the upper right (see (c)). At about the same time, it is assumed that the object is moved down by 20 in the terminal device T2, and as a result, it is moved to the lower left (see (d)).

The terminal device T1 transmits an operation result that the object has moved to the upper right to the server device S, and the server device S transmits this operation result to the terminal device T2. In response to this, the terminal device T2 moves the object that was moving to the lower left to the upper right that was received as the operation result (see (f)).

On the other hand, the terminal device T2 transmits an operation result that the object has moved to the lower left to the server device S, and the server device S transmits this operation result to the terminal device T1. In response to this, the terminal device T1 moves the object that has been moved to the upper right to the lower left received as an operation result (see (e)).

The problem here is that the operation result displayed on the terminal device T1 and the operation result displayed on the terminal device T2 are different. This is a fatal problem in co-editing.

It is an object of the present invention to provide a system that solves at least one of the above problems.

Hereinafter, the independently applicable features of the present invention are listed.

(1) (2) (3) The joint editing system according to the embodiment of the present invention is a content joint editing system including a server device and two or more terminal devices capable of communicating with the server device.
The server device includes an operation information recording means for recording operation information received from each terminal device in a recording unit, and an operation information distribution means for distributing the operation information recorded in the recording unit to each terminal device.
The terminal device operates the object based on a recording unit that records the feature coordinates of the object and the total amount of affine operations, a direct operation receiving means that accepts an operation on the object, and an operation on the object received by the direct operation receiving means. , The feature coordinates of the object and the total amount of affine operations are updated based on the operation on the object received by the direct operation display means for displaying the operation result on the display unit and the direct operation reception means, and the total amount of affine operations is used as the operation information. The object recorded in the recording unit when it receives the direct operation transmitting means to be transmitted to the server device, the indirect operation receiving means to receive the operation information received from the server device, and the operation information received by the indirect operation receiving means. The initial feature coordinates of the object are calculated based on the current feature coordinates of the object and the total amount of affine operations, and the feature coordinates after the operation are calculated based on the initial feature coordinates and the total amount of affine operations received. Indirect operation display means that calculates the operation result and displays the operation result on the display unit, and the indirect operation that updates the feature coordinates and the total amount of affine operations recorded in the recording unit with the feature coordinates after the operation and the total amount of affine operations received. It is equipped with a recording means.

Therefore, by exchanging the total amount of affine operations, it is possible to unify the operations in each terminal device.

(4) The joint editing system according to the present invention is characterized in that the direct operation transmission means transmits operation information to another terminal device via a server device.

Therefore, the operation of each terminal device can be unified by the server device.

(5) (6) (7) The joint editing system according to the present invention is a content joint editing system including a server device and two or more terminal devices capable of communicating with the server device.
The server device includes an operation information recording means for recording operation information received from each terminal device in a recording unit, and an operation information distribution means for distributing the operation information recorded in the recording unit to each terminal device.
The terminal device operates the object based on a recording unit that records the feature coordinates of the object and the total amount of affine operations, a direct operation receiving means that accepts an operation on the object, and an operation on the object received by the direct operation receiving means. , The feature coordinates of the object are updated based on the operation on the object received by the direct operation display means for displaying the operation result on the display unit and the direct operation reception means, and the inverse characteristic of the total amount of affine operations is added to the updated feature coordinates. Direct operation transmission means for transmitting the initial feature coordinates multiplied by An indirect operation that calculates the feature coordinates after the operation based on the total amount of affine operations of the object recorded in the recording unit and the initial feature coordinates that are the operation information, and displays the operation result on the display unit. It is provided with a display means and an indirect operation recording means for updating the feature coordinates recorded in the recording unit with the feature coordinates after the operation.

Therefore, even when the object is uniquely edited, the operation in each terminal device can be unified by transmitting the feature coordinates at the time of editing.

(8) The joint editing system according to the present invention is characterized in that the direct operation transmission means transmits operation information to another terminal device via a server device.

Therefore, the operation of each terminal device can be unified by the server device.

(9) (10) (11) The joint editing system according to the present invention is a content joint editing system including a server device and two or more terminal devices capable of communicating with the server device.
The server device includes an operation information recording means for recording operation information received from each terminal device in a recording unit, and an operation information distribution means for distributing the operation information recorded in the recording unit to each terminal device.
The terminal device includes a recording unit that records the feature coordinates of an object and the total amount of affine operations, a direct operation receiving means that accepts feature coordinate operations or affine operations on an object, and a feature coordinate operation or affine on an object that is received by the direct operation receiving means. If the operation is a feature coordinate operation based on the operation on the object received by the direct operation display means that operates the object based on the operation and displays the operation result on the display unit and the direct operation reception means, the operation is concerned. The feature coordinates of the object are updated, and the edited initial feature coordinates obtained by multiplying the updated feature coordinates by the inverse characteristic of the total amount of the affine operation are transmitted to the server device as operation information. A direct operation transmitting means that updates the feature coordinates and the total amount of affine operations and transmits the total amount of affine operations as operation information to the server device, an indirect operation receiving means that receives the operation information received from the server device, and an indirect operation receiving means. When the operation information received by is received, if the operation information is related to the feature coordinate operation, it is based on the total amount of affine operations of the object recorded in the recording unit and the edited initial feature coordinates which are the received operation information. , The feature coordinates after the operation are calculated and the operation result is displayed on the display unit. If the operation information is related to the affine operation, the current feature coordinates of the object and the total amount of the affine operation recorded in the recording unit. Based on the above, the initial feature coordinates of the object are calculated, the feature coordinates after the operation are calculated based on the initial feature coordinates and the total amount of Affin operation which is the received operation information, and the operation result is displayed. If the indirect operation display means displayed on the unit and the received operation information are feature coordinate operations, the feature coordinates recorded in the recording unit are updated with the feature coordinates after the operation, and the received operation information is an affine operation. If there is, it is provided with an indirect operation recording means for updating the feature coordinates and the total amount of object operations recorded in the recording unit with the feature coordinates after the operation and the total amount of the received object operations.

Therefore, it is possible to achieve both the unique editing of the object and the affine operation.

(12) The joint editing system according to the present invention is characterized in that the direct operation transmission means transmits operation information to another terminal device via a server device.

Therefore, the operation of each terminal device can be unified by the server device.

(13) In the joint editing system according to the present invention, the operation information recording means of the server device records the operation information received from each terminal device in the recording unit so that the order of reception becomes clear, and the server device. The operation information distribution means distributes the operation information recorded in the recording unit to each terminal device in the order of reception, receives the operation information by the indirect operation receiving means of the terminal device, and processes it by the indirect operation display means. The operation information to be performed is characterized in that it includes not only the operation information of the other terminal device but also the operation information of the own terminal device received by the direct operation reception means.

Therefore, it is possible to easily unify the operations in each terminal device.

(14) (15 (16) The joint editing system according to the present invention is a content joint editing system including a server device and two or more terminal devices capable of communicating with the server device.
The server device includes an operation information recording means for recording operation information received from each terminal device in a recording unit, and an operation information distribution means for distributing the operation information recorded in the recording unit to each terminal device.
The terminal device has a recording unit that records the feature coordinates and initial feature coordinates of the line object, a direct operation receiving means that accepts an operation on the line object, and a deletion that divides the line object into two or more received by the direct operation receiving means. Based on the operation, the line object is deleted based on the direct operation display means that deletes a part of the line object and displays the operation result on the display unit, and the partial deletion of the line object received by the direct operation reception means. It is divided into two or more line objects, and the feature coordinates of each line object are recorded in the recording unit, and the initial feature coordinates of the line object before division are recorded in association with these line objects, and these are used as operation information. When the direct operation transmitting means for transmitting to the server device, the indirect operation receiving means for receiving the operation information received from the server device, and the operation information received by the indirect operation receiving means are received, the line recorded in the recording unit. Based on the above deletion, the indirect operation display means that deletes a part of the object and displays the operation result on the display unit and the line object recorded in the recording unit are divided into two or more line objects, and each line object. In addition to recording the feature coordinates of the above in the recording unit, it is provided with an indirect operation recording means for recording the initial feature coordinates of the line object before division in association with these line objects.

Therefore, even if the object is divided and other operations are performed at the same time, both operations can be utilized.

(17) The joint editing system according to the present invention is characterized in that the direct operation transmission means transmits operation information to another terminal device via a server device.

Therefore, the operation of each terminal device can be unified by the server device.

(18) In the joint editing system according to the present invention, the operation information recording means of the server device records the operation information received from each terminal device in the recording unit so that the order of reception becomes clear, and the server device. The operation information distribution means distributes the operation information recorded in the recording unit to each terminal device in the order of reception, receives the operation information by the indirect operation receiving means of the terminal device, and processes it by the indirect operation display means. The operation information to be performed is characterized in that it includes not only the operation information of the other terminal device but also the operation information of the own terminal device received by the direct operation reception means.

Therefore, it is possible to easily unify the operations in each terminal device.

(19) The collaborative editing system according to the present invention is characterized in that the deletion operation information includes the deletion position relative to the total length of the line object regardless of the shape of the line object.

Therefore, even if the shape of the line object is changed, the position can be specified by the relative position.

In the embodiment, steps S503 and S522 correspond to the "direct operation receiving means".

In the embodiment, steps S504 and S523 correspond to the "direct operation display means".

In the embodiment, steps S506 and S525 correspond to the "direct operation transmission means".

In the embodiment, steps S507 and S526 correspond to the "indirect operation receiving means".

In the embodiment, steps S511 and S530 correspond to the "indirect operation display means".

In the embodiment, steps S512 and S531 correspond to the "indirect operation recording means".

The "program" is a concept including not only a program that can be directly executed by the CPU, but also a source format program, a compressed program, an encrypted program, and the like.

It is an overall block diagram of the content co-editing system by one Embodiment of this invention. It is a figure for demonstrating the processing of a content collaborative editing system. It is a system configuration diagram. This is the hardware configuration of the terminal device T1. This is the hardware configuration of the server device S. It is a flowchart of a collaborative editing process. It is a flowchart of a collaborative editing process. It is a list of operation data of the server device S. It is a figure for demonstrating the expression method of the position and size of an object. This is a display example in the terminal devices T1 and T2. FIG. 11A is an example of operation data, and FIG. 11B is an example of object data. It is a list of operation data of the terminal device T1. It is a list of operation data of the terminal device T2. It is a figure which shows another example. It is a figure which shows another example. It is a figure which shows another example. It is a figure which shows another example. It is an overall block diagram of the collaborative editing system by 2nd Embodiment. It is a figure for demonstrating the processing of a content collaborative editing system. It is a flowchart of a collaborative editing process. It is a flowchart of a collaborative editing process. It is a list of operation data of the server device S. It is a list of operation data of the terminal device T1. It is a list of operation data of the terminal device T2. This is a display example in the terminal devices T1 and T2. This is an example of object data. It is a figure which shows another example. It is an overall block diagram of the collaborative editing system by 3rd Embodiment. It is a flowchart of a collaborative editing process. It is a flowchart of a collaborative editing process. This is an example of operation data. It is a figure for demonstrating the operation of the conventional content co-editing system. It is a figure for demonstrating the operation of the conventional content co-editing system. It is an overall block diagram of the collaborative editing system by 4th Embodiment. It is a figure for demonstrating the processing of a content collaborative editing system. It is a flowchart of a collaborative editing process. It is a flowchart of a collaborative editing process. It is a flowchart of a collaborative editing process. It is the operation data of the server device S. It is a figure for demonstrating the affine operation. This is the operation data of the terminal device T1. This is the operation data of the terminal device T2. It is a figure for demonstrating the processing of a content collaborative editing system. This is the operation data of the terminal device T1. This is an example of unique editing. It is a figure for demonstrating the processing of a content collaborative editing system. This is the operation data of the terminal device T1. This is the operation data of the terminal device T2. It is the operation data of the server device S. It is an overall block diagram of the collaborative editing system by 5th Embodiment. It is a figure for demonstrating the processing of a content collaborative editing system. It is a flowchart of a collaborative editing process. It is a flowchart of a collaborative editing process. It is a flowchart of a collaborative editing process. It is the operation data of the server device S. This is the operation data of the terminal device T1. This is the operation data of the terminal device T2.

1. 1. First Embodiment
1.1 System Configuration and Overview Figure 1 shows the overall configuration of the content co-editing system according to one embodiment of the present invention. A plurality of terminal devices T1, T2 ... Tn are connected to the server device S. FIG. 2 is a conceptual diagram for explaining co-editing in a content co-editing system.

Hereinafter, a description will be given with reference to FIGS. 1 and 2. In both the terminal devices T1 and T2, it is assumed that the object is displayed in the upper left as shown in the uppermost part of FIG.

The direct operation receiving means 2 (FIG. 1) of the terminal device T1 accepts a user's operation with a mouse or the like. The direct operation display means 4 displays this operation content on the display unit 6. For example, as shown in FIG. 2, it is assumed that the user of the terminal device T1 operates to move the object from the upper left to the upper right ((1) in FIG. 2). The direct operation transmission means 10 of the terminal device T1 transmits this operation information to the server device S. In this embodiment, as the operation information, the operation result that the object is moved to the upper right is transmitted instead of the operation content that the object is moved to the right. The operation information recording means 22 (FIG. 1) of the server device S receives this and records it in the recording unit 24 ((2) of FIG. 2).

At this time, almost at the same time, the user of the terminal device T2 tries to operate the object with a slight delay. At this time, since the operation of the terminal device T1 has not been sent to the terminal device T2, the object is still displayed as if it is in the upper left. Here, it is assumed that the user of the terminal device T2 operates to move the object from the upper left to the lower left by operating the mouse or the like ((3) in FIG. 2). The direct operation transmission means 10 (not shown) of the terminal device T2 transmits this operation information to the server device S. The operation information recording means 22 (FIG. 1) of the server device S receives this and records it in the recording unit 24 ((4) in FIG. 2).

The operation information distribution means 26 of the server device S reads the operation information recorded in the recording unit 24 in the order of recording and distributes the operation information to the terminal devices T1, T2 ... Tn. First, the movement of the object operated by the terminal device T1 to the upper right is read out and distributed to the terminal devices T1, T2 ... Tn. At this time, the operation information is also distributed to the terminal device T1 that has transmitted the operation information ((5) in FIG. 2).

The indirect operation receiving means 12 of the terminal device T1 receives the operation information from the server device S ((5) in FIG. 2). The indirect operation display means 8 operates the object based on the received operation information and displays it on the display unit 6. In the terminal device T1, since the object is displayed in the upper right, it is held in the same position ((6) in FIG. 2).

Similarly, the indirect operation receiving means 12 (not shown) of the terminal device T2 also receives the operation information from the server device S ((5) in FIG. 2). The indirect operation display means 8 (not shown) operates the object based on the received operation information and displays it on the display unit 6 (not shown). In the terminal device T2, since the object is displayed in the lower left, it is moved to the upper right ((6) in FIG. 2).

Subsequently, the server device S reads out the movement of the object operated by the terminal device T2 to the lower left and distributes it to the terminal devices T1, T2 ... Tn. At this time, the operation information is also distributed to the terminal device T2 that has transmitted the operation information ((7) in FIG. 2).

The indirect operation receiving means 12 of the terminal device T1 receives the operation information from the server device S ((7) in FIG. 2). The indirect operation display means 8 operates the object based on the received operation information and displays it on the display unit 6. In the terminal device T1, since the object is displayed in the upper right, it is moved to the lower left ((8) in FIG. 2).

Similarly, the indirect operation receiving means 12 (not shown) of the terminal device T2 also receives the operation information from the server device S ((7) in FIG. 2). The indirect operation display means 8 (not shown) operates the object based on the received operation information and displays it on the display unit 6 (not shown). In the terminal device T2, since the object is displayed in the upper right, it is moved to the lower left ((8) in FIG. 2).

As described above, even if the operation is performed before the operation information is sent from the other terminal device, the operation of the terminal device that has been operated last is prioritized, and each terminal device T1 , T2 ... The operation results of the objects in Tn match. In addition, since the position of an unoperated object is not transmitted, the operation content is quickly reflected.

FIG. 3 shows an example of equipment configuration of this system. The server device S is connected to the tablet PCs, which are the terminal devices T1 to T3, and the stationary PC, which is the terminal device T4, via the Internet. The terminal devices T1 to T3 are connected to the server device S by a wireless LAN. The terminal device T4 is connected to the server device S by a LAN.

FIG. 4 shows the hardware configuration of the terminal device T1. A memory 32, a touch screen display 34, a non-volatile memory 36, and a communication circuit 38 are connected to the CPU 30. The touch screen display 34 can display and input using a stylus pen or the like. The communication circuit 38 is a circuit for connecting to the Internet.

The operating system 40 and the terminal program 42 are recorded in the non-volatile memory 36. Further, the object data 44 indicating the created / edited object and the operation data 45 indicating the operation on the object are recorded. The terminal program 42 exerts its function in cooperation with the operating system 40. These programs were downloaded and installed from a program distribution server device (not shown) via the Internet. The object data 44 is data indicating an object generated / edited in the own terminal device T1 and other terminal devices T2 to T4, and changes depending on the generation / editing status in each terminal device T1 to T4.

The terminal devices T2 and T3 have the same configuration. Further, the terminal device T4 has the same configuration, except that a display and a keyboard / mouse are provided instead of the touch screen display 34.

FIG. 5 shows the hardware configuration of the server device S. A memory 52, a display 54, a hard disk 56, a DVD-ROM drive 58, and a communication circuit 60 are connected to the CPU 50. The communication circuit 60 is a circuit for connecting to the Internet.

The operating system 62 and the server program 64 are recorded on the hard disk 56. The server program 64 exerts its function in cooperation with the operating system 62. These programs are those recorded on the DVD-ROM 68 installed on the hard disk 56 via the DVD-ROM drive 58. The operation data 45 is received from each terminal device T1 to T4.

1.2 Collaborative editing process Figures 6 and 7 show the flowchart of the collaborative editing process by this system. In FIGS. 6 and 7, the terminal device T1 and the terminal device T2 represent the terminal program 42. The server device S represents the server program 64. Although only the two terminal devices T1 and T2 are shown in FIGS. 6 and 7, the same processing is performed for the other terminal devices T3 and T4.

In the following, a case where joint editing has already been performed by the terminal devices T3 and T4 and then the terminal devices T1 and T2 participate in the joint editing will be described as an example.

The user who operates the terminal device T1 operates the touch screen display 34 with a stylus pen (not shown) to access the server device S. In response to this operation, the CPU 30 of the terminal device T1 (hereinafter, may be abbreviated as the terminal device T1) transmits the user ID and password entered by the user to the server device S (step S1).

In response to this, the CPU 50 of the server device S (hereinafter, may be abbreviated as the server device S) determines whether or not the combination of the user ID and the password matches the one recorded in the hard disk 56 in advance ( Step S101). If they match, it is determined that the login is from a legitimate user, and the operation data list of the objects already generated / edited by the other terminal devices T3 and T4 is transmitted to the terminal device T1 (step S102). ..

FIG. 8A shows an example of operation data. Here, only one operation data is recorded because only the object is generated. The number "0" at the left end indicates the order in which the operation data was recorded. The operation column indicates the type of operation. Here, "generation" is recorded. Further, along with the object ID that identifies the generated object, the attributes of the object, the coordinates of the feature points of the object, the color, the thickness, and the like are recorded. FIG. 9 shows a representation method of the coordinates of the object. The coordinates of the feature points A, B, C, and D of the object are represented by the origin (0,0) at the upper left corner of the display, the X axis in the horizontal direction, and the Y axis in the vertical direction.

The terminal device T1 receives this list of operation data and records it in the non-volatile memory 36 (step S2). FIG. 12A shows a list of operation data recorded in the terminal device T1.

Further, the terminal device T1 generates object data based on this operation data list, and displays the object on the touch screen display 34 (step S2).

FIG. 10A shows an object 70 displayed on the touch screen display 34. Since the attribute of the object is "square", the terminal device T1 displays the object as a quadrangle. At that time, the position and size are determined based on the coordinates of the points A, B, C, and D at the four corners of the quadrangle shown in the operation data. In addition, the color, thickness, etc. of the object are also displayed as specified in the operation data.

The CPU 30 of the terminal device T2 (hereinafter, may be abbreviated as the terminal device T2) also logs in to the server device S in the same manner as described above (step S21). The server device S performs a login process (step S103) and transmits a list of operation data to the terminal device T2 (step S104). FIG. 13A shows a list of operation data recorded in the terminal device T2.

The terminal device T2 that has received the operation data list generates object data and displays the object in the same manner as the terminal device T1 (step S22). FIG. 10B shows an object 70 displayed in the terminal device T2. Since the display is based on the same object data, the object is similarly displayed in the upper left in both the terminal devices T1 and T2.

Next, it is assumed that the user of the terminal device T1 moves the object 70 displayed on the touch screen display 34 to the right by a stylus pen (not shown). The terminal device T1 receives this operation and obtains the operation data X1 (step S3). Based on this operation data X1, the terminal device T1 corrects the object data and moves the display of the object 70 to the right as shown in FIG. 10C (step S4).

This operation data X1 is shown in FIG. The object ID and operation type of the operated object are recorded. Here, since the object has been moved, the operation type is recorded as a move. Following this operation type, the coordinates of the moved object are recorded. The terminal device T1 adds and records the operation data X1 to the operation data list received from the server device S (step S3). Therefore, the list of operation data recorded in the terminal device T1 is as shown in FIG. 12B.

The terminal device T1 then transmits the operation data X1 to the server device S (step S5). The server device S receives the operation data X1, adds it to the operation data list, and records it (step S105). Therefore, the list of operation data in the server device S is as shown in FIG. 8B.

On the other hand, it is assumed that the terminal device T2 also operates on the object 70 almost at the same time as the terminal device T1. At this time, in the terminal device T2, since the above operation data X1 has not arrived yet, the object is displayed as a state as shown in FIG. 10B.

Here, it is assumed that the user of the terminal device T2 operates the object 70 to move to the lower left. The terminal device T2 receives this operation and obtains the operation data X2 (step S23). The terminal device T2 adds and records the operation data X2 to the operation data list received from the server device S (step S23). Therefore, the list of operation data in the terminal device T2 is as shown in FIG. 13B.

Further, as shown in FIG. 10D, the movement of the object 70 is displayed on the touch screen display 34 (step S24). Subsequently, the operation data X2 is transmitted to the server device S (step S25).

The server device S receives the operation data X2 and records it on the hard disk 56 (step S106). Therefore, a list of operation data is recorded in the server device S as shown in FIG. 8C. In this embodiment, the operation data is numbered and recorded in the order in which they are received. The order of reception may be based on the time stamp at the time of reception. As described above, the operation data X1 and X2 are recorded in the server device S.

Subsequently, the server device S distributes the operation data received and recorded from the terminal devices T1 and T2 to all the terminal devices T1, T2, T3, and T4 in the order of the recording time (reception time order) (step). S107). In this example, first, the operation data X1 received from the terminal device T1 is distributed to the terminal devices T1, T2, T3, and T4.

In FIG. 7, only the distribution to the terminal devices T1 and T2 is displayed, but the distribution is similarly performed to the other terminal devices T3 and T4. At this time, the operation data X1 is received from the terminal device T1 as described above, but the server device S also transmits the operation data X1 to the terminal device T1. Further, the server device S sets a transmitted flag (not shown) for the transmitted operation data.

The terminal device T1 that has received the operation data X1 adds it to the operation data list of the non-volatile memory 36 and records it (step S6). However, here, since the latest operation data X1 already recorded in the terminal device T1 and the received operation data X1 are the same, recording is not performed again. Therefore, the list of operation data in the terminal device T1 remains as shown in FIG. 12B.

The terminal device T1 operates the object based on the operation data X1 and displays the operation result (step S8). That is, the object data is modified based on the operation data X1, and the object is displayed based on the modified object data.

The operation data X1 is an operation of moving the object 70 to the upper right. As shown in FIG. 10C, in the terminal device T1, the object 70 has already been moved to the upper right by the user's operation. Therefore, the terminal device T1 maintains the position of the object 70 displayed on the touch screen display 34 as it is in the upper right (FIG. 10E).

If the target object has already been deleted (the operation is for the already deleted object), the operation in step S8 is not executed (step S7). This point will be described later.

The terminal device T2 that has received the operation data X1 adds it to the operation data list of the non-volatile memory 36 and records it (step S26). Therefore, the list of operation data in the terminal device T2 is as shown in FIG. 13C.

The terminal device T2 operates the object based on the operation data X1 and displays the operation result (step S28). That is, the object data is modified based on the operation data X1, and the object is displayed based on the modified object data.

The operation data X1 is an operation of moving the object 70 to the upper right. As shown in FIG. 10D, in the terminal device T2, the object 70 has already been moved to the lower left by the user's operation. Therefore, the terminal device T2 operates so as to move the position of the object 70 displayed on the touch screen display 34 from the lower left to the upper right (FIG. 10F). In this embodiment, the operation result (moving to the upper right regardless of the current position) is reflected instead of reflecting the operation (moving from the current position to the right).

If the target object has already been deleted (the operation is for the already deleted object), the operation in step S28 is not executed (step S27). This point will be described later.

Next, the server device S distributes the operation data X2 received from the terminal device T2 to the terminal devices T1, T2, T3, and T4. In FIG. 7, only the distribution to the terminal devices T1 and T2 is displayed, but the distribution is similarly performed to the other terminal devices T3 and T4. At this time, the operation data X2 is received from the terminal device T2 as described above, but the server device S also transmits the operation data X2 to the terminal device T2.

The terminal device T1 that has received the operation data X2 adds it to the operation data list of the non-volatile memory 36 and records it (step S9). A list of operation data to which the operation data X2 is added is shown in FIG. 12C.

The terminal device T1 operates the object based on the operation data X2 and displays the operation result (step S11). That is, the object data is modified based on the operation data X2, and the object is displayed based on the modified object data. The object data in the terminal device T1 at this time is as shown in FIG. 11B.

The operation data X2 is an operation of moving the object 70 to the lower left. As shown in FIG. 10E, in the terminal device T1, the object 70 is located at the upper right. Therefore, the terminal device T1 moves the position of the object 70 displayed on the touch screen display 34 from the upper right to the lower left (FIG. 10G).

The terminal device T2 that has received the operation data X2 adds it to the operation data list of the non-volatile memory 36 and records it (step S29). A list of operation data to which the operation data X2 is added is shown in FIG. 13D.

The terminal device T2 operates the object based on the operation data X2 and displays the operation result (step S31). That is, the object data is modified based on the operation data X2, and the object is displayed based on the modified object data. The object data in the terminal device T2 at this time is as shown in FIG. 11B.

The operation data X2 is an operation of moving the object 70 to the lower left. As shown in FIG. 10F, in the terminal device T2, the object 70 is displayed in the upper right. Therefore, the terminal device T2 operates so as to move the position of the object 70 displayed on the touch screen display 34 from the upper right to the lower left (FIG. 10H).

As described above, the object data in each terminal device T1, T2, T3, and T4 are unified as shown in FIG. 11B, and the display of the object based on the object data is also unified.

In the above, the case where both of the terminal device T1 and the terminal device T2 perform a conflicting movement operation with respect to the same object has been described. Here, the "conflicting operation" means that one terminal device performs an operation on an object and the other terminal device performs an operation on the same object until the operation is reflected on the other terminal device. , Refers to both operations when an operation that is incompatible with the operation performed by one of the terminal devices is performed.

However, the above processing is performed not only for the movement operation but also for other conflicting operations. For example, if one terminal changes the color of an object and at the same time the other terminal changes the object to another color, or one terminal changes the linetype of the object and at the same time the other terminal changes the linetype of the object. The same processing is performed when the object is changed to another line type, or when one terminal device expands the object and at the same time the other terminal device reduces the object.

Also, between the time one terminal device performs an operation on an object and the time the operation is reflected on the other terminal device, the other terminal device performs an operation on the same object by one terminal device. The same process is performed when an operation compatible with the above is performed. However, since the operations are compatible with each other, not only the last operation but also both operations are effective.

For example, FIG. 14 shows the processing when the expansion operation is performed in the terminal device T1 and the line type is changed in the terminal device T2. It is assumed that the object is displayed in the upper left of both terminal devices T1 and T2.

Here, it is assumed that the object is enlarged in the terminal device T1 (see (1) in FIG. 14). The terminal device T1 transmits the operation data X1 of this expansion operation to the server device S. The server device S records this operation data X1 (see (2)). In this embodiment, the data after the operation is used as the operation data for the items of the object data that change depending on the operation. Therefore, the operation data X1 of the enlargement operation becomes the coordinates of each feature point of the enlarged object.

Suppose that, after a short delay, the terminal device T2 performs a thick line change operation for changing the line type of the object to a thick line (see (3)). The terminal device T2 transmits the operation data X2 of this thick line change operation to the server device S. The server device S records this operation data X2 (see (4)). The line type change operation data X2 has a line type as a thick line.

The server device S distributes the operation data X1 of the enlargement operation recorded earlier to all the terminal devices T1 and T2 (see (5)). As a result, in the terminal device T1, the enlarged object is maintained as it is (see (6)). In the terminal device T2, the object has already been changed to a thick line. Therefore, this thick line object is magnified (see (6)).

Subsequently, the server device S distributes the operation data X2 for changing the thick line to all the terminal devices T1 and T2 (see (7)). As a result, in the terminal device T1, the line type of the enlarged object is changed to a thick line (see (8)). In the terminal device T2, the line type of the object is already thick, so it is maintained as it is (see (8)).

As described above, even when compatible operations are performed in each terminal device, each terminal device T and server device S perform the same processing, but since the operations are compatible, both operations are utilized. Become.

Further, in the plurality of terminal devices, the operations of different objects performed before the operations of one terminal device are reflected in the other terminal devices are also processed according to the flowcharts of FIGS. 6 and 7. In this case, since the operations are for different objects and there is no conflict, both operations are considered to be effective, and the object data and display of all terminal devices are unified.

For example, FIG. 15 shows a process when the rotation operation of the object 70 is performed in the terminal device T1 and the line type of the object 72 is changed in the terminal device T2. It is assumed that the object 70 is displayed in the upper left and the object 72 is displayed in the upper right in both the terminal devices T1 and T2. Here, it is assumed that the rotation operation of the object 70 is performed in the terminal device T1 (see (1) in FIG. 15). The terminal device T1 transmits the operation data X1 of this expansion operation to the server device S. The server device S records this operation data X1 (see (2)).

It is assumed that a thick line change operation for changing the line type of the object 72 to a thick line is performed in the terminal device T2 with a slight delay (see (3)). The terminal device T2 transmits the operation data X2 of this thick line change operation to the server device S. The server device S records this operation data X2 (see (4)).

The server device S distributes the operation data X1 of the rotation operation for the object 70 recorded earlier to all the terminal devices T1 and T2 (see (5)). As a result, in the terminal device T1, the rotated object 70 is maintained as it is (see (6)). In the terminal device T2, the object 70 is rotated (see (6)). In the terminal device T2, the operation of changing the thick line of the object 72 has already been performed, but this operation is not affected by the operation data X1. This is because it is an operation on a different object.

Subsequently, the server device S distributes the operation data X2 for changing the thick line for the object 72 to all the terminal devices T1 and T2 (see (7)). As a result, in the terminal device T1, the object 72 is changed to a thick line (see (8)). Also in this case, the rotation operation of the object 70 that has already been operated is not affected. In the terminal device T2, the object 72 that has already been changed to a thick line is maintained (see (8)).

In this way, the operations of different objects performed before the operation by one terminal device is reflected in the other terminal device do not conflict with each other. Object data and display are unified.

In addition, even if the operation for the same object is performed on different terminal devices, all the operations are valid as long as the operation data by one terminal device is reflected on the other terminal device. Will be done. For example, FIG. 16 shows a process when an enlargement operation is performed in the terminal device T1 and the line type is changed in the terminal device T2 after the enlargement operation is reflected.

In this case, the object data and display of all the terminal devices are unified, assuming that the enlargement operation by the terminal device T1 and the thick line change operation by the terminal device T2 are both effective.

When the conflicting operation is performed in different terminal devices, as described above, the conflicting operation is unified by the last operation. However, in this embodiment, when at least one of the conflicting operations is an object deletion operation, the object deletion operation is used for unification. That is, the conflicting operation after the object deletion operation is not recorded in the object data, or even if it is recorded, it is not executed. In another embodiment, even if the conflicting operation includes a deletion operation, as a general rule, the conflicting operation may be unified by the last operation.

It should be noted that the timing of receiving the distribution from the server device S is different in each terminal device. Therefore, there is a case where the operation data is not received in one terminal device even though the operation data is received in the other terminal device. In this case, if an operation on the object is performed on the terminal device that has not received the operation data, a conflict will occur.

An example of such a case is shown in FIG. The expansion operation performed by the terminal device T1 is delivered from the server device S to each terminal device (see (4)). However, as shown in (5), the terminal devices T1 and T3 have been reached, but the terminal devices T2 have not been reached. At this time, if the reduction operation is performed by the terminal device T2, a conflict will occur.

The operation data of the enlargement operation reaches the terminal device T2 in (8). However, after that, the operation data of the reduction operation is unified into the reduction operation in the terminal devices T1, T2, and T3. That is, the operation in which the conflict occurs (enlargement operation) is finally invalidated, and the reduction operation performed by the terminal device T2 is unified.

In addition, conflict operations may be chained. For example, it is assumed that the terminal device T1 performs an operation to make the line type blue, and the terminal device T2 performs an operation to make the line type red. Further, it is assumed that the terminal device T3 performs an operation (an operation of turning the line type yellow) that does not conflict with the operation of the terminal device T1 but conflicts with the operation of the terminal device T2. That is, it is assumed that the operation is performed in the terminal device T3 after the operation of the terminal device T1 is reflected and before the operation of the terminal device T2 is reflected. In this case, the operation of each terminal device is unified by the operation performed by the terminal device T3 (the operation of turning the line type yellow).

In this embodiment, it is possible to edit an object even in a terminal device that is temporarily unable to communicate with the server device S. After that, when the terminal device becomes able to communicate with the server device S, it receives operation data from another terminal device and transmits its own operation data to another terminal device via the server device S. Can be done. In this case, if there is a conflicting operation, the operation recorded in the server device S at the end is prioritized and the operation in each terminal device is unified in the same manner as described above.

1.3 Others
(1) In the above embodiment, a quadrilateral object has been described as an example. However, the same can be applied to other figures, characters, codes, and the like. In this case, the coordinates recorded in the object data differ depending on the type of the figure or the like in order to specify the shape and position. For example, if it is a circle, it can be specified by the coordinates and radius of the center point.

(2) In the above embodiment, the operation result (state of the object after the operation) is transmitted as operation data. However, as the operation result, the object state before the operation and the operation content (movement amount, etc.) may be transmitted.

(3) In the above embodiment, the server device S sets a flag for the transmitted operation data and transmits the untransmitted operation data to each terminal device. However, in the server device S, the operation data may be recorded with a serial number or the like, and in each terminal device, the serial number of the received operation data may be recorded. In this case, each terminal device clearly indicates the serial number of the operation data received by itself at a predetermined timing, and requests the server device S to transmit the operation data.

(4) The above-described embodiment and modification can be implemented in combination with other embodiments as long as the essence is not contrary to the essence.

2. 2. Second embodiment
2.1 System Configuration and Overview Figure 18 shows the overall configuration of the content co-editing system according to one embodiment of the present invention. A plurality of terminal devices T1, T2 ... Tn are connected to the server device S. FIG. 19 is a conceptual diagram for explaining co-editing in the content co-editing system.

Hereinafter, description will be made with reference to FIGS. 18 and 19. In both the terminal devices T1 and T2, it is assumed that an elliptical object is displayed as shown in the uppermost row of FIG. In this embodiment, each object has a display overlap order (Z-order) as data. Here, it is assumed that the Z-order of the elliptical object is held as "0" (Z = 0). The smaller the Z-order value, the lower the display.

The direct change receiving means 102 (FIG. 18) of the terminal device T1 accepts a user's operation with a mouse or the like. The direct change display means 104 displays this operation content on the display unit 106. For example, as shown in FIG. 19, it is assumed that the user of the terminal device T1 creates a rhombus object (Z = 1) on the ellipse object ((1) in FIG. 19). The direct change transmission means 110 of the terminal device T1 transmits operation data (including Z-order) indicating that the diamond-shaped object (Z = 1) has been generated to the server device S. The Z-order information recording means 122 (FIG. 1) of the server device S receives this and records it in the recording unit 124 ((2) of FIG. 19).

At this time, almost at the same time, it is assumed that the user of the terminal device T2 creates a square object on the ellipse object with a slight delay ((3) in FIG. 19). At this time, since the operation data from the terminal device T1 is not sent to the terminal device T2, a square object is generated on the ellipse object. That is, the Z-order of the square object is "1" (Z = 1). The direct change transmission means 110 (not shown) of the terminal device T2 transmits this operation data (including Z-order) to the server device S. The Z-order information recording means 122 (FIG. 18) of the server device S receives this and records it in the recording unit 124 ((4) of FIG. 19).

The operation information distribution means 126 of the server device S reads the operation data recorded in the recording unit 124 in the order of recording and distributes the operation data to the terminal devices T1, T2 ... Tn. First, the operation data (generation of the diamond-shaped object (Z = 1)) generated by the terminal device T1 is distributed to the terminal devices T1, T2 ... Tn. At this time, the operation data is also distributed to the terminal device T1 that generated the diamond-shaped object ((5) in FIG. 19).

The indirect change receiving means 112 of the terminal device T1 receives the operation data (generation of the diamond-shaped object (Z = 1)) from the server device S ((5) in FIG. 19). The indirect change display means 108 generates and displays a rhombus object (Z = 1) based on the received operation data. In the terminal device T1, since the rhombus object (Z = 1) is displayed on the ellipse object (Z = 0), it is maintained as it is ((6) in FIG. 19). ..

Similarly, the indirect change receiving means 112 (not shown) of the terminal device T2 also receives the operation data (generation of the diamond-shaped object (Z = 1)) from the server device S ((5) in FIG. 19). The indirect change display means 108 (not shown) generates a rhombus object (Z = 1) based on the received operation data and displays it on the display unit 106 (not shown).

In the terminal device T2, the square object (Z = 1) is displayed on the ellipse object (Z = 0). Here, the delivered rhombus object (Z = 1) is generated and displayed. At this time, the indirect change display means 108 (not shown) does not change the Z-order of the delivered rhombus object (Z = 1), and does not change the hierarchical relationship of the existing objects. Add a diamond object.

Therefore, the terminal device T2 displays as an ellipse object (Z = 0), a rhombus object (Z = 1), and a square object (Z = 2). That is, as shown in (6) of FIG. 19, a rhombus object is displayed on the ellipse object, and a square object is displayed on the rhombus object.

Subsequently, the server device S reads the operation data (generation of the square object (Z = 1)) generated by the terminal device T2 and distributes the operation data to the terminal devices T1, T2 ... Tn. At this time, the operation data is also distributed to the terminal device T2 that has transmitted the operation information ((7) in FIG. 19).

The indirect change receiving means 112 of the terminal device T1 receives the operation data (generation of the square object (Z = 1)) from the server device S ((7) in FIG. 19). The indirect change display means 108 generates a square object (Z = 1) based on the received operation data and displays it on the display unit 106.

In the terminal device T1, the rhombus object (Z = 1) is displayed on the ellipse object (Z = 0). Therefore, the terminal device T1 sets the ellipse object (Z = 0) and the square object (Z = 1) according to the above rule, and changes the Z order of the rhombus object to "2". Therefore, as shown in (8) of FIG. 19, a square object is displayed on the ellipse object, and a rhombus object is displayed on the ellipse object.

Similarly, the indirect change receiving means 112 (not shown) of the terminal device T2 also receives the operation information from the server device S ((7) in FIG. 19). The indirect change display means 108 (not shown) displays a square object on the display unit 106 (not shown) based on the received object data (Z = 1).

In the terminal device T2, the rhombus object (Z = 1) is displayed on the ellipse object (Z = 0), and the square object is displayed on the rhombus object (Z = 1). Since the Z-order of the received square object is "1", the terminal device T2 displays the square object (Z = 1) on the ellipse object (Z = 0) according to the above-mentioned rule, and further on the ellipse object (Z = 1). A rhombus object (Z = 2) is displayed in ((8) in FIG. 19).

As described above, even if an operation related to the Z-order is performed before the Z-order change data is sent from another terminal device, the Z-order of the terminal device that has been operated last is displayed. It is prioritized and the Z-orders of the objects in each terminal device T1, T2 ... Tn match.

In the above embodiment, only the changed Z-order is transmitted, but all Z-orders including the unchanged object may be transmitted as operation information.

The system configuration, the hardware configuration of the terminal device T, and the hardware configuration of the server device S are the same as those of the first embodiment (see FIGS. 3 to 5).

2.2 Collaborative editing process Figures 20 and 21 show the flowchart of the collaborative editing process by this system. In FIGS. 20 and 21, the terminal device T1 and the terminal device T2 represent the terminal program 42. The server device S represents the server program 64. Although only the two terminal devices T1 and T2 are shown in FIGS. 20 and 21, the same processing is performed for the other terminal devices T3 and T4.

In the following, a case where joint editing has already been performed by the terminal devices T3 and T4 and then the terminal devices T1 and T2 participate in the joint editing will be described as an example.

The point that the terminal device T1 accesses the server device S and logs in is the same as in the first embodiment (steps S201 and S301). When the server device S determines that the login is from a legitimate user, the server device S transmits to the terminal device T1 a list of operation data that has already been sent and recorded from the other terminal devices T3 and T4 (step). S302).

FIG. 22A shows an example of a list of operation data. Here, only one operation data is recorded because only the object is generated. Along with the object ID that identifies the generated object, the Z-order, the attributes of the object, the coordinates of the feature points of the object, the color, the thickness, and the like are recorded.

The terminal device T1 receives this list of operation data and records it in the non-volatile memory 36 (step S202). FIG. 23A shows a list of operation data recorded in the terminal device T1.

Further, the terminal device T1 generates object data based on this operation data list, and displays the object on the touch screen display 34 (step S202).

FIG. 25A shows an object 70 displayed on the touch screen display 34. Since the attribute of the object is "ellipse", the terminal device T1 displays the object as an ellipse. The items F1, F2, F3, F4 ... Shown in the operation data represent the coordinates and dimensions of the feature points of the object, and are defined in advance according to the attributes. In the case of an "ellipse", F1 is defined as the center coordinate, F2 is defined as the minor axis, and F3 is defined as the major axis. The terminal device T1 determines its position and size based on the data of F1, F2, F3 ... In addition, the color, thickness, etc. of the object are also displayed as specified in the operation data.

The CPU 30 of the terminal device T2 also logs in to the server device S in the same manner as described above (step S211). The server device S performs a login process (step S303) and transmits a list of operation data to the terminal device T2 (step S304). FIG. 24A shows a list of operation data recorded in the terminal device T2.

The terminal device T2 that has received the operation data list generates object data and displays the object in the same manner as the terminal device T1 (step S212). FIG. 25B shows an ellipse object 70 displayed in the terminal device T2. Since the display is based on the same object data, the ellipse object 70 is similarly displayed in both the terminal devices T1 and T2.

Next, it is assumed that the user of the terminal device T1 draws the diamond-shaped object 72 on the elliptical object 70 displayed on the touch screen display 34 with a stylus pen (not shown). The terminal device T1 receives this operation and obtains the operation data X11 (diamond object generation) (step S203). The terminal device T1 generates a rhombus object based on the operation data X11 and displays it on the ellipse object 70 as shown in FIG. 25C (step S204).

Further, the operation data X11 (generated by the diamond-shaped object (Z = 1)) is added to and recorded in the operation data list received from the server device S (step S204). Therefore, the list of operation data recorded in the terminal device T1 is as shown in FIG. 23B. The objects generated in each terminal device are given a Z-order so as to be displayed in the foreground. Therefore, the Z-order of the diamond-shaped object 70 is "1".

The terminal device T1 then transmits the operation data X11 to the server device S (step S205). The server device S receives the operation data X11, adds it to the operation data list, and records it (step S305). Therefore, the list of operation data in the server device S is as shown in FIG. 22B.

On the other hand, it is assumed that the terminal device T2 also draws on the ellipse object 70 almost at the same time as the terminal device T1. However, in the terminal device T2, it is assumed that the square object 74 is drawn. At this time, in the terminal device T2, since the above operation data X11 has not arrived yet, the object is displayed as a state as shown in FIG. 25B.

Here, when the square object 74 is drawn by the user of the terminal device T2, the terminal device T2 accepts this operation and obtains the operation data X12 (step S213). The terminal device T2 generates a square object 74 based on the operation data X12 and displays it on the ellipse object 70 as shown in FIG. 25D (step S214). Further, the operation data X12 is added to and recorded in the operation data list received from the server device S (step S214). Therefore, the list of operation data recorded in the terminal device T2 is as shown in FIG. 24B.

The terminal device T2 then transmits the operation data X12 to the server device S (step S215). The server device S receives the operation data X12, adds it to the operation data list, and records it (step S306). Therefore, the list of operation data in the server device S is as shown in FIG. 22C.

Subsequently, the server device S distributes the operation data received and recorded from the terminal devices T1 and T2 to all the terminal devices T1, T2, T3, and T4 in the order of the recording time (reception time order) (step). S307). In this example, first, the operation data X11 (generation of the diamond-shaped object (Z = 1)) received from the terminal device T1 is distributed to the terminal devices T1, T2, T3, and T4.

In FIG. 21, only the distribution to the terminal devices T1 and T2 is displayed, but the distribution is similarly performed to the other terminal devices T3 and T4. At this time, the operation data X11 is received from the terminal device T1 as described above, but the server device S also transmits the operation data X11 to the terminal device T1. Further, the server device S sets a transmitted flag (not shown) for the transmitted operation data.

The terminal device T1 that has received the operation data X11 adds it to the operation data list of the non-volatile memory 36 and records it (step S206). However, here, since the latest operation data X11 already recorded in the terminal device T1 and the received operation data X11 are the same, recording is not performed again. Therefore, the list of operation data in the terminal device T1 remains as shown in FIG. 23B.

The terminal device T1 generates a rhombus object 72 based on the operation data X11, and displays the rhombus object so that the Z order “1” is maintained (step S207). However, here, since the diamond-shaped object 72 has already been generated and displayed on the ellipse object 70, the terminal device T1 maintains the current display (see FIG. 25E).

If the target object has already been deleted (the operation is for the already deleted object), the operation in step S207 is not executed. This point is the same as that of the first embodiment.

The terminal device T2 that has received the operation data X11 adds it to the operation data list of the non-volatile memory 36 and records it (step S216). Therefore, the list of operation data in the terminal device T2 is as shown in FIG. 24C.

The terminal device T2 generates a rhombus object 72 based on the operation data X11, and displays the rhombus object so that the Z order “1” is maintained (step S217). Here, the ellipse object 70 is already displayed in Z-order "0", and the square object is displayed in Z-order "1". Therefore, the terminal device T2 maintains the Z-order of the generated rhombus object 72 at "1" and changes the Z-order of the square object 74 to "2" for display (see FIG. 25F).

If the target object has already been deleted (the operation is for the already deleted object), the operation in step S217 is not executed. This point is the same as that of the first embodiment.

Next, the server device S distributes the operation data X12 (generation of the square object 74) received from the terminal device T2 to the terminal devices T1, T2, T3, and T4. In FIG. 21, only the distribution to the terminal devices T1 and T2 is displayed, but the distribution is similarly performed to the other terminal devices T3 and T4. At this time, the operation data X12 is received from the terminal device T2 as described above, but the server device S also transmits the operation data X12 to the terminal device T2.

The terminal device T1 that has received the operation data X12 adds it to the operation data list of the non-volatile memory 36 and records it (step S208). A list of operation data to which the operation data X12 is added is shown in FIG. 23C.

The terminal device T1 generates and displays a square object 74 (Z = 1) based on the operation data X12 (step S209). In the terminal device T1, a rhombus object (Z = 1) is displayed on the ellipse object (Z = 0). Therefore, the terminal device T1 changes the Z-order of the square object 74 specified in the operation data X12 to "1" and the Z-order of the diamond-shaped object 72 to "2". Therefore, the square object 74 is displayed on the ellipse object 70, and the rhombus object 72 is displayed on it (see FIG. 25G).

The object data in the terminal device T1 at this time is shown in FIG. The Z-order of the ellipse object is "0", the Z-order of the rhombus object is "2", and the Z-order of the square object is "1".

The terminal device T2 that has received the operation data X12 adds it to the operation data list of the non-volatile memory 36 and records it (step S218). A list of operation data to which the operation data X12 is added is shown in FIG. 24D.

The terminal device T2 generates and displays a square object 74 (Z = 1) based on the operation data X12 (step S218). In the terminal device T2, since the square object has already been generated, it is not generated. However, the terminal device T2 changes the Z order. Now, in the terminal device T2, the rhombus object 72 (Z = 1) is displayed on the ellipse object 70 (Z = 0), and the square object 74 (Z = 2) is displayed on the rhombus object 72 (Z = 1). Therefore, the terminal device T2 changes the Z-order of the square object 74 specified in the operation data X12 to "1" and the Z-order of the diamond-shaped object 72 to "2". Therefore, the square object 74 is displayed on the ellipse object 70, and the rhombus object 72 is displayed on it (see FIG. 25H).

The object data in the terminal device T2 at this time is shown in FIG. The Z-order of the ellipse object is "0", the Z-order of the rhombus object is "1", and the Z-order of the square object is "2".

As described above, the object data including the Z-order in each terminal device T1, T2, T3, and T4 is unified, and the display order of the objects based on the object data is also unified.

In the above, only the Z-order of the generated object is included in the operation data transmitted from each terminal device and distributed from the server device to each terminal device. However, the Z-order of all other objects existing at the time of object creation may be included and transmitted as operation data.

In the above, the case where both of the terminal device T1 and the terminal device T2 generate objects in duplicate (when the objects are operated at almost the same time) has been described. However, the same processing is performed not only for the generation of a new object but also for the general operation of changing the Z-order such as changing the Z-order of an existing object.

For example, FIG. 27 shows a process when the Z-order is changed in the terminal device T1 and the Z-order is changed in the terminal device T2 as well. In the example of FIG. 27, the Z-order of all objects is transmitted as operation data. In both terminal devices T1 and T2, it is assumed that the objects are displayed in the order of an ellipse (Z = 0), a square (Z = 1), and a rhombus (Z = 2) from the bottom (see the top row of FIG. 27). Here, it is assumed that the terminal device T1 is changed so that the rhombus is at the bottom, and the rhombus (Z = 0), the ellipse (Z = 1), and the square (Z = 2) are in this order from the bottom (FIG. 27). See (1)).

The terminal device T1 transmits the operation data X11 of this Z-order change to the server device S. When changing the Z-order, not only the Z-order of the changed object but also the Z-order of all the objects recorded in the terminal device T1 is transmitted as the operation data X11. The server device S records this operation data X11 (see (2)).

Suppose that after a short delay, the terminal device T2 is changed so that the ellipse is at the top, and the order is square (Z = 0), rhombus (Z = 1), and ellipse (Z = 2) from the bottom (FIG. 27). (See (3)).

The terminal device T2 transmits the operation data X12 of this Z-order change to the server device S. The server device S records this operation data X12 (see (4)).

The server device S distributes the previously recorded operation data X11 by the terminal device T1 to all the terminal devices T1 and T2 (see (5)). As a result, in the terminal device T1, the display order of the objects is maintained as it is (see (6)). In the terminal device T2, the display is changed in the order of a rhombus (Z = 0), an ellipse (Z = 1), and a square (Z = 2) from the bottom as specified by the operation data X11 (see (6)).

Subsequently, the server device S distributes the operation data X12 by the terminal device T2 to all the terminal devices T1 and T2 (see (7)). As a result, in the terminal device T1, the display is changed in the order of the square (Z = 0), the rhombus (Z = 1), and the ellipse (Z = 2) from the bottom as specified by the operation data X12 (see (8)). ). Similarly, in the terminal device T2, the display is changed in the order of a square (Z = 0), a rhombus (Z = 1), and an ellipse (Z = 2) from the bottom as specified by the operation data X12 (see (8)). ).

As described above, in this embodiment, when two (may be three or more) conflicting Z order change operations are performed on different terminal devices, the Z order change finally recorded in the server device S is performed. The operation is prioritized (other operations are invalid), and this Z order is unified.

Even if the Z-order change operation for the same object is performed on different terminal devices, all operations are performed after the Z-order change operation data by one terminal device is reflected on the other terminal device. The operation is considered valid.

It should be noted that the timing of receiving the distribution from the server device S is different in each terminal device. Therefore, there is a case where the operation data is not received in one terminal device even though the operation data is received in the other terminal device. In this case, if an operation on the object is performed on the terminal device that has not received the operation data, a conflict will occur. In this case as well, the last operation has priority.

2.3 Others The above embodiments and modifications can be implemented in combination with other embodiments as long as they do not contradict the essence.

3. 3. Third embodiment
3.1 System Configuration and Overview Figure 28 shows the overall configuration of the content co-editing system according to the third embodiment. A plurality of terminal devices T1, T2 ... Tn are connected to the server device S.

When the terminal identification code transmitting means 222 of the server device S receives the first access from the terminal devices T1, T2 ... Tn, the terminal identification code for identifying each terminal device is returned. The terminal identification code receiving means 206 of the terminal device T1 receives the terminal identification code and records it in the recording unit 208. In this embodiment, numerical data is used as the terminal identification code.

The object generation receiving means 202 accepts an object generation operation. The object recording means 204 generates a terminal object identification code for the generated object, and generates an object identification code by combining with the terminal identification code. In this embodiment, numerical data is used as the terminal object identification code. Therefore, the object identification code is composed of two numerical data. Further, the created object is recorded in the recording unit 208 with this object identification code. For example, if the terminal identification code is "3" and the terminal object identification code is "1", the object identification code is generated as "3,1". Since the numerical data are separated by commas and combined, even if the number of digits increases in the process of assigning serial numbers of object identification codes, it is possible to deal with them. For example, you can generate an object identification code such as "3,1236".

The operation information transmitting means 210 transmits the operation information for the object to the server device S together with the object identification code. The operation information recording means 224 of the server device S records the operation information including the received object identification code in the recording unit 226. Further, the server device S distributes the operation information to the terminal devices T2 ... Tn.

The operation means 212 of each terminal device T2 ... Tn that has received the distribution of the operation information performs an operation on the object to which the corresponding object identification code is attached.

In the above, the server device S does not distribute the operation information to the terminal device that has transmitted the operation information, but the server device S also distributes the operation information to the terminal device that has transmitted the operation information. You may do it.

In this way, it is possible to prevent the object identification codes generated by each terminal device from overlapping.

The system configuration, the hardware configuration of the terminal device T, and the hardware configuration of the server device S are the same as those of the first embodiment (see FIGS. 3 to 5).

3.2 Collaborative editing process FIGS. 29 and 30 show a flowchart of the collaborative editing process by this system. In FIGS. 29 and 30, the terminal device T1 and the terminal device T2 represent the terminal program 42. The server device S represents the server program 64. Although only the two terminal devices T1 and T2 are shown in FIGS. 29 and 30, the same processing is performed for the other terminal devices T3 and T4.

The point that the terminal device T1 accesses the server device S and logs in is the same as in the first embodiment (steps S401 and S501). When the server device S determines that the login is from a legitimate user, the server device S generates and transmits a terminal ID for the terminal device T1 (step S502).

In this embodiment, the server device S generates and assigns a three-digit serial number in the order of access to each terminal device. Here, it is assumed that "1" is assigned as the terminal ID to the terminal device T1. Upon receiving the terminal ID, the terminal device T1 records this in the non-volatile memory 36 (step S402).

Subsequently, it is assumed that the terminal device T2 accesses the server device S and logs in (steps S411 and S503). The server device S generates and transmits a terminal ID for the terminal device T2 (step S504). Here, it is assumed that "2" is assigned as the terminal ID to the terminal device T2. The terminal device T2 records this.

Although not shown in the flowchart, "3" and "4" are similarly assigned as terminal IDs to the terminal devices T3 and T4.

Here, it is assumed that the object is generated in the terminal device T1. The terminal device T1 accepts this (step S403). The terminal device T1 generates and records the operation data for object generation based on the received operation (step S404). For example, if a rhombus object is generated, the operation data as shown in FIG. 31 is generated and recorded.

The terminal device T1 generates the object ID in the operation data as follows. First, a serial number is generated as a terminal object ID for the object generated in the terminal device T1. Here, "1" is generated because it is the first created object. Next, the terminal device T1 combines the terminal ID and the terminal object ID into an object ID. In this embodiment, the terminal object ID is connected to the terminal ID with "," sandwiched between them to form an object ID. Therefore, "1,1" is obtained as the object ID.

In this embodiment, a unique terminal object ID is generated for each terminal device, and this is combined with a unique terminal ID for each terminal device to obtain an object ID. Therefore, a unique object ID can be generated on the terminal device side without making an inquiry to the server device S each time the object is generated.

Next, the terminal device T1 transmits the operation data including this object ID to the server device S (step S405). The server device S records the received operation data in the recording unit (step S505).

Further, the server device S distributes this operation data to other terminal devices T2 ... T4 (step S507). Each terminal device T2 ... T4 that has received this operation data generates and displays an object according to the operation data (steps S416 and S417). In addition, the object is managed by the object ID.

After that, when any of the terminal devices T1 ... Tn performs some operation on this object, the operation data with the object ID is generated and distributed to the other terminal device via the server device S. Will be done.

Since the object ID is configured by a combination of numerical values in this way, it is possible to quickly perform processing such as searching for the object ID and comparing the object IDs.

3.3 Others
(1) In the above embodiment, the case where this object data generation method is applied to the differential update method has been described, but the whole update method can also be applied.

(2) In the above embodiment, the object identification code is configured by the combination of the terminal object identification code represented by a numerical value and the terminal identification code represented by a numerical value. However, the object identification code may be configured by the combination of the terminal object identification code represented by the character string and the terminal identification code represented by the character string. In this case, in order to make the object identification code shorter, it is preferable that the terminal identification code is shorter than the unique hardware identification code assigned to the terminal device.

(3) The above-described embodiment and modification can be implemented in combination with other embodiments as long as the essence is not contrary to the essence.

4. Fourth Embodiment
4.1 System Configuration and Overview Figure 34 shows the overall configuration of the content co-editing system according to the fourth embodiment. A plurality of terminal devices T1, T2 ... Tn are connected to the server device S.

The direct operation receiving means 2 of the terminal device T1 receives an operation on an object. In this embodiment, the configuration for operating an object by so-called affine transformation is shown. Here, the affine transformation refers to an operation by linear transformation (enlargement / reduction, shearing, rotation), translation, or a combination thereof.

In this embodiment, the feature coordinates of each object are recorded in the recording unit 16. Furthermore, the contents of all affine transformations (total amount of affine operations) from the feature coordinates (initial feature coordinates) when the object is created are also recorded.

The direct operation display means 4 operates the object based on the affine transformation received for the object and displays the operation result on the display unit 6. Based on the affine transformation, the direct operation transmitting means 10 updates the feature coordinates and the total amount of affine operations recorded in the recording unit 16 after the operation of the object. Further, the total amount of affine operations is transmitted to the server device S as operation information.

The operation information recording means 22 of the server device S receives this and records it in the recording unit 24. Since a plurality of terminal devices T1 to Tn are connected, the server device S records operation information (total affine operation amount) in the recording unit 24 in the order of reception.

The operation information distribution means 26 distributes the operation information (total affine operation amount) recorded in the recording unit 24 to the terminal devices T1 to Tn in the order of reception. The operations of the terminal devices T1 to Tn that have received this operation information (total amount of affine operations) are as follows.

The indirect operation receiving means 12 of the terminal device T1 receives the operation information (total amount of affine operations) from the server device S. When the indirect operation display means 8 receives the operation information (total affine operation amount), the initial feature coordinates of the object are based on the current feature coordinates of the object and the current total affine operation amount recorded in the recording unit 16. Is calculated. Initial feature coordinates can be obtained by reversing all previous affine operations for the current feature coordinates. Further, the feature coordinates after the operation are calculated based on the calculated initial feature coordinates and the total amount of affine operations received, and the object after the operation is displayed on the display unit 6.

The indirect operation recording means 14 updates the feature coordinates and the affine operation total amount recorded in the recording unit 16 by the calculated feature coordinates after the operation and the received operation information (affine operation total amount).

The system configuration, the hardware configuration of the terminal device T, and the hardware configuration of the server device S are the same as those of the first embodiment (see FIGS. 3 to 5).

4.2 Collaborative editing process Figures 36 to 38 show the flowchart of the collaborative editing process by this system. In FIGS. 36 to 38, the terminal device T1 and the terminal device T2 represent the terminal program 42. The server device S represents the server program 64. Although only the two terminal devices T1 and T2 are shown in FIGS. 36 to 38, the same processing is performed for the other terminal devices T3 and T4.

In the following, a case where joint editing has already been performed by the terminal devices T3 and T4 and then the terminal devices T1 and T2 participate in the joint editing will be described as an example.

The user who operates the terminal device T1 operates the touch screen display 34 with a stylus pen (not shown) to access the server device S. In response to this operation, the CPU 30 of the terminal device T1 (hereinafter, may be abbreviated as the terminal device T1) transmits the user ID and password entered by the user to the server device S (step S1).

In response to this, the CPU 50 of the server device S (hereinafter, may be abbreviated as the server device S) determines whether or not the combination of the user ID and the password matches the one recorded in the hard disk 56 in advance ( Step S101). If they match, it is determined that the login is from a legitimate user, and the operation data list of the objects already generated / edited by the other terminal devices T3 and T4 is transmitted to the terminal device T1 (step S102). ..

FIG. 39A shows an example of operation data. The operation column indicates the type of operation. Here, "generation" is recorded. Further, along with the object ID that identifies the generated object, the attributes of the object, the coordinates (feature coordinates) of the feature points of the object, the color, the thickness, and the like are recorded. The feature coordinates of the newly generated object are called the initial feature coordinates in the sense that they are the feature coordinates before the affine operation (transformation) is applied.

The total affine operation amount M0 is the total amount of affine operations from the initial feature coordinates. In the affine operation, the converted feature coordinates can be calculated by multiplying the feature coordinates of the object by the matrix of the affine operation.

FIG. 40 shows an example of an affine operation and a corresponding matrix. FIG. 40A is a matrix in which Tx is “moved” in the X-axis direction and TY is “moved” in the Y-axis direction. By multiplying the feature coordinates of the object (a set of feature points represented in the form of (Px, Py, 1)) by this matrix, the feature coordinates after movement can be obtained.

FIG. 40B is a matrix for scaling a times in the X-axis direction and b times in the Y-axis direction. FIG. 40C is a matrix in which the object is rotated by an angle θ with respect to the origin. In addition, although not shown, there is also an affine transformation called shearing.

These affine transformations are linear transformations, and even if a plurality of affine transformations are performed, they can be multiplied and expressed in one matrix. In this embodiment, the matrix combined into one matrix is defined as the total amount of affine operations.

In the example of FIG. 39A, since the object is only created and no operation is performed on this object, the total affine operation amount M0 is a matrix indicating that there is no affine transformation as shown in FIG. 39A.

The terminal device T1 records the received operation data of FIG. 39A in the non-volatile memory 36, and displays an object on the touch screen display 34 (step S2). The displayed object is shown at the top of FIG. 35. FIG. 41A shows the operation data recorded in the terminal device T1.

The terminal device T2 also logs in in the same manner as the terminal device T1 (step S21), receives operation data from the server, and displays and records it (step S22). The displayed object is shown at the top of FIG. 35. FIG. 42A shows the operation data recorded in the terminal device T2.

A process when a conflicting operation is performed by the terminal device T1 and the terminal device T2 in such a state will be described. Also in this embodiment, one of the two terminal devices has an operation on the same object between the time when one terminal device performs an operation on the object and the time when the operation is reflected on the other terminal device. An operation that is incompatible with the operation performed by the terminal device is regarded as a conflicting operation. However, in this embodiment, in the above case, when both terminal devices perform an affine operation, even if these operations are compatible, they are treated as conflicting operations.

It is assumed that the user of the terminal device T1 enlarges the object 70 displayed on the touch screen display 34 with a stylus pen (not shown). The terminal device T1 accepts this operation (step S503). Based on this operation, the terminal device T1 calculates and records the feature coordinates, and enlarges and displays the object 70 as shown in FIG. 35 (1) (step S504).

Further, based on this operation, the feature coordinates of the operation data received from the server device S are updated to the enlarged feature coordinates (step S504). That is, as shown in FIG. 41B, the feature coordinates are rewritten to the enlarged coordinates.

Next, the terminal device T1 adds the affine operation matrix of the received operation to the original affine operation total amount (FIG. 41A), and updates the affine operation total amount as shown in FIG. 41B. Therefore, even if the operation is continued, the total amount of affine operations includes all affine operations from the initial feature coordinates.

Subsequently, the updated total amount of affine operations is transmitted to the server device S as operation data X1 (step S506). The reason why the feature coordinates after the operation are not transmitted is that if the total amount of the affine operation is transmitted, the feature coordinates after the operation can be calculated by the processing as described later in another terminal device.

The server device S receives the total amount of affine operations (operation data X1), adds it to the operation data list, and records it (step S105). Therefore, the list of operation data in the server device S is shown in FIG. 39B.

It is assumed that the terminal device T2 performs a move operation before the expansion operation by the terminal device T1 is reflected in the terminal device T2 (see FIG. 35 (3)). That is, it is assumed that the object is moved to the lower left as shown in FIG. 35 (3). As a result, in the terminal device T2, as shown in FIG. 42B, the feature coordinates are rewritten to the coordinates after the movement (steps S522 and S523). Further, the affine operation matrix of the received operation is added to the original affine operation total amount (FIG. 42A), and the affine operation total amount is updated as shown in FIG. 42B.

Subsequently, the updated total amount of affine operations is transmitted to the server device S as operation data X2 (step S525).

The server device S receives the total amount of affine operations (operation data X2), adds it to the operation data list, and records it (step S106). Therefore, the list of operation data in the server device S is shown in FIG. 39C.

Next, the server device S transmits the first recorded operation data X1 (enlargement operation) to each terminal device (step S107). That is, the data of the total affine operation amount M1 in the second row of FIG. 39C is transmitted together with the object ID.

The terminal device T1 receives the operation data X1 (total affine operation amount M1) (step S507), and acquires the current feature coordinates of the object and the total affine operation amount (step S508). The current feature coordinates of the terminal device T1 and the total amount of affine operations are as shown in FIG. 41B.

The terminal device T1 calculates the initial feature coordinates of the object based on the current feature coordinates and the total affine operation amount M1 (step S509). The total affine operation is a matrix containing all the affine operations since the object was created. Therefore, the initial feature coordinates can be calculated by multiplying the current feature coordinates by the inverse matrix of the total affine operation. Here, (5,5) (10,5) (5,10) (10,10) can be obtained.

Next, the terminal device T1 multiplies this by the operation data X1 (affine operation total amount M1) to calculate and record the feature coordinates after the operation by the operation data X1 (step S510). Here, (5,5) (15,5) (5,15) (15,15) can be obtained. The display based on this is as shown in FIG. 35 (6). Further, the total amount of affine operations is updated by the received operation data X1 (step S512).

Therefore, the operation data of the terminal device T1 is the same as that of FIG. 41B after all.

The same processing is performed in the terminal device T2 that has received the operation data X1. Therefore, the operation data of the terminal device T2 is as shown in FIG. 42C. The display is as shown in FIG. 35 (6).

Subsequently, the server device S transmits the next recorded operation data X2 (affine operation total amount M2) together with the object ID to each terminal device. That is, the data of the total affine operation amount M2 in the third row of FIG. 39C is transmitted.

In the terminal device T1 that has received the operation data X2, the initial feature coordinates are calculated (steps S514 and S515), and this is multiplied by the operation data X2 (affine operation total amount M2) to calculate the feature coordinates after the operation (step). S516). Further, the display is performed as shown in FIG. 35 (8) (step S517). Subsequently, the feature coordinates and the total amount of affine operations are updated (step S518). Therefore, the operation data of the terminal device T1 is as shown in FIG. 41C.

The same processing is performed in the terminal device T2 that has received the operation data X2. Therefore, the operation data of the terminal device T2 is as shown in FIG. 42D. The display is as shown in FIG. 35 (8).

As described above, even if conflicting operations are performed in two or more terminal devices, the operation results in each terminal device can be unified.

In the above description, the case where the movement operation is performed in the terminal device T2 before the expansion operation in the terminal device T1 is reflected in the terminal device T2 has been described. In this case, as described above, the operation is unified by the movement operation of the terminal device T2 later recorded in the server device S.

However, if the expansion operation in the terminal device T1 is reflected in the terminal device T2 and then the move operation is performed in the terminal device T2, as a matter of course, both operations are reflected as shown in FIG. 43. Be unified.

The operation data of the terminal device T1 at this time is shown in FIG. FIG. 44A is the initial feature coordinates. FIG. 44B shows the feature coordinates and the total amount of affine operations when the enlargement operation is performed. Further, FIG. 44C shows the feature coordinates and the total amount of affine operations when the movement operation is performed. As shown in FIG. 44C, the total affine operation amount M3 is a matrix including all the enlargement operations and movement operations performed on the object so far.

As described above, in this embodiment, the current feature coordinates and the total affine operation amount are recorded as operation data, and the total affine operation amount is transmitted to another terminal device. Therefore, it is possible to unify the operations in each terminal device while keeping the capacity of the transmission data small.

In the above, the processing when the operation by the affine transformation is performed has been described. That is, the case where the basic feature coordinates (initial feature coordinates) are not changed and the movement, enlargement, reduction, rotation, etc. are performed has been described. As described above, when there is no change in the basic feature coordinates, the operation result is substantially sent only by sending the total amount of affine operations, and it is possible to unify the operations in each terminal device.

In the following, the processing when the basic feature coordinates are changed by the operation (called unique editing) will be described. FIG. 45 shows an example of the case where the operation is performed on the basic feature coordinates (unique editing). In FIG. 45A, an operation of changing the direction of the balloon of the balloon figure is performed. In FIG. 45B, an operation is performed in which only one point of the rectangle is moved to form a deformed quadrangle.

After the operation shown in FIG. 43 is performed, the movement process is performed in the terminal device T1, and the process when the unique process is performed in the terminal device T2 before the process is reflected in the terminal device T2 is shown in FIG. 46. Shown in.

First, it is assumed that the terminal device T1 performs a process of moving an object to the lower right (see FIG. 46 (9)). As a result, the terminal device T1 transmits the total amount of affine operations to the server device S as described above. Therefore, the operation data is recorded in the server device S as shown in FIG. 49A.

Subsequently, it is assumed that the unique editing of the object is performed by the terminal device T2 (see FIG. 46 (11)). The terminal device T2 updates the feature coordinates of the operation data with the feature coordinates obtained as a result of the editing. Since the affine transformation is not performed, the total amount of affine operations remains M2 and is not changed.

Further, the terminal device T2 calculates the feature coordinates after the unique editing multiplied by the inverse matrix of the total amount of affine operations. That is, the editing result (called the initial conversion editing feature coordinates) when the unique editing this time is performed at the initial feature coordinates is calculated. The terminal device T2 transmits the initial conversion edit feature coordinates calculated in this way to the server device S as operation data. In the case of (12) in FIG. 46, the points A (5,5), B (10,5), C (0,7), and D (10,10) are obtained as the initial conversion editing feature coordinates. And sends it to the server device S. Therefore, as shown in FIG. 49B, the operation data of the unique edit is recorded in the server device S.

The server device S transmits the operation data indicated by the total affine operation amount M3 to each terminal device. In the terminal device T1, the initial feature coordinates are calculated based on the current feature coordinates and the total affine operation amount (see FIG. 47A) in the same manner as described above, and then the new affine operation total amount M3 is updated. Calculate feature coordinates.

The terminal device T2 that has received the operation data (total affine operation amount M3) similarly calculates the initial feature coordinates based on the current feature coordinates and the total affine operation amount (see FIG. 48A). Since the terminal device T2 has been uniquely edited, the calculated initial feature coordinates are not the feature coordinates at the time of object generation, but the initial conversion edit feature coordinates. Here, points A (5,5), B (10,5), C (0,7), and D (10,10) are obtained.

Subsequently, the terminal device T2 multiplies the initially converted edit feature coordinates by the received operation data (affine operation total amount M3) to obtain an edited object. That is, as shown in FIG. 46, the deformed object in the lower left is moved to the lower right. As described above, since the movement operation performed in the terminal device T1 and the unique editing performed in the terminal device T2 are compatible with each other, the results of both are reflected.

Next, the server device S transmits the operation data of the unique editing shown in FIG. 49B to each terminal device. When the terminal device T1 receives the operation data of the unique editing, it uses this as the initial feature coordinates and multiplies it by the current total affine operation amount M3 (see FIG. 47A) to calculate the edited feature coordinates.

As described above, the operation data of the unique edit indicates what would have happened if the unique edit performed was initially performed in the feature coordinates (initial conversion edit feature coordinates), so that the total amount of affine operations M3 By multiplying by, you can get the object after unique editing. Therefore, in the terminal device T1, the display as shown in FIG. 46 (16) is made.

Further, the terminal device T1 updates the feature coordinates of the edited object as shown in FIG. 47B. Since there is no change in the total amount of affine operation M3, it remains as it is. As described above, since the movement operation performed in the terminal device T1 and the unique editing performed in the terminal device T2 are compatible with each other, the results of both are reflected.

Similarly, the terminal device T2 that has received the operation data (initial conversion edit feature coordinates) uses this as the initial feature coordinates, and multiplies this by the current total affine operation amount M3 (see FIG. 48B) to obtain the edited feature coordinates. calculate. Update the feature coordinates of the object according to the feature coordinates after editing (there is no change here, so it remains as it is). Moreover, since there is no change in the total amount of affine operation M3, it remains as it is.

As described above, when the operation by one terminal device is performed by the other terminal device before it is reflected in the other terminal device (simultaneous operation), if both operations are affine operations, Unification is achieved by operating other terminal devices. The same applies when both operations are unique edits. Further, in the case of the above simultaneous operations, if one is an affine operation and the other is a unique edit, both operations are included in the unification.

As described above, in this embodiment, the total affine operation amount or the initial conversion edit feature coordinates are transmitted as the operation result.

4.3 Others
(1) In the above embodiment, even if the operations are simultaneous, if the affine operation and the unique editing are performed, it is possible to unify the operations in each terminal device including both operations.

However, object style changes (line width, line color, opacity, linetype, etc.) can be applied as well. For example, in the case of affine operation and style change, and unique editing and style change, it is possible to unify the operations on each terminal device including both operations even if they are simultaneous operations.

(2) In the above embodiment, the operation data is transmitted to another terminal device via the server device S. However, the operation data may be directly transmitted to another terminal device without going through the server device S.

(3) The above-described embodiment and modification can be implemented in combination with other embodiments as long as the essence is not contrary to the essence.

5. Fifth Embodiment
5.1 System Configuration and Overview Figure 50 shows the overall configuration of the content co-editing system according to the fifth embodiment. A plurality of terminal devices T1, T2 ... Tn are connected to the server device S.

The direct operation receiving means 2 of the terminal device T1 receives an operation on an object. In this embodiment, a configuration is shown for an operation of deleting a part of a handwriting input line (referred to as a stroke) and dividing it into two objects.

The direct operation display means 4 deletes the designated portion of the stroke based on the deletion operation received for the stroke which is an object, and displays the operation result on the display unit 6.

The direct operation transmitting means 10 erases the data of the stroke recorded in the recording unit 16 based on the deletion operation, and generates and records the data of the two strokes divided by the deletion operation. At this time, the data of the two newly generated strokes includes reference information indicating which part of the stroke before erasing (referred to as the base stroke) is deleted and formed. .. Further, the information of the deletion operation for the base stroke is transmitted to the server device S as the operation information.

The operation information recording means 22 of the server device S receives this and records it in the recording unit 24. Since a plurality of terminal devices T1 to Tn are connected, the server device S records operation information (deletion of base stroke) in the recording unit 24 in the order of reception.

The operation information distribution means 26 distributes the operation information (deletion of the base stroke) recorded in the recording unit 24 to the terminal devices T1 to Tn in the order of reception. The operations of the terminal devices T1 to Tn that have received this operation information (deletion of the base stroke) are as follows.

The indirect operation receiving means 12 of the terminal device T2 receives the operation information (deletion of the base stroke) from the server device S. When the indirect operation display means 8 receives the operation information (deletion of the base stroke), the indirect operation display means 8 performs a deletion operation based on the base stroke data recorded in the recording unit 16 and displays it on the display unit 6.

The indirect operation recording means 14 erases the data of the stroke recorded in the recording unit 16 based on the deletion operation, and generates and records the data of the two strokes divided by the deletion operation. At this time, the data of the two newly generated strokes includes reference information indicating which part of the stroke before erasing (referred to as the base stroke) is deleted and formed. ..

The same processing is performed in the other terminal devices T3 to Tn. In the terminal device T1, the above-mentioned deletion process has already been performed, but the operation information is transmitted and the deletion process is performed in the same manner as the other terminal devices. However, since the deletion process has already been performed, the operation result remains as it is.

The system configuration, the hardware configuration of the terminal device T, and the hardware configuration of the server device S are the same as those of the first embodiment (see FIGS. 3 to 5).

5.2 Collaborative editing process Figures 52 to 54 show the flowchart of the collaborative editing process by this system. In FIGS. 52 to 54, the terminal device T1 and the terminal device T2 represent the terminal program 42. The server device S represents the server program 64. Although only the two terminal devices T1 and T2 are shown in FIGS. 52 to 54, the same processing is performed for the other terminal devices T3 and T4.

In the following, a case where joint editing has already been performed by the terminal devices T3 and T4 and then the terminal devices T1 and T2 participate in the joint editing will be described as an example.

The user who operates the terminal device T1 operates the touch screen display 34 with a stylus pen (not shown) to access the server device S. In response to this operation, the CPU 30 of the terminal device T1 (hereinafter, may be abbreviated as the terminal device T1) transmits the user ID and password entered by the user to the server device S (step S1).

In response to this, the CPU 50 of the server device S (hereinafter, may be abbreviated as the server device S) determines whether or not the combination of the user ID and the password matches the one recorded in the hard disk 56 in advance ( Step S101). If they match, it is determined that the login is from a legitimate user, and the operation data list of the objects already generated / edited by the other terminal devices T3 and T4 is transmitted to the terminal device T1 (step S102). ..

FIG. 55A shows an example of operation data. The operation column indicates the type of operation. Here, "generation" is recorded. Further, along with the object ID that identifies the generated object, the attributes of the object, the coordinates (feature coordinates) of the feature points of the object, the color, the thickness, and the like are recorded. In this example, it is assumed that a straight line (called a stroke) handwritten by the user with a stylus pen is recorded as an object.

Further, "3,1" is recorded as the object ID. As described in the third embodiment, this object ID is composed of a combination of the terminal identification code "3" (indicating the terminal device T3) and the terminal object identification code "1".

In the example of FIG. 55A, since the stroke object is only generated and no operation is performed on this object, the total affine operation amount M0 is a matrix indicating that there is no affine transformation as shown in FIG. 55A. Become.

The terminal device T1 records the received operation data of FIG. 55A in the non-volatile memory 36, and displays the stroke object on the touch screen display 34 (step S2). The displayed stroke object is shown at the top of FIG. 51. FIG. 56A shows the operation data recorded in the terminal device T1.

The terminal device T2 also logs in in the same manner as the terminal device T1 (step S21), receives operation data from the server, and displays and records it (step S22). The displayed stroke object is shown at the top of FIG. 51. FIG. 57A shows the operation data recorded in the terminal device T2.

In such a state, it is assumed that the user of the terminal device T1 deletes a part of the stroke object by the eraser command. A case where the user of the terminal device T2 expands the stroke object (affine operation) before the deletion process is reflected in the terminal device T2 will be described. In this embodiment, as shown below, even in the above cases, both the deletion and the enlargement processing are adopted to achieve unification.

It is assumed that the user of the terminal device T1 deletes a part of the stroke object 70 displayed on the touch screen display 34 by a stylus pen (not shown) by an eraser operation. The terminal device T1 accepts this operation (step S603). Based on this operation, the terminal device T1 divides the stroke object 70 into two stroke objects 70a and 70b. That is, the original object 70 (referred to as a base object) is deleted, and new objects 70a and 70b are generated (steps S604 and S605).

FIG. 56B shows the operation data of the terminal device T1. The base object having the object ID of "3,1" is deleted, and two objects 70a and 70b having the object IDs of "1,1" and "1,2" are generated and recorded. These two objects 70a and 70b are created by dividing the base object 70.

The terminal device T1 assigns an object ID having a terminal identification code of the terminal device T1 such as "1,1" and "1,2" to the objects 70a and 70b generated separately. .. This makes it possible to prevent the object IDs of the newly generated objects 70a and 70b from overlapping with the object IDs generated in other terminal devices.

In this embodiment, the information of the base object is included after the operation data of the respective objects 70b and 70c. Further, an item of "corresponding part" is provided to indicate which part the object corresponds to when the total length of the base object is normalized to "1.0".

For example, looking at the object 70a (object ID = "1,1"), the stroke is from "5,5" to "8,5" in XY coordinates. This corresponds to the first half 30% of "5,5" to "15,5" of the base object in terms of length. Therefore, "0.0-0.3" is recorded in the item of the corresponding part (expressed by the ratio when the total length is "1"). Similarly, for the object 70b (object ID = "1,2"), "0.35-1.0" is recorded in the item of the corresponding part.

Subsequently, the terminal device T1 transmits the operation data of the deletion to the server device S (step S606). In this embodiment, the ID of the object targeted for the deletion operation and the deleted part indicating the deleted part as a numerical value normalized with respect to the length are transmitted as operation data. In the above example, the operation data of deleting "0.3-0.35" is transmitted for the object with the object ID = 3,1.

In the above, the straight stroke object has been described, but for the curved stroke object, the deleted part and the corresponding part are calculated by the numerical value normalized by the length along the curve from the end. Can be recorded.

The server device S receives the operation data X1, adds it to the operation data list, and records it (step S105). Therefore, the list of operation data in the server device S is shown in FIG. 55B.

It is assumed that the terminal device T2 performs an expansion operation (affine operation) before the partial deletion operation by the terminal device T1 is reflected in the terminal device T2 (see FIG. 51 (3)). That is, as shown in FIG. 51 (3), it is assumed that the stroke object is enlarged in the X-axis direction. As a result, in the terminal device T2, as shown in FIG. 57B, the feature coordinates are rewritten to the coordinates after the movement (steps S622 and S623). Further, the affine operation matrix of the received operation is added to the original affine operation total amount (FIG. 57A), and the affine operation total amount is updated as shown in FIG. 57B.

Subsequently, the updated total amount of affine operations is transmitted to the server device S as operation data X2 (step S625).

The server device S receives the total amount of affine operations (operation data X2), adds it to the operation data list, and records it (step S106). Therefore, the list of operation data in the server device S is shown in FIG. 55C.

Next, the server device S transmits the operation data X1 (partially deleted) recorded first to each terminal device (step S107). That is, the data of the partial deletion in the second line of FIG. 55C is transmitted.

The terminal device T1 receives the operation data X1 (partially deleted) and performs processing on the operation data (step S607). The details of the processing for the operation data are shown in FIG. 54. The terminal device T1 receives the operation data X1 from the server device S (step S650).

Subsequently, the terminal device T1 determines whether or not there is an object corresponding to the object ID specified in the operation data X1 (second line in FIG. 55C) (step S651). That is, it is determined whether or not there is an object with ID = "3,1". The current operation data of the terminal device T1 is as shown in FIG. 56B. Since the object with ID = "3,1" has already been deleted in the terminal device T1, there is no corresponding object.

The terminal device T1 searches for the ID of "3,1" as the associated base object ID (step S655). Here, the two objects whose base object IDs are recorded as "3,1" are the object IDs "1,1" and "1,2" (see FIG. 56B). Therefore, select these two objects.

Next, the operation data X1 is operated for the first searched object "1,1" (step S657). Since the operation data X1 is an operation on the base object, a partial deletion operation is performed with the base object as a reference. The content of the operation data X1 is to delete 0.3-0.35 with the normalized length. As a result, one of the two objects obtained is exactly the same as the object "1,1", so this is used as it is.

Next, for the next searched object "1,2", this is used as it is in the same manner as above.

The terminal device T1 displays these objects “1,1” and “1,2” (step S658). Since the objects "1,1" (70a) and "1,2" (70b) are already displayed on the terminal device T1, the display as it is is maintained.

The terminal device T2 also receives the operation data X1 and performs a process for the operation data X1 (step S626). The details of the processing for the operation data are shown in FIG. 54. The terminal device T2 receives the operation data X1 (step S650).

Subsequently, the terminal device T2 determines whether or not the object ID “3,1” specified in the operation data X1 exists (step S651). The current operation data of the terminal device T2 is as shown in FIG. 57B. Therefore, since the designated object "3,1" exists, an operation for this is performed (step S652). That is, in the normalized length, the portion of 0.3 to 0.35 is deleted, and the object is separated into two (step S652).

In the terminal device T2, since the enlargement processing has already been performed, the above-mentioned partial deletion processing is performed on the enlarged object. Therefore, the display as shown in FIG. 51 (6) is made (step S653). Further, the operation data of the terminal device T2 is as shown in FIG. 57C.

Here, in the terminal device T2, the object IDs of the objects newly generated by the division are set to "2,1" and "2,2". That is, an ID using the terminal identification code "2" is assigned. This makes it possible to prevent duplication of object IDs in each terminal device.

However, even though they are the same object, "1,1" ("1,2") is added to the terminal device T1 and "2,1" ("2,2") is added to the terminal device T2. .. Therefore, when the terminal device T1 later performs an operation on "1,1", the terminal device T1 normalizes not only the object ID "1,1" but also the base object "3,1". Send "0.0-0.3" to the server device S. Upon receiving this, the terminal device T2 can specify that the operation is for the object "2,1" based on the corresponding part "0.0-0.3" normalized to the base object "3,1".

Subsequently, the server device S transmits the next recorded operation data X2 (affine operation total amount M1) to each terminal device. That is, the data of the total affine operation amount M1 in the third row of FIG. 55C is transmitted.

In the terminal device T1 that has received the operation data X2, the processing for the operation data X2 (enlargement) is executed (step S608). The details of the processing for the operation data are shown in FIG. 54.

The terminal device T1 receives the operation data X2 (total affine operation amount M1) (step S650). The object ID instructed in the operation data X2 (see the third line in FIG. 55C) is "3,1". The operation data of the current terminal device T1 is as shown in FIG. 56B. Therefore, since the object ID "3,1" cannot be found, "3,1" is extracted from the ID of the base object described as reference information (step S655). As a result, the objects "1,1" and "1,2" to which the base object ID "3,1" is added as reference information are extracted.

Next, the operation data X2 is operated for the first extracted object "1,1" (step S657). Since the operation data X2 is an operation on the base object, the enlargement operation is performed with reference to the base object. That is, the following operations are performed.

First, the initial feature coordinates of the base object are calculated based on the total amount of affine operations of the base object added as reference information and the feature coordinates. In the example of FIG. 56B, since the total affine operation amount M0 indicates “no affine operation”, the recorded feature coordinates are the initial feature coordinates as they are. Subsequently, the operation data X2 (affine operation total amount M1) is multiplied by the initial feature coordinates to obtain the enlarged feature coordinates. Object "1,1" corresponds to 0.0-0.3 of the base object (see the relevant part). Therefore, the part corresponding to 0.0-0.3 is extracted from the enlarged base object, and the enlarged object "1,1" is obtained. By the above processing, the object "1,1" is updated as shown in FIG. 56C.

By the same processing, the objects "1,2" are also updated as shown in FIG. 56C.

The terminal device T1 displays the objects “1,1” (70a) and “1,2” (70b) enlarged as described above (step S658).

The terminal device T2 also receives the operation data X2 and performs processing on the operation data X2 (step S627). The details of the processing for the operation data are shown in FIG. 54. The terminal device T2 receives the operation data X2 (step S650).

Subsequently, the terminal device T2 determines whether or not the object ID “3,1” specified in the operation data X2 exists (step S651). The current operation data of the terminal device T2 is as shown in FIG. 57C. Therefore, since the specified object "3,1" does not exist, the base object is searched for "3,1". Here, "2,1" and "2,2" can be extracted as objects having "3,1" as the base object.

The terminal device T2 operates the object "2,1" by the operation data X2. Since the operation data X2 is an operation on the base object, the operation is performed based on this. However, here, since the total affine operation amount M1 of the base object and the total affine operation amount M1 by the operation data X2 are equal, no special processing is performed. This is because the affine operation (enlargement operation) has already been performed. The same applies to the object "2,2". Therefore, the operation data of the terminal device T2 is as shown in FIG. 57C, and the display is also shown in FIG. 51 (8).

As described above, when an operation by a certain terminal device is performed on the other terminal device before it is reflected on the other terminal device (simultaneous operation), one is a partial deletion operation. If the other is an affine operation, both operations are included in the unification.

In the above, the case of simultaneous operation has been described. Although the explanation is omitted, in the case of non-simultaneous operations (when the operation by one terminal device is reflected in the other terminal device and then the operation is performed in the other terminal device), both are used. It is natural that the operations are unified so as to include the operations of.

5.3 Others
(1) In the above embodiment, even if it is a simultaneous operation, if it is an affine operation and a partial deletion operation, it is possible to unify the operations in each terminal device including both operations.

However, object style changes (line width, line color, opacity, linetype, etc.) can be applied as well. For example, if it is an affine operation and a style change, and a partial deletion operation and a style change, it is possible to unify the operations in each terminal device including both operations even if they are simultaneous operations.

Further, if it is a unique editing operation and a partial deletion operation, even if it is a simultaneous operation, it is possible to unify the operations in each terminal device including both operations.

Further, even if both operations are simultaneous operations, if both operations are partial deletion operations, it is possible to unify the operations in each terminal device including both operations.

(2) In the above embodiment, when the stroke is divided, all the information of the base stroke is included in the data of the object after the division. However, the above processing can be performed by including at least the corresponding portion normalized to the base stroke ID. The initial feature coordinates of the base stroke can be derived from the total amount of affine operations of each stroke after division.

(3) In the above embodiment, the operation data is transmitted to another terminal device via the server device S. However, the operation data may be directly transmitted to another terminal device without going through the server device S.

(4) The above-described embodiment and modification can be implemented in combination with other embodiments as long as the essence is not contrary to the essence.

Claims (33)

A content co-editing system including a server device and two or more terminal devices capable of communicating with the server device.
The server device is
An operation information recording means for recording the operation information received from each terminal device in the recording unit, and
It is equipped with an operation information distribution means that distributes the operation information recorded in the recording unit to each terminal device.
The terminal device is
A recording unit that records the feature coordinates of the object and the total amount of affine operations,
A direct operation receiving means that accepts operations on objects, and
A direct operation display means that operates the object and displays the operation result on the display unit based on the operation on the object received by the direct operation reception means.
Based on the operation on the object received by the direct operation receiving means, the feature coordinates of the object and the total affine operation amount are updated, and the total amount of the affine operation is transmitted to the server device as the operation information.
Indirect operation receiving means for receiving operation information received from the server device, and
When the operation information received by the indirect operation receiving means is received, the feature coordinates at the time of generation of the object are calculated based on the current feature coordinates of the object recorded in the recording unit and the total amount of affine operations, and the generation is performed. An indirect operation display means that calculates the feature coordinates after the operation based on the initial feature coordinates and the total amount of affine operation that is the received operation information and displays the operation result on the display unit.
An indirect operation recording means that updates the feature coordinates and the total amount of affine operations recorded in the recording unit with the feature coordinates after the operation and the total amount of affine operations received.
Content co-editing system with. In the system of claim 1,
The direct operation transmission means is a system characterized in that operation information is transmitted to another terminal device via a server device. A recording unit that records the feature coordinates of the object and the total amount of affine operations,
A direct operation receiving means that accepts operations on objects, and
A direct operation display means that operates the object and displays the operation result on the display unit based on the operation on the object received by the direct operation reception means.
Direct operation Based on the operation on the object received by the receiving means, the feature coordinates of the object and the total affine operation amount are updated, and the total amount of the affine operation is directly or indirectly transmitted to another terminal device as operation information. Operation transmission means and
An indirect operation receiving means that directly or indirectly receives operation information received from another terminal device,
When the operation information received by the indirect operation receiving means is received, the feature coordinates at the time of generation of the object are calculated based on the current feature coordinates of the object recorded in the recording unit and the total amount of affine operations, and the generation is performed. An indirect operation display means that calculates the feature coordinates after the operation based on the initial feature coordinates and the total amount of affine operation that is the received operation information and displays the operation result on the display unit.
An indirect operation recording means that updates the feature coordinates and the total amount of affine operations recorded in the recording unit with the feature coordinates after the operation and the total amount of affine operations received.
A terminal device equipped with. In the apparatus of claim 3,
The direct operation transmission means is a device characterized in that operation information is transmitted to another terminal device via a server device. A terminal program for realizing a terminal device by a computer.
A direct operation receiving means that accepts operations on objects, and
A direct operation display means that operates the object and displays the operation result on the display unit based on the operation on the object received by the direct operation reception means.
Based on the operation on the object received by the direct operation receiving means, the feature coordinates of the object and the total amount of affine operations recorded in the recording unit are updated, and the total amount of affine operations is used as operation information directly or indirectly. Direct operation transmission means to send to the terminal device of
An indirect operation receiving means that directly or indirectly receives operation information received from another terminal device,
When the operation information received by the indirect operation receiving means is received, the feature coordinates at the time of generation of the object are calculated based on the current feature coordinates of the object recorded in the recording unit and the total amount of affine operations, and the generation is performed. An indirect operation display means that calculates the feature coordinates after the operation based on the initial feature coordinates and the total amount of affine operation that is the received operation information and displays the operation result on the display unit.
A terminal program for functioning as an indirect operation recording means for updating the feature coordinates and the total amount of affine operations recorded in the recording unit with the feature coordinates after the operation and the total amount of the received affine operations. In the program of claim 5,
The direct operation transmission means is a program characterized in that operation information is transmitted to another terminal device via a server device. A content co-editing system including a server device and two or more terminal devices capable of communicating with the server device.
The server device is
An operation information recording means for recording the operation information received from each terminal device in the recording unit, and
It is equipped with an operation information distribution means that distributes the operation information recorded in the recording unit to each terminal device.
The terminal device is
A recording unit that records the feature coordinates of the object and the total amount of affine operations,
A direct operation receiving means that accepts operations on objects, and
A direct operation display means that operates the object and displays the operation result on the display unit based on the operation on the object received by the direct operation reception means.
Based on the operation on the object received by the direct operation receiving means, the feature coordinates of the object are updated, and the feature coordinates at the time of generation obtained by multiplying the updated feature coordinates by the inverse characteristic of the total amount of affine operations are used as the operation information of the server device. Direct operation transmission means to send to
An indirect operation receiving means for receiving the operation information received from the server device, and
When the operation information received by the indirect operation receiving means is received, the feature coordinates after the operation are calculated based on the total amount of affine operations of the object recorded in the recording unit and the feature coordinates at the time of generation which are the operation information. Indirect operation display means for displaying the operation result on the display unit,
An indirect operation recording means that updates the feature coordinates recorded in the recording unit with the feature coordinates after the operation,
Content co-editing system with. In the system of claim 7,
The direct operation transmission means is a system characterized in that operation information is transmitted to another terminal device via a server device. A recording unit that records the feature coordinates of the object and the total amount of affine operations,
A direct operation receiving means that accepts operations on objects, and
A direct operation display means that operates the object and displays the operation result on the display unit based on the operation on the object received by the direct operation reception means.
Based on the operation on the object received by the direct operation receiving means, the feature coordinates of the object are updated, and the feature coordinates at the time of generation obtained by multiplying the updated feature coordinates by the inverse characteristic of the total amount of affine operations are used as operation information in the server device. Direct operation to send Sending means and
An indirect operation receiving means for receiving the operation information received from the server device, and
When the operation information received by the indirect operation receiving means is received, the feature coordinates after the operation are calculated based on the total amount of affine operations of the object recorded in the recording unit and the feature coordinates at the time of generation which are the operation information. Indirect operation display means for displaying the operation result on the display unit,
An indirect operation recording means that updates the feature coordinates recorded in the recording unit with the feature coordinates after the operation,
A terminal device equipped with. In the apparatus of claim 9,
The direct operation transmission means is a device characterized in that operation information is transmitted to another terminal device via a server device. A terminal program for realizing a terminal device by a computer.
A direct operation receiving means that accepts operations on objects, and
A direct operation display means that operates the object and displays the operation result on the display unit based on the operation on the object received by the direct operation reception means.
Based on the operation on the object received by the direct operation receiving means, the feature coordinates of the object recorded in the recording unit are updated, and the updated feature coordinates are multiplied by the inverse characteristic of the total amount of affine operation. Direct operation transmission means to send to the server device as operation information,
An indirect operation receiving means for receiving the operation information received from the server device, and
When the operation information received by the indirect operation receiving means is received, the feature coordinates after the operation are calculated based on the total amount of affine operations of the object recorded in the recording unit and the feature coordinates at the time of generation which are the operation information. Indirect operation display means for displaying the operation result on the display unit,
An indirect operation recording means that updates the feature coordinates recorded in the recording unit with the feature coordinates after the operation,
Terminal program with. In the program of claim 11,
The direct operation transmission means is a program characterized in that operation information is transmitted to another terminal device via a server device. A content co-editing system including a server device and two or more terminal devices capable of communicating with the server device.
The server device is
An operation information recording means for recording the operation information received from each terminal device in the recording unit, and
It is equipped with an operation information distribution means that distributes the operation information recorded in the recording unit to each terminal device.
The terminal device is
A recording unit that records the feature coordinates of the object and the total amount of affine operations,
A direct operation receiving means that accepts feature coordinate operations or affine operations on objects,
A direct operation display means that operates the object and displays the operation result on the display unit based on the feature coordinate operation or the affine operation for the object received by the direct operation receiving means.
If the operation is a feature coordinate operation based on the operation on the object received by the direct operation reception means, the feature coordinates of the object are updated, and the updated feature coordinates are multiplied by the inverse characteristic of the total amount of affine operations at the beginning of generation. If the operation is an affine operation, the feature coordinates of the object and the total amount of the affine operation are updated, and the total amount of the affine operation is transmitted to the server device as the operation information. Direct operation transmission means and
An indirect operation receiving means for receiving the operation information received from the server device, and
When the operation information received by the indirect operation receiving means is received, if the operation information is related to the feature coordinate operation, the total amount of affine operations of the object recorded in the recording unit and the received operation information are the characteristics at the time of generation. The feature coordinates after the operation are calculated based on the coordinates, and the operation result is displayed on the display unit. If the operation information is related to the affine operation, the current feature of the object recorded in the recording unit is displayed. The feature coordinates at the time of generation of the object are calculated based on the coordinates and the total amount of affine operations, and the feature coordinates after the operation are calculated based on the feature coordinates at the time of generation and the total amount of affine operations received as the operation information. Then, the indirect operation display means for displaying the operation result on the display unit,
If the received operation information is a feature coordinate operation, the feature coordinates recorded in the recording unit are updated with the feature coordinates after the operation, and if the received operation information is an affine operation, it is recorded in the recording unit. An indirect operation recording means that updates the feature coordinates and the total amount of affine operations with the feature coordinates after the operation and the total amount of affine operations received.
Content co-editing system with. In the system of claim 13,
The direct operation transmission means is a system characterized in that operation information is transmitted to another terminal device via a server device. In any of the systems of claims 2, 8 and 14.
The operation information recording means of the server device records the operation information received from each terminal device in the recording unit so that the order of reception becomes clear.
The operation information distribution means of the server device distributes the operation information recorded in the recording unit to each terminal device in the order of reception.
The operation information received by the indirect operation receiving means of the terminal device and processed by the indirect operation display means includes not only the operation information of the other terminal device but also the operation of the own terminal device received by the direct operation receiving means. A system characterized by including information. A recording unit that records the feature coordinates of the object and the total amount of affine operations,
A direct operation receiving means that accepts feature coordinate operations or affine operations on objects,
A direct operation display means that operates the object and displays the operation result on the display unit based on the feature coordinate operation or the affine operation for the object received by the direct operation receiving means.
If the operation is a feature coordinate operation based on the operation on the object received by the direct operation reception means, the feature coordinates of the object are updated, and the updated feature coordinates are multiplied by the inverse characteristic of the total amount of affine operations at the beginning of generation. If the operation is an affine operation, the feature coordinates of the object and the total amount of the affine operation are updated, and the total amount of the affine operation is transmitted to the server device as the operation information directly. Operation transmission means and
An indirect operation receiving means for receiving the operation information received from the server device, and
When the operation information received by the indirect operation receiving means is received, if the operation information is related to the feature coordinate operation, the total amount of affine operations of the object recorded in the recording unit and the received operation information are the characteristics at the time of generation. The feature coordinates after the operation are calculated based on the coordinates, and the operation result is displayed on the display unit. If the operation information is related to the affine operation, the current feature of the object recorded in the recording unit is displayed. The feature coordinates at the time of generation of the object are calculated based on the coordinates and the total amount of affine operations, and the feature coordinates after the operation are calculated based on the feature coordinates at the time of generation and the total amount of affine operations received as the operation information. Then, the indirect operation display means for displaying the operation result on the display unit,
If the received operation information is a feature coordinate operation, the feature coordinates recorded in the recording unit are updated with the feature coordinates after the operation, and if the received operation information is an affine operation, it is recorded in the recording unit. An indirect operation recording means that updates the feature coordinates and the total amount of affine operations with the feature coordinates after the operation and the total amount of affine operations received.
A terminal device equipped with. In the apparatus of claim 16,
The direct operation transmission means is a device characterized in that operation information is transmitted to another terminal device via a server device. In any of the devices of claims 4, 10 and 17.
The server device records the operation information received from each terminal device in the recording unit so that the order in which the information is received is clarified.
The server device distributes the operation information recorded in the recording unit to each terminal device in the order in which it is received.
The operation information received by the indirect operation receiving means of the terminal device and processed by the indirect operation display means includes not only the operation information of the other terminal device but also the operation of the own terminal device received by the direct operation receiving means. A device characterized by containing information. A terminal program for realizing a terminal device by a computer.
A direct operation receiving means that accepts feature coordinate operations or affine operations on objects,
A direct operation display means that operates the object and displays the operation result on the display unit based on the feature coordinate operation or the affine operation for the object received by the direct operation receiving means.
If the operation is a feature coordinate operation based on the operation on the object received by the direct operation receiving means, the feature coordinates of the object recorded in the recording unit are updated, and the total amount of affine operations is added to the updated feature coordinates. The original feature coordinates multiplied by the inverse characteristics are transmitted to the server device as operation information, and if the operation is an affine operation, the feature coordinates of the object and the total amount of the affine operation recorded in the recording unit are updated and the operation is performed. A direct operation transmission means for transmitting the total amount of affine operations as operation information to the server device,
An indirect operation receiving means for receiving the operation information received from the server device, and
When the operation information received by the indirect operation receiving means is received, if the operation information is related to the feature coordinate operation, the total amount of affine operations of the object recorded in the recording unit and the received operation information are the characteristics at the time of generation. The feature coordinates after the operation are calculated based on the coordinates, and the operation result is displayed on the display unit. If the operation information is related to the affine operation, the current feature of the object recorded in the recording unit is displayed. The feature coordinates at the time of generation of the object are calculated based on the coordinates and the total amount of affine operations, and the feature coordinates after the operation are calculated based on the feature coordinates at the time of generation and the total amount of affine operations received as the operation information. Then, the indirect operation display means for displaying the operation result on the display unit,
If the received operation information is a feature coordinate operation, the feature coordinates recorded in the recording unit are updated with the feature coordinates after the operation, and if the received operation information is an affine operation, it is recorded in the recording unit. A terminal program for functioning as an indirect operation recording means that updates the feature coordinates and the total amount of affine operations with the feature coordinates after the operation and the total amount of affine operations received. In the program of claim 19.
The direct operation transmission means is a program characterized in that operation information is transmitted to another terminal device via a server device. In any of the programs of claims 6, 12, and 20
The server device records the operation information received from each terminal device in the recording unit so that the order in which the information is received is clarified.
The server device distributes the operation information recorded in the recording unit to each terminal device in the order in which it is received.
The operation information received by the indirect operation receiving means of the terminal device and processed by the indirect operation display means includes not only the operation information of the other terminal device but also the operation of the own terminal device received by the direct operation receiving means. A program characterized by including information. A content co-editing system including a server device and two or more terminal devices capable of communicating with the server device.
The server device is
An operation information recording means for recording the operation information received from each terminal device in the recording unit, and
It is equipped with an operation information distribution means that distributes the operation information recorded in the recording unit to each terminal device.
The terminal device is
A recording unit that records the feature coordinates of the line object and the feature coordinates at the time of generation,
Direct operation receiving means that accepts operations on line objects,
A direct operation display means that deletes a part of the line object and displays the operation result on the display unit based on the delete operation that divides the line object into two or more received by the direct operation reception means.
Based on the partial deletion of the line object received by the direct operation reception means, the line object is divided into two or more line objects, the feature coordinates of each line object are recorded in the recording unit, and the line objects are associated with each other. A direct operation transmission means that records the initial feature coordinates of the line object before division in association with each other and transmits these as operation information to the server device.
Indirect operation receiving means for receiving operation information received from the server device, and
When the operation information received by the indirect operation receiving means is received, a part of the line object recorded in the recording unit is deleted and the operation result is displayed on the display unit.
Based on the above deletion, the line object recorded in the recording unit is divided into two or more line objects, the feature coordinates of each line object are recorded in the recording unit, and the line object before division is associated with these line objects. An indirect operation recording means that records the original feature coordinates of the object in association with each other.
Content co-editing system with. In the system of claim 22,
The direct operation transmission means is a system characterized in that operation information is transmitted to another terminal device via a server device. In the system of claim 23
The operation information recording means of the server device records the operation information received from each terminal device in the recording unit so that the order of reception becomes clear.
The operation information distribution means of the server device distributes the operation information recorded in the recording unit to each terminal device in the order of reception.
The operation information received by the indirect operation receiving means of the terminal device and processed by the indirect operation display means includes not only the operation information of the other terminal device but also the operation of the own terminal device received by the direct operation receiving means. A system characterized by including information. In any of the systems of claims 22-24
The deletion operation information is a system characterized in that the deletion position includes a position relative to the total length of the line object regardless of the shape of the line object. A recording unit that records the feature coordinates of the line object and the feature coordinates at the time of generation,
Direct operation receiving means that accepts operations on line objects,
A direct operation display means that deletes a part of the line object and displays the operation result on the display unit based on the delete operation that divides the line object into two or more received by the direct operation reception means.
Based on the partial deletion of the line object received by the direct operation reception means, the line object is divided into two or more line objects, the feature coordinates of each line object are recorded in the recording unit, and the line objects are associated with each other. A direct operation transmission means that records the initial feature coordinates of the line object before division in association with each other and directly or indirectly transmits these as operation information to other terminal devices.
An indirect operation receiving means that directly or indirectly receives operation information received from another terminal device,
When the operation information received by the indirect operation receiving means is received, a part of the line object recorded in the recording unit is deleted and the operation result is displayed on the display unit.
Based on the above deletion, the line object recorded in the recording unit is divided into two or more line objects, the feature coordinates of each line object are recorded in the recording unit, and the line object before division is associated with these line objects. An indirect operation recording means that records the original feature coordinates of the object in association with each other.
A terminal device equipped with. In the apparatus of claim 26
The direct operation transmission means is a device characterized in that operation information is transmitted to another terminal device via a server device. In the apparatus of claim 27
The operation information recording means of the server device records the operation information received from each terminal device in the recording unit so that the order of reception becomes clear.
The operation information distribution means of the server device distributes the operation information recorded in the recording unit to each terminal device in the order of reception.
The operation information received by the indirect operation receiving means of the terminal device and processed by the indirect operation display means includes not only the operation information of the other terminal device but also the operation of the own terminal device received by the direct operation receiving means. A device characterized by containing information. In any of the devices of claims 26 to 28,
The deletion operation information is a device characterized in that the deletion position includes a position relative to the total length of the line object regardless of the shape of the line object. A terminal program for realizing a terminal device by a computer.
Direct operation receiving means that accepts operations on line objects,
A direct operation display means that deletes a part of the line object and displays the operation result on the display unit based on the delete operation that divides the line object into two or more received by the direct operation reception means.
Based on the partial deletion of the line object received by the direct operation reception means, the line object is divided into two or more line objects, the feature coordinates of each line object are recorded in the recording unit, and the line objects are associated with each other. A direct operation transmission means that records the initial feature coordinates of the line object before division in association with each other and directly or indirectly transmits these as operation information to other terminal devices.
An indirect operation receiving means that directly or indirectly receives operation information received from another terminal device,
When the operation information received by the indirect operation receiving means is received, a part of the line object recorded in the recording unit is deleted and the operation result is displayed on the display unit.
Based on the above deletion, the line object recorded in the recording unit is divided into two or more line objects, the feature coordinates of each line object are recorded in the recording unit, and the line object before division is associated with these line objects. A terminal program for functioning as an indirect operation recording means that records the initial feature coordinates of an object in association with each other. In the program of claim 30
The direct operation transmission means is a program characterized in that operation information is transmitted to another terminal device via a server device. In the program of claim 31
The operation information recording means of the server device records the operation information received from each terminal device in the recording unit so that the order of reception becomes clear.
The operation information distribution means of the server device distributes the operation information recorded in the recording unit to each terminal device in the order of reception.
The operation information received by the indirect operation receiving means of the terminal device and processed by the indirect operation display means includes not only the operation information of the other terminal device but also the operation of the own terminal device received by the direct operation receiving means. A program characterized by including information. In any of the programs of claims 30 to 32
The deletion operation information is a program characterized in that the deletion position includes a position relative to the total length of the line object regardless of the shape of the line object.

Images