Shared edit access of electronic content
In various embodiments, a computerized method includes presenting an electronic document to one user out of multiple users that have edit access to the electronic document as part of a collaborative editing of the electronic document. The computerized method may include receiving an input from the user to edit the electronic document, as well as invoking a lock to prevent edit access by the other users responsive to receiving the input from the user to edit the electronic document.
Latest Adobe Systems Incorporated Patents:
This application is a continuation of U.S. application Ser. No. 13/081,236, filed Apr. 6, 2011, now U.S. Pat. No. 8,290,902, issued Oct. 16, 2012, and entitled “Shared Edit Access of Electronic Content,” which is a continuation of U.S. application Ser. No. 12/119,335, filed May 12, 2008, now U.S. Pat. No. 7,949,633 issued May 24, 2011, of which both applications are incorporated in their entirety herein by reference.
COPYRIGHTA portion of the disclosure of this document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever. The following notice applies to the software, data, and/or screenshots which may be described below and in the drawings that form a part of this document: Copyright 2008, Adobe® Systems Incorporated. All Rights Reserved.
BACKGROUNDThe approaches described in this section could be pursued, but are not necessarily approaches that have been previously conceived or pursued. Therefore, unless otherwise indicated herein, the approaches described in this section are not prior art to the claims in this application and are not admitted to be prior art by inclusion in this section.
In a collaborative content creation and review environment, content (e.g., an electronic document) may be stored in a server for access (e.g., edit, read, review, etc.) by multiple users using different client devices. In particular, the server may be communicatively coupled to the client devices to enable access by the users. In such an application, users may edit a same electronic content at substantially the same time, or at different times.
The embodiments are provided by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which:
Methods, apparatus and systems tier shared edit access of content in a collaborative environment are described. In the following description, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In other instances, structures and techniques have not been shown in detail in order not to Obscure the understanding of this description.
As used herein, the term “content” or “electronic content” may comprise any type of content for use in electronic form. Examples of content may comprise Portable Document Format (“PDF”) which may be viewed and modified in one of the Adobe® Acrobat® programs, a web page, a word processing document (such as a Microsoft® Word document), a spread sheet document, page-descriptive electronic content, hypertext document, a markup language document, declarative specification document (such as for example a HyperText Markup Language HTML or eXtensible Markup Language (XML) document), a finable form or data describing application graphical user interface, etc.
Some example embodiments are performed in a collaborative environment, wherein multiple users may access (e.g., edit, read, review, etc.) content. In particular, the content may be stored in a server. The users may access the content over a network using different client devices. Example embodiments enable shared edit access of content in such an environment. In particular, multiple users may edit the content.
In some example embodiments, a user locks the content to prevent other users from editing the content after the user performs content editing. In some example embodiments, the lock to prevent edit access remains until the edited content is saved. The saving of the content may be invoked by the user that performed the editing activity. Alternatively or in addition, the saving of the content may be invoked by the application (used to edit the content) after a given time period has expired since the edit has occurred. After the edited content has been saved, any of the users having edit access may edit the content. Once another edit has been performed by any one of the users, the content is again locked. The user that edited the content now has control and precludes other users from editing the content until the edits are saved. Accordingly, users are not required to explicitly check-out/check-in the content each time they are going to edit the content. In some example embodiments, the locking of the content for editing is integrated into editing/saving operations. Thus, some example embodiments provide more transparent and easier shared edit access for the multiple users.
The server computer system 108 comprises a collaborative control module 110 (hereinafter “the control module 110”) and is coupled to a machine-readable medium 112 (which may be or may not be part of the server computer system 108). In some example embodiments, the machine-readable medium includes tangible volatile and/or non-volatile media (e.g., read only memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media, flash memory devices, etc.). The machine-readable medium 112 may store content 114 that may be shared by multiple users, particular, multiple users may access (edit, read, review, etc.) the same content 114. For example more than one user (using one or more client computer systems 102) may edit the same electronic document forming a part of the electronic content 114 that is stored in the machine-readable medium 112.
The client computer systems 102A-102N comprise collaborative content application module 104A-104N (hereinafter “application modules 104”), respectively. The application modules 104 and the control module 110 may be software, hardware, firmware or a combination thereof for executing the various operations described herein, according to some example embodiments.
As part of multiple users having edit access to the same content 114, a first user may edit the content 114 using the application module 104A, and a second user may edit the same content 114 using the application module 104N at a different time. For example, the application modules 104 may comprise a type of word processor application for editing electronic documents. The application modules 104 may retrieve a copy of the content 114 from the server computer system 108 and make edits to such content 114. As further described below, after a first user edits (using the application module 104) a particular portion of the content 114, that portion of the content 114 is locked from being editing by other users until it is saved onto the machine-readable medium 112.
The system 100 may comprise any number of client computer systems 102. While the control module 110 and the content 114 are described as forming part of the same server, many embodiments are not so limited. Alternatively or in addition, the content 114 and the control module 110 may be distributed across any number of network storage devices/servers.
In some embodiments, operations may be executed in a peer-to-peer architecture. The network communication may occur as part of any combination of wired and wireless communication. In some embodiments, network communication may be based on one or more communication protocols (e.g., HyperText Transfer Protocol (HTTP), HTTP Secured (HTTPS), Real Time Messaging Protocol (RTMP), Real Time Messaging Protocol Secured/SSL (RTMPS), etc.). While the system 100 shown in
Operations, according to example embodiments, are now described. In certain embodiments, the operations are performed when instructions residing on machine-readable media (e.g., software) are executed, while in other embodiments, the methods are performed by hardware or other logic (e.g., digital logic).
Accordingly,
At block 202, the application module 104 presents content 114 to one or more users out of multiple users that have edit access to the content. In some example embodiments, the application module 104 may present a specific type of content 114 (e.g., an electronic document) to the user after the user selects the content 114 for editing, The application module 104 may request and receive the content 114 from the control module 110 on the server computer system 108. The application module 104 may present the content 114 to the user using some type of display.
For example, the user identification 306 identifies a user #1 that has an author role (which enables user #1 to edit the electronic document 304). The user identification 306 also indicates that the current access status is “viewing” for user #1. Accordingly, user #1 is currently viewing but not editing the electronic document 304. The user identification 308 identifies a user #2 that has an author role (which enables user #2 to edit the electronic document 304). The user identification 308 also indicates that the current access status is “viewing” for user #2. Returning to
At block 204, the application module 104 receives input from the user indicating a desire to edit the content 114. The input may be from a keyboard, mouse, microphone, etc. that causes changes in the content 114. The application module 104 may update the local copy of the content 114 that is being stored in some type of machine-readable medium (not shown) on the client computer system 102. For example, the updates may be made to a copy of the content 114 stored in random access memory. The application module 104 may also update any display of the content 114.
Returning to the description of block 204 of
At block 206, the application module 104 transmits a lock command (to lock the content 114) to the server computer system 108, in response to editing of the content 114. As further described below, the lock command precludes other users from editing the same content 114. In some situations, two users may be attempting edits at approximately the same time. Accordingly, one user will be able to lock the content 114, while the second user is locked out. Thus, the second user has made edits to content 114 that has been locked from edit access.
In some example embodiments, the application module 104 for the second user may process these edits that occur at different times differently (depending on the amount time that has expired between when the edit occurred and when the attempted lock command is transmitted to the server computer system 108). For example, if the amount of time that has expired is less than a given time period (e.g., 10 seconds, 20 seconds, 30 seconds, 1 minute, etc.), the application module 104 can display an error message to the second user and the edits made by the second user are discarded. If the amount of time that has expired is greater than the given time period, the application module 104 provides an option to the second user to save the content 114 under a different name (thus creating separately saved content 114 within the server computer system 108).
This preclusion of editing (caused by the lock command) remains until the edits that have already been entered are saved at the server computer system 108. Accordingly, locking occurs in response to an edit action that remains unsaved. There is no requirement that the user perform an explicit check-out of the content 114 in order to ensure that other users are precluded from editing the content 114. The method 200 continues at block 208.
At block 208, the application module 104 saves the content 114 to the server computer system 108. In some example embodiments, the application module 104 saves the content 114 in the machine-readable medium 112 at the server computer system 108. The application module 104 may transmit unsaved edits to the server computer system 108 via any type of communication (as described above). In some example embodiments, the save activity may be in response to a user-invoked save action, or an application-invoked save action. In particular, saving the content 114 may be invoked by input from a user that is editing the content 114. Alternatively or in addition, the application module 104 may periodically perform a save e.g., an auto-save). In some example embodiments, the application module 104 may save the content 114 (independent of user input) after a time period (that starts after an edit has occurred) during which there is no user activity relative to the content 114. For example, user activity may comprise editing data, movement of a cursor through the content 114, etc. In some example embodiments, this time period may be 15 seconds, 30 seconds, 45, seconds, 1 minute, 5 minutes, etc. Alternatively or in addition, the application module 104 may save the content 114 (independent of user input) after a time period (that starts after an edit has occurred) even if there is user activity relative to the content 114. in some example embodiments, this time period may be 30 seconds, 1 minute, 2 minutes, 3 minutes, 5 minutes, 10 minutes, etc. The method 200 continues at block 210.
At block 210, the application module 104 receives confirmation of the saving of the content 114 (at the server computer system 108) from the server computer system 108. In particular, if the edits to the content 114 are saved by the control module 110 in the machine-readable medium 112, the control module 110 transmits a confirmation back to the client computer system 102. The method 200 continues at block 212.
At block 212, the application module 104 transmits a release command (to release the lock of the content 114) to the server computer system 108. The release command is transmitted to the server computer system 108 to enable other users having edit access to edit this particular content 114. As further described below, the control module 110 transmits a release command to other client devices that are accessing this particular content 114. Accordingly, the application modules on these other client computer systems may then enable editing of the content 114 by other users. The method 200 is complete.
The operations, according to some example embodiments, of the control module 110 at the server computer system 108 are now described. In particular,
At block 502, the control module 110 receives a request, from a first client computer system 102, to edit content 114 by one user out of multiple users that have edit access to the content 114. The request may come from the application module 104 for the client computer system 102 that is being used to edit the content 114. In some example embodiments, the request may be a result of a user opening the content 114 using the application module 104. The method 500 continues at block 504.
At block 504, the control module 110 transmits the content 114 to the first client computer system 102. The control module 110 may retrieve a copy of the content 114 from the machine-readable medium 112 for transmission to the first client computer system 102. The method 500 continues at block 506.
At block 506, the control module 110 receives a lock command from the first client computer system 102 (to lock the content 114) from edit access by others of the multiple users. In some example embodiments, the lock command is received from the application module 104 in response to the first user editing the particular content 114 (as described above). The method 500 continues at block 508.
At block 508, the control module 110 transmits a lock command to other client computer systems 102 being used by other users. The lock command provides notification that the content 114 is currently locked from edit access. In some example embodiments, the control module 110 only transmits the lock command to the client computer systems 102 where the content 114 is currently being accessed. As further described below, the application modules 104 executing on these other client computer systems 102 prevent the users from editing the content 114 after the lock command is received. The method 500 continues at block 510.
At block 510, the control module 110 saves edits to the content 114 at the server computer system 108. In some example embodiments, a save command may be received from the client computer system 102 that is being used to edit the content 114. As described above, the save command may be in response to user-invoked or application-invoked save activity. The control module 110 may save the edits for this content 114 into the machine-readable medium 112. The method 500 continues at block 512.
At block 512, the control module 110 transmits confirmation of saving the content 114 at the server computer system 108. In particular, the control module 110 may transmit the confirmation back to the client computer system 102 from which the save command was received. The method 500 continues at block 514.
At block 514, the control module 110 receives a release command (to release the lock on the content 114). The release command may be received from the application module 104 that is executing on the client computer system 102 that saved the content 114. In some example embodiments, the release command enables other users to edit this particular content 114. The method 500 continues at block 516.
At block 516, the control module 110 transmits a release command to the other client computer systems 102 being used by other users having edit access with respect to the content 114. The release command provides notification that the content 114 (that was previously locked) can now be edited by the other users. In some example embodiments, the control module 110 only transmits to the client computer systems 102 wherein the content 114 is currently being accessed. As further described below, the application modules 104 executing on these other client computer systems 102 then allow the users to edit this particular content 114 after the release command is received.
In some example embodiments, the control module 110 may also transmit a release command to the other client computer systems 102 if there is a communication loss with the client computer system 102 that has locked the content 114. In particular, the control module 110 may exchange ping-type communications with the client computer system 102. If this communication ceases beyond a given period of time (e.g., 1 minute, 2 minutes, 5 minutes, 10 minutes, etc.), the control module 110 may release any locks currently in force. In some example embodiments, the client computer system that lost the lock may be able to reconnect and save unsaved edits. In particular, if the client computer system 102 reconnects with the server computer system 108 and no other client computer system 102 has locked the content 114 during the time when communication was lost, the application module 104 thereon may able to re-obtain the lock for the content 114. After the release command is transmitted, the method 500 is complete.
Additional operations, according to some example embodiments, of the application module 104 at the client computer system 102 are now described. In particular, these operations are from the perspective of the application module 104 that is being used by one user that is locked from edit access because another user is editing the content 114. Thus,
At block 602, the application module 104 presents content 114 to one or more users that have edit access to the content 114. In some example embodiments, the application module 104 may present particular content 114 (e.g., an electronic document) to a user after the user selects the content 114 for editing. The application module 104 may request and receive the content 114 from the control module 110 on the server computer system 108. The application module 104 may present the content 114 to the user using some type of display (see.
At block 604, the application module 104 receives a lock command from the server computer system 108. The lock command provides notification that the content 114 is currently locked from edit access because a different user has made edits to the content 114 that are not saved. The method 600 continues at block 606.
At block 606, the application module 104 locks the content 114 to prevent edit access by one or more users. Accordingly, these users are not allowed to edit the content 114 until the lock is released by saving the edits at the server computer system 108 (as described above).
In some example embodiments, a pop-up message is displayed to the user regarding their inability to edit. To illustrate,
At block 608, the application module 104 receives a release command to enable edit access of the content 114 by another user. This release command may be received from the control module 110 at the server computer system 108. In some example embodiments, this release is a result of the unsaved edits made by a different user on a different client computer system 102 being saved at the server computer system 108 (as described above). Also, as a result, the application module 104 releases the lock that is precluding edit access of the content 114. In some example embodiments, an attempt to edit the electronic content by the user may cause or attempt to cause a release of the lock that is precluding edit access of the electronic content (that has been locked by the other user). To illustrate, assume that the electronic content is currently locked because the other user has made unsaved edits to the electronic content. If this user attempts to edit the electronic content, a communication may be transmitted to the server computer system 108, the server computer system 108 may determine if a time period has expired since there has been activity by the other user within the electronic document. For example, the server computer system 108 may query the client computer system 102 being used by the other user (that has caused the locking) The query may request the last time that the other user performed any activity in the electronic content (e.g., editing, movement of cursor, etc.). If a time period has expired, the server computer system 108 may release the lock. In some example embodiments, the server computer system 108 may save any unsaved edits to the electronic content prior to the release. Moreover, the server computer system 108 may notify the other user of the release. At this point, the method 600 may be complete.
While the communications regarding the locking and releasing of edit access to content 114 may be routed through a server computer system 108, in some example embodiments, some or all such communications may also be routed among the client computer systems (independent of the server computer system 108). For example, a lock command initiated due to the existence of unsaved edits at one client computer system may be transmitted to other applicable client computer systems. Alternatively or in addition, while the content 114 is described as being stored at the server computer system 108, in some example embodiments, the content 114 may be stored at the client computer systems in a peer-to-peer configuration. Accordingly, after an edit is saved, the saved content 114 is distributed to the different client computer systems. In some example embodiments, this storage of data in the client computer systems may be in addition to or independent of storage of such content 114 at the server computer system 108.
A detailed block diagram of an example computer environment, according to some embodiments, is now described. In particular,
As illustrated in
The memory unit 830 may store data and/or instructions, and may comprise any suitable memory, such as a dynamic random access memory (DRAM). The computer system 800 also includes IDE drive(s) 808 and/or other suitable storage devices. A graphics controller 804 controls the display of information on a display device 806, according to some embodiments of the invention.
The input/output controller hub (ICH) 824 provides an interface to I/O devices or peripheral components for the computer system 800. The ICH 824 may comprise any suitable interface controller to provide for any suitable communication link to the processor(s) 802, memory unit 830 and/or to any suitable device or component in communication with the ICH 824. For one embodiment of the invention, the ICH 824 provides suitable arbitration and buffering for each interface.
For some embodiments of the invention, the ICH 824 provides an interface to one or more suitable integrated drive electronics (IDE) drives 808, such as a hard disk drive (HDD) or compact disc read only memory (CD ROM) drive, or to suitable universal serial bus (USB) devices through one or more USB ports 810. For one embodiment, the ICH 824 also provides an interface to a keyboard 812, a mouse 814, a CD-ROM drive 818, one or more suitable devices through one or more FireWire® ports 816. For one embodiment of the invention, the ICH 824 also provides a network interface 820 though which the computer system 800 can communicate with other computers and/or devices.
In some embodiments, the computer system 800 includes a machine-readable medium that stores a set of instructions (e.g., software) embodying any one, or all, of the methodologies for described herein, Furthermore, software may reside, completely or at least partially, within memory unit 830 and/or within the processor(s) 802.
In the description, numerous specific details such as logic implementations, opcodes, means to specify operands, resource partitioning/sharing/duplication implementations, types and interrelationships of system components, and logic partitioning/integration choices are set forth in order to provide amore thorough understanding of the present invention. It will be appreciated, however, by one skilled in the art that embodiments of the invention may be practiced without such specific details. In other instances, control structures, gate level circuits and full software instruction sequences have not been shown in detail in order not to obscure the embodiments of the invention, Those of ordinary skill in the art, with the included descriptions will be able to implement appropriate functionality without undue experimentation.
References in the specification to “one embodiment”, “an embodiment”, “an example embodiment”, etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic, Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
Embodiments of the invention include features, methods or processes that may be embodied within machine-executable instructions provided by a machine-readable medium. A machine-readable medium includes any mechanism which provides (i.e., stores and/or transmits) information in a form accessible by a machine (e.g., a computer, a network device, a personal digital assistant, manufacturing tool, any device with a set of one or more processors, etc.). In example embodiments, a machine-readable medium includes volatile and/or non-volatile media (e.g., read only memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media, flash memory devices, etc.).
Such instructions are utilized to cause a general or special purpose processor, programmed with the instructions, to perform methods or processes of the embodiments of the invention. Alternatively, the features or operations of embodiments of the invention are performed by specific hardware components which contain hard-wired logic for performing the operations, or by any combination of programmed data processing components and specific hardware components. Embodiments of the invention include software, data processing hardware, data processing system-implemented methods, and various processing operations, further described herein.
In view of the wide variety of permutations to the embodiments described herein, this detailed description is intended to be illustrative only, and should not be taken as limiting the scope of the invention. What is claimed as the invention, therefore, is all such modifications as may come within the scope and spirit of the following claims and equivalents thereto, Therefore, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.
Claims
1. A method comprising:
- providing an electronic document to a device of a user of a plurality of users that have edit access to the electronic document as part of a collaborative editing of the electronic document;
- receiving a lock command from the device of the user to prevent edit access by other users of the plurality of users that have edit access to the electronic document; and
- transmitting, using a hardware processor, the lock command to devices of the other users of the plurality of users.
2. The method of claim 1, further comprising:
- saving content received from the device of the user;
- sending a save confirmation to the device of the user based on the saving; and
- receiving a release command from the device of the user in response to the sending of the confirmation that releases a lock that is based on the lock command.
3. The method of claim 1, further comprising transmitting a release command to the devices of the other users of the plurality of users that releases a lock that is based on the lock command.
4. The method of claim 1, further comprising receiving an input from the device of the user to edit the electronic document, the input triggering the lock command to be generated at the device of the user.
5. The method of claim 1, further comprising allowing the other users to add a comment to the electronic document despite the lock to prevent edit access by the other users.
6. The method of claim 1, further comprising releasing the lock in response to a different user attempting to edit the electronic document and a time period having expired since there has been activity by the user to the electronic document.
7. The method of claim 1, further comprising providing a graphical user interface, the graphic user interface providing a list of the other users and an access status for each of the other users currently accessing the electronic document.
8. A method comprising:
- providing an electronic document to a device of a user of a plurality of users that have edit access to the electronic document as part of a collaborative editing of the electronic document;
- invoking, using a hardware processor, a lock to prevent edit access by other users of the multiple users of the electronic document in response to the receiving of an input from the device of the user to edit the electronic document that prevents edit access by other users of the plurality of users that have edit access to the electronic document;
- sending a save confirmation to the device of the user based on saving content provided by the device; and
- receiving a release from the device of the user in response to the device receiving the save confirmation that releases the lock.
9. The method of claim 8, further comprising transmitting a release command to devices of the other users of the plurality of users based on the receiving of the release from the device of the user.
10. The method of claim 8, further comprising receiving the input from the device of the user to edit the electronic document, the input triggering the lock command to be generated at the device of the user.
11. The method of claim 10, further comprising receiving the lock command from the device of the user to prevent edit access by the other users.
12. The method of claim 8, further comprising allowing the other users to add a comment to the electronic document despite the lock to prevent edit access by the other users.
13. The method of claim 8, further comprising releasing the lock in response to a different user attempting to edit the electronic document and a time period having expired since there has been activity by the user to the electronic document.
14. The method of claim 8, further comprising providing a graphical user interface, the graphic user interface providing a list of the other users and an access status for each of the other users currently accessing the electronic document.
15. A non-transitory machine-readable storage medium including instructions, which when executed by a machine, cause the machine to perform operations comprising:
- providing an electronic document to a device of a user of a plurality of users that have edit access to the electronic document as part of a collaborative editing of the electronic document;
- receiving a lock command from the device of the user to prevent edit access by other users of the plurality of users that have edit access to the electronic document; and
- transmitting the lock command to devices of the other users of the plurality of users.
16. The non-transitory machine-readable storage medium of claim 15, wherein the operations further comprise:
- saving content received from the device of the user;
- sending a save confirmation to the device of the user based on the saving;
- receiving a release command from the device of the user in response to the sending of the confirmation that releases a lock that is based on the lock command; and
- transmitting a release command to the devices of the other users of the plurality of users.
17. The non-transitory machine-readable storage medium of claim 15, wherein the operations further comprise allowing the other users to add a comment to the electronic document despite the lock to prevent edit access by the other users.
18. The non-transitory machine-readable storage medium of claim 15, wherein the operations further comprise releasing the lock in response to a different user attempting to edit the electronic document and a time period having expired since there has been activity by the user to the electronic document.
19. A server comprising:
- a non-transitory machine-readable medium to store an electronic document that is edit accessible by a plurality of users from client devices communicatively coupled to the server; and
- a control module to provide the electronic document for presentation to a user of the plurality of users that have edit access to the electronic document as part of a collaborative editing of the electronic document, to invoke a lock to prevent edit access by other users of the multiple users of the electronic document in response to the receiving of an input from the device of the user to edit the electronic document that prevents edit access by other users of the plurality of users that have edit access to the electronic document, to send a save confirmation to the device of the user based on saving content provided by the device; and to receive a release from the device of the user in response to the device receiving the save confirmation.
20. The server of claim 19, wherein the control module further comprises transmitting a release command to devices of the other users of the plurality of user based on the received release from the device of the user.
4714992 | December 22, 1987 | Gladney et al. |
4949300 | August 14, 1990 | Christenson et al. |
5008853 | April 16, 1991 | Bly et al. |
5014267 | May 7, 1991 | Tompkins et al. |
5072412 | December 10, 1991 | Henderson, Jr. et al. |
5220657 | June 15, 1993 | Bly et al. |
5245553 | September 14, 1993 | Tanenbaum |
5247615 | September 21, 1993 | Mori et al. |
5293619 | March 8, 1994 | Dean |
5339389 | August 16, 1994 | Bates et al. |
5379374 | January 3, 1995 | Ishizaki et al. |
5388196 | February 7, 1995 | Pajak et al. |
5428729 | June 27, 1995 | Chang et al. |
5446842 | August 29, 1995 | Schaeffer et al. |
5471318 | November 28, 1995 | Ahuja et al. |
5515491 | May 7, 1996 | Bates et al. |
5537529 | July 16, 1996 | Borovoy et al. |
5608872 | March 4, 1997 | Schwartz et al. |
5617539 | April 1, 1997 | Ludwig et al. |
5664183 | September 2, 1997 | Cirulli et al. |
5671428 | September 23, 1997 | Muranaga et al. |
5732184 | March 24, 1998 | Chao et al. |
5758079 | May 26, 1998 | Ludwig et al. |
5764902 | June 9, 1998 | Rothrock |
5778368 | July 7, 1998 | Hogan et al. |
5787175 | July 28, 1998 | Carter |
5806078 | September 8, 1998 | Hug et al. |
5835601 | November 10, 1998 | Shimbo et al. |
5867654 | February 2, 1999 | Ludwig et al. |
5907324 | May 25, 1999 | Larson et al. |
5909689 | June 1, 1999 | Van Ryzin |
5920694 | July 6, 1999 | Carleton et al. |
5963208 | October 5, 1999 | Dolan et al. |
5966512 | October 12, 1999 | Bates et al. |
5978817 | November 2, 1999 | Giannandrea et al. |
5995097 | November 30, 1999 | Tokumine et al. |
6005568 | December 21, 1999 | Simonoff et al. |
6005571 | December 21, 1999 | Pachauri |
6088702 | July 11, 2000 | Plantz et al. |
6243722 | June 5, 2001 | Day |
6266683 | July 24, 2001 | Yehuda et al. |
6314408 | November 6, 2001 | Salas et al. |
6314425 | November 6, 2001 | Serbinis et al. |
6342906 | January 29, 2002 | Kumar et al. |
6366930 | April 2, 2002 | Parker et al. |
6366933 | April 2, 2002 | Ball et al. |
6442748 | August 27, 2002 | Bowman-Amuah et al. |
6446093 | September 3, 2002 | Tabuchi |
6502113 | December 31, 2002 | Crawford et al. |
6507845 | January 14, 2003 | Cohen et al. |
6584466 | June 24, 2003 | Serbinis et al. |
6596030 | July 22, 2003 | Ball et al. |
6632251 | October 14, 2003 | Rutten et al. |
6643663 | November 4, 2003 | Dabney et al. |
6701345 | March 2, 2004 | Carley et al. |
6721921 | April 13, 2004 | Altman |
6757871 | June 29, 2004 | Sato et al. |
6772393 | August 3, 2004 | Estrada et al. |
6816906 | November 9, 2004 | Icken et al. |
6819806 | November 16, 2004 | Kubota et al. |
6839878 | January 4, 2005 | Icken et al. |
6865548 | March 8, 2005 | Wiechers |
6865713 | March 8, 2005 | Bates et al. |
6874124 | March 29, 2005 | Murase et al. |
6889896 | May 10, 2005 | Silverbrook et al. |
6894804 | May 17, 2005 | Nguyen et al. |
6898601 | May 24, 2005 | Amado et al. |
6901376 | May 31, 2005 | Sculler et al. |
6918082 | July 12, 2005 | Gross et al. |
6934721 | August 23, 2005 | Schein |
6950828 | September 27, 2005 | Shaw et al. |
6991154 | January 31, 2006 | Silverbrook et al. |
7007232 | February 28, 2006 | Ross et al. |
7028267 | April 11, 2006 | Beezer et al. |
7044363 | May 16, 2006 | Silverbrook et al. |
7051031 | May 23, 2006 | Schein |
7062497 | June 13, 2006 | Hamburg et al. |
7062532 | June 13, 2006 | Sweat et al. |
7146367 | December 5, 2006 | Shutt |
7149760 | December 12, 2006 | Breuer |
7249314 | July 24, 2007 | Walker et al. |
7263655 | August 28, 2007 | Carden, Jr. |
7325186 | January 29, 2008 | Jones et al. |
7392469 | June 24, 2008 | Bailin |
7421660 | September 2, 2008 | Charnock et al. |
7506262 | March 17, 2009 | Gupta et al. |
7574669 | August 11, 2009 | Braun et al. |
7587407 | September 8, 2009 | Gruhl et al. |
7676759 | March 9, 2010 | Carter |
7702618 | April 20, 2010 | Patterson |
7724249 | May 25, 2010 | Horikawa et al. |
7769810 | August 3, 2010 | Kaufman |
7788237 | August 31, 2010 | Voronov et al. |
7809688 | October 5, 2010 | Cisler et al. |
7836083 | November 16, 2010 | Cipollone |
7904425 | March 8, 2011 | Cannon et al. |
7945595 | May 17, 2011 | Kraley |
7949633 | May 24, 2011 | Shaver et al. |
7950064 | May 24, 2011 | Chavez et al. |
8290902 | October 16, 2012 | Shaver et al. |
8316292 | November 20, 2012 | Verstak et al. |
8396900 | March 12, 2013 | Kraley |
20010043716 | November 22, 2001 | Price et al. |
20010049704 | December 6, 2001 | Hamburg et al. |
20020133628 | September 19, 2002 | Asplund et al. |
20020163548 | November 7, 2002 | Chiu et al. |
20020186252 | December 12, 2002 | Himmel et al. |
20030214528 | November 20, 2003 | Pierce et al. |
20040041843 | March 4, 2004 | Cui et al. |
20040088331 | May 6, 2004 | Therrien et al. |
20040172595 | September 2, 2004 | Lerner et al. |
20050064858 | March 24, 2005 | Makela et al. |
20050081159 | April 14, 2005 | Gupta et al. |
20050097441 | May 5, 2005 | Herbach et al. |
20050193325 | September 1, 2005 | Epstein |
20050262225 | November 24, 2005 | Halpern et al. |
20060010382 | January 12, 2006 | Ejiri et al. |
20060026502 | February 2, 2006 | Dutta |
20060161516 | July 20, 2006 | Clarke et al. |
20060161578 | July 20, 2006 | Siegel et al. |
20060184901 | August 17, 2006 | Dietz |
20070057967 | March 15, 2007 | Armstrong |
20070118794 | May 24, 2007 | Hollander et al. |
20070150433 | June 28, 2007 | Chen |
20070198616 | August 23, 2007 | Goto |
20070239831 | October 11, 2007 | Basu |
20070260996 | November 8, 2007 | Jakobson |
20070271248 | November 22, 2007 | Albernoz et al. |
20070271502 | November 22, 2007 | Bedi et al. |
20080016091 | January 17, 2008 | Chandra |
20080034018 | February 7, 2008 | Cisler et al. |
20080059539 | March 6, 2008 | Chin et al. |
20080072135 | March 20, 2008 | Cragun et al. |
20080103877 | May 1, 2008 | Gerken |
20080141126 | June 12, 2008 | Johnson et al. |
20080209361 | August 28, 2008 | Nickerson et al. |
20080250329 | October 9, 2008 | Stefix et al. |
20080250332 | October 9, 2008 | Farrell et al. |
20090097815 | April 16, 2009 | Lahr et al. |
20090157811 | June 18, 2009 | Bailor et al. |
20090235155 | September 17, 2009 | Ueda |
20100145947 | June 10, 2010 | Kolman et al. |
20130198622 | August 1, 2013 | Kraley |
20140032502 | January 30, 2014 | Kraley |
20140032633 | January 30, 2014 | Kleppner |
20140033013 | January 30, 2014 | Shaver |
20140033015 | January 30, 2014 | Shaver |
20140033099 | January 30, 2014 | Treitman et al. |
0932108 | July 1999 | EP |
- “U.S. Appl. No. 12/119,421, Non Final Office Action mailed Apr. 15, 2013”, 23 pgs.
- “U.S. Appl. No. 12/119,350, Response filed Dec. 26, 2012 to Final Office Action mailed May 12, 2010”, 11 pgs.
- “U.S. Appl. No. 12/119,397 , Response filed Feb. 15, 2013 to Non Final Office Action mailed Oct. 16, 2012”, 10 pgs.
- “U.S. Appl. No. 12/119,397, Final Office Action mailed Jun. 7, 2013”, 21 pgs.
- “U.S. Appl. No. 12/119,397, Response filed Oct. 7, 2013 to Final Office Action mailed Jun. 7, 2013”, 12 pgs.
- “U.S. Appl. No. 12/119,421, Examiner Interview Summary mailed Jan. 6, 2014”, 3 pgs.
- “U.S. Appl. No. 12/119,421, Examiner Interview Summary mailed Aug. 6, 2013”, 3 pgs.
- “U.S. Appl. No. 12/119,421, Final Office Action mailed Nov. 14, 2013”, 23 pgs.
- “U.S. Appl. No. 12/119,421, Response filed Jul. 11, 2013 to Non Final Office Action mailed Apr. 15, 2013”, 12 pgs.
- “U.S. Appl. No. 13/794,079, Non Final Office Action mailed Dec. 13, 2013”, 7 pgs.
- Wiley, John, “Microsoft® Word 2007 Bible by Herb Tyson Publisher”, (Mar. 12, 2007), pgs. 797-800.
- “Adobe to Acquire Virtual Ubiquity”, The Buzzword Blog Building the first real word processor for the web, [Online] Retrieved from the internet: <URL:http://blog.buzzword.com/vu/index.php?paged=2>, (Oct. 1, 2007), 10 pgs.
- “U.S. Appl. No. 12/119,249, Examiner Interview Summary mailed Oct. 5, 2010”, 3 pgs.
- “U.S. Appl. No. 12/119,249, Final Office Action mailed Jun. 9, 2011”, 15 pgs.
- “U.S. Appl. No. 12/119,249, Non Final Office Action mailed Dec. 23, 2010”, 11 pgs.
- “U.S. Appl. No. 12/119,249, Response filed Mar. 23, 2011 to Non Final Office Action mailed Dec. 23, 2010”, 10 pgs.
- “U.S. Appl. No. 12/119,249, Response filed Oct. 10, 2011 to Final Office Action mailed Jun. 9, 2011”, 9 pgs.
- “U.S. Appl. No. 12/119,335, Non-Final Office Action mailed Sep. 1, 2010”, 8 pgs.
- “U.S. Appl. No. 12/119,335, Notice of Allowance mailed Jan. 13, 2011”, 4 pgs.
- “U.S. Appl. No. 12/119,335, Response filed Dec. 1, 2010 to Non Final Office Action mailed Sep. 1, 2010”, 12 pgs.
- “U.S. Appl. No. 12/119,350, Advisory Action mailed Aug. 4, 2010”, 3 pgs.
- “U.S. Appl. No. 12/119,350, Appeal Brief filed Oct. 28, 2010”, 25 pgs.
- “U.S. Appl. No. 12/119,350, Decision on Appeal mailed Oct. 25, 2012”, 5 pgs.
- “U.S. Appl. No. 12/119,350, Decision on Pre-Appeal Brief Request mailed Aug. 28, 2010”, 2 pgs.
- “U.S. Appl. No. 12/119,350, Examiner's Answer to Appeal Brief mailed Nov. 29, 2010”, 15 pgs.
- “U.S. Appl. No. 12/119,350, Final Office Action mailed May 12, 2010”, 14 pgs.
- “U.S. Appl. No. 12/119,350, Non-Final Office Action mailed Oct. 16, 2009”, 11 pgs.
- “U.S. Appl. No. 12/119,350, Pre-Appeal Brief Request filed Aug. 12, 2010”, 5 pgs.
- “U.S. Appl. No. 12/119,350, Response filed Jan. 19, 2010 to Non-Final Office Action mailed Oct. 16, 2009”, 11 pgs.
- “U.S. Appl. No. 12/119,350, Response filed Jul. 12, 2010 to Final Office Action mailed May 12, 2010”, 10 pgs.
- “U.S. Appl. No. 12/119,397, Appeal Brief filed May 23, 2012”, 17 pgs.
- “U.S. Appl. No. 12/119,397, Final Office Action mailed Oct. 28, 2011”, 18 pgs.
- “U.S. Appl. No. 12/119,397, Non Final Office Action mailed Jun. 23, 2011”, 20 pgs.
- “U.S. Appl. No. 12/119,397, Non Final Office Action mailed Oct. 16, 2012”, 20 pgs.
- “U.S. Appl. No. 12/119,397, Response filed Aug. 10, 2011 to Non Final Office Action mailed Jun. 23, 2011”, 9 pgs.
- “U.S. Appl. No. 12/119,407, 312 Amendment filed Apr. 11, 2011”, 3 pgs.
- “U.S. Appl. No. 12/119,407, Non-Final Office Action mailed Sep. 9, 2010”, 12 pgs.
- “U.S. Appl. No. 12/119,407, Notice of Allowance mailed Feb. 18, 2011”, 7 pgs.
- “U.S. Appl. No. 12/119,407, PTO Response to 312 Amendment mailed Apr. 15, 2011”, 2 pgs.
- “U.S. Appl. No. 12/119,407, Response filed Dec. 9, 2010 to Non Final Office Action mailed Sep. 9, 2010”, 17 pgs.
- “U.S. Appl. No. 12/119,421, Appeal Brief filed Jul. 27, 2012”, 25 pgs.
- “U.S. Appl. No. 12/119,421, Advisory Action mailed Mar. 22, 2011”, 3 pgs.
- “U.S. Appl. No. 12/119,421, Examiner Interview Summary mailed Jan. 31, 2012”, 3 pgs.
- “U.S. Appl. No. 12/119,421, Final Office Action mailed Jan. 13, 2011”, 27 pgs.
- “U.S. Appl. No. 12/119,421, Final Office Action mailed Feb. 29, 2012”, 31 pgs.
- “U.S. Appl. No. 12/119,421, Non Final Office Action mailed Oct. 18, 2011”, 29 pgs.
- “U.S. Appl. No. 12/119,421, Non-Final Office Action mailed Sep. 14, 2010”, 22 pgs.
- “U.S. Appl. No. 12/119,421, Response filed Jan. 18, 2012 to Non Final Office Action mailed Oct. 18, 2011”, 15 pgs.
- “U.S. Appl. No. 12/119,421, Response filed Mar. 3, 2011 to Final Office Action mailed Jan. 13, 2011”, 13 pgs.
- “U.S. Appl. No. 12/119,421, Response filed May 12, 2011 to Advisory Action mailed Mar. 22, 2011”, 15 pgs.
- “U.S. Appl. No. 12/119,421, Response filed Nov. 23, 2010 to Non-Final Office Action mailed Sep. 14, 2010”, 14 pgs.
- “U.S. Appl. No. 12/119,425, Appeal Brief filed Mar. 22, 2012”, 16 pgs.
- “U.S. Appl. No. 12/119,425, Examiner's Answer mailed Jul. 6, 2012”, 24 pgs.
- “U.S. Appl. No. 12/119,425, Final Office Action mailed Aug. 19, 2011”, 18 pgs.
- “U.S. Appl. No. 12/119,425, Non-Final Office Action mailed Mar. 1, 2011”, 17 pgs.
- “U.S. Appl. No. 12/119,425, Response filed Jun. 1, 2011 to Non Final Office Action mailed Mar. 1, 2011”, 17 pgs.
- “U.S. Appl. No. 13/081,236, Non Final Office Action mailed Jan. 24, 2012”, 10 pgs.
- “U.S. Appl. No. 13/081,236, Notice of Allowance mailed Jun. 14, 2012”, 9 pgs.
- “U.S. Appl. No. 13/081,236, Response filed Apr. 24, 2012 to Non Final Office Action mailed Jan. 24, 2012”, 12 pgs.
- “U.S. Appl. No. 13/081,267, Non Final Office Action mailed Jul. 13, 2012”, 6 pgs.
- “U.S. Appl. No. 13/081,267, Notice of Allowance mailed Nov. 9, 2012”, 5 pgs.
- “U.S. Appl. No. 13/081,267, Response filed Oct. 10, 2012 to Non-Final Office Action mailed Jul. 13, 2012”, 8 pgs.
- “Comparison of office suites”, Comparison of office suites—Wikipedia, the free encyclopedia, [Online] Retrieved from the internet: <URL:http://en.wikipedia.org/wiki/List—of—office—suites>, (Mar. 16, 2008), 4 pgs.
- “Forthcoming Functionality”, The Buzzword Blog Building the first real word processor for the web, [Online] Retrieved from the internet: <URL:http://blog.buzzword.com/vu/index.php?paged=3>, (Jul. 15, 2007), 10 pgs.
- “Google Docs”, Google Docs—Wikipedia, the free encyclopedia, [Online]. Retrieved from the Internet: <URL:http://en.wikipedia.org/wiki/Google—Docs>, (Mar. 16, 2008), 3 pages.
- “List of word processors”, From Wikipedia, the free encyclopedia The following is a list of word processors, [Online] Retrieved from the internet: <URL:http://en.wikipedia.org/wiki/List—of—word—processors>, (Mar. 16, 2008), 4 pgs.
- “The Buzzword Blog Building the first real word processor for the web”, Buzzword vs Google docs, [Online] Retrieved from the Internet: <URL:http://blog.virtub.com/>, (Mar. 12, 2008), 13 pages.
- “ThinkFree Docs :: Search, Share & Publish documents Page”, [Online] Retrieved from the internet: <URL:http://www.thinkfreedocs.com/, (Mar. 16, 2008), 1 page.
- “ThinkFree Docs::Search, Share & Publish documents”, FAQ [Online]. Retrieved from the Internet: <URL:http://www.thinkfreedocs.com/about/faq.html>, (Mar. 16, 2008), 1 page.
- “ThinkFree Office by Haansoft Corporation”, From Wikipedia, the free encyclopedia (Redirected from ThinkFree), [Online] Retrieved from the internet: <URL:http://en.wikipedia.org/wiki/ThinkFree>, (Nov. 7, 2006), 3 pgs.
- “Working with Collaborators: Real time collaboration”, Google Docs Help Center [Online]. Retrieved from the Internet: <URL:http://documents.google.com/support/bin/answer.py?answer=40971&topic=8628>, (Mar. 16, 2008), 2 pages.
- “Working with Collaborators: Simultaneous editing and viewing”, Google Docs Help Center [Online]. Retrieved from the internet: <URL:http://documents.google.com/support/bin/answer.py?answer=44680&topic=8628>, (Mar. 16, 2008), 2 pages.
- “ZCubes”, From Wikipedia, the free encyclopedia, [Online] Retrieved from the internet: <URL:http://en.wikipedia.org/wiki/ZCubes>, (Sep. 30, 2007), 5 pages.
- “Zoho Office Suite”, [Online] Retrieved from the interent: <URL:http://en.wikipedia.org/wiki/Zoho—Writer> From Wikipedia, the free encyclopedia (Redirected from Zoho Writer) Developed by AdventNet Inc. <URL:http://www.zoho.com>, (Mar. 16, 2008), 5 pgs.
- Agarwal, Deborah, et al., “Supporting collaborative computing and interaction”, Lawrence Berkeley National Laboratory, (May 22, 2002), 6 pgs.
- Descy, Don E, “Browser-Based Online Applications: Something for Everyone!”, TechTrends: Linking Research and Practice to Improve Learning, 51(2), (Mar. 2007), 3-5.
- Shen, H., “Integrating Advanced Collaborative Capabilities into Web-Based Word Processors”, Lecture Notes in Computer Science, 4674, (2007), 1-8.
- Simsarian, Kristian, et al., “Shared Spatial Desktop Development”, Kungl Tekniska Hogskolan Royal Institute of Technology Numerical Analysis and Computing Science. CID-86, KTH, Stockholm, Sweden 1999, Report No. CID-86 ISSN No. ISSN 1403-073X Reports can be ordered from: URL: http://www.nada.kth.se/cid/, (Aug. 1999), 103 pages.
- U.S. Appl. No. 12/119,421, Advisory Action mailed Mar. 7, 2014, 3 pgs.
- U.S. Appl. No. 12/119,421, Response filed Feb. 14, 2014 to Final Office Action mailed Nov. 14, 2013, 10 pgs.
- U.S. Appl. No. 12/119,421, Response filed Mar. 31, 2014 to Advisory Action mailed Mar. 7, 2014, 11 pgs.
- U.S. Appl. No. 13/794,079, Response filed Mar. 6, 2014 to Non Final Office Action mailed Dec. 13, 2013, 10 pgs.
Type: Grant
Filed: Sep 12, 2012
Date of Patent: Jul 1, 2014
Patent Publication Number: 20130006919
Assignee: Adobe Systems Incorporated (San Jose, CA)
Inventors: Robert Shaver (Watertown, MA), Paul Kleppner (Lexington, MA)
Primary Examiner: Uyen Le
Application Number: 13/612,549
International Classification: G06F 7/00 (20060101); G06F 17/00 (20060101);