Patent Grant
10585563
This disclosure relates to electronic display devices, and more particularly, to user interface (UI) techniques for interacting with computing devices.
Electronic display devices such as tablets, eReaders, mobile phones, smart phones, personal digital assistants (PDAs), and other such touch screen electronic display devices are commonly used for displaying consumable content. The content may be, for example, an eBook, an online article or blog, images, a movie or video, a map, just to name a few types. Such display devices are also useful for displaying a user interface that allows a user to interact with an application running on the device. The textual content and/or screen controls may be spoken aloud to the user. The user interface may include, for example, one or more touch screen controls and/or one or more displayed labels that correspond to nearby hardware buttons. The touch screen display may be backlit or not, and may be implemented for instance with an LED screen or an electrophoretic display. Such devices may also include other touch sensitive surfaces, such as a track pad (e.g., capacitive or resistive touch sensor) or touch sensitive housing (e.g., acoustic sensor).
5
a-b collectively illustrate an example accessible automatic reading mode of an electronic touch screen device, in accordance with an embodiment of the present invention.
6
a-d collectively illustrate an example accessible automatic reading mode of an electronic touch screen device, in accordance with another embodiment of the present invention.
Techniques are disclosed for providing accessible reading modes in electronic computing devices. The device may be a touch screen mobile device, or any other device with a touch sensitive surface that can detect user gestures. The user can activate a manual or automatic reading mode using an activation gesture, and may transition between the manual reading mode and the automatic reading mode using a transition gesture. The manual reading mode may, for example, allow the user to navigate through content, manually direct the reading of textual content using horizontal dragging gestures, share content with others, aurally sample and select content, add notes to selected content, share content, adjust the reading rate, font, volume, or configure other reading and/or device settings. The automatic reading mode facilitates an electronic device reading automatically and continuously from a predetermined point with a selected voice font, volume, and rate, and only responds to a limited number of command gestures that may include, for example, adjusting the reading rate and/or scrolling to the next or previous sentence, paragraph, page, chapter, section or other content boundary. For each reading mode, earcons may guide the selection and/or navigation techniques, indicate content boundaries, confirm user actions or selections, or to otherwise provide an intuitive and accessible user experience.
General Overview
As previously explained, electronic display devices such as tablets, eReaders, and smart phones are commonly used for displaying user interfaces and consumable content. The user of such devices can typically consume the displayed content with relative ease. In some instances, users who are unable to view or read text or other content on the screen may wish to consume textual content, adjust device settings, and/or select content on the device. While some electronic devices may aurally present textual content to a user, offer printed instructions on a screen protector (e.g., using a braille-embossed screen cover), or offer a hunt-and-peck approach for adjusting device settings, the multiple accessible reading modes described herein may provide a more intuitive or otherwise positive user experience.
Thus, and in accordance with an embodiment of the present invention, techniques are disclosed for providing accessible multiple reading modes in electronic touch screen devices. In one embodiment, a manual reading mode and an automatic reading mode may be provisioned by the device's UI, wherein the manual mode allows the user to actively navigate and/or adjust device settings. In one embodiment, the manual reading mode allows the user to navigate through content, share content with others, aurally sample and select content, add notes to selected content, adjust the reading rate, font, volume, or configure other reading and/or device settings. In one embodiment, the automatic reading mode facilitates an electronic device reading automatically and continuously from a predetermined point with a selected voice font, volume, and rate, and only detects a limited number of command gestures (e.g., skip sentence, skip page, etc.). In some cases, the voice font may include various voices of different gender, accents, or characteristics in which the textual content may be read to the user. The automatic mode may also, for example, play earcon audio cues upon passing sentences, paragraphs, pages, chapters, or other content boundaries. In manual mode, however, the user may change different reading rates, fonts, volumes, etc. The user can engage an automatic or manual reading mode by performing a reading mode activation gesture, or switch between reading modes using a simple transition gesture or control feature action. In one embodiment, the entire touch screen display may be treated as a single button to facilitate transitioning between automatic and manual modes, when the accessible user interface is active. For example, a single tap on the touch sensitive surface may transition the device from automatic mode to manual mode, while a double-tap gesture on the touch sensitive surface may transition the device from manual mode to automatic mode, in some embodiments. The single and double taps can be distinguished from other taps, based on the hold time. For instance, the taps to toggle between manual and automatic modes can be quick taps (e.g., quick tap and release of less than 1 second), while other taps intended for different functions can have a longer hold time (e.g., greater than 1 second). In any case, treating the entire touch screen as a single button when the accessible user interface is active effectively allows the user to interact with the device without regard to the location of any touch screen control features. Thus, the user need not be able to see any specific UI control features or otherwise touch those features. This look-free feature, in combination with the manual and automatic mode functions as variously described herein, allows a rich user experience for vision-impaired users or users who can otherwise not focus their attention on the display to interact with the device. An earcon may be, for example, a brief and distinctive sound or chime representing a specific action or event, conveying other information, or prompting a user action.
While operating in the manual reading mode, the user may, for example, aurally sample textual content on the device screen using a short press gesture, direct the reading of textual content using horizontal dragging gestures, navigate through menu options using vertical swipe gestures, select words and sections of text and read aloud selected content using various gesture combinations, just to name a few functions. In the automatic reading mode, the user may listen to textual content and perform a limited number of functions, including for example, adjusting the reading rate using vertical swipe gestures, and scrolling or skipping to the next or previous sentence, paragraph, page, chapter, section, article, or some other content boundary using various horizontal swipe gestures with one or more contact points. While scrolling through larger sections of content, such as chapters or articles, the automatic reading mode may remember where the user was currently reading and create a virtual bookmark at that page that prompts the reading mode to make an additional stop at that page if it is not the beginning of a chapter or other content section. For each of these reading modes, earcons may be employed to guide the selection and/or navigation techniques, indicate content boundaries, confirm user actions or selections, or to otherwise provide an intuitive and accessible user experience.
As used herein, a swipe gesture may include a sweeping or dragging gesture across at least a portion of the touch sensitive surface whether directly contacting that surface or hovering over that surface (e.g., within a few centimeters or otherwise close enough to be detected by the touch sensitive surface). In some embodiments, the swipe gesture may be performed at a constant speed in one single direction, or may also be an accelerated flick gesture. The gestures can be performed, for example, with the tip of a finger or a stylus, or any other suitable implement capable of providing a detectable swipe gesture. To facilitate detection of a substantially horizontal and/or vertical swipe gesture with reference to the bottom of the electronic device's screen, any swipe gesture that is, for example, within a range of 45 degrees of the horizontal or vertical may be treated as a horizontal or vertical gesture.
Given the global nature and/or uniqueness of the engagement mechanism, in accordance with some example embodiments, the accessible reading modes can be similarly invoked within multiple diverse applications, for example, an eReader, Internet browser, picture viewer, file browser, or any other textual content. In such embodiments, the accessible reading modes may be invoked without conflicting with other global gestures that might also be used by the device's operating system. Numerous uniquely identifiable engagement schemes that exploit a touch sensitive surface can be used as will be appreciated in light of this disclosure. Further note that any touch sensitive device (e.g., track pad, touch screen, or other touch sensitive surface, whether capacitive, resistive, acoustic or other touch detecting technology, regardless of whether a user is physically contacting the device or using some sort of implement, such as a stylus) may be used to detect the user contact, and the claimed invention is not intended to be limited to any particular type of touch sensitive technology, unless expressly stated. For ease of reference, user input is sometimes referred to as contact or user contact; however, direct and/or proximate contact (e.g., hovering within a few centimeters of the touch sensitive surface) can be used. In other words, in some embodiments, a user can operate the accessible menu navigation user interface without physically touching the touch sensitive device.
Architecture
As can be seen with this example configuration, the device comprises a housing that includes a number of hardware features such as a power button, control features, and a press-button (sometimes called a home button herein). A user interface is also provided, which in this example embodiment includes a quick navigation menu having six main categories to choose from (Home, Library, Shop, Search, Light, and Settings) and a status bar that includes a number of icons (a night-light icon, a wireless network icon, and a book icon), a battery indicator, and a clock. In one embodiment, an accessible UI may aurally present to the user the various menu categories from which the user may select the desired menu with a touch screen gesture or by activating a control feature. Some embodiments may have fewer or additional such UI features, or different UI features altogether, depending on the target application of the device. Any such general UI controls and features can be implemented using any suitable conventional or custom technology, as will be appreciated.
The hardware control features provided on the device housing in this example embodiment are configured as elongated press-bars and can be used, for example, to page forward (using the top press-bar) or to page backward (using the bottom press-bar), such as might be useful in an eReader application. The power button can be used to turn the device on and off, and may be used in conjunction with a touch-based UI control feature that allows the user to confirm a given power transition action request (e.g., such as a slide bar or tap point graphic to turn power off). Numerous variations will be apparent, and the claimed invention is not intended to be limited to any particular set of hardware buttons or UI features, or device form factor.
In this example configuration, the home button is a physical press-button that can be used as follows: when the device is awake and in use, pressing the button will present to the user (either aurally or visually) the quick navigation menu, which is a toolbar that provides quick access to various features of the device. The home button may also be configured to cease an active function that is currently executing on the device (such as a manual or automatic reading mode), or close a configuration sub-menu that is currently open. The button may further control other functionality if, for example, the user presses and holds the home button. For instance, an example such push-and-hold function could engage a power conservation routine where the device is put to sleep or an otherwise lower power consumption mode. So, a user could grab the device by the button, press and keep holding as the device is stowed into a bag or purse. Thus, one physical gesture may safely put the device to sleep. In such an example embodiment, the home button may be associated with and control different and unrelated actions: 1) present the quick navigation menu; 2) exit a configuration sub-menu; and 3) put the device to sleep. As can be further seen, the status bar may also include a book icon (upper left corner). In some cases, selecting the book icon may provide bibliographic information on the content or provide the main menu or table of contents for the book, movie, playlist, or other content.
In one particular embodiment, an accessible reading modes configuration sub-menu, such as the one shown in
As will be appreciated, the various UI control features and sub-menus displayed to the user are implemented as touch screen controls in this example embodiment. Such UI screen controls can be programmed or otherwise configured using any number of conventional or custom technologies. In general, the touch screen display translates a touch (direct or hovering, by a user's hand, a stylus, or any other suitable implement) in a given location into an electrical signal that is then received and processed by the device's underlying operating system (OS) and circuitry (processor, display controller, etc.). In some instances, note that the user need not actually physically touch the touch sensitive device to perform an action. For example, the touch screen display may be configured to detect input based on a finger or stylus hovering over the touch sensitive surface (e.g., within 3 centimeters of the touch screen or otherwise sufficiently proximate to be detected by the touch sensing circuitry). Additional example details of the underlying OS and circuitry in accordance with some embodiments will be discussed in turn with reference to
The touch sensitive surface (or touch sensitive display, in this example case) can be any surface that is configured with touch detecting technologies, whether capacitive, resistive, acoustic, active-stylus, and/or other input detecting technology, including direct contact and/or proximate contact. In some embodiments, the screen display can be layered above input sensors, such as a capacitive sensor grid for passive touch-based input, such as with a finger or passive stylus contact in the case of a so-called in-plane switching (IPS) panel, or an electro-magnetic resonance (EMR) sensor grid for sensing a resonant circuit of a stylus. In some embodiments, the touch sensitive display can be configured with a purely capacitive sensor, while in other embodiments the touch screen display may be configured to provide a hybrid mode that allows for both capacitive input and EMR input, for example. In still other embodiments, the touch sensitive surface is configured with only an active stylus sensor. Numerous touch screen display configurations can be implemented using any number of known or proprietary screen based input detecting technologies. In any such embodiments, a touch sensitive controller may be configured to selectively scan the touch sensitive surface and/or selectively report user inputs detected directly on or otherwise sufficiently proximate to (e.g., within a few centimeters, or otherwise sufficiently close so as to allow detection) the detection surface (or touch sensitive display, in this example case). The limited gesture options described above in reference to the automatic reading mode may be implemented, for example, using the selective scanning and/or reporting techniques described herein.
As previously explained, and with further reference to
With reference to
As can be further seen, a back button arrow UI control feature may be provisioned on the screen for any of the menus provided, so that the user can go back to the previous menu, if so desired. In other embodiments, a universal back screen gesture may be performed in order to return to the previous menu. Note that configuration settings provided by the user can be saved automatically (e.g., user input is saved as selections are made or otherwise provided). Alternatively, a save button or other such UI feature can be provisioned, or a save gesture performed, which the user can engage as desired. The configuration sub-menus shown in
In this example embodiment, the memory includes a number of modules stored therein that can be accessed and executed by the processor (and/or a co-processor). The modules include an operating system (OS), a user interface (UI), and a power conservation routine (Power). The modules can be implemented, for example, in any suitable programming language (e.g., C, C++, objective C, JavaScript, custom or proprietary instruction sets, etc), and encoded on a machine readable medium, that when executed by the processor (and/or co-processors), carries out the functionality of the device including a UI having multiple accessible reading modes as variously described herein. The computer readable medium may be, for example, a hard drive, compact disk, memory stick, server, or any suitable non-transitory computer/computing device memory that includes executable instructions, or a plurality or combination of such memories. Other embodiments can be implemented, for instance, with gate-level logic or an application-specific integrated circuit (ASIC) or chip set or other such purpose-built logic, or a microcontroller having input/output capability (e.g., inputs for receiving user inputs and outputs for directing other components) and a number of embedded routines for carrying out the device functionality. In short, the functional modules can be implemented in hardware, software, firmware, or a combination thereof.
The processor can be any suitable processor (e.g., Texas Instruments OMAP4, dual-core ARM Cortex-A9, 1.5 GHz), and may include one or more co-processors or controllers to assist in device control. In this example case, the processor receives input from the user, including input from or otherwise derived from the power button and the home button. The processor can also have a direct connection to a battery so that it can perform base level tasks even during sleep or low power modes. The memory (e.g., for processor workspace and executable file storage) can be any suitable type of memory and size (e.g., 256 or 512 Mbytes SDRAM), and in other embodiments may be implemented with non-volatile memory or a combination of non-volatile and volatile memory technologies. The storage (e.g., for storing consumable content and user files) can also be implemented with any suitable memory and size (e.g., 2 GBytes of flash memory). The display can be implemented, for example, with a 7 to 9 inch 1920×1280 IPS LCD touchscreen touch screen, or any other suitable display and touchscreen interface technology. The communications module can be, for instance, any suitable 802.11 b/g/n WLAN chip or chip set, which allows for connection to a local network, and so that content can be exchanged between the device and a remote system (e.g., content provider or repository depending on the application of the device). In some specific example embodiments, the device housing that contains all the various componentry measures about 7″ to 9″ high by about 5″ to 6″ wide by about 0.5″ thick, and weighs about 7 to 8 ounces. Any number of suitable form factors can be used, depending on the target application (e.g., laptop, desktop, mobile phone, etc). The device may be smaller, for example, for smartphone and tablet applications and larger for smart computer monitor and laptop and desktop computer applications.
The operating system (OS) module can be implemented with any suitable OS, but in some example embodiments is implemented with Google Android OS or Linux OS or Microsoft OS or Apple OS. As will be appreciated in light of this disclosure, the techniques provided herein can be implemented on any such platforms. The power management (Power) module can be configured as typically done, such as to automatically transition the device to a low power consumption or sleep mode after a period of non-use. A wake-up from that sleep mode can be achieved, for example, by a physical button press and/or a touch screen swipe or other action. The user interface (UI) module can be, for example, based on touchscreen technology and the various example screen shots and use-case scenarios shown in
Client-Server System
Accessible Reading Mode Examples
In one embodiment, dragging a contact point to the right, as shown in the example of
Methodology
As can be seen, the method generally includes sensing a user's input by a touch screen display. As soon as the user begins to swipe, drag or otherwise move a contact point, the UI code (and/or hardware) can assume a swipe gesture has been engaged and track the path of the contact point with respect to any fixed point within the touch screen until the user stops engaging the touch screen surface. The release point can also be captured by the UI as it may be used to commit the action started when the user pressed on the touch sensitive screen. In a similar fashion, if the user releases hold without moving the contact point, a tap or press or press-and-hold command may be assumed depending on the amount of time the user was continually pressing on the touch sensitive screen. These main detections can be used in various ways to implement UI functionality, including multiple accessible reading modes as variously described herein, as will be appreciated in light of this disclosure.
In this example case, the method includes detecting 701 a user gesture on the touch sensitive interface. As described above, the gesture contact may be performed in any suitable manner using a stylus, the user's finger, or any other suitable implement, and it may be performed on a touch screen surface, a track pad, acoustic sensor, or other touch sensitive surface. The user contact monitoring is essentially continuous. Once a user contact has been detected, the method may continue with determining 702 whether an automatic reading mode activation gesture has been performed. Such a gesture could include, for example, a single-tap, a double-tap, and/or a control feature action. If an automatic reading mode activation gesture has been performed, the method may continue with entering 703 the automatic reading mode. The method may continue with monitoring 704 the touch sensitive device for additional gestures. As discussed above, in some embodiments the automatic reading mode may only allow a limited number of automatic reading mode functions and gestures, and monitoring for gestures in the automatic reading mode may include only monitoring for those gesture types. Once a contact has been detected, the method may continue with determining 705 whether the reading mode transition gesture has been detected. If the reading mode transition gesture has not been detected, the method may continue with determining 706 whether an automatic reading mode gesture has been detected. As previously discussed, the automatic reading mode gestures may include vertical or horizontal swipe gestures performed with one or more contact points. If no automatic reading mode gesture has been detected, the contact may be reviewed 707 for some other UI request. If an automatic reading mode gesture has been detected, the method may continue with determining 708 whether a multi-page flip gesture has been detected. Such gestures may include, for example, a gesture to go to the next or previous chapter, section, article, or some other multi-page content boundary. If no multi-page flip gesture has been detected, the method may continue with performing 709 the automatic mode gesture function. In some cases, the function may include scrolling forward or backward by sentence or paragraph, or adjusting the reading rate. If a multi-page flip gesture has been detected, the method may continue with bookmarking 710 the current page before performing the multi-page flip function. The bookmark may be helpful later if another multi-page flip function is performed because the function may be configured to make an additional stop on the bookmarked page, in some embodiments. After performing the gesture function at 709, the method may continue with monitoring 704 for additional gestures.
If, however, no automatic reading mode activation gesture has been detected at 702, the method may continue with determining 711 whether a manual reading mode activation gesture has been detected. Such a gesture could include, for example, a single-tap, a double-tap, and/or a control feature action. If no manual reading mode activation gesture has been detected, the method may continue with reviewing 707 the contact for other UI requests. If a manual reading mode activation gesture has been detected, the method may continue with entering 712 the manual reading mode. Furthermore, if a reading mode transition gesture has been detected at 705, the method may also continue with entering the manual reading mode. The method may continue with monitoring 713 the touch sensitive device for additional gestures. Once a contact or gesture has been detected, the method may continue with determining 714 whether the reading mode transition gesture has been detected. If the reading mode transition gesture has been detected, the method may continue with entering 703 the automatic reading mode. If no reading mode transition gesture has been detected, the method may continue with determining 715 whether a manual reading mode gesture has been detected. If no manual reading mode gesture has been detected, the contact may be reviewed 707 for some other UI request. If a manual reading mode gesture has been detected, the method may continue with performing 716 the function associated with the manual reading mode gesture. As discussed above, example manual reading mode gestures along with their corresponding functions may include: a short press gesture to aurally sample textual content on the device screen, horizontal dragging gestures to direct the reading of textual content, vertical swipe gestures to navigate through menu options, a combination of tap gestures to define the beginning and end of a text selection, or a double-tap gesture to read aloud a text selection. Once the manual reading mode function has been performed, the method may continue with monitoring 713 for additional gestures. Note that at any point during the method, the accessible reading modes may be paused or abandoned completely by performing an exit gesture, pressing the device's home button, putting the device to sleep, or performing some other gesture or control feature action.
Numerous variations and embodiments will be apparent in light of this disclosure. One example embodiment of the present invention provides a device including a touch sensitive surface for allowing user input. The device also includes an accessible user interface including an automatic reading mode configured to automatically and continuously aurally present textual content from a predetermined point with a selected voice font, volume, and rate; and a manual reading mode configured to perform an action including at least one of: aurally present textual content at a current read point or that is selected, navigate menu options, share content, select content, add notes to content, adjust reading rate, adjust voice font, and/or adjust volume in response to one or more corresponding gestures; and wherein the accessible user interface is configured to transition between the automatic reading mode and the manual reading mode in response to a transition gesture. In some cases, the accessible user interface is further configured to activate the automatic reading mode in response to an automatic reading mode activation gesture, and to activate the manual reading mode in response to a manual reading mode activation gesture. In some cases, the automatic reading mode is further configured to aurally present one or more earcons in response to at least one of: passing a sentence, paragraph, page, slide, article, chapter, and/or content section. In some cases, the accessible user interface is further configured to aurally present one or more earcons in response to at least one of: confirming a user action, accepting a menu option, selecting content, entering an automatic reading mode, entering a manual reading mode, navigating through a menu, and/or adjusting a settings option. In some cases, the automatic reading mode is further configured to perform at least one of: adjust reading rate, scroll by sentence, scroll by paragraph, scroll by page, and/or scroll by chapter in response to a corresponding swipe gesture. In some such cases, the automatic reading mode is displaying a page that is not the beginning of a chapter and the mode is configured to create a virtual bookmark on the currently displayed page if a gesture is performed to scroll to the next or previous chapter, wherein the bookmark prompts the automatic reading mode to make an additional stop on the bookmarked page while scrolling over that page. In some cases, the automatic reading mode is configured to disregard all contacts on the touch sensitive surface other than commands to adjust reading rate, scroll by sentence, scroll by page, and/or scroll by chapter. In some cases, the manual reading mode is further configured to aurally present textual content in forward order in response to a horizontal drag gesture performed toward the right, and in reverse order in response to a horizontal drag gesture performed toward the left. In some cases, the manual reading mode is further configured to aurally present selected textual content in response to a double-tap gesture. In some cases, the touch sensitive surface is a touch screen display and the manual reading mode is further configured to aurally present a word to the user in response to a short press gesture performed over the word. In some such cases, the manual reading mode is further configured to select the word in response to a first tap gesture performed after the word is aurally presented, navigate to a terminating word in response to one or more navigation gestures, and select all text between the word and the terminating word in response to a second tap gesture performed after the terminating word has been presented to the user. In some such cases, the first tap gesture is performed while the short press gesture is still being held.
Another example embodiment of the present invention provides a mobile computing system including a processor and a touch sensitive surface for allowing user input, and an accessible user interface executable on the processor and including an automatic reading mode configured to automatically and continuously aurally present textual content from a predetermined point with a selected voice font, volume, and rate; and a manual reading mode configured to perform an action including at least one of: aurally present textual content at a current read point or that is selected, navigate menu options, share content, select content, add notes to content, adjust reading rate, adjust voice font, and/or adjust volume in response to one or more corresponding gestures, and wherein the accessible user interface is configured to transition between the automatic reading mode and the manual reading mode in response to a transition gesture. In some cases, the automatic reading mode is further configured to perform at least one of: adjust reading rate, scroll by sentence, scroll by paragraph, scroll by page, and/or scroll by chapter in response to a corresponding gesture on the touch sensitive surface. In some cases, the automatic reading mode is further configured to aurally present one or more earcons in response to at least one of: passing a sentence, paragraph, page, slide, article, chapter, and/or content section.
Another example embodiment of the present invention provides a computer program product including a plurality of instructions non-transiently encoded thereon to facilitate operation of an electronic device according to a process. The computer program product may include one or more computer readable mediums such as, for example, a hard drive, compact disk, memory stick, server, cache memory, register memory, random access memory, read only memory, flash memory, or any suitable non-transitory memory that is encoded with instructions that can be executed by one or more processors, or a plurality or combination of such memories. In this example embodiment, the process is configured to receive at a touch sensitive surface an accessible automatic reading mode activation gesture; automatically and continuously aurally present textual content from a predetermined point with a selected voice font, volume, and rate in response to the accessible automatic reading mode activation gesture; receive at a touch sensitive surface an accessible manual reading mode activation gesture, the manual reading mode configured to perform an action including at least one of: aurally present textual content at a current read point or that is selected, navigate menu options, share content, select content, add notes to content, adjust reading rate, adjust voice font, and/or adjust volume in response to one or more corresponding gestures; and transition between the automatic reading mode and the manual reading mode in response to a transition gesture. In some cases, the touch sensitive surface is a touch screen display and the process is further configured to receive at the touch screen display a short press gesture performed over a first word; and aurally present the first word to the user. In some such cases, the process is further configured to select the first word in response to a first tap gesture received on the touch screen display after the word is aurally presented; navigate to a terminating word in response to the one or more navigation gestures received at the touch screen display; aurally present the terminating word to the user; and select all content between the first word and the terminating word in response to a second tap gesture received on the touch screen display after the terminating word has been presented to the user. In some cases, the touch sensitive surface is a touch screen display and the process is further configured to proceed to an adjacent page in response to a page turning gesture received at the touch screen display; and proceed to the beginning of an adjacent chapter in response to a chapter scrolling gesture received at the touch screen display. In some such cases, the process is further configured to create a virtual bookmark on a currently displayed page if a chapter scrolling gesture is received, the currently displayed page not being the beginning of a chapter; and make an additional stop on the bookmarked page in response to a subsequent chapter scrolling gesture prompting the process to proceed over the bookmarked page.
The foregoing description of the embodiments of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of this disclosure. It is intended that the scope of the invention be limited not by this detailed description, but rather by the claims appended hereto.
This application is a continuation of U.S. application Ser. No. 13/946,538, which claims the benefit of U.S. Provisional Application Nos. 61/674,098 and 61/674,102 both filed on Jul. 20, 2012 all of which are herein incorporated by reference in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4896543 | Gullman | Jan 1990 | A |
| 5633471 | Fukushima | May 1997 | A |
| 5844557 | Shively, II | Dec 1998 | A |
| 6115482 | Sears | Sep 2000 | A |
| 6259438 | Fleck et al. | Jun 2001 | B1 |
| 6334157 | Oppermann et al. | Dec 2001 | B1 |
| 6933928 | Lilienthal | Aug 2005 | B1 |
| 6956564 | Williams | Oct 2005 | B1 |
| 7107533 | Duncan et al. | Sep 2006 | B2 |
| 7649524 | Haim et al. | Jan 2010 | B2 |
| 7840912 | Elias et al. | Nov 2010 | B2 |
| 7898541 | Hong et al. | Mar 2011 | B2 |
| RE42738 | Williams | Sep 2011 | E |
| 8059101 | Westerman et al. | Nov 2011 | B2 |
| 8239413 | Hubert | Aug 2012 | B2 |
| 8274536 | Chaudhri et al. | Sep 2012 | B2 |
| 8286104 | Yonge-Mallo | Oct 2012 | B1 |
| D670713 | Cranfill et al. | Nov 2012 | S |
| RE44103 | Williams | Mar 2013 | E |
| 8400417 | Ording et al. | Mar 2013 | B2 |
| 8452600 | Fleizach | May 2013 | B2 |
| 8508494 | Moore | Aug 2013 | B2 |
| 8659555 | Pihlaja | Feb 2014 | B2 |
| 8766928 | Weeldreyer et al. | Jul 2014 | B2 |
| 9615231 | Thiele et al. | Apr 2017 | B2 |
| 20010025289 | Jenkins et al. | Sep 2001 | A1 |
| 20020116421 | Fox et al. | Aug 2002 | A1 |
| 20050216839 | Salvucci | Sep 2005 | A1 |
| 20060053372 | Adkins | Mar 2006 | A1 |
| 20060067577 | Marggraff | Mar 2006 | A1 |
| 20070047002 | Hull et al. | Mar 2007 | A1 |
| 20080020356 | Saba | Jan 2008 | A1 |
| 20080036747 | Hope | Feb 2008 | A1 |
| 20090228798 | Kephart et al. | Sep 2009 | A1 |
| 20090295734 | Hendrickson et al. | Dec 2009 | A1 |
| 20100100854 | Russell et al. | Apr 2010 | A1 |
| 20100192086 | Kocienda et al. | Jul 2010 | A1 |
| 20100229130 | Edge et al. | Sep 2010 | A1 |
| 20100259482 | Ball | Oct 2010 | A1 |
| 20100262659 | Christiansen et al. | Oct 2010 | A1 |
| 20100299638 | Choi | Nov 2010 | A1 |
| 20100318895 | Steinberger et al. | Dec 2010 | A1 |
| 20100324902 | Kurzwell et al. | Dec 2010 | A1 |
| 20100328052 | Pasquero et al. | Dec 2010 | A1 |
| 20110050591 | Kim et al. | Mar 2011 | A1 |
| 20110167350 | Hoellwarth | Jul 2011 | A1 |
| 20110191675 | Kauranen | Aug 2011 | A1 |
| 20110210926 | Pasquero et al. | Sep 2011 | A1 |
| 20110234543 | Gardenfors et al. | Sep 2011 | A1 |
| 20110258542 | Kenney et al. | Oct 2011 | A1 |
| 20110273379 | Chen et al. | Nov 2011 | A1 |
| 20110283241 | Miller et al. | Nov 2011 | A1 |
| 20110304558 | Pasquero et al. | Dec 2011 | A1 |
| 20110307833 | Dale et al. | Dec 2011 | A1 |
| 20110310026 | Davis | Dec 2011 | A1 |
| 20120001843 | Gravino | Jan 2012 | A1 |
| 20120046947 | Fleizach | Feb 2012 | A1 |
| 20120050159 | Yu et al. | Mar 2012 | A1 |
| 20120056821 | Goh | Mar 2012 | A1 |
| 20120084694 | Sirpal | Apr 2012 | A1 |
| 20120084704 | Lee | Apr 2012 | A1 |
| 20120110517 | Sparks et al. | May 2012 | A1 |
| 20120124505 | St. Jacques, Jr. | May 2012 | A1 |
| 20120127110 | Amm et al. | May 2012 | A1 |
| 20120139879 | Kim et al. | Jun 2012 | A1 |
| 20120192093 | Migos | Jul 2012 | A1 |
| 20120192118 | Migos | Jul 2012 | A1 |
| 20120221938 | Patterson et al. | Aug 2012 | A1 |
| 20120235901 | Binder | Sep 2012 | A1 |
| 20120235921 | Laubach | Sep 2012 | A1 |
| 20120235938 | Laubach | Sep 2012 | A1 |
| 20120240041 | Lim et al. | Sep 2012 | A1 |
| 20120242579 | Chua | Sep 2012 | A1 |
| 20120242584 | Tuli | Sep 2012 | A1 |
| 20120249768 | Binder | Oct 2012 | A1 |
| 20120272144 | Radakovitz et al. | Oct 2012 | A1 |
| 20120280947 | Weaver et al. | Nov 2012 | A1 |
| 20120299853 | Dagar | Nov 2012 | A1 |
| 20120306765 | Moore | Dec 2012 | A1 |
| 20120306772 | Tan | Dec 2012 | A1 |
| 20120311438 | Cranfill et al. | Dec 2012 | A1 |
| 20120313848 | Galor | Dec 2012 | A1 |
| 20120324355 | Mbenkum et al. | Dec 2012 | A1 |
| 20120329529 | van der Raadt | Dec 2012 | A1 |
| 20130016045 | Zhao et al. | Jan 2013 | A1 |
| 20130024820 | Kirkpatrick | Jan 2013 | A1 |
| 20130036383 | Yuan et al. | Feb 2013 | A1 |
| 20130047115 | Migos et al. | Feb 2013 | A1 |
| 20130055141 | Arriola et al. | Feb 2013 | A1 |
| 20130063364 | Moore | Mar 2013 | A1 |
| 20130073998 | Migos et al. | Mar 2013 | A1 |
| 20130076632 | Sirpal et al. | Mar 2013 | A1 |
| 20130076637 | Teltz | Mar 2013 | A1 |
| 20130076638 | Sirpal et al. | Mar 2013 | A1 |
| 20130076781 | Sirpal et al. | Mar 2013 | A1 |
| 20130113699 | Lim | May 2013 | A1 |
| 20130117702 | Jang et al. | May 2013 | A1 |
| 20130120271 | Lee et al. | May 2013 | A1 |
| 20130130216 | Morton et al. | May 2013 | A1 |
| 20130135234 | Hisano et al. | May 2013 | A1 |
| 20130139078 | Chuang et al. | May 2013 | A1 |
| 20130139107 | Jung | May 2013 | A1 |
| 20130151955 | Williams | Jun 2013 | A1 |
| 20130155094 | Ahn | Jun 2013 | A1 |
| 20130159939 | Krishnamurthi | Jun 2013 | A1 |
| 20130162532 | Cheng et al. | Jun 2013 | A1 |
| 20130185680 | Chaudhri et al. | Jul 2013 | A1 |
| 20130194308 | Privault et al. | Aug 2013 | A1 |
| 20130212454 | Casey | Aug 2013 | A1 |
| 20130222274 | Mori et al. | Aug 2013 | A1 |
| 20130232408 | Xu | Sep 2013 | A1 |
| 20130268826 | Nowakowski et al. | Oct 2013 | A1 |
| 20130304474 | Conkie et al. | Nov 2013 | A1 |
| 20130328809 | Smith | Dec 2013 | A1 |
| 20130332827 | Smith | Dec 2013 | A1 |
| 20140123032 | Lanz et al. | May 2014 | A1 |
| 20140127667 | Iannacone | May 2014 | A1 |
| 20140142954 | Cameron et al. | May 2014 | A1 |
| 20140160035 | Sauer et al. | Jun 2014 | A1 |
| 20140189056 | St. Clair et al. | Jul 2014 | A1 |
| 20140189524 | Murarka et al. | Jul 2014 | A1 |
| 20140189531 | Murarka et al. | Jul 2014 | A1 |
| 20140189539 | St. Clair et al. | Jul 2014 | A1 |
| 20140210729 | Chattopadhyay et al. | Jul 2014 | A1 |
| 20140215329 | Zilberman et al. | Jul 2014 | A1 |
| 20140215339 | Klein et al. | Jul 2014 | A1 |
| 20140215340 | Shetty et al. | Jul 2014 | A1 |
| 20140223381 | Huang et al. | Aug 2014 | A1 |
| 20140354594 | Kreutzer et al. | Dec 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 722150 | Jul 1996 | EP |
| 2012170745 | Dec 2012 | WO |
| Entry |
|---|
| Non Final Office Action received in U.S. Appl. No. 13/912,980 (dated Sep. 21, 2018) (39 pages). |
| Non-Final Office Action received for U.S. Appl. No. 13/912,976, dated Jan. 5, 2015, 15 pages. |
| Final Office Action received for U.S. Appl. No. 13/912,976, dated Jun. 5, 2015, 20 pages. |
| “Gesture Search for Google Mobile”, printed from www.google.com/mobile/gesture-search on Dec. 26, 2012. |
| Andrew Bragdon et al., “Experimental Analysis of Touch-Screen Gesture Designs in Mobile Environments”, Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, pp. 403-412 (2011 ). |
| “PAiA-Touch Switches,” PAiA Corporation USA, file:///S:/Client%20Files/Barnes%20&%20Noble/IDS%20Master%20Folder/S&G%20-%2 . . . , 3 pages, printed from the Internet on Aug. 27, 2013. |
| “Adonit Jot Touch (for iPad),” Adonit Jot Touch (for iPad) Review & Rating—PCMag.com; http://www.pcmag.com/article2/0.2817.2411192.00.asp; 6 pages, printed from the Internet on Jun. 20, 2013. |
| Volpe, Joseph, Amazon patents intelligent pen for adding annotations to digital and printed media (updated), posted Mar. 6, 2012 at 5:39PM, http://www.engadget.com/2012/03/06/amazon-patents-intelligent-pen/, 3 pages, printed from the Internet on Jun. 20, 2013. |
| “Apple Secretly Filed Three Dynamic Smart Pen Patents in Europe that are Chock Full of Cool Ideas,” http://www.patentlyapple.com/patently-apple/2013/02/apple-secretly-filed-three-dynamic-smart-pen-patents-in-europe-that-are-chock-full-of-cool-ideas.html, originally published Feb. 28, 2013, 13 pages, printed from the Internet on Aug. 13, 2013. |
| “Bamboo Stylus,” Wacom Americas, http://www.wacom.com/en/products/stylus, 5 pages, printed from the Internet on Jun. 20, 2013. |
| Robertson, Adi, “Blue Tiger pressure-sensitive iOS stylus will work over Bluetooth 4.0,” Http://www.theverge.com/2012/3/7/2851562/blue-tiger-ten-one-design-pressure-sensitive-bluetooth-4-0-stylus, 1 page, printed from the Internet on Aug. 2, 2013. |
| Malacria, et al., “Clutch-Free Panning and Integrated Pan-Zoom Control on Touch-Sensitive Surfaces: The CycloStar Approach,” CHI 2010, Apr. 10-15, 2010, Atlanta, Georgia, USA. Copyright 2010 ACM 978-1-60558-929-9, 10 pages, Sep. 10, 2004. |
| “Pen,” DuoSense Pen, N-trig Hands-on computing, http://www.n-trig.com/Content.aspx?Page=DigitalPencil, 3 pages, printed from the Internet on Jun. 20, 2013. |
| “Easing functions,” Easing Functions Cheat Sheet, http://easings.net/, 3 pages, printed from the Internet on Jun. 17, 2013. |
| Kirupa, Easing Functions (aka Timing Functions) in CSS3, printed Apr. 3, 2013, kirupa.com, http://www.kirupa.com/html5/easing_functions_css3.htm, 16 pages, printed from the Internet on Jun. 18, 2013. |
| “EMR (Electro-Magnetic Resonance) Technology—The De Facto Standard for Pen Tablet Devices is Realized using EMR Technology,” Wacom Components: Input Technology: EMR Technology, http://wacom-components.com/english/technology/emr.html, 5 pages, printed from the Internet on Aug. 2, 2013. |
| “Simultaneous Pen & Touch: The Natural Way to Work,” Perceptive Pixel Active Stylus, www.perceptivepixel.com/_literature_ 136086/Active_Stylus, 2 pages, printed from the Internet on Dec. 14, 2012. |
| “Future Apple Notebooks & Tablets may use Acoustic Commands—Patently Apple,” originally published Feb. 18, 2011, Http://www.patentlyapple.com/patently-apple/2011/02/future-apple-notebooks-tablets-may,6 pages, printed from the Internet on Nov. 3, 2012. |
| “Guidelines for selecting text and images (Windows Store apps),” http://msdn.microsoft.com/en-us/library/windows/apps/hh465334, 5 pages, printed from the Internet on Jun. 20, 2013. |
| Lutz, Zachary, “Hands-on with wireless, ultrasonic stylus an touchless gestures at MWC (video),” posted Mar. 1, 2012 at 8:28 AM, http://www.engadgel.com/2012/03/01/hands-on-with-wireless-ultrasonic-stylus-and-touchl, 3 pages, printed from the Internet on Jun. 20, 2013. |
| “HEX3 JaJa Pressure Sensitive Stylus,” HEX3 JaJa Pressure Sensitive Stylus Review & Rating—PCMag.com, http://www.pcmag.com/article2/0,2817,2411194,00.asp, 6 pages, printed from the Internet on Jun. 20, 2013. |
| “How do WACOM tablets work?,” tablel4u.co.uk, http://www.lablet4u.co.uk/techinfo.html, 2 pages, printed from the Internet on Jun. 20, 2013. |
| Kim, Arnold, “Multi-Touch Page Flipping eBook Concept Shown on an iPad,” posted Jan. 22, 2012 at 10:52pm PST, MacRumors—news and rumors you care about, http://www.macrumors.com/2012/01/23/multi-touch-page-ftipping-ebook-concept-shown-6 pages, printed from the Internet on Nov. 3, 2012. |
| “Desktop Touchscreens,”—Desktop touchscreens explained, http://www.touchscreenmagazine.nl/touchscreen-solutions/desktop-touchscreens, 1 page, printed from the Internet on Nov. 3, 2012. |
| “MTStylus Wireless Stereo Stylus for iPhone/Andriod Phone & Tablet,” dexim-MTStylus Wireless Stereo Stylus, Http://www.dexim.nel/contenl.php?id=165&pid=11, 2 pages, printed from the Internet on Jun. 20, 2013. |
| “Padblue 2,” BRANDO—mobile.brando.com, http://mobile.brando.com/Padblue-2_p9162c1577d94.html., 4 pages, printed from the Internet on May 10, 2013. |
| “Fingas, Jon, “Panasonic mobile devices to use Anoto's pattern-based pen input technology,” posted Jan. 8, 2013 at 1 :OOPM, http://www.engadgel.com/2013/01 /08/panasonic-mobile-devices-to-use-anoto-pattern-pen-, 4 pages, printed from the Internet on Jun. 20, 2013.” |
| “Bluetooth 4.0 SmartPen the future just got a little brighter,” Pogo Connect, http://tenonedesign.com/connecl.php, 7 pages, printed from the Internet on Jun. 20, 2013. |
| “Quick, Darren, “Pressure sensitive technology set to bring 3D capability to touchscreens,” posted on Jan. 31, 2010, Mobile Technology, http://www.gizmag.com/new-touchscreen-technology, 4 pages, printed from the Internet on Aug. 2, 2013.” |
| Rigg, Jamie, “Sony tries to patent stylus with friction-based haptic feedback,” posted on Nov. 22, 2012 at 9:50 AM, http://www.engadget.com/2012/11/22/sony-haptic-feedback-stylus-patent/, 2 pages, printed from the Internet on Jun. 20, 2013. |
| “Stylus Hanging Bluetooth Headset,” BRANDO—mobile.brando.com, http://mobile.brando.com/prod_detail.php?prod_id=03291, 4 pages, printed from the Internet on May 10, 2013. |
| “The JukeStyle is a great budget stylus for your iOS devices,” stylus Archives—iPad News, http://www.ipadnews.nl/tag/stylus/, 44 pages, printed from the Internet on Jun. 20, 2013. |
| Lavrinc, Damon, “Why Flipping Through Paper-Like Pages Endures in the Digital World,” originally posted on May 11, 2012 at 3:48PM, Gadget Lab, Http://www.wired.com/gadgetlab/2012/05/why-ftipping-through-paper-like-pages-endures-in-the-digital-world/, 5 pages, printed from the Internet on May 6, 2013. |
| “Explaining how the sPen tech works (and is very diff than other styluses),” http://forum.xda-developers.com/showthread.php?t=, 1 page, printed from the Internet on Jan. 15, 2013. |
| Kanai, et al., “Intra-Rendition Navigation,” Copyright 2012-2013 International Digital Publishing Forum (IDPF), 13 pages. |
| “Comics by comiXology,” Comic Book Reader Guide, http://www.comicbookreaderguide.com/comics-by-comixology/, 24 pages, printed from the Internet on May 6, 2013. |
| “NFC Forum: Frequently Asked Questions,” http://www.nfc-forum.org/resources/faqs#acknowledge, 11 pages, printed from the Internet on Feb. 18, 2013. |
| “How to Remote Wipe an iPhone or iPad,” OSXDaily, http://osxdaily.com/2012/06/05/remote-wipe-iphone-or-ipad/, 4 pages, printed from the Internet on Feb. 2, 2013. |
| “Screen hotspot,” Wikipedia, the free encyclopedia, http://en.wikipedia.org/wiki/Screen_hotspot, 1 page, printed from the Internet on May 15, 2013. |
| Number | Date | Country | |
|---|---|---|---|
| 20170255353 A1 | Sep 2017 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61674098 | Jul 2012 | US | |
| 61674102 | Jul 2012 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13946538 | Jul 2013 | US |
| Child | 15601153 | US |
