A 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.
The 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. As part of creating and editing electronic content (e.g., an electronic document), different types of lists are created, modified, and deleted.
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:
In some example embodiments, methods, apparatus and systems enable managing paragraphs associated with items in a list. The list, in turn, may form part of selected electronic content. The detailed application of the various methods, apparatus, and systems will be described after certain terms are defined.
As used herein, “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 XML document), a fillable form or data describing application graphical user interface, etc.
As used herein, the term “continuity” relative to items in a list of electronic content may comprise any type consistency or continuation regarding any type of characteristic, parameter, etc. associated with items in a list. There may be continuity between items of different types of lists (ordered, unordered, etc.). For ordered lists, continuity between items may include an ordering (e.g., ascending, descending, etc.) relative to numbering, lettering, etc. For unordered lists, continuity between items may include consistency with respect to the use of bullets, dashes, etc. to demarcate a new item (as further described below). Continuity between items may also include the same type of format (e.g., a format style, which may be characterized by spacing, tabs, font, indentation, etc.).
Some example embodiments enable a creator or editor of a list forming a portion of electronic content to associate multiple paragraphs with the same item in a list. In conventional approaches, there is generally a one-to-one relationship between an item in a list and a paragraph. In contrast, in some example embodiments, there may be a one-to-N relationship between an item in a list and a paragraph, wherein N is greater than one. Accordingly, if a creator or editor of a list would like to include a large amount of data for an item in the list, the creator or editor may want to separate such data into multiple paragraphs.
Example embodiments may provide certain benefits, including the avoidance of cumbersome, error-prone workarounds that include the creation of two separate lists in response to positioning a separate paragraph below an item included in a first list. That is, in order to maintain order continuity (such as ascending numbering, lettering, etc.) between the items in the list, and a paragraph appended to the first list, a second list is typically started below the separate paragraph. The first item in this second list is ordered to begin where the last item in the first list ends. For example, if the last item (prior to adding a separate paragraph to the end of the first list) in the first list was number 15, the first item in the second list (after the separate paragraph is added) would start at number 16. Such approaches are cumbersome and subject to errors when items are added or deleted from one of the two resulting lists. For example, if an item is deleted from the first list, the user is usually required to update the numbering in the second list.
In some example embodiments, a Graphical User Interface (GUI) application may be presented for creating and editing of items in a list. In some example embodiments, the GUI application comprises a toggle button to convert an item in a list to a separate paragraph and vice versa.
For example, assume that a list comprises three items. If the cursor of the GUI application is positioned at the second item, the second item is converted into a separate paragraph that is then associated with the first item. In some example embodiments, the formatting between the first item and the separate paragraph is maintained. For example, the first item and the separate paragraph may have a same indentation, same font, etc. Thus, the first item may be used to set formatting for the second item, or the second item may be used to set formatting for the first item, depending on the user.
Moreover, continuity can be maintained between the first item and the third item. For example, if the list included ascending numbered items, after the second item was converted to a separate paragraph, the number for the third item would change from three to two. Accordingly, one list may be created wherein any or all of the items in the list may include any number of paragraphs. Some example embodiments are applicable to any type of list (e.g., ordered list, unordered list, etc.). Examples of ordered lists may include items that are in numeric order, alphabetical order, etc. Examples of unordered lists may include items that are delineated using bullets, dashes, etc.
The application module 102 may be software, hardware, firmware or a combination thereof for executing instructions to accomplish any of the operations described herein, including all of the methods disclosed herein, according to some example embodiments. The machine-readable medium may include 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.). While shown as being in a same system, in some example embodiments, the application module 102 and the machine-readable medium 112 may be in separate systems. For example, the application module 102 and the machine-readable medium 112 may reside on a client device and a server device, respectively. Accordingly, the application module 102 may retrieve the content 114 over a network that couples together the client device and the server device.
As further described below, the application module 102 may present a GUI application that is used by a creator or editor of the content 114. For example, the GUI application may comprise an application for word processing, creating slide presentations, or editing spreadsheets, etc.
Operations, according to example embodiments, are now described. In certain embodiments, the operations are performed by executing instructions residing on machine-readable media (e.g., software), while in other embodiments, the methods are performed by hardware or other logic (e.g., digital logic). In some cases, the methods are performed using a combination of these approaches.
At block 202, the application module 104 presents content 114 to a user by way of a GUI application. The GUI application may have an item toggle button for converting items to separate paragraphs associated with another item and vice versa.
Upon selection, the unordered list button 306 causes the text on the line where the cursor is currently positioned to take the form of an item in an unordered list (e.g., using bullet, dashes, etc.). Upon selection, the ordered list button 308 causes the text on the line where the cursor is currently positioned to take the form of an item in an ordered list (e.g., numeric, alphabetic, etc.). Upon selection, the item toggle button 310 causes the text on the line where the cursor is currently positioned to take the form of a separate paragraph (assuming that the text where the cursor was positioned, prior to activating the item toggle button 310, was part of an item in a list). Alternatively, upon selection, the item toggle button 310 causes the text on the line where the cursor is currently positioned to take the form of an item in a list (assuming that the text where the cursor was positioned, prior to activating the toggle button 310, was part of a separate paragraph). Thus, the item toggle button 310 enables the user to easily convert portions of text between having the appearance of an item in a list, or having the appearance of a separate paragraph. In some example embodiments, if the text is converted from an item in a list to a separate paragraph and if there is an item in the list positioned above the converted text, the separate paragraph becomes a part of or associated with the item positioned above the converted text. In some example embodiments, as mentioned previously, the formatting (e.g., format style) between the first item and the separate paragraph is maintained. For example, the first item and the separate paragraph may have a same indentation, same font, etc. This particular example is described in more detail below. Returning now to
At block 204, the application module 104 receives user input to create a first item and a second item in a list. The list may be ordered or unordered. A user may use a GUI application (as shown in
At block 206, the application module 104 creates the first item and the second item in the list (which in most embodiments includes continuity between the listed items). The application module 104 may update the electronic content that includes the first item and the second item, and update the display showing such content. To illustrate,
The screenshot 400 illustrates a word processing application 402 wherein an electronic document 404 is being edited. The word processing application 402 includes a list menu 405. The list menu 405 includes an unordered list button 406, an ordered list button 408 and an item toggle button 410 (as described above with respect to the description of
The list 420 may comprise a number of types, including and ordered list, an unordered list, etc. Furthermore, the first item 422 and the second item 424 may have continuity. Continuity between the items 422, 424 may include order (e.g., ascending, descending, etc.) relative to the numbering, lettering, etc. Continuity may also include the format (e.g., format style, and/or spacing, tabs, font, indentation, etc.). For example, the first item 422 and the second item 424 include a numerical ascending order (1, 2, etc.), the same format (e.g., spacing between the numbers and the text, the same font, the same amount of indentation, etc.). Returning now to
At block 208, the application module 104 receives a user selection of the item toggle button (e.g., as part of a GUI) while a cursor is positioned within the second item in the list. With reference to the example in
At block 210, the application module 104 converts the second item into a separate paragraph that is associated with the first item in the list. In some example embodiments, this conversion is in response to the user selection of the item toggle button. In some example embodiments, the formatting between the first item and the newly-added, but separate paragraph is maintained. For example, the first item and the separate paragraph may have the same indentation, same font, etc. The application module 104 may update the electronic content with the conversion of the second item and update the display to show this conversion.
To illustrate,
At block 212, the application module 104 receives user input to create a new second item in the list. In this example, the new second item of the list is created below the first item (also below the separate paragraph that now exists as part of the first item). A user may use a GUI application (as shown in
At block 214, the application module 104 creates the new second item in the list. The new second item remains a part of the same list as the first item. In some example embodiments, there is continuity between the first item and the new second item in the list. In some example embodiments, some or all of the continuity is not maintained relative to the previous second item (the separate paragraph that is part of the first item). To illustrate,
The screenshot 600 also illustrates the view after the application module 104 has created a new second item 626 in a list 620. As shown, the new second item 626 is positioned below the last of multiple paragraphs of a first item 622 (that includes at least a second paragraph). In some example embodiments, there is continuity between the first item 622 and the new second item 626. In this example, continuity between the first item 622 and the new second item 626 includes numerical order (1, 2, . . . ). This continuity also includes the same format (e.g., spacing between the numbers and the text, the same font, the same indentation, etc.).
Thus, as described, the user may enter commands to create items in a list, to change an item in a list to a separate paragraph and vice versa. For example, the user may select the ordered list button 608 to format text as items in a list. The application module 104 may create a first item in the list based on text received from a user. This first item includes a first ordered item demarcation that is adjacent to the received text. For example, for an ordered list, the demarcation may include numbers or letters. After the user selects return to begin entering text on the next line, the application module 104 may receive a command to suppress presentation of an ordered item demarcation. For example, the user may select the item toggle button 610. Thus, the application module 104 creates a separate paragraph below the first item based on received text. As shown by the second paragraph in
At block 216, the application module 104 stores the electronic content in a machine-readable medium. The application module 104 may store updates to the electronic content (as described above) in the machine-readable medium 112 as well. This storage activity may be in response to a user-invoked save action, auto-save activity, etc. The operations of the flow diagram 200 are complete.
Some example embodiments are not limited to the order, the type or the number of operations as set forth for the method 200. As described for the method 200, there are operations for creating items in a list, converting an item to a separate paragraph, etc. In some example embodiments, additional items may be created in the list, additional conversions of items to separate paragraphs may occur, and items may be converted from a separate paragraph back to an item in a list, etc. Still more embodiments may be realized.
For example, a detailed block diagram of an example computer environment, according to some embodiments, is now described. In particular,
As illustrated in
The memory unit 730 may store data and/or instructions, and may comprise any suitable memory, such as a dynamic random access memory (DRAM). The computer system 700 also includes IDE drive(s) 708 and/or other suitable storage devices. A graphics controller 704 controls the display of information on a display device 706, according to some embodiments of the invention.
The input/output controller hub (ICH) 724 provides an interface to I/O devices or peripheral components for the computer system 700. The ICH 724 may comprise any suitable interface controller to provide for any suitable communication link to the processor(s) 702, memory unit 730 and/or to any suitable device or component in communication with the ICH 724. For one embodiment of the invention, the ICH 724 provides suitable arbitration and buffering for each interface.
For some embodiments of the invention, the ICH 724 provides an interface to one or more suitable integrated drive electronics (IDE) drives 708, 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 710. For one embodiment, the ICH 724 also provides an interface to a keyboard 712, a mouse 714, a CD-ROM drive 718, one or more suitable devices through one or more Firewire ports 716. For one embodiment of the invention, the ICH 724 also provides a network interface 720 though which the computer system 700 can communicate with other computers and/or devices.
In some embodiments, the computer system 700 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 730 and/or within the processor(s) 702.
Accordingly, if the apparatus, systems, and methods described herein are implemented, several benefits may accrue. These include facilitating the management of lists, whether ordered or unordered. Greater efficiency in document production may result.
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 a more 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.
This application is a continuation of U.S. application Ser. No. 12/119,407, filed May 12, 2008, now U.S. Pat. No. 7,945,595 which is incorporated in its entirety herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
4714992 | Gladney et al. | Dec 1987 | A |
4949300 | Christenson et al. | Aug 1990 | A |
5008853 | Bly et al. | Apr 1991 | A |
5014267 | Tompkins et al. | May 1991 | A |
5072412 | Henderson, Jr. et al. | Dec 1991 | A |
5220657 | Bly et al. | Jun 1993 | A |
5245553 | Tanenbaum | Sep 1993 | A |
5247615 | Mori et al. | Sep 1993 | A |
5293619 | Dean | Mar 1994 | A |
5339389 | Bates et al. | Aug 1994 | A |
5379374 | Ishizaki et al. | Jan 1995 | A |
5388196 | Pajak et al. | Feb 1995 | A |
5428729 | Chang et al. | Jun 1995 | A |
5446842 | Schaeffer et al. | Aug 1995 | A |
5471318 | Ahuja et al. | Nov 1995 | A |
5515491 | Bates et al. | May 1996 | A |
5608872 | Schwartz et al. | Mar 1997 | A |
5617539 | Ludwig et al. | Apr 1997 | A |
5664183 | Cirulli et al. | Sep 1997 | A |
5671428 | Muranaga et al. | Sep 1997 | A |
5732184 | Chao et al. | Mar 1998 | A |
5758079 | Ludwig et al. | May 1998 | A |
5764902 | Rothrock | Jun 1998 | A |
5778368 | Hogan et al. | Jul 1998 | A |
5787175 | Carter | Jul 1998 | A |
5835601 | Shimbo et al. | Nov 1998 | A |
5867654 | Ludwig et al. | Feb 1999 | A |
5907324 | Larson et al. | May 1999 | A |
5920694 | Carleton et al. | Jul 1999 | A |
5963208 | Dolan et al. | Oct 1999 | A |
5966512 | Bates et al. | Oct 1999 | A |
5978817 | Giannandrea et al. | Nov 1999 | A |
5995097 | Tokumine et al. | Nov 1999 | A |
6005568 | Simonoff et al. | Dec 1999 | A |
6005571 | Pachauri | Dec 1999 | A |
6088702 | Plantz et al. | Jul 2000 | A |
6243722 | Day | Jun 2001 | B1 |
6266683 | Yehuda et al. | Jul 2001 | B1 |
6314408 | Salas et al. | Nov 2001 | B1 |
6314425 | Serbinis et al. | Nov 2001 | B1 |
6342906 | Kumar et al. | Jan 2002 | B1 |
6366933 | Ball et al. | Apr 2002 | B1 |
6442748 | Bowman-Amuah et al. | Aug 2002 | B1 |
6446093 | Tabuchi | Sep 2002 | B2 |
6502113 | Crawford et al. | Dec 2002 | B1 |
6507845 | Cohen et al. | Jan 2003 | B1 |
6584466 | Serbinis et al. | Jun 2003 | B1 |
6632251 | Rutten et al. | Oct 2003 | B1 |
6643663 | Dabney et al. | Nov 2003 | B1 |
6701345 | Carley et al. | Mar 2004 | B1 |
6721921 | Altman | Apr 2004 | B1 |
6757871 | Sato et al. | Jun 2004 | B1 |
6772393 | Estrada et al. | Aug 2004 | B1 |
6816906 | Icken et al. | Nov 2004 | B1 |
6819806 | Kubota et al. | Nov 2004 | B1 |
6839878 | Icken et al. | Jan 2005 | B1 |
6865548 | Wiechers | Mar 2005 | B2 |
6865713 | Bates et al. | Mar 2005 | B1 |
6874124 | Murase et al. | Mar 2005 | B2 |
6889896 | Silverbrook et al. | May 2005 | B2 |
6894804 | Nguyen et al. | May 2005 | B2 |
6898601 | Amado et al. | May 2005 | B2 |
6901376 | Sculler et al. | May 2005 | B1 |
6918082 | Gross et al. | Jul 2005 | B1 |
6934721 | Schein | Aug 2005 | B2 |
6950828 | Shaw et al. | Sep 2005 | B2 |
6991154 | Silverbrook et al. | Jan 2006 | B2 |
7007232 | Ross et al. | Feb 2006 | B1 |
7028267 | Beezer et al. | Apr 2006 | B1 |
7044363 | Silverbrook et al. | May 2006 | B2 |
7051031 | Schein | May 2006 | B2 |
7062532 | Sweat et al. | Jun 2006 | B1 |
7146367 | Shutt | Dec 2006 | B2 |
7249314 | Walker et al. | Jul 2007 | B2 |
7263655 | Carden, Jr. | Aug 2007 | B1 |
7325186 | Jones et al. | Jan 2008 | B2 |
7392469 | Bailin | Jun 2008 | B1 |
7506262 | Gupta et al. | Mar 2009 | B2 |
7574669 | Braun et al. | Aug 2009 | B1 |
7587407 | Gruhl et al. | Sep 2009 | B2 |
7676759 | Carter | Mar 2010 | B2 |
7724249 | Horikawa et al. | May 2010 | B1 |
7769810 | Kaufman | Aug 2010 | B1 |
7904425 | Cannon et al. | Mar 2011 | B2 |
7945595 | Kraley | May 2011 | B1 |
7949633 | Shaver et al. | May 2011 | B1 |
7950064 | Chavez et al. | May 2011 | B2 |
8290902 | Shaver et al. | Oct 2012 | B1 |
20010043716 | Price et al. | Nov 2001 | A1 |
20020133628 | Asplund et al. | Sep 2002 | A1 |
20020163548 | Chiu et al. | Nov 2002 | A1 |
20020186252 | Himmel et al. | Dec 2002 | A1 |
20030214528 | Pierce et al. | Nov 2003 | A1 |
20040041843 | Cui et al. | Mar 2004 | A1 |
20040088331 | Therrien et al. | May 2004 | A1 |
20040172595 | Lerner et al. | Sep 2004 | A1 |
20050064858 | Makela et al. | Mar 2005 | A1 |
20050081159 | Gupta et al. | Apr 2005 | A1 |
20050193325 | Epstein | Sep 2005 | A1 |
20050262225 | Halpern et al. | Nov 2005 | A1 |
20060010382 | Ejiri et al. | Jan 2006 | A1 |
20060026502 | Dutta | Feb 2006 | A1 |
20060161578 | Siegel et al. | Jul 2006 | A1 |
20060184901 | Dietz | Aug 2006 | A1 |
20070118794 | Hollander et al. | May 2007 | A1 |
20070198616 | Goto | Aug 2007 | A1 |
20070239831 | Basu | Oct 2007 | A1 |
20070260996 | Jakobson | Nov 2007 | A1 |
20070271248 | Albernoz et al. | Nov 2007 | A1 |
20070271502 | Bedi et al. | Nov 2007 | A1 |
20080016091 | Chandra | Jan 2008 | A1 |
20080059539 | Chin et al. | Mar 2008 | A1 |
20080072135 | Cragun et al. | Mar 2008 | A1 |
20080103877 | Gerken | May 2008 | A1 |
20080209361 | Nickerson et al. | Aug 2008 | A1 |
20080250329 | Stefix et al. | Oct 2008 | A1 |
20080250332 | Farrell et al. | Oct 2008 | A1 |
20090097815 | Lahr et al. | Apr 2009 | A1 |
20090157811 | Bailor et al. | Jun 2009 | A1 |
20090235155 | Ueda | Sep 2009 | A1 |
20100145947 | Kolman et al. | Jun 2010 | A1 |
Entry |
---|
“U.S. Appl. No. 12/119,249, Final Office Action mailed Jun. 9, 2011”, 15 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, Response filed Aug. 10, 2011 to Non-Final Office Action mailed Jun. 23, 2011”, 9 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,425, Final Office Action mailed Aug. 19, 2011”, 18 pgs. |
“U.S. Appl. No. 12/119,425, Response filed Jun. 1, 2011 to Non-Final Office Action mailed Mar. 1, 2011”, 17 pgs. |
“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, 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,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, 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,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, Response filed Dec. 9, 2010 to Non-Final Office Action mailed Sep. 9, 2010”, 17 pgs. |
“U.S. Appl. No. 12/119,421, Advisory Action mailed Mar. 22, 2011”, 3. |
“U.S. Appl. No. 12/119,421, Final Office Action mailed Jan. 13, 2011”, 27 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 Mar. 3, 2011 to Final Office Action mailed Jan. 13, 2011”, 13 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, Non-Final Office Action mailed Mar. 1, 2011”, 17 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”, [Online]. Retrieved from the internet: <URL:http://www.thinkfreedocs.com/about/faq.html>, FAQ, (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”, [Online]. Retrieved from the internet: <URL:http://documents.google.com/support/bin/answer.py?answer=40971&topic=8628>, Google Docs Help Center, (Mar. 16, 2008), 2 pages. |
“Working with Collaborators: Simultaneous editing and viewing”, [Online]. Retrieved from the internet: <URL:http://documents.google.com/support/bin/answer.py?answer=44680&topic=8628>, Google Docs Help Center, (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”, From Wikipedia, the free encyclopedia (Redirected from Zoho Writer) Developed by AdventNet Inc. <URL:http://www.zoho.com>, [Online] Retrieved from the internet: <URL:http://en.wikipedia.org/wiki/Zoho—Writer>, (Mar. 16, 2008), 5 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,249, Examiner Interview Summary mailed Oct. 5, 2010”, 3 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,350, Appeal Brief filed Oct. 28, 2010”, 25 pgs. |
“U.S. Appl. No. 12/119,350, Decision on Pre-Appeal Brief Request mailed Sep. 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,397 , Appeal Brief filed May 23, 2010”, 17 pgs. |
“U.S. Appl. No. 12/119,397, Final Office Action mailed Oct. 28, 2010”, 18 pgs. |
“U.S. Appl. No. 12/119,407, 312 Amendment filed Apr. 11, 2011”, 3 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,421 , Appeal Brief filed Jul. 27, 2012”, 25 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, Response filed Jan. 18, 2012 to Non Final Office Action mailed Oct. 18, 2011”, 15 pgs. |
“U.S. Appl. No. 12/119,421. Examiner Interview Summary mailed Jan. 31, 2012”, 3 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. 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. |
Agarwal, Deborah, et al., “Supporting collaborative computing and interaction”, Lawrence Berkeley National Laboratory, (May 22, 2002), 6 pgs. |
Number | Date | Country | |
---|---|---|---|
Parent | 12119407 | May 2008 | US |
Child | 13081267 | US |