In many fields of endeavour, the content of electronic documents is viewed and reviewed. Such content includes text, drawings, audio recordings, video recordings, multimedia presentations, and the like. Large amounts of content are often viewed as part of a document divided into smaller portions, such as pages, where a scroll bar is used to navigate between the portions. Thus, to move from viewing the content on page one-hundred to viewing the content on page two-hundred, for example, the reviewer knows to move the scroll bar slider in one of two possible directions. However, other than this indication of direction, the reviewer often has no precise idea of where the slider should be placed in the trough to view the desired page. Thus, when reviewing documents with more than a few pages, the reviewer often resorts to locating the slider in the trough by trial and error, eventually encountering the proper location to select a particular page for review.
Some embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings in which:
The inventors have determined that using a segmented scroll bar with a dynamically compressible trough can reduce or even eliminate trial and error as a mechanism for navigating to a specific page in a variety of documents.
For the purposes of this specification, the term “absolute location” within a document refers to a specific page number, paragraph number, column and/or line number, word number, or any other position of text within a document that can be directly referenced using a numeric or symbolic descriptor.
“Electronic content” includes any digital data that may be presented to a user (e.g., visually or audibly presented), such as an electronic document, page-descriptive electronic content including that contained in a page-descriptive electronic document, a media stream, a web page, a hypertext document, an image, digital video or a video recording, digital audio or an audio recording, animation, a markup language document, such as a HyperText Markup Language (HTML) or eXtensible Markup Language (XML) document, a form having blank components to accept entered data, or data describing the application of a GUI.
A “content element” includes any part of electronic content that is defined or discernable as a part. For example, a content element may be automatically discerned from a characteristic of the content element itself (e.g., a paragraph of an electronic document, or a file format designation) or may be manually defined by a user (e.g., a user-selected collection of words in an electronic document, a user-selected portion of a digital image). Examples of content elements include portions of a page-descriptive document or other electronic document, such as pieces of electronic text or other material within an electronic document, dynamic content in the form of portions of media streams, such as sections of digital video or frames or sets of frames of digital video or digital audio, dynamic content in the form of segments or frames of animations, electronic forms, form templates, form elements, form data, actuatable element specifications or executable instructions, and various elements presentable or accessible by users within electronic content, including instances of scripted and non-scripted dynamic content and the like.
A “dynamically compressible trough” has individual segments that represent one or more portions of the displayed electronic content, such as content included in an electronic document. For example, the portions might correspond to pages or paragraphs in the document. The segment length is determined according to both the length of the content (e.g., in pages) and the height of the scroll bar relative to the height of visible indicators in the trough. As the number of represented content portions per segment increases, the visible indicators in the trough are displayed in an alternating (e.g., 1, 3, 5, 7, etc.) format, instead of a strictly sequential (e.g., 1, 2, 3, 4, etc.) format, so that the indicated segments represent the compression of an increasing number of the portions into each segment.
The term “rendering” used as a verb includes presenting or making accessible electronic content or content elements to be perceived, viewed, or otherwise experienced by a user, or made available for further processing, such as, for example, searching, digesting, printing, analyzing, distilling, or transforming by computational processes that may not include processing the intrinsic data structure describing the electronic content or content element.
The term “rendering” used as a noun includes human-perceivable representations of data that is within a machine and perception-specialized organizations of data defining such representations. For example, a rendering may include a pattern of human-perceivable matter or energy presented on an output device (e.g., a display) by a machine, as well as the organization of data within a machine that defines such patterns. For example, such organizations of data may include the electronic configuration of a memory used by a graphics display processor, or a file containing an audio segment suitable for playing via an audio system of a computer.
The term “rendering module” may be taken to include systems, applications, and mechanisms for rendering or presenting electronic content to a user, including the presentation of content elements such as text, graphics, form element renderings, scroll bars, and other electronic content elements. An example of a rendering module includes a web browser component (e.g., Microsoft Internet Explorer) or some other component to render electronic content such as HTML pages. Another example of a rendering module includes the ADOBE® ACROBAT® electronic publishing program.
The term “rendering program” includes applications for rendering or presenting dynamic content to a user. An example of a rendering program is the ADOBE® FLASH® Player 9 runtime software application, as well as the Microsoft® Silverlight™ browser plug-in. In many embodiments, a rendering module interacts with a rendering program to render dynamic content. In some embodiments, a rendering module includes a rendering program.
A “segment” is a portion of the scroll bar trough that can be delimited using a segment division indicator, which comprises any kind of visible mark, including a horizontal line segment. In some embodiments, segments are delimited invisibly. This can occur, for example, when a displayed document has enough pages that the visible indicators are displayed in an alternating, and not strictly continuous, sequence.
“Visible indicators” comprise number, letters, or other symbols located in the trough. The visible indicators serve to indicate, relative to one another, the distance in the trough between portions of the displayed electronic content. For example, in many embodiments, the visible indicators also serve as page numbers of a displayed document. In this case, the visible indicators serve to indicate “absolute locations” within a document.
It is common for one or more users (e.g., viewer, reviewers, editors, or other actors, such as automated processes) to view, review, and revise electronic content 116. In some embodiments, a review may be carried out by one person or by a team including multiple persons.
When viewing, reviewing, or revising, a user may start up an application (e.g., a rendering program forming part of a rendering module) to render or otherwise present the electronic content 116 to the user. This electronic content may take a variety of forms such as an electronic document, an audio file, video file, sequence of images, dynamic content, combinations thereof, and other forms of electronic content.
During the course of this activity, the user may be presented with a rendering of various content elements (e.g., using an output device, such as a display) included in or otherwise associated with the electronic content 116. In some embodiments, these content elements may be presented in a sequential order so as to indicate their positions or interrelationships within the electronic content, or for ease of user perception.
Various types of content elements contained within electronic content 116 may be presented to a user on an output device in various ways according to the nature of the content elements and/or the preferences of users. For example, electronic content 116 representing an electronic document may be presented on a display screen in the form of renderings of pages as they might appear if the electronic document were to be printed out. In some such embodiments, a user input device (e.g., a mouse, keyboard, touch screen, touch pad, voice input, etc.) is used to explore the electronic content 116. The rendering application may provide such affordances as scroll bars 102, fast forward/reverse scan buttons, or other GUI elements to be manipulated by the user to carry out document exploration, including viewing, reviewing, and editing functions.
The scroll bar 102 in most embodiments comprises a dynamically compressible trough 104 divided into a plurality of segments 106. The trough 104 includes visible indicators 108, and segment division indicators 112 (which may be visible as shown in
The content 116 displayed via the GUI 100 can be navigated using a slider 120 in the trough 104. The slider 120 can be dragged up and down in the trough (assuming the trough 104 is displayed vertically, as shown in
The location of the slider 120 in the trough 104 can be manipulated as a result of commands received from actuating a user input device, such as a mouse, to point to the slider 120 (e.g., with a GUI pointer 126). If the user opts to select the slider 120, such as by pointing to the slider 120, and then clicking and holding a button on a mouse, the slider 120 can be moved to a new location in the trough 104. The slider 120 can also be moved in the trough 104 by using a keyboard with up arrow/down arrow keys, or Page Up/Page Down keys, or by using a mouse or other user input device to select (e.g., “click”) on the up/down arrows 130, 132 at each end of the trough 104. In addition, the user may go directly to a specific page by selecting (e.g., clicking) on or near one of the visible indicators that corresponds to that page.
The size of the slider 120 (e.g., its length in the trough 104) may correspond with the amount of content 116 that is displayed. For example, if the slide 120 covers visible indicators representing pages 1-3 of a document, then the GUI 100 may operate to render on a user display that is visible to the user at least a portion of pages 1-3 of the document. In many embodiments, the slider 120 is translucent, so that visible indicators 108 covered by the slider 120 are still visible.
At a certain point, the segment division indicators become invisible (as in
One example mechanism to determine how many portions, such as pages, should be indicated per segment includes the following activity:
(a) calculate the average number of pixels available per segment (Papps) by dividing the pixel height of the trough 104 by the number of portions (e.g., pages) of the content;
(b) calculate the minimum number of pixels needed per segment (Pmpps) by adding the height of the visible indicator to be displayed, in pixels, to the desired pixel height of the space above and below the indicator; and
(c) calculate the amount of compression in the dynamically compressible trough by determining the number of portions (e.g., pages) per segment (PPS) as follows: if Papps≧Pmpps, then PPS=1; otherwise PPS=ceil(Pmpps/Papps), where “ceil” is equivalent to the JAVA programming language ceiling function, which operates to round up the argument given to the nearest integer. Those of ordinary skill in the art may also call this type of operation “ceiled” or “covered quotient” division.
Thus, if PPS=2, then the page numbers of a document could be displayed in the trough 104 as 1, 3, 5, 7, etc. If PPS=3, then the pages numbers of a document could be displayed in the trough 104 as 1, 4, 7, 10, etc. If PPS=3, then the pages numbers of a document could be displayed in the trough 104 as 1, 5, 9, 13, etc. And so on. Thus many embodiments may be realized.
For example,
Thus, in some embodiments, a method 311 of displaying a segmented scroll bar may begin at block 319 with displaying electronic content as part of a GUI. The electronic content may comprise a document, text, drawings, audio recordings, video recordings, multimedia presentations, etc. Any documents may be organized according to a page descriptive format, which includes a portable document format, where “portable document format” means a device-independent and display resolution-independent fixed-layout document format, including the text and fonts, images, and graphic paths associated with the document. The format may comprise a representation of a two-dimensional document, or a three-dimensional document. An example of a commercially available portable document format (PDF) is the format described in “PDF Reference”, sixth edition, ADOBE® Portable Document Format, Version 1.7, November 2006. Another example is defined by the Microsoft® XML Paper Specification (XPS), Version 1.0, 2006.
The method 311 may continue at block 323 with displaying a scroll bar having a dynamically compressible trough as part of the GUI. The trough comprises segments corresponding to portions of the electronic content, and some or all of the segments may include visible indicators of absolute locations of the corresponding the portions within the electronic content.
In some embodiments, the method 311 may include displaying a translucent slider in the trough at block 327, wherein the visible indicators remain visible even when the translucent slider is displayed on top of the visible indicators.
If no command is received to move the slider in the trough at block 333, then the method 311 may including returning to block 319. However, if it is determined at block 333 that the method 311 includes receiving a command to move the slider in the trough to a selected one of the segments, then the method 311 may include, at block 339, displaying a selected one of the portions (e.g., part or all of a page) of the electronic content corresponding to the selected segment. As noted previously, the visible indicators may comprise numeric indicators (e.g., representing page numbers or other numbered items), non-numeric indicators, alphabetic indicators, and symbolic indicators (e.g., combinations of numeric and non-numeric indicators to operate as paragraph indicators, chapter indicators, figure or drawing indicators, index location indicators, etc.).
In some embodiments, the method 311 includes, at block 343, changing the color of one or more of the segments selected by a first activity with respect to the segments (e.g., using a mouse to hover the screen pointer over a segment) to indicate the next portion of the electronic content to be displayed if the segment is selected by a second activity (e.g., a mouse click to actually select the segment). Thus, the method 311 may include receiving a segment selection at block 347. Changing the color of a segment might include changing the hue of a segment, as well as simply displaying the segment as opaque, or as a different shade of gray, such as when a more basic black-on-white display environment is used.
The method 311 may go on to include, at block 351, displaying the number of pages corresponding to the number of the segments covered by a slider in the trough, as noted previously. In some embodiments, the total number of document pages may be displayed as the last of the visible indicators in the trough (e.g., page number “59” would be the last number displayed in the trough 104 of
For example,
In some embodiments, a method 411 of displaying a segmented scroll bar may begin at block 419 with receiving a first command, perhaps at a server device, to display at least part of a selected one of several portions of an electronic document (e.g., if the portions equate to document pages, then at least part of a page will be displayed). The selected portion can be indicated by a visible indicator in a selected segment of a dynamically compressible trough in a segmented scroll bar.
In many embodiments, a vertically-oriented display will be used. That is, as shown in
Thus, if it is determined that there has been a request for a horizontally-oriented display at block 423, then the method 411 may include preparing for display, at block 427, and eventually displaying the trough in a substantially horizontal position proximate to the lower side of the portion of content selected for display. Actual display may occur subsequently to the activity of block 435, which may include the action of sending a second command (e.g., from a server device to a client device) to display the selected portion as part of a document page having a page number corresponding to the visible indicator in the selected segment.
Here, as noted previously, the trough comprises segments corresponding to the portions of the document. It should be noted that the display commands described herein can be sent and received within a server, within a client, or between a server and a client. If there is no request for a horizontal display, as determined at block 423, the method 411 may include preparing for display, at block 431, and eventually displaying the trough in a substantially vertical position proximate to the right-hand side of the selected portion of the document as part of the GUI. Prior to display, the method 411 may go on to include receiving the second command at block 439, perhaps at a client device.
In most embodiments, the method 411 includes displaying the selected portion of the document on a display, perhaps forming a part of a client device, at block 443. The segmented scroll bar is also displayed, and in some embodiments, one or more of the segments have a variable length that corresponds to the length of the portion(s) represented. Thus, the segment length may correspond to page length, for example.
As noted previously, the method 411 may include displaying the number of pages corresponding to the segments covered by the slider in the trough, so that the slider covers approximately the same number of pages that are displayed. The method 411 may go on to include displaying a translucent slider in the trough at block 447, wherein the visible indicators remain visible even when the translucent slider is displayed on top of the visible indicators.
In some embodiments, the method 411 includes, at block 451, displaying a plurality of visible indicators in sequence, such as a monotonically increasing or monotonically decreasing sequence of integers which are visible as numeric indicators in the trough. The sequence of integers may include displayed integers and non-displayed integers, wherein the non-displayed integers comprise at least N integers between each of the displayed integers, and wherein N is an integer greater than or equal to one. This latter use of non-displayed integers may occur when the dynamically compressible trough includes several document portions per segment, such that some of the visible indicators in a sequence are skipped (e.g., every odd integer is displayed, up until the last page of the document).
The method 411 may go on to block 455 to include displaying a number of visible indicators, wherein at least one of the number corresponds to the last page number of the electronic content. Thus, the last number displayed in the trough is the same as the last page of the displayed document. The method 411 may include displaying several segment division indicators comprising line segments spanning at least part of a width of the trough and located in the trough between the segments (e.g., see
Those of ordinary skill in the art will realize that each of the method elements shown in
In order to avoid obscuring the components of
The data access module 510 may be used by the rendering module 506 to access a storage element 520, such as a database, a memory, a disk, or other storage device. The storage element 520 may serve to contain one or more items having electronic content 524, such as electronic documents 534. The data access module 510 may operate to read from and/or write to the electronic content 524 and may provide reading and writing services for the benefit of other system modules, including the GUI module 508, the rendering module 506, and the processor 504.
The data access module 510 may be present in some embodiments, and absent in others. When present, the data access module 510 may operate as a mediator between the various components of the system 500 and the electronic content 524. For example, the storage element 520 may be included in a remote server.
The rendering module 506 may be operably coupled to an output device 528, such as a display screen, printer, or loudspeaker, among others. This output device 528 may be used for presenting renderings of documents 534. Rendering may take the form of displaying the documents 534, including a vertically or horizontally-oriented version of the dynamically compressible trough in the segmented scroll bar described above.
The GUI module 508 may be operably connected to the rendering module 506 and the data access module 510. The rendering module 506 may comprise a portable document format processing program in some embodiments.
The GUI module 508 may receive input from a variety of input devices 532 (e.g., a keyboard, a mouse, a trackball, voice recognizer, touch pad, touch screen, etc.). Thus, many embodiments may be realized.
For example, a system 500 to display a segmented scroll bar with a dynamically compressible trough may include an output device 528, comprising a display, as well as a rendering module 506 to display electronic content 524 on the display as part of a GUI 540, which may be similar to or identical to either of the GUIs 100, 200 of
Thus, other embodiments may be realized. For example, an article 600 of manufacture, such as a computer, a memory system, a magnetic or optical disk, some other storage device, and/or any type of electronic device or system may include one or more processors 604 coupled to a machine-readable medium 608 such as a memory (e.g., removable storage media, as well as any memory including an electrical, optical, or electromagnetic conductor) having instructions 612 stored thereon (e.g., computer program instructions), which when executed by the one or more processors 604 result in the machine 602 performing any of the actions described with respect to the methods above.
The machine 602 may take the form of a computer system having a processor 604 coupled to a number of components directly, and/or using a bus 616. Thus, the machine 602 may be similar to or identical to the system 500 shown in
Turning now to
The processor 604, the memories 620, 624, and the storage device 606 may each include instructions 612 which, when executed, cause the machine 602 to perform any one or more of the methods described herein. In some embodiments, the machine 602 operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked environment, the machine 602 may operate in the capacity of a server or a client machine in server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine 602 may be a personal computer (PC), a tablet PC, a set-top box (STB), a PDA, a cellular telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine 602 is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.
While the machine-readable medium 608 is shown as a single medium, the term “machine-readable medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers, and or a variety of storage media, such as the registers of the processor 604, memories 620, 624, and the storage device 606 that store the one or more sets of instructions 612. The term “machine-readable medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine 602 to perform any one or more of the methodologies of the present invention, or that is capable of storing, encoding or carrying data structures utilized by or associated with such a set of instructions. The terms “machine-readable medium” or “computer-readable medium” shall accordingly be taken to include tangible media, such as solid-state memories and optical and magnetic media.
Implementing the apparatus, systems, and methods of the various embodiments may thus provide the ability to more quickly and accurately locate a specific portion of electronic content. Improved productivity and satisfaction on the part of the user may result.
Although embodiments of the invention have been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader scope of the invention. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof, show by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those of ordinary skill in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.
Embodiments may, for example, be implemented as a stand-alone application (e.g., without any network capabilities), a client-server application or a peer-to-peer (or distributed) application. Embodiments may also, for example, be deployed by Software-as-a-Service (SaaS), Application Service Provider (ASP), or utility computing providers, in addition to being sold or licensed via traditional channels.
Certain applications or processes are described herein as including a number of modules or mechanisms. A module or a mechanism may be a unit of distinct functionality that can provide information to, and receive information from, other modules. Accordingly, the described modules may be regarded as being communicatively coupled. Modules may also initiate communication with input or output devices, and can operate on a resource (e.g., a collection of information). Modules may include hardware circuitry, optical components, single or multi-processor circuits, memory circuits, software program modules and objects, firmware, and combinations thereof, as appropriate for particular implementations of various embodiments. The term “module” includes an identifiable portion of code, data, or a computational object to achieve a particular function, operation, processing, or procedure.
Such embodiments of the inventive subject matter may be referred to herein, individually and/or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of ordinary skill in the art upon reviewing the above description.
The Abstract of the Disclosure is provided to comply with 37 C.F.R. §1.72(b), requiring an abstract that will allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.
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 |
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 |
6314408 | Salas et al. | Nov 2001 | B1 |
6314425 | Serbinis et al. | Nov 2001 | 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 |
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 |
7574669 | Braun et al. | Aug 2009 | B1 |
7676759 | Carter | Mar 2010 | B2 |
7724249 | Horikawa et al. | May 2010 | B1 |
7769810 | Kaufman | Aug 2010 | B1 |
7945595 | Kraley | May 2011 | B1 |
7949633 | Shaver et al. | May 2011 | B1 |
20020163548 | Chiu et al. | Nov 2002 | A1 |
20020186252 | Himmel et al. | Dec 2002 | A1 |
20040041843 | Cui et al. | Mar 2004 | A1 |
20040088331 | Therrien et al. | May 2004 | A1 |
20050064858 | Makela et al. | Mar 2005 | A1 |
20050262225 | Halpern et al. | Nov 2005 | A1 |
20060010382 | Ejiri et al. | Jan 2006 | A1 |
20060026502 | Dutta | Feb 2006 | A1 |
20060184901 | Dietz | Aug 2006 | A1 |
20070198616 | Goto | Aug 2007 | A1 |
20070239831 | Basu | Oct 2007 | A1 |
20070260996 | Jakobson | Nov 2007 | A1 |
20070271502 | Bedi et al. | Nov 2007 | A1 |
20080059539 | Chin et al. | Mar 2008 | A1 |
20080250329 | Stefik et al. | Oct 2008 | A1 |
Entry |
---|
“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,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 pgs. |
“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,421, Response filed May 12, 2011 to Advisory Action mailed Mar. 22, 2011”, 15 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. |
“Comparison of office suites”, Comparison of office suites—Wikipedia, the free encylopedia, [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 the 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 interent: <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. |
Number | Date | Country | |
---|---|---|---|
20140033099 A1 | Jan 2014 | US |